Edi 11r107 Techinfo

ORACLE EDI GATEWAY
Support Document
R10.7CP and R11 Basic Technical
Information
Creation Date: March 8, 2002

Updated: March 8, 2002
Introduction
EC_11R107_TECHINFO.doc
Company Confidential - For internal use only
ii
Contents
Introduction .............................................................................................................................7
Document Purpose ..........................................................................................................7
General Design Overview...............................................................................................7
Transaction Summary .....................................................................................................8
EDI Gateway Forms................................................................................................................9
Trading Partner Group Form .........................................................................................9
Design Overview.....................................................................................................................9
Data Flow Diagram.................................................................................................................9
Data Model...............................................................................................................................9
Upgrade from R10.7 to R11....................................................................................................9
Setting Up Test Cases ...........................................................................................................10
Utilities ...................................................................................................................................10
Logging Problem Reports Bugs.......................................................................................10
Multiple Product Issues .......................................................................................................10
Trading Partner Set Up Form .......................................................................................11

Form Purpose ........................................................................................................................11
Design Overview...................................................................................................................11
Data Flow Diagram...............................................................................................................11
Data Model.............................................................................................................................11
R10.7 to R11 Upgrade ...........................................................................................................12
Utilities ...................................................................................................................................12
Code Category Set Up Form.........................................................................................13

Design Overview...................................................................................................................13
Interface File Definition Form ......................................................................................13

Design Overview...................................................................................................................13
Data Model.............................................................................................................................13
R10.7 to R11 Change .............................................................................................................13
Extract Program in Concurrent Manager ...................................................................14

Design Overview...................................................................................................................14
Data Model.............................................................................................................................14
Concurrent Programs : Extract process steps ....................................................................14
Extract Transaction Multiple Times....................................................................................15
Required Data per Open Interface ......................................................................................15
Import Program in Concurrent Manager ...................................................................15

Design Overview...................................................................................................................15
Data Model.............................................................................................................................15
Concurrent Programs: Import process steps .....................................................................15
Outbound Transactions........................................................................................................17
Design Overview...................................................................................................................17
Extension Tables....................................................................................................................17
Outbound Purchase Order Transaction (850/ORDERS)..........................................17

Design Overview...................................................................................................................17
Introduction
iii
Data Model.............................................................................................................................17
Concurrent Programs ...........................................................................................................18
Setting Up Test Cases in Purchasing ..................................................................................18
Extract Flags...........................................................................................................................18
Utilities ...................................................................................................................................18
Outbound Purchase Order Change Transaction (860/ORDCHG) .........................20

Design Overview...................................................................................................................20
Data Model.............................................................................................................................20
Extract Flags...........................................................................................................................21
Utilities ...................................................................................................................................21
Outbound Invoices Transaction (810/INVOIC) ........................................................22

Design Overview...................................................................................................................22
Data Model.............................................................................................................................22
Extract Flags...........................................................................................................................23
Utilities ...................................................................................................................................23
Outbound Payment Order/Remittance Advice Transaction

(820/PAYORD/REMADV) ..........................................................................................24
Design Overview...................................................................................................................24
Data Model.............................................................................................................................24
Setting Up Test Cases in Payables ......................................................................................25
Extract Flags...........................................................................................................................25
Utilities ...................................................................................................................................25
Extract Flags...........................................................................................................................25
Outbound Planning (830/DELFOR) and Shipping Schedule Transactions

(862/DELJIT) ..................................................................................................................27
Design Overview...................................................................................................................27
Data Model.............................................................................................................................27
Obsolete R10.7 EDI Gateway interface and extension tables due to design change ....28
Setting Up Test Cases in Supplier Scheduling ..................................................................28
Extract Flags for Planning Schedule ...................................................................................28
Extract Flags for Shipping Schedule ...................................................................................28
Utilities ...................................................................................................................................29
Outbound Ship Notice/Manifest Transaction (856/DESADV) ..............................30

Design Overview...................................................................................................................30
Data Model.............................................................................................................................30
Obsolete R10.7 EDI Gateway database views ...................................................................31
Introduction
iv
Obsolete R10.7 EDI Gateway interface and extension tables ..........................................31

Setting Up Test Cases in Departure Planning ...................................................................31
Extract Flags...........................................................................................................................31
Utilities ...................................................................................................................................32
Outbound Application Advice Transaction (824/APERAK) ..................................33

Design Overview...................................................................................................................33
Data Model.............................................................................................................................33
Extract Flags...........................................................................................................................34
Utilities ...................................................................................................................................34
Inbound Transactions ...........................................................................................................35

Inbound Purchase Order Transaction (850/ORDERS).............................................35
Design Overview...................................................................................................................35
Data Model.............................................................................................................................35
Utilities ...................................................................................................................................36
Inbound Invoice Transaction (810/INVOIC).............................................................37

Design Overview...................................................................................................................37
Data Model.............................................................................................................................37
Utilities ...................................................................................................................................37
Inbound Ship Notice Transaction (856/DESADV) Inbound Shipment & Billing

Notice Transaction (857) ...............................................................................................39
Design Overview...................................................................................................................39
Data Model.............................................................................................................................39
Utilities ...................................................................................................................................40
Inbound Price/Sales Catalog (832/PRICAT) Inbound Response to RFQ

(843/QUOTES) ...............................................................................................................41
Design Overview...................................................................................................................41
Data Model.............................................................................................................................41
Utilities ...................................................................................................................................42
Post Implementation Issues .................................................................................................43

These are common post implementation issues. See updated document in Metalink.43
Invalid file path .....................................................................................................................43
No file created .......................................................................................................................43
Introduction
Empty interface file created .................................................................................................43

Interface file doesnt match Users Guide ..........................................................................43
EDI Gateway import program failed..................................................................................43
Application Open Interface program failed ......................................................................43
Code conversion error if no keys ........................................................................................44
Code conversion error if keys used ....................................................................................44
Introduction
vi
Introduction
Document Purpose
This document provides basic technical information about the R11 EDI Gateway
forms and transactions. The following is included:
Design Overview
Data Flow Diagram
Data Model
Concurrent Program Processing Logic
Setting Up Test Cases
Extract Flags to Reset for Testing
Logging Problem Reports Bugs
Multiple Product Issues
General Design Overview

The following should be noted about the Oracle EDI Gateway:
Design Overview - EDI Gateway and all EDI transactions.

EDI Gateway is not Workflow-enabled.
EDI Gateway does not support multi-org, it is dependent on the
organization of the host application.
Transactions supported by EDI Gateway are designed to support any
EDI standard including ASC X12 and EDIFACT.
EDI Gateway does not have any localization requirements.
Introduction
Transaction Summary
The following R11 transactions are reviewed in this document.
Some transactions are also available in Release 10.7 Controlled Production.
OUTBOUND Transactions
R10.7CP
R11
Code
X12
EDIFACT
Direction
Description
Oracle base
application
PYO
820
PAYORD/
REMADV
Outbound
Payment/
Remittance
Advice
From Payables
INO
810
INVOIC
Outbound
Invoice
From Receivables
POO
850
ORDERS
Outbound
Purchase Orders
From Purchasing
POCO
860
ORDCHG
Outbound
Purchase Order
Changes
From Purchasing
X
Pack slip
based
(ASNO)
X
Departure
based
(DSNO)
ASNO/
DSNO
856
DESADV
Outbound
Ship
Notice/Manifest
From Order Entry

(this transaction is
totally changed
from R10.7
(ASNO) to R11
(DSNO))
SPSO
830
DELFOR
Outbound
Planning Forecast
SSSO
862
DELJIT
Outbound
Delivery Schedule
From Supplier
Scheduling
From Supplier
Scheduling
ADVO
824
APERAK
Code
X12
EDIFACT
Application
Advice
Several (for INI,

ASNI, SBNI)
Direction
Description
INBOUND Transactions
R10.7CP
9
POI
850
ORDERS
Inbound
Purchase Orders
Oracle base
application
Into Order Entry
10
INI
810
INVOIC
Inbound
Invoice
Into Payables
11
CATI
832
PRICAT
Inbound
Price Catalog
Into Purchasing
12
RRQI
843
QUOTES
Inbound
Response to RFQ
Into Purchasing
ASNI/
SBNI
856
DESADV
Inbound
Ship
Notice/Manifest
Into Purchasing
and
Receiving
13
R11
Introduction
EDI Gateway Forms

Trading Partner Group Form
Design Overview
Trading Partner Groups are defined using the Trading Partner Group window of the
Trading Partner form.
Represents a set of Trading Partner definitions

Supports integration with Automotive via Automotive button
Trading Partner Group is required for all implementation
This is a new R11 feature that does not replace existing functionality from R10.7.
Data Flow Diagram
ECE_TP_GROUP
ECE_TP_HEADERS
ECE_TP_DETAILS
Data Model
Table ECE_TP_GROUP is a master table to ECE_TP_HEADERS containing the

individual Trading Partner definitions.
There is no specific seed data.
Upgrade from R10.7 to R11

The R10.7 to R11 conversion program defines a unique Trading Partner Group for
each trading partner definition found in the R10.7 database
The Partner name in R10.7 becomes the Trading Partner Group name
in R11
This is a one for one conversion from the existing Trading Partner
definition to the Trading Partner Group. In order for many Trading
Partners to be assigned to a single Trading Partner Group, the newly
assigned Trading Partner Group from the upgrade must be deleted
before the Trading Partner can be assigned to another Trading
Partner Group.
EDI Gateway Forms

Select the Trading Partner form from the EDI Gateway navigation menu
Define a new Trading Partner Group
Identify specific trading partners for the Trading Partner Group
Commit the new Trading Partner Group to the database and query on it for
verification
Utilities
No utilities available to support debugging.
No additional information required to support bug report.
If the environment is installed with Automotive product, and the user clicked on the
Automotive button, ask for Automotive setup information
EDI Gateway Forms

10
Trading Partner Set Up Form
Form Purpose
Trading Partner association provides location cross-reference to physical site address in
Oracle Applications.
Trading Partner definitions are defined using the Trading Partner form.
Associate an EDI Gateway Trading Partner to one of the following:
Supplier/Supplier Site in PO/AP
Customer/Customer Site in OE/AR
Bank Branch in AP
Other address entities in HR tables such as buyers and warehouses
Design Overview
Moved EDI Gateway Trading Partner LOCATION CODE to Oracle Applications
TRADING PARTNER LOCATION CODE
In R10.7 address associations were implemented using the LOCATION CODE field on
the Trading Partner form
Data Flow Diagram
ECE_TP_GROUP
ECE_TP_HEADERS
ECE_TP_DETAILS
Data Model
Change was made to centralize the definition of an address entity to the application user.
Moved ECE_TP_HEADERS:TP_LOCATION_CODE_EXT to Oracle Applications tables in R11.
Obsoleted ECE_TP_HEADERS:TP_LOCATION_CODE_EXT from R10.7 EDI Gateway.
The following are new columns added to existing tables in R11 with no specific seed data:
Supplier:
PO_VENDOR_SITES:ECE_TP_LOCATION_CODE
PO_VENDOR_SITES:TP_HEADER_ID
Customer:
RA_ADDRESSES:ECE_TP_LOCATION_CODE
RA_ADDRESSES:TP_HEADER_ID
Bank Branch:
AP_BANK_BRANCHES:ECE_TP_LOCATION_CODE
AP_BANK_BRANCHES:TP_HEADER_ID
Human Resource:
HR_LOCATIONS:ECE_TP_LOCATION_CODE
EDI Gateway Forms
11
HR_LOCATIONS:TP_HEADER_ID
Human Resource - There are no EDI transactions which integrate with HR, but Oracle
Applications uses HR_LOCATIONS for other address entities such as buyer and warehouse
R10.7 to R11 Upgrade
The R11 conversion program copies the EDI Gateway Trading Partner location code to the
Oracle Applications location code.
1.
2.
3.
4.
5.
6.
Select Trading Partner form in EDI Gateway.

Select existing Trading Partner Group or add new Trading Partner Group.
Define new Trading Partner definition.
Query on the address entity in Oracle Applications.
Use the Assignment window of the Trading Partner form to associate the Trading
Partner definition to Oracle Applications address entity verified above.
Verify that Oracle Applications Trading Partner ID for address entity matches EDI
Gateway Trading Partner ID as follows:
PO_VENDOR_SITES:TP_HEADER_ID
RA_ADDRESSES:TP_HEADER_ID
AP_BANK_BRANCHES:TP_HEADER_ID
HR_LOCATIONS:TP_HEADER_ID
= ECE_TP_HEADERS:TP_HEADER_ID
Utilities
No utilities available to support debugging.
No additional information required to support bug report.
If association for supplier/supplier site in Purchasing/Payables, ask for supplier data.
If association for customer/customer site in Order Entry/Receivables, ask for customer data.
If association for bank branch in Payables, ask for bank branch data.
If association for buyer or warehouse in Human Resources, ask for buyer and warehouse data.
EDI Gateway Forms

12
Code Category Set Up Form

Design Overview
Table and view names in Assign Categories form moved from detail region to header region.
Code conversion feature is optional but use of Code Conversion Categories, Assign
Categories, and Code Conversion Values forms are required if code conversion feature is
implemented.
This is a GUI form change with no workaround required.
Table and view names in R11 Interface File Definition form moved from R10.7 Detail region
to header region.
Data Flow Diagram
ECE_XREF_CATEGORIES
ECE_XREF_DATA
Interface File Definition Form

Design Overview
Interface file definitions are preseeded. Using the Interface File Definition form to change the
seeded definitions is an optional feature.
Data Model
ECE_INTERFACE_TABLES
ECE_INTERFACE_COLUMNS
R10.7 to R11 Change

Obsoleted ECE_SOURCE_DATA_LOC, required data written to ECE_INTERFACE_TABLES
and ECE_INTERFACE_COLUMNS.
EDI Gateway Forms

13
Extract Program in Concurrent Manager

Design Overview
Standardize on R11 AOL to submit outbound transactions to the Concurrent Manager for
processing.
Data Model
Refer to AOL for Data Model.
Concurrent Programs : Extract process steps
1.
2.
3.
4.
5.
6.
Select Request to submit individual request.

Select extract program desired.
Provide selection criteria for extract program.
Enter Schedule options.
Enter Completion Options.
Submit extract request.
EDI Gateway Forms

14
Extract Transaction Multiple Times

The EDI Gateway sets an extract flag (or the print flag) and dates on most transactions in the
base application in order to prevent the transactions to be extracted more than once.
For some transactions, the EDI Extract flag is also the Print Flag for the document. This shared
usage prohibits both the EDI transaction extract and the printed documents to be created
without customer code. A custom workaround is needed to allow both extracts until this is
incorporated into the standard code.
For testing purposes, reset the appropriate extract flag to null to allow it to be extracted again.
This will save time from entering more transactions.
See the details in each transaction below to see what field to reset to null to allow the
transaction to be extracted again.
Required Data per Open Interface
Check for documents in OracleMetaLink under the Oracle EDI Gateway that detail the required
data for each transaction. Check your applications Open Interface manuals also.
Import Program in Concurrent Manager
Design Overview
Standardize on R11 AOL to submit inbound transactions to the Concurrent Manager for
processing.
Data Model
Refer to AOL for Data Model.
Concurrent Programs: Import process steps
1.
2.
3.
Select Request to submit an individual request.

Select the EDI Gateway import program desired.
Provide the inbound interface file name to the Parameter Window for the Import Program.
4.
Answer Execute Open Interface

Yes, to execute Application Open Interface validation in EDI Gateway.
No, to execute Application Open Interface validation in Oracle Applications.
5.
If Executing Open Interface in EDI Gateway:

Provide parameter values for Application Open Interface program.
6.
If Executing Open Interface in Oracle Applications:

Change responsibility to desired Oracle Application.
Complete import validation in Oracle Applications selected.
7.
Enter Schedule options.

EDI Gateway Forms
15
8.
9.
Enter Completion Options.

Submit import request.
EDI Gateway Forms

16
Outbound Transactions
Design Overview
Each outbound transaction is designed with the following objects:
Database views to select eligible data
Interface tables to store interface file data
Extension tables to store data from a non-Oracle data source
Stored procedure to mark the host application data to prevent duplicate extraction
Extension Tables
Each interface table has a corresponding extension table defined for it.
The extension contains a key to link it to the interface table.
The extension table is empty until populated by some custom code.
Data from the interface tables and extension tables are written to the interface file.
Use of the extension tables is optional.
Outbound Purchase Order Transaction (850/ORDERS)

Design Overview
Provide user ability to send approved purchase order to their suppliers.

System profile setting for Archive on Approval required.
System profile setting for Archive on Print will prevent purchase orders from being
extracted as they have been printed.
Data Flow Diagram
EDI Gateway
Database Views
Oracle
Purchasing
Tables
Flat File in
EDI Gateway
Interface Tables
Outbound
Directory
ECE_POO_HEADERS_V
ECE_PO_INTERFACE_HEADERS
ECE_POO_LINES_V
ECE_POO_SHIPMENTS_V
ECE_PO_INTERFACE_LINES
ECE_PO_INTERFACE_SHIPMENTS
POOnnnn.dat
Data Model
EDI Gateway database views:
ECE_POO_HEADERS_V
ECE_POO_LINES_V
ECE_POO_SHIPMENTS_V
Utilize database views to extract from Purchasing all approved purchase orders before applying
user entered selection criteria.
Database views are updated each time the transaction is executed.
17
EDI Gateway interface tables:

Utilize EDI Gateway interface tables to store data from Purchasing selected by the database
view that matches the user selection criteria.
EDI Gateway interface tables are purged after data is successfully written to the interface file.
Extension Tables
EDI Gateway extension tables for user customization:
ECE_PO_INTERFACE_HEADERS_X
ECE_PO_INTERFACE_LINES_X
ECE_PO_INTERFACE_SHIPMENTS_X
Utilize extension tables to store additional data from a non-Oracle data source to be included in
the interface file.
Extension tables are purged after data is successfully written to the interface file.
Concurrent Programs
Use Extract Programs to submit ECEPOO.sql to the Concurrent Manager for processing.
1.
2.
3.
4.
Setting Up Test Cases in Purchasing

Set system profile option: Archival Mode to Archive on Approval.
Create purchase order.
Approve the purchase order.
Submit extract using EDI Gateway extract program
Extract Flags
Reset the following flag on the base application header to allow the transactions to be extracted
again (Limit which transactions you reset the flags on to limit the volume of transactions to be
extracted again.):
Table:
Column:
Utilities
Verify that the user has current patch sets by referring to the Metalink web site.
Verify the user setup by referring to the Post Implementation guide on the Metalink web site.
If no flat file was created, verify if eligible data exists by doing the following:
1. In SQLPLUS, set the correct org context.
2. Execute header database view as follows:
>select count(*) from ECE_POO_HEADERS_V;
3. If count returned is zero, then nothing is eligible.
4. If count returned is greater than 0, execute extract code in SQLPLUS to get error
log as follows:
>@ECEPOO.sql
If a flat file was created, use PL/SQL procedure ECE_UTILITIES.VERIFY_FLATFILE
documented in Technical Perspective, page 67 to verify the contents of the flat file.
18

Get Concurrent Manager Report Log and Diagnostics report.
Get copy of file created.
Provide output from VERIFY_FLATFILE.

Dependent on Purchasings purchase order functionality.
Dependent on system profile option for Archive on Approval.
19
Outbound Purchase Order Change Transaction (860/ORDCHG)

Design Overview
Provide user the ability to send approved purchase order changes to their suppliers.
System profile setting for Archive on Approval required.
System profile setting for Archive on Print will prevent changed POs from being
extracted as they have been printed.
Data Flow Diagram
EDI Gateway
Database Views
Oracle
Purchasing
Tables
Flat File in
EDI Gateway
Interface Tables
Outbound
Directory
ECE_POCO_HEADERS_V
ECE_POCO_LINES_V
ECE_POCO_SHIPMENTS_V
POCOnnnn.dat
Data Model
ECE_POCO_HEADERS_V
ECE_POCO_LINES_V
ECE_POCO_SHIPMENTS_V
Utilize database views to extract from Purchasing all approved changed POs before applying
user-entered selection criteria.
Utilize EDI Gateway interface tables to store data from Purchasing selected by the database
view that matches the user selection criteria.
Extension Tables
The following are EDI Gateway extension tables for user customization:
ECE_PO_INTERFACE_HEADERS_X
ECE_PO_INTERFACE_LINES_X
ECE_PO_INTERFACE_SHIPMENTS_X
the interface file.
20
Concurrent Programs
Use Extract Programs to submit ECEPOCO.sql to the Concurrent Manager for processing.
1.
2.
3.

Make purchase order changes
Approve the purchase order changes
Submit extract using EDI Gateway extract program
Extract Flags
Reset the following flag on the base application header to allow the transactions to be extracted
again (Limit which transactions you reset the flags on to limit the volume of transactions to be
extracted again.):
Table:
Column:
Utilities
Verify that the user has current patch sets by referring to the Metalink web site.
Verify user setup by referring to the Post Implementation guide on the Metalink web site.
1. In SQLPLUS, set the correct org context
>select count(*) from ECE_POCO_HEADERS_V;
3. If count returned is zero, then nothing is eligible
log as follows:
>@ECEPOCO.sql
Logging Problem Reports or Bugs

Get copy of the file created.
Determine if user was adding a PO line, changing a PO line, or changing shipment
data.
Determine exactly which PO attribute the user was trying to change.

Dependent on Purchasings PO change functionality.
Dependent on system profile option for Archive on Approval.
Remember that Purchasing does not archive all PO changes and that EDI Gateway
depends on data in the PO Archive tables.
21
Outbound Invoices Transaction (810/INVOIC)

Design Overview
Provide user the ability to send approved invoices to their customers.

System profile setting for xxx required.
System profile setting for xxx will prevent invoices from being extracted as they have
been printed.
Data Flow Diagram
Oracle
Receivables
Flat File in
EDI Gateway
Interface Tables
EDI Gateway
Database Views
Outbound
Directory
ECE_INO_HEADER_V
ECE_ AR_TRX_HEADERS
ECE_INO_LINE_TAX_V
ECE_ AR_TRX _LINES
ECE_INO_LINE_V
ECE_ AR_TRX LINE_TAX
ECE_INO_ALLOWANCE_CHARGES_V
(Oracle Automoive Only)
ECE_AR_TRX_ALLOWANCE_CHARGES
ECE_INO_HEADER_1_V
ECE_AR_TRX_HEADER_1
(Oracle Aut5omitive Only)
INOnnnn.dat
Data Model
ECE_INO_HEADERS_V
ECE_INO_LINES_V
ECE_INO_SHIPMENTS_V
Utilize database views to extract from Receivables all approved invoices before applying userentered selection criteria.
ECE_INO_INTERFACE_HEADERS
ECE_INO_INTERFACE_LINES
Utilize EDI Gateway interface tables to store data from Receivables selected by the database
view that match the user selection criterion.
Extension Tables
EDI Gateway extension tables for user customization:
ECE_INO_INTERFACE_HEADERS_X
ECE_INO_INTERFACE_LINES_X
22
the interface file.
Concurrent Programs
Use Extract Programs to submit ECEINO.sql to the Concurrent Manager for processing.
1.
2.
3.
Create invoices
Approve the invoice.
Submit extract using EDI Gateway extract program.
Extract Flags
The flag to reset on transactions on the base application header to allow them to be extracted
again is the following: (Limit which transactions have the flags reset to limit the volume of
transactions to be extracted again.)
Table:
Column:
Utilities
Verify user has current patch sets by referring to the Metalink web site.
Verify user setup by referring to Post Implementation guide on the Metalink web site.
>select count(*) from ECE_INO_HEADERS_V;
log as follows:
>@ECEINO.sql
Get the Concurrent Manager Report Log and Diagnostics report.

Get a copy of the file created.
Dependent on Receivables invoice functionality,
Dependent on system profile option for xxx.

23
Outbound Payment Order/Remittance Advice Transaction (820/PAYORD/REMADV)
Design Overview
Provide payer ability to authorize bank to disburse payments to suppliers using EDI or
Electronic Funds Transfer (EFT).
Provide payer ability to send electronic remittance advice to supplier.
Payment extract must be submitted from Payment Workbench.
Payment extract cannot be submitted from EDI Gateway.

Data Flow Diagram
EDI Gateway
Database Views
Flat File in
EDI Gateway
Interface Tables
Outbound
Directory
Oracle
Payables
Tables
ECE_PYO_PAYMENT_V
ECE_AP_CHECKS_INTERFACE
ECE_PYO_INVOICE_V
ECE_AP_INVOICES_INTERFACE
PYOnnnn.dat
Data Model
ECE_PYO_PAYMENT_V
ECE_PYO_INVOICE_V
Utilize database views to extract from Payables the selected payment batch before applying
user-entered selection criteria.
ECE_AP_CHECKS_INTERFACE
ECE_AP_INVOICES_INTERFACE
Utilize EDI Gateway interface tables to store data from Payables for the payment batch.
Extension Tables
EDI Gateway extension tables for user customization are:
ECE_AP_CHECKS_INTERFACE_X
ECE_AP_INVOICES_INTERFACE_X
the interface file.
24
Concurrent Programs
Use Payables Payment Workbench to submit ECEPYO.sql to the Concurrent Manager for
processing
Setting Up Test Cases in Payables
1.
2.
Using Payment Workbench, select invoices for payment.

Select EDI as the format option to submit the extract program.
Extract Flags
The flag to reset on transactions on the base application header that will allow them to be
extracted again is the following: (Limit which transactions have the flags reset to limit the
volume of transactions to be extracted again.)
Table:
Column:
Utilities
Verify the user has current patch sets by referring to the Metalink web site.
1. In SQLPLUS, set the correct org context.
>select count(*) from ECE_PYO_PAYMENT_V;
3. If count returned is zero, then nothing is eligible.
log as follows:
>@ECEPYO.sql
1.
2.
3.
4.
5.
Get the Concurrent Manager Report Log and Diagnostics report

Get a copy of the file created
Provide output from VERIFY_FLATFILE
Get setup information
Get payment batch information
Extract Flags
The flag to reset on transactions on the base application header that will allow them to be
extracted again is the following: (Limit which transactions have the flags reset to limit the
volume of transactions to be extracted again.)
Table:
Column:
Dependent on Payables payment functionality.

25
Dependent on Payables Payment Workbench to submit the extract request.
26
Outbound Planning (830/DELFOR) and Shipping Schedule Transactions (862/DELJIT)
Design Overview
Provide supplier with your long-range forecast demand so the supplier may secure
material and labor resources to fulfill your demand.
Provide supplier with short term or firm requirements specifying shipment schedule
and location.
Extract may be submitted from Supplier Schedulings Scheduler Workbench, or

Supplier Schedulings AutoSchedule as an event-driven process.
Extract may be submitted using EDI Gateway.

Data Flow Diagram
EDI Gateway
Database Views for
830/DELFOR
Oracle
Supplier
Scheduling
Tables
ECE_SPSO_HEADERS_V
ECE_SPSO_HEADERS
ECE_SPSO_ITEMS_V
ECE_SPSO_ITEMS
ECE_SPSO_ITEM_DET
EDI Gateway
Database Views for
862/DELJIT
Oracle
Supplier
Scheduling
Tables
EDI Gateway
Interface Tables for
830/DELFOR
SPSOnnnn.dat
EDI Gateway
Interface Tables for
862/DELJIT
ECE_SSSO_HEADERS_V
ECE_SPSO_HEADERS
ECE_SSSO_ITEMS_V
ECE_SPSO_ITEMS
ECE_SPSO_ITEM_DET
SSSOnnnn.dat
Data Model
ECE_SPSO_HEADERS_V
ECE_SPSO_ITEMS_V
ECE_SSSO_HEADERS_V
ECE_SSSO_ITEMS_V
(for Planning Schedule 830)

(for Planning Schedule 830)
(for Shipping Schedules 862)
(for Shipping Schedules 862)
Utilize database views to extract from Supplier Scheduling the confirmed planning or shipping
schedules before applying user-entered selection criteria.
ECE_SPSO_HEADERS
27
ECE_SPSO_ITEMS
ECE_SPSO_ITEM_DET
(based on PL/SQL instead of database view)
Utilize EDI Gateway interface tables to store data from Supplier Scheduling for the confirmed
planning or shipping schedule.
Obsolete R10.7 EDI Gateway interface and extension tables due to design change
ECE_CHV_SCHED_HEADERS
ECE_CHV_SCHED_ITEMS
ECE_CHV_SCHED_ITEM_DET
ECE_CHV_SCHED_HEADERS_X
ECE_CHV_SCHED_ITEMS_X
ECE_CHV_SCHED_ITEM_DET_X
Extension Tables
ECE_SPSO_HEADERS_X
ECE_SPSO_ITEMS_X
ECE_SPSO_ITEM_DET_X
the interface file.
Concurrent Programs
Use Supplier Scheduling Scheduler Workbench or AutoSchedule to submit ECESPSO.sql (830)
or ECESSSO.sql (862) to the Concurrent Manager for processing.
Use Extract Programs to submit ECESPSO.sql (830) or ECESSSO.sql (862) to the Concurrent
Manager for processing.
Setting Up Test Cases in Supplier Scheduling
1.
2.
3.
Create planning and shipping schedules.

Confirm schedules.
Submit extract using EDI Gateway extract program or Supplier Scheduling.
Extract Flags for Planning Schedule
The flag to reset on transactions on the base application header that allows them to be extracted
Table:
Column:
Extract Flags for Shipping Schedule
28
Table:
Column:
Utilities
2. Execute header database view for 830/DELFOR as follows:
>select count(*) from ECE_SPSO_HEADERS_V; OR
3.
Execute header database view for 862/DELJIT as follows:

>select count(*) from ECE_SSSO_HEADERS_V;
4.
5.
If count returned is zero, then nothing is eligible

If count returned is greater than 0, execute 830/DELFOR extract code in
SQLPLUS as follows:
>@ECESPSO.sql (to get error log)
6.
If count returned is greater than 0, execute 862/DELJIT extract code in SQLPLUS

to get error log as follows:
>@ECESSSO.sql


Dependent on Supplier Schedulings Scheduler Workbench or AutoSchedule to submit

the extract request.
Get Planning or Shipping schedule report available in Supplier Scheduling.
29
Outbound Ship Notice/Manifest Transaction (856/DESADV)

Design Overview
Allows user to send a document itemizing the contents of a shipment to a customer.

Extract can be submitted from Order Entrys Departure Planning module as an eventdriven process.
Extract can be submitted using EDI Gateway.
Data Flow Diagram
Oracle
Order Entry
Departure
Planning
Tables
EDI Gateway
Database Views
EDI Gateway
Interface Tables
ECE_DSNO_ALLOWANCE_CHARGES_V
ECE_DSNO_ALLOWANCE_CHARGES
ECE_DSNO_CONTAINERS_V
ECE_DSNO_CONTAINERS
ECE_DSNO_DELIVERIES_V
ECE_DSNO_DELIVERIES
ECE_DSNO_DELIVERY_ATTRIBS_V
ECE_DSNO_DELIVERY_ATTRIBS
ECE_DSNO_ITEMS_V
ECE_DSNO_ITEMS
ECE_DSNO_ITEM_DETAILS_V
ECE_DSNO_ITEM_DETAILS
ECE_DSNO_ORDERS_V
ECE_DSNO_ORDERS
Flat File in
Outbound
Directory
DSNOnnnn.dat
ECE_DSNO_PACKED_QUANTITY_V
Data Model
Utilize database views to extract from Order Entry the closed departures before applying userentered selection criteria.
Utilize EDI Gateway interface tables to store data from Order Entry for closed departures.
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
ECE_DSNO_PACKED_QUANTITY_V
ECE_DSNO_ALLOWANCE_CHARGES
ECE_DSNO_CONTAINERS
ECE_DSNO_DELIVERIES
ECE_DSNO_DELIVERY_ATTRIBS
ECE_DSNO_ITEMS
ECE_DSNO_ITEM_DETAILS
30
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
the interface file.
Obsolete R10.7 EDI Gateway database views
Database views based on pick slip-based shipping model replaced with departurebased shipping model database views:
ECE_ASNO_LINES_V
ECE_ASNO_LINE_DETAILS_V
ECE_ASNO_HEADERS_V
Obsolete R10.7 EDI Gateway interface and extension tables
EDI Gateway interface tables based on pick slip-based shipping model replaced with
departure-based shipping model interface tables.
ECE_OE_SHIPPING_HEADERS
ECE_OE_SHIPPING_LINES
ECE_OE_SHIPPING_LINE_DETAILS
ECE_OE_SHIPPING_HEADERS_X
ECE_OE_SHIPPING_LINES_X
ECE_OE_SHIPPING_LINE_DETAILS_X
Concurrent Programs
Use Order Entry Departure Planning to submit ECEDSNO.sql to the Concurrent Manager for
processing.
Use Extract Programs to submit ECEDSNO.sql to the Concurrent Manager for processing.
Setting Up Test Cases in Departure Planning
1.
2.
3.
Define departure.
Close departure.
Submit extract using EDI Gateway extract program (or it may be automatically initiated by
Departure Planning).
Extract Flags
31
Table:
Column:
Utilities
>select count(*) from ECE_DSNO_DELIVERIES_V;
log as follows:
>@ECEDSNO.sql

Dependent on Order Entrys Departure Planning functionality.

Dependent on Order Entrys Departure Planning Workbench to submit the extract
request.
32
Outbound Application Advice Transaction (824/APERAK)
Design Overview
Provide supplier with discrepancy report in response to these transactions:
Inbound Invoice
Inbound Ship Notice
Inbound Shipment and Billing Notice
Data Flow Diagram
Flat File in
EDI Gateway
Database Views
EDI Gateway
Interface Tables
ECE_ADVO_HEADERS_V
ECE_ADVO_HEADERS_INTERFACE
ECE_ADVO_LINES_V
ECE_ADVO_LINES_INTERFACE
Outbound
Directory
Oracle
EDI Gateway
Tables
ADVOnnnn.dat
Data Model
ECE_ADVO_HEADERS_V
ECE_ADVO_DETAILS_V
Utilize database views to extract from Payables discrepancy data for a specific
inbound transaction before applying user-entered selection criteria.
EDI Gateway Application Advice tables:
ECE_ADVO_HEADERS
ECE_ADVO_DETAILS
ECE_ADVO_HEADERS_INTERFACE
ECE_ADVO_DETAILS_INTERFACE
Utilize EDI Gateway interface tables to store data from EDI Gateway application
advice tables for inbound transactions.
EDI Gateway interface tables are purged after data is successfully written to the
interface file.
Extension Tables
ECE_ADVO_HEADERS_INTERFACE_X
ECE_ADVO_DETAILS_INTERFACE_X
Utilize extension tables to store additional data from a non-Oracle data source to be
included in the interface file.
33
Concurrent Programs
Use Extract Programs to submit ECEADVO.sql to the Concurrent Manager for processing.
Import Invoices containing errors.

Import Ship Notices containing errors.
Submit extract using EDI Gateway extract program for specific inbound transaction.
Extract Flags
Table:
Column:
Utilities
If no flat file created, verify if eligible data exists by doing the following:
>select count(*) from ECE_ADVO_HEADERS_V;
log as follows:
>@ECEADVO.sql
If flat file created, use PL/SQL procedure ECE_UTILITIES.VERIFY_FLATFILE documented in
Technical Perspective, page 67 to verify the contents of the flat file.

Dependent on Payables to write invoice error data to EDI Gateway ECE_ADVO_HEADERS

and ECE_ADVO_DETAILS tables for reporting.
Dependent on Purchasing to write shipment error data to EDI Gateway
ECE_ADVO_HEADERS and ECE_ADVO_DETAILS tables for reporting.
Request from Payables, Payables Open Interface Rejections Report.
Request from Purchasing, Receiving Open Interface Errors Report.
34
Inbound Transactions
Inbound Purchase Order Transaction (850/ORDERS)

Design Overview
Provide user the ability to electronically receive purchase orders into Order Entry.
Data Flow Diagram
Flat File
from
Trading
Partner
Oracle
EDI
Gateway
EDI
Translator
Inbound
HEADERS_
Purchase
Order
INTERFACE
Order Entry
Open Interface Import
SO_
ECEPOI
Oracle EDI
SO_
Gatewayready
Flat File
LINES_
INTERFACE
Order Entry
Open
Interface
Import
Oracle
Order
Entry
(OrderImport)
Data Model
Order Entrys Open Interface tables:
SO_HEADERS_INTERFACE
SO_LINES_INTERFACE
Concurrent Programs
Use OrderImport Programs to submit ECEPOI.sql to the Concurrent Manager to populate the
Order Entry Open Interface tables with data from the inbound interface file.
Use Import Programs to submit the Order Entry Open Interface Import (OrderImport) program
to the Concurrent Manager to validate the data in the Order Entry Open Interface tables.
Import customer purchase orders.
35
Utilities
Use PL/SQL procedure ECE_UTILITIES.VERIFY_FLATFILE documented in Technical
Perspective, page 67 to verify the contents of the flat file.
1.
2.
3.
4.
5.
Enter Bug for EDI Gateway if the EDI Gateway import program failed.
Enter Bug for Payables if the Payables Open Interface Import failed.
Get a copy of the import file.
Dependent on Order Entrys Open Interface Import OrderImport.

Make sure all required fields contain a value.
36
Inbound Invoice Transaction (810/INVOIC)

Design Overview
Provide user the ability to electronically receive supplier invoices into Payables.
Supports error reporting via the outbound Application Advice (824/APERAK)
transaction.
Data Flow Diagram
Flat File
from
Trading
Partner
Oracle
EDI
Gateway
Payables Open
Interface Import
AP_
EDI
Translator
Inbound
Invoice
INVOICES_
INTERFACE
ECEINI
Oracle EDI
AP_
Gatewayready
Flat File
INVOICE_
LINES_
INTERFACE
AP
Open
Interface
Import
Oracle
Payables
APXIIMPT
Data Model
Payables Open Interface tables:
AP_INVOICES_INTERFACE
AP_INVOICE_LINES_INTERFACE
Concurrent Programs
Use Import Programs to submit ECEINI.sql to the Concurrent Manager to populate the
Payables Open Interface tables with data from the inbound interface file.
Use Import Programs to submit the Payables Open Interface Import (APXIIMPT) program to
the Concurrent Manager to validate the data in the Payables Open Interface tables.
Import supplier invoices.
Utilities
Verify the user setup by referring to the Post Implementation guide on the Metalink
web site.
37

1.
2.
3.
4.
5.
Enter Bug for EDI Gateway if the EDI Gateway import program failed
Enter Bug for Payables if the Payables Open Interface Import failed
Get a copy of the import file
Dependent on Payables Open Interface Import.

38
Inbound Ship Notice Transaction (856/DESADV)

Inbound Shipment & Billing Notice Transaction (857)
Design Overview
Provide user the ability to electronically receive supplier ship notice into Purchasing.
Provide user the ability to electronically receive supplier shipment and billing notice
into Purchasing and Payables.
Supports error reporting via the outbound Application Advice (824/APERAK)
transaction.
Data Flow Diagram
Flat File
from
Trading
Partner
EDI
Translator
Oracle EDI
Gatewayready
Flat File
Oracle
EDI
Gateway
Inbound
Ship
Notice
ECEASNII
OR
Shipment
& Billing
Notice
ECESBNI
Receiving Open
Interface
RCV_
HEADERS_
INTERFACE
RCV_
Receiving
Open
Interface
Oracle
Purchasing
RCVTP
TRANSACTIONS_
INTERFACE
Data Model
Receiving Open Interface tables:
RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE
Concurrent Programs
Use Import Programs to submit ECEASNI.sql (856) or ECESBNI.sql (857) to the Concurrent
Manager to populate the Receiving Open Interface tables with data from the inbound interface
file.
Use Import Programs to submit the Receiving Open Interface (RCVTP) program to the
Concurrent Manager to validate the data in the Receiving Open Interface tables.
Import supplier ship notices or shipment and billing notices
39
Utilities
Verify the user setup by referring to the Post Implementation guide on the Metalink
web site.
1.
2.
3.
4.
5.
Enter Bug for EDI Gateway if the EDI Gateway import program failed.
Enter Bug for Purchasing if the Receiving Open Interface failed.
Get a copy of the import file.
Dependent on Purchasings Receiving Open Interface.

40
Inbound Price/Sales Catalog (832/PRICAT)

Inbound Response to RFQ (843/QUOTES)
Design Overview
Provide users the ability to electronically receive supplier price catalogs into
Purchasing.
Provide users the ability to electronically receive supplier responses to RFQs into
Purchasing.
Data Flow Diagram
Flat File
from
Trading
Partner
EDI
Translator
Oracle EDI
Gatewayready
Flat File
Oracle
EDI
Gateway
Inbound
Price/Sales
Catalog
ECECATI
OR
Response
to RFQ
ECERRQI
Purchasing
Document
Open Interface
PO_
HEADERS_
INTERFACE
PO_
LINES_
Purchasing
Documents
Open
Interface
Oracle
Purchasing
POXPDOI
INTERFACE
Data Model
Purchasing Documents Open Interface tables:
PO_HEADERS_INTERFACE
PO_LINES_INTERFACE
Concurrent Programs
Use Import Programs to submit ECECATI.sql (832) or ECERRQI.sql (843) to the Concurrent
Manager to populate the Purchasing Documents Open Interface tables with data from the
inbound interface file.
Use Import Programs to submit the Purchasing Open Interface (POXPDOI) program to the
Concurrent Manager to validate the data in the Purchasing Documents Open Interface tables.
1.
2.
Import supplier price catalogs.

Import supplier response to RFQ.
41
Utilities
1.
2.
3.
Verify the user has current patch sets by referring to The Metalink web site.
Verify the user setup by referring to the Post Implementation guide on the Metalink web
site.
1.
2.
3.
4.
5.
Enter Bug for EDI Gateway if the EDI Gateway import program failed
Enter Bug for Purchasing if the Purchasing Documents Open Interface failed
Get a copy of the import file
Dependent on Purchasings Purchasing Documents Open Interface.

42
Postimplementation Issues
These are common postimplementation issues. See updated document on Metalink.
Invalid file path
System profile for inbound and outbound directory defined.
Directory access granted via utl_file_dir parameter in INIT.ORA file.
No file created
Directory must be write-enabled and access-granted.
Empty interface file created
Make sure Trading Partner defined.
Make sure Trading Partner is assigned to address entity for supplier, customer, bank branch or
warehouse.
Make sure transaction enabled for Trading Partner.
Make sure eligible documents exist in host application.
Interface file doesnt match Users Guide
Interface file definition in Users Guide match base line software.
Bug fixes may affect interface file definition.
Use report from Interface File Definition form to review interface file definition.
EDI Gateway import program failed
Use report log to determine error.
Correct error.
Rerun EDI Gateway import program.
Application Open Interface program failed
Determine if data has been imported into Application Open Interface tables.
Use report log to determine error.
Correct error.
Rerun Application Open Interface import program,
43
Code conversion error if no keys

Verify the following:
1. Verify code category is valid.
2. Verify valid code category assigned to table/view column to activate code
conversion.
3. Verify code conversion values exist for category code and internal/external
value.
Code conversion error if keys used
Verify the following:
1. Number of keys enabled in Code Conversion Categories =
Number of key columns selected in Assign Categories =
Number of key values in Code Conversion Values.
2.
Verify that key values entered on Code Conversion Values form are valid.
3.
Verify internal and external values in Code Conversion Values form are valid.
44
Oracle EDI Gateway

March 2002
Author: Bonnie Shebat Williams
Copyright Oracle Corporation 222
All Rights Reserved Printed in the U.S.A.
This document is provided for informational purposes only and
the information herein is subject to change without notice.
Please report any errors herein to Oracle Corporation. Oracle
Corporation does not provide any warranties covering and
specifically disclaims any liability in connection with this
document.
Oracle is a registered trademark and Enabling the
Information Age, Oracle, Oracle EDI Gateway, Oracle e-Commerce Gateway
are trademarks of Oracle Corporation.
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Worldwide Inquiries:
650.506.7000
Fax 650.506.7200
Copyright Oracle Corporation 2002
All Rights Reserved
45

Edi 11r107 Techinfo

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Edi 11r107 Techinfo

Transféré par

Droits d'auteur :

Formats disponibles

ORACLE EDI GATEWAY

Creation Date: March 8, 2002

Company Confidential - For internal use only

Trading Partner Set Up Form .......................................................................................11

Code Category Set Up Form.........................................................................................13

Interface File Definition Form ......................................................................................13

Extract Program in Concurrent Manager ...................................................................14

Import Program in Concurrent Manager ...................................................................15

Outbound Purchase Order Transaction (850/ORDERS)..........................................17

Company Confidential - For internal use only

Outbound Purchase Order Change Transaction (860/ORDCHG) .........................20

Outbound Invoices Transaction (810/INVOIC) ........................................................22

Outbound Payment Order/Remittance Advice Transaction

Outbound Planning (830/DELFOR) and Shipping Schedule Transactions

Outbound Ship Notice/Manifest Transaction (856/DESADV) ..............................30

Company Confidential - For internal use only

Obsolete R10.7 EDI Gateway interface and extension tables ..........................................31

Outbound Application Advice Transaction (824/APERAK) ..................................33

Inbound Transactions ...........................................................................................................35

Inbound Invoice Transaction (810/INVOIC).............................................................37

Inbound Ship Notice Transaction (856/DESADV) Inbound Shipment & Billing

Inbound Price/Sales Catalog (832/PRICAT) Inbound Response to RFQ

Post Implementation Issues .................................................................................................43

Company Confidential - For internal use only

Empty interface file created .................................................................................................43

Company Confidential - For internal use only

General Design Overview

Design Overview - EDI Gateway and all EDI transactions.

Company Confidential - For internal use only

From Order Entry

Several (for INI,

Company Confidential - For internal use only

EDI Gateway Forms

Represents a set of Trading Partner definitions

Data Flow Diagram

Table ECE_TP_GROUP is a master table to ECE_TP_HEADERS containing the

Upgrade from R10.7 to R11

EDI Gateway Forms

Company Confidential - For internal use only

Setting Up Test Cases

EDI Gateway Forms

Company Confidential - For internal use only

Trading Partner Set Up Form

Company Confidential - For internal use only

Select Trading Partner form in EDI Gateway.

EDI Gateway Forms

Company Confidential - For internal use only

Code Category Set Up Form

Interface File Definition Form

R10.7 to R11 Change

EDI Gateway Forms

Company Confidential - For internal use only

Extract Program in Concurrent Manager

Select Request to submit individual request.

EDI Gateway Forms

Company Confidential - For internal use only

Extract Transaction Multiple Times

Import Program in Concurrent Manager

Select Request to submit an individual request.

Answer Execute Open Interface

If Executing Open Interface in EDI Gateway:

If Executing Open Interface in Oracle Applications:

Enter Schedule options.

Company Confidential - For internal use only