Analytics Catalog/Data dictionary/PO_LINES_DRAFT_ALL
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · Data dictionary

PO_LINES_DRAFT_ALL

ProcurementUsed in 11 subject areas17 reporting columns

Purchasing (PO), transaction table (rows scoped across all operating units).

Likely primary key: PO_LINE_ID (inferred from Oracle naming conventions, verify against Tables & Views)
Joins (inferred from key columns): PO_LINE_ID → PO_LINES_ALL

Columns

ColumnKeyIn reportsDescription (inferred)
CONSIGNMENT_LINE_FLAG●Indicator (Y/N) for the consignment line.
FUNDS_STATUS●Status of the funds.
ITEM_DESCRIPTION●Description of the item.
ITEM_ID●Identifier for the item.
ITEM_REVISION●Item revision.
LINE_NUM●Line number.
MIN_RELEASE_AMOUNT●Min release amount.
NEGOTIATED_BY_PREPARER_FLAG●Indicator (Y/N) for the negotiated by preparer.
NOTE_TO_VENDOR●Note to vendor.
PO_LINE_IDPK?●Identifier for the purchase order line.
PURCHASE_BASIS●Purchase basis.
QUANTITY●Quantity.
REASON_FOR_CHANGE●Reason for change.
SHIPPING_UOM_CODE●Code identifying the shipping unit of measure.
UNIT_PRICE●Unit price.
UOM_CODE●Code identifying the unit of measure.
VENDOR_PRODUCT_NUM●Vendor product number.

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. In OTBI they combine only through shared dimensions or set operators such as union, inside one application; the owned conformed model joins this table across modules and systems on conformed keys.

Need the extract + dbt staging for PO_LINES_DRAFT_ALL?
We ship parameterized SQL, BICC config, and dbt models you own.
Talk to us
Problems that run through this table
What the extract does not carry · The export ceiling · The extraction pattern