[Home] [Help]
[Dependency Information]
Object Name: | AP_HOLDS_ALL |
---|---|
Object Type: | TABLE |
Owner: | AP |
FND Design Data: | ![]() |
Subobject Name: | |
Status: | VALID |
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.
.
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 Payables application 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 would result 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.
Tablespace: | ![]() |
---|---|
PCT Free: | 10 |
PCT Used: |
Index | Type | Uniqueness | Tablespace | Column |
---|---|---|---|---|
AP_HOLDS_N1 | NORMAL | NONUNIQUE |
![]() |
![]() ![]() |
AP_HOLDS_N2 | NORMAL | NONUNIQUE |
![]() |
![]() |
Name | Datatype | Length | Mandatory | Comments |
---|---|---|---|---|
INVOICE_ID | NUMBER | (15) | Yes | Invoice identifier |
LINE_LOCATION_ID | NUMBER | (15) | Purchase order line location identifier | |
HOLD_LOOKUP_CODE | VARCHAR2 | (25) | Yes | Name of hold code |
LAST_UPDATE_DATE | DATE | Yes | Standard Who column - date when a user last updated this row. | |
LAST_UPDATED_BY | NUMBER | (15) | Yes | Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID). |
HELD_BY | NUMBER | (15) | Yes | User that placed hold on invoice |
HOLD_DATE | DATE | Yes | Date user placed hold on invoice | |
HOLD_REASON | VARCHAR2 | (240) | Reason for hold being placed on invoice | |
RELEASE_LOOKUP_CODE | VARCHAR2 | (25) | Name of release code | |
RELEASE_REASON | VARCHAR2 | (240) | Reason for release being placed on invoice | |
STATUS_FLAG | VARCHAR2 | (25) | No longer used | |
LAST_UPDATE_LOGIN | NUMBER | (15) | Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID). | |
CREATION_DATE | DATE | Standard who column - date when this row was created. | ||
CREATED_BY | NUMBER | (15) | Standard who column - user who created this row (foreign key to FND_USER.USER_ID). | |
ATTRIBUTE_CATEGORY | VARCHAR2 | (150) | Descriptive flexfield structure definition column. | |
ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive flexfield segment | |
ORG_ID | NUMBER | (15) | Organization identifier | |
RESPONSIBILITY_ID | NUMBER | (15) | Responsibility identifier associated with Insufficient Funds hold | |
RCV_TRANSACTION_ID | NUMBER | Receipt identifier, RCV_TRANSACTIONS.TRANSACTION_ID, of receipt that this hold is assoicated with | ||
HOLD_DETAILS | VARCHAR2 | (2000) | ||
LINE_NUMBER | NUMBER | Invoice line number of the applied hold | ||
HOLD_ID | NUMBER | (15) | Yes | Hold identifier |
WF_STATUS | VARCHAR2 | (30) | Holds resolution workflow status |
Cut, paste (and edit) the following text to query this object:
SELECT INVOICE_ID
, LINE_LOCATION_ID
, HOLD_LOOKUP_CODE
, LAST_UPDATE_DATE
, LAST_UPDATED_BY
, HELD_BY
, HOLD_DATE
, HOLD_REASON
, RELEASE_LOOKUP_CODE
, RELEASE_REASON
, STATUS_FLAG
, LAST_UPDATE_LOGIN
, CREATION_DATE
, CREATED_BY
, ATTRIBUTE_CATEGORY
, ATTRIBUTE1
, ATTRIBUTE2
, ATTRIBUTE3
, ATTRIBUTE4
, ATTRIBUTE5
, ATTRIBUTE6
, ATTRIBUTE7
, ATTRIBUTE8
, ATTRIBUTE9
, ATTRIBUTE10
, ATTRIBUTE11
, ATTRIBUTE12
, ATTRIBUTE13
, ATTRIBUTE14
, ATTRIBUTE15
, ORG_ID
, RESPONSIBILITY_ID
, RCV_TRANSACTION_ID
, HOLD_DETAILS
, LINE_NUMBER
, HOLD_ID
, WF_STATUS
FROM AP.AP_HOLDS_ALL;
AP.AP_HOLDS_ALL does not reference any database object
AP.AP_HOLDS_ALL is referenced by following:
|
|
|