Results for “planning_group”

50+ results




Overview
Explore in AI Chat

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

Overview

MRP_GET_PROJECT is a utility PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It is classified under the ETRM metadata as an "OTHER" API, meaning it is not a formally published open interface but an internal helper package used by the Oracle Planning (MRP/MPS) product family and related modules. Its business function is to resolve surrogate numeric identifiers into human-readable descriptive values for display and reporting purposes within planning and project-related screens. Rather than maintaining business logic that creates or updates transactional data, MRP_GET_PROJECT provides a lightweight lookup and translation layer, converting project IDs, task IDs, organization IDs, item IDs, category IDs, customer IDs, and vendor site IDs into the names, codes, and descriptions that end users expect to see. The package is declared AUTHID CURRENT_USER and includes PRAGMA RESTRICT_REFERENCES purity assertions for PROJECT, TASK, and PLANNING_GROUP, confirming that these functions read database state without writing to it, which makes them safe for use inside SQL statements and views.

Key Procedures and Functions

The package exposes thirteen documented functions, all returning VARCHAR2 or an FND lookup meaning type:

  • PROJECT — returns the project name or number associated with a given project ID.
  • TASK — returns the task name or number for a given task ID.
  • PLANNING_GROUP — derives the planning group description for a project ID.
  • LOOKUP_FND — resolves a lookup type and lookup code combination into its FND meaning.
  • LOOKUP_MEANING — resolves a lookup type and numeric lookup code into its meaning.
  • ORG_CODE — returns the organization code for a given organization ID.
  • ITEM_NAME — returns the item name for an organization and item ID pair.
  • ITEM_DESC — returns the item description for an organization and item ID pair.
  • CATEGORY_DESC — returns a category description for a category set and category ID.
  • CATEGORY_NAME — returns the category name for a category ID.
  • CUSTOMER_NAME — returns the customer name for a customer ID.
  • SHIP_TO_ADDRESS — returns a formatted ship-to address for a site ID.
  • VENDOR_SITE_CODE — returns the vendor site code for an organization and vendor site ID.

Tables Accessed

The package reads from a broad set of APPS synonyms reflecting its role as a cross-module resolver. Project and task values are sourced from PA_PROJECTS_ALL and PA_TASKS, with planning group parameters drawn from MRP_PROJECT_PARAMETERS. Item name and description lookups use MTL_SYSTEM_ITEMS_KFV and MTL_PARAMETERS. Category resolution relies on MTL_CATEGORIES_KFV and MTL_CATEGORY_SETS. Customer-facing functions access the TCA model through HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTIES, HZ_PARTY_SITES, and HZ_LOCATIONS, while vendor site data and planning sequence numbers draw on MRP_SEIBAN_NUMBERS. All access is read-only, consistent with the purity pragmas declared in the specification.

Usage Notes

MRP_GET_PROJECT is referenced by 48 other packages, indicating it is an internal dependency of the planning suite rather than a standalone entry point. It is typically invoked from Oracle Forms, concurrent programs, and report queries where a foreign-key ID must be displayed as a meaningful label, and from custom code that needs the same translation behavior as standard planning screens. Because the functions carry RESTRICT_REFERENCES pragmas, they may be embedded directly in SQL SELECT lists and view definitions. Developers extending MRP functionality should treat the package as a stable read-only utility; signature changes should be avoided because of the large number of dependent packages. In EBS 12.1.1 and 12.2.2 the behavior is consistent, with 12.2.2 deployments using the same APPS synonym layer over the TCA and planning tables.