Oracle Fusion · Data dictionary
AP_HOLDS_ALL
PayablesUsed in 1 subject areas11 reporting columns
Payables (AP), invoice holds. Reasons an invoice is blocked from payment.
Primary key: HOLD_ID
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| HOLD_DATE | ● | Hold date. | |
| HOLD_DETAILS | ● | Hold details. | |
| HOLD_ID | PK | ● | Identifier for the hold. |
| HOLD_LOOKUP_CODE | ● | Lookup code for the hold. | |
| HOLD_REASON | ● | Hold reason. | |
| LAST_UPDATE_DATE | ● | Date and time the row was last updated (the incremental-extract key). | |
| LINE_NUMBER | ● | Line number. | |
| RELEASE_LOOKUP_CODE | ● | Lookup code for the release. | |
| RELEASE_REASON | ● | Release reason. | |
| STATUS_FLAG | ● | Indicator (Y/N) for the status. | |
| WF_STATUS | ● | Status of the wf. |
4 reports read from this table
Change a column here and these are the reports that move with it, the blast radius for any change to AP_HOLDS_ALL.
- AP Disbursements Report
- AP Invoice Detail Report
- Payables Key Indicators Report
- Payables Matching Hold Detail Report
Where this surfaces in OTBI
The OTBI subject areas that expose this table. You can't join across them in OTBI, the owned conformed model joins them on shared keys.
Need the extract + dbt staging for AP_HOLDS_ALL?
We ship parameterized SQL, BICC config, and dbt models you own.
Problems that run through this table