Results for “msc_apps_instances_v”

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

Overview

MSC_APPS_INSTANCES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Advanced Supply Chain Planning (MSC) product family. It exposes configuration and connectivity metadata for each registered EBS application instance participating in a distributed or multi-tier planning deployment. In such deployments, a central source instance communicates with one or more destination instances (for example, a planning server and a transactional source), and each pair of instances requires dedicated database links for bidirectional data exchange. The view provides administrators and integration developers with a consolidated, human-readable catalog of those instances, including the database link names used for source-to-planning (A2M) and planning-to-source (M2A) traffic.

Because it joins the underlying instance table to the MFG_LOOKUPS lookup view, MSC_APPS_INSTANCES_V also resolves the internal applications version code into a descriptive text value. This makes it suitable for direct use in reports, diagnostic queries, and integration validation logic without requiring the caller to perform the lookup join manually. The object status is documented as VALID in ETRM 12.2.2, and the same definition is applicable to 12.1.1 environments.

Underlying Base Objects

According to the documented ETRM metadata, the view is defined over two referenced base objects:

• MSC_APPS_INSTANCES (exposed to the APPS schema as a SYNONYM) — the primary table holding one row per registered application instance, including connection, version, and audit attributes.
• MFG_LOOKUPS (VIEW) — the standard Oracle Manufacturing lookup view, used here to translate the stored APPS_VER code into a meaning.

The view definition joins these objects with an equijoin on lookup type MSC_APPS_VERSION and lookup code equal to the instance's APPS_VER value. All columns from MSC_APPS_INSTANCES are projected through the view, with the addition of the lookup MEANING column, which appears in the view's column list as APPS_VER_TEXT. Because the lookup join is an inner join, an instance whose APPS_VER does not resolve to a defined lookup code will not be returned by the view.

Key Columns

• INSTANCE_CODE / INSTANCE_ID — identifying code and surrogate key for the registered instance.
• APPS_VER / APPS_VER_TEXT — the applications version code and its resolved description from the MSC_APPS_VERSION lookup.
• A2M_DBLINK — the database link used for Advancing-to-Manufacturing (source to planning) data movement, directly relevant to searches involving "a2m_dblink".
• M2A_DBLINK — the reciprocal database link for Manufacturing-to-Advancing traffic.
• INSTANCE_TYPE / DBS_VER — the instance role and its database version.
• ENABLE_FLAG / ST_STATUS / CLEANSED_FLAG — status and enablement indicators used to determine whether the instance is active for planning exchange.
• APPS_LRN / LRID / LRTYPE / LCID — logical replication and localization identifiers supporting distributed data synchronization.
• GMT_DIFFERENCE / CURRENCY — time-zone offset and currency context for the instance.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_ID, and the ATTRIBUTE1–15 descriptive flexfield columns.

Common Use Cases and Queries

The most frequent scenario is auditing or troubleshooting the database links configured between planning and source instances, particularly when an A2M or M2A link fails or is misconfigured. The view is equally useful for verifying that all participating instances run a compatible applications version before a data refresh.

• List all enabled instances and their database links:

SELECT instance_code, apps_ver_text, instance_type,
       a2m_dblink, m2a_dblink
FROM   msc_apps_instances_v
WHERE  enable_flag = 'Y';

• Identify instances with a specific A2M database link:

SELECT instance_code, a2m_dblink, m2a_dblink, st_status
FROM   msc_apps_instances_v
WHERE  UPPER(a2m_dblink) LIKE '%A2M%';

• Validate version consistency across the deployment:

SELECT apps_ver_text, COUNT(*)
FROM   msc_apps_instances_v
GROUP  BY apps_ver_text;

These queries support routine administration of ASCP distributed deployments and provide the authoritative source for the A2M_DBLINK value referenced throughout MSC integration setup.