Default Action Parameters for Payroll Extracts

Payroll process configuration groups provide sets of processing or action parameters, primarily related to logging and performance. Many delivered extracts, especially high-volume payroll extracts, include default, best-practice process configuration settings to optimize report performance.

Run the delivered payroll extracts directly without configuring some of the process configuration parameters for the report. For example, several high-volume extracts like the Payroll Activity Report has the process configuration parameter, Multithreaded XML Generation for Extracts (ORA_MULTITHREADED_XML) set to Y by default. You don't have to set the process configuration parameter either at the time of report submission or on the default process configuration group.

The best-practice process configuration settings are delivered as default values for each payroll extract. This table lists the action parameters that the delivered extracts include by default.

Parameter	Parameter Name	Default Value	Reports
Name of Extract Structure Block	EXTRACT_STRUCTURE_BLOCK	Global Payroll Register Extract Structure Block	Payroll Register Report Payroll Register Report for the Latest Process
Use Sub-set of Archive Extract Structure For Reports	USE_EXTRACT_STRUCTURE	Y	Payroll Register Report Payroll Register Report for the Latest Process
Suppression of Null Values	WRITE_NULL_VALUES	N	Payroll Activity Report Payroll Activity Report for the Latest Process Periodic Payroll Activity Report Statutory Deduction Register Statutory Deduction Register for the Latest Process Periodic Statutory Deduction Register Payroll Costing Results
Multithreaded XML Generation for Extracts	ORA_MULTITHREADED_XML	Y	Payroll Activity Report Payroll Activity Report for the Latest Process Periodic Payroll Activity Report Statutory Deduction Register Statutory Deduction Register for the Latest Process Periodic Statutory Deduction Register Payroll Costing Results
Skip BI server for online payslip	ORA_PAYSLIP_SKIP_BI_SERVER	Y	Payslip
Specifies the maximum number of payroll relationship actions per XML file	ORA_PAY_XML_SPLIT_CNT	N Disabled by default Note: This feature does not work by default. You must explicitly configure the required action parameters.	Payroll Deduction Report Costing Results Report

The delivered extracts use these default settings only if you haven't used your own values for these process configuration parameters.

Consider the following while using the action parameters for the delivered payroll extracts:

It is recommended that you use the default settings defined for the extract and don't set your own values for these parameters. Therefore, if you have configured an enterprise-level process configuration group with a different value for any of these parameters, delete them from the group and override them only on the extracts that need the override, individually.
If you have already copied the delivered extracts, you still need to use the process configuration group parameter on the report, unless you make a new copy of the delivered extract that now includes these default settings.
For user-defined extracts, you can set your own default settings as hidden extract and flow parameters, just like the delivered extracts. Alternatively or additionally, you could add a process configuration group parameter on the report to allow a different setting on each report submission.
Change the process configuration parameter values in the default process configuration group only if you're using the same values across payroll extracts, including those extracts that have their own default settings.

XML Data Split and Parallel Processing

The Global Payroll Deduction Report and Costing Results Report are enhanced to support large employee populations by enabling XML data split and parallel processing before BI Publisher execution.

The enhancement allows reports to successfully run even when the generated XML data size exceeds the BI Publisher memory guard limit (currently approximately 10 GB), improving scalability and performance.

Splits large report data into multiple XML outputs before BI processing
Executes each split as a separate BI Publisher job
Enables parallel processing of large datasets
Prevents BI job failures caused by excessive XML size
XML split is independent of BI Publisher XML chunking and both can be enabled together.
Consolidated output files are not available for these reports when XML Split is used, the output files generated by XML split are not merged.
This option isn't recommended for small populations where split overhead may exceed performance benefits.