Search Results get_person_name

Overview

APPS.ICX_GET is a utility package in the Oracle E-Business Suite Procurement and iProcurement schema, declared with AUTHID CURRENT_USER so that it executes under the privileges of the calling session rather than the package owner. Despite its name, it does not retrieve a single logical entity; it is a grab-bag of low-level scalar getter functions that return derived lookup values to Oracle iProcurement and related purchasing forms. The package header (ICXGETS.pls, version 115.2, last shipped 2001/12/05) exposes six public functions, all of which are scalar-returning and side-effect free. Each function is additionally protected by a PRAGMA RESTRICT_REFERENCES declaration (WNDS, RNPS, WNPS, and for one function WNDS only), which certifies to the PL/SQL runtime that the functions write no database state and read no package state — a requirement for calling these functions from SQL statements and from forms triggers. The package is referenced by seven other packages in the ETRM inventory, confirming its role as a shared convenience layer rather than an application entry point.

Key Procedures and Functions

• GET_PERSON_NAME — accepts a person identifier and returns the corresponding display name as a VARCHAR2. This is the function most commonly searched for; it provides a lightweight alternative to joining PER_ALL_PEOPLE_F directly when only a name is required.
• GET_ACTION_HISTORY_DATE — accepts an object identifier, object type code, subtype code, and action code, and returns the DATE on which the matching action occurred. It supports audit-style display of document progression.
• GET_AVAIL_ITEM_COUNT — accepts a vendor identifier and category identifier and returns a NUMBER representing the count of available items. It is used to populate catalog or sourcing indicators.
• GET_ORD_ITEM_COUNT — accepts a vendor identifier, a type code, and a category identifier and returns a NUMBER count of ordered items, supporting spend or activity summaries.
• GET_GL_ACCOUNT — accepts a code combination identifier and returns the corresponding GL account as a VARCHAR2.
• GET_GL_VALUE — accepts an application identifier, a key flexfield code, a key flexfield number, a code combination identifier, and a GL qualifier, returning a VARCHAR2 segment value. This is the most parameterized function in the package and is used for flexfield segment resolution.

Tables Accessed

The documented table references are resolved through APPS synonyms. PER_ALL_PEOPLE_F supplies the person data behind GET_PERSON_NAME. PO_ACTION_HISTORY provides the action/date records consumed by GET_ACTION_HISTORY_DATE. PO_HEADERS, PO_LINES, PO_REQUISITION_HEADERS, and PO_REQUISITION_LINES are the purchasing and requisition tables from which the item count functions derive their aggregate results. The GL functions resolve values through the standard flexfield structures rather than the transactional tables listed.

Usage Notes

ICX_GET is normally invoked from Oracle Forms (iProcurement and purchasing-related form modules) and from client-side or custom PL/SQL blocks requiring a single scalar value without the overhead of a full query. Because every function carries RESTRICT_REFERENCES pragmas, they may safely be called inside SQL SELECT lists and WHERE clauses. The package has been stable since its 2001 header, so behavior is consistent across EBS 12.1.1 and 12.2.2. Customizations should call the package rather than reimplementing person-name or flexfield lookups, since GET_PERSON_NAME and GET_GL_VALUE remain the canonical thin wrappers referenced by dependent packages.