Account PayablesTable Or View:TableImportant columns:1.
INVOICE_ID : Invoice identifier2.
LINE_LOCATION_ID : Purchase order line location identifier3.
HOLD_LOOKUP_CODE : Name of hold code4.
HELD_BY : User that placed hold on invoice5.
HOLD_DATE : Date user placed hold on invoice6.
HOLD_REASON : Reason for hold being placed on invoice7.
RELEASE_LOOKUP_CODE : Name of release code8.
RELEASE_REASON : Reason for release being placed on invoice9.
LINE_NUMBER : Invoice line number of the applied hold10.
HOLD_ID : Hold identifier
WF_STATUS : Holds resolution workflow status
AP_HOLDS_ALL contains information about holds that you or your Oracle Payables applicationplace 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 invoicemay have one or more corresponding rows in this table. Your Oracle Payables application does notpay invoices that have one or more unreleased holds recorded in this table.This table holds information referenced by the Invoice Holds window.In the strictest sense, AP_HOLDS_ALL has no primary key. It is possible for your Oracle Payablesapplication to place a certain type of hold on an invoice, then release it, then place another hold of the same type (if data changes before each submission of Payables Invoice Validation), which wouldresult in a duplicate primary key. But for practical purposes, the primary key is a concatenation of INVOICE_ID, LINE_LOCATION_ID, and HOLD_LOOKUP_CODE.