Search Results id_to_value

Overview

MRP_ID_TO_VALUE is a utility package in the Oracle E-Business Suite APPS schema that provides identifier-to-descriptive-value translation services for Oracle Manufacturing and Supply Chain objects. The package exposes a family of overloaded Id_To_Value functions, each of which accepts a surrogate key (a numeric ID) and returns the corresponding user-facing name or description as a VARCHAR2 string. This pattern is common in Oracle EBS, where transactional and planning tables store foreign key references to entities such as organizations, items, projects, tasks, and work-in-process entities, but end users and reports require the readable value rather than the internal identifier.

The package header carries an important internal characterization: it is partially generator-controlled. A comment block states that the Get_Attr_Tbl procedure is used by the generator to avoid overriding or duplicating existing Id_To_Value functions, and carries the directive "DO NOT MODIFY." The function prototypes themselves are delimited by -- START GEN Id_To_Value and -- END GEN Id_To_Value markers, indicating that an automated code generator appends new function prototypes between these markers. The package was originally shipped under the source header MRPSIDVS.pls, whose revision path dates to 1999, positioning this as a long-standing, stable component of the MRP (Material Requirements Planning) product family.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the defining user. This design supports invocation across schemas and reinforces the package's role as a shared, low-level reference utility rather than a privileged business process.

Key Procedures and Functions

The documented interface comprises nine callable objects: one procedure and eight functions.

• GET_ATTR_TBL — A generator-support procedure responsible for managing the internal attribute table. Per the source comments, it exists so that the code generator can detect and avoid overriding or duplicating existing Id_To_Value definitions. It is not intended for application or custom-code invocation.
• COMPLETION_LOCATOR — Returns the display value for a completion locator identifier, used to describe where completed assemblies are received in a discrete manufacturing context.
• LINE — Returns the descriptive value for a production line identifier, typically the line name used in repetitive manufacturing and scheduling.
• ORGANIZATION — Returns the organization name for an organization identifier, translating the operating unit or inventory organization key into a readable label.
• PRIMARY_ITEM — Returns the item description or name for a primary item identifier, allowing planning and WIP records to display the item rather than its numeric key.
• PROJECT — Returns the project name or number corresponding to a project identifier, supporting project-based manufacturing and planning views.
• SCHEDULE_GROUP — Returns the schedule group name for a schedule group identifier, relevant to production scheduling and grouping logic.
• TASK — Returns the task name or number for a task identifier, complementing the PROJECT function for project-and-task structures.
• WIP_ENTITY — Returns the descriptive identifier for a WIP entity, translating the work order or job key into a user-recognizable value.

Each function follows a uniform contract: a single numeric input identifier and a VARCHAR2 return value. Because the package is generator-controlled, the set of functions is expected to grow as new reference attributes are registered, with prototypes appended within the generated section of the header.

Tables Accessed

The documented metadata identifies three tables reached through APPS synonyms:

• WIP_LINES — The source of production line definitions, consulted by the LINE function to resolve a line identifier to its name.
• WIP_SCHEDULE_GROUPS — The source of schedule group definitions, consulted by SCHEDULE_GROUP to return the group name for a given identifier.
• PLITBLM — A multi-purpose foundation table used in Oracle EBS to store name-value pairs across many lookup and reference domains. Functions such as ORGANIZATION, PROJECT, TASK, PRIMARY_ITEM, COMPLETION_LOCATOR, and WIP_ENTITY are likely to resolve their values from this table, since it provides a generic attribute store keyed by identifier.

All access is read-only in nature; the functions exist to translate identifiers into descriptive strings and do not perform transactional writes.

Usage Notes

MRP_ID_TO_VALUE is designed as a lightweight, reusable lookup utility. In practice it is invoked from PL/SQL code, custom reports, and concurrent program logic wherever an MRP or WIP record must be presented with readable descriptions instead of raw IDs. Custom extensions and personalizations commonly call the individual functions directly — for example, MRP_ID_TO_VALUE.ORGANIZATION(l_org_id) — to populate descriptive columns in custom queries or interfaces.

Two constraints govern its use. First, because the package is generator-owned, developers must not modify the generated section or the GET_ATTR_TBL procedure; customization should instead be confined to separate, explicitly owned packages. Second, the AUTHID CURRENT_USER declaration means the caller requires appropriate privileges on the underlying tables (WIP_LINES, WIP_SCHEDULE_GROUPS, and PLITBLM) through APPS synonyms. Failure to hold those grants will cause runtime privilege errors regardless of the package's own definer rights.

The metadata further records that this package is referenced by one other package, confirming its role as a shared dependency in the Oracle Manufacturing and Planning code stack rather than a standalone deliverable. Administrators and developers should treat it as an internal infrastructure component whose signature and membership are maintained by Oracle's generator tooling across releases, including EBS 12.1.1 and 12.2.2.