Skip Headers
JD Edwards EnterpriseOne Applications Interoperability Fundamentals Implementation Guide
Release 9.1

Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Feedback page
Contact Us

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

3 Processing Interoperability Transactions

This chapter contains the following topics:

3.1 Processing Inbound Interoperability Transactions

This section provides overviews of inbound interoperability and of the Inbound Flat File Conversion program and discusses how to:

  • Run the Inbound Flat File Conversion program (R47002C).

  • Set processing options for the Inbound Flat File Conversion program (R47002C).

3.1.1 Understanding Inbound Interoperability

In an inbound transaction, you accept data from another system into a JD Edwards EnterpriseOne system. Processing inbound transactions consists of these tasks:

  1. The external system sends data to JD Edwards EnterpriseOne interface tables, which hold the data before it is copied to the application tables.

    The external system is responsible for conforming to the format and other requirements of the interface tables. If the external system cannot write the information in the required format, it can write the data to a flat file, and you can use the Inbound Flat File Conversion program to convert the data to the required format.

  2. You run a transaction process (a batch program) that validates the data, updates valid data from the interface tables to the JD Edwards EnterpriseOne application tables, and sends action messages to the Employee Work Center about invalid data.

  3. You use an inquiry function to interactively review and revise the incorrect data, and then run the transaction process again.

    You repeat this step as often as needed to correct errors. Receiving Transactions

When receiving data, the system stores the unedited data sent from the external system in interface tables. With this method, unedited transactions do not affect application tables. The next step is to run the appropriate transaction process to edit the transactions and update the appropriate application tables.

To be received into the interface tables, data from an external system must conform to the minimum field requirements specified for the interface table.

The receiving transaction process performs these tasks:

  • Validates the data in the interface table to ensure that data is correct and conforms to the format defined for the application table system.

  • Updates the associated application table with validated data.

  • Produces a report that lists invalid transactions and sends an action message for each invalid transaction to the Employee Work Center.

  • Marks, in the interface tables, those transactions that have been successfully updated to the application tables.

If the report indicates errors, access the Employee Work Center from Workflow Management (G02) and review the messages in the message center. Then use the associated inquiry function to review and revise the transactions and to rerun the transaction process.


When you run the Inbound Flat File Conversion program (R47002C) and it completes successfully, the system automatically starts the transaction process if that action is specified in the processing option for the conversion.

3.1.2 Understanding the Inbound Flat File Conversion Program

You use the Inbound Flat File Conversion program (R47002C) to import flat files into JD Edwards EnterpriseOne interface tables. You can create a separate version of the Inbound Flat File Conversion program for each interface table. This program recognizes both the flat file from which it reads and the record types user-defined code (UDC) (00/RD) within the flat file. Each flat file contains records of differing lengths, based on the interface table record to which they correspond. The Inbound Flat File Conversion program uses the Flat File Cross-Reference Table (F47002) to convert the flat file into the interface tables. The F47002 table indicates to the conversion program which flat file to read from and which interface table to use, based on the transaction type that you are receiving.

The conversion program reads each record in the flat file and maps the record data into each field of the interface tables, based on the text qualifiers and field delimiters that are specified in the flat file.

The conversion program inserts the field data as one complete record in the interface table. If the conversion program encounters an error while converting data, it withholds the data in error and continues processing the conversion. If the data is successfully converted, the system automatically starts the transaction process for that interface table, provided that you set the processing options in the conversion program to do so.

See Setting Processing Options for the Inbound Flat File Conversion Program (R47002C).

3.1.3 Running the Inbound Flat File Conversion Program (R47002C)

Use one of these navigations:

Select Condition-Based Maintenance Interoperability (G13CBM311), Inbound Condition-Based Alerts Flat File Conversion.

Select Forecast Interoperability (G36301), Inbound Flat File Conversions.

Select Inventory Interoperability (G41313), Inbound Flat File Conversion.

Select Meter Reading Interoperability (G1332), Inbound Meter Readings File Conversion.

Select Product Data Interoperability (G30311), Inbound Flat File Conversion.

Select Purchasing Interoperability (G43A313), Inbound Flat File Conversion.

Select Electronic Commerce Interoperability (G47311), Inbound Flat File Conversion.

Select Shop Floor Management Interoperability (G31311), Inbound XX Flat File Conversion, where XX is the process that the conversion completes, such as Inbound Completion Flat File Conversion.

3.1.4 Setting Processing Options for the Inbound Flat File Conversion Program (R47002C)

Processing options enable you to specify the default processing for programs and reports. Transaction

1. Enter the transaction to process.

Specify the type of transaction (00/TT) to be processed.

This value identifies the interoperability transaction type used to convert the flat file. Separators

1. Enter the field delimiter.

Specify the separator used to delimit fields.

The field delimiter is used by the system to identify field separation. For example, if you specify the field delimiter as a comma (,), order number and order type flat file entries would be:

"Order Number", "Order Type"

2. Enter the text qualifier.

Specify the text qualifier that surrounds text value objects. Process

1. Enter the inbound processor to run after successful completion of the conversion.

Specify the batch processor to run after the conversion completes successfully.

2. Enter the version for the inbound processor.

Indicate the version of inbound processor to use during inbound conversion. If you leave this processing option blank, the system uses XJDE0001.

3.2 Processing Outbound Interoperability Transactions

This section provides an overview of outbound interoperability and lists a prerequisite.

3.2.1 Understanding Outbound Interoperability

You might need to send transactions that you create or change in the JD Edwards EnterpriseOne system to an external system. For example, you might need to send information about changes on a journal entry or a purchase order to an external system.

To enable outbound processing, you specify a transaction type in the processing options of the appropriate originating program or interoperability processing options program. Additionally, some entry programs enable you to specify a version of the Master Business Function Processing Options program that, in turn, enables you to specify a version of the Interoperability Processing Options program. You can differentiate outbound transactions by transaction type by creating multiple versions of the interoperability processing option programs. For example, you might want to differentiate vouchers that are generated by Procurement from vouchers that are generated manually.

Using the master business function for the type of transaction, the system creates a copy of the transaction and places it in the interface table where external systems can access it.

If a program modifies a transaction without going through the master business function, the system still sends a copy of the transaction to the interface table where external systems can access it.

The default outbound transaction is a copy of a transaction after you create or change it (an after image). With interoperability, you can also send a copy of each transaction as it was before you changed it (a before image). To control the type of image, you set a processing option on the appropriate interoperability processing options program.


Creating and sending before images requires additional processing time.

The system places a copy of each transaction in the interface table (Z table) that corresponds to the type of transaction that you specify in the processing option. The system also adds a record to the Subsystem Job Master table (F986113).

To retrieve the data from the interface tables:

  1. Create a custom UBE (universal batch engine) or function to process the data from the interface tables in such a way that it can be used by the external system.

  2. Use the Data Export Controls program (P0047) to specify the custom UBE or function for the transaction type you specified in the interoperability processing options.

    The system stores this information in the Data Export Control table (F0047).

  3. Run the Interoperability Generic Outbound Subsystem UBE program (R00460).

    The Interoperability Generic Outbound Subsystem UBE program fetches the F986113 record and retrieves the name and version of the custom UBE or function from the F0047 table. The Interoperability Generic Outbound Subsystem UBE program passes information about the transaction to the custom UBE or function. The custom UBE or function then retrieves the records from the interface tables and processes that information.

3.2.2 Prerequisite

Define the data export controls for the type of outbound transaction.

The system uses data export controls to identify the batch programs or business processes that third parties provide for use in processing transactions.

See Setting Up Data Export Controls.

3.3 Reviewing the Processing Log

This section provides an overview of the processing log and lists the form used to review the processing log.

3.3.1 Understanding the Processing Log

You use the processing log to review whether the system has processed specific outbound transactions successfully. The system creates a record in the processing log for every outbound transaction that is processed. The processing log contains key fields from the F0047 table, such as transaction type, sequence number, batch process or function, and corresponding version.

The information in the processing log is for review only and cannot be changed in the processing log.

3.3.2 Form Used to Review the Processing Log

Form Name FormID Navigation Usage
Work With Processing Log W0046A You can access the Work With Processing Log form through multiple navigation paths. This list presents the most frequently used paths:

Inventory Interoperability (G41313), Processing Log

Financials Interoperability Processing (G00313), Processing Log

Forecast Interoperability (G36301), Processing Log

Product Data Interoperability (G30311), Processing Log

Purchasing Interoperability (G43A313), Processing Log

Sales Interoperability (G42A313), Processing Log

Shop Floor Management Interoperability (G31311), Processing Log

Review the processing log.