Search Results get_sort_order

Overview

APPS.PAY_PAYSLIP_REPORT is a server-side PL/SQL package body within the Oracle E-Business Suite Payroll module. Its primary business function is to generate payslip reporting data for employees, extracting assignment-level payroll results and formatting them into output suitable for presentation as a payslip or related statutory/remittance report. The package operates against legislative parameters stored on payroll actions to determine which employees, consolidation sets, and date ranges are in scope for a given run, then assembles the qualifying assignment population and produces the report payload.

The package header comment referencing pygpsrep.pkb and the internal globals for parameter handling indicate this is the reporting engine behind payslip-style concurrent output. It is classified under ETRM as an OTHER API object rather than a public business API, meaning it is intended for internal use by the payroll reporting framework rather than for direct customer invocation. It is referenced by three other packages, confirming it participates in a larger reporting dependency chain.

Key Procedures and Functions

• GET_PARAMETER — Parses a token/value pair from a legislative parameter string, supporting both space-delimited and pipe-delimited formats, and optionally extracts a specific colon-separated segment from the recovered value. This is the low-level parsing utility underpinning get_sort_order searches and the broader parameter model.
• GET_SORT_ORDER — Retrieves the configured sort order applied to the payslip report output, controlling the sequence in which qualifying assignments or report lines are presented. This is the function most commonly targeted by the search term "get_sort_order," as administrators and developers reference it when tuning report ordering behavior.
• GET_ALL_PARAMETERS — Reads the full set of legislative parameters from PAY_PAYROLL_ACTIONS for a given payroll action, returning the payroll identifier, consolidation set identifier, start date, end date, and related driver values used to scope the run.
• XML_ASG — Constructs XML output for an individual assignment, providing the structured data representation used in payslip rendering and downstream XSL/BI Publisher formatting.
• QUALIFYING_PROC — Determines whether an assignment qualifies for inclusion in the payslip report based on the run's selection criteria, serving as the population filter before output is produced.

Tables Accessed

The package reads and writes across the core payroll and HR schema through APPS synonyms. PAY_PAYROLL_ACTIONS supplies the legislative parameters and action context; PAY_ASSIGNMENT_ACTIONS and PAY_TEMP_OBJECT_ACTIONS hold the assignment-level action and temporary run results. PER_ALL_ASSIGNMENTS_F, PER_ALL_PEOPLE_F, PER_ASSIGNMENT_STATUS_TYPES, and PER_PERSON_TYPES provide the employee, assignment, status, and person-type attributes required to build and filter the qualifying population, while PER_TIME_PERIODS supplies payroll period boundaries. HR_SOFT_CODING_KEYFLEX, HR_ASSIGNMENT_SET_AMENDMENTS, and PAY_ACTION_INFORMATION support payroll costing and action detail, and PAY_REPORT_CATEGORIES and PAY_REPORT_GROUPS define the report configuration. DUAL and DBMS_SQL are used for utility and dynamic SQL operations.

Usage Notes

PAY_PAYSLIP_REPORT is typically invoked through the Oracle Payroll payslip concurrent program rather than called directly. The concurrent request seeds the payroll action, and the package reads its parameters via GET_ALL_PARAMETERS, resolves sort order via GET_SORT_ORDER, filters assignments through QUALIFYING_PROC, formats each assignment via XML_ASG, and writes the payslip output. Because it is referenced by three other packages, customizations should treat it as an internal dependency: modifications risk breaking dependent reports. For "get_sort_order" specifically, the value is driven by report configuration stored in the PAY_REPORT_GROUPS and PAY_REPORT_CATEGORIES tables, so ordering changes are best made through setup rather than code.