Oracle A75089-02 - Manual (Page 22)

How Oracle e-Commerce Gateway Works
1-4 Oracle e-Commerce Gateway User’s Guide
rules remain in the exception module where users can analyze the exceptions. After
corrective action in other modules or in the e-Commerce Gateway, the transaction
may be resubmitted for re-validation. Alternatively, if your trading partner will
re-send the transaction, you may delete the transaction from the exception module.
The base Oracle application continues validating transactions written to the
application’s open interface tables. All valid transactions are written to the
application tables. Invalid transactions remain in the open interface tables subject to
the application’s standard error handling procedures. All these processes are
automated so that transactions with no errors are posted directly to the base
application tables with no human intervention.
Outbound Transactions
For outbound transactions, the e-Commerce Gateway does the following:
A user-defined or an application event signals the e-Commerce Gateway to begin
the outbound process. User-defined events are set up using Oracle Application’s
Concurrent Manager.
The e-Commerce Gateway extracts data from the application transaction tables and
verifies that the receiving trading partner is authorized to receive the transaction.
Code conversion rules are applied to the data and the data is mapped and written
to the transaction interface data file. The format of this file is based on the standard
file layout define in the e-Commerce Gateway.