You are on page 1of 4

Table Conversion

Table conversions are type of batch process that allows you to do high-speed manipulation of data in the tables. There are four types of conversion that allows you to do variety of data manipulation.

Data Conversion:
Which allows you to transfer or copy data from an input table or business view into one or more output tables using any amount of logic necessary to perform the transfer. You can also use data conversion to update records in the table or business view.

Data Copy:
This allows you to copy one or more tables from one data source or environment to another data source or environment.

Data copy with table input


This allows you to copy tables based on information from an input table. For example input table might provide information about which table should be copied, where they should be copied, and so on.

Batch delete
Batch delete allows you to delete records from a table or business view. The table conversion tool allows you to access any available environment, both for input and output. The environment that you choose determines which tables and business views available for the conversion and where the tables reside. The specification or description of the tables and business views is also determined by environments that you choose.

Types of Table you can convert


Standard OneWorld Tables these tables exist in object librarian. At the design time
only the specification is needed to reference the table.

Non-OneWorld Tables These tables dont have oneworld definition, but they reside
in a database supported by OneWorld at design time and runtime. You must set up a data source and environment in oneworld to point the location of non-OneWorld table.

Business Views in Table Conversion


For transferring data from multiple tables to a single table For transferring data from multiple tables to a multiple table Business views can only be used as a Input to the table conversion, not for an output. System cant provide support for joining foreign tables.

Text files in Table Conversion


You can import directly from, or export directly to, a text file as well. When you convert it text file is stored similar to a foreign table, with a single long text field. In text file conversion, the table name includes the path and the file name. If you do not specify the path default path will be used.

Using sort and selection criteria in table conversion


We can give sort criteria in a table conversion to process input rows in a sequence that groups related records together. TC allows adding logic when there is a change in the field. It simplifies the process of writing records to the multiple tables in typical one-to-many conversion.

Input and Output Environments


An environment consists of path code and one or more OCM mapping records that indicate where various oneworld objects reside. Environments are used to locate the input and output tables. To locate non-OneWorld tables, TC uses the default OCM mapping records for tables. Pathcode is usually a subdirectory under the oneworld directory on your work station. To reference oneworld tables in the environment, full path code must exist on the machine where the conversion is designed and run. Non-oneworld tables can be referenced even if the path code does not exist. TC uses three environments when it is in process The environment that you are signed into The environment for the input tables The environment for the output tables Environment that youre signed in determines where the TC specification is stored. You can select an environment for input table or view, and one for converted output tables. All three of these could be the same or they could all be different.

Event Flow of Table Conversion


Process Begin Open I/P & O/P Tables Selection & Seq Yes Yes No Data Seq? No Data Change in Sort Column? Data Change Ev Yes Format Fetch Event User Defined Format? Clear O/P Tables Process Begin Fetch from input Table

No

Row Fetch

Return to row Fetch

Yes

No More Records?

Process End

Events n Table conversion


Process begin
Before fetching any records from the input table, the system invokes the process begin event. You can attach any logic that process only once at the beginning of a conversion, or any other value that doesnt change for each and individual record.

Data Changed
If you use data sequencing, the system invokes a data changed event for any sequenced field that changed. You can attach an event rule to this event if you want total a field or group of values.

Format fetched
If you use user defined format (also known as flat files) on the input tables, the system invokes format fetch event for each record fetched from the input table.

Row fetched
An input table invokes a row fetched event after each row is fetched from the input table.

Process end
After al records have been processed the system invokes process end event. You can attach logic to count total records to an output table.

You might also like