The same tables appear in the Assign Categories window, under View Name, for this transaction. Erroneous data are marked in the Payables database for future error reporting and correction. Valid data are written to the application tables. These tables are populated by the EDI Gateway import program and the data processed by the Payables Open Interface Import API. The following tables appear in the Interface File Definition window for this transaction. To define an invoice hold reason, use the Invoice Approvals window. This may be useful during implementation of a new trading partner to separate electronic invoices from other invoices in your Payables system. All invoices being imported into Payables may be placed on hold using the unique Invoice Hold Reason. You can optionally set up an Invoice Hold Reason unique to the this transaction. Prerequisite Optional Setup in Oracle Payables Using the Payables Open Interface, you can accomplish high-volume invoice import complete with all standard on-line invoice entry features, including purchase order matching, invoice approval, and invoice batch processing.Īpplication Open Interface(s) Payables Open Interface Use this transaction to import supplier invoices into your Oracle Payables system for manual or electronic payment. Your customer provides you with payment details ( EDI 820).Ĭheck out our glossary for more helpful definitions.Inbound Invoice (810 / INVOIC) (Oracle EDI Gateway Help). Your customer confirms receipt of your invoice (EDI 997).You send an invoice for the order (EDI 810).Your customer’s order is out the door, and you share the shipment details ( EDI 856).
0 Comments
Leave a Reply. |