Oracle Fusion · Data dictionary
PO_LINE_LOCATIONS_DRAFT_ALL
ProcurementUsed in 6 subject areas39 reporting columns
Purchasing (PO), transaction table (rows scoped across all operating units).
Primary key: not yet catalogued for PO_LINE_LOCATIONS_DRAFT_ALL, reference Oracle Tables & Views guide.
Joins (inferred from key columns): LINE_LOCATION_ID → PO_LINE_LOCATIONS_ALL
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| ACCRUE_ON_RECEIPT_FLAG | ● | Indicator (Y/N) for the accrue on receipt. | |
| ALLOW_SUBSTITUTE_RECEIPTS_FLAG | ● | Indicator (Y/N) for the allow substitute receipts. | |
| BACK_TO_BACK_FLAG | ● | Indicator (Y/N) for the back to back. | |
| COUNTRY_OF_ORIGIN_CODE | ● | Code identifying the country of origin. | |
| DAYS_LATE_RECEIPT_ALLOWED | ● | Days late receipt allowed. | |
| DESTINATION_TYPE_CODE | ● | Code identifying the destination type. | |
| END_DATE | ● | End date. | |
| ENFORCE_SHIP_TO_LOCATION_CODE | ● | Code identifying the enforce shipment to location. | |
| FUNDS_STATUS | ● | Status of the funds. | |
| INPUT_TAX_CLASSIFICATION_CODE | ● | Code identifying the input tax classification. | |
| LAST_ACCEPT_DATE | ● | Last accept date. | |
| LINE_INTENDED_USE | ● | Line intended use. | |
| LINE_LOCATION_ID | ● | Identifier for the line location. | |
| MODE_OF_TRANSPORT | ● | Mode of transport. | |
| NEED_BY_DATE | ● | Need by date. | |
| PRICE_DISCOUNT | ● | Price discount. | |
| PRICE_OVERRIDE | ● | Price override. | |
| PRODUCT_CATEGORY | ● | Product category. | |
| PRODUCT_FISC_CLASSIFICATION | ● | Product fisc classification. | |
| PRODUCT_TYPE | ● | Type of product. | |
| PROMISED_DATE | ● | Promised date. | |
| PROMISED_SHIP_DATE | ● | Promised shipment date. | |
| QTY_RCV_EXCEPTION_CODE | ● | Code identifying the quantity receiving exception. | |
| QUANTITY | ● | Quantity. | |
| REASON_FOR_CHANGE | ● | Reason for change. | |
| RECEIPT_DAYS_EXCEPTION_CODE | ● | Code identifying the receipt days exception. | |
| REQUESTED_SHIP_DATE | ● | Requested shipment date. | |
| SALES_ORDER_NUMBER | ● | Sales order number. | |
| SERVICE_LEVEL | ● | Service level. | |
| SFO_AGREEMENT_NUMBER | ● | Sfo agreement number. | |
| SHIPMENT_NUM | ● | Shipment number. | |
| SHIPPING_UOM_CODE | ● | Code identifying the shipping unit of measure. | |
| SHIP_TO_CUST_LOCATION_ID | ● | Identifier for the shipment to customer location. | |
| SHIP_TO_LOCATION_ID | ● | Identifier for the shipment to location. | |
| START_DATE | ● | Start date. | |
| SUPPLIER_ORDER_LINE_NUMBER | ● | Supplier order line number. | |
| TRX_BUSINESS_CATEGORY | ● | Transaction business category. | |
| UOM_CODE | ● | Code identifying the unit of measure. | |
| USER_DEFINED_FISC_CLASS | ● | User defined fisc class. |
Used by reports
No cataloged report reads from this table yet, it's part of the broader Fusion dictionary.
- ,
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.
- Maintenance Management - Purchased Item Usage Real Time
- Manufacturing - Purchased Item Usage Real Time
- Procurement - Pending Change Orders Real Time
- Procurement - Procure To Pay Real Time
- Procurement - Purchasing Real Time
- Procurement - Requisitions Real Time
Need the extract + dbt staging for PO_LINE_LOCATIONS_DRAFT_ALL?
We ship parameterized SQL, BICC config, and dbt models you own.
Problems that run through this table