Results for “blanket_po_document_number”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.POFV_BKT_PO_LINE_PRICE_BREAKS view is a Purchasing (PO) module reporting object that exposes price break shipment records defined on blanket purchase agreements. In Oracle EBS, a blanket purchase agreement captures negotiated prices at the line level, and each line may be subdivided into one or more price break shipments, where quantity tiers correspond to discounted or overridden prices. This view consolidates those price break shipments with their parent line, header, operating unit, and ship-to context into a single denormalized result set, allowing report writers and integrators to query price break information without joining multiple base tables manually.

The view is marked as retrofitted and valid within the EBS 12.1.1 and 12.2.2 data model, owned by the APPS schema. Its primary filtering predicates restrict output to blanket agreement headers (TYPE_LOOKUP_CODE = 'BLANKET') and to shipments whose shipment type is 'PRICE BREAK', ensuring that only relevant tiered pricing rows are returned. The presence of the "_SEC:PS.ORG_ID" security predicate indicates that the view participates in Oracle's multi-org security model, enforcing operating unit access controls at query time.

Underlying Base Objects

The view is defined over several documented base objects. The central driver is PO_LINE_LOCATIONS_ALL, aliased PS, which stores the price break shipment rows. It is joined to PO_LINES_ALL (PL) on PO_LINE_ID and to PO_HEADERS_ALL (PH) on PO_HEADER_ID, linking price breaks to their blanket line and header. Operating unit information is resolved through HR_ALL_ORGANIZATION_UNITS (OP), while ship-to location detail comes from HR_LOCATIONS (LO) and ship-to organization detail from HR_ALL_ORGANIZATION_UNITS (OG) and MTL_PARAMETERS (OC). These last three joins are outer joins, so price break rows remain visible even when ship-to references are absent or incomplete. The documented reference to HR_GENERAL reflects the internal business group security machinery used by the APPS schema.

Key Columns

The most significant column for users searching on "blanket_po_id" is BLANKET_PO_ID, which surfaces the PO_HEADER_ID of the parent blanket agreement. This is the canonical key for linking a price break back to its agreement, and it corresponds directly to the PO_HEADER_ID column in PO_HEADERS_ALL. Adjacent columns include BLANKET_PO_DOCUMENT_NUMBER (the header SEGMENT1, i.e., the visible agreement number), PRICE_BREAK_ID (the LINE_LOCATION_ID of the price break shipment), PRICE_BREAK_NUMBER (SHIPMENT_NUM), and PO_LINE_ID with LINE_NUMBER for the parent line. Pricing columns include DISCOUNTED_PRICE (PRICE_OVERRIDE), PRICE_DISCOUNT_PERCENTAGE (PRICE_DISCOUNT), and PRICE_BREAK_QUANTITY (QUANTITY). Context columns include OPERATING_UNIT_ID and OPERATING_UNIT_NAME, APPROVAL_DATE, SHIP_TO_LOCATION, SHIP_TO_ORGANIZATION_ID, SHIP_TO_ORGANIZATION_CODE, SHIP_TO_ORGANIZATION_NAME, plus standard audit columns (CREATED_DATE, CREATED_BY, LAST_UPDATED_DATE, LAST_UPDATED_BY). The "_LA:APPROVED_FLAG" and "_DF" columns are descriptor columns interpreted by Oracle Forms-based tooling rather than ordinary report fields.

Common Use Cases and Queries

Typical uses include reporting negotiated price tiers for a given blanket, validating tiered pricing ahead of requisition or order placement, and integrating price break data into external pricing or procurement analytics systems.

• Retrieve all price breaks for a specific blanket agreement: SELECT price_break_id, blanket_po_document_number, line_number, price_break_quantity, discounted_price, price_discount_percentage FROM pofv_bkt_po_line_price_breaks WHERE blanket_po_id = :p_header_id ORDER BY line_number, price_break_quantity;
• List price breaks for a blanket by its visible document number: SELECT * FROM pofv_bkt_po_line_price_breaks WHERE blanket_po_document_number = 'BPA-1001';
• Report price breaks by operating unit for multi-org visibility: SELECT operating_unit_name, blanket_po_document_number, line_number, price_break_quantity, discounted_price FROM pofv_bkt_po_line_price_breaks WHERE operating_unit_id = :p_org_id;
• Identify price breaks whose ship-to organization is populated, joining context for downstream shipping analysis: SELECT blanket_po_document_number, line_number, price_break_quantity, discounted_price, ship_to_organization_code FROM pofv_bkt_po_line_price_breaks WHERE ship_to_organization_id IS NOT NULL;

Because the view enforces org security and is defined WITH READ ONLY, it is safe for concurrent reporting workloads and cannot be used for DML. Queries should filter on BLANKET_PO_ID or BLANKET_PO_DOCUMENT_NUMBER to limit result sets, as the view spans all accessible operating units.