Results for “get_sort_order”
21 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PAY_PAYSLIP_REPORT is an Oracle Payroll PL/SQL package in the APPS schema that generates payslip output for employees processed through Oracle Payroll. In Oracle EBS 12.1.1 and 12.2.2, payslip generation is delivered primarily through a BI Publisher-based concurrent program, with the package supplying the underlying data extraction and formatting logic. The object is classified as OTHER in ETRM, indicating it is not a published public API but rather an internal supporting package called by report entry points and other payroll packages.
The package serves the business function of assembling payslip-level information — assignment details, person details, payroll action context, report grouping and category metadata, and time period attributes — and rendering it in a structured output suitable for printing, email delivery, or archival as an electronic payslip. Its status is VALID, confirming it is compiled and active in the documented environment.
Key Procedures and Functions
ETRM documents five procedures and functions within PAY_PAYSLIP_REPORT:
- GET_PARAMETER — Retrieves parameter values used to drive the payslip report run, supporting consumption of concurrent program or report definition parameters.
- GET_SORT_ORDER — Determines the sort ordering applied to payslip records, allowing the output to be sequenced according to report configuration.
- GET_ALL_PARAMETERS — Returns the complete set of parameters applicable to the payslip report, typically used to populate or validate the parameter list before processing.
- XML_ASG — Produces XML output at the assignment level, which is the core data payload consumed by the payslip layout template.
- QUALIFYING_PROC — A qualifying procedure used to filter or qualify assignments and records for inclusion in the payslip run, ensuring only eligible payroll actions and assignments are processed.
These routines collectively handle parameter resolution, record selection, ordering, and XML generation, forming the data pipeline behind the delivered payslip report.
Tables Accessed
The package reads from a defined set of payroll and HR tables, accessed through APPS synonyms:
- PER_ALL_ASSIGNMENTS_F and PER_ALL_PEOPLE_F — Source assignment and person records, providing the identity and employment context for each payslip.
- PER_ASSIGNMENT_STATUS_TYPES, PER_PERSON_TYPES, and PER_BUSINESS_GROUPS — Classification and eligibility data used to qualify records.
- PAY_PAYROLL_ACTIONS, PAY_ASSIGNMENT_ACTIONS, and PAY_ACTION_INFORMATION — Payroll run and action context, linking payslips to the payroll process that generated them.
- PAY_TEMP_OBJECT_ACTIONS, PAY_REPORT_CATEGORIES, PAY_REPORT_GROUPS, and PER_TIME_PERIODS — Reporting configuration, grouping, and period attributes.
- HR_SOFT_CODING_KEYFLEX, HR_ASSIGNMENT_SET_AMENDMENTS, and DUAL — Supporting lookups and utility access.
The package also references DBMS_SQL, indicating dynamic SQL is used for flexible data retrieval.
Usage Notes
PAY_PAYSLIP_REPORT is referenced by the APPS packages PAY_NO_PAYSLIP_REPORT, PAY_US_DEPOSIT_ADVICE_PKG, and PYCADAR_PKG, and is itself dependent on PAY_MAGTAPE_GENERIC. This dependency pattern reflects its role as a shared payslip engine reused by related report variants, including the no-payslip report, US deposit advice, and Canadian payroll reporting.
Typical invocation occurs indirectly through the delivered payslip concurrent program and its BI Publisher template, rather than through direct calls from forms. Customizations extending payslip content, altering selection logic via qualifying procedures, or reusing the XML extraction should treat the package as an internal implementation object, since it is classified as OTHER rather than as a supported public API. Any custom code should account for the dynamic SQL and the qualifying procedure logic to preserve correct record selection.
-
PACKAGE BODY: APPS.BOMPEXPL 12.1.1
-
PACKAGE BODY: APPS.BOMPEXPL 12.2.2