Results for “summary_flag”

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

Overview

ICX_MTL_SALES_ORDERS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is registered under the ICX product, Oracle iProcurement, and the ETRM repository classifies its status as obsolete. The view presents a denormalized projection of the MTL_SALES_ORDERS table, exposing the sales order identifier alongside descriptive flexfield segments, audit columns, and standard WHO/concurrent program tracking columns.

The view was historically used by iProcurement components that needed to display or reference sales order information maintained in the inventory module. Because the underlying MTL_SALES_ORDERS table stores sales orders in a key flexfield-style layout with SEGMENT1 through SEGMENT20 defining the concatenated order key, the view simplifies access by surfacing those segments individually. In current releases, this object is retained for backward compatibility only. It should not be used for new development or integrations.

Underlying Base Objects

The view is defined exclusively over a single base object: MTL_SALES_ORDERS, referenced through a synonym. There is no join, union, or aggregation in the documented view text. The definition is a straightforward column projection from the base table with no WHERE clause, filtering, or transformation logic. Consequently, the row count, uniqueness, and data quality of ICX_MTL_SALES_ORDERS_V are identical to those of the physical table it queries.

MTL_SALES_ORDERS is the inventory table that defines sales order identifiers used when material is issued against a customer order. Key flexfield configuration for this table determines which of the SEGMENT1 through SEGMENT20 columns are enabled and how they concatenate into the displayable sales order number. Because the view carries no predicate, consumers must apply their own filters for ENABLED_FLAG, SUMMARY_FLAG, or the active date range to obtain meaningful results.

Key Columns

• SALES_ORDER_ID — The primary identifier for the sales order. This is the column most frequently referenced in searches and is the join key to transactional tables such as MTL_SALES_ORDERS and related inventory transactions.
• SEGMENT1 through SEGMENT20 — Key flexfield segments that collectively represent the sales order number. Only the enabled segments per the flexfield definition contain meaningful values.
• SUMMARY_FLAG — Indicates whether the row is a summary (parent) record rather than a detail order; typical values are Y and N.
• ENABLED_FLAG — Indicates whether the sales order is currently enabled for use.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective date range controlling when the sales order key is valid.
• SOURCE_CODE / ORDER_TYPE — Descriptive attributes identifying the origin and classification of the sales order.
• Audit and program columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE provide WHO-column auditing and concurrent program traceability.

Common Use Cases and Queries

The primary historic use case was resolving a SALES_ORDER_ID into its human-readable flexfield segments for display in iProcurement pages and reports. Typical queries filter on the active and enabled flags and limit the segment set to the configured flexfield. A representative query is:

• SELECT sales_order_id, segment1, segment2, segment3 FROM apps.icx_mtl_sales_orders_v WHERE enabled_flag = 'Y' AND NVL(summary_flag,'N') = 'N' AND SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);
• SELECT sales_order_id, order_type, source_code, creation_date FROM apps.icx_mtl_sales_orders_v WHERE sales_order_id = :p_sales_order_id;

Because the ETRM metadata marks this view obsolete, integration and reporting developers should query MTL_SALES_ORDERS directly or use the currently supported Oracle Order Management views and APIs. Existing customizations that still reference ICX_MTL_SALES_ORDERS_V should be inventoried and migrated, since the object is retained only for compatibility and may be removed in a future release.