Search Results dff_dist_attr1




Overview
Explore in AI Chat

Overview

ITG_PO_DISTRBN_ARCH_V is an APPS-owned database view within the ITG - Internet Procurement Enterprise Connector product. Its documented purpose is to support XML mapping at the distribution level, feeding purchasing distribution data into the Internet Procurement connector messaging and integration flows. In this capacity, the view acts as a flattened, presentation-oriented projection of archived purchase order distribution records, joined to project, task, and requestor information so that a single row carries every distribution-level attribute required by an outbound XML document.

The view is defined over PO_DISTRIBUTIONS_ARCHIVE_ALL, meaning it exposes the historical/archived population of PO distributions rather than the live transactional tables. This distinction matters in both Oracle EBS 12.1.1 and 12.2.2, where archival purges move completed purchasing documents out of the active PO_DISTRIBUTIONS_ALL table. The view therefore serves as a stable reporting and integration surface for distributions that would otherwise no longer be accessible through the operational PO tables. It is a read-only object and is not a table, so no DML should be directed against it.

Underlying Base Objects

The documented base objects referenced by the view are:

  • PO_DISTRIBUTIONS_ARCHIVE_ALL (synonym) - the primary driving table, supplying distribution-level columns such as quantity ordered, rate, rate date, destination type code, revision number, and the DFF attribute segments.
  • PA_PROJECTS_ALL (synonym) - outer-joined on PROJECT_ID to return the project and its project type.
  • PA_TASKS (synonym) - outer-joined on PROJECT_ID and TASK_ID to return the task number.
  • PER_ALL_PEOPLE_F (synonym) - outer-joined on DELIVER_TO_PERSON_ID to return requestor name, e-mail address, and work telephone.
  • PER_PHONES (synonym) - referenced in the object dependency list, supporting telephone data used by the requestor columns.
  • MRP_GET_PROJECT (package) - invoked as MRP_GET_PROJECT.PROJECT(PROJECT_ID) to resolve the project number.

All joins to the project, task, and person objects are outer joins (denoted by the (+) operator), and the person join is further restricted by effective date so that only currently effective person records are returned. The PROJECT_NUM column is produced by a PL/SQL function call rather than a direct column reference, which means that column cannot be indexed or filtered efficiently and should be treated as a derived attribute.

Key Columns

Because the user searched on "qty_ordered," the most relevant column is QTY_ORDERED, which maps directly to PO_DISTRIBUTIONS_ARCHIVE_ALL.QUANTITY_ORDERED and represents the quantity ordered against a specific distribution. Other significant columns include:

Common Use Cases and Queries

Typical usage includes XML mapping for the Internet Procurement connector, reconciliation of archived purchasing activity, and ad hoc reporting on historical distributions. A representative query retrieving ordered quantities by header and distribution is:

SELECT po_header_id, po_line_id, po_line_loc_id, distribution_num, qty_ordered, conversion_rate, destination_type, requestor FROM apps.itg_po_distrbn_arch_v WHERE po_header_id = :header_id ORDER BY po_line_id, distribution_num;

For project-related analysis, the project and task columns can be aggregated as follows:

SELECT project_num, task_num, SUM(qty_ordered) total_qty FROM apps.itg_po_distrbn_arch_v WHERE project_num IS NOT NULL GROUP BY project_num, task_num;

When joining to live PO tables, use PO_DISTRIBUTION_ID as the linkage key, and remember that PO_RELEASE_ID of -9999 indicates a null release. Because the view is built on archive tables, results reflect archived documents only; live distributions remain in PO_DISTRIBUTIONS_ALL.