Anda di halaman 1dari 3

AP_INVOICES_ALL

AP_INVOICE_DISTRIBUTIONS_ALL
AP_INVOICE_PAYMENTS_ALL
AP_PAYMENT_HISTORY_ALL
AP_PAYMENT_DISTRIBUTIONS_ALL
AP_PAYMENT_SCHEDULES_ALL
AP_HOLDS_ALL
AP_SELECTED_INVOICES_ALL
AP_SELECTED_INVOICE_CHECKS_ALL
AP_CHECKS_ALL
AP_ACCOUNTING_EVENTS_ALL (Invoice)
AP_ACCOUNTING_EVENTS_ALL (Payment)
AP_AE_HEADERS_ALL (Invoice)
AP_AE_HEADERS_ALL (Payment)
AP_AE_LINES_ALL (Invoice)
AP_AE_LINES_ALL (Payment)
AP_ENCUMBRANCE_LINES_ALL
AP_INVOICES_ALL
INVOICE_ID (PK)
AP_HOLDS_ALL.INVOICE_ID
AP_INVOICE_DISTRIBUTIONS_ALL.INVOICE_ID
AP_INVOICE_DISTRIBUTIONS_ALL.PARENT_INVOICE_ID
AP_INVOICE_PAYMENTS_ALL.INVOICE_ID
AP_INVOICE_PREPAYS_ALL.PREPAY_ID
AP_INVOICE_PREPAYS_ALL.INVOICE_ID
AP_PAYMENT_SCHEDULES_ALL.INVOICE_ID
-------------------------------------------------------------
AP_INVOICE_DISTRIBUTIONS_ALL - holds the distribution information that is manually entered or system-
generated. There is one row for each invoice distribution.
When you account for an invoice, the Payables Accounting Process creates accounting events, accounting entry
headers and accounting entry lines for those distributions that have accounting dates included in the selected
accounting date range. The Transfer to General Ledger process can then transfer the accounting entries to
General Ledger as journal entries. Values forPOSTED _FLA G are Y for accounted distributions or N for
unaccounted distributions
INVOICE_ID
INVOICE_DISTRIBUTION_ID (PK)
DISTRIBUTION_LINE_NUMBER
ACCOUNTING_EVENT_ID - Accounting event identifier. Refers to the accounting event that accounted for
the distribution
PARENT_REVERSAL_ID - Invoice distribution identifier for distribution being reversed by the current
distribution
-------------------------------------------------------------
AP_ACCOUNTING_EVENTS_ALL
ACCOUNTING_EVENT_ID (PK)
EVENT_TYPE_CODE - Indicates the state of the accounting entries for the accounting event
SOURCE_TABLE - Table where event originating document resides. Possible values are AP_INVOICES or
AP_CHECKS
SOURCE_ID - Primary key for document originating the current event. Depending on the value for
source_table
it will contain either invoice_id or check_id
EVENT_NUMBER - Accounting event number for a given document
(e.g. Invoice #101 may have 3 accounting events associated with it, the event number acts as a sequence for
Invoice #101)
*What are the diff EVENT_TYPE_CODE ?
--------------------------------------------------------------
AP_AE_HEADERS_ALL - An accounting entry header is an entity grouping all accounting entry lines created
for a given accounting event and a particular set of books. An accounting entry header can either be transferred
over to GL or not at all.
AE_HEADER_ID (PK) - Accounting entry header identifier
ACCOUNTING_EVENT_ID - Accounting event identifier
*What does this ('An accounting entry header is an entity grouping all accounting entry lines created for a given
accounting event and a particular set of books') mean ?
--------------------------------------------------------------
AP_AE_LINES_ALL - An accounting entry line is an entity containing a proper accounting entry with debits or
credits both in transaction currency as well as functional currency along with an account and other reference
information pointing to the transaction data that originated the accounting entry line. An accounting entry line is
grouped with other accounting entry lines for a specific accounting entry header. Any such group of accounting
entry lines should result in balanced entries in the functional currency.
AE_LINE_NUMBER - Sequential number for accounting entry line within accounting entry header. E.g. 1, 2, 3
AE_LINE_TYPE_CODE - Accounting entry line type. E.g. Liability, Charge, etc
SOURCE_TABLE - Table where transaction document associated with accounting entry line resides.
Possible values are: AP_INVOICES, AP_INVOICE_DISTRIBUTIONS, AP_CHECKS,
AP_INVOICE_PAYMENTS
SOURCE_ID - Primary key for document originating the current accounting entry line. Depending on the value
for source_table it will contain either invoice_id, invoice_distribution_id, check_id or invoice_payment_id
--------------------------------------------------------------
AP_INVOICE_PAYMENTS_ALL - contains records of invoice payments that you made to suppliers.There is
one row for each payment you make
=======================
for each invoice. There is one payment and one invoice for each payment in this table. Your Oracle Payables
application updates this
table when you confirm an automatic payment batch, enter a manual payment, or process a Quick payment.
When you void a payment,
your Oracle Payables application inserts an additional payment line that is the negative of the original payment
line.
Values for POSTED_FLAG may be 'Y' for accounted payments
or 'N' for unaccounted payments. Values for
ACCRUAL_POSTED_FLAG may be 'Y' for accounted
payments or 'N' for unaccounted payments under
accrual basis accounting; values for CASH_POSTED_FLAG
may be 'Y' for accounted payments or 'N' for unaccounted
payments under cash basis accounting.
For manual payments and Quick payments, this table
corresponds to the Select Invoices window in the Payment workbench
INVOICE_PAYMENT_ID (PK)
CHECK_ID - Payment identifier
INVOICE_ID - Invoice identifier
ACCOUNTING_EVENT_ID - Accounting Event Identifier
REVERSAL_FLAG --> Flag that indicates whether current invoice payment is a reversal of another invoice
payment
Generally it is null for payment creation records and for payment cancellation records it will have value
i.e payment cancellation records only have value.
If the reveral_flag ='Y' means the payment is reversed and if reveral_flag ='N' means the payment is not
reversed.
To be precise reveral_flag indicates whether current invoice payment is a reversal of another invoice payment.
--------------------------------------------------------------
AP_PAYMENT_HISTORY_ALL - stores the clearing/unclearing history for payments. It also stores the
maturity history for future dated payments. The table contains a row for each future dated payment, once the
future dated payment matures, i.e. becomes negotiable. Any time a payment is cleared or uncleared, a row is
inserted into this table for the payment. The values for TRANSACTION_TYPE can be PAYMENT
MATURITY, PAYMENT CLEARING, or PAYMENT UNCLEARING. Each row in this table also has the
accounting status for the maturity, clearing or unclearing event.
PAYMENT_HISTORY_ID (PK)
CHECK_ID - Payment identifier
TRANSACTION_TYPE VARCHAR2 - Transaction type - value can be PAYMENT MATURITY, PAYMENT
CLEARING, or PAYMENT UNCLEARING
ACCOUNTING_EVENT_ID - Accounting event identifier
--------------------------------------------------------------
AP_PAYMENT_DISTRIBUTIONS_ALL -
INVOICE_PAYMENT_ID (PK)
PAYMENT_LINE_NUMBER (PK)
--------------------------------------------------------------
AP_PAYMENT_SCHEDULES_ALL -
INVOICE_ID (PK)
PAYMENT_NUM (PK)
AMOUNT_REMAINING - Invoice amount remaining for payment
GROSS_AMOUNT - Gross amount due for a scheduled payment
HOLD_FLAG - Flag that indicates if scheduled payment is on hold (Y or N)
PAYMENT_METHOD_LOOKUP_CODE - Payment method (for example, CHECK, WIRE, EFT)
PAYMENT_STATUS_FLAG - Flag that indicates if payment has been made (Y, N, or P)
--------------------------------------------------------------
AP_HOLDS_ALL - AP_HOLDS_ALL contains information about holds that you or your Oracle Payables
application place on an invoice.
For non-matching holds, there is one row for each hold placed on an invoice. For matching holds, there is
one
row for each hold
placed on an invoice-shipment match. An invoice may have one or more corresponding rows in this table.
Your
Oracle Payables application
does not pay invoices that have one or more unreleased holds recorded in this table.

Anda mungkin juga menyukai