Search Results plan_update

Overview

APPS.PJI_FM_XBS_ACCUM_MAINT is a public PL/SQL package belonging to the Oracle Projects (PJI) application module, focused on the maintenance of project financial plan and workplan accumulations. Its name reflects its role: managing the «XBS» (cross-business-entity) accumulation structures that back financial plans, budgets, and workplan versions within Oracle Projects. The package is defined with AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking user rather than its owner, which is significant for subledger-style installations and multi-org access.

The package serves as the operational engine behind the lifecycle events of financial plan versions — creation, update, deletion, baseline, origination, and copy — and behind the maintenance of project structures such as WBS, RBS, and smart slices. It is a foundational dependency in Oracle EBS 12.1.1 and 12.2.2, referenced by 21 other packages, which indicates it is invoked indirectly from multiple Projects flows rather than only through a dedicated UI.

Key Procedures and Functions

The 28 documented procedures group into several functional families:

• Plan lifecycle: PLAN_CREATE, PLAN_UPDATE, PLAN_UPDATE_PVT, PLAN_DELETE, PLAN_DELETE_PVT, PLAN_COPY_PVT, FINPLAN_COPY, PLAN_BASELINE, PLAN_BASELINE_PVT, PLAN_ORIGINAL, and PLAN_ORIGINAL_PVT manage the creation, modification, deletion, copying, baselining, and origination of financial plan versions.
• Accumulation and actuals: PLAN_UPDATE_ACT_ETC and PLAN_UPDATE_PVT_ACT_ETC handle the update of accumulated actuals and estimate-to-complete (ETC) values against plan and workplan versions.
• Structure maintenance: WBS_MAINT, PRG_CHANGE, RBS_PUSH, and RBS_DELETE maintain work breakdown structures, program changes, and resource breakdown structures.
• Smart slice management: DELETE_SMART_SLICE and MAINTAIN_SMART_SLICE provide for removal and upkeep of smart slice definitions in financial plans.
• Project summary: PROCESS_PROJ_SUM_CHANGES processes project summary changes triggered by plan or structure updates.

The user search term «plan_update» maps directly to PLAN_UPDATE, the public entry point that accepts a plan version identifier and returns a message code and return status. Its private counterpart, PLAN_UPDATE_PVT, performs the internal processing and returns a processing code. These are the routines most relevant to consumers seeking to refresh or recompute a plan version.

Tables Accessed

The package operates on a core set of Oracle Projects tables through APPS synonyms. PA_PROJECTS_ALL, PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, and PA_PROJ_ELEM_VER_STRUCTURE hold project, element, and structure version data. PA_PROJ_FP_OPTIONS, PA_PROJ_WORKPLAN_ATTR, and PA_PROJ_STRUCTURE_TYPES configure financial plan and workplan behavior and structure typing. PA_BUDGET_VERSIONS and PA_RBS_VERSIONS_B store budget and RBS version records, while PA_RESOURCE_LISTS_ALL_BG and PA_STRUCTURE_TYPES support resource list and structure type maintenance. PA_OBJECT_RELATIONSHIPS links plan and structure entities. Event logging is handled through PA_PJI_PROJ_EVENTS_LOG and PA_PJI_PROJ_EVENTS_LOG_S, and PJI_FM_EXTR_PLAN_LINES stores extracted plan line data.

Usage Notes

Because the package is classified as OTHER and is not a fully published open interface, it is typically invoked by Oracle Projects forms, concurrent programs, and internal API wrappers rather than by customer code directly. The 21 dependent packages confirm this pattern. The public PLAN_UPDATE, PLAN_CREATE, PLAN_DELETE, and PLAN_BASELINE procedures form the accessible surface, with PVT variants reserved for internal calls. Invocations should be wrapped in a standard consistency pattern: call the routine, check x_return_status for a value of FND_API.G_RET_STS_SUCCESS, and log x_msg_code or x_processing_code for diagnostics. Customizations should target the public procedures only and account for the AUTHID CURRENT_USER execution context, since privilege expectations differ from a definer-rights package.