Search Results get_act_to_period

Overview

PA_FP_GEN_FCST_PG_PKG is an Oracle Projects PL/SQL package in the APPS schema that supports the forecast generation subsystem of Oracle Project Management and Oracle Project Billing. Its name reflects its role as the packaging layer ("PG") for forecast generation ("GEN_FCST") within Oracle Projects financial planning ("PA_FP"). The package exposes a set of query and validation routines that resolve the version-level attributes required before a forecast or budget version can be generated, copied, or recalculated.

In Oracle EBS 12.1.1 and 12.2.2, forecasts and budget versions are stored in PA_BUDGET_VERSIONS, and generation behaviour is governed by options held in PA_PROJ_FP_OPTIONS. This package serves as the authoritative access point for those option and version attributes. Because many of the functions accept P_BUDGET_VERSION_ID, the package is directly relevant to callers that must determine, for a specific version, the actuals period range, the estimate-to-complete (ETC) period range, the treatment of unspent amounts, and the version type. The package also implements the validation logic that guards these operations, raising or reporting errors before generation proceeds.

Key Procedures and Functions

The documented routines fall into three categories: attribute getters, version detail access, and validations.

• GET_REV_GEN_METHOD — Returns the revenue generation method configured for a project, derived from PA_PROJ_FP_OPTIONS.
• GET_ACTUALS_THRU_PERIOD_DTLS — Returns period detail describing how far actuals are considered, based on a budget version and a context value.
• GET_ACT_FRM_PERIOD / GET_ACT_TO_PERIOD — Return the from and to periods bounding the actuals range for a given budget version.
• GET_ETC_FRM_PERIOD / GET_ETC_TO_PERIOD — Return the from and to periods bounding the ETC range for a given budget version.
• GET_UNSPENT_AMT_PERIOD — Returns the period associated with unspent amount handling for the version.
• GET_VERSION_DETAILS — Returns the version type for a budget version through an OUT parameter, together with standard return status, message count, and message data outputs.
• UPD_VER_DTLS_AND_GEN_AMT — Updates version details and generates amounts, honouring flags for unspent amounts, change documents, open commitments, and billing events.
• VALIDATE_PERIODS — Validates the period ranges associated with the version.
• VALIDATE_PA_GL_PERIODS — Validates that the relevant Oracle Projects and General Ledger periods are open and consistent.
• VALIDATE_PLAN_TYPE_OR_VERSION — Validates the plan type or version supplied by the caller.
• VALIDATION_FOR_COPY_ETC_FLAG — Validates whether the copy ETC flag may be applied for the version.

Tables Accessed

The package reads and writes against the following documented tables and synonyms:

• PA_BUDGET_VERSIONS — The primary source of version type and version-level attributes keyed by BUDGET_VERSION_ID.
• PA_PROJ_FP_OPTIONS — Supplies forecast generation options such as unspent amount, change document, open commitment, and billing event flags.
• PA_PROJECTS_ALL and PA_TASKS — Provide project and task context for the version.
• PA_BUDGET_LINES and PA_PROJ_ELEM_VER_STRUCTURE — Supply the budget line and structure detail required during version detail updates and amount generation.
• PA_PERIODS_ALL and GL_PERIOD_STATUSES — Used to validate Projects and General Ledger period status.
• PA_RESOURCE_ASSIGNMENTS and PA_RESOURCE_ASGN_CURR_TMP — Provide resource assignment data, including the temporary working table used during processing.
• FND_NEW_MESSAGES and PLITBLM — Used for message retrieval and PL/SQL table handling.

Usage Notes

PA_FP_GEN_FCST_PG_PKG is not an end-user interface object. It is invoked programmatically by Oracle Projects forms, by forecast and budget generation concurrent programs, and by other Oracle Projects packages. The ETRM metadata records that it is referenced by twelve other packages, confirming its role as a shared utility layer within the financial planning code family. Customizations and extensions that need to determine the actuals or ETC period boundaries for a budget version, or that must validate periods and plan types before generation, are the typical callers.

Because the primary entry points are keyed on P_BUDGET_VERSION_ID, a correct and committed version record in PA_BUDGET_VERSIONS is a prerequisite for every function and procedure in the package. Callers should also ensure the referenced project has forecast options defined in PA_PROJ_FP_OPTIONS, since several getters and the update routine depend on those option flags. The OUT-parameter signatures use NOCOPY for performance, and callers must check the returned status and message outputs rather than relying on exceptions alone. As with all Oracle Projects APIs, the package should be invoked within a properly initialised Oracle EBS session with the correct MO operating unit and user context set.