Search Results oe_org_address




Overview
Explore in AI Chat

Overview

PJM_INQUIRY is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite, documented under ETRM 12.2.2 with an API classification of OTHER. Its name, the PJM_ prefix, and its dependency set indicate that it belongs to the Oracle Projects (PJM) product family and functions as a lightweight inquiry and decode utility layer. Rather than performing transactional DML, the package exposes a set of small scalar functions that translate stored identifiers—person IDs, vendor IDs, location IDs, item IDs, term IDs, and lookup codes—into human-readable display values, and that derive totals and type descriptions from Project Procurement and related ordering data.

This pattern is characteristic of Oracle Forms-based inquiry windows, where a base block stores a foreign key and the form requires an immediate descriptive value for display or validation without a full join to the underlying entity. PJM_INQUIRY centralizes these derivations so that multiple forms and packages can reuse consistent lookup logic. The header comment (PJMWINQS.pls 120.4) confirms a long-lived, stable interface that has been carried forward across the 12.1.1 and 12.2.2 code lines. The package is referenced by six other packages, reflecting its role as a shared utility rather than an application entry point.

Key Procedures and Functions

The package declares nineteen documented functions, all returning VARCHAR2 or NUMBER scalars.

  • GET_REQ_TOTAL — returns a numeric total for a requisition header, aggregating requisition line amounts for display in inquiry screens.
  • BR_TYPE — returns the business type or subtype description for a given organization and subtype.
  • VENDOR_CONTACT — returns the display name of a supplier contact given a contact identifier.
  • OE_LOOKUP — resolves an Order Management lookup code and lookup type into its meaning.
  • ITEM_NUMBER — returns the item number (concatenated key flexfield display) for an item within an inventory organization.
  • PAYMENT_TERM — returns the translated payment term name for a term identifier.
  • PEOPLE_NAME — returns the full display name of a person for a given person identifier. This is the function associated with the search term "people_name" and is the most common reason users locate this package.
  • GET_LOOKUP — a generic lookup-value resolution function accepting a code and a lookup type.
  • LOCATION_CODE — returns the location code or description for a location identifier.
  • VENDOR_SITE — returns the vendor site description for a supplier and site pair.
  • VENDOR_NAME — returns the supplier name for a vendor identifier.
  • PO_TYPE — returns the purchasing document type description for an operating unit.
  • OE_ORDER_TOTAL — returns the numeric total for an Order Management order header.
  • OE_ORG_ADDRESS — returns the formatted address of an organization for a given organization type.
  • YES_NO — converts a lookup code into a Yes/No display string.
  • SYS_YES_NO — converts a numeric system flag into a Yes/No display string.
  • LOCATOR_CONTROL — returns the locator control description for a numeric lookup code.
  • COMPONENT_SERIAL — returns the serial number associated with a component at a given WIP operation sequence.
  • TRANSACTION_SOURCE_NAME — returns the descriptive name of a transaction source from its type ID and source ID.

Tables Accessed

The package reads from the following documented tables through APPS synonyms: AP_TERMS_TL (payment term names for PAYMENT_TERM); HR_LOCATIONS_ALL_TL and HZ_LOCATIONS, HZ_PARTY_SITES (address and location derivation for LOCATION_CODE and OE_ORG_ADDRESS); HZ_CUST_ACCT_SITES_ALL and HZ_CUST_SITE_USES_ALL (customer site context for order-related lookups); MTL_SYSTEM_ITEMS_KFV (item number display key flexfield for ITEM_NUMBER); MTL_MATERIAL_TRANSACTIONS and MTL_UNIT_TRANSACTIONS (transaction source and serial information for TRANSACTION_SOURCE_NAME and COMPONENT_SERIAL); OE_ORDER_LINES_ALL (order line amounts backing OE_ORDER_TOTAL); PO_HEADERS_ALL, PO_REQUISITION_LINES_ALL, and PO_DOCUMENT_TYPES_ALL_TL (requisition totals, purchase order types, and supplier-facing document descriptions); and PER_ALL_PEOPLE_F (person names for PEOPLE_NAME).

Usage Notes

PJM_INQUIRY is normally invoked from Oracle Forms inquiry windows and from custom PL/SQL blocks rather than from concurrent programs, since its functions return single scalar values suitable for a field-level trigger or a SQL SELECT list item. Because all documented functions are read-only, it is safe to call from custom code without concern for transactional side effects; however, callers should account for the fact that the functions resolve values at call time and therefore return the current effective row from date-tracked tables such as PER_ALL_PEOPLE_F. Code that depends on this package should treat the function signatures as stable, and should avoid assuming behavior beyond the documented return types.