Search Results get_func_currency_attributes

Overview

PO_INQ_SV is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It serves as a server-side inquiry utility for the Purchasing (PO) module, supplying derived and resolved values that are consumed primarily by Inquiry and OTM/HTML-based views rather than by core transaction-processing APIs. Its functional role centers on populating inquiry views with buyer-facing information such as vendor names, party details, currency attributes, document type names, exchange rate types, and supplier contact data.

The package is not classified as a public API; the ETRM metadata classifies it under API classification OTHER, indicating it is an internal supporting package. It is positioned beneath a broad set of inquiry views (ICX_EDM_*, POS_*, POR_RCV_*, PJM_PROJECT_*, RCV_*) that expose purchasing, sourcing, and receiving data to end users. Because it is referenced by 39 other database objects, PO_INQ_SV functions as a shared resolution layer across multiple inquiry surfaces.

Key Procedures and Functions

The ETRM metadata documents 33 procedures and functions. The named entries include the following:

• NAME — A function that returns a descriptive or display name used in inquiry output, typically resolving an identifier into a user-readable label.
• GET_FUNC_CURRENCY_ATTRIBUTES — Returns functional currency attributes for a given document or operating unit context, supporting monetary display in inquiry views.
• GET_SOURCE_INFO — Retrieves sourcing or source-document information (such as source type or source reference) associated with a purchasing document.
• GET_TYPE_NAME — Resolves a document or lookup type code into its display name, drawn from purchasing document type definitions.
• GET_RATE_TYPE — Returns the exchange rate type associated with a currency conversion on a purchasing document.
• GET_VENDOR_NAME — Returns the supplier name for a given vendor identifier, resolving against supplier master data.
• GET_PARTY_VENDOR_NAME — Returns the vendor name in the context of the TCA party model, using HZ_PARTIES data.
• GET_VENDOR_EMAIL — Returns the supplier contact e-mail address for inquiry display, typically used in supplier-facing or notification-oriented views.

The remaining undocumented-by-name procedures follow the same pattern: each accepts an identifier or context value and returns a resolved descriptive attribute for use in inquiry view SQL.

Tables Accessed

PO_INQ_SV reads from a defined set of master and transactional tables through APPS synonyms:

• PO_HEADERS_ALL — The primary purchasing document header table, supplying document-level context such as type, currency, vendor, and rate information.
• AP_SUPPLIERS and HZ_PARTIES — Supplier and party master data used to resolve vendor names and party-based vendor names.
• HZ_PARTY_USG_ASSIGNMENTS — Party usage data that governs how a party is classified as a supplier.
• FND_USER — Application user information, used to resolve buyer or requester display names.
• AP_TERMS — Payment terms definitions, used to display terms on inquiry views.
• FND_CURRENCIES and GL_DAILY_CONVERSION_TYPES — Currency and exchange rate type definitions supporting currency attribute resolution.
• FINANCIALS_SYSTEM_PARAMETERS and FINANCIALS_SYSTEM_PARAMS_ALL — System parameter values such as functional currency for the operating unit.
• BOM_DEPARTMENTS, BOM_RESOURCES, and BOM_STANDARD_OPERATIONS — Manufacturing reference data accessed for inquiry contexts involving project or work-order-related purchasing.
• HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL — Organization and translated organization names, used to resolve organization unit descriptions.
• PO_DOCUMENT_TYPES_VL — Purchasing document type view, used by GET_TYPE_NAME.

The read-only nature of this package is consistent with its inquiry role: it resolves reference and master data without modifying purchasing transactions.

Usage Notes

PO_INQ_SV is invoked indirectly. End users reach it through Oracle iProcurement, Purchasing inquiry responsibilities, and the OTM/HTML-based purchasing views (ICX_EDM_PURCHASE_ORDER_V, ICX_PO_HEADERS_ARCHIVE_V, ICX_PO_SUPPLIER_ORDERS_V, and similar). It also supports the Purchasing summary and detail views (POS_PO_SUMMARY_V, POS_PO_DETAILS_V, POS_PO_ARCH_SUMMARY_V), receiving and delivery views (POR_RCV_*), and project-related sourcing views (PJM_PROJECT_BLANKET_PO_V, PJM_PROJECT_QUOT_V, PJM_PROJECT_RFQ_V).

Customizations should treat PO_INQ_SV as an internal dependency rather than a supported integration point. Because its callers include middleware-style views and possibly workflow notification packages (PO_WF_PO_NOTIFICATION, PO_WF_REQ_NOTIFICATION), signature changes risk invalidating a wide dependency graph. Custom code requiring similar vendor, currency, or type-name lookups should prefer public APIs or direct master-table queries rather than calling this package directly, and any modification should be validated against the 39 dependent objects listed in the ETRM dependency report.