Results for “msc_apps_version”

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

Overview

APPS.MSC_APPS_INSTANCES_V is a view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It exposes instance-level configuration and registration data used by the Advanced Supply Chain Planning (ASCP) and related MSC (Manufacturing/Supply Chain) modules to identify and describe the application instances that participate in a distributed or multi-instance planning topology. The view presents information about each registered Oracle Applications instance, including its version, database connectivity details, language and territory attributes, and status indicators.

The object is classified as an internal Oracle view. Oracle documentation marks it as "Oracle Internal Use Only" and states that Oracle Corporation does not support access to applications data through this object except from standard Oracle Applications programs. The view is nevertheless registered in FND Design Data as MSC.MSC_APPS_INSTANCES_V and carries a status of VALID. The APPS_VER_TEXT column, which is the column most frequently associated with searches on this object, is an 80-character text representation of the Applications version and is commonly used to distinguish instances during multi-instance planning and data collection validation.

Underlying Base Objects

Per the documented ETRM metadata for release 12.2.2, MSC_APPS_INSTANCES_V is defined over the following base objects:

• MSC_APPS_INSTANCES (referenced through a SYNONYM) — the principal base table holding the registered application instance records. The view projects columns from this table, including instance identity, version, connectivity, and audit attributes.
• MFG_LOOKUPS (VIEW) — the standard Oracle lookup view, used to resolve coded values into their meanings. The view typically joins to lookups to translate numeric flags such as instance type, enabled flag, and status into descriptive values.

The view therefore acts as a reporting and integration layer over the base instance registry table, enriching stored code values with lookup-driven descriptive information. Because MSC_APPS_INSTANCES is referenced through a synonym, dependencies resolve through the APPS synonym rather than a hard-coded table reference, which is relevant when auditing invalidations or recompiling the view after upgrades.

Key Columns

The view exposes a broad set of columns spanning instance identity, version, connectivity, language, and standard WHO audit attributes.

• INSTANCE_CODE — a short code identifying the application instance.
• APPS_VER — the numeric Applications version identifier.
• APPS_VER_TEXT — an 80-character text rendition of the Applications version, the column most often queried when users search for "apps_ver_text."
• INSTANCE_TYPE — numeric code classifying the instance role within the planning topology.
• DBS_VER — the database version associated with the instance.
• A2M_DBLINK and M2A_DBLINK — database link names used for communication between the source and planning instances (Applications-to-MSC and MSC-to-Applications directions).
• ENABLE_FLAG — indicates whether the instance is active for processing.
• LRID, LRTYPE, APPS_LRN, LCID — language, territory, and locale related identifiers.
• INSTANCE_ID — the internal numeric identifier for the instance record.
• ST_STATUS and CLEANSED_FLAG — status and data cleansing indicators.
• GMT_DIFFERENCE — the instance's offset from GMT, used for time-zone normalization.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard Oracle descriptive flexfield columns, each 150 characters (category 30 characters).
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — standard WHO audit and concurrent program columns.
• CURRENCY — currency associated with the instance record.

Common Use Cases and Queries

The view is principally used to enumerate registered application instances, confirm the Applications version of each instance, and validate connectivity configuration before running data collection or planning processes. A typical query retrieves the instance code and version text for all enabled instances:

• SELECT instance_code, apps_ver, apps_ver_text FROM apps.msc_apps_instances_v WHERE enable_flag = 1 ORDER BY instance_code; — lists active instances and their versions.
• SELECT instance_code, apps_ver_text, dbs_ver, a2m_dblink, m2a_dblink FROM apps.msc_apps_instances_v; — reviews connectivity configuration across instances.
• SELECT instance_code, apps_ver_text, gmt_difference FROM apps.msc_apps_instances_v ORDER BY gmt_difference; — supports multi-instance time-zone analysis.

Because the object is documented as Oracle internal and unsupported for direct customer access, the recommended practice is to treat these queries as diagnostic aids for validation and troubleshooting rather than as an integration interface, and to rely on standard Oracle Applications programs for supported functionality.