Results for “req_distribution_id”

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

Overview

PO_DISTRIBUTIONS_V is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module. In the ETRM metadata for release 12.2.2 the object is flagged with the description "10SC ONLY", indicating that its use is restricted to a specific localization or operating scope rather than being a general-purpose, cross-module reporting entity. The view presents a denormalized projection of purchase order distribution records, combining distribution-level accounting, accrual, encumbrance, receiving, and destination attributes with selected requisition reference information. Because it exposes ROWID along with the primary distribution identifier, it behaves in the manner of an updatable-style view over the distribution base tables, but it is intended primarily for query and reporting access. The view is useful wherever a single flattened row per PO distribution is required, for example in encumbrance reconciliation, accrual analysis, project and expenditure linkage, and destination-based sourcing reporting.

Underlying Base Objects

The documented referenced base objects are HR_ALL_ORGANIZATION_UNITS_TL, PO_DISTRIBUTIONS, PO_DISTRIBUTIONS_ALL, PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL, and PO_REQ_DISTRIBUTIONS_ALL, all accessed through APPS synonyms. The principal source is POD1, which supplies the distribution columns such as PO_DISTRIBUTION_ID, REQ_DISTRIBUTION_ID, AMOUNT_BILLED, ENCUMBERED_AMOUNT, and the accounting flexfield reference CODE_COMBINATION_ID. Requisition context is joined from PO_REQUISITION_HEADERS_ALL (PORH) and PO_REQUISITION_LINES_ALL (PORL) to derive the requisition number and line number when a requisition distribution is present. HR_ALL_ORGANIZATION_UNITS_TL supports organizational descriptions for the destination or expenditure organization. The relationships follow the PO distribution hierarchy: header to line to distribution, with the optional requisition distribution link closing the loop back to the originating requisition.

Key Columns

• PO_DISTRIBUTION_ID, PO_HEADER_ID, PO_LINE_ID, PO_RELEASE_ID — primary distribution identity and its parent document keys.
• REQ_DISTRIBUTION_ID, REQ_HEADER_REFERENCE_NUM, REQ_LINE_REFERENCE_NUM — requisition linkage, resolved via DECODE against PORH.SEGMENT1 and PORL.LINE_NUM.
• CODE_COMBINATION_ID, SET_OF_BOOKS_ID — accounting flexfield and ledger context for the charge account.
• QUANTITY_ORDERED, QUANTITY_DELIVERED, QUANTITY_BILLED, QUANTITY_CANCELLED, UNENCUMBERED_QUANTITY — quantity lifecycle metrics.
• AMOUNT_BILLED, ENCUMBERED_AMOUNT, UNENCUMBERED_AMOUNT, ACCRUED_FLAG, ENCUMBERED_FLAG, ACCRUE_ON_RECEIPT_FLAG — monetary and accrual/encumbrance state.
• DESTINATION_TYPE_CODE, DESTINATION_ORGANIZATION_ID, DESTINATION_SUBINVENTORY, DELIVER_TO_LOCATION_ID, DELIVER_TO_PERSON_ID — destination and delivery attributes.
• PROJECT_ID, TASK_ID, EXPENDITURE_TYPE, EXPENDITURE_ITEM_DATE, EXPENDITURE_ORGANIZATION_ID — project accounting context.
• GL_ENCUMBERED_DATE, GL_CANCELLED_DATE, GL_CLOSED_DATE, GL_ENCUMBERED_PERIOD_NAME — period and GL closing information.
• ATTRIBUTE1 through ATTRIBUTE15, ATTRIBUTE_CATEGORY — descriptive flexfield values.

Note the DECODE expressions that derive a requisition-present indicator and substitute REQ_HEADER_REFERENCE_NUM or PORH.SEGMENT1 depending on whether REQ_DISTRIBUTION_ID is null, and the NVL wrapping on QUANTITY_DELIVERED and QUANTITY_BILLED to default these to zero. The searched column name "source_distribution_id" is not exposed by this view; the closest distribution identity columns are PO_DISTRIBUTION_ID and REQ_DISTRIBUTION_ID.

Common Use Cases and Queries

Typical scenarios include reconciling encumbered versus billed amounts on a purchase order, tracing distributions back to their originating requisition, and reporting delivery destinations by organization or subinventory. A representative query retrieving distribution counts per requisition follows:

• SELECT po_header_id, po_line_id, req_distribution_id, SUM(amount_billed) FROM apps.po_distributions_v GROUP BY po_header_id, po_line_id, req_distribution_id;
• SELECT po_distribution_id, po_header_id, code_combination_id, encumbered_amount, amount_billed FROM apps.po_distributions_v WHERE set_of_books_id = :ledger_id;
• SELECT req_header_reference_num, req_line_reference_num, destination_organization_id FROM apps.po_distributions_v WHERE req_distribution_id IS NOT NULL;

Given the restrictive "10SC ONLY" designation, consumers should confirm applicability to their operating unit and release before embedding this view in custom reporting or interfaces.