Search Results cp_sort_description2

Overview

PSP_PSPENEXR_XMLP_PKG is the generated PL/SQL package body that backs the Oracle E-Business Suite XML Publisher (BI Publisher) concurrent program used by the Oracle Grants/Projects suite to extract and report on expenditure exceptions and interface activity. The package follows the standard XMLP report package pattern, in which Oracle Reports-compatible user exits are exposed within a package whose before-report and after-report entry points are invoked automatically by the XML Publisher engine when the report is run. It resides in the APPS schema and is classified as an OTHER API, meaning it is not intended as a callable business API but rather as internal infrastructure for report execution.

The package's primary responsibility is to assemble the dynamic SELECT clause that drives the expenditure exception extract. Its central logic branches on the P_SORT_BY parameter, defaulting P_SORT_BY to 'O' when no value is supplied, and concatenates different column-ordering fragments into P_ACTUAL_SELECT. This mechanism allows a single SQL statement to present columns in different orders depending on the user's chosen sort criterion, while keeping the numeric column positions aligned for the report layout. The snippet references the header identifier "$Header: PSPENEXRB.pls 120.6 2007/10/29", indicating the package has been stable since the 12.1 era and remains compatible with 12.1.1 and 12.2.2.

Key Procedures and Functions

• BEFOREREPORT — Executed before report output is generated. It initialises P_SORT_BY defaults, resolves application IDs used by the extract, and builds the P_ACTUAL_SELECT string that injects sort-dependent columns such as organization_id, gl_code_combination_id, project_id, task_id, award_id, and expenditure_type.
• AFTERREPORT — Runs after report generation completes, used for cleanup and resetting package-level state.
• CF_ELEMENT_NAMEFORMULA — A group formula that returns the element name for each extracted row by looking up PAY_ELEMENT_TYPES_F.
• CF_SORT_DESCRIPTION1FORMULA — Returns the descriptive text associated with the first sort category.
• CF_SORT_BY_HEADERFORMULA — Produces the header label corresponding to the selected P_SORT_BY value.
• CF_PAYROLL_NAMEFORMULA — Resolves the payroll name for the payroll_id column in the output.
• CF_PERSON_NAMEFORMULA — Derives the person's display name from person_id.
• CF_ASSIGNMENT_NUMBERFORMULA — Returns the assignment number for the assignment_id column.
• CP_SORT_DESCRIPTION2_P — A concurrent-program-side data callback that supplies the second-level sort description; this is the object most closely associated with the user's search term "cp_sort_description2".
• CP_SORT_BY_DETAIL_P — Supplies the detail-level sort-by information used to order the final result set.

Tables Accessed

• FND_APPLICATION — Read during BEFOREREPORT to resolve the APPLICATION_ID for the SQLGL and GMS application short names.
• PAY_ELEMENT_TYPES_F — Source of element name and classification details displayed on the exception report.
• PER_ALL_ASSIGNMENTS_F — Provides assignment attributes such as assignment_id and assignment number used by the person formatter functions.
• PER_ALL_PEOPLE_F — Provides person-level attributes (person_id, name) consumed by CF_PERSON_NAMEFORMULA.

Usage Notes

This package is not called by other PL/SQL packages (referenced by 0 other packages) and is invoked exclusively through the XML Publisher concurrent program that owns it. Administrators run the corresponding concurrent program from the Grants or Projects responsibility, selecting a sort option that populates P_SORT_BY. The report engine then invokes BEFOREREPORT, evaluates the CF_* group formulas per row, applies the CP_SORT_DESCRIPTION2_P and CP_SORT_BY_DETAIL_P data callbacks for ordering, and finally calls AFTERREPORT. Customisations should be limited to copies or diagnostic inspection, since modifying the seeded package body directly invalidates Oracle's support for the report; enhancements are more safely delivered through XML Publisher template modifications or by extending the underlying data model in a separate custom package.