Search Results get_latest_recvr_gl_date
Overview
PA_EXPENDITURES_UTILS is a shared PL/SQL utility package in the Oracle EBS Projects (PA) module, owned by the APPS schema. It supplies reusable helper logic for validating and resolving expenditure-related data across Oracle Projects. Its role is largely supportive: it centralizes lookups for organization names, job names, expenditure type attributes, and date/period derivation so that other Project Costing and expenditure entry components do not each re-implement the same logic. The package is referenced by 51 other packages, which reflects its position as a common dependency rather than a standalone user-facing API. It is classified as OTHER in the API registry, meaning it is not a published interface API but an internal utility layer.
Key Procedures and Functions
The documented callable units fall into three broad groups.
- Organization name resolution: GETORGTLNAME and GETORGNAME return organization names, with GETORGTLNAME working against translated name data and GETORGNAME providing the base-language name. GET_ORG_NAME returns an organization name based on an organization identifier and organization control value, while GET_ORG_NAME_WOSEC provides an alternate organization-name lookup variant.
- Expenditure type validation: CHECK_EXPENDITURE_TYPE, CHECK_EXP_TYPE_CLASS_CODE, and CHECK_EXP_TYPE_SYS_LINK_COMBO validate expenditure type data. These routines verify that an expenditure type, its class code, and its system linkage combination are consistent and valid before expenditure records are processed. CHECK_EXP_TYPE_SYS_LINK_COMBO, the function most relevant to this search, confirms that a given expenditure type and system linkage pairing is a legitimate combination.
- Latest date and period derivation: GET_LATEST_DATE_PERIOD_NAME, GET_LATEST_GL_DATE, GET_LATEST_PA_DATE, GET_LATEST_RECVR_PA_DATE, GET_LATEST_RECVR_GL_DATE, GET_LATEST_PA_PER_NAME, GET_LATEST_GL_PER_NAME, GET_LATEST_RECVR_PA_PER_NAME, and GET_LATEST_RECVR_GL_PER_NAME return the most recent Project Accounting or General Ledger date or period name, including versions for receiver processing. GETJOBNAME returns a job name from the jobs table.
The package specification also declares numerous global variables, including G_exp_item_id, PA and GL date and period name globals, and receiver-related equivalents, which cache expenditure item context. Additional organization-related globals were introduced to support specific bug fixes. Several functions are declared with PRAGMA RESTRICT_REFERENCES (WNDS), indicating they are restricted to read operations with no database state writes, making them safe for use inside SQL.
Tables Accessed
The package reads from several underlying tables via APPS synonyms.
- HR_ALL_ORGANIZATION_UNITS_TL — translated organization unit names, used by the organization name functions.
- HR_ALL_ORGANIZATION_UNITS — base organization unit records, used for organization validation and name lookup.
- PER_JOBS — job definitions, used by GETJOBNAME.
- PA_COST_DISTRIBUTION_LINES_ALL — cost distribution lines, consulted when deriving latest dates and periods for expenditure items.
- PA_SYSTEM_LINKAGES — system linkage definitions, used by the expenditure type system linkage validation functions.
These reads support name resolution, validation of expenditure type and system linkage combinations, and determination of the most recent accounting dates and periods applicable to an expenditure item.
Usage Notes
Because PA_EXPENDITURES_UTILS is a utility package referenced by dozens of other packages, it is typically invoked indirectly rather than called by end users. It is expected to be called from Oracle Projects forms, concurrent programs, and custom extensions that need to validate expenditure types, resolve organization or job names, or determine the latest PA/GL date and period for an expenditure item. Functions declared with RESTRICT_REFERENCES (WNDS) can be referenced within SQL statements, which is useful for embedding name lookups or validation results directly in a query. Custom code should treat these routines as internal utilities: they carry no user-facing promise of stability, and callers should rely only on documented behavior. When building custom validation, CHECK_EXP_TYPE_SYS_LINK_COMBO and the related check routines provide the standard mechanism for confirming expenditure type and system linkage consistency before insert or update.