Results for “action_id”

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

Overview

MSC_GET_NAME is a foundational utility package in the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module, owned by the APPS schema and delivered in a VALID state across EBS 12.1.1 and 12.2.2. Its central purpose is name and label resolution: the package translates internal numeric identifiers, foreign keys, and coded values that populate the MSC_ planning tables into human-readable display strings. Rather than forcing every planning form, report, and analytic view to duplicate decoding logic, MSC_GET_NAME centralizes it so that item numbers, organization codes, location codes, project and task names, resource names, demand and supply dates, and lookup meanings can be consistently derived from the underlying planning engine data. Because it reads from the MSC_ synonym layer, it presents a stable interface to the MSC schema regardless of internal table changes, and its explicit caches (number and string) reduce the repetitive query cost inherent in resolving the same reference many times within a single planning run.

Key Procedures and Functions

The dictionary documents 156 procedures and functions in this package body, making it a broad resolution library rather than a single-purpose API. The documented entries cluster into functional families:

• Caching primitives: WRITE_TO_NUMBER_CACHE, READ_FROM_NUMBER_CACHE, WRITE_TO_STRING_CACHE, READ_FROM_STRING_CACHE implement the internal memoization used by the remaining resolvers.
• Entity and context resolvers: PROJECT, TASK, PLANNING_GROUP, ORG_CODE, LOCATION_CODE, INSTANCE_CODE, JOB_NAME, and RESOURCE_OVER_UTIL_COST return descriptive names for planning identifiers.
• Date and flow resolvers: DEMAND_DATE and SUPPLY_DATE format planning dates, while SUPPLY_ORDER and ORDER_TYPE identify fulfillment transactions and their classifications.
• Lookup and semantic decoders: LOOKUP_MEANING, LOOKUP_BY_PLAN, FND_LOOKUP_MEANING, and PROCESS_PRIORITY convert coded values from MFG_LOOKUPS, FND_LOOKUPS, and FND_LOOKUP_VALUES into displayable meanings, optionally scoped to a specific plan.

Each resolver accepts an identifier or code and returns the corresponding name or meaning, insulating callers from the join logic behind it.

Tables Accessed

The dependency list is dominated by the MSC_ planning data model. Planning configuration and reference tables include MSC_PLANS, MSC_PLAN_SCHEDULES, MSC_PLAN_BUCKETS, MSC_ITEMS, MSC_SYSTEM_ITEMS, MSC_ITEM_CATEGORIES, MSC_CATEGORY_SETS, and MSC_ABC_CLASSES. Manufacturing structures such as MSC_BOMS, MSC_BOM_COMPONENTS, MSC_ROUTINGS, MSC_ROUTING_OPERATIONS, MSC_OPERATION_NETWORKS, MSC_OPERATION_COMPONENTS, MSC_JOB_OPERATION_NETWORKS, and MSC_DEPARTMENT_RESOURCES supply resource and routing descriptions. Supply chain entities including MSC_DEMANDS, MSC_SUPPLIES, MSC_SALES_ORDERS, MSC_TRADING_PARTNERS, MSC_TRADING_PARTNER_SITES, MSC_CARRIER_SERVICES, and MSC_INTERORG_SHIP_METHODS drive demand, supply, order, and shipment lookups. Calendar and organizational context comes from MSC_CALENDAR_DATES, MSC_REGIONS, MSC_LOCATION_ASSOCIATIONS, MSC_APPS_INSTANCES, and MSC_SEGMENT_ALLOCATIONS. Project data is read from MSC_PROJECTS and MSC_PROJECT_TASKS, while exceptions and user annotations come from MSC_EXCEPTION_DETAILS, MSC_EXCEPTION_LOOKUP_V, MSC_X_EXCEPTION_DETAILS, MSC_USER_NOTES, and the MSC_USER_PREFERENCE family. Foundational Oracle Application Object Library tables — FND_APPLICATION, FND_LOOKUPS, FND_LOOKUP_VALUES, FND_GLOBAL, and FND_PROFILE — provide application context, session identity, and lookup meanings. DUAL and PLITBLM (the PL/SQL integer table type) are used for scalar arithmetic and bulk collection handling.

Usage Notes

MSC_GET_NAME is an internal workhorse rather than a user-invoked API. It is referenced by 169 other database objects, chiefly planners, concurrent programs, OBI/BI Publisher reports, and the ASCP workbench forms that display plan output. Typical invocation patterns include a report query calling ORG_CODE or ITEM-related resolvers to render readable columns, a planning process calling DEMAND_DATE or SUPPLY_DATE to format bucket dates, and exception or note screens calling LOOKUP_MEANING or FND_LOOKUP_MEANING to display coded statuses in the user's language via FND_GLOBAL and FND_PROFILE settings. Because the package performs no documented DML — it reads through APPS synonyms — it is safe to call from custom concurrent programs, views, and extensions; the caching procedures exist specifically to make repeated calls efficient. The package is never referenced by external database objects, confirming its position as a leaf-level utility layer within the MSC schema. Implementers extending ASCP output should reuse these resolvers rather than re-deriving names directly from MSC tables, ensuring consistent display behavior and honoring Oracle's cached access paths.