Download Oracle® e-Commerce Gateway

Inbound Transactions
Before an inbound transaction can be processed, the user needs to determine if the
predefined transaction record definition meets his business requirements and if the
predefined process rules and column rules that are assigned to the transactions meet his
needs. If the user does not perform this step, the Oracle e-Commerce Gateway uses the
seeded rules and actions for data validation.
Information concerning the Interface File Definition window and the establishing of
process and column rules can be found in this manual. Refer to Determine Process and
Column Rules and Actions and Modify Transaction Interface File for more details.
After an inbound transaction request is executed, users have the ability to view the
documents with exceptions using the View Staged Documents window.
After processing any inbound transaction, the user should check the concurrent
manager status. If it has a status of warning or error, the user can go to the View Staged
Documents window to see the document details such as rule exceptions and column
values. Users should also check the log file for other processing information.
View Staged Documents Window
The View Staged Documents window is used to view the results of inbound document
processing. Users access this window to display the number of documents in the
staging tables and to see if any failed the validation process. Users can drill down to
view the document numbers such as PO Number or Invoice Number that have rule
exceptions. From this window, users can select documents that have rule exceptions
and resubmit (after the errors have been resolved) or delete the documents.
This window consists of two major components. The left side shows the transactions in
a tree format and the right side shows the corresponding selected level summary. The
Summary shows different information depending on the tree node that is selected. The
tree data is only a snapshot of the staging table. Users need to Refresh the view to see
any new/modified data in the staging table.
Two functions are available from this window. The Resubmit function allows the users
to resubmit the given set of documents or a single document to be processed again
through the inbound process after errors have been corrected. For example, users can
select IN:Invoice (810/INVOIC) and use the resubmit function. In this case, the inbound
process will revalidate all the Invoices that have a status of Skip Document. The status
will be changed to Reprocess and a concurrent request is submitted to process the
documents. Also, the tree is refreshed with new data.
The Delete function enables users to delete the given set of documents or a single
document and the corresponding rule exceptions. For example, users can select Trading
Partner Alpha and use the Delete function. In this case, it deletes all of the invoices that
have a status of Skip Document for Trading Partner Alpha. After deleting the
documents, the document tree is refreshed without the deleted documents.
Troubleshooting 8-13