The Wiki 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 purpose of these conversion utilities is to provide this bulk load mechanism for the Wiki 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.
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.
This database is the one used for all the conversion processes. However, this database does not have any data in it. This database is usually created as a shell only. The following is the sequence of events that is followed to perform the conversion:
Installing the Oracle components and configuring the client for running the Conversion application is done once, for each computer or user that will participate in the conversion project. Typically, this is only one user on one computer. The remaining steps will be repeated several times until the process is working for all the tables that will be converted.
Screen captures are meant to be indicative of the concept being presented and may not reflect the current screen design.
If you have any comments or questions please email the Wiki Editor
All content © High Line Corporation