## JD Edwards EnterpriseOne Application Fundamentals Interoperability Preface

This preface discusses:

- JD Edwards EnterpriseOne products.

- JD Edwards EnterpriseOne application fundamentals.

- Common fields used in this implementation guide.

### JD Edwards EnterpriseOne Products

This implementation guide refers to these JD Edwards EnterpriseOne products from Oracle:

- 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

### JD Edwards EnterpriseOne Application Fundamentals

Additional, essential information describing the setup and design of the system appears in companion volumes of documentation called JD Edwards EnterpriseOne Financial Management Application Fundamentals 9.0 Implementation Guide, JD Edwards EnterpriseOne Human Capital Management Application Fundamentals 9.0 Implementation Guide, and JD Edwards EnterpriseOne Customer Relationship Management Application Fundamentals 9.0 Implementation Guide.

Customers must conform to the supported platforms for the release as detailed in the JD Edwards EnterpriseOne minimum technical requirements. In addition, JD Edwards EnterpriseOne may integrate, interface, or work in conjunction with other Oracle products. Refer to the cross-reference material in the Program Documentation at http://oracle.com/contracts/index.html for Program prerequisites and version cross-reference documents to assure compatibility of various Oracle products.

See Also

JD Edwards EnterpriseOne Financial Management Application Fundamentals 9.0 Implementation Guide

JD Edwards EnterpriseOne Human Capital Management Application Fundamentals 9.0 Implementation Guide

JD Edwards EnterpriseOne Customer Relationship Management Application Fundamentals 9.0 Implementation Guide

### About This Documentation

A companion Guide called About This Documentation contains general information, including:

- Related documentation, common page elements, and typographical conventions for guides.

- Information about using guides and managing the documentation library.

- Information on the International Organization for Standardization (ISO) country and currency codes used within documentation.

- A glossary of useful JD Edwards EnterpriseOne terms that are used in documentation.

See Also

About This Documentation Preface

Using Implementation Guides

Managing the Online Library and Implementation Guides

ISO Country and Currency Codes

Glossary of JD Edwards EnterpriseOne Terms

### Common Fields Used in This Implementation Guide

Batch Number | Enter the number that the transmitter assigns to the batch. During batch processing, the system assigns a new batch number to the transactions for each control batch number it finds.
Execute For Add and Execute For Del (execute for deletion) | Enter a code that determines whether the batch application is used to process an added or a deleted transaction record. Values are: 1: Use batch application. 0: Do not use batch application.
Execute For Inq (execute for inquiry) | Enter a code that determines whether the batch application is used to process an inquiry of a transaction record. Values are: 1: Use batch application. 0: Do not use batch application.
Execute For Upd (execute for update) | Enter a code that determines whether the batch application is used to process an updated transaction record. Values are: 1: Use batch application. 0: Do not use batch application.
Ext API Exp Mode (export API in external mode) | Enter a code that determines whether the system exports the transaction record to an external API. Values are: 1: Export 0: Do not export
Ext DB Exp Mode (export DB in external mode) | Enter a code that determines whether the transaction record should be exported to an external database. Values are: 1: Export 0: Do not export
Flat File Exp Mode (flat file export mode) | Enter a code that determines whether the transaction record should be exported to a flat file. Values are: 1: Export 0: Do not export
Function Library | Enter the library for the function. This includes the path for the directory where the library exists.
Function Name | Enter the name of the function. You can define data export control for either a vendor-specific batch process or function. If you enter information in fields for vendor-specific batch processors or functions, the system uses the batch process.
Launch Immediately | Enter a value that controls the immediate execution of a batch job. If the field is set to a 1, the job executes immediately.
Order Type | Enter a code (00/DT) that identifies the type of document. This code also indicates the origin of the transaction. We have reserved document type codes for vouchers, invoices, receipts, and time sheets, which create automatic offset entries during the post program. (These entries are not self-balancing when you originally enter them.) We have defined these document types that should not be changed: P: Accounts Payable R: Accounts Receivable T: Payroll I: Inventory O: Purchase Order Processing J: General Accounting and Joint Interest Billing S: Sales Order Processing
Transaction | Enter the transaction type. This can be a code from user-defined code (UDC) 00/DT or a transaction type, such as, JDEVOUCH for voucher transactions.
Transaction Number | Enter the number that an Electronic Data Interchange (EDI) transmitter assigns to a transaction. In a non-EDI environment, you can assign any number that is meaningful to you to identify a transaction within a batch. It can be the same as a JD Edwards EnterpriseOne document number.
UBE Name (universal batch engine name) | Enter the name that identifies a system object. JD Edwards EnterpriseOne architecture is object-based. Discrete software objects are the building blocks for all applications, and developers can reuse the objects in multiple applications. The Object Librarian tracks each object. Examples of system objects include: Batch Applications (such as reports) Interactive Applications Business Views Business Functions Business Functions Data Structures Event Rules Media Object Data Structures You can define data export control for either a vendor-specific batch process or function. If you enter information in fields for vendor-specific batch processors or functions, the system uses the batch process.
User ID (user identification) | Enter the source of the transaction. This can be an ID, a workstation, the address of an external system, a node on a network, and so on. This field helps identify both the transaction and its point of origin.
Version | Enter a set of specifications that control how applications and reports run. You use versions to group and save a set of processing option values and data selection and sequencing options. Interactive versions are associated with applications (usually as a menu selection). Batch versions are associated with batch jobs or reports. To run a batch process, you must select a version.