<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>v20.2 on </title>
    <link>/tags/v20.2/</link>
    <description>Recent content in v20.2 on </description>
    <generator>Hugo -- gohugo.io</generator><atom:link href="/tags/v20.2/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SICS 20.2</title>
      <link>/sicsdocs/technical/misc/technical_changes/20.2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/technical/misc/technical_changes/20.2/</guid>
      <description>SE-1861 # Adding a new column to an existing table when a default value needs to be set results in SQL to update the entire table. For a table with a large number of rows, this causes a large transaction log in Microsoft SQL Server.
To prevent this, large table updates on Microsoft SQL Server will be batched into increments of 10k rows when the Optimized Schema is in use.</description>
    </item>
    
    <item>
      <title>Introduction</title>
      <link>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/life/mtk_csv_file_utilities/introduction/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/life/mtk_csv_file_utilities/introduction/</guid>
      <description>The Life MTK CSV File Utilities consist of two parts, the export utility and the helper utility. The export utility is meant as an aid in the migration process. A domain object (business, business partner, bank, etc.) can be exported from the SICS system to a CSV file. This file can then be used as an example of how a CSV file should be constructed. The helper utility can be used to view the structure of the parts of a domain object.</description>
    </item>
    
    <item>
      <title>Introduction</title>
      <link>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/life/mtk_loader/introduction/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/life/mtk_loader/introduction/</guid>
      <description>In this document the term &amp;quot;MTK&amp;quot; will be an alias for &amp;quot;Migration Tool Kit&amp;quot;.
This document explains the concepts of the MTK and how to load data from a CSV file into SICS.
Performance # It is possible to execute data migrations on more than one machine at a time; however, each set of data has to be independent of any other migration. e.g. Split the input file containing business partners into several files where all information related to one single business partner is gathered in one file.</description>
    </item>
    
    <item>
      <title>Introduction</title>
      <link>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/pc/mtk_split_file_utility/introduction/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/pc/mtk_split_file_utility/introduction/</guid>
      <description>Purpose # MTK Splitter tool is a utility to split large CSV migration upload files into a set of smaller files of manageable size which can be easily uploaded by the MTK loader.
Abbreviation # In this document the term &amp;quot;MTK&amp;quot; will be an alias for &amp;quot;Migration Tool Kit&amp;quot;.
This document explains the concepts of the MTK Splitter and how to load data and Split Files from a CSV file into SICS.</description>
    </item>
    
    <item>
      <title>SAP BusinessObjects Enterprise</title>
      <link>/sicsdocs/sys_admin_guide/business_objects/database_connections/sap_boe/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/sys_admin_guide/business_objects/database_connections/sap_boe/</guid>
      <description>This section describes to setup database connections to various database systems for SAP BusinessObjects Enterprise.
Note: The SAP BusinessObjects Enterprise install directory is referred to as &amp;lt;install directory&amp;gt;.
Microsoft SQL Server # Note: The newest possible version of Microsoft SQL Server JDBC Driver that can be used by SAP BusinessObjects Enterprise is 6.4 because JRE 7 support was dropped in version 7.0.
Download the Microsoft JDBC Driver Version 6.4 from: Release Notes for the JDBC Driver: 6.</description>
    </item>
    
    <item>
      <title>Export Utility</title>
      <link>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/life/mtk_csv_file_utilities/export_utility/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/life/mtk_csv_file_utilities/export_utility/</guid>
      <description>The following actions are required to export a domain object:
Choose the type of domain object to export in the root objects drop-down list. You must provide the object ID unless the unique criteria of the record are unique in the database. Select a filename to export to. Press Start Export. A file with the name that was designated in the field Output file will be generated.
Figure 2 - Migration Manager Window</description>
    </item>
    
    <item>
      <title>Running The MTK Loader</title>
      <link>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/life/mtk_loader/running_the_mtk_loader/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/life/mtk_loader/running_the_mtk_loader/</guid>
      <description>Start the MTK Loader # Start the SICS Life Administration Utility as explained in the installation procedure. Open the Inbound Interfaces Folder and Migration Toolkit Folder and double click on the Migration Utility icon. This procedure will then start the Migration Manager.
Figure 1 - Life System Admin Desktop
SICS Migration Manager # Figure 2 - SICS Migration Manager
Input File The name of the file containing the data that you want to migrate into SICS.</description>
    </item>
    
    <item>
      <title>Running The MTK Splitter tool</title>
      <link>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/pc/mtk_split_file_utility/running_the_mtk_splitter_tool/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/pc/mtk_split_file_utility/running_the_mtk_splitter_tool/</guid>
      <description>Starting the Tool # Start the SICS P&amp;amp;C Administration Utility as explained in the installation procedure. Open the Inbound Interfaces Folder and Migration Toolkit Folder and double click on the Split Input File Utility icon.
This starts the Migration Toolkit File Splitter.
Figure 1 - SICS System Admin Desktop</description>
    </item>
    
    <item>
      <title>SAP BusinessObjects BI 4.3</title>
      <link>/sicsdocs/sys_admin_guide/business_objects/database_connections/sap_bo_bi_43/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/sys_admin_guide/business_objects/database_connections/sap_bo_bi_43/</guid>
      <description>This section describes to setup database connections to various database systems for SAP BusinessObjects BI 4.3.
Note: The SAP BusinessObjects BI 4.3 install directory is referred to as &amp;lt;install directory&amp;gt;.
Microsoft SQL Server # Note: SAP BusinessObjects BI 4.3 is using JRE 8, therefore, the JRE 8 version of the Microsoft JDBC Driver need to be used.
Download the Microsoft JDBC Driver from: Download Microsoft JDBC Driver for SQL Server.</description>
    </item>
    
    <item>
      <title>Helper Utility</title>
      <link>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/life/mtk_csv_file_utilities/helper_utility/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/life/mtk_csv_file_utilities/helper_utility/</guid>
      <description>The helper utility can be used to view the structure of the CSV definitions. It is possible to navigate down from a root object and view its parts. When an object is selected in the tree view the row definition is displayed in the Details view at the bottom. It is also possible to view a sample output line for the row definition by selecting the Example Line page.
Figure 3 - Helper Utility Tab</description>
    </item>
    
    <item>
      <title>Input Files</title>
      <link>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/life/mtk_loader/input_files/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/life/mtk_loader/input_files/</guid>
      <description>The Input File # The input file is a Comma Separated Value (CSV) file and can be created by an extraction program or through standard Windows utilities (e.g. Windows Notepad or Excel).
Restrictions to the format of the CSV input file Each field must be separated by comma. , Strings, if the field data contains a comma the whole field must be enclosed in double quotes. &amp;quot; Decimal points must be period.</description>
    </item>
    
    <item>
      <title>SICS Split Input File Utility</title>
      <link>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/pc/mtk_split_file_utility/split_input_file_utility/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/pc/mtk_split_file_utility/split_input_file_utility/</guid>
      <description>Figure 2 - File Splitter Window
File To Split The path of the csv file containing the data that you want to split Split Record Identifier This is the record identifier to be used to mark a split boundary Records Per file User input &amp;quot;Not Mandatory&amp;quot; can select the number of records needed in one file and system would calculate the number of files to be created based on number of records in input file.</description>
    </item>
    
    <item>
      <title>Output Files</title>
      <link>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/life/mtk_loader/output_files/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/life/mtk_loader/output_files/</guid>
      <description>The Rejected Records File # This file contains all records that were rejected by the migration process. The records written to this file are an exact copy of the rejected records from the input file.
After the error that generated the rejected records has been corrected the file of rejected records can be used as the input file for processing.
The Error Message File # In this file you will get an explanation as to why your records were rejected.</description>
    </item>
    
    <item>
      <title>Migrate Data into Loader Files</title>
      <link>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/life/mtk_loader/migrate_data_into_loader_files/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/life/mtk_loader/migrate_data_into_loader_files/</guid>
      <description>Introduction # One of the main performance problems with migration of data has to do with large number of inserts of new objects into the database using the SQL command interface. The database engine must parse each SQL insert statement. A significant portion (approximately 60%) of the data passed between the client and the server is information to help the parser figure out what kind of data it is, what format it is in, and where it goes.</description>
    </item>
    
    <item>
      <title>The Database Specific Loaders</title>
      <link>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/life/mtk_loader/db_specific_loaders/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/life/mtk_loader/db_specific_loaders/</guid>
      <description>The Oracle Loader # Oracle has a utility for doing bulk-inserts that is called SQLLOAD. If you are connected to an Oracle database server while doing migration, the data files that are output will be in the format required by the Oracle loader.
Each file has two sections, the header section and the data section. The header section gives information about the format and destination of the data, including the table, column names, types, order, and format information.</description>
    </item>
    
    <item>
      <title>The Load Sequence</title>
      <link>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/life/mtk_loader/load_sequence/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/sicsdocs/sys_admin_guide/sys_admin_utility/migration_toolkit/life/mtk_loader/load_sequence/</guid>
      <description>Joint Life Cession with retrocessions attached # Load sequence:
Load Joint Life Individual Cession (ex: AIC743).
Load Individual Retrocession (ex: AIC743-0).
Load OCC retrocession (ex: AIC743 and OUT10).
It has a link to both the inward cession and the retrocessionaire retrocession
Similar logic is used for Individual cessions with retrocessions linked.</description>
    </item>
    
  </channel>
</rss>
