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

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
9 26-Nov-2021 10:22 3 KB RForbes to previous
8 26-Nov-2021 10:22 3 KB JEscott to previous | to last
7 26-Nov-2021 10:22 3 KB JAiken to previous | to last
6 26-Nov-2021 10:22 3 KB JEscott to previous | to last
5 26-Nov-2021 10:22 3 KB JEscott to previous | to last
4 26-Nov-2021 10:22 3 KB JEscott to previous | to last
3 26-Nov-2021 10:22 3 KB JEscott to previous | to last
2 26-Nov-2021 10:22 3 KB JEscott to previous | to last
1 26-Nov-2021 10:22 3 KB JEscott to last

Page References

Incoming links Outgoing links
CONVERTING DATA INTO P 2 K TABLES (PL SQL ROUTINES)
CONVERTING DATA INTO P2K TABLES (PL SQL ROUTINES)

Version management

Difference between version and

At line 1 changed one line
!!!Converting Data into P2k Tables [PL/SQL Routines]
!!!Converting Data into P2k Tables (PL / SQL Routines)
At line 3 changed one line
The conversion of the data from the interface tables, into the P2K tables, is actually performed by stored procedures within the database. There are over 60 of these procedures stored in the P2K schema of the database. Each procedure will read the contents of one of the interface tables and insert the records into the corresponding P2K tables. The records being inserted in the database may actually insert into several tables, from the one interface table. For example, the data from the INF_CV_PERSONALS table is actually inserted into the [P2K_HR_IDENTITIES], [P2K_HR_PERSONALS], [P2K_HR_ALIASES] and [P2K_HR_USER_FIELD_VALUES] tables. Certain columns within this interface table will store their data in one of these columns of these tables. At the end of each report that the conversion process generates the number of records inserted into each table will be identified.
The conversion of the data from the interface tables, into the application tables, is actually performed by stored procedures within the database. There are over 60 of these procedures stored in the P2K schema of the database. Each procedure will read the contents of one of the interface tables and insert the records into the corresponding P2K tables. The records being inserted in the database may actually insert into several tables, from the one interface table. For example, the data from the [INF_CV_PERSONALS] table is actually inserted into the [P2K_HR_IDENTITIES], [P2K_HR_PERSONALS], [P2K_HR_ALIASES] and [P2K_AM_USER_FIELD_VALUES] tables. Certain columns within this interface table will store their data in one of these columns of these tables. At the end of each report that the conversion process generates the number of records inserted into each table will be identified.
At line 9 changed one line
As the records are read and processed by the conversion procedures they are deleted from the INF table if they are successfully inserted into the P2K tables. When the conversion procedure completes, if any records generated errors they will not be moved to the P2K tables and will not be delete from the INF table. These records can be corrected within the conversion application screens and then converted again to be moved to the P2K tables.
As the records are read and processed by the conversion procedures they are deleted from the INF table if they are successfully inserted into the application tables. When the conversion procedure completes, if any records generated errors they will not be moved to the application tables and will not be delete from the INF table. These records can be corrected within the conversion application screens and then converted again to be moved to the application tables.
At line 11 changed one line
When the number of bad records exceeds the maximum error count allowed in the conversion procedure and abort error will be displayed at the end of the conversion report. The records that remain in the INF table of the database will contain both error records and records that have not been processed yet. The unprocessed records could be additional error records or valid records that would be moved to the P2K tables if there were processed. Until the error records are corrected [or deleted] these additional records will not get processed by the conversion routines.
When the number of bad records exceeds the maximum error count allowed in the conversion procedure and abort error will be displayed at the end of the conversion report. The records that remain in the INF table of the database will contain both error records and records that have not been processed yet. The unprocessed records could be additional error records or valid records that would be moved to the P2K tables if there were processed. Until the error records are corrected (or deleted) these additional records will not get processed by the conversion routines.
Since the report can be extremely large after the first run through the records in the interface table, the initial report can be ignored and the conversion process be run a second time. During the second processing of the records it will abort after processing the first 50 errors. All the good records will have been deleted from the interface table, leaving the bad records and unprocessed records after them. This version of the report will contain errors only and can be printed without wasting a large amount of paper with irrelevant information.
----
![Notes|Edit:Internal.CONVERTING DATA INTO P2K TABLES (PL SQL ROUTINES)]
[{InsertPage page='Internal.CONVERTING DATA INTO P2K TABLES (PL SQL ROUTINES)' default='Click to create a new notes page'}]
This page (revision-9) was last changed on 26-Nov-2021 10:22 by RForbesTop