Search Results read_from_number_cache

Overview

MSC_GET_NAME is a shared utility package in the Oracle Advanced Supply Chain Planning (ASCP) schema, owned by APPS and classified as OTHER in ETRM. Its business purpose is name resolution: it converts internal numeric identifiers used throughout the MSC planning tables into the human-readable values that planners, reports, and concurrent programs expect to see. Planning data is stored keyed by surrogate IDs — project_id, task_id, organization_id, resource_id, plan_id, and instance_id — and MSC_GET_NAME provides the single, centrally maintained translation layer between those IDs and their descriptive names. Because the package is referenced by 169 other packages, it functions as a foundational dependency across the MSC module rather than an end-user-facing component.

Key Procedures and Functions

The documented interface consists of 156 functions, of which the following are representative of its resolution responsibilities.

• PROJECT, TASK, PLANNING_GROUP, JOB_NAME — return descriptive names for project, task, planning group, and job identifiers within the context of a given organization, plan, and instance.
• ORG_CODE, LOCATION_CODE, INSTANCE_CODE — resolve organization, inventory location, and application instance identifiers to their codes; ORG_CODE is overloaded to accept either a numeric organization ID or an instance-qualified varchar2 form, the latter added for SRP (single resource planning) support.
• DEMAND_DATE, SUPPLY_DATE — return DATE values derived from a pegging identifier and plan, used to present pegging-derived dates without the caller having to join the pegging tables directly.
• RESOURCE_OVER_UTIL_COST — returns a NUMBER for a resource, department, organization, and plan combination.
• LOOKUP_MEANING, LOOKUP_BY_PLAN, FND_LOOKUP_MEANING — translate lookup codes into meanings. LOOKUP_BY_PLAN adds plan-type and source-organization awareness, while FND_LOOKUP_MEANING applies standard FND lookup semantics.
• SUPPLY_ORDER, ORDER_TYPE — resolve supply and order identifiers to their display values.
• PROCESS_PRIORITY — the function associated with the searched term; it resolves a process-priority identifier to its descriptive value, consistent with the package's general naming role.
• WRITE_TO_NUMBER_CACHE, READ_FROM_NUMBER_CACHE, WRITE_TO_STRING_CACHE, READ_FROM_STRING_CACHE — an internal caching mechanism that reduces repeated lookups of the same identifiers during a plan run.

Tables Accessed

MSC_GET_NAME reads from a broad set of ASCP planning tables through APPS synonyms. FND_APPLICATION and FND_LOOKUP_VALUES supply application and lookup meaning data. MSC_APPS_INSTANCES supports instance code resolution. MSC_CALENDAR_DATES underpins date returns. MSC_BOMS and MSC_BOM_COMPONENTS, MSC_DEPARTMENT_RESOURCES, MSC_DESIGNATORS, and MSC_ABC_CLASSES provide name and classification data for bills, resources, and items. MSC_DEMANDS, MSC_DRP_ALLOC_RULES, MSC_DRP_DMD_PRI_RULES, and MSC_EAM_ACT_ASSOCIATIONS support demand, distribution, and asset association resolution. In practice the package is predominantly a read-only resolver against these sources.

Usage Notes

The package is almost never invoked directly by end users. It is called from planning engine code, from other MSC packages (the 169 documented dependents), from Planner Workbench forms and their supporting libraries, and from custom concurrent programs and reports that need to display planning identifiers as names. The internal number and string caches are session-scoped aids, so callers should expect that repeated resolution of the same ID within a single session is served from cache. Custom code should call these functions rather than joining the underlying planning tables directly, so that naming conventions and plan-context logic remain consistent with standard ASCP behavior.