Search Results task_num

Overview

PO_ECX_DISTRBN_ARCH_V is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module. It is documented as being "Used for XML mapping in the distribution level," which places it within the E-Business Suite's e-commerce and integration framework (ECX), specifically supporting XML-based document exchange such as purchase order and release communications. The view projects purchasing distribution data drawn from the archived distributions table, enriching it with project, task, and requestor attributes so that distribution-level detail can be mapped into XML payloads used by the PO integration and messaging infrastructure.

The object is listed as VALID and is present in both Oracle EBS 12.1.1 and 12.2.2, with the documented ETRM metadata reflecting the 12.2.2 definition. Because it reads from an archive table rather than the live distributions table, the view is oriented toward historically retained purchasing distribution records rather than the current transactional set. This distinction is important: the view is designed for scenarios in which the distribution information has been archived, and the integration or reporting layer still requires a consistent, mapped representation of that data.

Underlying Base Objects

The view is defined over the following documented base objects:

• PO_DISTRIBUTIONS_ARCHIVE_ALL (SYNONYM) — the primary source of distribution records, providing quantity ordered, rate, destination type, distribution number, and the descriptive flexfield attribute columns.
• PA_PROJECTS_ALL (SYNONYM) — joined on PROJECT_ID to supply the project identifier and project type through the PA.PROJECT_TYPE column.
• PA_TASKS (SYNONYM) — joined on PROJECT_ID and TASK_ID to provide the task number.
• PER_ALL_PEOPLE_F (SYNONYM) — joined on DELIVER_TO_PERSON_ID to supply the requestor's full name, restricted to the currently effective person record.
• MRP_GET_PROJECT (PACKAGE) — invoked as a function, MRP_GET_PROJECT.PROJECT(PDAA.PROJECT_ID), to resolve the project number.

All joins to the project, task, and person tables are outer joins, so distribution rows without a matching project, task, or deliver-to person are retained. The person join is further constrained by NVL(PAPF.EFFECTIVE_END_DATE, SYSDATE) >= SYSDATE, ensuring only the effective-dated person row is used. The project and task joins are both conditioned on PDAA.PROJECT_ID, meaning tasks are matched within the same project context.

Key Columns

The view exposes identifiers and descriptive attributes used for XML mapping and downstream processing. Significant columns include:

• REVISION_NUM, PO_RELEASE_ID, PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOC_ID, PO_DISTRIBUTION_ID — the purchasing document hierarchy keys, from release and header down to line, line location, and distribution.
• DISTRIBUTION_NUM — the distribution number within the line location.
• QTY_ORDERED — the quantity ordered on the distribution, sourced from PDAA.QUANTITY_ORDERED. This is the column most commonly referenced when users search on "qty_ordered," since the view's physical column name differs from the base table's QUANTITY_ORDERED.
• CONVERSION_RATE (RATE) and CONV_RATE_DATE (RATE_DATE) — the currency conversion rate and its effective date.
• DESTINATION_TYPE (DESTINATION_TYPE_CODE) — the type of distribution destination.
• PROJECT_NUM, PROJECT_TYPE, TASK_NUM — project and task attribution resolved through the MRP_GET_PROJECT package and the project/task tables.
• REQUESTOR — the full name of the deliver-to person, resolved from PER_ALL_PEOPLE_F.
• DFF_DIST_ATTR1 through DFF_DIST_ATTR16 — the descriptive flexfield attribute category and attributes 1–15, remapped into sixteen sequentially named columns for XML consumption.

Common Use Cases and Queries

The view is principally used to extract archived distribution-level purchasing data for XML mapping, integration testing, and reconciliation of historical purchase order distributions. A typical query retrieving ordered quantities by distribution is:

• SELECT po_header_id, po_line_id, po_line_loc_id, distribution_num, qty_ordered, conversion_rate, project_num, task_num, requestor FROM apps.po_ecx_distrbn_arch_v WHERE po_header_id = :header_id;

Because QTY_ORDERED is the aliased name of the archived quantity, reporting that compares ordered quantities against receipts or invoices for archived documents should target this column. Project-aware reporting can filter on project_num or project_type, while integration developers can inspect the DFF_DIST_ATTR columns to confirm flexfield mapping completeness before XML generation. When the view returns no rows for a given document, the likely cause is that the corresponding distribution has not been archived, since the primary source is PO_DISTRIBUTIONS_ARCHIVE_ALL rather than the live PO_DISTRIBUTIONS_ALL table. Oracle Proprietary, Confidential Information — Legal Notices apply.