Results for “vendor_site”

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

Overview

APPS.PJM_INQUIRY is a VALID PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle Projects module (PJM prefix) and is classified as an OTHER API in the ETRM repository. Its documented purpose is to centralize inquiry and lookup logic used by Project Manufacturing and Project Contracts inquiry screens, providing a single, reusable layer of helper routines that resolve surrogate identifiers and coded values into the descriptive text displayed on Oracle Forms inquiry windows.

The package encapsulates cross-module reference data retrieval, spanning Oracle Purchasing, Oracle Order Management, Oracle Inventory, Oracle Payables, Oracle Receivables, and Oracle Human Resources. Each function returns a scalar descriptive attribute — a name, a code, a description, or a flag — for a given identifier. Because APPS.PJM_INQUIRY is not referenced by any database object, it is strictly a leaf-level utility library consumed by client-side code rather than by triggers or other PL/SQL units. The ETRM metadata records that six other packages reference it, confirming its role as a shared display-support service across the Project Manufacturing inquiry family.

Key Procedures and Functions

The ETRM metadata documents nineteen procedures and functions. They are consistently typed as scalar value resolvers, and no parameter lists are published in the metadata.

• VENDOR_NAME, VENDOR_SITE, VENDOR_CONTACT — resolve supplier identification and contact details for purchasing and receiving inquiry displays.
• PAYMENT_TERM — derives payment term descriptions from AP_TERMS_TL for supplier-related inquiry screens.
• PO_TYPE and PO_DOCUMENT_TYPES_ALL_TL support — translate purchasing document type codes into descriptive text.
• GET_REQ_TOTAL — calculates or retrieves the total quantity or amount associated with requisition lines for inquiry presentation.
• ITEM_NUMBER and LOCATOR_CONTROL — return the concatenated item key flexfield value and the locator control setting for inventory-related displays.
• COMPONENT_SERIAL and TRANSACTION_SOURCE_NAME — resolve component serial numbers and the descriptive name of an inventory transaction source.
• OE_ORDER_TOTAL, OE_ORG_ADDRESS, and OE_LOOKUP — provide order totals, warehouse organization addresses, and Order Management lookup descriptions.
• PEOPLE_NAME — returns a formatted person name from PER_ALL_PEOPLE_F for buyer, planner, or approver fields.
• LOCATION_CODE — returns a location code from the HR and HZ location tables.
• BR_TYPE, GET_LOOKUP, and OE_LOOKUP — generic lookup description resolvers against FND_LOOKUPS, MFG_LOOKUPS, and OE_LOOKUPS respectively.
• YES_NO and SYS_YES_NO — convert stored flags into the standard EBS Yes/No and Yes/No (System) display values.

Tables Accessed

All table access is performed through APPS synonyms. The package reads supplier and purchasing data from PO_VENDORS, PO_VENDOR_SITES_ALL, PO_VENDOR_CONTACTS, PO_HEADERS_ALL, PO_REQUISITION_LINES_ALL, and PO_DOCUMENT_TYPES_ALL_TL. Order and pricing data are drawn from OE_ORDER_LINES_ALL, MTL_SALES_ORDERS_KFV, and OKE_K_HEADERS_V. Inventory inquiries use MTL_SYSTEM_ITEMS_KFV, MTL_MATERIAL_TRANSACTIONS, and MTL_UNIT_TRANSACTIONS. Party, customer, and location data come from HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTY_SITES, HZ_LOCATIONS, and HR_LOCATIONS_ALL_TL. Payables and human resources references include AP_TERMS_TL and PER_ALL_PEOPLE_F. Lookup tables enumerated in the dependency list include FND_LOOKUPS, MFG_LOOKUPS, OE_LOOKUPS, and PO_LOOKUP_CODES. The dependency metadata also lists the package itself and SYS.STANDARD, indicating internal package references and standard PL/SQL library usage.

Usage Notes

In Oracle EBS 12.1.1 and 12.2.2, PJM_INQUIRY is typically invoked from Oracle Forms inquiry screens within the Project Manufacturing and Project Contracts modules, where field-level validation and post-query triggers call the scalar functions to populate descriptive, non-key fields. Concurrent programs or custom PL/SQL extensions that need the same code-to-description conversions may also call it directly.

Because the functions are read-only, the package introduces no transaction or locking side effects. Its performance profile is dominated by high-frequency single-row lookups against the reference tables listed above, so custom code should avoid invoking it in tight loops. As with all APPS-owned packages, customizations should not modify the body; callers should rely on the published function names and treat them as a stable interface. Oracle Forms and concurrent programs that overlay the base EBS codebase should apply patches in the normal manner, since the package is delivered as a valid, supported component.