Results for “value_basis”

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

Overview

The APPS.POBV_BKT_PO_LINE_PRICE_BREAKS view is a Business Intelligence (BKT) reporting object within the Oracle E-Business Suite Purchasing (PO) module. As indicated by the "BKT" designator and the "Retrofitted" description, this view was introduced or adapted to expose blanket purchase agreement price break data in a denormalized, report-friendly format. Price breaks are quantity-tiered pricing arrangements on a blanket purchase agreement (BPA), whereby a supplier offers progressively different unit prices as the ordered quantity increases. This view flattens that structure — joining line locations, lines, headers, and organization units — so that downstream reporting tools, discoverer workbooks, and integration extracts can retrieve price break information without reimplementing the underlying joins.

The view is defined with a WITH READ ONLY clause, confirming it is intended strictly for query and extraction rather than DML. Its presence in the APPS schema and its ownership under PO align it with standard EBS reporting conventions for the 12.1.1 and 12.2.2 releases.

Underlying Base Objects

The view is defined over four base objects, all exposed through APPS synonyms:

• PO_LINE_LOCATIONS_ALL (aliased PS) — the primary driving table, filtered to records where SHIPMENT_TYPE = 'PRICE BREAK', which isolates the price break shipment rows.
• PO_LINES_ALL (aliased PL) — provides the parent blanket line, joined on PO_LINE_ID.
• PO_HEADERS_ALL (aliased PH) — supplies the document header, restricted to TYPE_LOOKUP_CODE = 'BLANKET', ensuring only blanket agreements are returned.
• HR_ALL_ORGANIZATION_UNITS (aliased OP) — resolves the operating unit name, joined on PS.ORG_ID = OP.ORGANIZATION_ID.

The joins enforce that a price break row exists only where a matching blanket line and header exist, and the organization unit provides the operating unit context. A security predicate, '_SEC:PS.ORG_ID' IS NOT NULL, applies Multi-Org Access Control (MOAC) filtering so that users see only the operating units to which they are authorized. A label substitution, '_LA:PS.APPROVED_FLAG:PO_LOOKUP_CODES:YES/NO:DISPLAYED_FIELD', denotes the approved flag lookup display.

Key Columns

• PRICE_BREAK_ID — unique identifier for the price break (derived from LINE_LOCATION_ID).
• PRICE_BREAK_NUMBER — the shipment number of the price break record.
• PRICE_BREAK_QUANTITY — the quantity threshold at which the associated price or discount applies; this is the column users target when searching for "price_break_quantity."
• DISCOUNTED_PRICE — the unit price effective at the price break quantity.
• PRICE_DISCOUNT_PERCENTAGE — the discount percentage applied at that tier.
• BLANKET_PO_ID / BLANKET_PO_DOCUMENT_NUMBER — the parent blanket agreement identifier and its document number (SEGMENT1).
• PO_LINE_ID / LINE_NUMBER — the associated blanket line and its visible line number.
• OPERATING_UNIT_ID / OPERATING_UNIT_NAME — the operating unit owning the agreement.
• APPROVAL_DATE and the approval flag lookup — approval status and date of the shipment/price break.
• SHIP_TO_LOCATION_ID / SHIP_TO_ORGANIZATION_ID — the destination ship-to context.
• Audit columns — CREATED_DATE, CREATED_BY, LAST_UPDATED_DATE, LAST_UPDATED_BY.

Common Use Cases and Queries

Typical applications include price break validation, supplier tiered-pricing analysis, and MOAC-aware extracts. A simple query to retrieve quantity tiers for a blanket line:

• SELECT PRICE_BREAK_QUANTITY, DISCOUNTED_PRICE, PRICE_DISCOUNT_PERCENTAGE FROM APPS.POBV_BKT_PO_LINE_PRICE_BREAKS WHERE BLANKET_PO_DOCUMENT_NUMBER = :doc_num ORDER BY PRICE_BREAK_QUANTITY;
• SELECT BLANKET_PO_DOCUMENT_NUMBER, LINE_NUMBER, PRICE_BREAK_QUANTITY, DISCOUNTED_PRICE FROM APPS.POBV_BKT_PO_LINE_PRICE_BREAKS WHERE OPERATING_UNIT_NAME = :ou;

Because the view already resolves the header, line, and operating unit, it eliminates multi-table joins otherwise required against PO_LINE_LOCATIONS_ALL, PO_LINES_ALL, and PO_HEADERS_ALL, making it well suited to BI Publisher data templates and ad-hoc reporting.