Search Results firm_planned_status_flag

Overview

APPS.PO_PO_SUPPLY_VIEW is a seeded Oracle E-Business Suite database view owned by the APPS schema and registered in FND Design Data under the product short name PO. It exposes purchase order supply information in a denormalized form, joining purchase order header, line, line location, distribution, release, and inventory supply data. The view is classified as an internal, Oracle-internal-use-only object. Oracle Corporation does not support direct access to applications data through this object except from standard Oracle Applications programs; consequently, it should be treated as a read-only reporting and integration surface rather than a supported extension point. Its status is VALID, and in ETRM 12.2.2 it is built over a defined set of PO and inventory base tables.

Underlying Base Objects

The view is defined over the following documented base objects, referenced through synonyms: MTL_SUPPLY, MTL_UNITS_OF_MEASURE, PO_DISTRIBUTIONS_ALL, PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, and PO_RELEASES_ALL. The purchase order tables provide the document structure: headers supply vendor and PO number context, lines supply item and pricing context, line locations supply scheduling and receipt information, releases support blanket and planned order supply, and distributions provide destination and accounting-derived detail. MTL_SUPPLY contributes the supply record and inventory-side scheduling attributes, while MTL_UNITS_OF_MEASURE supports unit-of-measure relationships. Because the view consolidates these normalized tables, it presents a single row-oriented supply picture across sourcing documents.

Key Columns

The view exposes identifiers and descriptive attributes that align with purchasing and planning processes. ITEM_ID and ORGANIZATION_ID identify the item and destination organization. PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID, PO_DISTRIBUTION_ID, VENDOR_ID, and VENDOR_SITE_ID provide keys back to the sourcing document hierarchy. PO_NUMBER, LINE_NUM, and PO_REVISION_NUM identify the purchase order and revision. Quantities and units are represented by QUANTITY, PO_UOM_CODE, PRIMARY_UOM_QUANTITY, PRIMARY_UOM, UNIT_PRICE, and ITEM_REVISION. Scheduling columns include EXPECTED_DOCK_DATE (documented as the expected receipt date), PRINTED_DATE, MRP_EXPECTED_DELIVERY_DATE, and EXPECTED_DELIVERY_DATE. Planning-related fields include FIRM_PLANNED_STATUS_FLAG, MRP_PRIMARY_QUANTITY, MRP_PRIMARY_UOM, MRP_DESTINATION_TYPE_CODE, MRP_TO_ORGANIZATION_ID, and MRP_TO_SUBINVENTORY. DESTINATION_TYPE_CODE and MRP_DESTINATION_TYPE_CODE describe the destination context. For searches on "expected_dock_date," the relevant column is EXPECTED_DOCK_DATE, a DATE representing the expected receipt date for the supply.

Common Use Cases and Queries

Typical uses include purchase order supply reporting, expected receipt analysis, planning supply visibility, and integration extracts that require a flattened PO supply record. A common query filters and sorts by expected receipt date:

• SELECT po_number, line_num, item_id, organization_id, quantity, po_uom_code, expected_dock_date FROM apps.po_po_supply_view WHERE organization_id = :org_id AND expected_dock_date BETWEEN :start_date AND :end_date ORDER BY expected_dock_date, po_number, line_num;
• SELECT po_number, po_line_id, po_line_location_id, po_distribution_id, vendor_id, vendor_site_id, primary_uom_quantity, primary_uom FROM apps.po_po_supply_view WHERE po_header_id = :po_header_id;
• SELECT item_id, organization_id, SUM(primary_uom_quantity) FROM apps.po_po_supply_view WHERE expected_dock_date <= SYSDATE AND firm_planned_status_flag IS NOT NULL GROUP BY item_id, organization_id;

Because the object is documented as internal use only, production code should avoid direct dependencies on it where a supported API or concurrent program exists. Where direct querying is unavoidable, restrict access to read-only reporting schemas and validate behavior across both 12.1.1 and 12.2.2 environments, since column composition and underlying joins may differ by release.