Search Results get_pa_date

Overview

PA_UTILS2 is a shared Oracle Projects utility package in the APPS schema that centralizes date derivation, period-name resolution, project status interrogation, and archive/purge support logic used across the Oracle E-Business Suite Projects family. In Oracle EBS 12.1.1 and 12.2.2 it functions as a common service layer: rather than duplicating PA date and GL date/period logic in every transaction package, dependent modules call PA_UTILS2 to obtain consistent results. Its scope is indicated by the fact that it is referenced by 41 other packages, and it is classified as API classification OTHER rather than as a public, externally supported API.

The package header declares a substantial set of package-level global variables used for two distinct purposes: archive/purge commit sizing and multi-reporting-currency (MRC) row counting (ARPUR_Commit_Size, ARPUR_MRC_Commit_Size, MRC_ROW_COUNT), and caching of PA dates and receiver PA dates for cost distribution lines. The caching variables follow an explicit Provider/Receiver naming convention (g_prvdr_org_id, g_p_earliest_pa_start_date, g_p_earliest_pa_end_date, g_p_earliest_pa_period_name, g_prvdr_pa_date, g_prvdr_pa_period_name, and the corresponding g_recvr_* set). Caching these values across calls reduces repeated queries against PA_COST_DISTRIBUTION_LINES_ALL during cost distribution processing.

Key Procedures and Functions

The package exposes 44 documented procedures and functions. The most directly relevant to the search term get_pa_date is GET_PA_DATE, which returns the PA date used for cost distribution processing, and its companion GET_RECVR_PA_DATE, which returns the corresponding receiver-side PA date. Both leverage the cached global variables described above, allowing a caller to obtain a previously established PA date without re-querying the distribution lines.

Date and period resolution is further served by GET_GL_DT_PERIOD, which derives the GL date and corresponding period, GET_PERIOD_NAME, which resolves a period name, and PA_PERIOD_NAME_PROFILE, which returns period-name profile information. Collector and transaction-related helpers include GETPRODUCTRELEASE, GETLABORCOSTMULTIPLIER, and GETPRJORGID.

Status and validation functions form a second major group. ISPROJECTCLOSED determines whether a project is closed. ISPROJECTINPURGESTATUS tests the purge status of a project, while ISDESTPURGED, ISSOURCEPURGED, ISPROJECTTXNSPURGED, ISPROJECTCAPITALPURGED, ISPROJECTBUDGETSPURGED, and ISPROJECTSUMMARYPURGED report whether specific project data subsets have been purged; ISACTIVEPRJTXNSPURGED covers purged active project transactions. CHECKEXPORG, CHECKSYSLINKFUNCACTIVE, and CHECKADJFLAG provide organizational, system-link function, and adjustment-flag validation checks.

Tables Accessed

PA_UTILS2 reads from and writes to core Oracle Projects tables through APPS synonyms. Cost distribution and expenditure data are accessed via PA_COST_DISTRIBUTION_LINES_ALL, PA_COST_DISTRIBUTION_LINES, PA_EXPENDITURE_ITEMS_ALL, and PA_DRAFT_REVENUES_ALL, supporting the PA date and receiver PA date derivation. Period and installation context comes from PA_PERIODS, PA_PERIODS_ALL, PA_IMPLEMENTATIONS_ALL, and FND_PRODUCT_GROUPS. Project definition and classification data are obtained from PA_PROJECTS_ALL, PA_PROJECT_TYPES_ALL, and PA_TRANSACTION_SOURCES. General Ledger integration uses GL_DATE_PERIOD_MAP, GL_PERIODS, and GL_PERIOD_STATUSES, while HR_ALL_ORGANIZATION_UNITS supplies organization information for the provider/receiver organization identifiers.

Usage Notes

PA_UTILS2 is an internal utility package, not a documented public API, so customizations should call it with care and expect signatures to remain stable only within a release. Typical invocation occurs from Oracle Projects forms, concurrent programs, and other Oracle Projects PL/SQL packages that need a consistent PA date, GL date/period, or project status check. Because caching globals persist for the duration of a database session, callers in long-running or multi-organization sessions should be aware that cached provider and receiver PA dates may not be refreshed unless the package state is reset.