Search Results mrp_get_project




Overview
Explore in AI Chat

Overview

MRP_GET_PROJECT is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema, classified under the ETRM documentation as an OTHER (non-API) utility package. Its documented purpose is to support the Oracle Material Requirements Planning (MRP) and Supply Chain Planning product family by returning and resolving descriptive reference information for planning-related entities. Rather than exposing a formal public application programming interface, MRP_GET_PROJECT functions as an internal lookup and conversion helper: it translates stored identifier values into human-readable descriptions for projects, tasks, planning groups, organizations, items, categories, customers, ship-to addresses, and vendor sites.

The package is present and valid in both Oracle EBS 12.1.1 and 12.2.2, and it depends extensively on Oracle Planning, Oracle Projects, Oracle Inventory, Oracle Purchasing, and Oracle Trading Community Architecture (TCA / HZ) base tables. It is a heavily reused internal object: the ETRM metadata records that it is referenced by 48 other database packages, while it is not referenced by any database object itself, confirming its role as a leaf-level data retrieval utility consumed by higher-level planning programs.

Key Procedures and Functions

The ETRM documentation lists thirteen callable units within this package body. Each serves as a specialized retrieval routine:

  • PROJECT — resolves and returns descriptive information for a project, drawing on the Oracle Projects project definition data.
  • TASK — returns descriptive information for a project task associated with a project.
  • PLANNING_GROUP — retrieves the description of a planning group used to segment planning activity.
  • LOOKUP_FND — returns a lookup code value from the Oracle Application Object Library lookup facility.
  • LOOKUP_MEANING — returns the user-facing meaning (description) for a given lookup code, complementing LOOKUP_FND.
  • ORG_CODE — resolves and returns the organization code for a given inventory organization.
  • ITEM_NAME — returns the concatenated item name for an inventory item.
  • ITEM_DESC — returns the description of an inventory item.
  • CATEGORY_DESC — returns the description for an item category.
  • CATEGORY_NAME — returns the concatenated (key flexfield) name of an item category.
  • CUSTOMER_NAME — returns the customer name associated with a customer account, sourced from TCA.
  • SHIP_TO_ADDRESS — returns the formatted ship-to address for a customer site.
  • VENDOR_SITE_CODE — returns the supplier site code associated with a purchasing vendor site.

Tables Accessed

The package reads from a broad set of base and descriptive tables through APPS synonyms. Customer and address data come from HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_PARTIES, and HZ_PARTY_SITES. Project and task definitions come from PA_PROJECTS_ALL and PA_TASKS. Item and category data come from MTL_SYSTEM_ITEMS_KFV, MTL_CATEGORIES_KFV, MTL_CATEGORIES_VL, MTL_CATEGORY_SETS, MTL_PARAMETERS, and ORG_ORGANIZATION_DEFINITIONS. Supplier site information comes from PO_VENDOR_SITES_ALL. Planning-specific control data comes from MRP_PROJECT_PARAMETERS and MRP_SEIBAN_NUMBERS, while lookup values derive from FND_LOOKUPS and MFG_LOOKUPS. These reads support the descriptive-resolver role of the package; no write activity is implied by the documented dependencies.

Usage Notes

MRP_GET_PROJECT is an internal utility rather than an end-user-facing API. It is typically invoked from within other planning packages, concurrent planning programs, and Oracle Forms-based planner workbenches that need to render project, task, item, category, customer, or supplier-site descriptions alongside numeric identifiers. Because it is referenced by 48 packages, customizations should treat it as a shared dependency and avoid modifying its behavior. The presence of a standalone package function named MRP_GET_PROJECT (mirroring the package name) indicates it exposes a specific project-resolution entry point in addition to its broader resolver routines. Developers extending planning functionality may call these functions for consistent description retrieval, but should rely on documented parameters and behavior rather than assuming a public supported interface.