Search Results resubmit_concurrent_process




Overview
Explore in AI Chat

Overview

PA_FIN_PLAN_MAINT_VER_GLOBAL is an Oracle EBS Projects (PA) package body owned by APPS that exposes a set of public APIs supporting the Org Forecast: Maintain Versions page. The package encapsulates version lifecycle operations for financial plans, providing server-side logic for creating working copies of plan versions, initializing the maintenance page, and resubmitting concurrent processes associated with version processing. It also manages user-level security privileges governing whether a given user may submit, rework, or baseline a financial plan version.

The package relies on package-level global variables to carry session context — the current project identifier (G_PROJECT_ID), financial plan type identifier (G_FIN_PLAN_TYPE_ID), and login person identifier (G_LOGIN_PERSON_ID) — together with three security flags (G_SECURITY_S, G_SECURITY_R, G_SECURITY_B) that represent the submit, rework, and baseline privileges respectively. These globals are populated during page initialization and consumed by later calls, giving the package a stateful, page-scoped behavior typical of Oracle Forms–driven Projects functionality.

An internal debug flag, P_PA_DEBUG_MODE, is derived from the PA_DEBUG_MODE profile option at package instantiation, allowing diagnostic output to be enabled through standard profile configuration rather than code changes.

Key Procedures and Functions

  • GET_PROJECT_ID — Returns the project identifier held in the package global, allowing callers to retrieve the project context established during initialization.
  • GET_FIN_PLAN_TYPE_ID — Returns the financial plan type identifier from the package global, identifying which plan type the current maintenance session operates against.
  • GET_LOGIN_PERSON_ID — Returns the person identifier of the logged-in user, used for security and ownership evaluation.
  • GET_FIN_PLAN_SECURITY — Accepts a security type indicator (Submit, Rework, or Baseline) and returns the corresponding security value stored in the package globals. This was introduced under bug 5629469 to expose version-level privileges to the calling page.
  • MAINTAIN_VERSIONS_INIT — Initializes the Maintain Versions page, populating the package globals and establishing the context required by subsequent operations.
  • CREATE_WORKING_COPY — Creates a working copy of a financial plan version, enabling users to modify plan data without affecting the baselined or submitted version.
  • RESUBMIT_CONCURRENT_PROCESS — Resubmits a concurrent process associated with a financial plan version. This procedure is the object most commonly sought by users searching on "resubmit_concurrent_process," as it provides the programmatic entry point for re-triggering failed or interrupted version-processing requests.

Tables Accessed

  • PA_BUDGET_VERSIONS — Stores budget and forecast version definitions; read and updated as versions are created, submitted, reworked, or baselined.
  • PA_FIN_PLAN_TYPES_B and PA_FIN_PLAN_TYPES_TL — Provide the base and translated definitions of financial plan types, validating the plan type context for the maintenance page.
  • PA_PROJECTS_ALL — Supplies project header information used to establish and validate the project context.
  • PA_PROJECT_TYPES_ALL — Used to determine project type attributes that influence plan version behavior.
  • PA_PROJ_FP_OPTIONS — Holds project-level financial plan options that govern version maintenance rules and available actions.

Usage Notes

The package is referenced by six other packages within the EBS schema, indicating it functions as a shared service layer rather than a standalone utility. It is typically invoked from the Org Forecast Maintain Versions page, where initialization is performed first, followed by version operations and, when necessary, resubmission of concurrent requests. The RESUBMIT_CONCURRENT_PROCESS procedure is relevant in scenarios where a version submission or baseline request has failed, been cancelled, or terminated abnormally; calling code uses it to re-enqueue the request without recreating the version. The procedures are also callable from custom PL/SQL, provided the caller first establishes project, plan type, and login person context and respects the security flags returned by GET_FIN_PLAN_SECURITY. Standard EBS error-handling conventions apply, with OUT parameters for return status, message count, and message data.