Results for “invoice_adjustment_flag”

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

Overview

The PO_DISTRIBUTION_XML view is an Oracle E-Business Suite database object owned by the APPS schema and defined within the Purchasing (PO) product module. This view exposes accounting distribution data from Oracle Purchasing purchase order shipments in a format specifically optimized for XML-based communication and outbound document generation. Its name reflects its primary design intent: supplying distribution-level detail, formatted through the PO_COMMUNICATION_PVT package, to the XML messaging layer that produces purchase order documents, supplier notifications, and related business-to-business message payloads.

Unlike the transactional table PO_DISTRIBUTIONS_ALL, this view applies presentation and formatting logic — notably numeric formatting through PO_COMMUNICATION_PVT.GETFORMATMASK and date conversion via explicit TO_CHAR operations. This makes the view a reporting and integration artifact rather than a pure data access layer. The view is VALID and present in both EBS 12.1.1 and 12.2.2, providing a stable interface across these releases. Because it presents distribution rows with monetary amounts rendered as formatted character strings, consumers of the view receive data already shaped for embedding into XML documents, reducing transformation effort in downstream communication programs.

Underlying Base Objects

The view is defined over the synonym PO_DISTRIBUTIONS_ALL, which resolves to the PO_DISTRIBUTIONS_ALL base table. Each row in PO_DISTRIBUTIONS_ALL corresponds to an accounting distribution of a purchase order shipment, and the view inherits that granularity unchanged. The documented referenced base objects also include GL_CODE_COMBINATIONS_KFV, the key flexfield view that exposes concatenated accounting code combinations; HR_LOOKUPS, which provides lookup code meanings; PER_ALL_PEOPLE_F, the person view used to resolve employee references; and the PO_COMMUNICATION_GT and PO_COMMUNICATION_PVT package objects, the latter supplying the GETFORMATMASK function applied to monetary columns. The HR_API package is likewise referenced, consistent with communication processing logic. Importantly, while these objects are documented as referenced dependencies, the view's own SELECT statement operates directly against PO_DISTRIBUTIONS_ALL and the PO_COMMUNICATION_PVT formatting function, while the additional referenced objects support the broader communication framework in which the view participates.

Key Columns

The view exposes a wide set of distribution attributes. Key columns include:

• PO_DISTRIBUTION_ID, PO_HEADER_ID, PO_LINE_ID, and LINE_LOCATION_ID — the identifiers linking the distribution to its header, line, and shipment.
• AMOUNT_ORDERED, AMOUNT_DELIVERED, AMOUNT_CANCELLED, and AMOUNT_TO_ENCUMBER — monetary values rendered as formatted character strings via PO_COMMUNICATION_PVT.GETFORMATMASK.
• DISTRIBUTION_TYPE and DESTINATION_TYPE_CODE — classify the distribution and its destination behavior.
• CODE_COMBINATION_ID, BUDGET_ACCOUNT_ID, ACCRUAL_ACCOUNT_ID, and VARIANCE_ACCOUNT_ID — accounting flexfield references.
• PROJECT_ID, TASK_ID, EXPENDITURE_TYPE, EXPENDITURE_ITEM_DATE, and EXPENDITURE_ORGANIZATION_ID — project and expenditure accounting context.
• WIP_ENTITY_ID, WIP_OPERATION_SEQ_NUM, WIP_RESOURCE_SEQ_NUM, WIP_REPETITIVE_SCHEDULE_ID, WIP_LINE_ID, and BOM_RESOURCE_ID — work-in-process and bill-of-material references.
• Dates such as LAST_UPDATE_DATE, CREATION_DATE, GL_CLOSED_DATE, GL_CANCELLED_DATE, and EXPENDITURE_ITEM_DATE, each converted to 'DD-MON-YYYY HH24:MI:SS' character format.
• Desk-flex columns ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 for extensibility.
• ORG_ID, SET_OF_BOOKS_ID, USSGL_TRANSACTION_CODE, GOVERNMENT_CONTEXT, and the encumbrance-related flags.

Common Use Cases and Queries

The view is most frequently used to diagnose or reproduce distribution data as it appears in purchase order XML output, and to reconcile communication payloads against source distributions. A typical query retrieves formatted amounts for a given purchase order:

• SELECT po_distribution_id, po_header_id, amount_ordered, amount_delivered, amount_to_encumber FROM po_distribution_xml WHERE po_header_id = :p_header_id;
• SELECT po_distribution_id, code_combination_id, amount_ordered, last_update_date FROM po_distribution_xml WHERE org_id = :p_org_id AND destination_type_code = 'INVENTORY';
• SELECT po_distribution_id, project_id, task_id, expenditure_type, amount_ordered FROM po_distribution_xml WHERE project_id IS NOT NULL;

Because amounts are returned as formatted strings, these queries are suited to display, reporting, and payload comparison rather than arithmetic aggregation; numeric computations should reference PO_DISTRIBUTIONS_ALL directly. The view remains a valuable reference for developers building or troubleshooting PO XML communication, and for analysts comparing formatted output against stored distribution values.