This page (revision-5) 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
5 26-Nov-2021 10:22 4 KB JEscott to previous
4 26-Nov-2021 10:22 4 KB JEscott to previous | to last
3 26-Nov-2021 10:22 4 KB JAiken to previous | to last
2 26-Nov-2021 10:22 4 KB JEscott to previous | to last
1 26-Nov-2021 10:22 3 KB JEscott to last

Page References

Incoming links Outgoing links
CONVERSION OVERVIEW
CONVERSION OVERVIEW

Version management

Difference between version and

At line 5 changed one line
One of the other effects that this has on converting data into the software application is that the conversion programs cannot read the data directly from flat files stored on the server. All records that are to be loaded into the software data structure must first be loaded into interface tables within the Oracle database itself, before being moved to the tables owned by P2K. Once the information has been loaded in these interface tables it can be edited or reported with the supplied screens and reports. Both the screens and report can be accessed from within the menu structure designed into the Conversion application.
One of the other effects that this has on converting data into the software application is that the conversion programs cannot read the data directly from flat files stored on the server. All records that are to be loaded into the software data structure must first be loaded into interface tables within the Oracle database itself, before being moved to the tables owned by the P2K user. Once the information has been loaded in these interface tables it can be edited or reported with the supplied screens and reports. Both the screens and report can be accessed from within the menu structure designed into the Conversion application.
At line 7 changed one line
Loading the software conversion data into the interface tables gives us the ability to verify that the loaded data is correct and in the format that the conversion programs require, prior to altering the [{$applicationname}] tables. This also allows us to perform any additional translation of the data that could not be performed prior to loading the information into the tables. Several third party applications are capable of reading, manipulating and storing the altered data back into Oracle tables. The use of SQL scripts to perform the same translation of the data is also available, and can be done with the utilities provided by Oracle.
Loading the software conversion data into the interface tables gives us the ability to verify that the loaded data is correct and in the format that the conversion programs require, prior to altering the tables. This also allows us to perform any additional translation of the data that could not be performed prior to loading the information into the tables. Several third party applications are capable of reading, manipulating and storing the altered data back into Oracle tables. The use of SQL scripts to perform the same translation of the data is also available, and can be done with the utilities provided by Oracle.
At line 10 changed one line
The [{$applicationname}] screens allow the users to key in all of the client data into the application in a structured format. The records need to be entered into the screen in a specific order and the data builds onto one another as it goes. If the quantity of records to be entered into some of the tables is small, keying them in will actually be faster that loading them in. However, there are a number of tables that need to have the records loaded into them in bulk.
The application screens allow the users to key in all of the client data into the application in a structured format. The records need to be entered into the screen in a specific order and the data builds onto one another as it goes. If the quantity of records to be entered into some of the tables is small, keying them in will actually be faster that loading them in. However, there are a number of tables that need to have the records loaded into them in bulk.
At line 12 changed one line
The purpose of these conversion utilities is to provide this bulk load mechanism for the [{$applicationname}] application. The records will still have to be loaded in the table in the same order that they would have to be keyed in. This is actually dictated by the data integrity constraints defined in the database, as part of the application configuration.
The purpose of these conversion utilities is to provide this bulk load mechanism for the application. The records will still have to be loaded in the table in the same order that they would have to be keyed in. This is actually dictated by the data integrity constraints defined in the database, as part of the application configuration.
At line 14 changed one line
During the initial installation of the application environment, three separate database where created. One of these databases will be called CONV or PROD, depending on the specific installation of Oracle and the Personality application.
During the initial installation of the application environment, three separate database where created. One of these databases will be called CONV or PROD, depending on the specific installation of Oracle and the application.
At line 21 changed one line
# Extract data from the legacy system into pre-defined, comma delimited data files (CSV files). Note; this step is only discussed for High Line products.
# Extract data from the legacy system into pre-defined, comma delimited data files (CSV files).
At line 23 changed one line
# Make changes to the load process to format the data as it is loaded to match [{$applicationname}] needs
# Make changes to the load process to format the data as it is loaded to match the application's needs
At line 25 changed 3 lines
# Apply any scripts needed to fix the data prior to converting into the [{$applicationname}] tables.
# Run the stored procedures to convert, or move, the records from the interface tables into the P2K tables.
# Verify the data loaded into the target database through screens and reports of the application and custom reports (I.E. Discoverer). If needed, drop the contents of the specific [{$applicationname}] table and reload the data (step 5).
# Apply any scripts needed to fix the data prior to converting into the tables.
# Run the stored procedures to convert, or move, the records from the interface tables into the application tables.
# Verify the data loaded into the target database through screens and reports of the application and custom reports (I.E. Discoverer). If needed, drop the contents of the specific table and reload the data (step 5).
At line 32 added 5 lines
----
![Notes|Edit:Internal.CONVERSION+OVERVIEW]
[{InsertPage page='Internal.CONVERSION+OVERVIEW' default='Click to create a new notes page'}]
This page (revision-5) was last changed on 26-Nov-2021 10:22 by JEscottTop