Results for “pobv_bkt_po_distributions”

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

Overview

The view APPS.POBV_BKT_PO_DISTRIBUTIONS is a Purchasing (PO) module database view in Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its ETRM description is marked "- Retrofitted," indicating it was introduced or re-created to restore functionality that existed in an earlier release line, most likely to preserve backward compatibility for downstream reports, concurrent programs, or integrations dependent on the original object definition.

Functionally, the view presents a denormalized, flattened perspective of purchase order distribution records. Rather than requiring a consumer to join the distribution table to line, shipment, header, release, and organization tables, the view pre-assembles these relationships and exposes descriptive attributes (such as the PO number, line number, shipment number, release number, and operating unit name) alongside the distribution-level transactional and accounting data. This makes it well suited to reporting, extracts, and integration use cases where a single, self-contained query against purchasing distributions is preferred over a multi-table join.

Underlying Base Objects

According to the documented metadata, the view is defined over the following base objects, referenced through synonyms in the APPS schema:

• PO_DISTRIBUTIONS_ALL — the driving table (aliased PD), supplying distribution-level detail.
• PO_LINE_LOCATIONS_ALL — shipment/schedule lines (aliased PS), joined for SHIPMENT_NUM.
• PO_LINES_ALL — order lines (aliased PL), joined for LINE_NUM.
• PO_HEADERS_ALL — order headers (aliased PH), joined for SEGMENT1 (the PO number) and TYPE_LOOKUP_CODE.
• PO_RELEASES_ALL — releases (aliased PR), joined for RELEASE_NUM.
• HR_ALL_ORGANIZATION_UNITS — organization units (aliased OP), joined for the operating unit NAME.

The join predicate shown is driven from the header (PH.TYPE_LO...) into the line, shipment, release, and organization hierarchy. This structure mirrors the standard Purchasing entity model and confirms the view is a convenience projection rather than an aggregation.

Key Columns

The view exposes a broad set of columns spanning purchasing, receiving, and encumbrance attributes. Notable categories include:

• Keys and identifiers: PO_DISTRIBUTION_ID, DISTRIBUTION_NUM, PO_LINE_ID, PO_HEADER_ID, LINE_LOCATION_ID, PO_RELEASE_ID, ORG_ID, CODE_COMBINATION_ID.
• Descriptive context: SEGMENT1 (PO number), LINE_NUM, SHIPMENT_NUM, RELEASE_NUM, and the operating unit NAME.
• Quantities: QUANTITY_ORDERED, QUANTITY_DELIVERED, QUANTITY_CANCELLED, QUANTITY_BILLED, UNENCUMBERED_QUANTITY.
• Amounts and rates: AMOUNT_ORDERED, AMOUNT_DELIVERED, AMOUNT_CANCELLED, AMOUNT_BILLED, RATE, RATE_DATE, ENCUMBERED_AMOUNT, UNENCUMBERED_AMOUNT.
• Accounting dates and status: GL_CANCELLED_DATE, GL_CLOSED_DATE, GL_ENCUMBERED_DATE, GL_ENCUMBERED_PERIOD_NAME, EXPENDITURE_ITEM_DATE — the GL_CANCELLED_DATE column in particular being the field users frequently search on when reconciling cancelled distributions.
• Flags and lookups: ACCRUE_ON_RECEIPT_FLAG, ACCRUED_FLAG, ENCUMBERED_FLAG, PREVENT_ENCUMBRANCE_FLAG, DESTINATION_TYPE_CODE, FAILED_FUNDS_LOOKUP_CODE, each surfaced via PO_LOOKUP_CODES.
• Project and manufacturing references: PROJECT_ID, TASK_ID, BOM_RESOURCE_ID, WIP_ENTITY_ID, and related WIP columns.

Common Use Cases and Queries

The view is commonly used for distribution-level reporting, accrual and encumbrance reconciliation, and extracts that must join purchasing data to accounting. A typical query listing open distributions for a given PO is:

• SELECT segment1, line_num, shipment_num, distribution_num, quantity_ordered, quantity_billed, amount_billed FROM apps.pobv_bkt_po_distributions WHERE segment1 = :po_number ORDER BY line_num, shipment_num, distribution_num;
• SELECT segment1, distribution_num, gl_cancelled_date, amount_ordered FROM apps.pobv_bkt_po_distributions WHERE gl_cancelled_date IS NOT NULL AND org_id = :org_id; — useful when searching on GL cancellation dates for reconciliation.
• SELECT op_name, COUNT(*) FROM (SELECT name op_name FROM apps.pobv_bkt_po_distributions) GROUP BY op_name; — illustrative of grouping by operating unit for volume analysis.

Because the view consolidates six base objects, it reduces query complexity for ad-hoc analysis and interface extracts. However, it carries no additional indexing beyond that of its underlying tables, so filters should target PO_header, org, and date columns to maintain acceptable performance in high-volume environments.