Oracle A75089-02 - Manual (Page 102)

Extensible Architecture
8-2 Oracle e-Commerce Gateway User’s Guide
Extensible Architecture
The Oracle e-Commerce Gateway provides two methods to add additional data
elements that are not defined in Oracle Applications to EDI transactions:
■
Descriptive flexfields.
■
Oracle e-Commerce Gateway extensible architecture.
Either method may be used separately, or both methods may be used together to
customize a specific transaction to meet business needs. Descriptive flexfields may
be used for both inbound and outbound transactions, while extensible architecture
applies only to outbound transactions.
Most business needs for additional data can be accommodated by the use of
descriptive flexfields. Use extensible architecture if data from an outside application
must be merged with Oracle Applications data to create a single outbound
transaction.
For complete information, see: Extensible e-Commerce Gateway Architecture,
Oracle e-Commerce Gateway Implementation Manual.
Running the Application Advice Outbound (ADVO) Extract Program
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 e-Commerce Gateway product. The processing errors are reported to
the trading partner using the Application Advice transaction.
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.