Search Results get_period_amt

Overview

PA_PAXMGPSD_XMLP_PKG is an Oracle E-Business Suite XML Publisher (BI Publisher) report package owned by APPS. It implements the server-side data preparation logic for the Project Management report identified by the module prefix PA and the report short name PAXMGPSD. In release 12.1.1 and 12.2.2, packages of this naming convention are generated when a concurrent program is defined against a BI Publisher template; the package body supplies the PL/SQL entry points that the Oracle Reports or XML Publisher runtime invokes before the report layout is rendered. The header comment ("$Header: PAXMGPSDB.pls 120.2 2008/01/03 ... krreddy noship $") confirms its origin as a seeded, non-shippable report package.

Functionally, the package gathers project budgeting and period-based actual versus budget data. It resolves reporting context (organization, project manager, project number and name) and then computes the period and amount values that appear in the report output. The API classification is OTHER, reflecting that this is a report support package rather than a public business API. It is not referenced by any other package, so its consumers are limited to the reporting runtime and any custom code that explicitly calls it.

Key Procedures and Functions

The package exposes thirty-two documented procedures and functions. The most significant are:

• GET_COVER_PAGE_VALUES – Initializes cover page substitution values for the report layout.
• BEFOREREPORT – The primary before-report trigger. It captures the concurrent request ID via FND_GLOBAL, reads the PA_DEBUG_MODE profile option, and populates the organization name, project manager, project number, and project name global variables. It chains to GET_COMPANY_NAME and NO_DATA_FOUND_FUNC and raises INIT_FAILURE when initialization cannot complete.
• GET_COMPANY_NAME and NO_DATA_FOUND_FUNC – Helper validation and lookup routines used during initialization.
• GET_PERIOD, PERIOD_NAMEFORMULA, GET_PERIOD_AMT, and GET_PERIOD_AMT_SUM – Period resolution and amount calculation logic. GET_PERIOD_AMT returns the amount associated with a period and is the object users most commonly search for; GET_PERIOD_AMT_SUM returns the corresponding aggregate.
• UNBILLED_RECEIVABLESFORMULA, UNEARNED_REVENUEFORMULA, UNBILLED_RETNFORMULA – Named formula functions that compute report columns for unbilled receivables, unearned revenue, and related retention balances.
• C_PROJECT_ACTUAL_COSTFORMULA, C_ACT_PER_REVFORMULA, C_ACT_PER_COSTFORMULA, C_ACT_PER_REV_SUMFORMULA, C_ACT_PER_COST_SUMFORMULA, CF_CURRENCY_CODEFORMULA – Column-level formula functions for actual cost and revenue comparisons and currency code display.
• GET_RSRC_NAME_DISP – Resolves the resource name display value.
• AFTERREPORT and AFTERPFORM – Post-report and post-form triggers used to release runtime state and finalize output.

Tables Accessed

The package reads from four APPS synonyms:

• PA_PROJECTS – Source of the project number (SEGMENT1) and project name used to populate the report header.
• HR_ORGANIZATION_UNITS – Resolves the organization name from ORG_ID for the reporting context.
• PA_PERIODS – Supplies period definitions used by GET_PERIOD and the period amount functions.
• PA_BUDGET_TYPES – Provides budget type codes and descriptions for cost and revenue budget columns.
• PA_IMPLEMENTATIONS – Used to validate the installed Project Accounting configuration.

Note that PER_PEOPLE_F is also queried in BEFOREREPORT to resolve the project manager's full name; the ETRM table list emphasizes the PA-schema objects.

Usage Notes

PA_PAXMGPSD_XMLP_PKG is invoked by the concurrent program associated with the PAXMGPSD report. The Oracle XML Publisher engine calls BEFOREREPORT before generating output, the *FORMULA functions during layout evaluation, and AFTERREPORT on completion. Because the package is not referenced by any other package, direct dependencies are limited to the reporting runtime and to custom extensions that explicitly name it.

Customizations should avoid modifying the seeded package body; the standard approach is to copy the report definition and template, or to extend behavior through a custom package. When troubleshooting, confirm that the concurrent request ID and PA_DEBUG_MODE profile are available, since BEFOREREPORT depends on both. The "noship" designation in the header indicates the package is a seeded report artifact rather than a shippable product API, so it may change between patch levels without a formal compatibility guarantee.