Professional Documents
Culture Documents
6/2/13
If you enable Batch Control, each invoice must correspond to a record in this table. Your Oracle Payables application uses this information to group together invoices that one person entered in a batch. AP_CHECKS_ALL: It stores information about payments issued to suppliers or refunds received from suppliers. There is one row for each payment you issue to a supplier or refund received from a supplier. Oracle Payables application uses this information to record payments you make to suppliers or refunds you receive from suppliers. Oracle Payables application stores the supplier name and bank account name for auditing purposes, in case either one is changed after you create the payment. Oracle Payables application also stores address information for all payments. AP_HOLDS_ALL: It 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. AP_BANK_ACCOUNTS_ALL: It contains information about your bank accounts. There is one row for each bank account you define and each bank account must be affiliated with one bank branch. AP_BANK_ACCOUNT_USES_ALL: It stores information for the internal and external bank accounts you define in Oracle Payables and Oracle Receivables applications. AP_CARDS_ALL: It stores information about the corporate credit cards issued to your employees by your corporate credit card providers. AP_TRIAL_BALANCE: It contains denormalized information about invoices and payments posted to the accrual set of books.
www.club-oracle.com/forums/r12-important-ap-tables-and-brief-narrative-t4914/
2/2