Search Results cf_refreshformula

Overview

PA_PARCPRJR_XMLP_PKG is the generated PL/SQL package specification that backs the Oracle Projects XML Publisher concurrent program report PA_PARCPRJR (internally referenced by the source file PARCPRJRS.pls). The package follows the standard Oracle Reports-to-XML-Publisher migration pattern in Oracle E-Business Suite, where a report is published through BI Publisher and its report-level logic — parameter defaults, data retrieval support, and formatting formulas — is encapsulated in a database package owned by APPS. The header comment indicates a build stamp of 120.1 dated 2008/04/09, consistent with a report package carried forward into the 12.1.1 and 12.2.2 code lines.

The business function of this package is to support reporting and validation around project resource and organization assignments. The public variables exposed at the top of the specification include organization selection (P_ORGANIZATION_ID, P_START_ORGANIZATION_ID, P_ORG_STR_VERSION_ID), employee number ranges (P_FROM_EMP_NUM, P_TO_EMP_NUM), chart of accounts (P_COA_ID), a refresh flag (P_REFRESH), and person type (P_PERSON_TYPE). This naming indicates the report is used to produce or refresh resource assignments by organization and person, and to display organization structure information as of a selected version. Because the user search term was "cf_refreshformula", the CF_REFRESHFORMULA function is the most relevant entry point: it drives the display and derivation of the refresh indicator used by the report layout.

Key Procedures and Functions

• BEFOREREPORT — The report-level initialization hook. It executes prior to data retrieval to set up report parameter state and any prerequisite processing.
• AFTERREPORT — The post-report cleanup and finalization hook, invoked after the report completes.
• CF_REFRESHFORMULA — A character formula function that returns the derived refresh value used by the report. This is directly relevant to the "cf_refreshformula" search.
• CF_ORGANIZATION_NAMEFORMULA — Returns the formatted organization name for report display.
• CF_SELECTION_OPTIONFORMULA — Returns the formatted selection option text used in the report output.
• CF_ORG_STR_VERSION_IDFORMULA — Returns the formatted organization structure version identifier.
• CF_START_ORG_IDFORMULA — Returns the formatted starting organization identifier.
• CF_PULL_TERM_RESFORMULA — Returns the formatted value controlling whether terminated resources are pulled into the report.
• CF_PERSON_TYPEFORMULA — Returns the formatted person type value.
• CP_NODATAFOUND_P, CP_COUNT_P — Accessors exposing the "No Data Found" message and row count state.
• CP_CHK_ORG_OR_EMP_P, CP_CHK_EMP_RANGE_P, CP_CHK_ORG_AND_EMP_RANGE_P, CP_CHK_SINGLE_ORG_P, CP_CHK_START_ORG_P — Validation accessors governing mutual-exclusivity and range checks between organization and employee parameters.

Tables Accessed

Documented table access is via APPS synonyms:

• FND_LOOKUP_VALUES — supplies lookup-driven values for report parameters and display.
• HR_ALL_ORGANIZATION_UNITS — the validated list of organizations used in selection.
• PA_RESOURCES and PA_RESOURCES_DENORM — the core project resource data and its denormalized reporting view.
• PER_ORGANIZATION_STRUCTURES and PER_ORG_STRUCTURE_VERSIONS — organization hierarchy and version context for the start-organization and structure-version parameters.
• DUAL — used for scalar derivations, consistent with the CF_*FORMULA functions.

Usage Notes

This package is not called directly by end users. It is invoked by the Oracle XML Publisher / BI Publisher runtime when the associated concurrent program executes, with BEFOREREPORT and AFTERREPORT firing at the report lifecycle boundaries and the CF_*FORMULA functions invoked by the layout to render derived values such as the refresh indicator. The package is referenced by no other database packages per the metadata. Report developers extending behavior for the "cf_refreshformula" path would review CF_REFRESHFORMULA in the corresponding body (PARCPRJRS.pll-derived package body), since the specification exposes only the signatures. Customizations should treat the package as a report artifact and follow Oracle's supported cloning conventions rather than editing the shipped specification in place.