JD Edwards EnterpriseOne Data Interface for Electronic Data Interchange 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 guides refers to these JD Edwards EnterpriseOne products from Oracle:

JD Edwards EnterpriseOne Accounts Payable
JD Edwards EnterpriseOne Accounts Receivable
JD Edwards EnterpriseOne Demand Scheduling Execution
JD Edwards EnterpriseOne Inventory Management
JD Edwards EnterpriseOne Procurement and Subcontract Management
JD Edwards EnterpriseOne Sales Order Management

Note. This implementation guide documents only form elements that require additional explanation. If a form element is not documented with the process or task in which it is used, then it either requires no additional explanation or is documented with the common fields for the section, chapter, or implementation guide.

JD Edwards EnterpriseOne Application Fundamentals

The JD Edwards EnterpriseOne Data Interface for Electronic Data Interchange 9.0 Implementation Guide provides you with implementation and processing information for the JD Edwards EnterpriseOne EDI solution. However, additional, essential information describing the setup and design of the system resides in companion documentation. The companion documentation consists of important topics that apply to many or all JD Edwards EnterpriseOne products lines. The companion volume for Data Interface for Electronic Data Interchange is:

JD Edwards EnterpriseOne Financial 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.

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.

Common Fields Used in This Implementation Guide

Send Method	Enter a code that indicates how documents are sent to a customer or supplier. It is part of the Accounts Payable Batch Upload process, and can be used as a criterion when you write reports.
Transaction Set	Enter the qualifier used to identify a specific type of EDI transaction.
Transaction Set Purpose	Enter a User-defined code (47/PU) that identifies the purpose of the transaction set. The first character of the second description in that table controls how the transaction is processed. Refer to ANSI X.12 Data Item 353.
Record Type	Enter the identifier used to mark EDI transaction records as header and detail information. This is an EDI function only.
Hierarchical Configuration	Enter an EDI 856 transaction set hierarchy configuration code that specifies the levels present in the Ship Notice/Manifest. This field consists of a combination of two character Hierarchical Level Codes (values from the X12 specification for data element 735 - Hierarchical Level Code). You can enter up to nine combinations of HLCs in this field.
Hierarchical Structure Code	Enter a code that indicates the hierarchical application structure of an EDI transaction set that utilizes the HL segment to define the structure of the transaction set.
SCC Number (shipment container code number)	Enter the Shipping Container Code, which must conform to the UCC structure for SCC numbers.
UPC Number (universal product code number)	Enter the Universal Product Code number, which must conform to the UCC structure for UPC numbers.