AP_INVOICES_ALL

AP_INVOICES_ALL contains records for invoices you enter. There is

one row for each invoice you enter. An invoice can have one or more
invoice distribution lines. An invoice can also have one or more
scheduled payments.
An invoice of type EXPENSE REPORT must relate to a row in
AP_EXPENSE_REPORT_HEADERS_ALL unless the record has been
purged from AP_EXPENSE_REPORT_HEADERS_ALL. Your Oracle
Payables application uses the INTEREST type invoice for interest that it
calculates on invoices that are overdue. Your Oracle Payables
application links the interest invoice to the original invoice by inserting
the INVOICE_ID in the AP_INVOICE_RELATIONSHIPS table.

AP_INVOICE_DISTRIBUTIONS_ALL
AP_INVOICE_DISTRIBUTIONS_ALL holds the distribution line
information that you enter for invoices. There is a row for each invoice
distribution. A distribution line must be associated with an invoice. An
invoice can have multiple distribution lines.
Your Oracle Payables application automatically creates rows in this table
when: 1) you choose a distribution set at the invoice level 2) you import
expense reports 3) you match an invoice to a purchase order or receipt; it
uses information from the matched purchase order or receipt 4) you
import invoices via the Open Interface Import process 5) you select to
automatically calculate tax 6) you select to automatically do
withholding.
Each invoice distribution line has its own accounting date. When you
account for an invoice, your OraclePayables application creates
accounting events, accounting entry headers and accounting entry lines
for those distribution lines that have accounting dates included in the
selected accounting date range for the Payables Accounting Process.
The accounting entries can then be transferred over to General Ledger
by running the Transfer to General Ledger process which creates journal
entries. Values for POSTED_FLAG may be Y for accounted
distributions or N for distributions that have not been accounted.
Values for ACCRUAL_POSTED_FLAG maybe Y if distribution has been
accounted and system is set up for accrual basis accounting or N if
either distribution has not been accounted or accrual basis accounting is
not used.
Values for CASH_POSTED_FLAG may be Y if distribution has been
accounted and system is set up for cash basis accounting, N if either
distribution has not been accounted or system is not set up for cash basis
accounting or P if distribution has been partially accounted in the cash
set of books.
The MATCH_STATUS_FLAG indicates the approval status for the
distribution. Values for the MATCH_STATUS_FLAG can be null or N
for invoice distributions that Approval has not tested or T for
distributions that have been tested or A for distributions that have been
tested and approved.
Invoice distributions may be interfaced over/from Oracle Assets or
Oracle Projects. Your Oracle Payablesapplication sets the
ASSETS_ADDITION_FLAG to U for distributions not tested by Oracle
Assets; Oracle Assets then adjusts this flag after it tests a distribution for assignment as an asset.

To avoid the same invoice distribution being

interfaced to both Oracle Projects and Oracle Assets, you must interface
any project–related invoice distribution to Oracle Projects before you can
interface it to Oracle Assets. If the project–related invoice distribution is
charged to a capital project in Oracle Projects, Oracle Projectssets the
ASSET_ADDITION_FLAG to P when the PA_ADDITION_FLAG is set
to Y, Z or T. Oracle Assets only picks up invoice distributions with the
ASSET_ADDITION_FLAGset to U and if project–related, with the
PA_ADDITION_FLAG set to Y, Z, or T. PA_ADDITION_FLAG tracks
the status of project–related supplier invoice distribution lines and
expense report distribution lines.

For supplier invoice distributions

entered via Oracle Payables, the PA_ADDITION_FLAGis set to N if the
distribution is project–related, otherwise it is set to E and it is updated
by Oracle Projects when the distribution is processed by the Oracle
Projects Interface Supplier Invoiceprocess. Oracle Projects sets the
PA_ADDITION_FLAG to Y or Z after the item is successfully processed,
or may be set to a rejection code if the line is rejected during transfer to
Oracle Projects; see QuickCodes listing for all the errors. You must
correct the rejection reason an try to retransfer the line. For supplier
invoice adjustment lines interfaced from OracleProjects to Oracle
Payables (which must net to zero with another line), the value for the
PA_ADDITION_FLAG is set to T. For expense report distributions
interfaced from Oracle Projects to Oracle Payables via Invoice Import,
this value is set to N. This row is never picked up by the Interface
Supplier Invoices process based on the
AP_INVOICES.INVOICE_TYPE_LOOKUP_CODE = EXPENSE
REPORT. For expense report adjustment lines interfaced from Oracle
Projects to Oracle Payables which net to zero with another line, this
value is set to T. Both lines are associated with the original invoice by
the Oracle Projects Interface Expense Reports to AP process.
Values for the ENCUMBERED_FLAG are as follows: Y indicates a
regular distribution that has been successfully encumbered by Payables;
W indicates a regular distribution that has been encumbered in advisory
mode even though insufficient funds existed; H indicates a regular
distribution that has not been encumbered because it was put on hold;
Nor null indicates a regular line that has not been encumbered because
it has not been looked at yet; D is the same as Y for a reversal
distribution line; X is the same as W for a reversal distribution line; P is
the same as H for a reversal distribution line; R indicates a line to be
ignored by encumbrance and approval code because neither the original
nor the reversal distributions were looked at and they offset each other
so, they can be ignored.