This chapter contains the following topics:
To fully cover the information requirements of an enterprise, companies sometimes use products from different software and hardware providers. Interoperability among different products is important to successfully implementing the enterprise solution. Full interoperability among different systems results in a flow of data that is seamless to the user. The interoperability function provides an interface that facilitates exchanging transactions, both inbound and outbound, with external systems.
External systems send information to the interface tables using either an external program or flat files and the Inbound Flat File Conversion program. The party sending the information is responsible for conforming to format and other requirements for the interface tables.
You run a transaction process (a batch program) that validates the data, updates valid data to the JD Edwards EnterpriseOne application tables, and sends action messages about incorrect data to the Work Center.
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.
Interoperability for outbound transactions requires that you set a processing option specifying a transaction type. 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. This is useful if you need to create a personal version of the Interoperability Processing Options program to designate different transaction types.
JD Edwards EnterpriseOne Application Fundamentals Interoperability from Oracle provides these business processes:
Running the conversion program for inbound transactions.
Reviewing and revising inbound interoperability transactions.
Sending outbound transactions.
Reviewing outbound transactions in the processing log.
Purging interoperability transactions.
We discuss these business processes in the business process chapters in this Implementation Guide.
You use interoperability to integrate the JD Edwards EnterpriseOne system with external systems. You do not use interoperability to integrate JD Edwards EnterpriseOne systems with other JD Edwards EnterpriseOne systems.
This section provides an overview of the steps that are required to implement JD Edwards EnterpriseOne Interoperability.
In the planning phase of the implementation, take advantage of all JD Edwards EnterpriseOne sources of information, including the installation guides and troubleshooting information.
Implementing interoperability for a particular system must be preceded by setting up the corresponding JD Edwards EnterpriseOne system:
JD Edwards EnterpriseOne Accounts Payable
JD Edwards EnterpriseOne Accounts Receivable
JD Edwards EnterpriseOne Capital Asset Management
JD Edwards EnterpriseOne Condition-Based Maintenance (CBM)
JD Edwards EnterpriseOne Fixed Assets
JD Edwards EnterpriseOne Forecast Management
JD Edwards EnterpriseOne General Accounting
JD Edwards EnterpriseOne Inventory Management
JD Edwards EnterpriseOne Procurement
JD Edwards EnterpriseOne Product Data Management
JD Edwards EnterpriseOne Quality Management
JD Edwards EnterpriseOne Sales Order Management
JD Edwards EnterpriseOne Service Management
JD Edwards EnterpriseOne Shop Floor Management
The Getting Started chapter in the implementation guide for each of these systems contains specific implementation information for that system.
Following is the implementation step for Interoperability:
Set up transaction types, data export controls, the flat-file cross-reference, and processing options.