2 Setting Up Interoperability Transactions

This chapter contains the following topics:

• Section 2.1, "Understanding Interoperability Transaction Setup"

• Section 2.2, "Setting Up for Interoperability"

2.1 Understanding Interoperability Transaction Setup

External systems can use a variety of methods to send data to the interoperability interface tables. One method is to write the data to a flat file. If you use this method, the system converts the flat file to the interface table. For the system to convert data from the flat file to the interface table, you must identify the transaction using this information:

• Transaction type, which is a unique description that identifies the transaction.

• A direction indicator (inbound or outbound).

• Record types, which indicate the sort of information that is exchanged between JD Edwards EnterpriseOne and external systems.

• Tables, which are the sources or destinations of the transaction.

You can set a processing option to start the transaction process automatically when the conversion completes successfully. The transaction process copies the data from the interface tables to the application tables. JD Edwards EnterpriseOne applications can access the data from these tables.

2.1.1 Record Types Review

When you set up flat file cross-reference information, you must specify the record types. Record types indicate the sort of information that is exchanged between the JD Edwards EnterpriseOne system and external systems, such as addresses, header or detail transactions, text, or additional information.

You can review hard-coded record types in user-defined code (UDC) 00/RD. The system uses these codes to identify the forms from which the system stores information for outbound documents and to which the system stores information for inbound documents.

2.1.2 Transaction Type Setup

To identify the transactions that the system uses in the flat file cross-reference, you can add codes or transaction types to UDC 00/TT. You use the transaction types to identify whether the information exchange is inbound or outbound, and to identify the corresponding applications and versions. You must set up transaction types before you define data export controls and flat file cross-reference information.

2.1.3 Data Export Control Setup

You define the export information for outbound transactions only. To set up data export controls properly, you must indicate the transaction, document type, batch application or function, and version from which the external system retrieves information from the interface tables.

You can define export controls based on either of these two options:

Based On	Description
Function Name and Library	Specify a vendor-specific function name and library to identify the external custom program that accesses the JD Edwards EnterpriseOne interface tables.
UBE (universal batch engine) or batch processor	Specify a vendor-specific outbound batch processor that accesses the JD Edwards EnterpriseOne interface tables.

2.1.4 Flat File Cross-Reference Setup

Before you can convert a flat file, you must provide a cross-reference from the flat file fields to the interface table fields. When you exchange data between this system and an external system, you use flat file cross-reference information for these conditions:

• Inbound transactions for which the external system cannot write data to the interface tables in the required format for this system.

  In this case, the external system can write the data to a specific flat file for each transaction and record type.

• Outbound transactions for which this system cannot write data to the interface tables in the format that is required by the external system.

  In this case, this system can write the data to a specific flat file for each transaction and record type.

The process for setting up flat file cross-references for interoperability is identical to that for EDI (electronic data interchange) interface tables.

See "Processing EDI Documents" in the JD Edwards EnterpriseOne Applications Data Interface for Electronic Data Interchange Implementation Guide.

2.2 Setting Up for Interoperability

This section lists prerequisites and discusses how to:

• Set up data export controls.

• Set up the flat file cross-reference.

2.2.1 Prerequisites

Before you complete the tasks in this section:

• Ensure that the flat file is a comma-delimited ASCII text (flat) file to which the workstation has read and write access.

• Ensure that the data conforms to the required format.

  See "Processing EDI Documents" in theJD Edwards EnterpriseOne Applications Data Interface for Electronic Data Interchange Implementation Guide.

• On the appropriate drives on the computer or network, set up the folders for the flat files.

2.2.2 Forms Used to Set Up JD Edwards EnterpriseOne for Interoperability Transactions

Form Name	FormID	Navigation	Usage
User Defined Codes	W0004AA	You can access the Transaction Type form through multiple navigation paths. This list presents the most frequently used paths: Condition-Based Alerts Interoperability (G13CBM311), Transaction Type Inventory Interoperability (G41313), Transaction Type Financials Interoperability Processing (G00313), Transaction Type Forecast Interoperability (G36301), Transaction Type Meter Reading Interoperability (G1332), Transaction Type Product Data Interoperability (G30311), Transaction Type Purchasing Interoperability (G43A313), Transaction Type	Set up transaction types. For every outbound transaction type, you must set up data export controls. You use the transaction type when you set up flat file cross-reference information.
Data Export Control Revisions	W0047C	You can access the Data Export Controls form through multiple navigation paths. This list presents the most frequently used paths: Inventory Interoperability (G41313), Data Export Controls Financials Interoperability Processing (G00313), Data Export Controls Forecast Interoperability (G36301), Data Export controls Product Data Interoperability (G30311), Data Export Controls Purchasing Interoperability (G43A313), Data Export Controls Sales Interoperability (G42A313), Data Export Controls Shop Floor Management Interoperability (G31311), Data Export Controls	Set up data export controls.
Flat File Cross-Reference	W47002B	You can access the Flat File Cross-Reference form through multiple navigation paths. This list presents the most frequently used paths: Condition-Based Maintenance Interoperability (G13CBM311), Flat File Cross-Reference Inventory Interoperability (G41313), Flat File Cross-Reference Financials Interoperability Processing (G00313), Flat File Cross Reference Forecast Interoperability (G36301), Flat File Cross-Reference Meter Reading Interoperability (G1332), Flat File Cross Reference Product Data Interoperability (G30311), Flat File Cross-Reference	On Work With Flat File Cross-Reference, click Add to set up the flat file cross-reference.

2.2.3 Setting Up Data Export Controls

Access the Data Export Control Revisions form.

Figure 2-1 Data Export Control Revisions form

Description of "Figure 2-1 Data Export Control Revisions form"

Transaction

Specify a code to identify a specific type of transaction. Values are stored in UDC 00/TT.

Order Type

Enter a code to identify the type of document that you are exporting.

UBE Name

Specify a vendor-specific outbound batch processor that accesses the JD Edwards EnterpriseOne interface tables.

Version

Specify the version of the outbound batch processor.

Function Name

Specify a vendor-specific function name to identify the external custom program that accesses the JD Edwards EnterpriseOne interface tables.

Function Library

Specify the library for the function.

Execute For Add

Enter 1 to process an added transaction record or enter 0 if the transaction should not be processed as an added transaction record.

Execute For Upd (execute for update)

Enter 1 to process an updated transaction record or enter 0 if the transaction should not be processed as an update.

Execute For Del (execute for delete)

Enter 1 to process a deleted transaction record or enter 0 if the transaction should not be processed as a deleted transaction record.

Execute For Inq (execute for inquiry)

Enter 1 to process an inquiry of a transaction record or enter 0 if the transaction should not be processed as an inquiry.

Flat File Exp Mode (flat file export mode)

Enter 1 to export the transaction record to a flat file or enter 0 if you do not want to export the transaction record to a flat file.

Ext DB Exp Mode (external database export mode)

Enter 1 to export the transaction record to an external database or enter 0 if you do not want to export the transaction record to an external database.

Ext API Expo Mode (external API export mode)

Enter 1 to export the transaction record to an external API or enter 0 if you do not want to export the transaction record to an external API.

Launch Immediately

Enter 1 if you want to execute the batch job immediately.

Note: You should complete either the UBE Name and Version fields or the Function Name and Function Library fields.

2.2.4 Setting Up the Flat File Cross-Reference

Access the Flat File Cross-Reference form.

Figure 2-2 Flat File Cross-Reference form

Description of "Figure 2-2 Flat File Cross-Reference form"

Transaction

Specify a code to identify a specific type of transaction. Values are stored in UDC 00/TT.

Direction Indicator

Enter 1 for an inbound transaction or 2 for an outbound transaction.

Flat File Name

Enter the name of the flat file, including the directory path where the flat file exists.

Record Type

Specify an identifier used to mark EDI transaction records as header and detail information. This is an EDI function only. Values are stored in UDC 00/RD.

File Name

Enter the number of a specific table to identify the source or destination of the information. For example, the Account Master table name is F0901.