Results for “destination_type_code_int”

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

Overview

The APPS.ECE_PO_PROJECT_INFO_V view is a reporting and integration object owned by the APPS schema within the e-Commerce Gateway (EC) product module. It exposes project-level distribution data associated with the Purchase Order (850/ORDERS) and Purchase Order Change (860/ORDCHG) outbound transactions. In the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, this view supplies the project accounting attributes that must accompany a purchase order or change order when it is transmitted to a trading partner through the e-Commerce Gateway. Because the view is a read-only construct, it is used exclusively for querying and extraction rather than for transactional DML.

The view resolves the project, task, and distribution identifiers attached to a PO distribution and enriches them with descriptive project and task information. This allows the gateway publishing programs and any downstream reporting to present human-readable project numbers and task numbers alongside the raw surrogate keys. The object carries a VALID status in the ETRM dictionary, confirming it is compiled and available in the documented releases.

Underlying Base Objects

The view is defined over the following documented base objects:

• PO_DISTRIBUTIONS (synonym) — the driving table, providing PO header, release, line, line location, distribution, project, and task identifiers together with the quantity, amount, and attribute columns.
• PA_PROJECTS_EXPEND_V (view) — supplies PROJECT_NUMBER and PROJECT_TYPE.
• PA_TASKS (synonym) — supplies TASK_NUMBER.
• PA_PROJECT_UTILS, PA_CROSS_BUSINESS_GRP, and FND_PROFILE — packaged APIs referenced in the view's dependency chain, typically for project security and business group resolution.

The joins are outer joins: POD.TASK_ID = PAT.TASK_ID (+) and POD.PROJECT_ID = PAT.PROJECT_ID (+) link tasks, while POD.PROJECT_ID = PPE.PROJECT_ID (+) links the project descriptive view. This ensures that distributions without a valid project or task still return a row, with descriptive columns nulled.

Key Columns

The view exposes a combination of identifier, quantity, and descriptive columns:

• PO_HEADER_ID, PO_RELEASE_ID, PO_LINE_ID, LINE_LOCATION_ID, PO_DISTRIBUTION_ID — the PO document hierarchy keys; PO_RELEASE_ID is NVL'd to 0.
• PROJECT_ID, TASK_ID, DISTRIBUTION_NUM — the project/task keys and distribution sequence.
• PROJECT_NUMBER, PROJECT_TYPE, TASK_NUMBER — descriptive values sourced from the PA views and tables.
• QUANTITY_ORDERED, QUANTITY_DELIVERED, QUANTITY_BILLED, QUANTITY_CANCELLED — the quantity metrics at distribution level. QUANTITY_BILLED reflects the quantity against which the distribution has been billed and is the column users most frequently search on.
• AMOUNT_BILLED, CONVERSION_RATE, CONVERSION_DATE — billing amount and currency conversion metadata.
• DESTINATION_TYPE_CODE_INT and DISTRIBUTION_ATTRIB_CATEGORY, DISTRIBUTION_ATTRIBUTE1..15 — the destination type and the DFF attribute segments.

Common Use Cases and Queries

Typical scenarios include reconciling billed quantities against ordered quantities, extracting project-coded PO distributions for gateway transmission, and auditing distributions with outstanding billing balances. For example, to find over- or partially-billed distributions:

• SELECT po_header_id, po_line_id, distribution_num, project_number, task_number, quantity_ordered, quantity_billed, amount_billed FROM apps.ece_po_project_info_v WHERE quantity_billed > 0 AND quantity_billed < quantity_ordered ORDER BY po_header_id, po_line_id;
• SELECT project_number, project_type, SUM(quantity_ordered) ordered_qty, SUM(quantity_billed) billed_qty FROM apps.ece_po_project_info_v GROUP BY project_number, project_type;
• Gateway extraction: SELECT * FROM apps.ece_po_project_info_v WHERE po_header_id = :p_po_header_id; to supply the project segment of the outbound 850/860 message.

Because the view is outer-joined, filters on PROJECT_NUMBER or TASK_NUMBER will implicitly restrict results, so users requiring all distributions should query the identifier columns instead.