Results for “po_type”

50+ results




Overview
Explore in AI Chat

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

Overview

APPS.PJM_COMMITMENT_UTILS is a PL/SQL utility package in the Oracle E-Business Suite Projects (PJM) module that supplies reusable lookup and derivation functions for commitment-related processing. Commitments in Oracle Projects represent externally obligated costs — purchase orders, requisitions, and similar documents — that originate in Oracle Purchasing and other source applications and are subsequently interfaced into Project Costing for budgeting and expenditure tracking. The package provides the common resolution logic required to translate raw commitment attributes (organization, project, destination, item, resource, and subtype identifiers) into the descriptive values that commitment records and their associated user interfaces must display or validate.

The package carries a header version of 120.1 dated 2006/07/10 and is classified under ETRM as an "OTHER" API. It exposes eighteen documented functions and is referenced by five other packages, indicating that it functions as a shared, low-level utility layer rather than a standalone user-facing API. Note that in EBS 12.1.1 and 12.2.2 the majority of the source header is unchanged; the object is shipped in the APPS schema and accessed through APPS synonyms.

Key Procedures and Functions

  • REQ_TYPE and PO_TYPE — return the document type description for a given organization and subtype, resolving requisition and purchase order classifications.
  • BOM_RESOURCE — resolves a resource identifier to its descriptive resource value.
  • ITEM_NUMBER — returns the item number for an item and organization pair.
  • PO_EXP_ORG, PO_EXP_TYPE, PO_TASK_ID — derive the expenditure organization, expenditure type, and task identifier applicable to a purchasing-originated commitment, based on organization, project, item, resource, destination, subinventory, entity, and sequence inputs.
  • UOM_CONVERSION_RATE — returns the unit-of-measure conversion rate for the given lookup, destination, item, and organization.
  • GET_UNIT, GET_UOM_CODE, GET_UOM_TL — return the unit of measure in base, coded, and translated (language-specific) forms respectively. GET_UOM_TL, the subject of the search, supplies the translated UOM description.
  • VENDOR_NAME and PEOPLE_NAME — resolve vendor and person identifiers to display names.
  • PO_PROJECT_ID — validates and returns the project identifier for a purchase order context.
  • MTL_EXPENDITURE_TYPE, RES_EXPENDITURE_TYPE, OSP_EXPENDITURE_TYPE — derive the appropriate expenditure type for material, resource, and outside-processing contexts.
  • CREATE_SYNONYMS — a utility routine for creating the APPS synonyms under which the package and its dependencies are accessed.

Tables Accessed

The package reads (and in limited cases references) a defined set of tables through APPS synonyms. MTL_SYSTEM_ITEMS_B, WIP_DISCRETE_JOBS, and WIP_OPERATIONS supply item and work-in-process context; BOM_RESOURCES and BOM_DEPARTMENTS support resource resolution. CST_ITEM_COST_DETAILS and CST_CAT_ELE_EXP_ASSOCS provide costing detail and category-element-to-expenditure-type associations. PA_EXPENDITURE_TYPES resolves expenditure types. PO_DOCUMENT_TYPES_ALL_TL provides translated purchasing document types for REQ_TYPE and PO_TYPE. PER_ALL_PEOPLE_F supplies person names. PJM_ORG_PARAMETERS and PJM_PROJECT_PARAMETERS supply committing-organization and project parameter setup, while MTL_PARAMETERS and FND_PRODUCT_INSTALLATIONS support organization and installation context, and FND_ORACLE_USERID supports user identification.

Usage Notes

PJM_COMMITMENT_UTILS is invoked as a supporting utility from other PL/SQL packages and from Oracle Projects commitment-processing logic rather than being called directly by end users. It is typically reached through form logic, concurrent program internals, or custom extensions that need consistent derivation of expenditure type, organization, task, and UOM values. Because it is classified as "OTHER" and is not a formal public API, callers should treat its signatures as internal and stable as shipped, relying on GET_UOM_TL and its siblings for translated lookup values without assuming version-to-version behavior beyond the documented functions.