0% found this document useful (0 votes)
70 views34 pages

Table Conversion 1

Table conversion is a batch process that allows high-speed manipulation of data in tables through various methods such as Data Conversion, Data Copy, and Batch Delete. The Table Conversion Director guides users through setting up these processes, providing options for defining input and output environments, mapping data, and applying event rules. Users can also utilize features like Data Copy with Table Input to automate copying based on predefined criteria and manage record deletions effectively.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
70 views34 pages

Table Conversion 1

Table conversion is a batch process that allows high-speed manipulation of data in tables through various methods such as Data Conversion, Data Copy, and Batch Delete. The Table Conversion Director guides users through setting up these processes, providing options for defining input and output environments, mapping data, and applying event rules. Users can also utilize features like Data Copy with Table Input to automate copying based on predefined criteria and manage record deletions effectively.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

TABLE CONVERSION

Table conversion is a type of batch process that allows you to manipulate the data in tables
at a high speed. The table conversion tool uses the following conversion types, which allow
you to manipulate data in a variety of ways:

• Data Conversion 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 also can use Data Conversion to update records in a table or business view.
• Data Copy 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 allows you to copy tables based on information from an input
table. For example, the input table might provide information about which tables should be
copied, where they should be copied to, and so on.
• Batch Delete allows you to delete records from a table or business view.
Table Conversion Director

The Table Conversion Director guides you through the process of setting up a table
conversion. The
Navigation Assistant, which appears within the Director, provides a visual reminder of where
you are
throughout the setup process. You also can use the Navigation Assistant to move to a
different step in
the process by clicking any step listed in the Assistant.

► To use the Table Conversion Director


From the Cross Application Development Tools menu (GH902), choose Object Management
Workbench.
1. Click Find.
2. Click the project to which the new batch process will be added, and then click Add.
3. On Add J.D. Edwards Object to the Project, choose Batch Application and click OK.
4. On Add Object, complete the following fields:
• Object Name
• Description
• Product Code
• Product System Code
• Object Use
5. Turn on the Table Conversion option, and then click OK.
6. On Batch Application Design, click the Design Tools tab and then click Start Table
Conversion Design Aid.
The system displays the Introduction form for the Table Conversion Director. Depending on
the conversion you want to perform, follow the steps that are described in the following
topics in this guide:
• Data Conversion
• Data Copy
• Data Copy with Table Input
• Batch Delete

Data Conversion
You use the Data Conversion option on the Table Conversion Director when you want to
move data
to one or more tables from:
• A single table
• Multiple tables defined in a business view
• A single text file
The Director leads you through a process for creating a data conversion batch application by
asking questions about its structure and function. When you are finished, you can review
and alter the conversion, if necessary.

► To define external data

1. On the Introduction form of the Table Conversion Director, click the Data Conversion
option and then click Next.
2. On the External Data form, click Select to attach a predefined processing option template
to the table conversion.
3. If you want to attach data structures, click Define.
4. On the Report Data Structure form, define the data structures that you want to attach to
the table conversion, and then click OK to return to the External Data Form.
5. Click Next.
► To define input and output environments
1. On the Select Environments form, choose the input and output environments that you
want to use.
2. If you are creating a table conversion that will run in a different environment than the one
in which you are creating it and the <LOGIN ENV> is not appropriate for the type of
conversion that you are creating, click the Force Version to Override Input Environment
option or the Force Version to Override Output Environment option.
For example, if you create a conversion that will be shipped to a client who does not have
the environments that you have, you would turn on these options. When the conversion is
invoked at the client site, the system will not run the conversion until the user chooses an
appropriate environment in which to run it.
3. Click Next
► To define input
1. On the Select Input form, click the appropriate tab (based on whether your input is a
table, a business view, a foreign table, or a text file).
2. If your input is a table or a business view, drag it to the Description pane.
If you know the name of the table or business view that you want to use, enter the name in
the Object Name field in the query by example (QBE) line and press Enter.
You can choose only one table or one business view per conversion. If your input consists of
multiple tables, you must create a single, joined business view.
3. If your input is a text file, on the Text File tab, type the name of the file and click Use or
click Browse and then open the appropriate text file.
4. To delete an input name, choose it and press Delete.
5. Click Next.
6. On the Sequencing form, click Data Sequencing to define data sequencing for a table or
business view.
If you specify a text file for input, you cannot define data sequencing or selection for that
file.
► The Data Selection form appears
► To define output

1. On the Select Outputs form, drag the table or tables that you want to use as your outputs
to the Description pane on the right and click Next.
2. For text file conversions, from the Text File tab, choose the file that you want to use as
your output and click Use.
3. Click Next.

► On Table Options
• Run Currency Triggers- Choose this option if the PeopleSoft EnterpriseOne table or tables
contain currency triggers.
• Clear Output Tables
• Force Row by Row Processing- Choose this option if, for example, you want to test the
table conversion or if you want to ensure that the conversion always runs in row-by-row
mode.
• Buffer Inserts To Output Tables- Choose this option to improve conversion performance if
you have no event rules in place to process insertion errors and if you are processing row by
row.
► To map inputs to outputs
1. On the Mapping form, specify the event on which you want mapping to occur by choosing
an event from the Events list.
In most cases, you use either the Row Fetched event or Format Fetched event. For example,
if you are working with a user-defined format, choose the Format Fetched event.
2. Click Advanced ER to further modify your mappings based on a particular event.
3. Click Map Same to map your inputs directly to outputs.
4. Drag inputs to outputs to define exactly where you want information to map.
Note:
Click Delete to erase the mapping for a selected output. Click Delete All to erase the
mapping for all outputs.
5. If you have multiple output files, choose each file from the outputs list and map the
appropriate input columns to output columns.
6. To define advanced output, double-click an output column.
The Advanced Outputs form appears. This form allows you to define literals, calculations,
and other mappings without using Advanced ER. You might want to use an advanced input
to add a constant, literal value into a field. Or, you might want to insert a calculation into an
output field, such as adding two input fields together.
7. On Advanced Outputs, click one of the following tabs and add the appropriate input:
• Available objects
Choose the output column, choose the appropriate value, and then click Apply.
• Literal
Choose the output column, enter the appropriate value, and click Apply.
• Defaults
Choose the Use Dictionary Defaults option, and then click Apply.
Use this option if you want to use the default value in the data dictionary at runtime. If no
default values exist in the data dictionary, the system displays a warning message.
• Calculation
Click Define Calculation and then define a calculation in Expression Manager.
8. When you finish defining an advanced input, click Apply and then click Close.
9. On Mapping, choose the Issue a Write for this Event option to insert a row to the selected
output after performing all column mappings for this event.
10. Click Next.
► To choose logging options

► To Create Version
► To review the results of the director
Copying Data
You use the Data Copy feature on the JD Edwards EnterpriseOne Table Conversion director
to copy tables from one environment or data source to another. You can also import a copy
table script to use in the conversion.

 Select Data Copy, and click Next.

 On the External Data form, select a processing option template, define a data
structure, as appropriate, and click Next.
 On the Select Environments form, select an input environment and an output
environment, and click Next.

 On the Select Actions form, enter the name of a table in the Table field of the grid.
If you want to copy a single table, select <Literal>, and enter the name of that table on the
Single Value tab. If you do not know the name of the table that you want to copy, use the
<Find a Table> option.
When you enter the name of a table, the system automatically populates the remaining
fields for you.
On the Select Actions form, modify these fields as necessary:
o To Table
Enter either the last table in a range of tables to be copied, or
leave the field blank if you are copying a single table.
o Source Type
Select Data Source if the input and output sources are data
sources. Select Environment if the input and output sources
are environments.
When you select Data Source, the system retrieves table
definitions from the specifications in the sign-in environment.
When you select Environment, the system uses the input and
output environments to locate data and specifications for the
tables. This enables the specifications to be different in the
input and output environment, but the data is copied.
o Input Source
Select the data source or environment from which the input is
read.
o Output Source
Select the data source or environment to which the output is
written.
o Create
When you select <If Table Exists>, the system creates the
table in the output and runs the conversion only if both the
table specifications and the actual table exist in the input.
When you select <Yes>, the system creates the table in the
output. If the table already exists in the output, the system
deletes it and creates a new table.
When you select <No>, the system assumes that the table
already exists in the output and does not create it.
o Clear
When you select <If Table Exists>, the system clears the
table in the output only if it exists in the input.
When you select <Yes>, the system deletes all rows in the
output table before copying the table.
When you select <No>, the output table is not cleared.
Note: If you select <No> to not clear the output table, the
conversion could result in key conflicts.
o Copy
When you select <Yes>, the system copies the data from the
input table to the output table using Map Same.
When you select <No>, no data is copied.
o Owner ID
o Owner Pwd (owner password)
If the data source requires an owner ID and password, enter
them here. If you leave these fields blank, the system enters
the ID and password of the sign-in user, or <None> if the
data source does not have security.

 To import an existing copy table script from another location, click Import, locate
the file that you want to import, and click Open.
The system adds an action for each copy table item in the copy table script.

 Click Advanced ER to add event rule logic to the copy table process, and click Next.
You can use event rules to write a custom copy table script.

 On the Logging Options form, select the appropriate logging options, and click
Next.
 On the Finish form, select a version option, and click Finish.

► To review the results of the director


Copying Data with Table Input
The Data Copy with Table Input feature is similar to the Data Copy option, except that it
allows information for the process to come from an input table. The input table might
provide information about which tables are copied, where they are copied, and so on. The
Data Copy with Table Input feature enables you to select data.

For example, suppose that you create a table that includes:

 A table name
 The next backup date
 The backup frequency
You might populate this table with a list of tables to be archived and information specifying
how often they are archived. You can then use the Data Copy with Table Input feature to
select all rows in which the backup date is less than or equal to the current date, and
calculate a new backup date.

 Select Data Copy with Table Input, and click Next.

 On the External Data form, select a processing option


template, define a data structure, as appropriate, and click
Next.
 On the Select Environments form, select an input
environment and an output environment, and click Next.

 On the Select Input form, select a table, business view, or


foreign table, and click Next.
 On the Sequencing form, define data sequencing as
appropriate, and click Next.

 On the Data Selection form, define data selection as


appropriate, and click Next.
 On the Table Options form, select Run Currency Triggers, if appropriate, and click
Next.
Select this option if a JD Edwards EnterpriseOne table included in the table
conversion contains currency triggers. If a table contains currency fields and you do
not select this option, the system cannot determine where the decimal should be
placed within a field. If you do not select the currency trigger option and the source
or destination fields are currency fields used in a calculation, you might receive
unexpected results.
Do not select Run Currency Triggers if the input and output data sources are the
same type (for example, Oracle, IBM i, or SQL Server) and no calculations are being
performed. Selecting this option results in slower processing.
You should not use currency triggers for an environment that has a different path
code than the login environment.
On the Select Actions form, enter the name of a table in the Table
field, modify the remaining fields as appropriate, and click Next.

 To import an existing copy table script from another


location, click Import, locate the file that you want to
import, and click Open.

 Click Advanced ER to add event rule logic to the copy table


process, and click Next.
 On the Logging Options form, select logging options, and
click Next.

 On the Finish form, select a version option, and click Finish.

Deleting Groups of Records


The Batch Delete feature enables you to delete a range of records from a JD Edwards
EnterpriseOne input table or foreign table based on selection criteria that you define. For
example, you can set up a batch delete table conversion that deletes records in an input
table that does not contain valid data. You can also set up table conversions that delete all
records from a particular table.

 Select Batch Delete, and click Next.

 On the External Data form, select a processing option template, define a data
structure, as appropriate, and click Next.

 On the Select Environments form, select a source environment, and click Next.
 On the Select Input form, drag the appropriate table to the Description column,
and click Next.
To delete an input table, select it and press Delete.

 On the Table Options form, select Run Currency Triggers, if appropriate, and click
Next.
Select this option if a JD Edwards EnterpriseOne table included in the table conversion
contains currency triggers. If a table contains currency fields and you do not select this
option, the system cannot determine where the decimal should be placed within a field. If
you do not select the currency trigger option and the source or destination fields are
currency fields used in a calculation, you might receive unexpected results.

Do not select Run Currency Triggers if the input and output data sources are the same type
(for example, Oracle, IBM i, or SQL Server) and no calculations are being performed.
Selecting this option results in slower processing.
You should not use currency triggers for an environment that has a path code that is
different from the sign-in environment.

 On the Data Selection form, define data selection as appropriate.


 Select the Row Fetched event when deleting rows; otherwise, no records are
deleted.

When you run the table conversion, the system fetches the rows one at a time, runs the
conversion for each row, and deletes the record from the input.

Click Advanced ER to insert additional event rule logic.

Verify that the Delete All Selected Records option is selected, and click Next.

This option inserts the Delete Current Input Row system function into event rule.

 On the Logging Options form, select logging options, as appropriate, and click Next.
 On the Finish form, select a version option, and click Finish.

► To review the results of the director


Understanding Event Rules in Table Conversions
You can use event rules to build complex functional logic into table conversions. For
example, you can use event rules to insert information into a table or delete rows in a table
based on specific conditions.

You attach event rules to an event, such as:

 Process Begin
 Row Fetched
 Format Fetched
 Process End

Event rules in table conversions include system functions that are specific to JD Edwards
EnterpriseOne Table Conversion Design Aid.

Table Conversion System Functions


System Function Description

CopyTableDataSource Enables you to copy a table or range of tables


from one data source to another. The system
copies tables based on specifications in the
sign-in environment.

CopyTableEnvironment Enables you to copy a table or range of tables


from one environment to another. The system
copies tables based on specifications in the
input and output environments. If the
specifications differ, the system performs a
map-and-drop. This means that it creates a
mapping between like fields in the source and
destination tables and ignores all other fields.

TCInsertRow The table conversion system inserts this


system function when you select the Issue a
write for this event? option and it cannot be
moved. This function instructs the system that
data should be written to the output table.

UserInsertRow Enables you to specify when and where a row


is inserted into the specified output table.

DeleteCurrentInputRow Enables you to delete the current record from


the input table.

UpdateCurrentInputRow Enables you to update the current record in


the input table after it has been modified.

SetSelectionAppendFlag Enables you to determine whether selection


criteria that is added by the system function
SetUserSelection on the input table should be
appended to the existing selection criteria or if
it should replace the existing selection criteria.

SetUserSelection Enables you to conditionally modify data


selection on the input table. Call
SetSelectionAppendFlag before calling
SetUserSelection to indicate whether to
replace or append to the existing data
selection.

Creating Event Rules in Table Conversions

Access a table conversion form that includes an Advanced ER button.


 From the Events drop-down list, select the event to which you want
to attach event rules, and click Advanced ER.
 On the Event Rules Design form, select any of these options to
define specific business logic:
o Assignment
Select this option to assign a fixed value, a field, or a
mathematical expression to a field or variable.
o If\While
Select this option to create If and While logic statements,
which are conditional instructions for event rule logic.
o Business Function
Select this option to attach an existing JD Edwards
EnterpriseOne business function to an event. Business
functions can retrieve a next number value for a new
customer or convert Julian calendar dates to month, day, and
year.
o System Function
Select this option to attach an existing JD Edwards
EnterpriseOne system function, such as Copy Table
Environment or User Insert Row.
o Variables
Select this option to create event rule variables, using existing
data items, to store values for additional processing. Event
rule variables can be used to accumulate totals, record the
number of records that are read, and so on.
o Else
Select this option to create Else logic statements. An Else
statement is automatically inserted after an If statement.
o Table I/O
Select this option to open tables in the input, output, or sign-in
environment. Table I/O enables you to read data from tables
other than the input table and use the data to create an
output record. For example, suppose that you create a table
conversion that loops through records in the F0101 table. The
table conversion copies the records to another table, loops
back through the records to find each customer that has a
specific employee as a contact, and copies the information to
the output table.
o Report Interconnect
Select this option to connect a batch process or report to the
table conversion.
 Define the logic, save the event rules, and quit Event Rules Design.

You might also like