Results for “system_flag”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The view MSD_CS_CLMN_IDENTIFIERS_VL is an Oracle E-Business Suite database object owned by the APPS schema and defined within the MSD – Demand Planning product family. Its documented purpose is to expose Custom Stream Column identifiers, providing a language-aware, fully translated representation of the identifier definitions used by the Demand Planning custom stream framework. The "_VL" suffix indicates that the view joins a base entity table with its translation table and applies the session language, so that descriptive text returned to the user appears in the correct linguistic context.
In the context of Oracle EBS 12.1.1 and 12.2.2, this view functions as a reporting and integration access point rather than as a transaction-processing object. It consolidates identifier metadata — column identifiers, descriptions, prompts, and system flags — with the meaning derived from the lookup type MSD_CS_IDENTIFIERS. Because the view is documented as VALID in the ETRM repository, it can be relied upon by concurrent programs, BI Publisher data templates, and custom SQL reports that need to enumerate the identifiers available to a custom stream configuration without querying the underlying tables directly.
Underlying Base Objects
The view text documented in the ETRM metadata is built from three referenced objects: FND_LOOKUP_VALUES_VL (a view), and the synonyms MSD_CS_CLMN_IDENTIFIERS and MSD_CS_CLMN_IDENTIFIERS_TL. These synonyms resolve to the base identifier and identifier-translation tables in the APPS schema.
The join logic is straightforward. The base table MSD_CS_CLMN_IDENTIFIERS supplies the stored identifier attributes, while MSD_CS_CLMN_IDENTIFIERS_TL supplies the translatable description and user prompt. The two are joined on COLUMN_IDENTIFIER, and the translation row is restricted by LANGUAGE = USERENV('LANG'), which returns only the row matching the current session language. The lookup view FND_LOOKUP_VALUES_VL is outer-joined by matching LOOKUP_TYPE = 'MSD_CS_IDENTIFIERS' and LOOKUP_CODE = IDEN.IDENTIFIER_TYPE, which resolves the stored identifier type code into a user-facing meaning. This lookup dependency means that changes to the MSD_CS_IDENTIFIERS lookup values are reflected automatically in the view output.
Key Columns
The view exposes the following documented columns:
- COLUMN_IDENTIFIER — The unique key for the custom stream column identifier; also the join key between the base and translation tables.
- DESCRIPTION — The translated descriptive text for the identifier, sourced from the TL table.
- IDENTIFIER_TYPE — The code classifying the identifier; participates in the lookup join.
- IDENTIFIER_TYPE_DESC — The resolved meaning of the identifier type, drawn from
FND_LOOKUP_VALUES_VL. - USER_PROMPT — The translatable prompt presented to the user when the identifier is selected.
- SYSTEM_FLAG — Indicates whether the identifier is seeded by the application (system-defined) or user-defined.
- CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified the row.
The IDENTIFIER_TYPE column is particularly relevant to the "identifier_type" search term, as it is the attribute that links each identifier to its classification and to the corresponding lookup meaning.
Common Use Cases and Queries
Typical uses include validating identifier configurations prior to custom stream setup, generating reference listings for demand planning administrators, and driving parameter lists (LOVs) in custom concurrent programs. The following query lists all identifiers with their translated type and prompt, ordering system-defined entries first:
SELECT column_identifier, identifier_type, identifier_type_desc, description, user_prompt, system_flag FROM apps.msd_cs_clmn_identifiers_vl ORDER BY system_flag, column_identifier;
To isolate user-defined identifiers:
SELECT column_identifier, description, user_prompt FROM apps.msd_cs_clmn_identifiers_vl WHERE system_flag = 'N';
To filter by a specific identifier type:
SELECT column_identifier, identifier_type_desc, description FROM apps.msd_cs_clmn_identifiers_vl WHERE identifier_type = :p_type;
Because the view already resolves the language via USERENV('LANG'), no additional language predicate is required in reporting queries. Callers should be aware that rows whose identifier type has no matching lookup value will return a null IDENTIFIER_TYPE_DESC, since the lookup is applied as an outer join.
-
This view for Custom Stream Column identifiers
APPS.MSD_CS_CLMN_IDENTIFIERS_VL·↳ FND_LOOKUP_VALUES_VL·↳ MSD_CS_CLMN_IDENTIFIERS·↳ MSD_CS_CLMN_IDENTIFIERS_TL·Explore MSD module →
-
This view for Custom Stream Column identifiers
APPS.MSD_CS_CLMN_IDENTIFIERS_VL·↳ FND_LOOKUP_VALUES_VL·↳ MSD_CS_CLMN_IDENTIFIERS·↳ MSD_CS_CLMN_IDENTIFIERS_TL·Explore MSD module →
-
Table: PON_FIELDS 12.1.1
Stores information about a field.
-
OZF_SD_STATUS_TRANSITIONS stores the status transition information for a Ship & Debit request.
-
Stores price element type details
-
This table has Column identifiers for Custom Data Stream.
-
Table: PON_FIELDS 12.2.2
Stores information about a field.
-
OZF_SD_STATUS_TRANSITIONS stores the status transition information for a Ship & Debit request.
-
Table: PON_FORMS_SECTIONS 12.1.1
Store the header details for a form, section or abstract.
-
Stores attribute set information for RX reports (base MLS table)
-
Stores attribute set information for RX reports (base MLS table)
-
View: BIS_TARGET_LEVELS_VL 12.1.1
APPS.BIS_TARGET_LEVELS_VL·↳ BIS_TARGET_LEVELS·↳ BIS_TARGET_LEVELS_TL·Explore BIS module →
-
View to access price element type name and description in the session language.
APPS.PON_PRICE_ELEMENT_TYPES_VL·↳ PON_PRICE_ELEMENT_TYPES·↳ PON_PRICE_ELEMENT_TYPES_TL·Explore PON module →
-
This table has Column identifiers for Custom Data Stream.
-
This table stores defaulting conditions for an entity
-
This table store the constraint record sets and the constraint conditions can be built to validate against any or all the records in this record set.
-
View to access negotiation style name and description in the session language.
APPS.PON_NEGOTIATION_STYLES_VL·↳ PON_NEGOTIATION_STYLES·↳ PON_NEGOTIATION_STYLES_TL·Explore PON module →
-
This table stores the responsibilities that are constrained by the constraint identified by constraint_id.
-
View: FA_RX_ATTRSETS_VL 12.1.1
Stores attribute set information for RX reports (translated MLS view)
APPS.FA_RX_ATTRSETS_VL·↳ FA_RX_ATTRSETS_B·↳ FA_RX_ATTRSETS_TL·Explore OFA module →
-
This table stores elements (columns and column values) that makeup the defaulting condition identified by condition_id.
-
Stores price element type details
-
Associates the defaulting condtion, defined at the entity level , to a specific attribute.
-
This table stores negotiation style related information.
-
View: BISBV_TARGET_LEVELS 12.1.1
APPS.BISBV_TARGET_LEVELS·↳ BIS_TARGET_LEVELS·↳ BIS_TARGET_LEVELS_TL·Explore BIS module →
-
This table store the constraint record sets and the constraint conditions can be built to validate against any or all the records in this record set.
-
MSC_BIS_TARGET_LEVELS contains different combinations of dimension levels to be applied simultaneously to get a performance indicator relevant to a particular reporting need. For example, if someone wants to know sales revenues broken down
-
View: OE_DEF_CONDITIONS_VL 12.1.1
This view stores the defaulting conditions.
APPS.OE_DEF_CONDITIONS_VL·↳ AK_OBJECTS_VL·↳ OE_AK_OBJECTS_EXT·↳ OE_DEF_CONDITIONS·Explore ONT module →
-
This table stores elements (columns and column values) that makeup the defaulting condition identified by condition_id.
-
View: OE_PC_RSETS_VL 12.2.2
APPS.OE_PC_RSETS_VL·↳ OE_PC_RSETS·↳ OE_PC_RSETS_TL·Explore ONT module →
-
View: PON_COST_FACTORS_VL 12.1.1
View to show details of the cost factors/price elements in the session language. This view is similar to pon_price_element_types_vl except that its WHERE clause excludes the price element with id -10 corresponding to the item price. Item
APPS.PON_COST_FACTORS_VL·↳ PON_PRICE_ELEMENT_TYPES·↳ PON_PRICE_ELEMENT_TYPES_TL·Explore PON module →
-
View: PON_COST_FACTORS_VL 12.2.2
View to show details of the cost factors/price elements in the session language. This view is similar to pon_price_element_types_vl except that its WHERE clause excludes the price element with id -10 corresponding to the item price. Item
APPS.PON_COST_FACTORS_VL·↳ PON_PRICE_ELEMENT_TYPES·↳ PON_PRICE_ELEMENT_TYPES_TL·Explore PON module →
-
View to access price element type name and description in the session language.
APPS.PON_PRICE_ELEMENT_TYPES_VL·↳ PON_PRICE_ELEMENT_TYPES·↳ PON_PRICE_ELEMENT_TYPES_TL·Explore PON module →
-
View: OE_DEF_CONDN_ELEMS_V 12.1.1
This view stores the elements of the defaulting conditions.
APPS.OE_DEF_CONDN_ELEMS_V·↳ AK_OBJECT_ATTRIBUTES_VL·↳ OE_DEF_CONDITIONS·↳ OE_DEF_CONDN_ELEMS·Explore ONT module →
-
BIS_TARGET_LEVELS contains different combinations of dimension levels to be applied simultaneously to get a performance indicator relevant to a particular reporting need. For example, if someone wants ot know sales revenues broken d
-
MSC_BIS_TARGET_LEVELS contains different combinations of dimension levels to be applied simultaneously to get a performance indicator relevant to a particular reporting need. For example, if someone wants to know sales revenues broken down
-
View: OE_DEF_CONDITIONS_VL 12.2.2
This view stores the defaulting conditions.
APPS.OE_DEF_CONDITIONS_VL·↳ AK_OBJECTS_VL·↳ OE_AK_OBJECTS_EXT·↳ OE_DEF_CONDITIONS·Explore ONT module →
-
View: FA_RX_ATTRSETS_VL 12.2.2
Stores attribute set information for RX reports (translated MLS view)
APPS.FA_RX_ATTRSETS_VL·↳ FA_RX_ATTRSETS_B·↳ FA_RX_ATTRSETS_TL·Explore OFA module →
-
This table stores the constraints that prevent create/update/delete of order entities.
-
Order security rules
-
The staging table used by the collection program to validate and process data for table MSC_BIS_TARGET_LEVELS
-
View: OE_PC_CONSTRAINTS_V 12.1.1
This view stores the processing constraints.
APPS.OE_PC_CONSTRAINTS_V·↳ OE_PC_ATTRIBUTES_V·↳ OE_PC_CONSTRAINTS·Explore ONT module →
-
This table stores the constraint validation templates that are used in constraint conditions.
-
Table: PON_FORMS_SECTIONS 12.2.2
Store the header details for a form, section or abstract.
-
View: OE_PC_RSETS_V 12.1.1
This view stores the processing constraints record sets.
APPS.OE_PC_RSETS_V·↳ OE_PC_ENTITIES_V·↳ OE_PC_RSETS·↳ OE_PC_RSETS_TL·Explore ONT module →
-
This table stores the conditions associated with the constraints identified by constraint_id.
-
View: OE_PC_VTMPLTS_VL 12.2.2
APPS.OE_PC_VTMPLTS_VL·↳ OE_PC_VTMPLTS·↳ OE_PC_VTMPLTS_TL·Explore ONT module →
-
View: OE_PC_CONDITIONS_VL 12.2.2
APPS.OE_PC_CONDITIONS_VL·↳ OE_PC_CONDITIONS·↳ OE_PC_CONDITIONS_TL·Explore ONT module →
-
Predefined list of valid period types for payroll and HR budget calendars.
-
View: OE_DEF_CONDN_ELEMS_V 12.2.2
This view stores the elements of the defaulting conditions.
APPS.OE_DEF_CONDN_ELEMS_V·↳ AK_OBJECT_ATTRIBUTES_VL·↳ OE_DEF_CONDITIONS·↳ OE_DEF_CONDN_ELEMS·Explore ONT module →