Search Results update_reporting_lines_frombl




Overview

PA_FP_PJI_INTG_PKG is an Oracle Projects integration package responsible for synchronizing Project Journal Inquiry (PJI) reporting data whenever forecast or budget lines in Oracle Projects are created, updated, or deleted. The package header identifies it as the main API invoked from the calculate and budget generation processes to maintain the reporting PJI data derived from budget line activity. In Oracle EBS 12.1.1 and 12.2.2, the package is owned by APPS and classified under the "OTHER" API category, meaning it is an internal integration utility rather than a public application programming interface intended for general customer use.

The business problem addressed by this package is the need to keep the Project Journal Inquiry extraction structure (external planning lines) consistent with the transactional budget data held in Oracle Projects. Because budget lines change frequently during calculate and budget generation cycles, the PJI reporting tables must be refreshed in step; this package performs that refresh while respecting rejection-code validation rules on the underlying budget lines.

Key Procedures and Functions

  • UPDATE_REPORTING_LINES — The primary documented procedure, invoked from calculate and budget generation to update reporting PJI data when budget lines are created, updated, or deleted. It accepts a calling-module indicator (with a default of CALCULATE_API), an activity code of UPDATE or DELETE, and budget line identification, date, currency, and amount parameters spanning transaction, project, and project-functional currency. For UPDATE, all amount and currency columns must be supplied; for DELETE, negative budget-line amounts are selected from the database and any passed amounts are ignored. Standard EBS message-data, message-count, and return-status out parameters are returned to the caller.
  • BLK_UPDATE_REPORTING_LINES — A bulk-processing variant of the reporting-line update. The header commentary states that this API was created for bulk process of data, and that all parameters must be passed, since passing null or incomplete parameters will result in an error. The calling API is expected to initialize its input structures before invocation.
  • UPDATE_REPORTING_LINES_FROMBL — A documented procedure that drives the reporting-line update from budget-line sourced data, supporting the integration flow in which budget line records are the originating input.

No parameter lists are reproduced here beyond those documented; the package header explicitly warns that parameters must be fully populated and that a record must exist in PA_RESOURCE_ASSIGNMENTS for the passed resource assignment identifier before calling the update API.

Tables Accessed

The package references the following tables through APPS synonyms. PA_BUDGET_LINES and PA_BUDGET_VERSIONS supply and validate the budget line and version context. PA_PROJECTS_ALL provides project-level attributes, while PA_PROJ_FP_OPTIONS supplies forecast planning options that govern how reporting data is derived. PA_RESOURCE_ASSIGNMENTS is required for resource assignment validation. PJI_FM_EXTR_PLAN_LINES is the primary target, holding the Project Journal Inquiry external planning line data that the package maintains. Utility references include DBMS_UTILITY for message stack handling, DUAL for single-row queries, and PLITBLM for PL/SQL-supplied message text.

Usage Notes

PA_FP_PJI_INTG_PKG is invoked indirectly by Oracle Projects calculate and budget generation processes rather than by end users. The p_calling_module parameter defaults to CALCULATE_API, confirming that the calculate API is the principal caller. The package is also referenced by two other packages in the EBS codebase. Before calling the update procedure, callers must ensure that no rejection codes are stamped on the affected budget lines and that a corresponding resource assignment record exists. Custom code should treat this package as internal, inheriting Oracle's upgrade behavior, and should rely on the documented bulk procedure only when complete parameter sets are available.