This page (revision-4) was last changed on 26-Nov-2021 10:22 by JEscott

This page was created on 26-Nov-2021 10:22 by JEscott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
4 26-Nov-2021 10:22 3 KB JEscott to previous
3 26-Nov-2021 10:22 2 KB JEscott to previous | to last
2 26-Nov-2021 10:22 2 KB JAiken to previous | to last
1 26-Nov-2021 10:22 2 KB JEscott to last

Page References

Incoming links Outgoing links
CONVERTING DATA IN INTERFACE TABLES
CONVERTING DATA IN INTERFACE TABLES

Version management

Difference between version and

At line 3 changed one line
Since the size of the modification tokens in the SQL Loader .CTL files are limit to 256 characters and can only work with one record at a time, there are times when the data must be loaded into the INF table before it can be modified and then converted. This also simplifies the extract and load process for the legacy data, as all the data manipulation to fit the Personality environment is done with .SQL scripts after the data has been loaded into the INF tables.
Since the size of the modification tokens in the SQL Loader .CTL files are limit to 256 characters and can only work with one record at a time, there are times when the data must be loaded into the INF table before it can be modified and then converted. This also simplifies the extract and load process for the legacy data, as all the data manipulation to fit the environment is done with .SQL scripts after the data has been loaded into the INF tables.
At line 5 changed one line
This step of the conversion process is optional, and may not be needed for all files being loaded into Personality. Each table will need to be evaluated to see if modification scripts will be needed to complete the conversion of the data. Typically, modification scripts are used on the data if it is easier to access the needed in formation from other tables in Personality. An example of this would be the loading of SUNDRYLINES. The IPSN screen, the P2K_PR_SUNDRY_LINES and P2K_PR_SUNDRY_LINE_DETAILS tables require specific data for the pay components to be loaded into the records. This information is stored on the pay component definition tables and can be seen in the IPPC screen of Personality. It is very unlikely that this information will be available to the routines that will be used to extract the data, or during the loading of it into the INF table.
This step of the conversion process is optional, and may not be needed for all files being loaded in. Each table will need to be evaluated to see if modification scripts will be needed to complete the conversion of the data. Typically, modification scripts are used on the data if it is easier to access the needed information from other tables in the application. An example of this would be the loading of SUNDRY LINES. The [IPSN] screen, the [P2K_PR_SUNDRY_LINES] and [P2K_PR_SUNDRY_LINE_DETAILS] tables require specific data for the [pay components|PAY COMPONENTS] to be loaded into the records. This information is stored on the pay component definition tables and can be seen in the [IPPC] screen. It is very unlikely that this information will be available to the routines that will be used to extract the data, or during the loading of it into the INF table.
At line 11 changed one line
The following sample script will delete all the records from the INF_CV_ASSIGNMENTS for employees that the POSITION record does not exist for:
The following sample script will delete all the records from the [INF_CV_ASSIGNMENTS] for employees that the POSITION record does not exist for:
At line 17 added 5 lines
----
![Notes|Edit:Internal.CONVERTING+DATA+IN+INTERFACE+TABLES]
[{InsertPage page='Internal.CONVERTING+DATA+IN+INTERFACE+TABLES' default='Click to create a new notes page'}]
This page (revision-4) was last changed on 26-Nov-2021 10:22 by JEscottTop