EDI Gateway

Oracler EDI Gateway
Users Guide
Release 11
March 1998
Enabling the Information Aget
OracleR EDI Gateway Users Guide

Release 11
The part number for this volume is A5827101.
Copyright E 1998, Oracle Corporation. All Rights Reserved.
Major Contributors: Kurt Thompson, Bonnie Williams, Janet Lee
Contributors: Garret Minakawa, David Wrightson, Winston Lang
The programs (which include both the software and documentation) contain
proprietary information of Oracle Corporation; they are provided under a license
agreement containing restrictions on use and disclosure and are also protected by
copyright, patent and other intellectual property law. Reverse engineering of the
Programs is prohibited.
The information contained in this document is subject to change without notice. If you
find any problems in the documentation, please report them to us in writing. Oracle
Corporation does not warrant that this document is errorfree. No part of this document
may be reproduced or transmitted in any form or by any means, electronic or mechanical,
for any purpose, without the express written permission of Oracle Corporation.
Restricted Rights Legend
Programs delivered subject to the DOD FAR Supplement are commercial computer
software and use, duplication and disclosure of the Programs shall be subject to the
licensing restrictions set forth in the applicable Oracle license agreement. Otherwise,
Programs delivered subject to the Federal Acquisition Regulations are restricted
computer software and use, duplication and disclosure of the Programs shall be subject to
the restrictions in FAR 52.22714, Rights in Data General, including Alternate III (June
1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or
other inherently dangerous applications. It shall be licensees responsibility to take all
appropriate failsafe, backup, redundancy and other measures to ensure the safe use of
such applications if the Programs are used for such purposes, and Oracle disclaims
liability for any damages caused by such use of the Programs.
Oracle is a registered trademark and Oracle8, Oracle Application Object Library, Oracle
Alert, Oracle Financials, Oracle Quality, Oracle Workflow, Oracle Work in Process,
SQL*Forms, SQL*Plus, SQL*AMX, SQL*Report, and SQL*ReportWriter are trademarks or
registered trademarks of Oracle Corporation.
All other company or product names are mentioned for identification purposes only, and
may be trademarks of their respective owners.
Contents
Preface
vii
Chapter 1
Overview of Oracle EDI Gateway . . . . . . . . . . . . . . . . . . . . . . . . 1 1

Overview of Oracle EDI Gateway . . . . . . . . . . . . . . . . . . . . . . . . . 1 2
How To Use Oracle EDI Gateway . . . . . . . . . . . . . . . . . . . . . . 1 9
Chapter 2
Trading Partner Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1

Overview of Trading Partners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2
Defining Trading Partner Data . . . . . . . . . . . . . . . . . . . . . . . . 2 9
Chapter 3
Code Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of Code Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Code Conversion Categories . . . . . . . . . . . . . . . . . .
Assigning Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Predefined Code Categories . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Code Conversion Values . . . . . . . . . . . . . . . . . . . . .
31
32
3 13
3 14
3 15
3 18
Chapter 4
Data File Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview of Data File Structure . . . . . . . . . . . . . . . . . . . . . . . . . . .
Control Record Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Required Inbound Control Record . . . . . . . . . . . . . . . . . . . . .
Record Key (1100) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4
4
4
4
4
1
2
4
10
11
Contents
iii
Record Layout Codes Summary . . . . . . . . . . . . . . . . . . . . . . . 4 16

Reusable Record Layout Details . . . . . . . . . . . . . . . . . . . . . . . 4 19
Mapping Rules for EDI Translators . . . . . . . . . . . . . . . . . . . . 4 25
Chapter 5
Data File Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1

Changing the Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2
Chapter 6
Importing and Extracting EDI Documents . . . . . . . . . . . . . . . . .

Defining Data File Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Oracle EDI Gateway Profile Options . . . . . . . . . . . . . . . . . . . . . . .
Running the Import Program for Inbound Transactions . . . . . .
Running the Extract Programs for Outbound Transactions . . . .
Viewing the Status of Concurrent Programs . . . . . . . . . . . . . . . .
Data File Definition Format Legend . . . . . . . . . . . . . . . . . . . . . . .
Chapter 7
Inbound Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1
Inbound Invoice (810 / INVOIC) . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2
Running the EDI Invoice Inbound Program . . . . . . . . . . . . . 7 3
Inbound Price / Sales Catalog (832 / PRICAT) . . . . . . . . . . . . . . 7 6
Running the EDI Price / Sales Catalog Inbound Program . 7 7
Inbound Response to Request for Quote (843 / QUOTES) . . . . 7 10
Running the EDI Response to Request for
Quote Inbound Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 11
Inbound Price / Sales Catalog and Response to Request for
Quote Data File Organization . . . . . . . . . . . . . . . . . . . . . . . . . 7 14
Inbound Purchase Order (850 / ORDERS) . . . . . . . . . . . . . . . . . . 7 19
Running the EDI Purchase Order Inbound Program . . . . . . 7 20
Inbound Purchase Order Data File Organization . . . . . . . . . 7 22
Inbound Ship Notice / Manifest (856 / DESADV) . . . . . . . . . . . 7 27
Running the EDI Ship Notice / Manifest Inbound Program 7 28
Inbound Shipping and Billing Notice (857) . . . . . . . . . . . . . . . . . . 7 30
Running the EDI Shipping and Billing Notice Inbound
Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 31
Inbound Ship Notice / Manifest and Shipping and
Billing Notice Data File Organization . . . . . . . . . . . . . . . . . . . 7 33
Chapter 8
Outbound Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1
Outbound Application Advice (824 / APERAK) . . . . . . . . . . . . 8 2
iv Oracle EDI Gateway Users Guide
61
62
63
64
66
68
69
Running the EDI Application Advice Outbound

Extract Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outbound Application Advice Data File Organization . . . .
Outbound Invoice (810 / INVOIC) . . . . . . . . . . . . . . . . . . . . . . . .
Running the EDI Invoice Outbound Extract Program . . . . .
Outbound Invoice Data File Organization . . . . . . . . . . . . . . .
Outbound Payment Order / Remittance Advice
(820 / PAYORD, REMADV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Running the EDI Payment Order / Remittance Advice
Outbound Extract Program . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outbound Payment Order / Remittance Advice Data
File Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outbound Planning Schedule (830 / DELFOR) . . . . . . . . . . . . . .
Outbound Planning Schedule Data File Organization . . . . .
Outbound Shipping Schedule (862 / DELJIT) . . . . . . . . . . . . . . .
Outbound Shipping Schedule Data File Organization . . . . .
Running the EDI Outbound Planning and Shipping
Schedule Extract Program . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outbound Planning Schedule and Shipping Schedule
Summary Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outbound Purchase Order (850 / ORDERS) . . . . . . . . . . . . . . . .
Running the EDI Purchase Order Outbound Extract
Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outbound Purchase Order Data File Organization . . . . . . .
Outbound Purchase Order Change Request (860 / ORDCHG)
Running the EDI Outbound Purchase Order Change
Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outbound Purchase Order Change Request Data File
Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outbound Ship Notice / Manifest (856 / DESADV) . . . . . . . . .
Running the EDI Ship Notice / Manifest Outbound
Extract Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outbound Ship Notice / Manifest Data File Organization .
Chapter 9
Extensible EDI Gateway Architecture . . . . . . . . . . . . . . . . . . . . .

Extensible EDI Gateway Architecture . . . . . . . . . . . . . . . . . . . . . .
Technical Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Extensible Architecture Example . . . . . . . . . . . . . . . . . . . . . .
Provide Additional Values . . . . . . . . . . . . . . . . . . . . . . . . . . . .
83
85
89
8 10
8 12
8 20
8 22
8 23
8 27
8 30
8 47
8 50
8 51
8 53
8 58
8 59
8 61
8 67
8 69
8 71
8 77
8 79
8 81
91
92
94
95
9 10
Contents
Appendix A
Windows and Navigator Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . A 1

EDI Gateway Windows and Navigator Paths . . . . . . . . . . . . . . . A 2
Glossary
Index
vi Oracle EDI Gateway Users Guide
Preface
Welcome to the OracleR EDI Gateway Users Guide, Release 11.
This users guide includes the information you need to work with
Oracle EDI Gateway effectively. It contains detailed information about
the following:
Overview and reference information
Specific tasks you can accomplish using Oracle EDI Gateway
Oracle EDI Gateway setup
Oracle EDI Gateway functions and features
Oracle EDI Gateway windows
Oracle EDI Gateway reports and processes
This preface explains how this users guide is organized and introduces
other sources of information that can help you.
Preface
vii
About this Users Guide

This guide contains overviews as well as task and reference
information about Oracle EDI Gateway. This guide includes the
following chapters:
Chapter 1 presents an overview of how the EDI Gateway works,
including how inbound and outbound transactions are processed
in relation to Oracle Applications.
Chapter 2 describes how to set up trading partners for sending
and / or receiving EDI transactions.
Chapter 3 describes how to understand and set up code
conversion so that trading partners on either side of the
transaction can use codes familiar to them.
Chapter 4 provides a detailed overview of how data files are
structured.
Chapter 5 describes how to customize your data files to meet
your business needs.
Chapter 6 tells you how to import inbound EDI transactions and
export outbound EDI transactions.
Chapter 7 provides an overview of each inbound transaction,
including important details about the data file.
Chapter 8 provides an overview of each outbound transaction,
including important details about the data file.
Chapter 9 describes important details on how to customize your
outbound transactions using the EDI Gateways extensible
architecture.
viii
Oracle EDI Gateway Users Guide
Audience for This Guide

This guide assumes you have a working knowledge of your business
areas processes and tools. It also assumes you are familiar with EDI
Gateway. If you have never used EDI Gateway, we suggest you attend
one or more of the EDI Gateway training classes available through
World Wide Education. For more information about EDI Gateway and
Oracle training, see: Other Information Sources.
Do Not Use Database Tools to Modify Oracle Applications Data

Because Oracle Applications tables are interrelated, any change you
make using Oracle Applications can update many tables at once. But
when you modify Oracle Applications data using anything other than
Oracle Applications, you may change a row in one table without
making corresponding changes in related tables. If your tables get out
of synchronization with each other, you risk retrieving erroneous
information and you risk unpredictable results throughout Oracle
Applications.
When you use Oracle Applications to modify your data, Oracle
Applications automatically checks that your changes are valid. Oracle
Applications also keeps track of who changes information. If you enter
information into database tables using database tools, you may store
invalid information. You also lose the ability to track who has changed
your information because SQL*Plus and other database tools do not
keep a record of changes.
Consequently, we STRONGLY RECOMMEND that you never use
SQL*Plus or any other tool to modify Oracle Applications data unless
otherwise instructed.
Other Information Sources

Here are some other ways you can increase your knowledge and
understanding of EDI Gateway.
Online Documentation
All Oracle Applications documentation is available online on
CDROM, except for technical reference manuals. There are two online
Preface
ix
formats, HyperText Markup Language (HTML) and Adobe Acrobat

(PDF).
All users guides are available in HTML, Acrobat, and paper. Technical
reference manuals are available in paper only. Other documentation is
available in Acrobat and paper.
The content of the documentation does not differ from format to format.
There may be slight differences due to publication standards, but such
differences do not affect content. For example, page numbers and
screen shots are not included in HTML.
The HTML documentation is available from all Oracle Applications
windows. Each window is programmed to start your web browser and
open a specific, contextsensitive section. Once any section of the
HTML documentation is open, you can navigate freely throughout all
Oracle Applications documentation. The HTML documentation also
ships with Oracle Information Navigator (if your national language
supports this tool), which enables you to search for words and phrases
throughout the documentation set.
Related Users Guides

EDI Gateway shares business and setup information with other Oracle
Applications products. Therefore, you may want to refer to other
users guides when you set up and use EDI Gateway.
If you do not have the hardcopy versions of these manuals, you can
read them online using the Applications Library icon or Help menu
command.
Oracle Applications Users Guide
This guide explains how to enter data, query, run reports, and navigate
using the graphical user interface (GUI) available with this release of
EDI Gateway (and any other Oracle Applications products). This
guide also includes information on setting user profiles, as well as
running and reviewing reports and concurrent processes.
You can access this users guide online by choosing Getting Started
with Oracle Applications from any Oracle Applications help file.
Oracle Applications Demonstration Users Guide
This guide documents the functional storyline and product flows for
Global Computers, a fictional manufacturer of personal computers
products and services. As well as including product overviews, the
book contains detailed discussions and examples across each of the

major product flows. Tables, illustrations, and charts summarize key
flows and data elements.
Oracle Automotive Users Guide
This guide describes how to add commodity code, customer item,
trading partner, and customer address information to information
already defined in various Oracle Applications. This guide also
describes how to import and export information into and out of Oracle
Automotive, as well as how to process the information once it has been
imported into Oracle Automotive.
Oracle Inventory Users Guide
This guide describes how to define items and item information,
perform receiving and inventory transactions, maintain cost control,
plan items, perform cycle counting and physical inventories, and set up
Oracle Inventory.
Oracle Master Scheduling/MRP and Supply Chain Planning Users
Guide
This guide describes how to anticipate and manage both supply and
demand for your items. Using a variety of tools and techniques, you
can create forecasts, load these forecasts into master production
schedules, and plan your enditems and their component
requirements. You can also execute the plan, releasing and
rescheduling planning suggestions for discrete jobs and repetitive
schedules.
Oracle Order Entry/Shipping Users Guide
This guide describes how to enter sales orders and returns, copy
existing sales orders, schedule orders, release orders, plan departures
and deliveries, confirm shipments, create price lists and discounts for
orders, and create reports.
Oracle Purchasing Users Guide
This guide describes how to create and approve purchasing
documents, including requisitions, different types of purchase orders,
quotations, RFQs, and receipts. This guide also describes how to
manage your supply base through agreements, sourcing rules and
approved supplier lists. In addition, this guide explains how you can
Preface
xi
automatically create purchasing documents based on business rules

through integration with Oracle Workflow technology, which
automates many of the key procurement processes.
Oracle Service Users Guide
This guide describes how you can track service requests, maintain and
repair customer products in your installed base, and bill your
customers for services rendered. This guide also gives an overview of
the workflows that Oracle Service provides.
Oracle Supplier Scheduling Users Guide
This guide describes how you can use Oracle Supplier Scheduling to
calculate and maintain planning and shipping schedules and
communicate them to your suppliers.
Reference Manuals
Oracle Automotive Implementation Manual
This manual describes the setup and implementation of the Oracle
Applications used for the Oracle Automotive solution.
Oracle Manufacturing, Distribution, Sales and Service Open
Interfaces Manual
This manual contains uptodate information about integrating with
other Oracle Manufacturing applications and with your other systems.
This documentation includes open interfaces found in Oracle
Manufacturing.
Oracle Applications Message Reference Manual
This manual describes all Oracle Applications messages. This manual
is available in HTML format on the documentation CDROM for
Release 11.
Oracle Project Manufacturing Implementation Manual
This manual describes the setup steps and implementation for Oracle
Project Manufacturing.
xii
Oracle SelfService Web Applications Implementation Manual

This manual describes the setup steps for Oracle SelfService Web
Applications and the Web Applications dictionary.
Installation and System Administration

Oracle Alert Users Guide
This guide explains how to define periodic and event alerts to monitor
the status of your Oracle Applications data.
Multiple Reporting Currencies in Oracle Applications
If you use the Multiple Reporting Currencies feature to record
transactions in more than one currency, use this manual before
implementing EDI Gateway. This manual details additional steps and
setup considerations for implementing EDI Gateway with this feature.
Multiple Organizations in Oracle Applications
If you use the Oracle Applications Multiple Organization Support
feature to use multiple sets of books for one EDI Gateway installation,
this guide describes all you need to know about setting up and using
EDI Gateway with this feature.
Oracle Applications Implementation Wizard Users Guide
If you are implementing more than one Oracle product, you can use the
Oracle Applications Implementation Wizard to coordinate your setup
activities. This guide describes how to use the wizard.
Oracle Applications Developers Guide
This guide contains the coding standards followed by the Oracle
Applications development staff. It describes the Oracle Application
Object Library components needed to implement the Oracle
Applications user interface described in the Oracle Applications User
Interface Standards. It also provides information to help you build your
custom Developer/2000 forms so that they integrate with Oracle
Applications.
Preface
xiii
Oracle Applications Flexfields Guide

This guide provides flexfields planning, setup and reference
information for the EDI Gateway implementation team, as well as for
users responsible for the ongoing maintenance of Oracle Applications
product data. This manual also provides information on creating
custom reports on flexfields data.
Oracle Applications Installation Manual for Windows Clients
This guide provides information you need to successfully install Oracle
Financials, Oracle Public Sector Financials, Oracle Manufacturing, or
Oracle Human Resources in your specific hardware and operating
system software environment.
Oracle Applications Product Update Notes
If you are upgrading your Oracle Applications, refer to the product
update notes appropriate to your update and product(s) to see
summaries of new features as well as changes to database objects,
profile options and seed data added for each new release.
Oracle Applications Upgrade Preparation Manual
This guide explains how to prepare your Oracle Applications products
for an upgrade. It also contains information on completing the
upgrade procedure for each product. Refer to this manual and the
Oracle Applications Installation Manual when you plan to upgrade your
products.
Oracle Applications System Administrators Guide
This manual provides planning and reference information for the EDI
Gateway System Administrator.
Other Sources
Training
We offer a complete set of formal training courses to help you and your
staff master EDI Gateway and reach full productivity quickly. We
organize these courses into functional learning paths, so you take only
those courses appropriate to your job or area of responsibility.
xiv
You have a choice of educational environments. You can attend

courses offered by Oracle Education Services at any one of our many
Education Centers, or you can arrange for our trainers to teach at your
facility. In addition, Oracle training professionals can tailor standard
courses or develop custom courses to meet your needs. For example,
you may want to use your organization structure, terminology, and
data as examples in a customized training session delivered at your
own facility.
Support
From onsite support to central support, our team of experienced
professionals provides the help and information you need to keep EDI
Gateway working for you. This team includes your Technical
Representative, Account Manager, and Oracles large staff of
consultants and support specialists with expertise in your business
area, managing an Oracle8 server, and your hardware and software
environment.
About Oracle
Oracle Corporation develops and markets an integrated line of
software products for database management, applications
development, decision support, and office automation, as well as
Oracle Applications, an integrated suite of more than 45 software
modules for financial management, supply chain management,
manufacturing, project systems, human resources and sales and service
management.
Oracle products are available for mainframes, minicomputers, personal
computers, network computers and personal digital assistants,
allowing organizations to integrate different computers, different
operating systems, different networks, and even different database
management systems, into a single, unified computing and information
resource.
Oracle is the worlds leading supplier of software for information
management, and the worlds second largest software company.
Oracle offers its database, tools, and applications products, along with
related consulting, education, and support services, in over 140
countries around the world.
Preface
xv
Thank You
Thank you for using EDI Gateway and this users guide.
We value your comments and feedback. At the end of this guide is a
Reader s Comment Form you can use to explain what you like or
dislike about EDI Gateway or this users guide. Mail your comments
to the following address or call us directly at (650) 5067000.
Oracle Applications Documentation Manager
Oracle Corporation
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Or, send electronic mail to [email protected] .
xvi
CHAPTER
Overview of Oracle EDI

Gateway
T his chapter presents an overview of the EDI Gateway:
Overview: page 1 2
How to Use Oracle EDI Gateway: page 1 9
Overview of Oracle EDI Gateway
11

Oracle Applications provides users with the ability to conduct business
electronically between trading partners based on the Electronic
Commerce standards and methodology. One form of Electronic
Commerce is Electronic Data Interchange (EDI).
EDI is an electronic exchange of information between trading partners.
Data files are exchanged in a standard format to minimize manual
effort, speed data processing, and ensure accuracy.
The EDI Gateway performs the following functions:
define trading partner groups and trading partner locations
enable transactions for trading partners
provide location code conversion between trading partner
location codes and codes used in Oracle Applications
provide general code conversion between trading partner codes
or standard codes
define interface data files so that application data can interface
with EDI translators
extract application data, format, and write to data files (outbound
transactions)
import data or converted codes into application open interface
tables so that application program interfaces (API) can validate
and update Oracle application tables (inbound transactions)
How Oracle EDI Gateway Works with Other Oracle Applications

Oracle Applications are designed with an open architecture for easy
integration with EDI translators and electronic transmission products to
provide a seamless solution. Oracle Applications utilize the Oracle EDI
Gateway to integrate with EDI translator software. EDI translation
software packages integrate with an electronic transmission service to
provide a closedloop between Oracle Applications and the trading
partners application.
The Oracle Applications for Manufacturing, Distribution, and Financials
are EDIenabled using the Oracle EDI Gateway product. The Oracle
EDI Gateway product augments the existing standard paper document
capabilities of Oracle Applications, or adds functionality where no
corresponding paper documents exist.
12
A common EDI implementation is via ASCII data files in a batch

environment. Data from the sending application is extracted into an
application data file. The application data file is received by the
translation software which translates it into the an EDI standard both
trading partners agree upon. Then the EDI data file is placed on a
network for transmission to the receiving application. The receiving
applications EDI translator receives the EDI data file from the network
and begins the file processing in reverse sequence. The translator
translates the EDI data file and creates an application data file
meaningful to the receiving application. The receiving application
receives the application data file for processing and imports the data
into the application.
The following figure illustrates the outbound EDI Gateway transaction
flow:
Figure 1 1
13
The following figure illustrates the inbound EDI Gateway transaction

flow:
Figure 1 2
Oracle EDI Gateway Product Architecture

With an open architecture, Oracle Applications allows you to choose the
best translation and electronic transmission service for your business
requirements. You can use a commercially available EDI translator and
transmission provider or use a proprietary solution. The Oracle
Applications and the Oracle EDI Gateway places no restriction on your
choices.
Product Components for All Transactions

The Oracle EDI product architecture consists of the following features
for both outbound and inbound EDI transactions.
Trading Partner Definition
Used for both inbound and outbound transactions to define trading
partner locations within a trading partner group. By defining a trading
partner, you do the following:
enable EDI translations
establish a link to the location or business entity defined in the
Oracle Applications
14
establish a link to the trading partner definition in the EDI

translator.
Code Conversion Definition
Used for both inbound and outbound transactions to convert general
codes between the sending and receiving systems. This can be used to
convert Oracle Applications codes to EDI standard codes or
userdefined codes.
Flexfields
Flexfields (attributes) are userdefined fields in the Oracle Applications.
They are found in both inbound and outbound transactions.
You have to modify the general EDI translator data maps or templates to
use flexfields.
Product Components for Outbound Transactions

The Oracle EDI Gateway product architecture consists of the following
components for outbound transactions:
Oracle Applications Concurrent Program Manager
Used for outbound transactions to initiate data extraction programs that
create interface data files that are passed to the EDI translator for
processing the data into the desired EDI standard.
Stored Procedures to Prevent Duplicate Extraction
Used with outbound transactions to provide encapsulated application
logic to record the EDI transaction in the Oracle application. For
example, the Oracle Purchasing tables are updated to reflect the
extraction of purchase order data. This prevents the same data from
being extracted again.
Transactionspecific Extension Tables
Used with outbound transactions to temporarily store usersupplied
data or data from a nonOracle Applications source that is required by
target EDI documents. See: Extensible EDI Gateway Architecture: page
9 2.
15
Transactionspecific Interface Tables

Used with outbound transactions to temporarily store data extracted
from the Oracle Applications, including converted codes and data
copied from customized extension tables.
Transactionspecific Database Views
Used with outbound transactions to provide encapsulated data selection
logic for the target EDI transaction. You enter selection criteria, using
Standard Request Submission, to launch individual extract programs.
Interface Tables Table
Used with outbound transactions to store the starting record identifier
of each section of the output file and to track which transactionspecific
interface and extension tables are related. The data extract program uses
this information to write the next sequential identifier at the beginning
of each record in the data file.
Interface Columns Table
Used with outbound transactions to store the assigned location of each
data element within the data file. The data extract program uses this
information to write data to the correct position in the data file.
Data Extract Programs
Used with outbound transactions to create a standard ASCII data file
format that can be mapped to any standard. The data file contains data
from Oracle Applications, converted codes from EDI Gateway tables,
and descriptive flexfields defined in both EDI Gateway and the Oracle
applications.
Extension Tables
The EDI Gateway extension tables are used to hold outbound data from
tables that are outside the Oracle application. These extension tables are
installed with EDI Gateway. However, you must define and populate
the table columns if you want to use these tables.
Each transaction interface table has one extension table per interface
table for the given transaction. The extension tables share the same base
interface table name as the transaction with an _X suffix. For
example, the primary interface table ECE_DSNO_ORDERS has the
extension table ECE_DSNO_ORDERS_X.
16
IndustrySpecific Tables
Some Oracle Applications have additional application tables for vertical
industry solutions. These additional tables are detected in the EDI
Gateway by reading system setup tables. If industryspecific tables are
detected, their data, along with customerdefined extension table data,
is copied to the EDI Gateway extension tables during the data extraction
for outbound transactions.
Note: EDI extension tables are not used with inbound
transactions.
Product Components for Inbound Transactions

The Oracle EDI Gateway product architecture consists of the following
components for inbound transactions:
Oracle Applications Concurrent Program Manager
Used for inbound transactions to initiate data load programs that import
interface data files from the EDI translator to EDI Gateway for
processing into Oracle Applications.
Data Load Programs
Used with inbound transactions to load the Oracle Applications open
interfaces from a standard ASCII data file. The data load program
converts external codes in the file to internal codes found in the code
conversion tables. The internal codes found in the code conversion
tables or found in the internal fields as populated by the EDI translator
are loaded into the application open interface tables.
Oracle Applications Open Interface
Used with inbound transactions. The application open interface consists
of temporary interface tables and an application open interface API. The
temporary interface tables are used to store the data loaded by the data
load programs. The API is used to validate the data in the temporary
interface tables and populate the Oracle Application tables. See:
Running the Import Program for Inbound Transactions: page 6 4.
Error detection, reporting, correction, and recovery are addressed by the
respective Oracle Applications.
17
EDI Standards Supported

The Oracle EDI Gateway product is designed to support any EDI
standard supported by EDI translation software; it is not tailored to any
specific EDI standard.
EDI Transaction Support

The following transactions are supported:
ASC X12
EDIFACT
Document ID Description
Inbound Transactions
810
INVOIC
INI
Inbound Invoice: page 7 2
832
PRICAT
CATI
Inbound Price / Sales Catalog: page 7 6
843
QUOTES
RRQI
Inbound Response to Request for Quote: page 7 10
850
ORDERS
POI
Inbound Purchase Order: page 7 19
856
DESADV
ASNI
Inbound Ship Notice / Manifest: page 7 27
857
No
equivalent
SBNI
Inbound Shipping and Billing Notice: page 7 30
Outbound Transactions
824
APERAK
ADVO
Outbound Application Advice: page 8 2
810
INVOIC
INO
Outbound Invoice: page 8 9
820
PAYORD /
REMADV
PYO
Outbound Payment Order / Remittance Advice: page 8 20
830
DELFOR
SPSO
Outbound Planning Schedule: page 8 27
862
DELJIT
SSSO
Outbound Shipping Schedule: page 8 47
850
ORDERS
POO
Outbound Purchase Order: page 8 58
860
ORDCHG
POCO
Outbound Purchase Order Change Request: page 8 67
856
DESADV
DNSO
Outbound Ship Notice / Manifest: page 8 77
Table 1 1 (Page 1 of 1)
18
See Also
Extensible EDI Gateway Architecture: page 9 1
Outbound Transactions: page 8 1
Inbound Transactions: page 7 1
How To Use Oracle EDI Gateway

To use the Oracle EDI Gateway, perform the following tasks:
Step 1. Define Data File Directories
To use EDI Gateway, you must first create directories where data files,
for both inbound and outbound transactions, are stored. You must then
specify these in the INIT.ORA file and in the EDI Gateway profile
options. See: Defining Data File Directories: page 6 2 and EDI
Gateway Profile Options: page 6 3.
Step 2. Define Trading Partner Data
First, define a trading partner group and associate all trading partner
location (address) entities to this group. Define basic information about
the trading partner and associate that to a specific trading partners
location. This is necessary to integrate Oracle Applications and EDI
translator software. See: Defining Trading Partner Data: page 2 9.
Step 3. Define Code Conversions
The Oracle EDI Gateway code conversion function provides a method
by which trading partner and standard codes can be converted to Oracle
Application codes and vice versa. See: Overview of Code Conversion:
page 3 2.
1.
Define code conversion categories to specify a subset of codes

within the code conversion table. See: Defining Code Conversion
Categories: page 3 13.
2.
For each data element in a transaction that requires code conversion

by EDI Gateway, assign one code conversion category. See:
Assigning Categories: page 3 14.
3.
Enter the actual code conversion values from the internal codes to
external codes into the code conversion table. The internal codes are
defined in the Oracle Applications. The external codes are the
19
associated values required by the trading partner or chosen EDI

standard.
Step 4. Customize Data File Formats
Oracle delivers a standard predefined data file format containing all the
data that may be required to support a particular EDI transaction. You
may customize this data file to meet specific business needs. See:
Changing the Data File: page 5 2.
Step 5. Initiate EDI Transactions
Once data file directories, trading partner information, code
conversions, and optional customizations of data files have been
performed, use Oracle Applications Standard Request Submission to
run extract programs for outbound transactions and import programs
for inbound transactions. See: Running the Extract Programs for
Outbound Transactions: page 6 6, Running the Import Programs for
Inbound Transactions: page 6 4, and Viewing the Status of Concurrent
Programs: page 6 8.
1 10
CHAPTER
Trading Partner Setup

T
his chapter tells you how to set up trading partners in Oracle EDI
Gateway:
Overview: page 2 1
Defining Trading Partner Data: page 2 9
21
Overview of Trading Partners

The term trading partner is used differently in the context of EDI
translators than in the context of the EDI Gateway.
For EDI translators, the purpose of trading partner data is to:
identify sending and receiving electronic mailbox addresses
identify the communication medium (such as network or direct
connection)
enable specific transactions by trading partner
For the Oracle EDI Gateway, the purpose of trading partner data is to:
crossreference a particular address location in Oracle
Applications to the location code defined for the trading partner
for that address
link the EDI translator trading partner identifier to the EDI
Gateway trading partner for the primary business address entity
in the transaction
enable specific transactions for the EDI Gateway trading partner
In the EDI Gateway, the trading partner is defined as any address in
Oracle Applications. This allows the conversion of location codes
between the senders defined code in their application to the receivers
defined code in their Oracle Application and vice versa. The translator
code definition in the EDI Gateway identifies the trading partner setup
code as defined in the EDI translator.
For example, assume the trading partner defined the address code as
AL012. However, the same physical address was defined as 1234 in
Oracle Applications. Defining the trading partner location in the
appropriate Oracle application ensures that the code AL012 is returned
in transactions.
When defining trading partner data in the EDI Gateway, transactions
must be enabled for the trading partner in order for data to be imported
or extracted and written to the data file.
The primary trading partner location is the location in the transaction
detail records that is reviewed in the EDI Gateway to determine the key
business entity that has ownership of this transaction in the Oracle
Application. This entity is at the address or site level in the transaction.
22
The higher level customer or supplier definition (without addresses) is

determined by the primary site entity found within the transaction.
The EDI translator writes a trading partner code for the record 0010
control record but it is not reviewed by the EDI Gateway. The detail
location codes extracted from N104 and NAD records are reviewed
within the EDI Gateway to determine the primary entity as needed by
the Oracle application.
The primary trading partner location is the address location reviewed
within the transaction to determine the trading partner code for the
record 0010 control record. This is the coded that links the transaction to
the trading partner definition in the EDI translator.
Document
Direction
ASC
X12
EDIFACT
Content
Primary Trading
Partner Location
INI
Inbound
810
INVOIC
Invoice
SUPPLIER SITE
CATI
Inbound
832
PRICAT
Price / Sales
Catalog
SUPPLIER SITE
RRQI
Inbound
843
QUOTES
Response to
Request for
Quotation
SUPPLIER SITE
POI
Inbound
850
ORDERS
Purchase Orders
SHIP TO
ANSI
Inbound
856
DESADV
Ship Notice /
Manifest
SUPPLIER SITE
SBNI
Inbound
857
n/a
Shipment and
Billing Notice
SHIP TO
INO
Outbound
810
INVOIC
Invoice
BILL TO
PYO
Outbound
820
REMADV
/ PAYORD
Payment Order /
Remittance
Advice
PAYING BANK
BRANCH
SPSO
Outbound
830
DELFOR
Planning
Schedule
SUPPLIER SITE
POO
Outbound
850
ORDERS
Purchase Orders
SUPPLIER SITE
Table 2 1
23
Document
Direction
ASC
X12
EDIFACT
Content
Primary Trading
Partner Location
POCO
Outbound
860
ORDCHG
Purchase Order
Change
SUPPLIER SITE
SSSO
Outbound
862
DELJIT
Shipping
Schedule
SUPPLIER SITE
Table 2 1
Each trading partner is assigned a primary address to associate with the

transaction, such as billto address for outbound invoices or shipto
address for inbound purchase orders.
If a trading partner is both a customer and a supplier, Oracle
recommends that you define the partner twice, once as a customer and
once as a supplier. For each, enter a note in the trading partner
description field to indicate whether it is the customer or supplier
definition.
You must define a trading partner header for every location code found
in the transaction. For example, an outbound invoice may have a
remitto location and a shipto location. Both locations must be defined
as trading partners in the EDI Gateway to define the external location
code to appear in transactions.
Test / Production Transaction Status

Each application open interface has its own processing rules for
validating EDI inbound transactions, including those marked as test
transactions. The test / production status code is found on the control
record (0010) in the data file. The status code is set by the EDI translator
for inbound transactions. For outbound transactions, the status code is
set by the EDI Gateway.
Some open interface programs include a test / production status code as
one of the parameters entered when you launch the Standard Request.
This status code may override the test / production status code found in
the control record (0010) for each transaction.
Note: The test / production status code may be presented
differently for various reasons. For example, T for Test, P for
Production, or Y for Yes.
If the application open interface table has a test / production status
code, the following may happen:
24
the test / production status code is passed from the control record
of each transaction to the open interface table without being
overridden by the Standard Request Submission or the open
interface.
the test /production status code is passed from the control record
but overridden by the test / production code from the Standard
Request Submission parameters
the test / production status code is ignored by the application
open interface and is determined from the Standard Request
Submission parameters.
For further information, refer to the Oracle Manufacturing and
Distribution Open Interfaces Manual, Release 11 or the Oracle Financials
Open Interfaces Manual, Release 11.
EDI in a MultiOrganization Environment

A separate EDI responsibility must be defined for each organization that
processes EDI transactions. Therefore, you must run EDI transactions
separately by organization.
Note: Some outbound transactions may operate on all
organizations. However, you must still define a separate
responsibility for each organization.
For outbound transactions, you extract data for the organization
assigned to the current responsibility. So, if you intend to extract data
from multiple organizations, you must do so from separate
responsibilities.
For inbound transactions, the EDI translator, another process, or the
trading partner sending the data file must separate the transactions by
organization before the EDI Gateway imports the data. In other words,
each data file sent by a trading partner should contain only those
transactions into the specific organization.
If you intend to extract data from multiple organizations, you must
switch to Transactions associated with other organizations will not
successfully crossreference the trading partners location codes. The
EDI Gateway associates the organization defined in the EDI Gateway
responsibility with each primary trading partner location during the
location cross reference. If the responsibility has organization A, but all
the trading partner primary locations in the transactions are defined to
organization B in the Oracle Application, the location codes cross
reference process cannot find the location in the Oracle Application. The
25
EDI Gateway reads only trading partner locations for the specified
organization.
Attention: During code conversion, the organization defined in the

EDI responsibility is assigned to the trading partner primary
location. If that organization is not correct for the location, the
application open interface rejects the transaction during validation.
Review the error report or online error handling procedure for the
specific application.
Separate Transactions by Location

EDI translators can separate transactions into different data files.
Transactions can be segregated into:
different trading partner electronic envelopes
different functional groups within the same electronic envelope
different mailboxes.
One solution is to have your trading partner separate the transactions in
separate address locations that mirror your different organizations. If
you have a single physical address that you have defined to two or more
organizations, you may request that your trading partner also
distinguish the locations. They can define unique address site / location
codes in their application even those codes have the same physical
address. The EDI translator can then separate the transactions to
different electronic envelopes or functional groups within envelopes.
The transactions can then be processed separately into different
organizations.
Address Site ID Retrieval

Each transaction is associated with a primary internal location address
site defined in the Oracle application. That has a corresponding external
location code defined by the trading partner. The external code is the
location code found in the ASC X12 N1 name segment or the
UN/EDIFACT NAD name and address segment. Multiple customers
could use the same external location codes because the combination of
their trading partner translator code (their identifier in the EDI
translator) and their external location code make a unique combination
in the EDI Gateway trading partner definition. This pair of codes is
associated with the address site in the Oracle application.
There is a conflict when a given trading partner sends transactions with
the same trading partner translator code and the same external location
codes. However, some of these transactions are split across different
26
organizations. Only one organization can be associated to a given

address site.
Each EDI trading partner location code is derived from a unique address
site ID defined in the Oracle application. That site ID is often written
into the transaction so that the application open interface can correctly
identify the correct address site for the customer, supplier, or other
trading partner.
When extracting or importing transactions, only those address site IDs
that belong to the organization defined for the current responsibility are
retrieved. The same location codes used in other organizations are not
retrieved, since the process is organizationspecific.
The following table illustrates an external location code defined in
multiple organizations. Assume that the trading partner used the code
AB123 that is associated with two addresses in different organizations in
the Oracle application:
Customer
or Supplier
Address Site
Trading Partner
Translator Code
External
Location
Code (on N1
or NAD
segment)
ACME Inc.
123 Main, Chicago IL
E1ACME1
AB123
ACME. Inc.
123 Main, Chicago IL
E1ACME2
AB123
Address Site ID
Organization for
the Address Site
ID
12345678
13567890
Table 2 2 Sample Trading Partner Data
Note: The organization is defined in the Oracle application for this

address site. This is not validated by the EDI Gateway. It may be
passed to the application open interface table given the address site
ID that is retrieved by the EDI Gateway.
The address site ID is assigned when you set up the trading partner
and is retrieved when the EDI Gateway processes the transaction.
The EDI Gateway crossreferences the trading partner external
location code to the Oracle application internal location code
(defined during trading partner set up) to retrieve the associated
address site ID to be used bye the application open interface. For
organization A, only the address site IDs defined for organization A
are retrieved. Address site ID 13567890 in organization B is not
referenced during execution.
27
Attention: If there are problems with transactions loading to the

correct address site, review the organization for the address site, and
check the EDI responsibility in use when loading transactions to the
open interface tables.
Test and Production Environments

The following table describes four possible scenarios for inbound
transactions. If you import a production transaction into either a
production or test environment, or if you import a test transaction in a
test environment, the open interfaces validate the data and load it into
production tables.
However, you must use caution when importing a test transaction into a
production environment. Otherwise, test data is imported into your
production environment.
Transaction Status
Application Environment
Production
Test
Production
Open interfaces validate

and load into application
tables. Set parameters as
required by the application
open interface.

open interface.
Test
See Test Transaction to

Production Environment.

open interface.
Test Transaction to Production Environment

Caution: Unless care is exercised, test transactions may be
processed into production tables. You must set up test / production
status codes properly in your EDI translator and enter them
properly when you launch Standard Requests to ensure test data is
not loaded into your production database.
If the application open interface has a test / production status code and
it is set for test, validation is performed but data is not committed to the
database. (To perform a complete test where data is committed to the
database, you must set up a test environment with a test database.)
28
If the trading partner is currently in production for the particular

transaction at the particular site, and you want to test a transaction for
that trading partner, make sure that you set up a trading partner for the
test transaction with a different translator code. All test transactions
must be given a different translator code when defining trading partner
data. All test / production flags are associated with the combination of
the trading partner definition and the translator code. Providing
different translator codes for production and test transactions ensures
that the two are not confused. This is only necessary if the trading
partner is mixing production and test transactions for the same locations
within one translator code.
See Also
Defining Trading Partner Data

"
To define a trading partner group:

1.
Navigate to the Trading Partner Groups window.
2.
Enter a unique trading partner group identifier.

A trading partner group is a collection of individual address entities
for a given trading partner.
3.
Optionally, enter a description for the trading partner group.
29
4.
Do one of the following:

To add a new trading partner to a trading partner group, enter the
trading partner code and description. Then choose the New
button.
This trading partner entity is linked to a physical address in the
Oracle application using the Assignments alternative region of
the Define Trading Partner window.
To update an existing trading partner in a trading partner group,

enter the trading partner location code and description. Then
choose the Open button.
5.
"
2 10
For Automotive users, choose the Automotive button to enter

additional trading partner information. See: Entering Additional
Trading Partner Information, Oracle Automotive Users Guide, Release
11.
To define a trading partner within a trading partner group:

1.
Enter a unique trading partner identifier. This defines a trading

partner identifier for the EDI Gateway. This code is not written to
the data files.
2.
Optionally, enter the trading partner description.
3.
Enter references 1 and 2. This is for any additional information

needed by the trading partner.
This data is written to the control record of every outbound
transaction as the primary location for the specific transaction. You
can use this information to return codes to the trading partner per
their requirement.
For example, assume the billto customer wants code ABXY
added to all invoices, but you do not want to define an application
flexfield for this customerspecific code. Once the code is in the
data file, you can map it to the desired data element in the standard
transaction.
4.
"
Access trading partner flexfields (also known as attributes) set up

using system administration.
To define trading partner assignment:

1.
In the Assignment alternative region, associate this trading partner

definition with the corresponding Oracle Applications physical
address entity. This is usually address or sitelevel data.
2.
Do one of the following:

If you are defining the trading partner as a customer, select a
customer and customer site. These values are defined in Oracle
Order Entry and / or Oracle Receivables.
If you are defining the trading partner as a supplier, select a
supplier and supplier site. These values are defined in Oracle
Purchasing and / or Oracle Payables.
If you are defining the trading partner as a bank, select a bank
branch address. This value is defined in Payables.
If you are defining other trading partner relationships, select the
Human Resources location code. These values are defined in
Oracle Human Resources.
"
To define trading partner details:

1.
Open the Details alternative region to enable EDI transactions and

processing rules for the trading partner location.
2.
Select the EDI document and the document type. Doing so enables
the transaction for the trading partner.
You must enter each document and each type explicitly to enable the
transaction. If you do not enter both, no data is extracted.
2 11
3.
Enter the translator code (as defined in the EDI translator software)
to associate with the transaction and location which is being
enabled. The translator code links the EDI Gateway trading partner
definition to that in the EDI translator.
4.
Indicate whether to send documents via EDI to this trading partner.

This permits outbound transactions to be extracted and sent via EDI
for this trading partner.
5.
Indicate whether to print a paper copy for this partner. (This

functionality is not presently supported.)
6.
Indicate whether you are sending / receiving test EDI transactions

for this partner.
This allows transactions to be marked as a test transaction even if it
is extracted from a production application. This code should agree
with the test / production flag defined in the EDI translator
software.
"
To define trading partner contact data:

H
2 12
Optionally, open the Contact alternative region and enter the EDI
contact name, title, basic address information, electronic mail
address, phone, fax number, and so on. This information is useful
for EDI coordinators in case issues arise regarding transmission of
EDI files. This data is not written to the data files. The data is
independent of all contact information in the Oracle Applications.
CHAPTER
Code Conversion
T
his chapter covers the code conversion feature of Oracle EDI

Gateway:
Overview: page 3 2
Defining Code Conversion Categories: page 3 13
Assigning Categories: page 3 14
Predefined Code Categories: page 3 15
Defining Code Conversion Values: page 3 18
Code Conversion
31
Overview of Code Conversion

The Oracle EDI Gateway code conversion function provides a method
by which trading partner codes can be converted from and to codes
used in Oracle Applications. For example, assume that the ABC
Corporation transmits a purchase order to the XYZ Corporation. The
XYZ Corporation processes the incoming data using its own internal
codes, but they are required to return the ABC Corporations original
codes. In this way, the trading partner that created the original
transaction receives response transactions in their own internal codes.
The code conversion function enables you to:
Store trading partners external data that is equivalent to internal
application data.
Store and translate different categories of data, including unit of
measure, carrier code, and location codes such as shipto, billto,
and remitto locations.
Store and read key information from the EDI translator to
validate inbound transactions. For outbound transactions, this
information is used to pass meaningful information to the EDI
translator.
Identify unique conversion codes at the customer, customer site,
or up to five levels of a search key: for example, a customer with
multiple shipto locations, each of which has unique carrier
codes, all of which must be converted to internal carrier codes.
Each data element in the data file contains data as defined in the
senders or in the receivers application. The type of data that is
typically converted includes location codes, item (product) codes, carrier
codes, and unit of measurements.
For example, Purchasing defines buyer product codes and locations
while Order Entry defines supplier product codes and customer
locations. A code conversion or cross reference must be established
before the correct product can be shipped to the correct location.
There are several types of codes that need converting and they may be
converted in two places.
Item Code Conversion

Buyer product codes and supplier product codes are likely to be
different. Some trading partners may send both the buyer and supplier
product codes. Others may send only one. Often the product code must
be converted to the internally defined product code even if both product
32
codes are sent. An Oracle Application internal code sent from a trading
partner may not be reliable.
Generally, it is appropriate that the application retain both the buyer and
supplier product codes to avoid future code conversions. If this is not
done, consider using an API within the application to convert the codes.
Alternately, if the product fields are identified in the EDI Gateway as
candidates for general code conversion as assigned in the Code
Conversion Assignment window, EDI Gateway can convert the codes if
a code category is assigned.
For inbound transactions, item (product) code conversions are
performed by the application open interface, when possible.
For outbound transactions, item (product) code conversions are
performed by APIs called by the EDI Gateway during the transaction
extract when possible.
Alternately, item code conversion can be performed by the EDI Gateway
general code conversion tables, if not addressed by the Oracle
Applications.
Both the internal and external items should be in the data files.
Location Code Conversion

Trading partners have address location codes generated by their
respective applications to represent the same physical address. For
example, the trading partner location site code ABC, which is externally
defined to your application, must be converted to code 123 before your
application recognizes the location site.
You can perform most location code conversions by properly setting up
trading partners in the EDI Gateway. See: Defining Trading Partner
Information: page 2 9.
Location code conversion does not use the general code conversions
except where noted in a specific transaction. Some types of locations
may need a code conversion through the general code conversion set up
if the particular location application address table does not
accommodate the link to the EDI Gateway.
General Code Conversion

Like trading partner location codes, many general codes need
converting. These codes usually are found in two categories:
Oracle application codes to EDI or ISO standard codes
Code Conversion
33
Oracle application codes to trading partnerspecific codes.

Oracle Application Codes to EDI Standard Codes or ISO Codes
Codes like unit of measurement, currency, and country codes have been
defined by standards organizations such as ASC X12 and EDIFACT.
However, these codes may not be the codes recognized by the Oracle
application where many fields are userdefined. Hence, any codes of
this class in the standard transaction must be converted to data that the
Oracle application can recognize.
Oracle Application Codes to Trading Partnerspecific Codes
Codes like carrier codes may be defined in the trading partners
application. Like standard defined codes, these codes must be
converted to internal codes to be recognized by the Oracle application.
A response transaction may be required to return the codes exactly as
they were received in the original transaction. Either the application
retained both the external and internal codes or code conversion must be
performed to reverse the original code conversion.
The EDI Gateway code conversion function performs the general code
conversion.
During code conversion:
external data is converted to internal application data for inbound
transactions
internal application data is converted to external data for the
trading partner for outbound transactions.
General code conversions for inbound and outbound transactions can be
accommodated with the EDI Gateway or the EDI translator. You decide
which application is the best for your environment, user responsibilities,
and application access.
Inbound transactions can crossreference the data during the EDI
Gateway processing. The inbound transaction files are not updated by
the EDI Gateway with the internal codes, although they are defined on
the data file record. The retrieved codes are loaded into the interface
tables for the API without writing the codes to the data files.
The EDI Gateway only uses the data defined as internal data for the
application interface tables. Either the EDI Gateway or the EDI
translator must determine the internal code given the external data
found in the transaction.
For inbound transactions, if the code conversion for a data element is
enabled in the Assign Categories window, the code conversion takes
34
place even if it was already done in the EDI translator if there is data in
the external field. For outbound transactions, code conversion always
occurs if the data element is enabled for code conversion.
Data that needs converting has at least two data elements defined on an
outbound record on the Oracle data file. One data element contains the
data as defined in the Oracle application (internal data), and the other
data element has the data as requested by the trading partner or
required by the standards (external data).
Each internal code may crossreference one to five external fields.
The EDI translator should use the external fields in their general data
maps, if populated. If no values exist in the external fields, then, use the
internal fields.
Code Conversion Categories

A code conversion category is a code that represents a subset of entries
in the general code conversion table. For example, table entries under
category UOM cover unit of measurement code conversion; table
entries under category SHIP VIA cover carrier / ship via code
conversions. See: Defining Code Conversion Categories: page 3 13.
Oracle EDI Gateway provides a set of seeded code categories. However,
you can define your own code category names. You could use a
different category per application. For example, UOM_OE and
UOM_PO could be used for unit of measurements in Order Entry and
Purchasing, respectively.
A single code category can be used with many data elements within a
transaction and across many transactions.
If the entries for code conversion apply to all trading partners, do not
enable key search fields when assigning categories. These fields are
used to indicate how many search keys to use to find table entries for a
specific trading partner. For example, if Key 1 is used, one data field
may be used in a search key to find entries with a specific value in one
key. If Key 2 is also used, a second data field is concatenated to the first
search key to narrow the table entry to a more specific business entity.
Up to five keys may be used as a search key for the table entries. See:
Assigning Categories: page 3 14.
The actual code conversion values for a specific trading partner are
entered when you define code conversion values. From one to five
search keys can be entered to narrow the table search to specific trading
partners or any entity identified in the data file. See: Defining Code
Conversion Values: page 3 18.
Code Conversion
35
Note: If a category is used across many transactions and the

code conversion table is trading partner or trading partner
sitespecific (i.e., does not apply globally), verify that each
transaction has the same trading partner or trading partner site
data in the transactions for entries in the code conversion value
tables.
For example, assume the SHIP_VIA is used in the Order Entry inbound
purchase order and outbound invoice transactions. Assume also that
the purchase order transaction has supplier codes, but the invoice
transaction has supplier numbers. In this case, the code conversion
values entered require different table entries: one set for the supplier
number as key; the other set for the supplier code as the key.
Search Keys
Code conversion for a given trading partner may have one to five keys
to search a table for their specific codes. For example, carrier codes may
be set up for a specific destination (ship to) location, a specific customer
(over several ship to locations), or be a generic code across all customers.
To limit a code conversion table entry to any entity, search keys must be
established; otherwise, the internal and external codes in the table entry
apply to all trading partners.
When a search of the code conversion table begins, all defined keys (up
to five) are concatenated and treated as a single search key. If the search
is unsuccessful, the last key is removed and the search is performed
again with all remaining keys. The removal of one key continues until a
table entry is found. If no entry is found, the default is used. If the
default is not found, null is returned.
An accurate number of keys must be enabled for the data element to
avoid superfluous access to the code conversion table. For example, if
five keys are enabled, but only two keys are entered in the code
conversion values, the table is accessed three times without benefit.
Similarly, if the code conversion value table has data in search keys 1
and 2, but no keys are enabled, only a global, generic search is made and
the keys are ignored.
The data elements used in the search key must be defined in the tables
and columns assigned to the specific transaction in the Assign
Categories window.
In addition, the number of search keys used must be enabled in the
Code Conversion Categories window to use the keys specified in the
Assign Categories Window.
36
Example
In this illustration, only the first two search keys were enabled in the
Code Conversion Categories window:
Search Order
Category
Key 1
Key 2
First Search
SHIP_VIA
CUSTOMER CODE
SHIP TO
SITE
CODE
Second Search
SHIP_VIA
CUSTOMER CODE
SHIP_VIA
No specific key provided.

The third search will
be a generic search
with no specific key.
Third Search
Keys 35
Fourth Search
(none)
Fifth Search
(none)
Code Conversion Category Setup

In the Code Conversion Categories window, two Key Used check boxes
were enabled for code conversion category SHIP_VIA. In this case, the
search keys contain the customer code and the shipto site code.
In the Assign Categories window, assume the following:
transaction = Purchase Order Inbound
output level = header
view name = SO_HEADERS_INTERFACE
reference view column = SHIP_VIA
Assume the category SHIP_VIA and the column name where the actual
customer code is found is entered under Key 1 View Column. Use
CUSTOMER_NUMBER.
The column name where the actual ship to site code is found is entered
under Key 2 View Column. Use SHIP_TO_SITE_NUMBER.
Code Conversion Values Setup
The following table shows the data as set up in the Code Conversion
Values window (the code conversion category is SHIP_VIA):
Code Conversion
37
Internal Code
Key 1
Key 2
Ext 1
Ext 2
UPSBLUE
1004
1010
UPS
FED_EXP
1004
1010
FEDEX
FED
FEDEXP
In the Code Conversion Value window, the actual customer code for the
specific trading partner is entered under Key 1. Use 1004 for their
specific customer code.
The actual shipto site code for the specific trading partner is entered
under Key 2. Use 1010 for their specific ship to site number.
First, the two keys, customer code and the shipto site number, are
concatenated to 1004+1010. The search is performed using this
concatenated key (1004 + 1010). If no value is found, a second search by
the customer code alone (1004) is made. If no value is found, a default
code conversion value (no key specified) is used. If no default is found,
null is returned.
During the execution of the EDI Gateway of inbound transactions, the
internal data found during code conversion is written to the application
interface tables. For outbound transactions, the internal and external
codes are written to the data file according to the data file definition
defined in the Interface File Definition window. The EDI translator
should use the external fields in their general data maps if populated;
otherwise, use the internal fields.
Code Conversion Values

The actual codes to be converted are defined in the Code Conversion
Values window.
The transaction data file may have data in the External Code 1 through
External Code 5 from the EDI translator data mapping. For example,
the carrier code may be in external code 1 and transportation method
(air, land, sea) may be moved to external code 2. These two codes
together determine the internal code used by the Oracle Application.
38
If the EDI translator does the code conversion, the resulting code is
moved to the internal code.
If the EDI Gateway does the code conversion, the derived internal code
is passed to the application open interface tables and not written to the
data file.
The transaction data files have the Oracle Application internal code, and
External Code 1 through External Code 5 (as many as indicated for this
transaction field in the Interface File Definition window).
When the EDI translator does the data map, it maps data from the
external fields if they are populated. Otherwise, they map the internal
codes to their position in the standard.
The following is an example of the code conversion table:
Meaning
Code
Conversion
Category
Internal Code
Ext 1
Freight Carrier code
CARRIER
UPSBLUE
UPS
FOB Terms
FOB
ORIGIN
OR
Payment Terms
PAY_TERMS
NET 10, 3O DAYS
.10
Tax Exempt Flag
TAX_EX
Transaction Purpose
Code
TRX_PURP
CHANGE
04
Unit of Measurement
UOM
EACH
EA
Ext 2
30
Note the following:

The Oracle data files have one data field for the Oracledefined
internal codes and one to five data element fields for their
external counterparts. An internal code is a code defined in the
transaction host Oracle Application regardless of the direction of
the transaction.
For inbound data, the data from the standard transactions that
need code conversions are moved to the external data elements in
the data files by the EDI translators. The EDI Gateway can
determine the internal data elements. If the EDI translator
Code Conversion
39
determines the Oracle internal code, it is written to the data

elements internal code field in addition to the external values.
For outbound data, the Oracle application data is stored in the
internal field. If the internal data is crossreferenced, the results
of the code conversion are stored in the external data elements.
The EDI Translators should usually move the data in the external
fields to the standard transactions. If no data is present in the
external fields, the internal fields should be mapped to the
standard.
Most code conversions match one internal code to one external
code. In this case, only one external field is activated on the data
file. You can choose to activate the external fields 25 if necessary
for the transaction. Data field conversions that are known by the
application to convert to more than one external code are
indicated in the predefined data files.
Use of Two Standards in Code Conversion

There are three options to accommodate code conversion to two or more
standards in the EDI Gateway:
one constant standard code in the data file in a single external
record
multiple standard codes in the data file in a single external field
multiple standard codes in multiple external fields in the data file
One Constant Standard Code in the Data File in a Single External
Field
Let the EDI Translator convert the code on the file to a second standard.
EDI Gateway
EDI Translator
Internal Code
External Code 1
External Code 1
Second Standard
PER HUNDRED
PH
PH
PERH
There is the option that one standard (such as ASC X12) be maintained
in the EDI Gateway and written to the data file. If some trading
partners require an alternative standard (such as EDIFACT), the first
standard on the data file can be converted to the second standard (such
3 10
as ASC X12 to EDIFACT) by the EDI translator for specific trading

partners.
This second standard code conversion is minimized in the EDI
translator if the predominant standard is converted in the EDI Gateway
and the second standard is converted in the EDI translator.
Multiple Standard Codes in the Data File in a Single External Field
Use a search key to a specific trading partner or group of trading
partners.
EDI Gateway
Category
Search Key 1
Internal Code
External Code 1
UOM
Alpha Company
PER HUNDRED
PH
UOM
Beta Company
PER HUNDRED
PERH
The EDI Gateway code conversion has the option of specifying code
values within a Code Category to a specific trading partner or other
search criteria. This method may accommodate code conversion in
some categories. However, this method requires numerous code
conversion table entries if the search key is customerspecific.
Multiple Standard Codes in Multiple External Fields in the Data File.
EDI Gateway
Category
Search Key 1
Internal Code
External Code 1
External Code 2
UOM
(optional
blank)
PER
HUNDRED
PH
PERH
Most code conversions are likely to have one internal code to one
external code. Consequently, most data elements have just one
anticipated external field defined in the EDI Gatewaydefined data files.
However, the EDI Gateway code conversion process can write two
standards codes, one in External code 1, the other in External code 2, to
the data file by doing the following:
Code Conversion
3 11
In the Code Conversion Categories window:

enabling the corresponding Used Key 2 fields
indicating one standard in the external 1 field, and the
second standard in the external 2 field for the same table
entry.
In the Interface File Definition window:
Add an external 2 field to the data file by assigning it a
record number, position, width, conversion sequence, record
layout, record layout qualifier, and so on to ensure that the
additional fields are written to all desired records in the data
file.
Note: Any record within the transaction must be 600 characters
or less. If the activated external value 2 forced the record
beyond 600 characterss, you can move the external value 2 to
another record within the data level of that transaction. Data
levels indicate header, item, or other detail level tables of that
transaction. Alternatively, other data elements can be moved to
other records to make room for external value 2.
If you change interface records over time, but continue to archive
transactions to the same historical file, you may not be able to recreate
the standard records in the EDI translator. Different data file record
layouts may have the same modified map name.
Unused external codes 25 may be found at the end of the interface
tables in the Code Conversion Values window since they were not
assigned a record number, position, width, conversion sequence, record
layout code, record layout qualifier and other data file data by the EDI
Gateway.
If the external 2 code was not at the end of the tables, this method
cannot be used on that specific data field. Contact World Wide Support
to report the required data element from the EDI Gateway interface
table.
Note: Changes you make to all interface records require
changes to the EDI Translator data map.
The EDI Translator data maps or templates need changes to recognize
the additional standard code in the additional external fields, and use
the correct standard code for the appropriate trading partner.
See Also
3 12
Defining Code Conversion Categories: page 3 13

Changing the Data File: page 5 2
Defining Code Conversion Categories

All desired categories, such as unit of measure or carrier code, must be
defined. Each category is associated with a specific table and column
that contains the Oracle internal data. Any category can be used in
several transactions, or several times within a single transaction.
Once defined, code conversion categories must be assigned to table
columns to activate the code conversion for the specific data element.
You can use a code conversion category for the EDI Gateways
predefined list or you can define your own code conversion category.
"
To define additional code conversion categories:

1.
Navigate to the Code Conversion Categories window.
2.
Enter the category code and description.
3.
To assign code conversion values to specific trading partners, enable

one or more search keys.
Code Conversion
3 13
The actual search criteria is entered in the Assign Categories

window.
See Also
Overview of Code Conversion: page 3 2
Predefined Code Categories: page 3 15
Assigning Categories
For a given transaction, use assign code conversion categories to activate
code conversion for a transaction data field. If search keys are enabled
when you defined code conversion categories (see: Defining Code
Conversion Categories: page 3 13), use this window to identify the
view columns containing the search value.
Prerequisites
Define code conversion categories. See Defining Code Conversion

"
3 14
To assign code conversion categories:

1.
Navigate to the Assign Categories window.
2.
Select a transaction.
3.
Select an output level.

The views and column names for fields identified by the EDI
Gateway for code conversion are displayed.
All the data elements identified as code conversion candidates are
displayed. For outbound transactions, the list of data elements from
each interface view table is displayed, sorted by output level.
For inbound transactions, the list of data elements from each
application open interface table is displayed, sorted by output level.
Output level is an indicator of each table defined in the EDI
Gateway, for example, HEADER, ITEM, or DETAIL.
4.
Assign a code category to activate code conversion for the view or

application open interface column. If no code category is assigned,
code conversion is not performed. See: Predefined Code Categories:
page 3 15.
5.
Specify a view or application open interface table column (Key 1

through Key 5) containing the key search value if a code cross
reference is applied selectively to only certain trading partners or
EDI transaction.
However, if you intend a code cross reference to apply globally for
all trading partners, do not enter values for key view column fields.
Attention: The values for the specified view column are used to
access the code conversion cross reference table for the
corresponding external value(s). If no entry is found which
corresponds to the search key, the global code cross reference value
is applied.
See Also
Predefined Code Categories

The following are valid code categories preseeded by Oracle EDI
Gateway. You may use these codes or add new code categories for use
when assigning categories. See: Assigning Categories: page 3 14:
Code Conversion
3 15
Category
Codes
AC_HANDL
Allowance and Charge Handling
AC_SPECC
Allowance and Charge Special Charges
AC_SPECS
Allowance and Charge Special Services
ACTION_TYPE
Action Type
AETC_RESP
AETC Responsibility
AETC_RSN
AETC Reason
AGREEMENT
Agreement
BANK_ACCT_TYPE
Bank Account Type
BANK_BRCH_ID
Bank Branch ID
BANK_BRCH_TYPE
Bank Branch Type
BILL_TO_LOCATION
BillTo Location
BUYER_ITEM
Buyer Item (Product)
BUYER_PRODUCT
Buyer Product
CARRIER
Freight Carrier
COMPANY_CODE
Company
CONTAINER_CODE
Container
CONTAINER_TYPE
Container Type
CONTAINER_TYPE_CODE
Container Type
COUNTRY
Country
CURR_CONV_TYPE
Currency Conversion Type
CURRENCY
Currency
CUSTOMER_CODE
Customer
DOCUMENT_TYPE
Document Type
EQUIPMENT
Equipment
FOB
FOB
FOB_PAYMENT
FOB Payment
FREIGHT_TERMS
Freight Terms
Table 3 7
3 16
Category
Codes
HAZ_CLASS
Hazardous Class
HAZ_MAT
Hazard Material
INVOICE_SITE
Invoice Site
INVOICE_TYPE
Invoice Type
ITEM_CATEGORY
Item Category
ITEM_TYPE
Item Type
LOC_BANK_BRCH_SITE
Location Bank Branch Site
LOC_VENDOR_SITE
Location Vendor Site
ORDER_TYPE
Order Type
PAY_FMT
Payment Format
PAY_METH
Payment Method
PAY_TERMS
Payment Terms
PAY_TYPE
Payment Type
PRICE_BASIS
Price Basis
PROVINCE
Province
REGION1
Region 1
REGION2
Region 2 (for state in certain address tables)
REGION3
Region 3
SHIP_ORDER_STAT
Shipment Order Status
SHIP_PRIOR
Shipment Priority
SHIP_TO_LOCATION
Ship To Location
SHIP_TO_ORG
Ship To Organization
SHIP_TO_SITE
Ship To Site
SHIP_VIA
Ship Via (carrier)
SS_DESCRIPTOR
Supplier Scheduling Descriptor
STATE
State
SUPPLIER_NUMBER
Supplier Number
Table 3 7
Code Conversion
3 17
Category
Codes
SUPPLIER_SITE
Supplier Site
TAX_CODE
Tax Code
TAX_EX
Tax Exempt Flag
TAX_EXRSN
Tax Exemption Reason
TAX_JURS
Tax Jurisdiction
TRANS_TERM
Transportation Terms
TRX_HANDL
Transaction Handling
TRX_PURP
Transaction Purpose
UOM
Unit of Measurement
VENDOR
Supplier Code
VENDOR_BANK_ACCT_TYPE
Supplier Bank Account Type
VENDOR_NAME
Supplier Name
VENDOR_NUMBER
Supplier Number
VENDOR_SITE
Supplier Site
WAREHOUSE
Warehouse
WAREHOUSE_SITE
Warehouse Site Code
X12_MAPPING
X12 Mapping
Table 3 7
Defining Code Conversion Values

Depending upon the EDI standard, user requirements, and the
application data, a single Oracle Application internal data element may
require one to five external data elements for the data file to satisfy the
data requirements for the EDI standard or the trading partner.
Prerequisites
Define code conversion categories. See Defining Code Conversion

3 18
Assign Code Conversion Categories. See: Assigning Categories:

page 3 14.
"
To define code conversion cross reference values:

1.
Navigate to the Code Conversion Values folder window.
2.
Enter the category code.
3.
Enter key values (1 to 5) for search keys for the set of internal /
external values.
Use this only if search keys are enabled in the Define Code Category
window and view / interface table columns are identified in the
Assign Code Category window.
4.
Enter the internal and external value pairs (1 to 5) for one to many
conversions.
See Table 3 2 and Table 3 3 for an illustration.
See Also
Code Conversion
3 19
3 20
CHAPTER
Data File Structure

T
his chapter covers the structure of the data file for EDI transactions
transactions:
Overview: page 4 2
Control Record Layout: page 4 4
Required Inbound Control Record: page 4 10
Record Key (1100): page 4 11
Record Layout Codes Summary: page 4 16
Reusable Record Layout Details: page 4 19
Mapping Rules for EDI Translators: page 4 25
Data File Structure
4 1
Overview of Data File Structure

Oracle EDI Gateway produces an ASCII data file for outbound
transactions. For inbound transactions, EDI Gateway processes an
ASCII data file produced by the EDI translator software that contains
the trading partners business data.
Each data file consists of several records. Each record has two sections,
the record key (positions 1100) and the application data area (positions
101 to 600).
The structure is shown in the following table:
Data
Position
Length
Trading Partner Code (short)
125
25
Key 1 (primary document identifier)
2647
22
Key 2
4869
22
Key 3
7091
22
Record Number
9295
Record Number
9697
Record Qualifier
98100
101600
500
Common Key (1100)
Application Data (101 512+)

Table 4 1
You can customize the data file per your specifications and define any
logical record size to be less than 600 bytes.
Reusable Predefined Records

Predefined record layouts such as those for addresses, contacts, and
flexfields are defined by the EDI Gateway. However, verify each data
element length in the detail record for discrepancies.
4 2
Control Record (Record Number 0010)

All transactions begin with a control record that contains transaction
identification, trading partner identification, key document numbers,
document codes, and batch control numbers. Batch control numbers
from the standard transactions are for inbound transactions only since
they are received with the transactions.
Record Key
Each record within a transaction has a record key area of 100 characters
(positions 1100). This area contains the trading partner code, one to
three key identifiers from the transaction document, and record
identification codes. This data should facilitate sorting of the file if data
must be regrouped to facilitate alternate data mapping, and audit and
research of transactions when needed.
The record number in positions 9295 is the record identifier to indicate
the set of data elements on the record.
Each transaction writes different data in Key1, Key2, and Key3 in
positions 2691. Key1 should be the primary document identifier, for
example, invoice number for the invoice transaction, and purchase order
number for the procurement transactions.
Flexfields
The EDI Gateway defines all descriptive flexfields with length of 80
characters instead of their maximum table length of 150 characters.
Most flex fields span four interface file records to store 15 flex fields or
five interface records for 20 flex fields depending on the application
tables. The customer may shorten the fields to actual lengths for their
data and fit the flex fields onto fewer records, or even one record if they
choose. (Use the Interface File Definition window to make these
adjustments.) See: Changing the Data File: page 5 2.
Redefinable Records
You can redefine which records are actually written to the interface file
from all the predefined records in the general transaction extract. (Use
the Interface File Definition window to make these adjustments.) See:
Changing the Data File: page 5 2.
After the records are defined and written to the interface file, all the
defined records are written to the interface table even if there is no
application data after the record key area. There is no skipping of
Data File Structure
4 3
flexfield records if there is no application data, except in the case where

the record is suppressed by removing the data element using the
Interface File Definition window. See: Changing the Data File: page
5 2.
Control Record Layout

Record 0010 is the common control record to be used by both the EDI
Gateway and the EDI translator for trading partner identification and
processing rules. It includes information identifying the transaction
type, transaction date and time, trading partner code, EDI document
being transmitted, and whether it is a test or production transaction.
This record is 600 characters long. The common control record layout is
illustrated in the following table:
Seq.
Data Element
Length
Position
Sample Inbound Transaction
Sample
Outbound
Transaction
01
25
125
A1ACME2
A1ACME1
02
Key 1: (may be truncated)
22
2647
1234567890123456789012
64564522
03
Key 2:
22
4869
04
Key 3:
22
7091
05
Record Number
9295
0010
0010
06
Record Layout
9697
CT
CT
07
Record Qualifier
98100
CTL
CTL
08
Communication Method
101102
ED
ED
09
Test Flag
103
10
Document ID
104109
POI
POO
11
Document Type
110114
STAND
BLANK
12
Document Purpose Code
115116
OR
CH
13
Document Code (full)
35
117151
1234567890123456789012345
64564522
14
Trading Partner Translator

Code (full)
35
152181
A1ACME2
A1ACME1
15
TP Location Code External
30
182216
AC7654
AC9832
16
Trading Partner Description
76
217292
ACME CORP
ACME INC
17
TP Reference 1
80
293372
1234
4 4
Seq.
Data Element
Length
Position
Sample Inbound Transaction
Sample
Outbound
Transaction
18
TP Reference 2
80
373452
9875
19
Transaction Date/Time
15
453467
19970616 230723
20
Transmission Run ID
15
468482
534342
21
Control Number 1 (external)
10
483492
654
22
10
493502
897
23
10
503512
3423
19970626
Control Record (Record 0010)

The following table details the control record:
Seq.
Data Element
Length
Position
Value
Note
01
25
125
First 25
characters of
the Trading
Partner Code
This is the trading partner identified for

this transaction as defined by the EDI
translator. This code is the result of the
location code conversion of the Primary
location code in the Translator Code in
the Trading Partner Detail region in the
Trading Partner form.
02
Key 1: (short)
22
2647
First 20 characters of Document Code.

Do not use in the EDI Translator data
map, since it may be truncated.
03
Key 2:
22
4869
(blank)
04
Key 3:
22
7091
(blank)
05
Record Number
9295
0010
Fixed value 0010.
06
Record Layout
9697
CT
Fixed value CT.
07
Record Qualifier
98100
CTL
Fixed value CTL.
08
Communication Method
101102
E (EDI)
This code indicated if this transaction is to

be faxed or sent via the EDI standard process.
Data File Structure
4 5
Seq.
Data Element
Length
Position
Value
Note
09
Test Flag
103
T (test)
This code is the flag to indicate that the

transaction is to be treated as test (T) or
production (P) by the EDI translator. This
code must remain synchronized with the
Test flag defined in the EDI Translator.
Which code overrides the other if they are
out of sync depends on the EDI translator.
For inbound transactions, the EDI Trading
Partner detail flag prevails.
P (production)
10
Document ID
104109
POI = PO
Inbound
This code identifies the transaction type

and its direction, e.g., POI for purchase
orders inbound.
11
Document Type
110114
BLANKET,
STANDARD
This code identifies sub types of the transactions, such as blanket order or standard
orders to process.
12
Document Purpose Code
115116
OR (original),
This code identifies the transaction as the

original, change, replacement or other appropriate status for the given transaction.
CH (change)
13
Document Code (full)
35
117151
This is the primary transaction code such

as the purchase order or invoice number.
The code is the key document identified
for the specific transaction.
14
Trading Partner Code (full)
30
152181
This is the full length Trading Partner

code defined in the EDI Translator to
identify this Trading Partner.
15
TP Location Code External
35
182216
This code is the Trading Partner location

code as defined by the trading partner for
the given transaction.
This is usually found in the ASC X12
N104 ID code or the EDIFACT NAD segment. This code is maintained in the
Oracle application for this transaction.
16
Trading Partner Description
71
217292
This is the trading partner description as

defined in the EDI Gateway for outbound
transactions or the EDI Translator for inbound transactions.
17
TP Reference 1
80
293372
This is the trading partner reference 1

code defined in the EDI Gateway for the
primary trading partner location for outbound transactions.
18
TP Reference 2
80
373452
This is the trading partner reference 2

code defined in the EDI Gateway for the
primary trading partner location for outbound transactions.
4 6
Seq.
Data Element
Length
Position
Value
19
Transaction Date/Time
15
453467
This is the date and time that the transaction is created by the EDI Gateway or the
EDI Translator.
20
Transmission Run ID
15
468482
Run ID from the Concurrent Manager

which created the transaction.
21
10
483492
from inbound
transaction
22
10
493502
from inbound
transaction
Note
This is the batch control number from the

outer most electronic envelope for inbound transactions only.
This is the ASC X12 ISA or EDIFACT
UNB control number.
This is the batch control number from
the inner electronic envelope for
inbound transactions only.
This is the ASC X12 GS or EDIFACT
UNG control number.
23
10
503512
from inbound
transaction
This is the batch control number from

the starting transactions segment for
inbound transactions only.
This is the ASC X12 ST or EDIFACT
UNH control number.
Data File Structure

Each record is referenced by a record number which identifies the level
and block of data in the data file. The numbering scheme for each level
is in increments of 1000.
Record Number
Content
0010
Control Record
00200050
EDI Gateway Flexfields
10001999
Application Header Level
20002999
Application Detail Level
30003999
Application Next Detail Level
Table 4 4
Data File Structure
4 7
Record Number
Content
40004999
Application Next Detail Level
et cetera
Table 4 4
The exact record number blocks varies by transaction due to variations

in the data required. However, the hierarchy remains the same. Large
transactions may have any level span over several blocks of 1000. For
example, the header level may span from 1000 to 3999, and the item
level may span from 4000 to 5999.
Sample File Structure

The following table from the outbound invoice transaction illustrates the
record number range and levels of data on each record.
Seq.
Data Type
Data Level
Record (Position
9295)
Control Record
CONTROL
0010
Trading Partner Header Flexfields
TRADING PARTNER
00200050
Trading Partner Detail Flexfields
TRADING PARTNER
00600070
Bill To Address /code
INVOICE HEADER (LOCATION)
1000
Bill to Misc. data, contacts
1010
Bill to Customer Flexfields
10201050
Bill to Site Flexfields
10601090
Ship to Address/code
1100
Ship to Misc. data, contacts
1110
10
Sold to Address/code
1200
11
Sold to Misc. data, Contact
1210
12
Remit to address/code
1300
13
Ship From Codes
1400
14
Basic Invoice Header Data
INVOICE HEADER
2000
15
Invoice Amount Data
INVOICE HEADER
2010
16
Invoice Misc. Data
INVOICE HEADER
2020
Table 4 5
4 8
Seq.
Data Type
Data Level
Record (Position
9295)
17
Shipment Data
INVOICE HEADER
2030
18
Currency Data, Misc. data
INVOICE HEADER
2040
19
Payment Terms Data
INVOICE HEADER
2050
20
Sales Representative, Comments
INVOICE HEADER
2060
21
Invoice Header Flexfields
INVOICE HEADER
30003030
22
Invoice Header Interface Flexfields
INVOICE HEADER
30403070
23
Header Allowance/Charges
INVOICE HEADER
30803090
24
Extension Tables: Invoice Header

Data (custom)
INVOICE HEADER
3900
25
Basic Item Data
ITEM
4000
26
Sales Order Data
ITEM
4010
27
Part Descriptions, Sales Channel,

Order Status
ITEM
4020
28
Transaction Reference Key
ITEM
4030
29
Interface Line Flexfields
ITEM
50005030
30
Line Flexfields
ITEM
50405070
31
Line Part Flexfields
ITEM
51005130
32
Extension Tables: Item Data (custom)
ITEM
5900
33
Line Tax Data
ITEM DETAIL
60006010
34
Line Tax Flexfields
ITEM DETAIL
60206060
35
Detail Allowance/Charges
ITEM DETAIL
70007010
36
Extension Tables: Transaction Line

Detail Data
ITEM DETAIL
7900
Table 4 5
See Also
Required Inbound Control Record: page 4 10
Data File Structure
4 9
Provide Additional Values: page 9 10

Required Inbound Control Record

Record 0010 must be found in every EDI inbound data file. The EDI
Gateway does not update the data file from the EDI translator; the
trading partner header flexfield records 00200050 are not added to the
file. The EDI translators do not access Oracle tables to retrieve trading
partner flexfield data from the EDI Gateway tables.
Record
Number
Record Layout
Record
Qualifier
Content
0010
CT
CTL
Control Records
Table 4 6
Required Outbound Control Record

Record 0010 must be found in every EDI outbound data file. The EDI
Gateway populates all data fields except Key 2, Key 3 and the control
numbers at the end of the record.
Record
Number
Record Layout
Record
Qualifier
Content
0010
CT
CTL
Control Records
Table 4 7
Optional Outbound EDI Gateway Trading Partner Records

Records 00200050 may be found in any EDI Outbound data file. You
must enable the trading partner header (system administration
required) to use the following flexfields. The records may appear in the
interface file with no data if the columns are not added to the EDI
Gateway Trading Partner flexfield tables.
4 10
Record
Number
Record Layout
Record
Qualifier
Content
0020
A1
TH1
Trading Partner Header

Flex Fields 14
0030
A2
TH2

Flex Fields 59
0040
A2
TH3

Flex Fields 1015
0050
A2
TH4

Flex Fields
Table 4 8
See Also
EDI Transaction Support: page 1 8
Overview of Data File page 4 2
Record Key (1100)

The following table describes the Oracle data file record key which
occupies the first 100 characters of each record in every transaction. This
area facilitates any visual audit and research into the file.
Note: The content of the first 100 characters on the control
(0010) record is defined the same as every other record in the
interface file.
Some of the transaction data in the record key may be truncated so the
EDI translator should refer to the full transaction data in the data area
(positions 101512) of the record.
Data File Structure
4 11
The data in Key 1 through Key 3 varies by the transaction and the record
level within the transaction.
Attention: The record number should allow the EDI translator

to uniquely identify a record layout within the transaction. Do
not rely on the record layout code and record layout qualifier to
uniquely identify a record.
Record Key Data Element Summary
Seq.
Data Element
TRADING
PARTNER CODE
(short)
125
25
This is the trading partner code for

this transaction as defined by the EDI
translator.
This field may be truncated from the
full Trading Partner Code in positions
149183 on the Control 0010 Record.
KEY 1 (Primary
Key)
2647
22
This is the Primary Key from the

transaction. It may be the purchase
order number, invoice number or
shipper number for corresponding
transactions. Full primary document
key is written in positions 114148.
KEY 2
4869
22
This is the second level key for the

given transaction, e.g., detail level
with item as a key.
KEY 3
7091
22
This is the third level key for the given

transaction.
RECORD
NUMBER
9295
This is a four position number to

identify the record in this transaction.
Use this field to identify what is on
the record.
RECORD
LAYOUT CODE
9697
This is a two character code to

identify record content.
RECORD
LAYOUT
QUALIFIER
98100
This is a three character code to

identify or qualify the record content
especially if the record has a reusable
record layout.
Table 4 9
4 12
Position
Length
Note
Trading Partner Code (125)

This code is the trading partner identifier as defined in the EDI
translator. The code identifies the communications method, electronic
mailbox, standard, and data maps for the specific transaction. This code
is the link between the EDI Gateway and the EDI Translator.
This code is defined as the translator code in the Details region of the
Trading Partner window.
Keys 13 (2691)
Keys 13 represent key data from the first three levels of the given
transaction. This data is for audit or research purposes to facilitate
reading the file directly. The data may be truncated.
Key 1 is the Primary Key from the transaction. It may be the purchase
order number, invoice number, or shipment number for corresponding
transactions. Full primary document key is written in positions 114148
of the control 0010 record.
Keys 23 represents other data at the second and third level within the
transaction. A transaction may have more than three levels of data
which are not stored in the key area.
Record Number (9295)

The record number is a unique number within a transaction to identify
specific data in a transaction. EDI translators should rely on the record
number to uniquely identify a record in the data file.
Data levels in a transaction have record numbers in the thousandth
range. A sample of a simple numbering scheme and a larger range
numbering scheme are displayed in the following table. Any
transaction may use any range of numbers for a data level. The number
usually increments by 10 within a data level.
The record numbers are not used consistently across transactions. For
example, the record 1050 may contain different data depending upon
the transaction.
The X900 series in any range is reserved for EDI Gateway extension
tables for consistency.
Data File Structure
4 13
Sample Record Numbers

Record Number
Sample-Simple
Transaction
Record Number
Sample-Longer
Transaction
Content
0010
0010
Control Record
00200050
00200050
EDI Gateway Flex Fields
10001890
10004890
19001990
49004990

Extension Table
(Customized)
20002890
50005890
Application Detail Level 1
29002990
59005990

Extension Table
(Customized)
30003890
60006890
39003990
69006990

Extension Table
(Customized)
40004890
70007890
49004990
79007990

Extension Table
(Customized)
et cetera
Table 4 10
Record Layout Code (9697)

The record layout code is used to indicate the type of data in the record.
These codes are particularly useful when reusable records such as
addresses and flexfields are used in the file.
Except for reusable records defined by the EDI Gateway, the record
layout may have a different meaning across transactions. For example,
the record layout IT may contain different data depending upon the
transaction.
4 14
Record Qualifiers (98100)

Record qualifier codes qualify what type of data is on the reusable
records or any other record in the transaction. For example, an AD
address record must be qualified to be a shipto, billto, remitto, and so
on address record for visual purposes.
Other record qualifiers are assigned to every record in the transaction to
complete the record key, but they do not necessarily facilitate data
mapping since only the record number uniquely identifies a record to
the EDI translator.
Sample Record Number, Record Layout, and Record Qualifier
Record
Number
Record
Layout
Record
Qualifier
Content
0010
CT
CTL
Control Record
1010
AD
ST1
Address Record with Ship to Location

Data
1040
AD
BT1
Address Record with Bill to Location

Data
1060
A1
HD1
Flex Field data with Reusable Record

A1 Layout qualified by HD1
1070
A2
HD2

A2 Layout qualified by HD2
2000
IT
ITM
IT for Item data qualified by ITM to

distinguish the data from other IT records in this transaction.
2100
A1
IT1

A1 Layout qualified by IT1
2110
A2
IT2

A2 Layout qualified by IT2
et cetera
Table 4 11
See Also
Overview of Data File Structure: page 4 2
Data File Structure
4 15

Record Layout Codes Summary

Record layout codes are indicated in positions 9697 of the record key.
Several data elements relate to each other and can be found in several
standard transactions. These related elements, for example, include
addresses, contact data, and flexfields. The actual content of any record
is qualified by the record layout qualifier, for example, ST or ST1 for
shipto address, and BT or BT1 for billto address.
Attention: You can modify these record layouts. However, any

changes may affect the EDI translator data map you may be
using.
Common Records for Inbound and Outbound Transactions

Seq.
Record Layout
Codes
Description
A1
Flexfield Layout 1
Meaning
Flexfields Layout 1
Layout 1 contains the Flexfield Context

plus attributes each with length 80.
The interface table has the flexfield

with the full length of 150 characters if
needed.
A2
Flexfield Layout 2
Flexfields Layout 2.
Layout 2 contains attributes each with

length 80.

needed.
Table 4 12
4 16
Seq.
Record Layout
Codes
Description
A3
Flexfield Layout 3
Meaning
Flexfields Layout 3
Layout 3 contains the Flexfield Context

plus attributes each with length 100.
The interface table has the attribute
needed.
A4
Flexfield Layout 4
Attribute /Flexfields Layout 4.
Layout 4 contains attributes each with

length 100.

needed.
CT
Control Record
Control Record to start each

transaction
CN
Contact
Record-Format 1
Primary Personnel Contact, title and

phones.
CM
Contact
Record-Format 2
Phones
Table 4 12
Transactions have both external and internal codes contained in the data
file. This facilitates research on extracted application data and the data
that resulted from code conversions. Inbound transactions do not have
the internal fields in the file updated by the EDI Gateway. However,
they are defined in the file in case code conversion is performed by the
EDI translator or another process outside the EDI Gateway.
Reusable record layouts are listed in the following table.
Data File Structure
4 17
Common Records for Outbound Transactions

Record
Layout
Codes
Description
AD
Address Record
Meaning
Full Name and Addresses and Codes for

each business entity where State and
county codes are explicit.
This is usually data from RAtables.
AX
Address Record
A5
Flexfield Layout 5
Full Name and Addresses and Codes for

each business entity where REGION 1,
REGION2, REGION3 contain the state
and county.
This is usually data from HRtables.
Attribute /Flexfields Layout 5
Layout 5 contains four pairs of internal

defined flexfields and its external converted codes plus the Flexfield Context.
The interface table has the flexfield with

the full length of 150 characters if needed.
A6
Flexfield Layout 6
Attribute /Flexfields Layout 6
Layout 6 contains four pairs of internal

defined flexfields and its external converted codes.
The interface table has the flexfield with

the full length of 150 characters if needed.
Table 4 13
See Also
4 18
Reusable Record Layout Details

EDI Flexfield 1 (A1) Record Layout
Pos.
Control Level Flexfields
Length
01
Common key + Record Type
100
02
Any Flexfield Context
30
03
Any Flexfield 1
80
04
Any Flexfield 2
80
05
Any Flexfield 3
80
06
Any Flexfield 4
80
Table 4 14
EDI Flexfield (A2) Record Layout
Pos.
Length
01
100
02
Any Flexfield 1
80
03
Any Flexfield 2
80
04
Any Flexfield 3
80
05
Any Flexfield 4
80
06
Any Flexfield 5
80
Table 4 15
Data File Structure
4 19
Pos.
Length
01
100
02
Any Flexfield Context
30
03
Any Flexfield 1
100
04
Any Flexfield 2
100
05
Any Flexfield 3
100
Table 4 16

Pos.
Length
01
100
02
Any Flexfield 1
100
03
Any Flexfield 2
100
04
Any Flexfield 3
100
05
Any Flexfield 4
100
Table 4 17
Pos.
Flexfields
Length
01
Common Key + Record Type
100
02
Shipment Allowance/Charge Flexfield Context
30
03
Shipment Allowance/Charge Flexfield 1Internal
70
Table 4 18
4 20
Pos.
Flexfields
Length
04
Shipment Allowance/Charge Flexfield 1External
25
(ACSpecial Services_code)
05
70
06
25
(AC_Special_Charges_code)
07
70
(AETC_number)
08
25
09
70
(AETC_Responsibility_Code)
10
25
Table 4 18

The following table has a similar layout to A5 for flexfields 58, 912,
and 1315:
Pos.
Flexfields
Length
01
Common Key + Record Type
100
02
70
(AETC_Reason_Code)
03
25
04
70
05
25
06
70
07
25
Table 4 19
Data File Structure
4 21
Pos.
Flexfields
Length
08
70
09
25
Table 4 19
Address (AD) Record Layout

All name and address records that have explicit state/province and
county data have the following format. There may be cases where the
interface process does not populate some of the data fields depending
on data availability.
Pos.
Business Entity Data
Length
ASC X12
01
Record Type + Common Key
100
02
Business Entity Site Code (internal)
20
Internal
03
Business Entity Site Code (external)
20
N104
04
Business Entity Name
60
N102
05
Business Entity Address Line 1
35
N301
06
35
N302
07
35
N301
08
35
N302
09
Business Entity City
30
N401
10
Business Entity Postal Code
15
N403
11
Business Entity Country (Internal)
20
12
Business Entity Country (ISO) (external)
03
13
Business Entity State (internal)
20
14
Business Entity State (External)
10
15
Business Entity Province (internal)
20
16
Business Entity Province (External)
10
17
Business Entity County
25
Table 4 20
4 22
N404
N402
N402
Address (AX) Record Layout

All name and address records which have REGION 1, REGION2, and
REGION3 in place of explicit state / province and county data have the
following format. This data is extracted from Human Resources tables
as needed. There may be cases where the interface process does not
populate some of the data fields depending on data availability.
Pos.
Business Entity Data
Length
ASC X12
01
100
02
Business Entity Site Code (Internal)
20
Internal
03
Business Entity Site Code (External)
20
N104
04
Business Entity Name
60
N102
05
35
N301
06
35
N302
07
35
N301
08
Business Entity City
30
N401
09
Business Entity Postal Code
15
N403
10
Business Entity Country (Internal)
20
11
Business Entity Country (ISO) (External)
03
12
Business Entity REGION 1 (Internal)
25
13
Business Entity REGION 1 (External)
10
14
25
15
10
16
25
17
10
N404
N402
N402
Table 4 21
Data File Structure
4 23
Contact (CN) Record Layout-FORMAT1

You may add secondary contact data to this record.
Pos.
Business Entity Contact Data
Length
01
100
02
Business Entity Primary Contact
35
ASC X12
PER02
Last Name
03
Business Entity Primary Contact
35
First Name
04
Business Entity primary Contact
40
PER09
Job Title
05
Business Entity Primary Area Code 1
10
PER04
06
Business Entity Primary Telephone 1
60
PER04
07
10
PER04
08
60
PER04
09
10
PER04
10
60
PER04
Table 4 22
Contact (CM) Record Layout-FORMAT2

These records can store phone numbers when contact personnel data is
not available. Area Codes are not stored separately in the application.
Pos.
Business Entity Contact Data
Length
01
100
02
60
PER04
03
60
PER04
04
60
PER04
Table 4 23
4 24
ASC X12
See Also
Mapping Rules for EDI Translators

The following rules apply to EDI translators:
Outbound and Inbound Transactions

If you use descriptive flexfields, you must define them in the Oracle
Application. They require custom changes to the EDI translator data
map for correct placement in the EDI standard or application.
Rely on the record number on every record in Positions 9295 to identify
the record content.
Outbound Transactions Only

A given data element may have both internal Oracle application values
and corresponding external values made up of one to five distinct fields.
For a given data element, the first place to find data is the external fields.
If the External field is empty, move data from the internal fields. Apply
code conversion if necessary.
Inbound Transactions Only

The EDI Gateway can only use the data defined as internal data for the
application open interface tables. Either the EDI Gateway or the EDI
translator must determine the internal code given the external data
found in the transaction. If the code conversion for a data element is
enabled by the Assign Categories window, EDI Gateway performs the
Data File Structure
4 25
code conversion even if the code conversion was already performed in

the EDI translator and there is data in the internal field.
If both internal and external data elements are present in a standard
transaction for a given piece of business data, the EDI translator should
move the data from the standard transaction to the internal and external
field in the data file.
4 26
CHAPTER
Data File Definition

T
his chapter tells discusses how to change the data file format for all
transactions:
51
Changing the Data File

Both inbound and outbound data files are predefined by Oracle EDI
Gateway. The data file may be used as defined or customized to match
your specific business requirements.
Some of the reasons to modify the predefined file format include:
exclude unused columns and unused records
change column size
rearrange data file layout within an interface table
activate data elements in the interface table
change sequence of the five external fields resulting from code
conversion
change the layout code
change the layout qualifier
By making the data file formats tabledriven, your format changes take
effect immediately without any code changes.
"
To change the data file definition:

1.
52
Attention: You cannot use this window to add data elements or

records to the data file format, unless they are already defined to the
EDI Gateway interface tables.
Navigate to the Interface File Definition window.
2.
Select the transaction type.
3.
Select the data level. This is a sixcharacter EDI Gateway code that
identifies the desired transaction and interface table.
This identifies the level of data within the transaction defined in the
EDI Gateway interface table structure. The levels may differ when
compared to the base application tables as data is denormalized.
All the records for the output level are displayed. The data format
for outbound transactions is displayed by EDI Gateway interface
table name and column. The data format for inbound transactions is
displayed by application open interface table name and column.
You cannot change the data in these two columns.
4.
Change the record number.

You can change the record number to another number within the
same level or enter blanks to exclude the record from the data file.
The record number indicates the relative position of a group of data
in a file.
5.
Change the position number.

You can change the position number to another number within the
record or enter blanks to exclude the column from the data file.
The position number identifies the relative position of a data item in
a record. Each record item is numbered sequentially for each logical
group up to 512 bytes of data. A record can support more than 512
bytes only if the EDI translator software can support longer records.
6.
Change the width of the data element.

Most data elements have lengths based on standards. Those lengths
are usually longer in Oracle Applications. You may increase the
length up to the length in the Oracle application as needed per data
element.
7.
Change the sequence of external codes.

This identifies the order of the five external values derived by
applying code conversion to an internal Oracle data element.
Positions for five return values are allocated with default sequence
numbers 1 to 5.
You may retain as many external values in the set required by your
code conversion rules. Or, you may delete all five external values in
the set if code conversion is not used.
A conversion sequence of 0 is reserved for the Oracle internal value.
Do not change.
53
8.
Change the record layout code.

This identifies the data content of a data element. These codes are
predefined for the transaction. Generic record layouts for addresses
and flexfields are defined and used across all transactions. Other
record layouts are defined for a specific transaction. You may
modify the predefined value. See: Record Layout Codes: page
4 16.
9.
Change the record layout qualifier.

This identifies the type of data in the record. For example, a generic
record layout code for addresses may have a record layout qualifier
that identifies the address as a shipto, billto, or remitto address
type. You may modify the predefined value.
See Also
Data File Structure: page 4 1
54
CHAPTER
Importing and
Extracting EDI
Documents
T
his chapter tells you how to import and extract EDI transactions
with Oracle EDI Gateway:
Defining Data File Directories: page 6 2
Profile Options: page 6 3
Running the Import Program for Inbound Transactions: page
64
Running the Extract Program for Outbound Transactions: page
66
Viewing the Status of Concurrent Programs: page 6 8
Data File Definition Format Legend: page 6 9
Importing and Extracting EDI Documents
61
Defining Data File Directories

During implementation, the system administrator sets up inbound and
outbound data file directories.
For the EDI Gateway, define inbound and outbound directories in the
INIT.ORA file and in the ECE: Inbound directory and ECE:
Outbound file path profile options. See: EDI Gateway Profile Options:
page 6 3.
You must define these directories in three places: on your computer, the
INIT.ORA file, and in two profile options. The inbound directory
specification must match in all three places; the outbound directory
must match in all three places.
"
To define data file directories:

1.
Create one directory on your computer to house inbound data files,

and one to house outbound data files.
2.
In the INIT.ORA file, add one line to designate the inbound

directory and one line to designate the outbound directory. Both
must match exactly the directories you created in the previous step.
The syntax is the same for both:
utl_file_dir=directory
where directory is the properly formatted (operating system

dependent) pathname of an existing directory. (For UNIX
operating systems, include the leading slash, /, to designate the
root directory. For example, the following two lines designate the
inbound and outbound directories on a UNIX system:
utl_file_dir=/home/oracle/inbound
utl_file_dir=/home/oracle/outbound
Note: Make sure these directories have open read and write
permissions.
3.
62
After you save the INIT.ORA file, stop and then restart the
database so that your changes take effect.
Oracle EDI Gateway Profile Options

During implementation, the system administrator sets up profile
options.
For the EDI Gateway, you must create inbound and outbound
directories on your computer, and then specify them in the INIT.ORA
file and in the ECE: Inbound directory and ECE: Outbound file
path profile options, respectively. See: Defining Data File Directories:
page 6 2.
ECE: Inbound directory
Indicate the directory where inbound data files are expected. This
value must match the actual directory on disk and that designated in
the INIT.ORA file.
ECE: Output file path
Indicate the directory where outbound data files are written. This
value must match the actual directory on disk and that designated in
the INIT.ORA file.
See Also
Setting Your Personal User Profile, Oracle Applications Users Guide
Common User Profile Options, Oracle Applications Users Guide
Profile Options in Oracle Application Object Library, Oracle Appliactions
System Administrators Guide
63
Running the Import Program for Inbound Transactions

The Oracle EDI Gateway reads the EDI translatorprovided data file
and writes the data into the application open interface tables. The
Application Open Interface validates the data and populates the
application database tables. Data that does not pass validation is
marked for corrective action.
Validation is based on the same business rules applied to the data if it
were entered manually.
Validation is performed at the transaction, header, and detail levels.
Only valid data is imported into the application database.
If no value is found for a required data field, the application open
interface derives default values based on standard value rule sets for
required fields.
Refer to the Oracle Manufacturing Implementation Manual, Release 10 and
the Oracle Financials Open Interface Manual, Release 10 for descriptions of
each Application Open Interface and their corresponding error
detection and recovery processes. Included in the descriptions are
standard value rule sets.
The import program performs the following functions common to all
inbound EDI transactions. The EDI Gateway:
retrieves processing rules defined for the trading partner and
transaction
applies trading partner location cross reference
imports trading partner business data into the application open
interface tables
applies code conversion to external data to derive Oracle
Applications internal data
The Oracle Application Open Interface:
validates data in the application open interface tables
populates the application database with valid data
marks erroneous data for corrective action in the application
64
Prerequisites
Create the inbound directory and update the INIT.ORA file. See:
Defining Data File Directories: page 6 2.
"
To run the import programs for inbound transactions:

1.
Define the ECE: Inbound file path profile option. See: EDI
Gateway Profile Options: page 6 3.
2.
Define trading partner and enable EDI transactions for the trading
partner. See: Define Trading Partner Data: page 2 9.
3.
Define code conversions.

See: Defining Code Conversion Categories: page 3 13, Assigning
Categories: page 3 14, and Defining Code Conversion Values:
page 3 18.
4.
Customize data file layout, if necessary. See: Changing the Data

File: page 5 2.
5.
From the Navigator, choose Import Programs.
See Also
Running the EDI Purchase Order Inbound Program: page 7 20

Running the EDI Invoice Inbound Program: page 7 3
Running the EDI Price / Sales Catalog Inbound Program: page 7 7
Running the EDI Response to Request for Quote Inbound Program:
page 7 11
Running the EDI Ship Notice / Manifest Inbound Program: page 7 28
Running the EDI Shipping and Billing Notice Inbound Program: page
7 31
Submitting a Request, Oracle Applications Users Guide, Release 11
65
Running the Extract Programs for Outbound Transactions

The extract program performs the following functions common to all
outbound EDI transactions:
retrieves processing rules defined for the transaction and trading
partner
applies trading partner location cross reference
extracts information from the Oracle Applications database into
EDI Gateway interface tables
applies code conversion to Oracle Applications internal data to
derive external data
creates a data file that via the EDI translator become the EDI
document
updates the Oracle Applications database that the EDI document
has been extracted
Prerequisites
Create the outbound directory and update the INIT.ORA file. See:
"
To run the extract programs for outbound transactions:

1.
Define the ECE: Output file path profile option. See: EDI Gateway
Profile Options: page 6 3.
2.
3.
Define code conversions.

See: Defining Code Conversion Categories: page 3 13, Assigning
Categories: page 3 14, and Defining Code Conversion Values:
page 3 18.
66
4.

File: page 5 2.
5.
From the Navigator, choose Extract Programs.
See Also
Submitting a Request, Oracle Applications Users Guide, Release 10SC
Running the EDI Ship Notice / Manifest Outbound Extract Program:
page 8 79
Running the EDI Application Advice Outbound Extract Program: page
83
Running the EDI Invoice Outbound Extract Program: page 8 10
Running the EDI Purchase Order Outbound Extract Program: page
8 59
Running the EDI Outbound Purchase Order Change Request Extract
Program: page 8 69
Running the EDI Outbound Planning and Shipping Schedule Extract
Program: page 8 51
Running the EDI Payment Order / Remittance Advice Outbound
Extract Program: page 8 22
Transactions: page 4 1
67
Viewing the Status of Concurrent Programs

"
To view the status of your concurrent programs:

H
Choose View My Requests from the Help menu of the Submit

Requests window and identify your request for inbound or
outbound transactions.
Or, choose Requests from the Navigator to open the Concurrent
Requests Summary window and find the request ID corresponding
to your inbound and / or outbound request.
See: Submitting a Request, Oracle Applications Users Guide, Release
11
68
Data File Definition Format Legend

The data file definition format is described in the following table:
Attention: The Data File Definitions for individual transactions are

available only in the online HTML version of this Users Guide.
Navigate to the Inbound Transactions or Outbound Transactions
sections (as appropriate) and click on the link to the Data File
Definition you want to examine.
Column
Description
Field Description Data element description
Category The associated Code Conversion Category for general code

conversion. You may define your own code conversion category for
similar data.
Record Record numbers assigned by the EDI Gateway.
Format Attribute of the Data:

(Char or Varchar2) is alphanumeric characters.
(Number) is numeric.
(Date) for date format YYYYMMDD HHMMSS, where, for the date
portion, YYYY indicates the four digit year (1997, not 97), MM is
month, and DD is day. The time portion, HHMMSS, where HH
indicates hours, MM indicates minutes, and SS indicates seconds.
The time portion is 000000 if not needed. (Note the space between
date and time.)
Position Relative position among the business data within the given record,
starting in position 101.
Width Data element width. This data is likely to be shorter than data
defined in the Oracle Application to align the data with the
standards.
Start Starting position of the data within the given record.
Application Table For outbound transactions, application table is the source table of the
Oracle data from which the data is extracted. For inbound
transactions, the table is the interim interface table of the Oracle
application open interface (API) to receive the data from the EDI
Gateway.
Application For outbound transactions, application column is the source column
Column of the Oracle data within the Application Table. For inbound
transactions, the application column is the column within the
interim Application Table of the Oracle application open interface
(API) to receive the data.
69
6 10
]
CHAPTER
T
his chapter describes the Oracle EDI Gateway inbound

transactions:
Inbound Invoice (810/INVOIC): page 7 2
Inbound Price / Sales Catalog (832/PRICAT): page 7 6
Inbound Response to Request for Quote (843/QUOTES): page
7 10
Inbound Purchase Order (850/ORDERS): page 7 19
Inbound Ship Notice / Manifest (856/DESADV): page 7 27
Inbound Shipping and Billing Notice (857): page 7 30
71
Inbound Invoice (810 / INVOIC)

Use this transaction to import supplier invoices into your Oracle
Payables system for manual or electronic payment. Using the Payables
Open Interface, you can accomplish highvolume invoice import
complete with all standard online invoice entry features, including
purchase order matching, invoice approval, and invoice batch
processing.
Application(s)
accessed
Oracle Payables
Application Open Payables Open Interface

Interface(s)
ASC X12
Transaction
810
EDIFACT
Message
INVOIC
Prerequisite Optional Setup in Oracle Payables

You can optionally set up an Invoice Hold Reason unique to the this
transaction. All invoices being imported into Payables may be placed
on hold using the unique Invoice Hold Reason. This may be useful
during implementation of a new trading partner to separate electronic
invoices from other invoices in your Payables system. To define an
invoice hold reason, use the Invoice Approvals window. See: Invoice
Approvals, Oracle Payables Users Guide, Release 11.
Interface Tables
The following tables appear in the Interface File Definition window for
this transaction. These tables are populated by the EDI Gateway import
program and the data processed by the Payables Open Interface Import
API. Valid data are written to the application tables. Erroneous data are
marked in the Payables database for future error reporting and
correction.
The same tables appear in the Assign Categories window, under View
Name, for this transaction. Columns within these tables are identified as
candidates for code conversion.
AP_INVOICES_INTERFACE
AP_INVOICE_LINES_INTERFACE
72
Error Detection, Reporting, Correction, and Recovery

See the Oracle Financials Open Interfaces Manual, Release 11 for details
regarding the Payables Open Interface table layout and import program
business rules for validation, defaults, and derivations.
Use Oracle Payables Open Interface Report to review potential errors.
You have the option on rejected invoices to review the errors and make
corrections. You can then validate again, or enable the trading partner
to receive the application advice transaction (ADVO) for the invoice to
notify them of the error. The trading partner is expected to resend the
corrected invoice.
See Also
Running the EDI Invoice Inbound Program: page 7 3
Creating Electronic Payments, Oracle Payables Users Guide, Release 11
Running the EDI Invoice Inbound Program

Prerequisites
Define the ECE: Inbound file path profile option. See: EDI Gateway
Define trading partner relationships and enable EDI transactions for

the trading partner. See: Define Trading Partner Data: page 2 9.
Define code conversions. See: Defining Code Conversion

Categories: page 3 13, Assigning Categories: page 3 14, and
Defining Code Conversion Cross Reference Values: page 3 18.
"
To run the EDI Invoice inbound program:

1.
Navigate to the Import Program window.
2.
Select Request to submit an individual request.
3.
Select the EDI Invoice Inbound request.
4.
Open the parameters window.
73
5.
Enter the inbound data file or accept the default.
6.
In the Execute Open Interface field,

enter Y to initiate the Payables Open Interface Import program
using the default parameter values.
enter N to initiate the Payables Open Interface.
7.
Enter the following parameters:

Source: (required) Select EDI Gateway or the source you defined.
Group: (optional) Enter a code to segregate data from the same
source to improve the performance of the Payables Open Interface
Import program. You may want to use a succession of numeric
values to identify the groups (1,2,3,4).
Batch Name: (required) If using batch control, enter a name to be
assigned to the batch of invoices to be imported. The Batch Name
may be used in the outbound Payment Order/Remittance Advice
transaction (ASC X12 820 or EDIFACT PAYORD/REMADV) to
reference a batch of invoices identified for electronic payment.
Hold Name: (optional) Enter an Invoice Hold Reason if you want to
place all invoices to be imported on hold for review or audit
purposes.
Hold Reason: (optional) Accept default Hold Reason Description or
overwrite the default.
GL Date: (optional) Enter GL date in an open period to be applied to
imported invoices.
Purge After Import: (optional) Enter Yes if you wish to delete the
invoice data from the Payables Open Interface tables after the data
has been imported into Oracle Payables.
8.
When finished, choose OK in the Parameters window.
9.
Enter completion options.
10. Enter schedule options to schedule the request.

11. Choose Submit and make a note of the Request ID returned.
74
Attention: The Data File Definition for this transaction is available

only in the online HTML version of this Users Guide. Navigate to
this samenamed section there and click on the link to the Data File
Definition.
See Also
Inbound Invoice: page 7 2
75
Inbound Price / Sales Catalog (832 / PRICAT)

Use this transaction to import supplier catalogs into your Purchasing
system as Catalog Quotes or Purchase Agreements to support online
catalog lookup and purchase order placement. During the import
process, supplier sourcing rules may be added to Oracle Purchasing,
and the Oracle Inventory item master may be updated with catalog item
changes or new catalog items.
Application(s)
accessed
Oracle Purchasing, Oracle Inventory
Applications
Open Interface(s)
Purchasing Document Open Interface, Item Open

Interface
ASC X12
Transaction
832
EDIFACT
Message
PRICAT
Prerequisite Setup in Oracle Purchasing

Allow updating of item description in Purchasing Options. See:
Defining Control Options, Oracle Purchasing Users Guide, Release 11.
Prerequisite Setup in Oracle Inventory

Allow the updating of item status codes at the site level. Set the INV:
Default Item Status profile to Active. See: Oracle Inventory Profile
Options, Oracle Inventory Users Guide, Release 11 and Receiving Catalog
Information Electronically, Oracle Purchasing Users Guide, Release 11.
Interface Tables
program which are then processed by the Purchasing Document Open
Interface API. Valid data are written to the application tables.
Erroneous data are marked for correction.
76
Name, for this transaction. Columns within these tables are identified as
PO_HEADER_INTERFACE
PO_LINES_INTERFACE

See the Oracle Manufacturing and Distribution Open Interfaces Manual,
Release 11 for details regarding the Purchasing Document Open Interface
table layout and import program business rules for validation, defaults,
and derivations.
See Also
Running the EDI Price / Sales Catalog Inbound Program: page 7 7
Inbound Price / Sales Catalog Data File Organization: page 7 14
Running the EDI Price / Sales Catalog Inbound Program

Prerequisites


Defining Code Conversion Values: page 3 18.
"
To run the EDI Price / Sales Catalog inbound program:

1.
2.
3.
Select the EDI Catalog Inbound request.
77
4.
Open the Parameters window.
5.
6.

enter Y to initiate the Purchasing Document Open Interface
program using the default parameter values.
enter N to initiate Purchasing Document Open Interface in
Purchasing.
7.

Default Buyer: (required) Enter the default buyer name for the
Price/Sales Catalog or Response to RFQ.
Document Type: Required, valid options are Blanket and Quotation.
The option of Blanket directs Purchasing to create a Blanket
Agreement for the document to be imported. The option of
Quotations directs Purchasing to create a Catalog Quotation for the
document to be imported.
Document Sub Type: (optional) Used with document type of
Quotation to indicate a document sub type of Catalog
Quotation for the Price/Sales Catalog or Response to RFQ to be
imported. The document sub type of Bid Quotation is invalid for
the transaction.
Create or Update Item: Required, used with the Price/Sales Catalog
or Response to RFQ to indicate whether you wish to update the item
master with catalog item changes or add catalog items to the item
master.
Create Sourcing Rules: (required) Indicate Yes or No on whether
supplier sourcing rules should be created automatically during the
Price/Sales Catalog and Response to RFQ import process.
Release Generation Method: (optional) Used when Document Type is
set to Blanket and Create Sourcing Rules is set to Yes. Select from
the following three blanket release methods:
Release using Autocreate: allows you to use the Purchasing
Autocreate function to convert purchase requisitions into blanket
releases for blanket purchase orders.
Automatic Release: allows Purchasing to automatically generate
approved blanket releases for items that are autosourced to a
single supplier.
Automatic Release with Review: allows Purchasing to
automatically generate releases and forwards them for approval.
78
Commit Interval: (required) Enter a numeric value or accept the

default value of 100 representing the number of records processed
before committing the data to the database.
Batch ID: (optional) Enter a valid batch ID which corresponds to
the RUN ID in EDI Gateway.
Approval Status: (optional) Enter desired status of Approved or
Incomplete for Blanket Agreement and Quotation created by
Purchasing for the Price/Sales Catalog or Response to RFQ to be
imported.
8.
9.
Enter schedule options to schedule the request.
10. Enter completion options.

See Also
Inbound Price / Sales Catalog: page 7 6
Inbound Price / Sales Catalog and Response to Request for Quote Data
File Organization: page 7 14
79
Inbound Response to Request for Quote (843 / QUOTES)

Use this transaction to import supplier responses to your request for
quotes into your Purchasing system to support the procurement process.
Application(s)
accessed
Oracle Purchasing
Application Open Purchasing Document Open Interface

Interface(s)
ASC X12
Transaction
843
EDIFACT
Message
QUOTES

Allow updating of item description in Purchasing Options. See:
Defining Control Options, Oracle Purchasing Users Guide, Release 11.
Prerequisite Setup in Oracle Inventory

Allow the updating of item status codes at the site level. Set the INV:
Default Item Status profile to Active. See: Oracle Inventory Profile
Options, Oracle Inventory Users Guide, Release 11 and Receiving Catalog
Information Electronically, Oracle Purchasing Users Guide, Release 11.
Interface Tables
program which are then processed by the Purchasing Document Open
Interface API. Valid data are written to the application tables.
Erroneous data are marked for correction.
These tables are also used in assigning cross references between
customers and suppliers. Each table contains some columns that require
cross references. You can view those columns in the Assign Categories
window, under View Name, for this transaction.
PO_HEADER_INTERFACE
PO_LINES_INTERFACE
7 10

Release 11 for details regarding the Purchasing Document Open Interface
table layout and import program business rules for validation, defaults,
and derivations.
See Also
Running the EDI Response to Request for Quote Inbound Program:
page 7 20
Running the EDI Response to Request for Quote Inbound Program

Prerequisites



File: page 5 2.
"
To run the EDI Response to Request for Quote inbound program:

1.
2.
3.
Select the EDI Response to RFQ request.
4.
5.
7 11
6.

enter Y to initiate the Purchasing Document Open Interface
program using the default parameter values.
enter N to initiate Purchasing Document Open Interface in
Purchasing.
7.

Default Buyer: (required) Enter the default buyer name for the
Price/Sales Catalog or Response to RFQ.
Document Type: (required) Valid options are Blanket and Quotation.
The option of Blanket directs Purchasing to create a Blanket
Agreement for the document to be imported. The option of
Quotations directs Purchasing to create a Catalog Quotation for the
document to be imported.
Document Sub Type: (optional) Used with document type of
Quotation to indicate a document sub type of Catalog
Quotation for the Price/Sales Catalog or Response to RFQ to be
imported. The document sub type of Bid Quotation is invalid for
the transaction.
Create or Update Item: (required) Used with the Price/Sales Catalog
or Response to RFQ to indicate whether you wish to update the item
master with catalog item changes or add catalog items to the item
master.
Create Sourcing Rules: (required) Indicate Yes or No on whether
vendor sourcing rules should be created automatically during the
Price/Sales Catalog and Response to RFQ import process.
Release Generation Method: (optional) Used when Document Type is
set to Blanket and Create Sourcing Rules is set to Yes. Select from
the following three blanket release methods:
a. Release using Autocreate: allows you to use the Purchasing
Autocreate function to convert purchase requisitions into blanket
releases for blanket purchase orders.
b. Automatic Release: allows Purchasing to automatically
generate approved blanket releases for items that are autosourced
to a single supplier.
c. Automatic Release with Review: allows Purchasing to
automatically generate releases and forwards them for approval.
Commit Interval: (required) Enter a numeric value or accept the
default value of 100 representing the number of records processed
before committing the data to the database.
7 12
Batch ID: (optional) Enter a valid batch ID which corresponds to

the RUN ID in EDI Gateway.
Approval Status: (optional) Enter desired status of Approved or
Incomplete for Blanket Agreement and Quotation created by
Purchasing for the Price/Sales Catalog or Response to RFQ to be
imported.
8.
9.
10. Enter the completion options.

See Also
Inbound Response to Request for Quote: page 7 10
7 13
Inbound Price / Sales Catalog and Response to Request for Quote Data File
Organization
The following tables provide a summary description of the data file.

Definition.
Record Occurrences within the Transaction

Records
Content
Occurrences
EDI Gateway Control Record
Only one record occurrence per

transaction
10001999
Transaction Header
Only one set of records per

price/sales catalog
20002999
Transaction Item
One set of item records per item

within the transaction.
0010
Record Summary
Seq.
Type of Data
Data Level
Record
Number
Notes
Control Record
CONTROL
0010
Transaction Identification
TRANSACTION HEADER
1000
Currency, Payment Terms
TRANSACTION HEADER
1010
FOB, Carrier, Freight Terms
TRANSACTION HEADER
1020
Miscellaneous Header Data
TRANSACTION HEADER
1030
Action Type, Group Code
TRANSACTION HEADER
1040
Note to Vendor
TRANSACTION HEADER
1050
Note to Receiver
TRANSACTION HEADER
1060
Comments
TRANSACTION HEADER
1070
10
Ship to Address
TRANSACTION HEADER
1100
11
Bill to Address
TRANSACTION HEADER
1110
7 14
Seq.
Type of Data
Data Level
Record
Number
Notes
12
Vendor Data
TRANSACTION HEADER
1120
13
Header Flex Fields 14, Context
TRANSACTION HEADER
1200
Flexfields
14
Header Flex Fields 59
TRANSACTION HEADER
1210
Flexfields
15
TRANSACTION HEADER
1220
Flexfields
16
TRANSACTION HEADER
1230
Flexfields
17
Item Identification
TRANSACTION ITEM
2000
18
Quantity, Description
TRANSACTION ITEM
2010
19
Prices, Dates
TRANSACTION ITEM
2020
20
Payment Terms (Item Level)
TRANSACTION ITEM
2030
21
FOB, Carrier, Freight Terms (Item Level)
TRANSACTION ITEM
2040
22
Hazardous data, Weight,

Volume, Lead Time
TRANSACTION ITEM
2050
23
Tax
TRANSACTION ITEM
2060
24
Note to Vendor (Item Level)
TRANSACTION ITEM
2070
26
Ship To Data (Item Level)
TRANSACTION ITEM
2100
26
Line Level Flex Field 14, Context
TRANSACTION ITEM
2200
Flexfields
27
Line Level Flex Field 59
TRANSACTION ITEM
2210
Flexfields
28
TRANSACTION ITEM
2220
Flexfields
29
TRANSACTION ITEM
2230
Flexfields
30
Shipment Flex Field 14, Context
TRANSACTION ITEM
2240
Flexfields
31
Shipment Flex Field 59
TRANSACTION ITEM
2250
Flexfields
32
TRANSACTION ITEM
2260
Flexfields
33
TRANSACTION ITEM
2270
Flexfields
34
Item Level Flex Field 14, Context
TRANSACTION ITEM
2280
Flexfields
35
Item Level Flex Field 59
TRANSACTION ITEM
2290
Flexfields
36
TRANSACTION ITEM
2300
Flexfields
37
TRANSACTION ITEM
2310
Flexfields
7 15
Transactionspecific Data in the Common Key Positions 1100
Records
Content
Occurrences
125
TP_CD
Trading Partner Code as defined in the

EDI Translator
2647
DOC
Transaction Identification from trading

partner
4869
ITEM
Supplier Item Number
7091
(blank)
Not Used
9295
(varies)
Record Number
9697
(varies)
Record Layout
98100
(varies)
Record Layout Qualifier
Transactionspecific Data in the Common Key Positions 1100 Per Record

Seq.
Record
TP_CD
Reference 1
Reference
2
Reference
3
Record
Number
Record
Layout
Record
Qualifier
Length
25
22
22
22
Position
125
2647
4869
7091
9295
9697
98100
Control Record
TP_CD
0010
CT
CTL
Transaction
Identification
TP_CD
DOC
1000
HA
HD1
Currency,
Payment Terms
TP_CD
DOC
1010
HB
HD2
FOB, Carrier,
Freight Terms
TP_CD
DOC
1020
HC
HD3
Miscellaneous
Header Data
TP_CD
DOC
1030
HD
HD4
Action Type,
Group Code
TP_CD
DOC
1040
HE
HD5
Note to Vendor
TP_CD
DOC
1050
NT
HVN
Note to Receiver
TP_CD
DOC
1060
NT
HRC
Comments
TP_CD
DOC
1070
NT
HCM
10
Ship to Address
TP_CD
DOC
1100
AD
ST1
11
Bill to Address
TP_CD
DOC
1110
AD
BT1
7 16
Seq.
Record
TP_CD
Reference 1
Reference
2
Reference
3
Record
Number
Record
Layout
Record
Qualifier
12
Vendor Data
TP_CD
DOC
1120
VN
VN1
13
Header Flex
Fields 14,
context
TP_CD
DOC
1200
A1
HD1
14
Header Flex
Fields 59
TP_CD
DOC
1210
A2
HD2
15
Header Flex
Fields 1014
TP_CD
DOC
1220
A2
HD3
16
Header Flex
Fields 15
TP_CD
DOC
1230
A2
HD4
17
Item
Identification
TP_CD
DOC
ITEM
2000
IA
IT1
18
Quantity,
Description
TP_CD
DOC
ITEM
2010
IB
IT2
19
Prices, Dates
TP_CD
DOC
ITEM
2020
IC
IT3
20
Payment Terms
(Item Level)
TP_CD
DOC
ITEM
2030
ID
IT4
21
FOB, Carrier,
Freight Terms
(Item Level)
TP_CD
DOC
ITEM
2040
IE
IT5
22
Hazardous data,
Weight,
Volume, Lead
Time
TP_CD
DOC
ITEM
2050
IF
IT6
23
Tax
TP_CD
DOC
ITEM
2060
IG
IT7
24
Note to Vendor
(Item Level)
TP_CD
DOC
ITEM
2070
NT
DVN
25
Ship To Data
(Item Level)
TP_CD
DOC
ITEM
2100
AD
SH2
26
Line Level Flex

Field 14, Context
TP_CD
DOC
ITEM
2200
A1
LN1
27
Line Level Flex

Field 59
TP_CD
DOC
ITEM
2210
A2
LN2
28
Line Level Flex

Field 1014
TP_CD
DOC
ITEM
2220
A2
LN3
29
Line Level Flex

Field 15
TP_CD
DOC
ITEM
2230
A2
LN4
30
Shipment Flex
Field 14, Context
TP_CD
DOC
ITEM
2240
A1
SH1
31
Shipment Flex
Field 59
TP_CD
DOC
ITEM
2250
A2
SH2
7 17
Seq.
Record
TP_CD
Reference 1
Reference
2
Reference
3
Record
Number
Record
Layout
Record
Qualifier
32
Shipment Flex
Field 1014
TP_CD
DOC
ITEM
2260
A2
SH3
33
Shipment Flex
Field 15
TP_CD
DOC
ITEM
2270
A2
SH4
34
Item Level Flex

Field 14, Context
TP_CD
DOC
ITEM
2280
A1
IT1
35
Item Level Flex

Field 59
TP_CD
DOC
ITEM
2290
A2
IT2
36
Item Level Flex

Field 1014
TP_CD
DOC
ITEM
2300
A2
IT3
37
Item Level Flex

Field 15
TP_CD
DOC
ITEM
2310
A2
IT4
7 18
Inbound Purchase Order (850 / ORDERS)

Use this transaction to import customer orders into Oracle Order Entry
for order fulfillment.
Application(s)
accessed
Oracle Order Entry
Application Open OrderImport Open Interface

Interface(s)
ASC X12
Transaction
850
EDIFACT
Message
ORDERS
Prerequisite Setup in Oracle Order Entry

Use the OrderImport program to import customer purchase orders into
your system as a sales order.
EDI Gateway assumes Order Entry is fully implemented. Validation is
based on the same business rules applied to manually entered sales
orders.
Interface Tables
program. The data is then processed by the application open interface.
Valid data is written to the application tables. Erroneous data is marked
for corrective action. The same tables appear in the Assign Categories
window, under View Name, for the transaction. Columns within these
tables are identified as candidates for code conversion.
SO_HEADER_INTERFACE
SO_LINES_INTERFACE
See Also
Running the EDI Purchase Order Inbound Program: page 7 20
Inbound Purchase Order Data File Organization: page 7 22
7 19
Running the EDI Purchase Order Inbound Program

Prerequisites



File: page 5 2.
"
To run the EDI PO inbound program:

1.
Navigate to the Import Programs window.
2.
3.
Select the EDI PO Inbound request.
4.
Enter the inbound data file name or accept the default.
5.
Open the parameters window.
6.

enter Y to initiate the OrderImport program using the default
parameter values. The default source is EDI.
enter N to initiate OrderImport and enter the parameters Source
and Number of Instances.
7.
8.
9.
7 20
See Also
Inbound Purchase Order: page 7 19
Inbound Purchase Order Data File Organization: page 7 22
7 21
Inbound Purchase Order Data File Organization

The following tables provide a summary description of the data file.

Definition.
Record Summary
Seq.
Data
Data Level
Record
Number
Control Record
CONTROL
0010
Basic Purchase
Order Header
PURCHASE ORDER HEADER
1000
Payment Terms,
Other PO Header
Data
1010
Basic Purchase
Order Header
1020
Purchase Order
Flexfields
10401070
Ship to
Address/Code
(header level)
1190
Ship to Contacts
(header level)
1200
10
Bill to
Address/Code
1210
Note
11
Bill to Contact
1220
12
Buyer Name
1230
13
Basic Purchase
Order Header
Data
1240
14
Header Level
Shipping
Instructions
1250
15
Basic Purchase
Order Header
Data
1260
Table 7 5
7 22
Flexfields
Seq.
Data
Data Level
Record
Number
Note
16
Extension Tables:
Purchase Order
Header Data
1900
17
Basic Item Data
PURCHASE ORDER ITEM
2000
18
Basic Item Data in PURCHASE ORDER ITEM

Item Segments
(26)
2120
19

Item Segments
(711)
2130
20

Item Segments
(1216)
2140
21

Item Segments
(1720)
2150
22
Pricing Flexfields
PURCHASE ORDER ITEM
21602190
23
Basic Item Data
PURCHASE ORDER ITEM
2200
24
Purchase Order
Item Flexfields
PURCHASE ORDER ITEM
30103040
25
Ship to Address
(Item Level)
PURCHASE ORDER ITEM
3050
26
Ship to Contact
(Item Level)
PURCHASE ORDER ITEM
3060
28
Extension Tables:
Purchase Order
Item Data
PURCHASE ORDER ITEM
3900
(Custom)
Flexfields
Flexfields
(Custom)
Table 7 5
Transactionspecific Data in the Common Key
Position
Code
Content
125
TP_CD
Trading Partner Code as defined in the EDI

Translator
2647
PO
Purchase order number
Table 7 6
7 23
Position
Code
Content
4869
ITEM
Purchase order line number
7091
(blank)
Table 7 6
Seq.
Data
Trading
Partner
Reference 1
Reference 2
Reference 3
Record
Number
Record
Layout
Record Layout
Qualifier
Length
25
22
224
22
Position
125
2647
4869
7091
9295
9697
98100
Control
Record
TP_CD
PO
0010
CT
CTL
Basic
Purchase
Order
Header
TP_CD
PO
1000
PO
PO1
Payment
Terms,
Other PO
Header
Data
TP_CD
PO
1010
PO
PO2
10
Basic
Purchase
Order
Header
TP_CD
PO
1020
PO
PO3
11
Purchase
Order
Flexfields
TP_CD
PO
1040
A1
PO1
12
Purchase
Order
Flexfields
TP_CD
PO
1050
A2
PO2
13
Purchase
Order
Flexfields
TP_CD
PO
1060
A2
PO3
14
Purchase
Order
Flexfields
TP_CD
PO
1070
A2
PO4
15
Ship to
Address/co
de
TP_CD
PO
1190
AD
ST1
7 24
Seq.
Data
Trading
Partner
Reference 1
Reference 2
Reference 3
Record
Number
Record
Layout
Record Layout
Qualifier
16
Ship to
Contacts
TP_CD
PO
1200
CN
ST1
17
Bill to
Address/C
ode
TP_CD
PO
1210
AD
BT1
18
Bill to
Contact
TP_CD
PO
1220
CN
BT1
19
Buyer
Name
TP_CD
PO
1230
PO
PO4
20
Basic
Purchase
Order
Header
TP_CD
PO
1240
PO
PO5
21
Shipping
Instruction
(Header
level)
TP_CD
PO
1250
PO
PO6
22
Basic
Purchase
Order
Header
TP_CD
PO
1260
PO
PO7
23
Extension
Tables:
Purchase
Order
Header
Data
TP_CD
PO
1900
24
Basic Item
Data
TP_CD
PO
ITEM
2000
IT
IT1
25
Item Data
in Segments
(26)
TP_CD
PO
ITEM
2120
IT
IT2
26
Item Data
in Segments
(711)
TP_CD
PO
ITEM
2130
IT
IT3
27
Item Data
in Segments
(1216)
TP_CD
PO
ITEM
2140
IT
IT4
28
Item Data
in Segments
(1720)
TP_CD
PO
ITEM
2150
IT
IT5
(Custom)
7 25
Seq.
Data
Trading
Partner
Reference 1
Reference 2
Reference 3
Record
Number
Record
Layout
Record Layout
Qualifier
29
Pricing
Flexfields
TP_CD
PO
ITEM
2160
A1
PR1
30
Pricing
Flexfields
TP_CD
PO
ITEM
2170
A2
PR2
31
Pricing
Flexfields
TP_CD
PO
ITEM
2180
A2
PR3
32
Pricing
Flexfields
TP_CD
PO
ITEM
2190
A2
PR4
33
Basic Item
Data
TP_CD
PO
ITEM
2200
IT
IT6
34
Purchase
Order Item
Flexfields
TP_CD
PO
ITEM
3010
A1
IT1
35
Purchase
Order Item
Flexfields
TP_CD
PO
ITEM
3020
A2
IT2
36
Purchase
Order Item
Flexfields
TP_CD
PO
ITEM
3030
A2
IT3
37
Purchase
Order Item
Flexfields
TP_CD
PO
ITEM
3040
A2
IT4
38
Ship To
Address/C
ode (Item
Level)
TP_CD
PO
ITEM
3050
AX
ST2
39
Ship To
Contact
(Item Level)
TP_CD
PO
ITEM
3060
CN
ST2
41
Extension
Tables:
Purchase
Order Item
Data
TP_CD
PO
7 26
3900
(Custom)
Inbound Ship Notice / Manifest (856 / DESADV)

Use this transaction to import supplier ship notices into your Purchasing
system as a prereceipt. The electronic ship notice provides a shipment
identifier to facilitate the receipt of the physical goods.
Application(s)
accessed
Oracle Purchasing
Application Open Receiving Open Interface

Interface(s)
ASC X12
Transaction
856
EDIFACT
Message
DESADV

Receiving Options: ASN Control: Action (action associated with RCV:
Show ASN Matched POs profile)
Interface Tables
program and processed by the Receiving Open Interface API. Valid data
are written to the application tables. Erroneous data are marked for
correction.
Name, for the transaction. Columns within these tables are identified as
RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE

Release 11 for details regarding the Receiving Open Interface table layout
and import program business rules for validation, defaults, and
derivations.
Use this transaction to import supplier responses to your RFQs into
your Purchasing system to support the procurement process.
7 27
See Also
Running the EDI Ship Notice / Manifest Inbound Program: page 7 28
Inbound Ship Notice / Manifest and Shipping and Billing Notice Data
Running the EDI Ship Notice / Manifest Inbound Program

Prerequisites



File: page 5 2.
"
To run the EDI Ship Notice / Manifest inbound program:

1.
2.
3.
Select the EDI Advance Ship Notice Inbound request.
4.
5.
6.

enter Y to initiate the Receiving Open Interface program
immediately. There are no program parameters.
enter N to initiate the Receiving Open Interface program in
Purchasing. There are no program parameters.
7.
7 28
8.
9.
Enter the completion options.
See Also
Inbound Ship Notice / Manifest: page 7 27
7 29
Inbound Shipping and Billing Notice (857)

Use this transaction to import supplier ship notices and invoices into
your Purchasing and Payables system as a prereceipt and unapproved
invoice.
Similar to the Ship Notice/Manifest transaction, the electronic ship
notice provides a shipment identifier to facilitate the receipt of the
physical goods and the creation of the unapproved invoice in a single
EDI transaction.
Application(s)
accessed
Oracle Purchasing, Oracle Payables
Application Open Receiving Open Interface

Interface(s)
ASC X12
Transaction
857
EDIFACT
Message
This transaction has no equivalent in EDIFACT.

None.
Prerequisite Setup in Oracle Payables

Supplier site must be defined as a Pay on Receipt site.
Interface Tables
program which are then processed by the Receiving Open Interface API.
Valid data are written to the application tables. Erroneous data are
marked for correction.
Name, for the transaction. Columns within these tables are identified as
RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE
7 30

See the Oracle Manufacturing and Distribution Implementation Manual,
Release 11 for details regarding the Receiving Open Interface table layout
and import program business rules for validation, defaults, and
derivations.
See Also
Running the EDI Shipping and Billing Notice Inbound Program: page
7 31
Running the EDI Shipping and Billing Notice Inbound Program

Prerequisites



File: page 5 2.
"
To run the EDI Shipping and Billing Notice inbound program:

1.
2.
3.
Select EDI Shipment and Billing Notice request.
4.
5.
7 31
6.

enter Y to initiate the Receiving Open Interface program
immediately. There are no program parameters.
enter N to initiate the Receiving Open Interface program in
Purchasing. There are no program parameters.
7.
8.
9.
Enter the completion options.
See Also
Inbound Shipping and Billing Notice: page 7 30
7 32
Inbound Ship Notice / Manifest and Shipping and Billing Notice Data File
Organization
The following tables provide a summary description of the data file:

Definition.

Records
Content
Occurrences
00100070
EDI Gateway Control

Records
Only one record occurrence

per transaction
10001900
Shipment Notice Header

Records

per transaction
20003900
Shipment Notice Item

Records
One set of records per item

within the Shipment Notice
header
Record Summary
Seq.
Type of Data
Data Level
Record
(Pos. 9295)
Common Control
Record
CONTROL
0010
Shipment Notice
Basic Header
SHIPMENT NOTICE HEADER
1000
Carrier, Weights,
Packaging
1010
Shipment Method SHIPMENT NOTICE HEADER

of Payment
1020
Currency, Tax,
Payment Terms
1030
Allowances/Char
ges (Freight)
1040
Note
Table 7 9
7 33
Seq.
Type of Data
Data Level
Record
(Pos. 9295)
Note
Hazardous
Material, Special
Handling
1050
Header Note
1090
Vendor
Address/Code
1100
10
Destination
Address/Code
1120
11
Destination
Contact
1130
12
Shipment Header
Flexfields
12001230
13
Basic Item Data
SHIPMENT NOTICE ITEM
2000
14
Hazardous
Material Codes
2010
15
Currency, Tax
(Item Level)
2020
16
Notes
2030
17
Shipment Line
Flexfields
21002130
Flexfields
18
Transaction
Flexfields
21402170
Flexfields
19
Destination
Address
3000
20
Destination
Location
3020
Flexfields
Table 7 9
Position
Code
Content
125
TP_CD

Translator
2647
SHIPMENT
Shipment Number
Table 7 10
7 34
Position
Code
Content
4869
LINE
Item Number
7091
(blank)
N/A
9295
(varies)
Record Number
9697
(varies)
Record Layout
98100
(varies)
Table 7 10

Seq.
Data
TP_CD
Reference 1
Reference 2
Reference 3
Record
Number
Record
Layout
Record Layout
Qualifier
25
22
22
22
4869
7091
Length
125
2647
9295
9697
98100
Common
Control
Record
Position
TP_CD
SHIPMENT
0010
CT
CTL
Shipment
Notice
Basic
Header
TP_CD
SHIPMENT
1000
L1
DL1
Carrier,
Weights,
Packaging
TP_CD
SHIPMENT
1010
L2
DL2
Shipment
Method of
Payment
TP_CD
SHIPMENT
1020
L3
DL3
Currency,
Tax,
Payment
Terms
TP_CD
SHIPMENT
1030
L4
DL4
Allowances
/Charges
(Freight)
TP_CD
SHIPMENT
1040
L5
DL5
Hazardous
Material,
Special
Handling
TP_CD
SHIPMENT
1050
HZ
HZ1
7 35
Seq.
Data
TP_CD
Reference 1
Reference 2
Reference 3
Record
Number
Record
Layout
Record Layout
Qualifier
Header
Note
TP_CD
SHIPMENT
1090
NT
NH1
Vendor
Address/C
ode
TP_CD
SHIPMENT
1100
AI
SU
10
Destination
Address/C
ode
TP_CD
SHIPMENT
1120
AX
ST
11
Destination
Contact
TP_CD
SHIPMENT
1130
CN
ST
12
Shipment
Header
Flexfields
TP_CD
SHIPMENT
1200
A1
SH1
13
Shipment
Header
Flexfields
TP_CD
SHIPMENT
1210
A2
SH2
14
Shipment
Header
Flexfields
TP_CD
SHIPMENT
1220
A2
SH3
15
Shipment
Header
Flexfields
TP_CD
SHIPMENT
1230
A2
SH4
16
Basic Item
Data
TP_CD
SHIPMENT
LINE
2000
l1
IT1
17
Hazardous
Material
Codes
TP_CD
SHIPMENT
LINE
2010
I2
IT2
18
Currency,
Tax (Item
Level)
TP_CD
SHIPMENT
LINE
2020
I3
IT3
19
Notes
TP_CD
SHIPMENT
LINE
2030
NT
ND1
20
Shipment
Line
Flexfields
TP_CD
SHIPMENT
LINE
2100
A1
SL1
21
Shipment
Line
Flexfields
TP_CD
SHIPMENT
LINE
2110
A2
SL2
22
Shipment
Line
Flexfields
TP_CD
SHIPMENT
LINE
2120
A2
SL3
7 36
Seq.
Data
TP_CD
Reference 1
Reference 2
Reference 3
Record
Number
Record
Layout
Record Layout
Qualifier
23
Shipment
Line
Flexfields
TP_CD
SHIPMENT
LINE
2130
A2
SL4
24
Order Line
Flexfields
TP_CD
SHIPMENT
LINE
2140
A1
RC1
25
Order Line
Flexfields
TP_CD
SHIPMENT
LINE
2150
A2
RC2
26
Order Line
Flexfields
TP_CD
SHIPMENT
LINE
2160
A2
RC3
27
Order Line
Flexfields
TP_CD
SHIPMENT
LINE
2170
A2
RC4
28
Destination
Address/C
ode
TP_CD
SHIPMENT
LINE
3000
AX
ST
29
Destination
Location
TP_CD
SHIPMENT
LINE
3020
CO
ST
7 37
7 38
CHAPTER
T
his chapter describes each outbound transaction and explains how

to extract the data to create the data file:
Outbound Application Advice (824/APERAK): page 8 2
Outbound Invoice (810/INVOIC): page 8 9
Outbound Payment Order / Remittance Advice (820/PAYORD,
REMADV): page 8 20
Outbound Planning Schedule (830/DELFOR): page 8 27
Outbound Shipping Schedule (862/DELJIT): page 8 47
Outbound Purchase Order (850/ORDERS): page 8 58
Outbound Purchase Order Change Request (860/ORDCHG):
page 8 67
Outbound Ship Notice / Manifest (856/DESADV): page 8 77
81
Outbound Application Advice (824 / APERAK)

Use this transaction to acknowledge transaction errors for the following
inbound transactions:
Invoice
Ship Notice/Manifest
Shipment and Billing Notice
The respective inbound transactions write data regarding errors
including the error message code, error message text and erroneous data
to the application advice tables in the EDI Gateway product. The
processing errors are reported to the trading partner using the
Application Advice transaction.
Application(s)
accessed
Oracle Purchasing, Oracle Payables
ASC X12
Transaction
824
EDIFACT
Message
APERAK
Prerequisite Set Up in Oracle Purchasing and Oracle Payables

There is no prerequisite set up in Oracle Purchasing or Oracle Payables.
However, Purchasing and Payables maintain application open interface
audit reports.
Interface Table, Extension Table, and View Names

The following tables and views appear in the Interface File Definition
window for this transaction. See: Changing the Data File: page 5 2.
Interface Tables
ECE_ADVO_DETAILS_INTERFACE
ECE_ADVO_HEADERS_INTERFACE
Extension Tables
Each extension table shares its name with a base interface table, except
for the trailing _X. You must define the columns for the extension
tables if you choose to use them. See: Extensible EDI Gateway
Architecture: page 9 1.
82
ECE_ADVO_DETAIL_INTERFACE_X
ECE_ADVO_HEADER_INTERFACE_X
Views
The following views appear in the Assign Categories window, under
View Name, for this transaction. Columns within these views are
identified as candidates for code conversion. See: Code Conversion:
page 3 1.
ECE_ADVO_DETAIL_V
ECE_ADVO_HEADERS_V (no conversion candidates listed)
See Also
Running the EDI Application Advice Outbound Extract Program: page
83
Running the EDI Application Advice Outbound Extract Program

Prerequisites
Define trading partner data and enable EDI transactions for the
trading partner. See: Define Trading Partner Data: page 2 9.


File: page 5 2.
"
To run the EDI application advice outbound extract program:

1.
Navigate to the Extract Program window.
2.
83
3.
Select the EDI Application Advice Outbound transaction.
4.
In the Parameters window, enter the following selection criteria:

Specify an output file name if not using the default.
Enter trading partner name.
Enter Response to Document to indicate which application advice
messages to extract related to which inbound transactions.
Enter the transaction date From and To.
Enter the first external reference relevant for the document name.
For example, enter ASN number for inbound Ship Notice /
Manifest or invoice number for inbound invoices.
Enter second external reference relevant for the document name.
For example, enter shipment number for inbound Ship Notice /
Manifest.
Enter the next external reference relevant for the document name.
Enter the next external reference relevant for the document name.
Enter next external reference relevant for the document name.
Enter next external reference relevant for the document name.
5.
6.
7.
8.
Choose Submit and make a note of the Request ID returned.
See Also
Outbound Application Advice: page 8 2
Oracle Payables, Oracle Payables Users Guide, Release 11
84
Outbound Application Advice Data File Organization

The data file produced by this transaction consists of two level of data:
header and details.
Each application advice contains one header record that applies to the
inbound document to be reported. The application advice header is
followed by one or more application advice lines representing each
unique error related to the document.
The output file is structured as follows:
Application advice header
Application advice detail
Application advice header
Summary Tables

Definition.

Records
Content
Occurrences
00100070
EDI Gateway Control Records

per transaction
10001999
Application Advice Header Records

per transaction
20002999
Application Advice Detail Records
One set of detail records per

error within the transaction.
85
Record Summary
Seq.
Type of Data
Data Level
Record
Number
Notes
Control Record
CONTROL
0010
Trading Partner Header Attributes
TRADING PARTNER
0020
Flexfields
Trading Partner Header Attributes
TRADING PARTNER
00300050
Flexfields
Advice Header External Reference 14
HEADER
1000
Advice Header External Reference 56
HEADER
1010
Advice Header Internal Reference 15
HEADER
1020
Advice Header Internal Reference 6
HEADER
1030
10
Trading Partner Address
HEADER
1040
11
Extension Table: Header Level
HEADER
1900
12
Advice Detail External Reference 14
DETAIL
2000
13
Advice Detail External Reference 56
DETAIL
2010
14
Advice Detail Internal Reference 15
DETAIL
2020
15
Advice Detail Internal Reference 6
DETAIL
2030
16
Advice Detail Data (Error)
DETAIL
2040
17
Advice Detail Data (Accepted)
DETAIL
2050
18
Extension Table: Detail Level
DETAIL
2900
(Custom)
(Custom)

Records
Content
Occurrences
125
TP_CD
Trading Partner Code as defined in the EDI Translator
2647
DOC
Related Document ID
4869
ERR_CNT
Error Counter
7091
(blank)
Not Used
9295
(varies)
Record Number
86
Records
Content
Occurrences
9697
(varies)
Record Layout
98100
(varies)

Seq.
Record
TP_CD
Reference
1
Reference
2
Reference
3
Record
Number
Record
Layout
Record
Qualifier
Length
25
22
22
22
Position
125
2647
4869
7091
9295
9697
98100
Control Record
TP_CD
0010
CT
CTL
Trading Partner
Header
Attributes
TP_CD
0020
A1
TH1
Trading Partner
Header
Attributes
TP_CD
00300050
A2
TH2
Advice Header
External
Reference 14
TP_CD
DOC
1000
HD
EX1
Advice Header
External
Reference 56
TP_CD
DOC
1010
HD
EX2
Advice Header
Internal
Reference 15
TP_CD
DOC
1020
HD
IN1
Advice Header
Internal
Reference 6
TP_CD
DOC
1030
HD
IN2
10
Trading Partner
Address
TP_CD
DOC
1040
AD
TP1
11
Extension Table:
Header Level
TP_CD
DOC
1900
(custom)
(custom)
12
Advice Detail
External
Reference 14
TP_CD
DOC
2000
DT
EX1
ERR_CNT
87
Seq.
Record
TP_CD
Reference
1
Reference
2
Reference
3
Record
Number
Record
Layout
Record
Qualifier
13
Advice Detail
External
Reference 56
TP_CD
DOC
ERR_CNT
2010
DT
EX2
14
Advice Detail
Internal
Reference 15
TP_CD
DOC
ERR_CNT
2020
DT
IN1
15
Advice Detail
Internal
Reference 6
TP_CD
DOC
ERR_CNT
2030
DT
IN2
16
Advice Detail
Data (Error)
TP_CD
DOC
ERR_CNT
2040
ER
ER1
17
Advice Detail
Data (Accepted)
TP_CD
DOC
ERR_CNT
2050
AC
AC1
18
Extension Table:
Detail Level
TP_CD
DOC
ERR_CNT
2900
(custom)
(custom)
88
Outbound Invoice (810 / INVOIC)

Use this transaction to bill customers for goods sold and services
rendered.
Application(s)
accessed
Oracle Receivables
ASC X12
Transaction
810
EDIFACT
Message
INVOIC
Prerequisite Setup in Oracle Receivables

Use Receivables to enter or adjust customer invoices.
In addition to entering customer invoices manually, you may also use
AutoInvoice feature of Receivables to import customer invoices from
nonOracle financial systems before extracting data for the EDI process.

Interface Tables
ECE_AR_TRX_ALLOWANCE_CHARGES (Oracle Automotive
only)
ECE_AR_TRX_HEADERS
ECE_AR_TRX_HEADER_1 (Oracle Automotive only)
ECE_AR_TRX_LINES
ECE_AR_TRX_LINE_TAX
Extension Tables
ECE_AR_TRX_ALLOWANCE_CHARGES_X
ECE_AR_TRX_HEADERS_X
89
ECE_AR_TRX_HEADER_1_X
ECE_AR_TRX_LINES_X
ECE_AR_TRX_LINE_TAX_X
Views
page 3 1.
ECE_INO_ALLOWANCE_CHARGES_V (Oracle Automotive
only)
ECE_INO_HEADER_1_V (Oracle Automotive only)
ECE_INO_HEADER_V
ECE_INO_LINE_TAX_V
ECE_INO_LINE_V
See Also
Running the EDI Invoice Outbound Extract Program: page 8 10
Outbound Invoice Data File Organization: page 8 12
Running the EDI Invoice Outbound Extract Program

Prerequisites
Define trading partner information and enable EDI transactions for


8 10
Customize the data file layout, if necessary. See: Changing the Data
File: page 5 2.
"
To run the EDI invoice outbound extract program:

1.
2.
3.
Select the EDI Invoice Outbound transaction.
4.
In the Parameters window, enter the following optional selection

criteria:
Specify an output data file name if not using the default.
Enter creation dates, From and To.
Enter a billto customer name.
Enter a billto site name.
Enter a transaction type and a transaction (invoice) number.
5.
6.
7.
8.
See Also
Outbound Invoice: page 8 9
Viewing the Status of Your Concurrent Programs: page 6 8
Outbound Invoice Data File Organization: page 8 12
8 11
Outbound Invoice Data File Organization

The data file produced by this transaction consists of three levels of data:
header, line, and tax.
Each invoice contains one header record that applies to the entire
invoice such as customer information. The invoice header is followed
by one or more invoice lines, each representing the item or service being
billed. Each line is followed by one or more tax lines associated with the
line item.
invoice header
invoice header allowance charges
invoice line
invoice line allowance charges
invoice line
invoice line detail
invoice line VAT tax
For the automotive environment, the following records are populated.
In all other environments, these records are left blank.
Record
Description
1015
Trading Partner References 1 & 2
1115
1215
1315
3075
Vehicle information
30903094
Allowance and charges attributes
8 12
Record
Description
7000
7010
7100
7110
7120
Allowance and charges attributes
6005
6025
6070
6080
6090
6095
VAT taxes
Summary Tables

Definition.

Records
Content
Occurrences
00100070
EDI Gateway Control

Records

per transaction
10003900
Invoice Header Records

per transaction
40005900
Invoice Item Records

within the invoice header
60007900
Invoice Item Detail

Records

within the invoice item
8 13
Record Summary
Seq.
Data
Data Level
Record
Number
Note
Control Record
CONTROL
0010

Flexfields
TRADING
PARTNER
00200050
Bill To Address /Code
INVOICE HEADER
1000
Bill to Misc. Data, Contacts
INVOICE HEADER
10101015
Bill to Customer Flexfields
INVOICE HEADER
10201050
Flexfields
INVOICE HEADER
10601090
Flexfields
INVOICE HEADER
1100
Ship to Misc. Data,

Contacts
INVOICE HEADER
1110
10
Sold to Address/Code
INVOICE HEADER
1200
11
Sold to Misc. data, Contact
INVOICE HEADER
12101215
12
Remit to Address/Code
INVOICE HEADER
13001315
13
Ship From Codes
INVOICE HEADER
1400
14
Basic Invoice Header Data
INVOICE HEADER
2000
15
Invoice Misc. Data
INVOICE HEADER
20102020
16
Shipment Data
INVOICE HEADER
2030
17
Currency Data, Misc. data,
INVOICE HEADER
2040
18
Payment Terms Data
INVOICE HEADER
2050
19
Sales Representative,
Comments
INVOICE HEADER
2060
20
Invoice Header Flexfields
INVOICE HEADER
30003030
Flexfields
21
Invoice Header Interface

Flexfields
INVOICE HEADER
30403070
Flexfields
22
Shipping Information
INVOICE HEADER
3080
23
Header Allowance/Charges
INVOICE HEADER
30903100
24
Extension Tables:
Invoice Header Data
INVOICE HEADER
3900
25
Basic Item Data
ITEM
4000
26
Sales Order Data,

Part Descriptions
ITEM
4010
27
Sales Channel
ITEM
4020
28
Order Status, Transaction

Reference Key
ITEM
4030
Table 8 7
8 14
Flexfields
(Custom)
Seq.
Data
Data Level
Record
Number
Note
29
Interface Line Flexfields
ITEM
50005030
Flexfields
30
Line Flexfields
ITEM
50405070
Flexfields
31
ITEM
51005130
Flexfields
32
Extension Tables: Item

Data
ITEM
5900
(Custom)
33
Line Tax Data
ITEM DETAIL
60006010
Flexfields
34
Line Tax Flexfields
ITEM DETAIL
60206060
Flexfields
35
Detail Allowance/Charges
ITEM DETAIL
70007010
36
Extension Tables:
Transaction Line Detail
Data
ITEM DETAIL
7900
(Custom)
37
Extension Tables:
Transaction Line Detail
Data
ITEM DETAIL
7900
(Custom)
Table 8 7
TransactionSpecific Data in the Common Key Positions 1100

Records
Content
Occurrences
125
TP_CD
Trading Partner Code as

defined in the EDI Translator
2647
INVOICE
Invoice number
4869
ITEM
Item sequence number
7091
TAX
Tax sequence number
9295
(Varies)
Record Number
9697
(Varies)
Record Layout
98100
(Varies)
8 15
TransactionSpecific Data in the Common Key Positions 1100 Per Record

Seq.
Data
Trading
Partner
Reference
1
Reference
2
Reference
3
Record
Number
Record
Layout
Record
Layout
Qualifier
Length
25
22
22
22
Position
125
2647
4869
7091
9295
9697
98100
Control Record
TP_CD
INVOICE
0010
CT
CTL
Trading Partner
Header Flexfields
TP_CD
INVOICE
0020
A3
TH1
Trading Partner
Header Flexfields
TP_CD
INVOICE
0030
A4
TH2
Trading Partner
Header Flexfields
TP_CD
INVOICE
0040
A4
TH3
Trading Partner
Header Flexfields
TP_CD
INVOICE
0050
A4
TH4
Trading Partner
Detail Flexfields
TP_CD
INVOICE
0060
A3
TD1
Trading Partner
Detail Flexfields
TP_CD
INVOICE
0070
A4
TD2
Bill To Address
/Code
TP_CD
INVOICE
1000
AD
BT1
Bill to Misc. data,

Contacts
TP_CD
INVOICE
101010
15
RF
BT1
10
Bill to Customer
Flexfields
TP_CD
INVOICE
1020
A1
BT1
11
Bill to Customer
Flexfields
TP_CD
INVOICE
1030
A2
BT2
12
Bill to Customer
Flexfields
TP_CD
INVOICE
1040
A2
BT3
13
Bill to Customer
Flexfields
TP_CD
INVOICE
1050
A2
BT4
14
TP_CD
INVOICE
1060
A1
BS1
15
TP_CD
INVOICE
1070
A2
BS2
16
TP_CD
INVOICE
1080
A2
BS3
17
TP_CD
INVOICE
1090
A2
BS4
18
Ship to
Address/code
TP_CD
INVOICE
1100
AD
ST1
19
Ship to Misc. data,

contacts
TP_CD
INVOICE
1110111
5
RF
ST1
8 16
Seq.
Data
Trading
Partner
Reference
1
Reference
2
Reference
3
Record
Number
Record
Layout
Record
Layout
Qualifier
20
Sold to
Address/code
TP_CD
INVOICE
1200
AD
SO1
21
Sold to Misc. data,

Contact
TP_CD
INVOICE
121012
15
RF
SO1
22
Remit to
address/code
TP_CD
INVOICE
1300
AD
RE1
22
Remit to Miscalleous
Data
TP_CD
INVOICE
1315
RF
RE1
23
Ship From Codes
TP_CD
INVOICE
1400
SF
SF1
24
Basic Invoice Header

Data
TP_CD
INVOICE
2000
IV
IV1
25
Invoice Amount
Data
TP_CD
INVOICE
2010
IV
IV2
26
Invoice Misc. Data
TP_CD
INVOICE
2020
IV
IV3
27
Shipment Data
TP_CD
INVOICE
2030
IV
IV4
28
Currency Data,
Shipping Data,
Miscellaneous Data
TP_CD
INVOICE
2040
IV
IV5
29
Payment Terms Data
TP_CD
INVOICE
2050
IV
IV6
30
Sales Representative,
Comments
TP_CD
INVOICE
2060
IV
IV7
31
Invoice Header
Flexfields
TP_CD
INVOICE
3000
A1
IH1
32
Invoice Header
Flexfields
TP_CD
INVOICE
3010
A2
IH2
33
Invoice Header
Flexfields
TP_CD
INVOICE
3020
A2
IH3
34
Invoice Header
Flexfields
TP_CD
INVOICE
3030
A2
IH4
35
Invoice Header
Interface Flexfields
TP_CD
INVOICE
3040
A1
IH5
36
Invoice Header
TP_CD
INVOICE
3050
A2
IH6
37
Invoice Header
TP_CD
INVOICE
3060
A2
IH7
38
Invoice Header
TP_CD
INVOICE
3070
A2
IH8
8 17
Seq.
Data
Trading
Partner
Reference
1
Reference
2
Reference
3
Record
Number
Record
Layout
Record
Layout
Qualifier
39
Invoice Header
Shipping
Instructions
TP_CD
INVOICE
3075
IV
SHP
40
Header
Allowance/Charges
TP_CD
INVOICE
3090
AH
AH1
41
Header
Allowance/Charges
TP_CD
INVOICE
3100
AH
AH2
42
Extension Tables:
Invoice Header Data
TP_CD
INVOICE
3900
43
Basic Item Data
TP_CD
INVOICE
ITEM
4000
IT
IT1
44
Sales Order Data,

Part, Customer
Item Description
TP_CD
INVOICE
ITEM
4010
IT
IT2
45
Sales Channel, Order

Status
TP_CD
INVOICE
ITEM
4020
IT
IT3
46
Transaction
Reference Key,
Order Status
TP_CD
INVOICE
ITEM
4030
IT
IT4
47
Interface Line
Flexfields
TP_CD
INVOICE
ITEM
5000
A1
IL1
48
Interface Line
Flexfields
TP_CD
INVOICE
ITEM
5010
A2
IL2
49
Interface Line
Flexfields
TP_CD
INVOICE
ITEM
5020
A2
IL3
50
Interface Line
Flexfields
TP_CD
INVOICE
ITEM
5030
A2
IL4
51
Line Flexfields
TP_CD
INVOICE
ITEM
5040
A1
LN1
52
Line Flexfields
TP_CD
INVOICE
ITEM
5050
A2
LN2
53
Line Flexfields
TP_CD
INVOICE
ITEM
5060
A2
LN3
54
Line Flexfields
TP_CD
INVOICE
ITEM
5070
A2
LN4
55
TP_CD
INVOICE
ITEM
5100
A1
LP1
56
TP_CD
INVOICE
ITEM
5110
A2
LP2
57
TP_CD
INVOICE
ITEM
5120
A2
LP3
58
TP_CD
INVOICE
ITEM
5120
A2
LP4
59
Extension Tables:
Item Data
TP_CD
INVOICE
ITEM
5900
60
Line Tax Data
TP_CD
INVOICE
ITEM
8 18
TAX
6000
(Custom)
(Custom)
TX
TX1
Seq.
Data
Trading
Partner
Reference
1
Reference
2
Reference
3
Record
Number
Record
Layout
Record
Layout
Qualifier
61
Line Tax Data
TP_CD
INVOICE
ITEM
TAX
601060
20
TX
TX2
62
Line Tax Flexfields
TP_CD
INVOICE
ITEM
TAX
6030
A1
TX1
63
Line Tax Flexfields
TP_CD
INVOICE
ITEM
TAX
6040
A2
TX2
64
Line Tax Flexfields
TP_CD
INVOICE
ITEM
TAX
6050
A2
TX3
65
Line Tax Flexfields
TP_CD
INVOICE
ITEM
TAX
6060
A2
TX4
66
Detail
Allowance/Charges
TP_CD
INVOICE
ITEM
TAX
7000
AD
AD1
67
Detail
Allowance/Charges
TP_CD
INVOICE
ITEM
TAX
7010
AD
AD2
68
Detail
Allowance/Charges
Flexfields
TP_CD
INVOICE
ITEM
TAX
7100
AL
IL1
69
Detail
Allowance/Charges
TP_CD
INVOICE
ITEM
TAX
7110
AL
IL2
70
Detail
Allowance/Charges
TP_CD
INVOICE
ITEM
TAX
7120
AL
IL3
71
Detail
Allowance/Charges
TP_CD
INVOICE
ITEM
TAX
7130
AL
IL4
72
Extension Tables:
Transaction Line
Detail Data
TP_CD
INVOICE
ITEM
TAX
7900
(Custom)
8 19
Outbound Payment Order / Remittance Advice (820 / PAYORD,

REMADV)
Use this transaction to electronically make a payment, or make a
payment and send a remittance advice to your creditors.
The payment portion of this transaction is a request to your financial
institution to perform cash application to relieve your account and to
pay your payees account.
The remittance advice portion of this transaction contains the payment
distribution by invoice. It may be sent directly to the payee, through a
financial institution, or through a third party. In addition, you may use
Oracle Payables to print your remittance advice.
Payments made using electronic funds transfer (EFT) may be processed
via EDI if your EDI translator has the means to download the payment
data from Payables to tape for delivery to the payees bank.
Application(s)
accessed
Oracle Payables
ASC X12
Transaction
820
EDIFACT
Messages
PAYORD / REMADV
PAYEXT / REMADV
Prerequisite Set Up in Oracle Payables

Use Payables to enable the payer and payee site. Indicate for the payer
and payee site the payment method, payment format, remittance
method, remittance instruction, and transaction handling instructions.
Use the Invoice Workbench to enter and approve invoices, and to release
invoice holds.
Use the Payment Workbench to select invoices for payment, create a
payment batch, and to submit the EDI payment transaction. This
transaction is eventdriven and integrated with the standard Payables
payment process. It cannot be initiated through the EDI Gateway.
However, you must use the EDI Gateway to set up the trading partner
and enable the transaction.
8 20

Interface Tables
ECE_AP_CHECKS_INTERFACE
ECE_AP_INVOICES_INTERFACE
Extension Tables
ECE_AP_CHECKS_INTERFACE_X
ECE_AP_INVOICES_INTERFACE_X
Views
page 3 1.
ECE_PYO_INVOICE_V
ECE_PYO_PAYMENT_V
See Also
Running the EDI Payment Order / Remittance Advice Outbound
Extract Program: page 8 22
Outbound Payment Order / Remittance Advice Data File Organization:
page 8 23
8 21
Running the EDI Payment Order / Remittance Advice Outbound Extract Program
Prerequisites



File: page 5 2.
"
To run the EDI payment order / remittance advice outbound extract

program:
H
The extract program for this transaction is eventdriven in Payables.

It cannot be initiated through EDI Gateway.
The current payment batch being processed is extracted and written
to a default data file named ECEPYO, which is placed in the
designated outbound directory. See: Creating Electronic Payments
with the Oracle EDI Gateway, Oracle Payables Users Guide, Release 11.
See Also
Outbound Payment Order / Remittance Advice: page 8 20
Outbound Payment Order / Remittance Advice Data File Organization:
page 8 23
8 22
Outbound Payment Order / Remittance Advice Data File Organization

The data file produced by this transaction consists of two levels of data:
payment and invoices.
Each payment will contain one or many invoices associated with that
payment.
payment
invoice
payment
invoice
invoice
Summary Tables

Definition.

Records
Content
Occurrences
00100070
EDI Gateway
Control Records
Only one record
10001050
Payment Header
Records
Only one record occurrence per

transaction
20002040
Remittance/Invoice
Records
One set of records per invoice within the

Payment Header
8 23
Record Summary
Seque
nce
Type of Data
Data Level
Record
Number
Control Record
CONTROL
0010

Attributes
TRADING
PARTNER
0020
Flexfields

Attributes
TRADING
PARTNER
00300050
Flexfields
Account Data
PAYMENT
1000
Payment Data
PAYMENT
1010
Supplier Flex Field

Segments
PAYMENT
1020
Bank Address / Code
PAYMENT
1030
10
Bank Contacts
PAYMENT
1040
11
Supplier Site Address /

Code
PAYMENT
1050
12
Extension Tables:
Payment Data
PAYMENT
1900
13
Remittance / Invoice
Details
INVOICE /
REMITTANCE
2000
14
Remittance Advice
Flexfields 14
INVOICE /
REMITTANCE
2010
Flexfields
15
Remittance Advice
Flexfields 59
INVOICE /
REMITTANCE
2020
Flexfields
16
Remittance Advice
Flexfields 1014
INVOICE /
REMITTANCE
2030
Flexfields
17
Remittance Advice
Flexfields 15
INVOICE /
REMITTANCE
2040
Flexfields
8 24
Misc. Info.

Position
Code
Content
125
TP_CD
Trading partner code as defined in the EDI

translator
2647
BATCH
Payment batch number
4869
INVOICE
Invoice number
7091
(blank)
Not used
9295
(varies)
Record number
9697
(varies)
Record layout
98100
(varies)
Record layout qualifier

Seq.
Record
Length
Position
TP_CD
Reference
1
Reference
2
Reference
3
Record
Number
Record
Layout
Record
Quallifier
25
22
22
22
125
2647
4869
7091
9295
9697
98100
Control record
TP_CD
0010
CT
CTL
Trading partner header

attributes
TP_CD
0020
A1
TH1
Trading partner header

attributes
TP_CD
00300050
A2
TH2TH4
Account data
TP_CD
BATCH
1000
BK
BK1
Payment data
TP_CD
BATCH
1010
PY
PAY
Supplier flexfield segments
TP_CD
BATCH
1020
VN
VN1
Bank address / code
TP_CD
BATCH
1030
AD
BK1
10
Bank contacts
TP_CD
BATCH
1040
CN
BK1
11
Supplier site address /

code
TP_CD
BATCH
1050
AD
VS1
Table 8 13
(Page 1 of 2)
8 25
Seq.
Record
TP_CD
Reference
1
12
Extension tables: payment

data
TP_CD
BATCH
13
Remittance / invoice
details
TP_CD
BATCH
14
Remittance advice
flexfields 14
TP_CD
15
Remittance advice
flexfields 59
16
17
Record
Number
Record
Layout
Record
Quallifier
1900
EX
(custom)
INVOICE
2000
IV
INV
BATCH
INVOICE
2010
A1
RE1
TP_CD
BATCH
INVOICE
2020
A2
RE2
Remittance advice
flexfields 1014
TP_CD
BATCH
INVOICE
2030
A2
RE3
Remittance advice
flexfields 15
TP_CD
BATCH
INVOICE
2040
A2
RE4
Table 8 13
8 26
(Page 2 of 2)
Reference
2
Reference
3
Outbound Planning Schedule (830 / DELFOR)

Use this transaction to communicate forecast requirements to your
suppliers. The planning schedules may be comprised of both forecast
and material release information including authorizations from the
buyer to commit material and labor resources for a specific period. The
planning schedule may be stated in daily, weekly, monthly, quarterly, or
in any combination of periods.
Application(s)
accessed
Oracle Supplier Scheduling, Oracle Purchasing,

Oracle Planning
ASC X12
Transaction
830
EDIFACT
Message
DELFOR (DELivery FORecast)
Prerequisite Setup in Oracle Applications

Oracle Supplier Scheduling
Create planning schedules manually using the Schedulers Workbench
or automatically using AutoSchedule.
Define bucket patterns, enable CUM Accounting for an organization to
track quantity received by supplier site, and define authorizations that
grant approval to a supplier to procure components, process material,
and carry finished goods.
Use the Scheduler Workbench or enable AutoConfirm option in
AutoSchedule to confirm your schedules. Only confirmed planning
schedules may be transmitted via EDI to your supplier(s).
Oracle Purchasing
Supplier Scheduling uses components of Oracle Purchasing to calculate
and maintain schedules. Use the Approved Supplier list created in
Purchasing to establish a relationship between the shipto organization,
supplier site, and item.
Information related to approved purchase requisitions, approved supply
agreement releases, receipts from supplier, returns to supplier and
associated adjustments are used to determine the supplier requirement.
8 27
Oracle Planning
Supplier Scheduling also uses components of Oracle Planning to
calculate and maintain schedules. Use Sourcing Rules (which may be
created in Purchasing, Oracle Supply Chain Planning, or Supplier
Scheduling) to define how an item is replenished for a given
organization. This includes the ability to identify multiple supplier
sources, their percentage splits, and priority ranking.
Information related to unimplemented planned orders generated by
Planning via MPS, MRP, or DRP are used to determine the supplier
requirement.

Interface Tables
ECE_SPSO_HEADERS
ECE_SPSO_ITEMS
ECE_SPSO_ITEM_DEF
Extension Tables
ECE_SPSO_HEADERS_X
ECE_SPSO_ITEMS_X
ECE_SPSO_ITEM_DEF_X
Views
The following view appears in the Assign Categories window, under
View Name, for this transaction. Columns within this view are
page 3 1.
ECE_SPSO_HEADERS_V
ECE_SPSO_ITEMS_V
ECE_SPSO_ITEM_DEF_V
8 28
See Also
Program: page 8 51
Outbound Planning Schedule Data File Organization: page 8 30
8 29
Outbound Planning Schedule Data File Organization

schedule header, schedule line, and schedule line details.
Each planning schedule contains one schedule header record that
applies to the entire schedule. The schedule header is followed by one
or more schedule lines, each representing an item. Each schedule line is
followed by one or more line details representing requirements,
authorizations, and the items last and cumulative receipts.
The ship to location is at the schedule line level. All schedule quantities
are discrete quantities, not cumulative quantities. The CUM enabling
flag addresses only the receipt data to be provided as a CUM receipt
quantity. The CUM enabling flag does not impact the schedule
requirements.
The line details section includes the following:
Requirements
Up to 60 occurrences per the userdefined bucket

and planning horizon for the schedule.
Prior
Authorization
One occurrence if authorizations are enabled at the

Approved Suppliers list.
Authorizations
One occurrence for each authorization type if

authorizations are enabled at the Approved
Supplier list. Authorizations cover raw material,
labor, labor & material or finished goods.
Last Receipt
One occurrence identifying the quantity, date and

shipment number of the last receipt for the item.
Cumulative
Receipt
One occurrence identifying the cumulative receipt

quantity for the item if CUM accounting is enabled.

schedule header
schedule line and cumulative receipt
schedule line detail (requirements)
schedule line detail (authorizations)
schedule line detail (last receipt)
schedule line and cumulative receipt
8 30
See: Running the EDI Outbound Planning and Shipping Schedules

Extract Program: page 8 51.
General Information
The supplier scheduling transactions support the following transactions
and their counterparts in any other standard:
Planning Schedule (830) / Delivery Just in Time (DELJIT)
Shipping Schedule (862) / Delivery Schedule (DELFOR)
The outbound planning and shipping schedule data file definition
describes the position, field name, field size, and format of each record
in the data file.
Details for the ASC X12 transactions are documented below.
The shipping schedule transaction does not include the last shipment
receipt records 2040 and the 4000 with Detail Descriptor set to RECEIPT
or authorizations with Detail Descriptor set to AUTHORIZATION.
Otherwise, the interface files are identical.
Discrete (actual) requirement quantities are indicated in the buckets in
the application, i.e., in a weekly bucket, the quantity required for that
week only.
The EDI Translator needs to build cumulative required quantities using
the cum received quantity if the trading partner wants a cumulative
schedule.
Ship to Location
The Ship to location may be found in the header level of the transaction
(records 10301060) if the single location applies to the entire
transaction. Alternately, the Ship to location may be found at the detail
level (records 20502060) for a given item. In each case, the Ship To Org
Enable CUM Flag indicates that the site is using CUM quantities, and
that the Ship To Org CUM Period Start Date should be used whenever a
start date is needed in the detail.
ASC X12 Specifics

Supplier Scheduling supports the following data on the Beginning
Segment for Planning Schedule (BRF) segment in the 830 transaction.
8 31
The following values should be used in the EDI data mapping to the
ASC X12 transaction.
ASC X12 Data Element
ASC X12 Position

and Values
Data
Transaction Purpose
BRF01 = 05
Replacement
Schedules Only
Schedule Type Qualifier
BRF04 = DL
Delivery Based
Schedules
Schedule Quantity Qualifier
BRF05 = A
Actual Discrete
Quantity Only
Last Receipt Data (Record 2040) Item Level

The application shipment data is copied to the Item level (record 2040)
from the shipment level (record 4000) since the last shipment data
applies to the item. The data is copied from two Forecast/Planned
Detail (4000) records with Detail Category set to RECEIPT.
This data is mapped to the ASC X12 Shipped (SHP) and Reference (REF)
segments.
Record 4000 Source

Pos.
Interface Record
Receipt
Detail Category/
Descriptor
Data Element
RECEIPT/LAST
100 Document
Type
(Map to ASC X12

SHP segment)
Common Key
10
Record Number
2040
Record Layout
LS
Record Layout
Qualifier
LS1
Last Receipt
Shipment
Identification
AUTHORIZATION
<Shipment
Number>
Table 8 15 Last Receipt and Cumulative Data-Record 2040 Details
8 32
Record 4000 Source
20
Last Receipt Date
PRIOR <Last
Transaction Date>
RECEIPT/LAST
50 Starting Date
30
Last Receipt
Quantity
<Last Quantity
Received>
RECEIPT/LAST
90 Total Quantity
40
CUM Quantity
after last Receipt
<Starting CUM
Quantity>
RECEIPT/CUMULATIVE
90 Total Quantity
Table 8 15 Last Receipt and Cumulative Data-Record 2040 Details
Table 8 16 through Table 8 20 illustrate where data in Table 8 15 is

mapped in SHP and REF segments. Two occurrences of SHP segments
are required: one to specify last discrete quantity received or shipped,
and one to specify cumulative quantity received or shipped since last
cum reset.
SHP Segment
Data
Element
Position
Content
Record 2040 Source
Quantity Qualifier
673
SHP01=
01
Standard for discrete quantity
Quantity
380
SHP02=
<Last Shipment Quantity>
30 Last Receipt Quantity
Date/Time Qualifier
374
SHP03=
050 or
Standard for Received or
011
Standard for Shipped

20 Last Receipt Date
Date
373
SHP04=
<Last Receipt Date>
Time
337
SHP05=
n/a
Date
373
SHP06=
n/a
Time
337
SHP07=
n/a
Table 8 16 Data Mapping of the Last Receipt Data from Record 2040 to map to Shipped (SHP) segment
SHP Segment
Data
Element
Position
ASC X12 Value
Record 2040 Source
Quantity Qualifier
673
SHP01=
02
40 Standard for Cumulative quantity
Quantity
380
SHP02=
Date/Time Qualifier
374
SHP03=
051
Standard for Cumulative quantity

Start
Table 8 17 Data Mapping of the Cumulative Quantity Received from Record 2040 to SHP shipment
8 33
SHP Segment
Data
Element
Position
ASC X12 Value
Date
373
SHP04=
Time
337
SHP05=
n/a
Date
373
SHP06=
n/a
Time
337
SHP07=
n/a
Record 2040 Source
Table 8 17 Data Mapping of the Cumulative Quantity Received from Record 2040 to SHP shipment
REF Segment
Data
Element
Position
ASC X12 Value
Record 2040 Source
Reference Qualifier
REF01=
SI
Standard for Shipment Identifier
Reference Identification
REF02=
<shipment number>
10 Last Receipt Shipment Number
Table 8 18 Data Mapping of the Last Receipt Shipment Number from Record 2040 to REF segment
Forecast/Planned Details (Record 4000)

Record 4000 in the Supplier Scheduling interface file contains data from
several sources. This causes the data to be mapped to one of the
following segments in ASC X12:
Shipped/Received Information (SHP)
Resource Authorization (ATH)
Forecast Schedule (FST)
The Detail Category and the Detail Descriptor in the record indicate the
content of specific data. The combination of these two fields and their
record content are summarized in Table 8 19.
The dates on the Forecast Schedule (FST) segment represent the starting
date for the bucketed period only. Ending date is applicable only for
Detail Descriptor BUFFER in the Record 4000.
A given transaction may technically have a mixture of planning
schedules with discrete and cumulative based quantities if the supplier
scheduling process does not prohibit it across all the items within a
single transaction.
8 34
The quantities and start/end dates on record 4000 data for a given
Detail Category and Detail Descriptor varies depending upon if the
SHIP_TO_ORG_ ENABLE_CUM_FLAG is enabled. See the Record 4000
Detail tables below for their content.
Last Receipt Data (Record 4000) Shipment Level

Last shipment data and cumulative receipt data are found in a Record
4000 (detail level) with Detail Category RECEIPT and Descriptor LAST
and CUMULATIVE, respectively. The data was combined at the item
level into Record 2040 (item level). Either may be used for data
mapping in the EDI Translator; however, the data is appropriate at the
item level and more likely to be mapped from that level.
Table 8 19 and Table 8 20 summarize the type of data found on
record 4000:
Record 4000 Detail

Category (position
20)
Record 4000 Detail

Descriptor
(position 30)
Associated
ASC X12
Segment
RECEIPT
LAST
SHP
Record Content
Last Receipt data

(data also on record 2040)
CUM total attained upon last received

shipment.
RECEIPT
CUMULATIVE
SHP
(Data also on record 2040)
Create this SHP record only if the ship

to location is doing CUM management (CUM Flag is enabled).
AUTHORIZATION
PRIOR
ATH
Prior Authorization
AUTHORIZATION
FI
ATH
Authorization data for finished Inventory
AUTHORIZATION
LB
ATH
Authorization data for labor only
AUTHORIZATION
LM
ATH
Authorization data for labor and material
AUTHORIZATION
MT
ATH
Authorization data for material only
REQUIREMENT
PAST_DUE
FST
Planned or firm requirements for Past

due (immediate use) quantities
REQUIREMENT
DAY
FST
Planned or firm requirements in daily

quantities
Table 8 19 Data Content by Detail Category and Detail Descriptor for Record 4000
8 35
Record 4000 Detail

Category (position
20)
Record 4000 Detail

Descriptor
(position 30)
Associated
ASC X12
Segment
Record Content
REQUIREMENT
BUFFER
FST
Planned or firm requirements for flexible intervals quantities
REQUIREMENT
WEEK
FST
Planned or firm requirements for

weekly quantities
REQUIREMENT
MONTH
FST

monthly quantities
REQUIREMENT
QUARTER
FST

quarterly quantities
Table 8 19 Data Content by Detail Category and Detail Descriptor for Record 4000
Key data elements for the ASC X12 segment given Detail Category and
Detail Descriptor indicated.
Record 4000 Detail
Category (position
20)
Record 4000
Detail
Descriptor
(position 30)
Key ASC X12 Data Element
RECEIPT
LAST
SHP01= 01 (Discrete Qty)
Note
Also written to Record

2040
SHP03= 050 (Received)
RECEIPT
CUMULATIVE
SHP02=02 (Cum Qty)
Create SHP segment

only if
SHIP_TO_ORG_ENA
BLE_CUM_FLAG is
enabled.
SHP03=051 (Cum Qty Start)
Also written to Record

2040
AUTHORIZATION
PRIOR
ATH01=PQ (Cum Requirement

Prior to First Schedule Period)
AUTHORIZATION
FI
ATH01=FI (Finished Inventory)
AUTHORIZATION
LB
ATH01= LB (labor)
AUTHORIZATION
LM
ATH01= LM (labor, material)
AUTHORIZATION
MT
ATH01= MT (material)
REQUIREMENT
PAST_DUE
FST02 =A (Immediate)
REQUIREMENT
(all values
except
PAST_DUE)
FST02 =C (Firm)
If Release Quantity > 0
Table 8 20 Key ASC X12 Data Element per Detail Category and Detail Descriptor within Record 4000
8 36
Record 4000 Detail

Category (position
20)
Record 4000
Detail
Descriptor
(position 30)
Key ASC X12 Data Element
REQUIREMENT
(all values
except
PAST_DUE)
FST02 =D (Planning)
REQUIREMENT
PAST_DUE
FST03=A (Immediate)
REQUIREMENT
DAY
FST03=C (Daily)
REQUIREMENT
BUFFER
FST03=F (Flexible Interval)
REQUIREMENT
WEEK
FST03=W (Weekly Bucket)
REQUIREMENT
MONTH
FST03=M (Monthly Bucket)
REQUIREMENT
QUARTER
FST03=Q (Quarterly)
Note
If Forecast Quantity >

0
Table 8 20 Key ASC X12 Data Element per Detail Category and Detail Descriptor within Record 4000
Table 8 21 through Table 8 29 illustrate the details of record 4000 for

each pair of values of the Detail Category and Detail Descriptor,
followed by the placement of data on the ASC X12 transaction.
A. Receipt / Last
Last shipment received:
Position
Interface Record
Last Shipment
(Map to ASC X12 SHP segment)
Common Key
Record Number
4000
Record Layout
SC
SCH
10
Schedule Item Detail

Sequence
<a counter>
20
Detail Category
AUTHORIZATION RECEIPT
30
Detail Descriptor
PRIOR LAST
40
Detail Descriptor (external)
50
Starting Date
<Last Shipment Date>
60
Ending Date
n/a
Table 8 21 RECEIPT / LASTRecord 4000 Details (maps to SHP segment)
8 37
Position
Interface Record
Last Shipment
70
Forecast Quantity
n/a
80
Release Quantity
n/a
90
Total Quantity
<Actual Last Shipped Quantity or

zero>
100
Document Type
SHIPMENT
110
Document Number
<Shipment Number>
Table 8 21 RECEIPT / LASTRecord 4000 Details (maps to SHP segment)
This data is also found on the Record 2040 at the schedule level.
SHP Segment
Data
Element
Position
ASC X12 Value
Record 4000
Quantity
Qualifier
673
SHP01=
01
Standard for Discrete

Quantity
Quantity
380
SHP02=
<Last Shipment Qty>
90 Total Quantity
Date/Time
Qualifier
374
SHP03=
050
Standard for
Received
Date
373
SHP04=
<Last Shipment Date>
50 Starting Date
Time
337
SHP05=
n/a
Date
373
SHP06=
n/a
Time
337
SHP07=
n/a
Table 8 22 RECEIPT / LASTRecord 4000 mapped to Shipped (SHP) segment
B. Receipt / Cumulative
CUM quantities after the last shipment was received:
Pos.
Interface Record
Cumulative Receipt
(Map to ASC X12 SHP segment)
Common Key
Record Number
4000
Table 8 23 RECEIPT / CUMULATIVERecord 4000 Details
8 38
Pos.
Interface Record
Cumulative Receipt
Record Layout
SC
SCH
10
Schedule Item Detail Sequence
<a counter>
20
Detail Category
AUTHORIZATION RECEIPT
30
Detail Descriptor
PRIOR CUMULATIVE
40
50
Starting Date
<Cum Period Start Date>
Ship To Org CUM Period Start Date
60
Ending Date
<Schedule Horizon Start Date>
70
Forecast Quantity
n/a
80
Release Quantity
n/a
90
Total Quantity
Cumulative Receipt Quantity as of schedule Horizon Start Date
100
Document Type
n/a
110
Document Number
n/a
(Forecast Horizon Start Date)
Table 8 23 RECEIPT / CUMULATIVERecord 4000 Details
This data is also moved to the Record 2040 at the item level.
SHP Shipped
Segment
Data
Element
Position
ASC X12 Value
Record 4000
Quantity
Qualifier
673
SHP01=
02
Standard for Cum

Quantity
Quantity
380
SHP02=
<CUM Receipt Qty as of

schedule Horizon Start Date>
90 Total Quantity
Date/Time
Qualifier
374
SHP03=
051
Standard for Cum

Quantity
Date
373
SHP04=
<Ship to Org CUM Period Start

Date>
50 Starting Date
Time
337
SHP05=
n/a
Table 8 24 RECEIPT / CUMULATIVERecord 4000 mapped to SHP Segment *The ending date of
the cumulative period is the starting date of the schedule.
8 39
SHP Shipped
Segment
Data
Element
Position
ASC X12 Value
Date
373
SHP06=
<Forecast Horizon Start Date> *
Time
337
SHP07=
n/a
Record 4000
60 Ending Date
Table 8 24 RECEIPT / CUMULATIVERecord 4000 mapped to SHP Segment *The ending date of
the cumulative period is the starting date of the schedule.
C. Authorization / Prior
Authorizations for quantities prior to first schedule period:
File
Pos.
Interface Record
CUM Management Enabled
CUM Management
Not Enabled
This record does not

exist if CUM
Management is Not
Enabled.
Common Key
Record Number
4000
Record Layout
SC
Record Layout
Qualifier
SCH
10
Schedule Item
Detail Sequence
<a counter>
20
Detail Category
AUTHORIZATION
30
Detail Descriptor
PRIOR
40
Detail Descriptor
(external)
50
Starting Date
<Cum Period Start Date> *
60
Ending Date
<Schedule Horizon Start Date>
70
Forecast Quantity
n/a
80
Release Quantity
n/a
Table 8 25 AUTHORIZATION / PRIORRecord 4000 Details with CUM enabled

and not enabled (to map to AASC X12 ATH segment). *The ending date of the cumulative period is the starting date of the schedule.
8 40
File
Pos.
Interface Record
CUM Management Enabled
90
Total Quantity
<Starting Authorization
Quantity
(sum of past due and CUM
received)>
100
Document Type
n/a
110
Document
Number
n/a
CUM Management
Not Enabled
Table 8 25 AUTHORIZATION / PRIORRecord 4000 Details with CUM enabled

and not enabled (to map to AASC X12 ATH segment). *The ending date of the cumulative period is the starting date of the schedule.
ATH Authorization
Segment
Data
Element
Position
ASC X12 Value
Record 4000 Source
Resource
Authorization Code
672
ATH01=
PQ
Standard (CUM qty

required Prior to first
Schedule Period)
(based on 30 Detail
Descriptor is PRIOR)
Date (through Date)
373
ATH02=
<Schedule Horizon Start

Date>
60 Ending Date
Quantity
(Current Cum
Requirement Qty)
380
ATH03=
<Starting Authorization
Quantity>
90 Total Quantity
Quantity
380
ATH04=
n/a
n/a
Date (Cumulative
Start Date)
373
ATH05=
<CUM Period Start Date>
50 Starting Date
Table 8 26 AUTHORIZATION / PRIORRecord 4000 Details mapped to ATH segment
8 41
3. Authorization / FI, LB, LM, MT

Authorizations for finished inventory, labor, and / or material:
File
Pos.
Interface Record
Common Key
CUM Management Not

Enabled
Record Number
4000
Record Layout
SC
SCH
10
Schedule Item Detail Sequence
<a counter>
20
Detail Category
AUTHORIZATION
30
Detail Descriptor
FI or LB or LM or MT
40
50
Starting Date
<Schedule Horizon Start

Date>
60
Ending Date
<Authorization Cut Off

Date>
70
Forecast Quantity
n/a
80
Release Quantity
n/a
90
Total Quantity
<Cumulative Authorized
Quantity for Schedule>
100
Document Type
n/a
110
Document Number
n/a
Table 8 27 AUTHORIZATION / (FL/LB/LM/MT)Record 4000 Details

with CUM enabled and not enabled (to map to ASC X12 ATH segment).
ATH Authorization
Segment
Data
Element
Position
ASC X12 Value
Record 4000
Source
Resource Authorization
Code*
672
ATH01=
FI (Finished Inventory),
LB (Labor),
LM (Labor & Material),
MT (Material
Standard (based
on 30 Detail
Descriptor)
Date
(through Date)
373
ATH02=
If CUM or NOT CUM,

<Authorization Cut Off Date>
60 Ending Date
Table 8 28 AUTHORIZATION / (nonPRIOR Descriptor)Record 4000 Details mapped to ATH segment
8 42
ATH Authorization
Segment
Data
Element
Position
ASC X12 Value
Record 4000
Source
Quantity
(Current Cum Requirement
Qty)
380
ATH03=
If CUM,
<CUM Authorized Qty for CUM period>
If NOT CUM,
<Cumulative Authorized Qty for
Schedule>
90 Total Quantity
Quantity
380
ATH04=
(blank)
n/a
Date (Cumulative Start

Date)
373
ATH05=
If CUM, <CUM Period Start Date>

If NOT CUM, <Schedule Horizon Start
Date>
50 Starting Date
Table 8 28 AUTHORIZATION / (nonPRIOR Descriptor)Record 4000 Details mapped to ATH segment
4. Requirement / PAST_DUE, DAY, BUFFER, WEEK, MONTH, QUARTER

Planned and Firm forecast quantities:
Pos.
Interface Record
Common Key
Record Number
4000
Record Layout
SC
Record Layout
Qualifier
SCH
10
Schedule Item
Detail Sequence
<a counter>
20
Detail Category
REQUIREMENT
30
Detail Descriptor
PAST_DUE, BUFFER, DAY,

WEEK, MONTH, QUARTER
40
Detail Descriptor
(external)
A (Immediate (PAST_DUE))
F (Flexible Interval (BUFFER))
D (Day), W (Week), M (Month),
Q (Quarter)
50
Starting Date
<Requirement Start Date>
60
Ending Date
<Requirement End Date
70
Forecast Quantity
<Discrete Quantity>
Only if
Detail
Descriptor
is BUFFER
Table 8 29 REQUIREMENT / (all values)Record 4000 Details (to map

to ASC X12 FST segment).
8 43
Pos.
Interface Record
80
Release Quantity
<Discrete Release Quantity>
90
Total Quantity
<Cumulative Authorized
Quantity for Schedule> (Sum of
70 Forecast Quantity and 80
Release Quantity
100
Document Type
n/a
110
Document
Number
n/a
Not
mapped to
the
standard
Table 8 29 REQUIREMENT / (all values)Record 4000 Details (to map

to ASC X12 FST segment).
Note: If both Release Quantity is greater than zero and Forecast

Quantity is greater than zero, two ASC X12 FST segments should be
generated.
If 80 Release Quantity >0,
move 80 Release Quantity to Quantity (FST01)
move C (Firm) to Forecast Qualifier (FST02)
move 50 Start Date to Date (FST04)
(and if Detail Descriptor is BUFFER, move 60 Ending Dates to
Date (FST05)
If 80 release Quantity > 0 and Detail Descriptor is PAST_DUE
move 80 Release Quantity to Quantity (FST01),
move A (Immediate) to Forecast Qualifier (FST02),
more 50 Start Date to Date (FST04)
If 70 Forecast Quantity > 0,
move 70 Forecast Quantity to Quantity (FST01),
move D (Planned) to Forecast Qualifier (FST02)
move 50 Start Date to Date (FST04)
(and if Detail Descriptor is BUFFER, move 60 Ending Dates to
Date (FST05)
Position 30 Detail Descriptor (internal) has a code conversion to
determine position 40 Detail Descriptor (External) if needed for
Forecast Timing Qualifier (FST03).
8 44
The Detail Descriptor of PAST_DUE is different as noted above.

Total quantity is the sum of released and forecast quantity. If
needed, you can demote the release quantity to forecast when a
bucketed period includes both. Sending both released and
forecasted in the same time period is not actually done in EDI.
However, Oracle data comes from two different sources that do not
make each other mutually exclusive, so this could happen.
Firm Forecast Data

FST Forecast
Segment
Data
Element
Position
ASC X12 Value
Record 4000
80 Release Quantity
Quantity
380
FST01=
<Release Quantity>
Forecast Qualifier
680
FST02=
C (Firm) if Release Quantity > 0
Forecast Timing
Qualifier
681
FST03=
D (Day), W (Week), M (Month), Q (Quarter)
40 Detail Descriptor
(external)
Date (Start)
373
FST04=
<Starting Date>
50 Starting Date
Date (End)
(ONLY IF
BUFFER)
373
FST05=
<Ending Date>
60 Ending Date
Date/Time
Qualifier
374
FST06=
002
Standard for Delivery

Requested
Time
337
FST07=
n/a
Reference
Number Qualifier
128
FST08=
n/a
Reference
Number
127
FST09=
n/a
Table 8 30 Data Mapping of the REQUIREMENT Detail Category data to the FST segment when (Firm) Release
Quantity Zero
Planned Forecast Data

FST Forecast
Segment
Data
Element
Position
ASC X12 Value
Record 4000 Source
70 Forecast Quantity
Quantity
380
FST01=
<Forecast Quantity>
Forecast Qualifier
680
FST02=
D (Planned) if Forecast Quantity > 0
8 45
FST Forecast
Segment
Data
Element
Position
ASC X12 Value
Record 4000 Source
Forecast Timing
Qualifier
681
FST03=
D (Day), W (Week), M (Month), Q (Quarter)
40 Detail Descriptor
(external)
Date (Start)
373
FST04=
<Starting Date>
50 Starting Date
Date (End)
(ONLY IF
BUFFER)
373
FST05=
<Ending Date>
60 Ending Date
Date/Time
Qualifier
374
FST06=
002
Standard for Delivery

Requested
Time
337
FST07=
n/a
Reference
Number Qualifier
128
FST08=
n/a
Reference
Number
127
FST09=
n/a
Table 8 31 Data Mapping of the REQUIREMENT Detail Category data to the FST segment when (Planned) Forecast
Quantity Zero
See Also
Running the EDI Outbound Planning and Shipping Schedules Extract
Program: page 8 51
Outbound Planning Schedule and Shipping Schedule Summary Tables:
page 8 53
8 46
Outbound Shipping Schedule (862 / DELJIT)

Use this transaction to communicate shortterm firm requirements and
shipping schedules to your suppliers. Shipping schedules are usually
stated in daily buckets and are used to refine planning schedules in
support of a JustinTime planning environment.
This transaction supersedes certain shipping and delivery information
transmitted in a previous planning schedule (830 transaction), but does
not replace it.
This transaction may not be used to authorize labor, material, or other
resources.
Application(s)
accessed
Oracle Supplier Scheduling, Oracle Purchasing,

Oracle Planning
ASC X12
Transaction
862
EDIFACT
Message
DELJIT
Prerequisite Setup in Oracle Applications

Oracle Supplier Scheduling
Create shipping schedules manually using the Schedulers Workbench
or automatically using AutoSchedule.
Define bucket patterns, enable CUM Accounting to track quantity
received by supplier site. Unlike a planning schedule (830 transaction),
the concept of authorizations does not apply to shipping schedules.
Use Scheduler Workbench or enable AutoConfirm option in
AutoSchedule to confirm your schedules. Only confirmed shipping
schedules may be transmitted via EDI to your supplier(s).
Oracle Purchasing
Supplier Scheduling uses components of Oracle Purchasing to calculate
and maintain schedules. Use the Approved Supplier list created in
Purchasing to establish a relationship between the shipto organization,
supplier site, and item.
Information related to approved purchase requisitions, approved supply
agreement releases, receipts from supplier, returns to supplier and
associated adjustments are used to determine the supplier requirement.
8 47
Oracle Planning
Supplier Scheduling also uses components of Oracle Planning to
calculate and maintain schedules. Use Sourcing Rules (which may be
created in Purchasing, Oracle Supply Chain Planning, or Supplier
Scheduling) to define how an item is replenished for a given
organization. This includes the ability to identify multiple supplier
sources, their percentage splits, and priority ranking.
Information related to unimplemented planned orders generated by
Planning via MPS, MRP, or DRP are used to determine the supplier
requirement.

Interface Tables
ECE_SPSO_HEADERS
ECE_SPSO_ITEMS
ECE_SPSO_ITEM_DEF
Extension Tables
ECE_SPSO_HEADERS_X
ECE_SPSO_ITEMS_X
ECE_SPSO_ITEM_DEF_X
Views
page 3 1.
ECE_SSSO_HEADERS_V
ECE_SSSO_ITEM_V
ECE_SSSO_ITEM_DET_V
8 48
See Also
Program: page 8 51
Outbound Shipping Schedule Data File Organization: page 8 50
8 49
Outbound Shipping Schedule Data File Organization

schedule, schedule line, and line details.
Each shipping schedule contains one schedule header record that
applies to the entire schedule. The schedule header is followed by one
or more schedule lines, each representing an item. Each schedule line is
followed by one or more line details representing requirements and the
items last and cumulative receipts.
The line details section includes the following:
Requirements
Up to 60 occurrences per the userdefined bucket

and planning horizon for the schedule.
Last Receipt
One occurrence identifying the quantity, date and

shipment number of the last receipt for the item.
Cumulative
Receipt
One occurrence identifying the cumulative receipt

quantity for the item if CUM accounting is enabled.

schedule header
schedule line
schedule line detail (cumulative receipt)
schedule line
schedule line detail (cumulative receipt)
See Also
Running the EDI Outbound Planning and Shipping Schedules Extract
Program: page 8 51
page 8 53
8 50
Running the EDI Outbound Planning and Shipping Schedule Extract Program
In addition to using EDI Gateway to transmit your planning or shipping
schedules, you may transmit the schedules using Supplier Schedulings
Scheduler Workbench or AutoSchedule process. With the Scheduler
Workbench, you select the schedules using the schedule ID. With
AutoSchedule, all built and confirmed schedules designated for EDI
transmission are sent if they were not previously sent.
Prerequisites



File: page 5 2.
"
To run the EDI Planning and Shipping Schedule extract program:

1.
2.
Select Request to submit the individual request.
3.
Select the EDI Planning or Shipping Schedule Outbound

transaction.
4.

criteria:
Specify an output data file name if you are not using the default.
Enter the schedule ID.
5.
6.
7.
8.
8 51
See Also
Outbound Planning Schedule: page 8 27
Outbound Shipping Schedule: page 8 47
Outbound Planning Schedule Data File Organization: page 8 30
Outbound Shipping Schedule Data File Organization: page 8 50
page 8 53
8 52
Outbound Planning Schedule and Shipping Schedule Summary

Tables
These two transactions share the same data file and so are documented
together.

Definition.
Records
Content
Occurrences
00100070
EDI Gateway Control Records
Only one record occurrence per transaction
10001900
Header Records
Only one record occurrence per transaction
20002900
Item Records
One set of records per item within the Planning Schedule header
40004900
Authorization Records
One records per forecast, authorization or receipt data per item
Record Summary
Seq.
Data
Data Level
Record
Number
Note
Control Record
CONTROL
0010
TRADING PARTNER
00200050
Basic Planning Schedule Header
PLANNING SCHEDULE HEADER
1000
Supplier Numbers
1010
Supplier Site Address/Code
1020
Supplier Site Phone
1030
Ship to Address/Code
1050
Ship to Miscellaneous Data
1060
10
Schedule Header Flex Fields
15001530
Flexfields
11
Supplier Flex Fields
16001630
Flexfields
Table 8 33
Flexfields
(Page 1 of 2)
8 53
Seq.
Data
Data Level
Record
Number
Note
12
Supplier Site Flex Fields
16501680
Flexfields
13
Shipping Organization Flex Fields
17001730
Flexfields
14
Ship To Options Flex Fields
17501780
Flexfields
15
Extension Tables:
PLANNING SCHEDULE ITEM
1900
(Custom)
Purchase Order Header Data
16
Basic Item Data
2000
17
Product Description
2010
18
Hazardous Material Codes
2020
19
Contact Names
2030
20
Last Receipt Data
2040
21
Ship To Organization Address/Code
2050
22
Ship To Organization Data
2060
23
Approved Supplier List Flex Fields
21002130
Flexfields
24
Item Flex Fields
21502180
Flexfields
25
Ship To Organization Flex Fields
22002230
Flexfields
26
Organization Option Flex Fields
22502280
Flexfields
27
Schedule Item Flex Fields
23002330
Flexfields
28
Extension Tables: Item Data
2900
(Custom)
29
Forecast and Authorization Data
PLANNING SCHEDULE AUTHORIZATION
4000
30
Extension Tables: Forecast and Authorization Data
PLANNING SCHEDULE AUTHORIZATION
4900
Table 8 33
(Page 2 of 2)

Position
Code
Content
125
TP_CD
2647
SP
Planning Schedule number
4869
ITEM
Planning Schedule line number
8 54
(Custom)
Position
Code
Content
7091
SCHEDULE
Schedule Bucket Number
9295
(varies)
Record Number
9697
(varies)
Record Layout
98100
(varies)

Seq.
Data
Trading
Partner
Reference 1
Reference
2
Reference 3
Record
Number
Record
Layout
Record
Layout
Qualifier
Length
25
22
22
22
4869
7091
Position
125
2647
9295
9697
98100
Control Record
TP_CD
SP
0010
CT
CTL
Trading Partner
Header Flexfields
TP_CD
SP
0020
A1
TH1
Trading Partner
Header Flexfields
TP_CD
SP
0030
A2
TH2
Trading Partner
Header Flexfields
TP_CD
SP
0040
A2
TH3
Trading Partner
Header Flexfields
TP_CD
SP
0050
A2
TH4
Planning Schedule
Header
TP_CD
SP
1000
HD
FRC
Planning Schedule
Header
TP_CD
SP
1010
SP
SU
10
Planning Schedule
Header
TP_CD
SP
1020
AD
SS
11
Planning Schedule
Header
TP_CD
SP
1030
CN
SS
12
Planning Schedule
Header
TP_CD
SP
1050
AX
ST1
13
Planning Schedule
Header
TP_CD
SP
1060
ST
ST2
14
Schedule Header
Flex Fields
TP_CD
SP
1500
A1
SH1
Table 8 35
(Page 1 of 3)
8 55
Seq.
Data
Trading
Partner
Reference 1
Reference
2
Reference 3
Record
Number
Record
Layout
Record
Layout
Qualifier
15
Schedule Header
Flex Fields
TP_CD
SP
15101530
A2
SH2SH4
16
TP_CD
SP
1600
A1
VN1
17
TP_CD
SP
16101630
A2
VN2VN4
18
Supplier Site Flex

Fields
TP_CD
SP
1650
A1
VS1
19
Supplier Site Flex

Fields
TP_CD
SP
16601680
A2
VS2VS4
20
Shipping
Organization Flex
Fields
TP_CD
SP
1700
A1
ST1
21
Shipping
Organization Flex
Fields
TP_CD
SP
17101730
A2
ST2ST4
22
Ship To Options Flex

Fields
TP_CD
SP
1750
A1
OP1
23
Ship To Options Flex

Fields
TP_CD
SP
17601780
A2
OP2OP4
24
Extension Tables:
Schedule Level
TP_CD
SP
1900
EX
25
Basic Item Data
TP_CD
SP
ITEM
2000
IT
IT1
26
Product Description
TP_CD
SP
ITEM
2010
IT
IT2
27
Hazardous Material
Data
TP_CD
SP
ITEM
2020
HZ
HZ1
28
Contact Names
TP_CD
SP
ITEM
2030
CN
IT1
29
Last Receipt Data
TP_CD
SP
ITEM
2040
LS
LS1
30
Ship to Organization
Address/Code
TP_CD
SP
ITEM
2050
AX
SI2
31
Data
TP_CD
SP
ITEM
2060
ST
SI3
32
Approved Supplier
List Flex Fields
TP_CD
SP
ITEM
2100
A1
AS1
33
Approved Supplier
List Flex Fields
TP_CD
SP
ITEM
21102130
A2
AS2AS4
34
Item Flex Fields
TP_CD
SP
ITEM
2150
A1
IT1
35
Item Flex Fields
TP_CD
SP
ITEM
21602180
A2
IT2IT4
36
Flex Fields (item)
TP_CD
SP
ITEM
2200
A1
DI1
Table 8 35
8 56
(Page 2 of 3)
Seq.
Data
Trading
Partner
Reference 1
Reference
2
Reference 3
Record
Number
Record
Layout
Record
Layout
Qualifier
37
Flex Fields (item)
TP_CD
SP
ITEM
22102230
A2
DI2DI4
38
Organization Option
Flex Fields
TP_CD
SP
ITEM
2250
A1
SO1
39
Organization Option
Flex Fields
TP_CD
SP
ITEM
22602280
A2
SO2SO4
40
Schedule Item Flex

Fields
TP_CD
SP
ITEM
2300
A1
SI1
41
Schedule Item Flex

Fields
TP_CD
SP
ITEM
23102330
A2
SI2SI4
42
Extension Tables:
Item Level
TP_CD
SP
ITEM
2900
EX
43
Forecast Dates,
Authorization,
TP_CD
SP
ITEM
SCHEDULE
4000
SC
TP_CD
SP
ITEM
SCHEDULE
4900
EX
SCH
Receipt Data
44
Extension Tables:
Forecast Level
Table 8 35
(Page 3 of 3)
8 57
Outbound Purchase Order (850 / ORDERS)

Use this transaction to procure goods and services from suppliers.
Approved purchase orders (POs), including standard POs, planned
orders, planned releases, blanket purchase agreement, and blanket
releases can be extracted.
Note: This transaction is not used to convey PO change or
acknowledgement information.
Application(s)
accessed
Oracle Purchasing
ASC X12
Transaction
850
EDIFACT
Message
ORDERS

Use Purchasing to convert purchase requisitions to POs or to create new
POs, planned orders, blanket purchase agreements or blanket releases.
Use Purchasing to approve POs before transmitting them to your
supplier.

Interface Tables
ECE_PO_INTERFACE_HEADERS
ECE_PO_INTERFACE_LINES
ECE_PO_INTERFACE_SHIPMENTS
Extension Tables
ECE_PO_INTERFACE_HEADERS_X
ECE_PO_INTERFACE_LINES_X
8 58
ECE_PO_INTERFACE_SHIPMENTS_X
Views
page 3 1.
ECE_POO_HEADERS_V
ECE_POO_LINES_V
ECE_POO_SHIPMENTS_V
See Also
Running the EDI Purchase Order Outbound Extract Program: page
8 59
Outbound Purchase Order Data File Organization: page 8 61
Running the EDI Purchase Order Outbound Extract Program

Prerequisites


File: page 5 2.
"
To run the EDI purchase order outbound extract program:

1.
8 59
2.
3.
Select the EDI Purchase Order Outbound transaction.
4.

criteria:
Specify an output data file name if you are not using the default.
Enter PO numbers From and To.
Enter PO creation dates From and To.
Enter the PO type.
Enter the supplier name and supplier site.
5.
6.
7.
8.
See Also
Outbound Purchase Order: page 8 58
Outbound Purchase Order Data File Organization: page 8 61
8 60
Outbound Purchase Order Data File Organization

header, line, and shipments.
Each purchase order contains one header record that applies to the
entire order. The PO header is followed by one or more PO lines, each
representing the item or service purchased. Each line is followed by one
or more shipments, each representing a specific shipment scheduled for
the line item.
With blanket purchase agreements, each agreement line price break is
stored at the PO shipment level. The unit price for items on a blanket
release are based on the shipment quantity. If the shipment quantity
does not qualify for a price break, the item master unit price is used.
purchase order header
purchase order line
purchase order shipment
purchase order line
purchase order line
Summary Tables

Definition.
Record Summary
Seq.
Data
Data Level
Common Control Record
CONTROL
TRADING PARTNER
Record
Number
Note
0010
00200050
Flexfields
Table 8 36
8 61
Seq.
Data
Data Level
Record
Number
Note
Purchase Order Basic Header
1000
Payment Terms
1010
Purchase Order Basic Header
1020
Purchase Order Notes to Supplier
1030
Purchase Order Flexfields
10401070
Flexfields
Supplier Flexfields
10801110
Flexfields
10
Supplier Site Flexfields
11201150
Flexfields
11
Supplier Site Address/Code
1160
12
Supplier Site Contacts
11701180
13
1190
14
Ship to Contacts
1200
15
Bill to Address/Code
1210
16
Bill to Contact
1220
17
Buyer Name
1230
18
Extension Tables:
Purchase Order Header Data
PURCHASE ORDER ITEM
1900
19
Basic Item Data
PURCHASE ORDER ITEM
2000
20
Basic Item Data
PURCHASE ORDER ITEM
2010
21
Basic Item Data,

Hazardous Material Codes
PURCHASE ORDER ITEM
2020
22
Item Note to Supplier
PURCHASE ORDER ITEM
2030
23
Line Flexfields
PURCHASE ORDER ITEM
20402070
Flexfields
24
PURCHASE ORDER ITEM
20802110
Flexfields
25
Extension Tables:
Purchase Order Item Data
PURCHASE ORDER ITEM
2900
(Custom)
26
Basic Shipment Data
PURCHASE ORDER SHIPMENT
3000
27
Shipment Flexfields
30103040
28
Ship To Address/Code
3050
29
Ship To Contact
3060
30
Extension Tables:
Purchase Order Item Data
3900
Table 8 36
8 62
(Custom)
Flexfields
(Custom)
Transaction Specific Data in the Common Key
Position
Code
Content
125
TP_CD
Trading Partner Code as defined in

the EDI Translator
2647
PO
4869
ITEM
Item number
7091
SHIPMENT
Shipment Number
Table 8 37

Seq.
Data
Trading
Partner
Reference 1
Reference 2
Reference 3
Record
Number
Record
Layout
Record
Layout
Qualifier
Length
25
22
22
22
Position
125
2647
4869
7091
9295
9697
98100
Control Record
TP_CD
PO
0010
CT
CTL
Trading Partner
Header
Flexfields
TP_CD
PO
0020
A3
TH1
Trading Partner
Header
Flexfields
TP_CD
PO
0030
A4
TH2
Trading Partner
Header
Flexfields
TP_CD
PO
0040
A4
TH3
Trading Partner
Header
Flexfields
TP_CD
PO
0050
A4
TH4
Purchase Order
Basic Header
TP_CD
PO
1000
PO
PO1
Payment Terms
TP_CD
PO
1010
PO
PO2
10
Purchase Order
Basic Header
TP_CD
PO
1020
PO
PO3
Table 8 38
(Page 1 of 4)
8 63
Seq.
Data
Trading
Partner
Reference 1
Reference 2
Reference 3
Record
Number
Record
Layout
Record
Layout
Qualifier
11
Purchase Order
Notes to
Supplier
TP_CD
PO
1030
PO
PO4
12
Purchase Order
Flexfields
TP_CD
PO
1040
A1
PO1
13
Purchase Order
Flexfields
TP_CD
PO
1050
A2
PO2
14
Purchase Order
Flexfields
TP_CD
PO
1060
A2
PO3
15
Purchase Order
Flexfields
TP_CD
PO
1070
A2
PO4
16
Supplier
Flexfields
TP_CD
PO
1080
A1
SU1
17
Supplier
Flexfields
TP_CD
PO
1090
A2
SU2
18
Supplier
Flexfields
TP_CD
PO
1100
A2
SU3
19
Supplier
Flexfields
TP_CD
PO
1110
A2
SU4
20
Supplier Site
Flexfields
TP_CD
PO
1120
A1
SS1
21
Supplier Site
Flexfields
TP_CD
PO
1130
A2
SS2
22
Supplier Site
Flexfields
TP_CD
PO
1140
A2
SS3
23
Supplier Site
Flexfields
TP_CD
PO
1150
A2
SS4
24
Supplier Site
Address
TP_CD
PO
1160
AD
SU1
25
Supplier Site
Contact
TP_CD
PO
1170
CN
SS1
26
Supplier Site
Contact
TP_CD
PO
1180
CN
SS2
27
Ship to
Address/Code
TP_CD
PO
1190
AX
ST1
28
Ship to Contacts
TP_CD
PO
1200
CN
ST1
29
Bill to
Address/Code
TP_CD
PO
1210
AX
BT1
Table 8 38
8 64
(Page 2 of 4)
Seq.
Data
Trading
Partner
Reference 1
Reference 2
Reference 3
Record
Number
Record
Layout
Record
Layout
Qualifier
30
Bill to Contact
TP_CD
PO
1220
CN
BT1
29
Buyer Name
TP_CD
PO
1230
PO
PO5
30
Extension
Tables:
Purchase Order
Header Data
TP_CD
PO
1900
31
Basic Item Data
TP_CD
PO
ITEM
2000
IT
IT1
32
Basic Item Data
TP_CD
PO
ITEM
2010
IT
IT2
33
Basic Item Data,

Hazardous
Material Codes
TP_CD
PO
ITEM
2020
IT
IT3
34
Item Note to
Supplier
TP_CD
PO
ITEM
2030
IT
IT4
35
Line Flexfields
TP_CD
PO
ITEM
2040
A1
LN1
36
Line Flexfields
TP_CD
PO
ITEM
2050
A2
LN2
37
Line Flexfields
TP_CD
PO
ITEM
2060
A2
LN3
38
Line Flexfields
TP_CD
PO
ITEM
2070
A2
LN4
39
Line Part
Flexfields
TP_CD
PO
ITEM
2080
A1
LP1
40
Line Part
Flexfields
TP_CD
PO
ITEM
2090
A2
LP2
41
Line Part
Flexfields
TP_CD
PO
ITEM
2100
A2
LP3
42
Line Part
Flexfields
TP_CD
PO
ITEM
2110
A2
LP4
43
Extension
Tables:
Purchase Order
Item Data
TP_CD
PO
ITEM
2900
44
Basic Shipment
Data
TP_CD
PO
ITEM
SHIPMENT
3000
SH
SH1
45
Shipment
Flexfields
TP_CD
PO
ITEM
SHIPMENT
3010
A1
SH1
46
Shipment
Flexfields
TP_CD
PO
ITEM
SHIPMENT
3020
A2
SH2
47
Shipment
Flexfields
TP_CD
PO
ITEM
SHIPMENT
3030
A2
SH3
Table 8 38
(Custom)
(Custom)
(Page 3 of 4)
8 65
Seq.
Data
Trading
Partner
Reference 1
Reference 2
Reference 3
Record
Number
Record
Layout
Record
Layout
Qualifier
48
Shipment
Flexfields
TP_CD
PO
ITEM
SHIPMENT
3040
A2
SH4
49
Ship To
Address/Code
TP_CD
PO
ITEM
SHIPMENT
3050
AX
SL1
50
Ship To Contact
TP_CD
PO
ITEM
SHIPMENT
3060
CN
51
Extension
Tables:
Purchase Order
Shipment Data
TP_CD
PO
ITEM
SHIPMENT
3900
Table 8 38
8 66
(Page 4 of 4)
SL1
(Custom)
Outbound Purchase Order Change Request (860 / ORDCHG)

Use this transaction to request a change to a previously submitted
purchase order (PO). You may include changes for approved POs of the
type standard POs, planned POs, planned releases, blanket purchase
agreements, and blanket releases.
Application(s)
accessed
Oracle Purchasing
ASC X12
Transaction
860
EDIFACT
Message
ORDCHG
Supported changes by this transaction include:

cancel line
add line
change price
change quantity
change shipto location
change shipment date
change shipment quantity
Cancelling a PO at the header level cancels every line associated with
the PO. New lines are appended to the end; old line numbers are not
reused.
To maintain shipment data integrity, all shipment information associated
with a PO line are sent to the supplier, even if changes were made to
only one shipment.
Note: Check with the trading partner to verify their ability to
process any type of change.

Use Purchasing to change an existing purchase order or blanket
purchase agreement. You may cancel a line, add a line, change the line
price or quantity, change the shipto location, or shipment date or
quantity.
If your Purchasing system option is set to Archive on Approval, you
must reapprove changed POs before transmitting them to your supplier.
8 67
See: Running the EDI Purchase Order Change Request Outbound

Extract Program: page 8 69.

Interface Tables
ECE_PO_INTERFACE_HEADERS
ECE_PO_INTERFACE_LINES
ECE_PO_INTERFACE_SHIPMENTS
Extension Tables
ECE_PO_INTERFACE_HEADERS_X
ECE_PO_INTERFACE_LINES_X1
ECE_PO_INTERFACE_SHIPMENTS_X
Views
page 3 1.
ECE_POCO_HEADERS_V
ECE_POCO_LINES_V
ECE_POCO_SHIPMENTS_V
See Also
Running the EDI Outbound Purchase Order Change Request Extract
Program: page 8 69
Outbound Purchase Order Change Request Data File Organization:
page 8 61
8 68
Running the EDI Outbound Purchase Order Change Request

Prerequisites


File: page 5 2.
"
To run the EDI Purchase Order Change extract program:

1.
2.
3.
Select the EDI PO Change Outbound transaction.
4.

criteria:
Enter the output file name if you are not using the default.
Enter the PO number From and To.
Enter the PO creation (or revision) date From and To.
Enter the PO type.
Enter the supplier and supplier site.
5.
6.
7.
8.
8 69
See Also
Outbound Purchase Order Change Request: page 8 67
Outbound Purchase Order Change Request Data File Organization:
page 8 61
8 70
Outbound Purchase Order Change Request Data File Organization

header, line, and shipments.
Each PO contains one header record that applies to the entire order. The
PO header is followed by one or more PO lines, each representing the
item or service purchased. Each line is followed by one or more
shipments, each representing a specific shipment scheduled for the line
item.
purchase order header
purchase order line
purchse order shipment
purchase order line
purchase order line
purchse order shipment
Summary Tables

Definition.

Records
Content
Occurrences
00100070
EDI Gateway Control

Records

per transaction
10001900
PO Header Records

per transaction
20002900
PO Item Records

within the PO header
30003900
PO Shipment Records
One set of records per schedule within the PO item
8 71
Record Summary
Seq.
Data
Data Level
Record
Number
Control Record
CONTROL
0010

Flexfields
TRADING PARTNER
00200050
Purchase Order Basic

Header
1000
Payment Terms
1010

Header
1020
Purchase Order Notes to

Supplier
1030
Purchase Order
Flexfields
10401070
Flexfields
Supplier Flexfields
10801110
Flexfields
10
11201150
Flexfields
11
Supplier Site Address/

Code
1160
12
Supplier Site Contacts
11701180
13
1190
14
Ship to Contacts
1200
15
1210
16
Bill to Contact
1220
17
Buyer Name
1230
18
Extension Tables: PO
Header Data
PURCHASE ORDER ITEM
1900
19
Basic Item Data
PURCHASE ORDER ITEM
2000
20
Basic Item Data
PURCHASE ORDER ITEM
2010
21
Basic Item Data: Hazardous Material Codes
PURCHASE ORDER ITEM
2020
Table 8 40
8 72
Note
Flexfields
(Custom)
Seq.
Data
Data Level
Record
Number
Note
22
PURCHASE ORDER ITEM
2030
23
Line Flexfields
PURCHASE ORDER ITEM
20402070
Flexfields
24
PURCHASE ORDER ITEM
20802110
Flexfields
25
Item Data
PURCHASE ORDER ITEM
2900
(Custom)
26
Basic Shipment Data
3000
27
Shipment Flexfields
30103040
28
3050
29
Ship To Contact
3060
30
Extension Tables:PO
Item Data
3900
Flexfields
(Custom)
Table 8 40
Transactionspecific Data in the Common Key positions 1100

Position
Code
Content
125
TP_CD

Translator
2647
PO
4869
ITEM
Purchase order line number
7091
SHIPMENT
Shipment Number
9295
(varies)
Record Number
9697
(varies)
Record Layout
98100
(varies)
8 73

Seq.
Data
Length
Position
Trading
Partner
Reference
1
Reference
2
Reference 3
Record
Number
Record
Layout
Record
Layout
Qualifier
25
22
22
22
125
2647
4869
7091
9295
9697
98100
Control Record
TP_CD
PO
0010
CT
CTL

Flexfields
TP_CD
PO
0020
A3
TH1

Flexfields
TP_CD
PO
0030
A4
TH2

Flexfields
TP_CD
PO
0040
A4
TH3

Flexfields
TP_CD
PO
0050
A4
TH4

Header
TP_CD
PO
1000
PO
PO1
Payment Terms
TP_CD
PO
1010
PO
PO2
10

Header
TP_CD
PO
1020
PO
PO3
11
Purchase Order Notes

to Supplier
TP_CD
PO
1030
PO
PO4
12
Purchase Order
Flexfields
TP_CD
PO
1040
A1
PO1
13
Purchase Order
Flexfields
TP_CD
PO
1050
A2
PO2
14
Purchase Order
Flexfields
TP_CD
PO
1060
A2
PO3
15
Purchase Order
Flexfields
TP_CD
PO
1070
A2
PO4
16
Supplier Flexfields
TP_CD
PO
1080
A1
SU1
17
Supplier Flexfields
TP_CD
PO
1090
A2
SU2
18
Supplier Flexfields
TP_CD
PO
1100
A2
SU3
19
Supplier Flexfields
TP_CD
PO
1110
A2
SU4
20
TP_CD
PO
1120
A1
SS1
21
TP_CD
PO
1130
A2
SS2
22
TP_CD
PO
1140
A2
SS3
23
TP_CD
PO
1150
A2
SS4
24
Supplier Site Address
TP_CD
PO
1160
AD
SU1
Table 8 42
8 74
(Page 1 of 3)
Seq.
Data
Trading
Partner
Reference
1
25
Supplier Site Contact
TP_CD
26
Supplier Site Contact
27
28
Record
Number
Record
Layout
Record
Layout
Qualifier
PO
1170
CN
SS1
TP_CD
PO
1180
CN
SS2
Ship to Address/Code
TP_CD
PO
1190
AX
ST1
Ship to Contacts
TP_CD
PO
1200
CN
ST1
29
TP_CD
PO
1210
AX
BT1
30
Bill to Contact
TP_CD
PO
1220
CN
BT1
29
Buyer Name
TP_CD
PO
1230
PO
PO5
30
Extension Tables:PO
Header Data
TP_CD
PO
1900
31
Basic Item Data
TP_CD
PO
ITEM
2000
IT
IT1
32
Basic Item Data
TP_CD
PO
ITEM
2010
IT
IT2
33
Basic Item Data

Hazardous Material
Codes
TP_CD
PO
ITEM
2020
IT
IT3
34
TP_CD
PO
ITEM
2030
IT
IT4
35
Line Flexfields
TP_CD
PO
ITEM
2040
A1
LN1
36
Line Flexfields
TP_CD
PO
ITEM
2050
A2
LN2
37
Line Flexfields
TP_CD
PO
ITEM
2060
A2
LN3
38
Line Flexfields
TP_CD
PO
ITEM
2070
A2
LN4
39
TP_CD
PO
ITEM
2080
A1
LP1
40
TP_CD
PO
ITEM
2090
A2
LP2
41
TP_CD
PO
ITEM
2100
A2
LP3
42
TP_CD
PO
ITEM
2110
A2
LP4
43
Item Data
TP_CD
PO
ITEM
2900
44
Basic Shipment Data
TP_CD
PO
ITEM
SHIPMENT
3000
SH
SH1
45
Shipment Flexfields
TP_CD
PO
ITEM
SHIPMENT
3010
A1
SH1
46
Shipment Flexfields
TP_CD
PO
ITEM
SHIPMENT
3020
A2
SH2
47
Shipment Flexfields
TP_CD
PO
ITEM
SHIPMENT
3030
A2
SH3
48
Shipment Flexfields
TP_CD
PO
ITEM
SHIPMENT
3040
A2
SH4
49
TP_CD
PO
ITEM
SHIPMENT
3050
AX
SL1
Table 8 42
Reference
2
Reference 3
(Custom)
(Custom)
(Page 2 of 3)
8 75
Seq.
Data
Trading
Partner
Reference
1
Reference
2
Reference 3
Record
Number
Record
Layout
Record
Layout
Qualifier
50
Ship To Contact
TP_CD
PO
ITEM
SHIPMENT
3060
CN
SL1
51
Shipment Data
TP_CD
PO
ITEM
SHIPMENT
3900
Table 8 42
8 76
(Page 3 of 3)
(Custom)
Outbound Ship Notice / Manifest (856 / DESADV)

Use this transaction to list the contents of a shipment including
departure and delivery data such as carrier, parties involved with the
shipment, container, order; product data such as description, physical
characteristics, type of packaging, lot and serial numbers; and
allowances and charges.
This transaction is initiated by the shipping application or by EDI
Gateway if necessary.
Application(s)
accessed
Oracle Order Entry / Shipping
ASC X12
Transaction
856
EDIFACT
Message
DESADV
Prerequisite Setup in Oracle Order Entry

Use Oracle Order Entry to enter and maintain customer orders.
Alternately, Order Entrys OrderImport can be used to import customer
orders from nonOracle order management systems and EDI
transactions.
After the customer order is entered, use Order Entry to book, approve,
and schedule shipments. During the shipment preparation process,
inventory is released, pick slips are printed, shipping documents are
prepared, and the shipment is confirmed.
Once the shipment is confirmed, define a departure to specify the exact
contents. A departure may be a truck load containing x number of items
in y number of boxes defined and in z number of pallets.
After the departure is closed, the shipping process initiates the EDI
transaction through the EDI Gateway. This transaction is eventdriven
by the shipping process; it is not driven by the schedule. EDI Gateway
can be used to reinitiate the process, if necessary.

8 77
Interface Tables
ECE_DSNO_ALLOWANCE_CHARGES
ECE_DSNO_CONTAINERS
ECE_DSNO_DELIVERIES
ECE_DSNO_DELIVERY_ATTRIBS
ECE_DSNO_ITEMS
ECE_DSNO_ITEM_DETAILS
ECE_DSNO_ORDERS
Extension Tables
ECE_DSNO_ALLOWANCE_CHARGES_X
ECE_DSNO_CONTAINERS_X
ECE_DSNO_DELIVERIES_X
ECE_DSNO_DELIVERY_ATTRIBS_X
ECE_DSNO_ITEMS_X
ECE_DSNO_ITEM_DETAILS_X
ECE_DSNO_ORDERS_X
Views
page 3 1.
ECE_DSNO_ALLOWANCE_CHARGES_V
ECE_DSNO_CONTAINERS_V
ECE_DSNO_DELIVERIES_V
ECE_DSNO_DELIVERY_ATTRIBS_V
ECE_DSNO_ITEMS_V
ECE_DSNO_ITEM_DETAILS_V
ECE_DSNO_ORDERS_V
8 78
See Also
Running the EDI Ship Notice / Manifest Outbound Extract Program:
page 8 79.
Outbound Ship Notice / Manifest File Organization: page 8 81
Running the EDI Ship Notice / Manifest Outbound Extract Program

Prerequisites


File: page 5 2.
"
To run the EDI Ship Notice / Manifest outbound extract program:

Note: Performing this procedure from EDI Gateway is only
necessary if you need to rerun the extract.
1.
2.
3.
Select the EDI Ship Notice Out request.
4.
In the Parameters window, enter the following:

Enter the departure identifier.
Enter the temporary output path and file name.
Enter the actual output path and file name.
5.
6.
8 79
7.
8.
See Also
Outbound Ship Notice / Manifest: page 8 77
Outbound Ship Notice / Manifest Data File Organization: page 8 81
8 80
Outbound Ship Notice / Manifest Data File Organization

The data file produced by this transaction consists of seven levels of
data: delivery, delivery allowance / charges, containers, orders, items,
item allowance / charges, and item details.
Each data file contains all deliveries on the departure. A complete ship
notice is generated for each delivery. Each delivery contains both data
specific to that delivery and departure information that applies to all
deliveries on the departure. The delivery level is followed by any
allowance / charge lines that relate to the entire delivery.
Next, any loose items not in containers are represented as one or more
orders, items, item allowance / charges, and item detail records.
Finally, containers on the delivery are processed, beginning with the
outermost container and continuing with inner containers. Each
container is completely processed, listing the contents as a series of
orders, items, item allowance / charges, and item details. Since
containers may be nested to any level, processing continues in this
manner until no more containers are found. Each outer container is
completely processed, including all levels of nested containers, before
moving on to the next outer container.
Each ship notice transaction contains one set of records at the header
level, including departure data, delivery data, and all location codes and
their applicable flexfields.
The shipment header is followed by one or more sets of container data
within the delivery.
Each container consists of items from one or more purchase orders.
Within the specific purchase order, all included shipped items are listed.
Each item may have a set of item detail records for the lot or serial
numbers, and a set of allowance and charge records, if they apply. Both
the item detail and allowance / charge records are optional.
Delivery
Delivery allowance / charges (if present)
Orders: loose items (if present)
Items: loose (if present)
Item allowance/charges: loose items (if present)
Item details: loose items (if present)
8 81
Containers: outer
Orders
Items
Item allowance / charges (if present)
Item details
Containers: inner
Summary Tables

Definition.
Record Summary
Seq.
Data
Data Level
Record
Number
Note
Control Record
CONTROL
0010
TRADING PARTNER
00200050
Warehouse Address
SHIPMENT
1000
Warehouse Contact data
SHIPMENT
1010
Warehouse Flexfields Data
SHIPMENT
10201060
Pooled Address Data
SHIPMENT
1200
Pooled Contact Data
SHIPMENT
1210
Destination Address
SHIPMENT
1300
10
Destination Contact
SHIPMENT
1310
11
Destination Flexfields
SHIPMENT
13201350
12
Consignee Address Data
SHIPMENT
1360
13
Consignee Contact Data
SHIPMENT
1370
14
Customer Flexfields
SHIPMENT
13801410
Flexfields
15
Customer Global Flexfields
SHIPMENT
14201460
Flexfields
16
Departure Data
SHIPMENT
2000
17
Departure Data
SHIPMENT
2010
Table 8 43
8 82
Flexfields
Flexfields
Seq.
Data
Data Level
Record
Number
Note
Flexfields
18
Departure Flexfields
SHIPMENT
20202050
19
Delivery data
SHIPMENT
3000
20
Delivery data
SHIPMENT
3010
21
Delivery Flexfields
SHIPMENT
30203050
22
Extension Tables Picking level
SHIPMENT
3900
23
Allowance/Charge data
SHIPMENT
4000
24
Shipment Allowance/Charge Flexfields
SHIPMENT
40104040
25
Extension Tables A/C data
SHIPMENT
4900
26
Container Data
TARE
5000
27
Container Flexfields
TARE
50105040
28
Extension Tables Container level
TARE
5900
29
Purchase Order Data
ORDER
6000
30
Purchase Order Data
ORDER
6010
31
Purchase Order Data (Payment Terms

Data, Currency)
ORDER
6020
32
Purchase Order Data (FOB Data)
ORDER
6030
33
Shipping & Packing Instructions
ORDER
6040
34
Order By Address, Data
ORDER
6050
35
Order By Contact Data
ORDER
6060
36
Invoice Address Data
ORDER
6070
37
Invoice Contact Data
ORDER
6080
38
Picking Header Flexfields
ORDER
61006130
Flexfields
39
Order Header Flexfields
ORDER
62006230
Flexfields
40
Order Header Global Flexfields
ORDER
63006340
Flexfields
41
Extension Tables : Order level
ORDER
6900
42
Item Data
ITEM
7000
43
Item Data
ITEM
7010
44
Item Data
ITEM
7020
45
Item Data
ITEM
7030
46
Hazardous Data
ITEM
7040
47
Industry Data (if exist)
ITEM
(7100)
48
Order Line Pricing Flexfields
ITEM
72007230
Flexfields
Flexfields
Flexfields
Flexfields
Table 8 43
8 83
Seq.
Data
Data Level
Record
Number
Note
49
Order Line Flexfields
ITEM
72407270
Flexfields
50
Order line Detail Flexfields
ITEM
72807310
Flexfields
51
Order Line Global Flexfields
ITEM
73207360
Flexfields
52
Order Line Detail Global Flexfields
ITEM
73707410
Flexfields
53
Picking Line Flexfields
ITEM
74207450
Flexfields
54
ITEM
74607490
Flexfields
55
Container Contents Flexfields
ITEM
75007530
Flexfields
56
Order Line Industry Flexfields
ITEM
76007630
Flexfields
57
Extension Tables Item level
ITEM
7900
58
Allowance/Charge Line item
ITEM
8000
59
Item Allowance/Charge Flexfields
ITEM
80108040
60
Extension ITEM level A/C data
ITEM
8900
61
Lot , serial, production sequence
ITEM DETAIL
9000
62
Picking Line Detail Flexfields
ITEM DETAIL
90109040
63
Extension Table: item detail
ITEM DETAIL
9900
Flexfields
Flexfields
Table 8 43
Transactionspecific Data in the Common Key

Position
Code
Content
125
TP_CD
2647
DELIVERY
Delivery Name
4869
SO
Sales Order Number
7091
ITEM
Supplier Part Number
Table 8 44
8 84
Seq.
Record
Data Level
TP_CD
Reference
1
Reference
2
Reference
3
Record
Number
Record
Layout
Record
Layout
Qualifier
Length
25
22
22
22
Position
125
2647
4869
7091
9295
9697
98100
Common
Control
Record
CONTROL
TP_CD
DELIVERY
0010
CT
CTL
Trading
Partner
Header
Flexfields
TRADING
PARTNER
TP_CD
DELIVERY
0020
A3
TH1
Trading
Partner
Header
Flexfields
TRADING
PARTNER
TP_CD
DELIVERY
0030
A4
TH2
Trading
Partner
Header
Flexfields
TRADING
PARTNER
TP_CD
DELIVERY
0040
A3
TH3
Trading
Partner
Header
Flexfields
TRADING
PARTNER
TP_CD
DELIVERY
0050
A4
TH4
Warehouse
Address
SHIPMENT
TP_CD
DELIVERY
1000
AD
SF
Warehouse
Contact
Data
SHIPMENT
TP_CD
DELIVERY
1010
CN
SF
10
Warehouse
Flexfields
SHIPMENT
TP_CD
DELIVERY
1020
A1
SF1
11
Warehouse
Flexfields
SHIPMENT
TP_CD
DELIVERY
1030
A2
SF2
12
Warehouse
Flexfields
SHIPMENT
TP_CD
DELIVERY
1040
A2
SF3
13
Warehouse
Flexfields
SHIPMENT
TP_CD
DELIVERY
1050
A2
SF4
14
Warehouse
Flexfields
SHIPMENT
TP_CD
DELIVERY
1060
A2
SF5
Table 8 45
(Page 1 of 10)
8 85
Seq.
Record
Data Level
TP_CD
Reference
1
Reference
2
Reference
3
Record
Number
Record
Layout
Record
Layout
Qualifier
15
Pooled
Address
Data
SHIPMENT
TP_CD
DELIVERY
1200
AD
IC
16
Pooled
Contact
Data
SHIPMENT
TP_CD
DELIVERY
1210
CN
IC
17
Destination
Address
SHIPMENT
TP_CD
DELIVERY
1300
AD
ST
18
Destination
Contact
SHIPMENT
TP_CD
DELIVERY
1310
CN
ST
19
Destination
Flexfields
SHIPMENT
TP_CD
DELIVERY
1320
A1
ST1
20
Destination
Flexfields
SHIPMENT
TP_CD
DELIVERY
1330
A2
ST2
21
Destination
Flexfields
SHIPMENT
TP_CD
DELIVERY
1340
A2
ST3
22
Destination
Flexfields
SHIPMENT
TP_CD
DELIVERY
1350
A2
ST4
23
Consignee
Address
Data
SHIPMENT
TP_CD
DELIVERY
1360
AD
CSG
24
Consignee
Contact
Data
SHIPMENT
TP_CD
DELIVERY
1370
CN
CSG
25
Customer
Flexfields
SHIPMENT
TP_CD
DELIVERY
1380
A1
CU1
26
Customer
Flexfields
SHIPMENT
TP_CD
DELIVERY
1390
A2
CU2
27
Customer
Flexfields
SHIPMENT
TP_CD
DELIVERY
1400
A2
CU3
28
Customer
Flexfields
SHIPMENT
TP_CD
DELIVERY
1410
A2
CU4
29
Customer
Global
Flexfields
SHIPMENT
TP_CD
DELIVERY
1420
A1
CG1
30
Customer
Global
Flexfields
SHIPMENT
TP_CD
DELIVERY
1430
A2
CG2
Table 8 45
8 86
(Page 2 of 10)
Seq.
Record
Data Level
TP_CD
Reference
1
Reference
2
Reference
3
Record
Number
Record
Layout
Record
Layout
Qualifier
31
Customer
Global
Flexfields
SHIPMENT
TP_CD
DELIVERY
1440
A2
CG3
32
Customer
Global
Flexfields
SHIPMENT
TP_CD
DELIVERY
1450
A2
CG4
33
Customer
Global
Flexfields
SHIPMENT
TP_CD
DELIVERY
1460
A2
CG5
34
Departure
Data
SHIPMENT
TP_CD
DELIVERY
2000
D1
DP1
35
Departure
Data
SHIPMENT
TP_CD
DELIVERY
2010
D2
DP2
36
Departure
Flexfields
SHIPMENT
TP_CD
DELIVERY
2020
A1
DP1
37
Departure
Flexfields
SHIPMENT
TP_CD
DELIVERY
2030
A2
DP2
38
Departure
Flexfields
SHIPMENT
TP_CD
DELIVERY
2040
A2
DP3
39
Departure
Flexfields
SHIPMENT
TP_CD
DELIVERY
2050
A2
DP4
40
Delivery
data
SHIPMENT
TP_CD
DELIVERY
3000
L1
DL1
41
Delivery
data
SHIPMENT
TP_CD
DELIVERY
3010
L2
DL2
42
Delivery
Flexfields
SHIPMENT
TP_CD
DELIVERY
3020
A1
DL1
43
Delivery
Flexfields
SHIPMENT
TP_CD
DELIVERY
3030
A2
DL2
44
Delivery
Flexfields
SHIPMENT
TP_CD
DELIVERY
3040
A2
DL3
45
Delivery
Flexfields
SHIPMENT
TP_CD
DELIVERY
3050
A2
DL4
46
Extension
Tables
Picking
level
SHIPMENT
TP_CD
DELIVERY
3900
SH
EX
Table 8 45
(Page 3 of 10)
8 87
Seq.
Record
Data Level
TP_CD
Reference
1
Reference
2
Reference
3
Record
Number
Record
Layout
Record
Layout
Qualifier
47
Allowance
/Charge
Data
SHIPMENT
TP_CD
DELIVERY
4000
AC
HA1
48
Shipment
Allowance
/Charge
Flexfields
SHIPMENT
TP_CD
DELIVERY
4010
A5
HA2
49
Shipment
Allowance
/Charge
Flexfields
SHIPMENT
TP_CD
DELIVERY
4020
A6
HA3
50
Shipment
Allowance
/Charge
Flexfields
SHIPMENT
TP_CD
DELIVERY
4030
A6
HA4
51
Shipment
Allowance
/Charge
Flexfields
SHIPMENT
TP_CD
DELIVERY
4040
A6
HA5
52
Extension
Tables A/C
data
SHIPMENT
TP_CD
DELIVERY
4900
AS
EX
53
Container
Data
TARE
TP_CD
DELIVERY
5000
TR
54
Container
Flexfields
TARE
TP_CD
DELIVERY
5010
A1
CT1
55
Container
Flexfields
TARE
TP_CD
DELIVERY
5020
A2
CT2
56
Container
Flexfields
TARE
TP_CD
DELIVERY
5030
A2
CT3
57
Container
Flexfields
TARE
TP_CD
DELIVERY
5040
A2
CT4
58
Extension
Tables
Container
level
TARE
TP_CD
DELIVERY
5900
CN
EX
59
Purchase
Order Data
ORDER
TP_CD
DELIVERY
SO
6000
P1
PO1
60
Purchase
Order Data
ORDER
TP_CD
DELIVERY
SO
6010
P2
PO2
Table 8 45
8 88
(Page 4 of 10)
Seq.
Record
Data Level
TP_CD
Reference
1
Reference
2
Reference
3
Record
Number
Record
Layout
Record
Layout
Qualifier
61
Purchase
Order Data
(Payment
Terms
Data,
Currency)
ORDER
TP_CD
DELIVERY
SO
6020
P2
PO3
62
Purchase
Order Data
(FOB Data)
ORDER
TP_CD
DELIVERY
SO
6030
P4
PO4
63
Shipping &
Packing
Instructions
ORDER
TP_CD
DELIVERY
SO
6040
NT
INS
64
Order By
Address,
Data
ORDER
TP_CD
DELIVERY
SO
6050
AD
ISS
65
Order By
Contact
Data
ORDER
TP_CD
DELIVERY
SO
6060
CN
ISS
66
Invoice
Address
Data
ORDER
TP_CD
DELIVERY
SO
6070
AD
BT
67
Invoice
Contact
Data
ORDER
TP_CD
DELIVERY
SO
6080
CN
BT
68
Picking
Header
Flexfields
ORDER
TP_CD
DELIVERY
SO
6100
A1
PH1
69
Picking
Header
Flexfields
ORDER
TP_CD
DELIVERY
SO
6110
A2
PH2
70
Picking
Header
Flexfields
ORDER
TP_CD
DELIVERY
SO
6120
A2
PH3
71
Picking
Header
Flexfields
ORDER
TP_CD
DELIVERY
SO
6130
A2
PH4
72
Order
Header
Flexfields
ORDER
TP_CD
DELIVERY
SO
6200
A1
OR1
73
Order
Header
Flexfields
ORDER
TP_CD
DELIVERY
SO
6210
A2
OR2
Table 8 45
(Page 5 of 10)
8 89
Seq.
Record
Data Level
TP_CD
Reference
1
Reference
2
Reference
3
Record
Number
Record
Layout
Record
Layout
Qualifier
74
Order
Header
Flexfields
ORDER
TP_CD
DELIVERY
SO
6220
A2
OR3
75
Order
Header
Flexfields
ORDER
TP_CD
DELIVERY
SO
6230
A2
OR4
76
Order
Header
Global
Flexfields
ORDER
TP_CD
DELIVERY
SO
6300
A1
HG1
77
Order
Header
Global
Flexfields
ORDER
TP_CD
DELIVERY
SO
6310
A2
HG2
78
Order
Header
Global
Flexfields
ORDER
TP_CD
DELIVERY
SO
6310
A2
HG3
79
Order
Header
Global
Flexfields
ORDER
TP_CD
DELIVERY
SO
6320
A2
HG4
80
Order
Header
Global
Flexfields
ORDER
TP_CD
DELIVERY
SO
6340
A2
HG5
81
Extension
Tables :
Order level
ORDER
TP_CD
DELIVERY
SO
6900
OR
EX
82
Item Data
ITEM
TP_CD
DELIVERY
SO
ITEM
7000
I1
IT1
83
Item Data
ITEM
TP_CD
DELIVERY
SO
ITEM
7010
I2
IT2
84
Item Data
ITEM
TP_CD
DELIVERY
SO
ITEM
7020
I3
IT3
85
Item Data
ITEM
TP_CD
DELIVERY
SO
ITEM
7030
I4
IT4
86
Hazardous
Data
ITEM
TP_CD
DELIVERY
SO
ITEM
7040
HZ
HZ1
87
Industry
Data (if
exist)
ITEM
TP_CD
DELIVERY
SO
ITEM
(7100)
IN
IND
88
Order Line
Pricing
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7200
A1
PR1
Table 8 45
8 90
(Page 6 of 10)
Seq.
Record
Data Level
TP_CD
Reference
1
Reference
2
Reference
3
Record
Number
Record
Layout
Record
Layout
Qualifier
89
Order Line
Pricing
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7210
A2
PR2
90
Order Line
Pricing
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7220
A2
PR3
91
Order Line
Pricing
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7230
A2
PR4
92
Order Line
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7240
A1
LI1
93
Order Line
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7250
A2
LI2
94
Order Line
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7260
A2
LI3
95
Order Line
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7270
A2
LI4
96
Order line
Detail
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7280
A1
LD1
97
Order line
Detail
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7290
A2
LD2
98
Order line
Detail
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7300
A2
LD3
99
Order line
Detail
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7310
A2
LD4
100
Order Line
Global
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7320
A1
LG1
101
Order Line
Global
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7330
A2
LG2
102
Order Line
Global
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7340
A2
LG3
Table 8 45
(Page 7 of 10)
8 91
Seq.
Record
Data Level
TP_CD
Reference
1
Reference
2
Reference
3
Record
Number
Record
Layout
Record
Layout
Qualifier
103
Order Line
Global
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7350
A2
LG4
104
Order Line
Global
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7360
A2
LG5
105
Order Line
Detail
Global
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7370
A1
DG1
106
Order Line
Detail
Global
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7380
A2
DG2
107
Order Line
Detail
Global
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7390
A2
DG3
108
Order Line
Detail
Global
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7400
A2
DG4
109
Order Line
Detail
Global
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7410
A2
DG5
110
Picking
Line
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7420
A2
PL1
110
Picking
Line
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7430
A2
PL2
111
Picking
Line
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7440
A2
PL3
112
Picking
Line
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7450
A2
PL4
113
Line Part
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7460
A1
LP1
114
Line Part
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7470
A2
LP2
Table 8 45
8 92
(Page 8 of 10)
Seq.
Record
Data Level
TP_CD
Reference
1
Reference
2
Reference
3
Record
Number
Record
Layout
Record
Layout
Qualifier
115
Line Part
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7480
A2
LP3
116
Line Part
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7490
A2
LP4
117
Container
Contents
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7500
A1
CC1
118
Container
Contents
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7510
A2
CC2
119
Container
Contents
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7520
A2
CC3
120
Container
Contents
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7530
A2
CC4
121
Container
Contents
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7530
A2
CC5
122
Order Line
Industry
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7600
A1
IN1
123
Order Line
Industry
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7610
A2
IN2
124
Order Line
Industry
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7620
A2
IN3
125
Order Line
Industry
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
7630
A2
IN4
126
Extension
Tables Item
level
ITEM
TP_CD
DELIVERY
SO
ITEM
7900
IT
EX
127
Allowance
/Charge
Line item
ITEM
TP_CD
DELIVERY
SO
ITEM
8000
AC
IA1
129
Item
Allowance
/Charge
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
8010
A5
IA2
Table 8 45
(Page 9 of 10)
8 93
Seq.
Record
Data Level
TP_CD
Reference
1
Reference
2
Reference
3
Record
Number
Record
Layout
Record
Layout
Qualifier
130
Item
Allowance
/Charge
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
8020
A6
IA3
131
Item
Allowance
/Charge
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
8030
A6
IA4
132
Item
Allowance
/Charge
Flexfields
ITEM
TP_CD
DELIVERY
SO
ITEM
8040
A6
IA5
133
Extension
ITEM level:
A/C data
ITEM
TP_CD
DELIVERY
SO
ITEM
8900
AI
EX
134
Lot , serial,
production
sequence
ITEM
DETAIL
TP_CD
DELIVERY
SO
ITEM
9000
LS
DET
135
Picking
Line Detail
Flexfields
ITEM
DETAIL
TP_CD
DELIVERY
SO
ITEM
9010
A1
PD1
136
Picking
Line Detail
Flexfields
ITEM
DETAIL
TP_CD
DELIVERY
SO
ITEM
9020
A2
PD2
137
Picking
Line Detail
Flexfields
ITEM
DETAIL
TP_CD
DELIVERY
SO
ITEM
9030
A2
PD3
138
Picking
Line Detail
Flexfields
ITEM
DETAIL
TP_CD
DELIVERY
SO
ITEM
9040
A2
PD4
139
Extension
Table: item
detail
ITEM
DETAIL
TP_CD
DELIVERY
SO
ITEM
9900
ID
EX
Table 8 45
8 94
(Page 10 of 10)
CHAPTER
Extensible EDI
Gateway Architecture
T
his chapter describes the extensible architecture of Oracle EDI

Gateway. You can use this information to customize your
implementation:
Overview: page 9 2
Technical Overview: page 9 4
Extensible Architecture Example: page 9 5
Extensible EDI Gateway Architecture
91

While the Oracle Applications data model is robust enough to meet
most needs, you may need additional information for EDI
transactionseither now or in the futureas EDI transaction sets
change. The extensible EDI Gateway architecture gives you great
flexibility to customize your outbound EDI transactions.
Architecture Overview
Extensible EDI Gateway architecture includes:
Transactionspecific interface tables
Transactionspecific extension tables
A table of the interface tables
A table of the interface columns
TransactionSpecific Interface Tables

A series of tables with names in the format ECE_<Transaction.Name>
exist to provide as much information for specific transactions as
possible. In addition, each of these tables contain:
a foreign key to the transactionspecific extension table, called
TRANSACTION_RECORD_ID, also resides in this table. The
relationship between these two tables is onetoone.
TransactionSpecific Extension Tables

A series of tables with names in the format ECE_<Transaction.Name>_X
exist that hold data from sources other than Oracle Applications.
The primary key for this table is TRANSACTION_RECORD_ID,
referenced by the foreign key TRANSACTION_RECORD_ID in the
corresponding transactionspecific interface table.
During installation, the table is created with only one column, the
TRANSACTION_RECORD_ID column. Simple SQL statements, like the
ALTER TABLE command can be used to customize this table. You can
add to or modify this table according to your requirements for the
transaction.
92
A Table of Interface Tables

This table, named ECE_INTERFACE_TABLES, stores the starting
identifier (number) of each section of the output file. Some notable
columns include:
the composite primary key, TRANSACTION_TYPE and
INTERFACE_TABLE_NAME
TRANSACTION_TYPE, which identifies the transaction; for
example, POO (for outbound purchase order), and so on
INTERFACE_TABLE_NAME, which identifies the
transactionspecific interface table
START_NUMBER, which stores the starting identifier number of
each section in the output file
EXTENSION_TABLE_NAME, which tracks the
transactionspecific interface and extension tables that are related
A Table of Interface Columns

Data extract programs need guidelines to write output data in the
correct position of the output file. This table, named
ECE_INTERFACE_COLUMNS, stores this type of location information.
Notable columns:
Column
Description
INTERFACE_COLUMN_ID
Primary key.
INTERFACE_TABLE_ID to
ECE_INTERFACE_TABLES
Foreign key.
BASE_TABLE_NAME
The view from which data is extracted.
BASE_COLUMN_NAME
The column of the view from which data is extracted.
POSITION
The relative position on the record in the data

file.
INTERFACE_COLUMN_NAME
The column where the data is temporarily

stored in the interface table before being written to the data file.
93
See Also
Technical Overview
The Oracle EDI Gateway consists of interface tables, packaged
procedures, and setup tables used to create output data files for
outbound EDI document. The gateway is executed via the following
steps:
Execute
ECE_<EDI_document_name>.POPULATE_<EDI_document_name>_
API packaged procedure to populate the gateway. This routine
identifies row(s) of data and copies data into the EDI Gateway
interface tables: ECE_<EDI_document_name>_HEADERS,
ECE_<EDI_document_name>_LINES, and
ECE_<EDI_document_name>_ LINE_DETAILS.
(Optional) Execute customized code to populate the interface
extension tables. The EDI Gateway extension tables,
ECE_<EDI_document_name>_HEADERS_X,
ECE_<EDI_document_name>_LINES_X, and
ECE_<EDI_document_name>_LINE_DETAILS_X, are created
during the gateways initial installation. These tables are
modified by the customer to hold data elements that are not
directly extracted from the Oracle Application.
Execute
ECE_<EDI_document_name>.PUT_DATA_TO_OUTPUT_TABLE
packaged procedure. This procedures derives data from the
interface and interface extension tables to build output records.
The output record layout is defined in the EDI Gateway setup
tables ECE_INTERFACE_TABLES and
ECE_INTERFACE_COLUMNS. Formatted records are inserted
into the ECE_OUTPUT table.
Move the data from ECE_OUTPUT to a data file using the
PL/SQL package UTL_FILE.
The output file created by the Gateway reflects the data model used in
the Oracle Application, which usually contains three types of logical
records: Header, Line, and Line Detail. Using the EDI Gateway setup
tables, data from the interface tables can be mixed with data from the
94
corresponding extension table. (For example, data from

ECE_PO_INTERFACE_HEADERS can be mixed only with data from
ECE_PO_INTERFACE_HEADERS_X.) The data elements within the
physical records are fixed length fields. The fixed data length is derived
from the data dictionary.
Outbound Data File

Characteristics of output file created by the Oracle EDI Gateway
The outbound data file layout provides only one record at each
level (header, line, shipment). This is consistent with the data
model used in the Oracle Application.
The Oracle EDI Gateway ties field lengths to the Oracle data
dictionary, i.e., fixed length format.
The Oracle EDI Gateway does not currently provide formatting
options.
The Oracle data file layout is not of any particular EDI standards,
ASC X12 or EDIFACT. User has the flexibility to translate the
outbound file to whatever format is the most desirable.
See Also
Overview of Extensible Architecture: page 9 2
Extensible Architecture Example

As an example, suppose you want to send a Ship Notice / Manifest
(856) out via EDI. Most of the required information is stored in the
application database. However, you may want to send other
information, such as truck number, container number, the name of the
driver, driver license number, driving record, and so on.
Application Base Data
Supplier Name
Client Name
Purchase Order Number
Product Number
Quantity Shipped
Date Shipped
Additional Data
Truck Number
Container Number
Name of Driver
License Number
Driving record status
95
Expected Arrival Date

Carrier
I. Modify the Transaction Specific Extension Table

You must first modify the extension table to store additional data for the
transaction.
ALTER TABLE ECE_ASN_HEADERS_X
ADD ( Truck_Num
VARCHAR2(30),
Container_Num
VARCHAR2(30),
Driver_Name
VARCHAR2(30),
....... )
II. Insert data into the Extension table

Modify the ECASNOXB.pls file to insert records into the extension
tables at execution time:
Procedure populate_extension_header(l_fkey
IN NUMBER,
l_plsql_tbl
IN ece_flatfile_pvt.Interface_tbl_type)
is
Declare new variables
xPONumber
NUMBER;
xTruckNum
NUMBER;
xContainerNum NUMBER;
xDriverName
VARCHAR2(30);
begin
Get PO number from the PL/SQL table
ece_flatfile_pvt.find_pos(l_plsql_tbl,PO_NUMBER,xPONumber);
Go to legacy system and retrieve added info
and assign it to the variables based on xPONumber.
xTruckNum
= legacy data where po_num = xPONumber
xContainerNum
= legacy data where po_num = xPONumber
xDriverName
= legacy data whree po_num = xPONumber
Insert this data into the extension table
insert into ECE_OE_SHIPPING_HEADERS_X
(transaction_record_id,
truck_num,
container_num,
driver_num)
values
(l_fkey,
xTruckNum,
xContainerNum,
xDriverName);
end populate_extension_header;
96
III. Insert data into ECE_INTERFACE_COLUMNS table

You need to insert new data column name into the
ECE_INTERFACE_COLUMNS table so that they can be included in the
output file, for example:
insert into ECE_INTERFACE_COLUMNS
(interface_column_id,
interface_table_id,
interface_column_name,
record_number,
position,
width,
data_type,
created_by,
creation_date,
last_update_login,
last_update_date,
last_update_by)
select
ece_interface_column_id_s.nextval,
eit.interface_table_id,
TRUCK_NUM,
1999,
10,
30,
NUMBER,
1,
sysdate,
1,
sysdate,
1
from ece_interface_tables eit
where eit.transaction_type = ASNO and
eit.interface_table_name = ECE_OE_SHIPPING_HEADERS;
97
Trans_method
Type
Qty
Supplier_Name
Client_Name
PO_Num
Trans_Record_ID
EDI
ASNO
20
ABC
NBC
14938
101
EDI
ASNO
10
ABC
UPS
23456
201
Table 9 2 ECE_ASN_HEADERS Table (Page 1 of 1)
Trans_Record_ID
Truck_Num
Container_Num
Driver_Name
101
2A
G768
SAM
Table 9 3 ECE_ASN_HEADERS_X Table (Page 1 of 1)
Type
Interface_Table_Name
Start_Number
Extension_Table_Name
856O
ECE_ASN_HEADER
10
ECE_ASN_HEADER_X
856O
ECE_ASN_LINE
30
ECE_ASN_LINE_X
Table 9 4 ECE_INTERFACE_TABLES Table (Page 1 of 1)
Type
Interface_Table_Name
Table_Name
Column_Name
Position
856O
ECE_ASN_HEADER
ECE_ASN_HEADER
Client_Name
856O
ECE_ASN_HEADER
ECE_ASN_HEADER_X
Truck_Num
Table 9 5 ECE_INTERFACE_COLUMNS Table (Page 1 of 1)
Data Extraction
The extensible architecture allows the user to fetch data from sources
other than Oracle Applications and store them in the extension table.
Then you can produce, for example, the ASN with data from the
transaction specific interface table and the extension table.
In the above example, based on the Position column in the
INTERFACE_COLUMNS table, the Client_Name is the first data in the
output file, Truck_Num is the ninth field in the output file.
98
The record identifier in this section of the output file starts with 10
based on the Start_Num column in the ECE_INTERFACE_TABLES
table.
The SELECT statement:
Select ECE_ASN_HEADER.Client_Name, ECE_ASN_HEADER.PO_Num,
ECE_ASN_HEADER_X.Truck_Num, ECE_ASN_HEADER_X.Container_Num
from ECE_ASN_HEADER, ECE_ASN_HEADER_X
where ECE_ASN_HEADER.Transaction_Record_ID (+) =
ECE_ASN_HEADER_X.Transaction_Record_ID
and [other criteria]
Output
The output file produced by the EDI Gateway looks similar to the
following file:
10NBC
shington
*11DC
*12...
...
*30...
10UPS
Lincoln
*11NE
*12...
...
*30...
14938
ABC
77781
2A
23456
20
300 Beltway
G768
ABC
Wa
SAM
10
214 Temple
88832
where NBC is the Client Name, Position 1, and 2A is the Truck Num
in Position 9.
See Also
Overview of Extensible Architecture: page 9 2
99
Provide Additional Values

You may need additional values for EDI transactions not covered by the
Oracle Applications data model.
Descriptive Flexfields
Use the descriptive flexfields feature of Oracle Applications to supply
any additional information necessary to complete your EDI transactions.
Descriptive flexfields provide a flexible way of adding
implementationspecific data elements to the Applications data model
without programming. These data elements are then stored in the
ATTRIBUTE* columns in the applications tables. These ATTRIBUTE*
columns are included in the EDI Gateway interface tables for outbound
transactions and the application open interface tables for inbound
transactions.
The ECE_TP_HEADERS and ECE_TP_DETAILS tables have additional
ATTRIBUTE* columns also. This allows you to store additional
information for each trading partner that can then be placed in the
inbound or outbound data files.
If descriptive flexfields do not provide you with sufficient flexibility, you
can utilize the extensible architecture of Oracle EDI Gateway to
accommodate additional data needs.
See Also
9 10
APPENDIX
Windows and
Navigator Paths
T
his appendix shows you the default Navigator path for each EDI
Gateway window. Refer to this appendix when you do not already
know the Navigator path for a window you want to use.
Windows and Navigator Paths
A1
EDI Gateway Windows and Navigator Paths

For windows described in other manuals:
See...
Refer to this manual for a complete window description.
User
Oracle Applications Users Guide
Text in brackets ([ ]) indicates a button.

Windows
Navigator Menu Path
Define Trading Partner: page 2 9
Trading Partners
Code Conversion Categories: page 3 13
Code Conversion Categories
Code Conversion Values: page 3 18
Code Conversion Values
Assign Categories: page 3 14
Code Categories Assignment
Interface File Definition: page 5 2
Output Definition
Run EDI Outbound Extract Program: page

66
Extract Programs
Run EDI Inbound Datafile Import

Program: page 6 4
Import Programs
Concurrent Requests Summary (See User)
Requests
Table 10 1
A2
Glossary
ANSI American National Standards Institute
which establishes national standards for the
United States. The parent organization for
X12 and also serves as the North American
representative to ISO (International
Standards Organization).
ASC X12 Accredited Standards Committee
X12 group. This group is accredited by ANSI
and maintains and develops the EDI
standards for the United States and Canada.
ASCII American Standard Code for
Information Interchange. A standard file
format used for transmission and storage.
ASCII is a sevenbit code with an eighth bit
used for parity.
Automated Clearing House (ACH) A
nationwide network operated by the Federal
Reserve used to connect banks together for
the electronic transfer of funds.
bankers automated clearing system (BACS)
The standard format of electronic funds
transfer used in the United Kingdom.
business application Software that performs a
particular business function or group of
functions (accounts payable, for example).
business document A document used for
conducting business between two trading
partners a purchase order or invoice, for
example.
EDI See Electronic Data Interchange (EDI)
EDIFACT Electronic Data Interchange for
Administration, Commerce, and Trade is the
current acronym for standards developed
within Working Party 4. See also WP4
methods of exchanging business information

electronically, such as Electronic Data
Interchange (EDI), FAX, email, and eforms.
Electronic Data Interchange (EDI) Exchanging
business documents electronically between
trading partners. EDI subscribes to standard
formats for conducting these electronic
transactions as stated by various standards.
electronic funds transfer A method of
payment in which your bank transfers funds
electronically from your bank account into
another bank account. In Oracle Payables,
funds are transferred from your account into
that of a supplier. This information is sent to
the bank in a file.
financial EDI The exchange of machine
readable financial documents between a
corporation and its financial institution. The
exchange includes both collections and
disbursements in the form of credit and debit
transfers, related bank balance, banking
transactions, and account analysis.
functional acknowledgment The
acknowledgement to indicate the results of
the syntactical analysis of electronically
encoded documents. Applies to a functional
group and can include detail.
National Automated Clearing House
Association The NACHA is a nonprofit
organization responsible for developing and
maintaining the rules and guidelines for
using the ACH network.
payment batch A group of invoices selected
for automatic payment processing via Oracle
Payables AutoSelect function.
electronic commerce Conducting business via

an electronic medium. This includes
Glossary
payment document Medium used to instruct

a bank to disburse funds to the account of a
site location or supplier.
remittance advice A document that lists the
invoices being paid with a particular
payment document.
trading partner Any company that sends and
receives documents via EDI.
transaction set A complete business document
such as an invoice, a purchase order, or a
remittance advice. Synonym for document
or message.
transaction set line item area The line item
area encompasses the actual business
transaction set and includes information,
such as quantities, descriptions, and prices.
transaction set summary area The summary
area contains control information and other
data that relate to the total transaction.
VAN(S) Value Added Network (Supplier).

wire A payment method where you pay
invoices by notifying your bank to debit your
account and credit your suppliers account.
WP4 Working Party 4 on the facilitation of
international trade procedures of the
Economic Commission for Europe, a
commission of the United Nations. Working
Party 4 has experts on data elements and
interchange, and on trade procedures.
X12 ANSI standard for interindustry
electronic interchange of business
transactions.
X.400 International standard (in development)
for message transmission.
Index
Numbers
810 inbound. See Invoice inbound

810 outbound. See Invoice outbound
820 outbound. See Payment Order /
Remittance Advice outbound
824 outbound. See Application Advice
outbound
830 outbound. See Planning Schedule
outbound
832 inbound. See Price / Sales Catalog inbound
843 inbound. See Response to Request for
Quote inbound
850 inbound. See Purchase Order inbound
850 outbound. See Purchase Order outbound
856 inbound. See Shipping Notice / Manifest
inbound
856 outbound. See Ship Notice / Manifest
outbound
857 inbound. See Shipping and Billing Notice
inbound
860 outbound. See Purchase Order Change
Request outbound
862 outbound. See Shipping Schedule
outbound
APERAK. See Application Advice outbound

Application Advice outbound, 8 2
data file organization, 8 5
extracting, 8 3
C
Changing the Data File, 5 2
Code conversion, 3 2
D
Data file definition format legend, 6 9
Defining Data File Directories, 6 2
DELFOR outbound. See Planning Schedule
outbound
DELJIT outbound. See Shipping Schedule
outbound
DESADV inbound. See Ship Notice / Manifest
inbound
DESADV outbound. See Ship Notice /
Manifest outbound
Index 1
Directories, data files, 6 2
E
EDI standards support, 1 8
extensible architecture, 9 2
I
INVOIC inbound. See Invoice inbound
INVOIC outbound. See Invoice outbound
Invoice inbound, 7 2
importing, 7 3
Invoice outbound, 8 9
extracting, 8 10
Price / Sales Catalog inbound, 7 6

importing, 7 7
Profile options, 6 3
Purchase Order Change Request outbound,
8 67
extracting, 8 69
Purchase Order inbound, 7 19
importing, 7 20
Purchase Order outbound, 8 58
extracting, 8 59
Q
QUOTES inbound. See Response to Request for
Quote inbound
Oracle EDI Gateway

architecture, 1 4, 9 2
overview, 1 2
ORDCHG outbound. See Purchase Order
Change Request outbound
ORDERS inbound. See Purchase Order
inbound
ORDERS outbound. See Purchase Order
outbound
Ship Notice / Manifest inbound, 7 27

importing, 7 28
Ship Notice / Manifest outbound, 8 77
extracting, 8 79
Shipping and Billing Notice inbound, 7 30
importing, 7 31
Shipping Schedule outbound, 8 47
extracting, 8 51
summary tables, 8 53
standards, EDI Gateway support for, 1 8
Payment Order / Remittance Advice

outbound, 8 20
extracting, 8 22
PAYORD outbound. See Payment Order /
Planning Schedule outbound, 8 27
extracting, 8 51
summary tables, 8 53
PRICAT inbound. See Price / Sales Catalog
inbound
Index 2
REMADV outbound. See Payment Order /

Response to Request for Quote inbound, 7 10
importing, 7 11
Supported transactions, 1 8
T
Transactions
Application Advice outbound, 8 2
Invoice inbound, 7 2
Invoice outbound, 8 9
Payment Order / Remittance Advice
outbound, 8 20
Planning Schedule outbound, 8 27
Price / Sales Catalog inbound, 7 6
Purchase Order Change Request outbound,
8 67
Purchase Order inbound, 7 19

Purchase Order outbound, 8 58
Response to Request for Quote inbound,
7 10
Ship Notice / Manifest inbound, 7 27
Ship Notice / Manifest outbound, 8 77
Shipping and Billing Notice inbound, 7 30
Shipping Schedule outbound, 8 47
Transactions supported, 1 8
W
Windows and navigator paths, A 2
Index 3
Index 4
Readers Comment Form

A5827101
Oracle Corporation welcomes your comments and suggestions on the quality and usefulness
of this publication. Your input is an important part of the information we use for revision.
Did you find any errors?

Is the information clearly presented?
Do you need more information? If so, where?
Are the examples correct? Do you need more examples?
What features did you like most about this manual? What did you like least about it?
If you find any errors or have any other suggestions for improvement, please indicate the topic, chapter,
and page number below:
Please send your comments to:

Oracle Applications Documentation Manager
Oracle Corporation
500 Oracle Parkway
Redwood Shores, CA 94065 USA
Phone: (650) 5067000 Fax: (650) 5067200
If you would like a reply, please give your name, address, and telephone number below:
Thank you for helping us improve our documentation.

EDI Gateway

Uploaded by

Copyright:

Available Formats

EDI Gateway

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EDI Gateway

Uploaded by

Copyright:

Available Formats

What is the document about?

What is the document about?

What are some of the main chapters covered?

What are some of the main chapters covered?

Oracler EDI Gateway

Enabling the Information Aget

OracleR EDI Gateway Users Guide

Overview of Oracle EDI Gateway . . . . . . . . . . . . . . . . . . . . . . . . 1 1

Trading Partner Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1

Data File Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Record Layout Codes Summary . . . . . . . . . . . . . . . . . . . . . . . 4 16

Data File Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1

Importing and Extracting EDI Documents . . . . . . . . . . . . . . . . .

iv Oracle EDI Gateway Users Guide

Running the EDI Application Advice Outbound

Extensible EDI Gateway Architecture . . . . . . . . . . . . . . . . . . . . .

Windows and Navigator Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . A 1

vi Oracle EDI Gateway Users Guide

About this Users Guide

Oracle EDI Gateway Users Guide

Audience for This Guide

Do Not Use Database Tools to Modify Oracle Applications Data

Other Information Sources

formats, HyperText Markup Language (HTML) and Adobe Acrobat

Related Users Guides

Oracle EDI Gateway Users Guide

book contains detailed discussions and examples across each of the

automatically create purchasing documents based on business rules

Oracle EDI Gateway Users Guide

Oracle SelfService Web Applications Implementation Manual

Installation and System Administration

Oracle Applications Flexfields Guide

Oracle EDI Gateway Users Guide

You have a choice of educational environments. You can attend

Oracle EDI Gateway Users Guide

Overview of Oracle EDI

How to Use Oracle EDI Gateway: page 1 9

Overview of Oracle EDI Gateway

Overview of Oracle EDI Gateway

How Oracle EDI Gateway Works with Other Oracle Applications

Oracle EDI Gateway Users Guide

A common EDI implementation is via ASCII data files in a batch

Overview of Oracle EDI Gateway

The following figure illustrates the inbound EDI Gateway transaction

Oracle EDI Gateway Product Architecture

Product Components for All Transactions

Oracle EDI Gateway Users Guide

establish a link to the trading partner definition in the EDI

Product Components for Outbound Transactions

Overview of Oracle EDI Gateway

Transactionspecific Interface Tables

Oracle EDI Gateway Users Guide

Product Components for Inbound Transactions

Overview of Oracle EDI Gateway

EDI Standards Supported

EDI Transaction Support

Inbound Invoice: page 7 2

Inbound Price / Sales Catalog: page 7 6

Inbound Response to Request for Quote: page 7 10

Inbound Purchase Order: page 7 19