Skip Headers
JD Edwards EnterpriseOne Tools Table Conversion Guide
Release 9.1

E24236-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

4 Running Table Conversions

This chapter contains the following topics:

4.1 Understanding Table Conversion Processing

You run a table conversion by submitting an associated batch version.

To track the table conversion process, you can use the tracing feature. The tracing feature writes the details of the table conversion process to a log. You can define the trace level to control the level of detail that is included in the log. When you test a table conversion, you can select to process the conversion one row at a time, which enables you to isolate problems or unexpected results.

4.2 Submitting Table Conversions

This section provides overviews of submitting table conversions and overriding table conversion properties and discusses how to:

4.2.1 Understanding Submitting Table Conversions

When you submit versions of table conversions, you can override table conversion properties, such as:

  • Input and output environments.

  • Trace level.

  • Location where the table conversion is processed.

    Overriding the location where you process the table conversion enables you to process the table conversion even if the server that you normally use is inoperable.

4.2.2 Understanding Overriding Table Conversion Properties

When you submit versions of table conversions, you can override these properties:

Properties Description
Environments Enables you to change the location of the input or output data.
Data selection Enables you to limit the number of input records.
Table options Enables you to control how the JD Edwards EnterpriseOne Table Conversion system processes records during the conversion.
Logging options Enables you to modify logging options.
Debug logging Enables you to override the setting for debug logging as defined in the jde.ini.

4.2.2.1 Table Conversions on the Web Client

Submitting versions of table conversions from the web client is different from submitting them from the Microsoft Windows client. From the web client, you cannot modify properties. You can select and modify processing options and you can select these options:

  • Override Location

  • Override Job Queue

  • Submit Version Specifications Only

  • Data Selection

See "Copying Batch Version Specifications to an Enterprise Server" in the JD Edwards EnterpriseOne Tools Batch Versions Guide.

4.2.3 Forms Used to Submit Table Conversions

Form Name FormID Navigation Usage
Work With Batch Versions - Available Versions W98305A EnterpriseOne Life Cycle Tools, Report Management (GH9111), Batch Versions Enter a table conversion template, and select a version.
Table Conversion Prompting W98305D Highlight a version on the Work With Batch Versions form, and click Select. Work with versions.
Properties NA Select the Properties option on the Table Conversion Prompting form, and click Submit. Review and override the environments, data selection, table options, and logging options that are specified within the conversion.
JD Edwards Data Sources W98305B Select the Override Location option on the Table Conversion Prompting form, and click Submit. Select a data source to use as an override location.

4.2.4 Overriding Table Conversion Properties at Runtime

Access the Work With Batch Versions - Available Versions form.

Note:

When you override table conversion properties at runtime, the overrides are for that single process only; they are not saved with the version.
  1. Enter the name of the table conversion template in the Batch Application field, and click Find.

    The name of the Batch Application field changes to Table Conversion.

    You can also use the visual assist in the Batch Application field to search for the correct table conversion.

  2. Select a batch version, and click Select.

  3. On the Table Conversion Prompting form, select Properties, and click Submit.

  4. On the Properties form, review and override the environments, data selection, table options, and logging options that specified in the table conversion.

    These forms are similar to the forms in Table Conversion Design Aid.

  5. Select the Debug Logging tab to perform these functions:

    • Select the Use ini settings for trace level and number of rows to process option to use the jde.ini settings for the trace level and row-by-row conversion process.

      This option ensures that the system uses the settings that are defined in the jde.ini instead of the values that are entered in the Trace Level and Number of Rows fields.

    • Clear the Use ini settings for trace level and number of rows to process option to override the trace level in the jde.ini. Enter a value from 0 to 10 in the Trace Level field.

    • Clear the Use ini settings for trace level and number of rows to process option to convert a specific number of records (for example, if you want to test the table conversion). Enter the number of rows to process in the Number of Rows field.

      When you enter 0 in the Number of Rows field, the system processes all rows.

      This option corresponds to the StopAfterRow setting in the jde.ini file. If you enter a value here, you override any specifications in the jde.ini.

  6. Click OK to save the changes to the version.

    The system processes the table conversion.

4.2.5 Overriding Table Conversion Properties of New Versions

Access the Work With Batch Versions - Available Versions form.

Note:

If you override table conversion properties from the Tools tab, the new properties are saved with the version.
  1. Enter the name of the table conversion in the Batch Application field, and click Find.

    The name of the Batch Application field changes to Table Conversion.

    You can also use the visual assist in the Batch Application field to search for the correct table conversion.

  2. Add a new version of the table conversion, complete the version information, and click OK.

  3. On the Table Conversion Version Design form, select the Tools tab, and click Properties.

  4. On the Properties form, review and override the environments, data selection, table options, and logging options that are specified in the table conversion.

    These forms are similar to the forms in Table Conversion Design Aid.

  5. To use debug logging, select the Debug Logging tab to perform these functions:

    • Select the Use ini settings for trace level and number of rows to process option to use the jde.ini settings for the trace level and row-by-row conversion process.

      This option ensures that the system uses the settings that are defined in the jde.ini instead of the values that are entered in the Trace Level and Number of Rows fields.

    • Clear the Use ini settings for trace level and number of rows to process option to override the trace level in the jde.ini. Enter a value from 0 to 10 in the Trace Level field.

    • Clear the Use ini settings for trace level and number of rows to process option to convert a specific number of records (for example, if you want to test the table conversion). Enter the number of rows to process in the Number of Rows field.

      When you enter 0 in the Number of Rows field, the system processes all rows.

      This option corresponds to the StopAfterRow setting in the jde.ini file. If you enter a value here, you override any specifications in the jde.ini file.

4.2.6 Overriding Table Conversion Locations

Access the Work With Batch Versions - Available Versions form.

  1. Enter the name of the table conversion in the Batch Application field, and click Find.

    The name of the Batch Application field changes to Table Conversion.

    You can also use the visual assist in the Batch Application field to search for the correct table conversion.

  2. Select a batch version, and click Select.

  3. On the Table Conversion Prompting form, select Override Location, and click Submit.

  4. On the JD Edwards Data Sources form, select the data source to use, and click Select.

4.2.7 Running Table Conversions from the Web Client

From EnterpriseOne Menu, select Submit Job to access the Submit Job-Work With Batch Versions-Available Versions form.

  1. Enter the name of the table conversion in the Batch Application field, and click Find.

    The name of the Batch Application field changes to Table Conversion.

  2. Select a batch version, and click Select.

  3. On the Table Conversion Prompting form, select from these override options, and click Submit:

    • Override Location

    • Override Job Queue

    • Submit Version Specifications Only

    • Data Selection

  4. Modify the appropriate property, and submit the batch version.

4.3 Testing Table Conversions

This section provides an overview of table conversion testing and discusses how to:

4.3.1 Understanding Table Conversion Testing

You can test table conversions in proof mode to ensure that they are processed as expected without errors. You can log debug information about the conversion while it is being processed. You can also force the conversion to process one row at a time, which is useful if the conversion normally runs as an insert-from-select.

To log debug information for table conversions, enable tracing and set a trace level in the jde.ini. Use a value in the range of 0 to 10 for the trace level. These values indicate the level of detail that you want to include in the log. If necessary, you can override the jde.ini settings on the batch version of a table conversion.

If you set the trace level for logging at 1, the system logs basic information about the table conversion, such as:

  • Name

  • Inputs

  • Outputs

  • Event rule logic

  • Number of rows inserted

If you set the trace level at 10, the system logs all information about every column in every format, including:

  • User-defined formats.

  • Processing options that are associated with the table conversion.

  • All other information that is involved in the table conversion process.

The higher that you set the trace level, the more details the system provides regarding the table conversion process.

You can force row-by-row processing on the workstation or on the server when you want to test the table conversion. You can also set a trace level on the workstation or on the server, depending on where you process the table conversion. You can specify the number of rows to process in combination with forcing a row-by-row conversion.

4.3.1.1 Difference Between Logging Options and Debug Logging

Logging options, which you define when you set up a table conversion, can log:

  • All errors that occur during the table conversion.

  • All records that are copied, deleted, or updated.

  • Details of copy table actions.

Debug logging logs more detailed information about the table conversion. This information enables you to determine the exact area in the table conversion where errors occurred.

Note:

If you modify the debug logging in the batch version, you override the settings in the jde.ini.

4.3.1.2 Trace Levels

You can define a trace level for debug logging either on a workstation or on a server, depending on where you run the table conversion.

This table describes the logging information for each trace level:

Trace Level Logging Information
Level 1 Logs general information about the conversion, such as name, inputs, outputs, event rule logic, and how many rows were inserted.
Level 2 Logs function call traces, such as starting conversion, ending conversion, and inserting rows. Also includes all level 1 information.
Level 3 Logs the points at which event rules are processed. Also includes all level 1 and level 2 information.
Level 4 Not applicable.
Level 5 Logs the points at which jdeCallObject is processed, such as calls to business functions from event rules. Also includes all level 1, level 2, and level 3 information.
Levels 6-8 Not applicable.
Level 9 Logs the content of columns during input, the processing of event rules, and the content before output. Also includes all level 1, level 2, level 3, and level 5 information.
Level 10 Logs all information for all applicable levels.

Important:

Do not set the trace level at 10 when running a table conversion on tables that contain large amounts of data. The system writes the data to the server, and large amounts of data can cause the server to run out of disk space. You can, however, specify the number of rows to process on the batch version properties form.

4.3.2 Setting the Trace Level for Debug Logging on the Workstation

To define the trace level for debug logging on the workstation.

  1. Open the jde.ini on the workstation.

  2. To enable tracing and to set the trace level on a workstation, add this new information to the [TCEngine] section of the jde.ini:

    [TCEngine]
    _continue-
    TraceLevel=n
    

    where n is a number from 0 through 10.

  3. To enable tracing and to set the trace level on a workstation, modify this information in the [Debug] and [UBE] sections of the jde.ini:

    [Debug]
    Output=File
    
    [UBE]
    UBESaveLogFile=1
    

4.3.3 Setting the Trace Level for Debug Logging on the Server

To define the trace level for debug logging on the server.

  1. To enable tracing and to set the trace level on a server, set the following information in the [TCEngine] section of the server jde.ini:

    [TCEngine]
    
    TraceLevel=n
    

    where n is a number from 0 to 10.

  2. To enable tracing and to set the trace level on a server, modify this information in the [Debug] section of the server jde.ini:

    [Debug]
    Output=File
    
    KeepLogs=1
    

4.3.4 Forcing Row-By-Row Conversion

To force row-by-row conversion and specify the number of rows to process:

  1. Open the jde.ini file.

  2. To force row-by-row conversion, add this new information to the [TCEngine] section of the jde.ini:

    [TCEngine]
    ForceRowByRow=1
    _Continue -
    
  3. To specify the number of rows to process, add this new information to the [TCEngine] section of the jde.ini:

    StopAfterRow=n
    

    where n is the number of rows that you want to process.