Search Results get_project_info

Overview

PA_ACCUM_UTILS is a public PL/SQL utility package in the Oracle EBS Projects (PA) application, owned by APPS and declared with AUTHID CURRENT_USER. It provides the core programmatic services that support the Project Accumulation (PA_ACCUM) feature set in EBS 12.1.1 and 12.2.2. Project Accumulation maintains summarized actual, commitment, and budget balances for a project, task, and resource combination across PA and GL periods, and PA_ACCUM_UTILS supplies the shared helper routines that determine when to accumulate, which period is current, and how header and detail records in the PA_PROJECT_ACCUM_* tables are established and maintained. Its responsibilities include verifying the existence of project-level accumulation records, deriving the accumulation option (PA period versus GL period) from PA_IMPLEMENTATIONS, resolving current and prior period information, and ensuring the header/detail hierarchy is consistent. Because it is broadly referenced—nineteen other packages call into it—it functions as an infrastructure layer rather than an end-user-facing API.

Key Procedures and Functions

The package exposes roughly twenty-four documented procedures and functions. Grouped by purpose, they are:

• Period resolution: GET_CURRENT_PA_PERIOD and GET_CURRENT_GL_PERIOD return the active PA and GL periods; GET_CURRENT_PERIOD_INFO and GET_PA_PERIOD_INFO return the full set of current, previous, and year-related period attributes used in accumulation logic; SET_CURRENT_PERIOD_INFO stores that context; GET_PERIOD_YEAR_INFO and GET_FIRST_ACCUM_PERIOD support period and year derivation; and GET_CHECK_REPORTING_END_DATE / SET_CHECK_REPORTING_END_DATE manage the reporting-end-date flag.
• Header and detail maintenance: PROJ_LEVEL_RECORD verifies the existence of the project-level accumulation record (task ID 0, resource list member ID 0) and creates a PA_PROJECT_ACCUM_HEADERS row if absent, returning the Project_Accum_Id; CHECK_ACTUALS_DETAILS, CHECK_CMT_DETAILS, and CHECK_BUDGET_DETAILS verify and create the corresponding detail rows for all tasks in the hierarchy; UPDATE_PROJ_ACCUM_HEADER maintains header data; and CHECK_TASKS_RESTRUCTURED_FLAG detects task restructuring so accumulation remains aligned.
• Configuration and project context: GET_IMPL_OPTION reports whether accumulation is driven by PA_PERIOD or GL_PERIOD as defined in PA_IMPLEMENTATIONS; GET_CONFIG_OPTION retrieves related configuration values; GET_PROJECT_INFO returns project attributes; and GET_EXISTING_HIGHER_TASKS identifies parent tasks in the hierarchy.
• Specialized calculation: GET_SPREAD_AMOUNT_VAL—the routine most often sought by developers—supports the calculation of spread amounts used when accumulating or reporting balances across periods.

Tables Accessed

The package reads and writes against several Projects and General Ledger tables. It queries and maintains PA_PROJECT_ACCUM_HEADERS and PA_PROJECT_ACCUM_HEADERS_S, along with the detail tables PA_PROJECT_ACCUM_ACTUALS, PA_PROJECT_ACCUM_BUDGETS, and PA_PROJECT_ACCUM_COMMITMENTS, which hold accumulated balances by project, task, and resource. Project and task hierarchy context comes from PA_PROJECTS, PA_TASKS, and PA_PROJECT_TYPES. Configuration and period definitions are drawn from PA_IMPLEMENTATIONS, PA_PERIODS, PA_TXN_ACCUM, PA_RESOURCE_ACCUM_DETAILS, PA_ACCUM_COLUMNS, and GL_PERIOD_STATUSES. DUAL is used for single-row context queries.

Usage Notes

PA_ACCUM_UTILS is invoked indirectly rather than directly by end users. It is called by accumulation processing, project summary generation, and the other Projects packages that reference it, and it executes within the standard EBS APPS schema with AUTHID CURRENT_USER and the usual MO: Operating Unit and MO: Security Profile considerations. Customizations should call its documented procedures rather than replicate accumulation logic, and any direct use should respect the period, implementation option, and header/detail preconditions enforced by PROJ_LEVEL_RECORD and the CHECK_* routines.