- goal: What fields in tables ap_invoices_interface and ap_invoice_lines_interface should be populated to import invoices matched to Purchasing order ( PO )?
- fact: APXIIMPT – Payables Open Interface Import
- fact: Oracle Payables 11.5
- fact: Oracle Payables 11
- fact: Oracle Payables 10.7
fix:
PO MATCHED INVOICES
AP_INVOICES_INTERFACE:
================
Required Columns
================
INVOICE_ID (Populated from AP_INVOICES_INTERFACE_S.NEXTVAL)
INVOICE_NUM (Must be unique to the supplier)
PO_NUMBER (An approved, not cancelled, not closed or final closed PO. Validated against PO_HEADERS)
INVOICE_AMOUNT (Positive Amount)
SOURCE (Must be in select lookup_code from ap_lookup_codes where lookup_type='SOURCE')
ORG_ID (Required in Multi-Org Environment. Validated against AP_SYSTEM_PARAMETERS_ALL.ORG_ID)
================
Optional Columns
================
INVOICE_DATE (Defaulted to SYSDATE)
INVOICE_TYPE_LOOKUP_CODE (Defaulted to 'STANDARD')
INVOICE_CURRENCY_CODE (Defaulted from PO_VENDOR_SITES.INVOICE_CURRENCY_CODE)
EXCHANGE_RATE_TYPE (Defaulted from AP_SYSTEM_PARAMETERS.DEFAULT_EXCHANGE_RATE_TYPE)
TERMS_ID or TERMS_NAME (Defaulted from PO_VENDOR_SITES.TERMS_ID)
DOC_CATEGORY_CODE (Only populated if using automatic voucher number)
PAYMENT_METHOD_LOOKUP_CODE (Defaulted from PO_VENDOR_SITES.PAYMENT_METHOD_LOOKUP_CODE)
PAY_GROUP_LOOKUP_CODE (Defaulted from PO_VENDOR_SITES.PAY_GROUP_LOOKUP_CODE)
ACCTS_PAY_CODE_COMBINATION_ID (Defaulted from PO_VENDOR_SITES.ACCTS_PAY_CODE_COMBINAITON_ID)
GROUP_ID (Group identifier. Suggest to use it)
STATUS (DO NOT POPULATE IT)
==========================
AP_INVOICE_LINES_INTERFACE
==========================
Required Columns for PO Matched Lines
=====================================
INVOICE_ID (Populated from AP_INVOICES_INTERFACE.INVOICE_ID)
INVOICE_LINE_ID (Populated from AP_INVOICE_LINES_INTERFACE_S.NEXTVAL)
LINE_NUMBER (A unqiue number to the invoice)
LINE_TYPE_LOOKUP_CODE ('ITEM')
AMOUNT (Should be QUANTITY_INVOICED * UNIT_PRICE)
======================================
If MATCH_OPTION is 'P', then populate:
======================================
RELEASE_NUM or PO_RELEASE_ID (For Blanket Release only, validated against PO_RELEASES_ALL)
PO_NUMBER or PO_HEADER_ID (Validated against PO_HEADER_ALL)
PO_LINE_NUMBER or PO_LINE_ID (Validated against PO_LINES_ALL)
PO_SHIPMENT_NUM or PO_LINE_LOCATION_ID (Validated against PO_LINE_LOCATIONS_ALL)
======================================
If MATCH_OPTION is 'R', then populate:
======================================
RECEIPT_NUMBER (Validated against RCV_SHIPMENT_HEADERS.RECEIPT_NUM)
RCV_TRANSACTION_ID or PO_LINE_LOCATION_ID (Validated against RCV_TRANSACTIONS)
======================================
Optional Columns for PO Matched Lines:
======================================
QUANTITY_INVOICED (Populated if different from PO shipment)
UNIT_PRICE (Populated if different from PO shipment)
MATCH_OPTION ('P' or 'R' or Defaulted from PO_VENDOR_SITES.MATCH_OPTION)
ACCOUNTING_DATE (Defaulted from INVOICE_DATE or SYSDATE)
FINAL_MATCH_FLAG (Populated 'Y' if it is final matching)
INVENTORY_ITEM_ID (Validated against PO_LINES.INVENTORY_ITEM_ID)
INVENTORY_DESCRIPTION (Validated against PO_LINES.INVENTORY_ITEM_DESCRIPTION)
SHIP_TO_LOCATION_CODE (Populated if different from PO shipment)
PRICE_CORRECTION_FLAG (Populated 'Y' if it is price correction)
Like this:
Like Loading...
Pingback: [AP000001] What Fields in Tables Ap_Invoices_Interface and Ap_Invoice_Lines_Interface Should Be Populated to Import Invoices Matched to Purchasing Order (PO)? « OraPedia
Pingback: [HR000009] Why an ex-employee cannot be seen when a custom security profile is used? « OraPedia