Search Results create_customer_flag

Overview

APPS.ASO_I_ORDER_SOURCES_V is a view in the Oracle E-Business Suite Order Management (ASO) schema, registered under the FND Design Data identifier ASO.ASO_I_ORDER_SOURCES_V. Its status is documented as VALID, and it is owned by the APPS schema. The view exposes configuration data about order import sources — the feeder systems from which sales orders and related transactions are loaded into Oracle Order Management through the Order Import process. It presents each source as a single row containing an identifier, a display name, a description, an enabled flag, and two behavioral control flags.

From a functional standpoint, the object serves reporting and integration validation needs: it allows administrators and technical consultants to enumerate which import sources are active, what each represents, and how transactions from that source should be interpreted during import. The ETRM documentation explicitly designates this object as Oracle Internal Use Only, meaning Oracle Corporation does not support direct access to application data through it except from standard Oracle Applications programs. Consequently, custom code referencing this view should be treated as unsupported, and it is preferable to call the underlying base object or a supported API where one exists.

Underlying Base Objects

According to the documented dependency information, ASO_I_ORDER_SOURCES_V references a single base object: APPS.OE_ORDER_SOURCES, exposed through a synonym. There is no indication that the view performs joins across multiple tables, aggregates rows, or applies complex filtering logic. The view is not referenced by any other database object, confirming that it functions as a leaf-level read interface rather than a component of a larger dependency chain.

The view is therefore best understood as a projection layer over OE_ORDER_SOURCES, selecting and exposing a subset of attributes from that table. Because the view is internal, its column list and semantics may change between patch levels; any dependence on it carries upgrade risk across 12.1.1 and 12.2.2.

Key Columns

• ORDER_SOURCE_ID (NUMBER) — The unique identifier for the order source. This is the primary key value used internally to associate imported transactions with their originating feeder system.
• NAME (VARCHAR2, 240) — The name of the foreign feeder source, serving as the human-readable label presented in Order Import setup and related forms.
• DESCRIPTION (VARCHAR2, 2000) — A free-text description of the feeder source, typically explaining the origin system or the business purpose of the source.
• ENABLED_FLAG (VARCHAR2) — Identifies whether an import source is active. Values follow standard Oracle EBS conventions (typically Y/N or similar), allowing disabled sources to be retained while excluded from active processing.
• CREATE_CUSTOMER_FLAG (VARCHAR2) — Documented in the metadata as Not supported. This is the column that users most commonly interrogate when searching for create_customer_flag. Because ETRM classifies it as unsupported, it should not be relied upon for custom development; consult the Order Import configuration forms or supported APIs instead.
• USE_IDS_FLAG (VARCHAR2) — Identifies whether the import file will contain both names and IDs for transactions in this source. This flag governs how Order Import resolves references when loading data.

Common Use Cases and Queries

Typical usage centers on inventorying configured sources and verifying import behavior settings. A basic query returns all configured sources:

SELECT ORDER_SOURCE_ID, NAME, DESCRIPTION, ENABLED_FLAG, CREATE_CUSTOMER_FLAG, USE_IDS_FLAG FROM APPS.ASO_I_ORDER_SOURCES_V;

To restrict results to active sources only, a filter on ENABLED_FLAG is applied. To determine which sources expect both names and IDs in their import files, users filter on USE_IDS_FLAG. Reports that document feeder system configuration often join ORDER_SOURCE_ID to imported transaction staging tables to attribute loaded orders to their origin.

Given the internal-use restriction, any query against this view should be validated against the base OE_ORDER_SOURCES table and confirmed as supported for the target release before being embedded in production code. Where possible, obtain source configuration through standard Order Management setup screens or supported PL/SQL APIs rather than direct SQL on this view.