Oracle Apps Payable Open Interface Import
Import invoice from legacy system into oracle Application using Payable Open Interface import. Explain Interface table and validation used for payable import. Explain the important columns need to populate for interface.
This Interface is used to import invoices from legacy system into Oracle Application.
Data is populated in interface table from the following sources.
Invoice which are rejected by the program, you can find the error why this records where rejected in the table AP_INTERFACE_REJECTIONS
Data is populated in interface table from the following sources.
- Supplier EDI invoices transferred through Oracle EDI Gateway
- Invoice load with custom SQL*Loader
- Credit card transactions you transferred using Credit Card Invoice Interface summary.
Interface Tables:
- AP_INVOICES_INTERFACE
- AP_INVOICE_LINES_INTERFACE
Base Table
- AP_INVOICES_ALL
- AP_INVOICE_DISTRIBUTIONS_ALL
Concurrent Program:
- Payables Open Interface Import
Validation
Header Validation- Check if Operating unit is valid or not.
- Check if Invoice Type is Valid or not.
- Check if Vendor Name is valid or not against which invoice is created.
- Check if Vendor site is valid or not.
- Check if Invoice currency is valid or not.
- Check invoice_num and invoice_date should not be null.
Line Validation
- Check if Line type is valid or not.
- Check dist_code_combination_id is valid or not.
- Some important columns that need to populate in interface table.
AP_INVOICES_INTERFACE
- INVOICE_ID
- INVOICE_NUM
- INVOICE_TYPE_LOOKUP_CODE
- STATUS
- REQUEST_ID
- INVOICE_DATE
- VENDOR_NUM
- VENDOR_SITE_CODE
- INVOICE_CURRENCY_CODE
AP_INVOICE_LINES_INTERFACE
- INVOICE_ID
- INVOICE_LINE_ID
- LINE_TYPE_LOOKUP _CODE
- AMOUNT
Invoice which are rejected by the program, you can find the error why this records where rejected in the table AP_INTERFACE_REJECTIONS
No comments:
Post a Comment