Search Results invoice_to_address_id




Overview
Explore in AI Chat

Overview

The ICX_EDM_SALES_ORDER_V view is a reporting and integration object within the ICX (Oracle iProcurement) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is "Project Related Sales Order View," indicating that it exposes sales order header and line information that has been linked to project and task identifiers. The view consolidates order-level, customer-level, address-level, and project-level attributes into a single flattened row per project-related sales order line, enabling downstream modules such as iProcurement, project accounting, and external reporting tools to retrieve project-linked order data without writing complex multi-table joins.

In the ETRM documentation set for 12.2.2, the view is noted as "Not implemented in this database," and no owner or referenced base objects are formally documented. This means the view exists as a defined object in the EBS data model but may not be deployed in every environment. Where it is present, it serves as a denormalized read-only interface that shields consumers from the underlying Oracle Order Management and Project Management schema complexity.

Underlying Base Objects

Although the ETRM metadata documents no base objects, the view text reveals its composition. The core tables are SO_HEADERS (H) and SO_LINES (L), joined on HEADER_ID, which supply order header and line detail. Project linkage is provided through PJM_PROJECTS_V (PROJ) and PA_TASKS (TASK), joined via PROJECT_ID and TASK_ID. Customer and address information is derived from RA_CUSTOMERS, RA_ADDRESSES (for both invoice-to and ship-to), and RA_SITE_USES. Order type and category decoding rely on SO_ORDER_TYPES and three aliases of SO_LOOKUPS (SOLKP1 for ORDER_CATEGORY, SOLKP2 for SHIPMENT_PRIORITY, and SOLKP3 for FREIGHT_TERMS). Payment terms come from RA_TERMS. Most joins use outer-join syntax (noted by the "+" operator) on lookup and task tables, allowing rows to survive missing decode values.

Key Columns

Common Use Cases and Queries

This view is typically used to report on sales orders tied to projects, to validate freight terms and shipping attributes on project orders, and to feed iProcurement or project accounting dashboards. Because FREIGHT_TERMS is a decoded lookup, analysts commonly filter or group by it.

Sample query retrieving project orders by freight terms:

SELECT PROJECT_NUMBER,
       ORDER_NUMBER,
       CUSTOMER_NAME,
       FREIGHT_TERMS,
       ORDER_TOTAL,
       CURRENCY_CODE
FROM   ICX_EDM_SALES_ORDER_V
WHERE  FREIGHT_TERMS = 'Prepaid & Add'
AND    CANCELLED_FLAG = 'N';

Aggregating order totals by project and shipping location:

SELECT PROJECT_NUMBER,
       SHIP_TO_LOCATION,
       SUM(ORDER_TOTAL) TOTAL_AMOUNT
FROM   ICX_EDM_SALES_ORDER_V
GROUP  BY PROJECT_NUMBER, SHIP_TO_LOCATION;

Verifying freighting and shipment priority combinations on open orders:

SELECT ORDER_NUMBER, FREIGHT_TERMS,
       SHIPMENT_PRIORITY, SHIP_METHOD_CODE
FROM   ICX_EDM_SALES_ORDER_V
WHERE  CANCELLED_FLAG = 'N'
ORDER  BY ORDER_NUMBER;

Because the view is documented as not implemented in the reference database, availability should be confirmed before reliance, and because it performs DISTINCT and outer joins over large transactional tables, query performance should be validated against production data volumes.