Search Results c_unit

Overview

APPS.PER_PERRPRBD_XMLP_PKG is a generated Oracle Reports PL/SQL library package body associated with the Oracle E-Business Suite HRMS budget reporting family. The suffix _XMLP_PKG identifies it as the packaged program unit produced by Oracle Reports XML Publisher (BI Publisher) integration, containing helper functions referenced by report-level formula columns, user parameters, and format triggers. The report designation PER_PERRPRBD corresponds to a position, budget, or compensation budget report driven by a user-selected budget definition and budget version over a defined time period range.

The package does not expose public business APIs. All documented entry points are invoked by the Oracle Reports runtime engine during report execution, or by other PL/SQL constructs embedded within the same report definition. Its central role is to resolve descriptive attributes — budget name, budget version, business group name, time period ranges, and actual-versus-budget values — so that the report layout can render human-readable labels rather than primary key identifiers.

Key Procedures and Functions

The package exposes eighteen documented program units, most of which are report formula or summary columns paired with their supporting lookup functions.

• BEFOREREPORT — Fires once at report initialisation. It populates the package-level global variables C_UNIT, C_BUSINESS_GROUP_NAME, C_BUDGET_NAME, C_BUDGET_VERSION, C_START_PERIOD_NAME, C_END_PERIOD_NAME, and C_REPORT_SUBTITLE by calling the lookup functions described below.
• C_START_VALUEFORMULA — A formula column that invokes GET_ACTUALS and returns the starting actual value, simultaneously setting the C_END_VALUE, C_AMOUNT, and C_PERCENTAGE globals.
• AFTERREPORT — Terminal report hook, typically used for cleanup or signalling completion.
• C_END_VALUE_P, C_AMOUNT_P, C_PERCENTAGE_P — Placeholder (format trigger) functions that expose the corresponding global variables set during BEFOREREPORT or C_START_VALUEFORMULA.
• C_BUSINESS_GROUP_NAME_P, C_REPORT_SUBTITLE_P, C_BUDGET_NAME_P, C_BUDGET_VERSION_P, C_START_PERIOD_NAME_P, C_END_PERIOD_NAME_P, C_UNIT_P — Placeholder functions that surface each initialised global variable for use in the report layout.
• GET_BUDGET — Resolves a budget identifier into its budget name, using the P_BUDGET_ID parameter.
• GET_BUDGET_VERSION — Resolves the combination of P_BUDGET_ID and P_BUDGET_VERSION_ID into the descriptive budget version name displayed in the report header and column labels. This is the function most closely associated with the search term “get_budget_version”.
• GET_TIME_PERIOD — Returns the period name together with its start and end dates for a given time period identifier.
• GET_BUSINESS_GROUP — Returns the business group name for P_BUSINESS_GROUP_ID.
• GET_ACTUALS — Computes actual values, starting value, ending value, amount, and percentage for a given organisation, job, position, grade, and date range, comparing them against the supplied budget value.

Tables Accessed

The package reads from the APPS synonym PER_BUDGETS, which stores budget definitions for the HRMS budget hierarchy. In BEFOREREPORT the query on PER_BUDGETS retrieves the UNIT column into V_UNIT for the given BUDGET_ID, with a NO_DATA_FOUND handler that leaves the value null. Additional lookups executed by GET_BUDGET, GET_BUDGET_VERSION, GET_TIME_PERIOD, GET_BUSINESS_GROUP, and GET_ACTUALS read from the standard HRMS time period, business group, and budget version views referenced by those functions. No DML is performed; the package is strictly read-only.

Usage Notes

PER_PERRPRBD_XMLP_PKG is invoked exclusively by the Oracle Reports runtime when the associated budget report is executed, typically launched from a concurrent program or the HRMS budget form. The documented header indicates version 120.1 with a 2007 copyright date and noship flag, meaning the file is compiled into the APPS schema as part of the standard product installation rather than shipped as a separately patchable object. Because the package is referenced by zero other packages, it has no downstream dependency in ETRM; custom extensions should not call these functions directly, since their signatures are tied to the report parameter set and may change between release levels. For custom reporting on budget versions, the underlying data dictionary views and PER_BUDGETS table should be queried directly rather than invoking GET_BUDGET_VERSION.