Overview of Payroll Data Validation Report

Before you run payroll or any other statutory processes or reports, the required HR and payroll data setup must be complete for all your workers. Missing or noncompliant data can impact legal processes or reports.

The Payroll Data Validation Report provides details of missing or statutorily noncompliant data at the worker and organization level. Prior to running the payroll process or any other report, run the Payroll Data Validation Report. You can then take corrective action as necessary to complete the data setup and correct noncompliant data.

During the implementation phase, add the business rules and validation messages at the enterprise or legislative data group level. These validations are in addition to the country-specific validations that are predefined in the application.

Validation Levels

The data group you select when adding validation rules to the Data Validation Report determines the level of validation. For example, you might have a validation rule at the tax reporting unit level or at the person details level. When adding a validation, you must ensure a database item exists for the attribute for which you're adding the validation.

Set Up Validation Rules

Use the delivered formula 'Global Attribute Mandatory Check' to set up validations to identify missing data. You add the validations to the Data Validation Report extract definition. Here's the summary of the required steps to set up the validation rules:

Identify a suitable short name for the attribute for which you want to add the validation, for example, ASG_JOB_CODE. Prefix it with CST to mean user-defined. Therefore, the short name should be CST_ASG_JOB_CODE.
Set up a lookup code to control the validation. For mandatory validations, that you set up using the delivered formula, set up the lookup code as a short name suffixed by >MC. For example, CST_ASG_JOB_CODE>MC.
Based on the level at which you need the validation, you must create the records and data elements in the appropriate data group. Identify the relevant data group to add the validation and create a record in the group. For example, add assignment level validations to the Assignment Data Group.

Note: A database item must exist for the attribute for which you're adding the validation.
Add the validation and create the extract definition attributes.
Generate and compile the formula at the report record.
Run the appropriate Payroll Data Validation Report to include the validations.

Control the Validations

Use the delivered ORA_HRX_GLB_VALIDATION_OBJECTS lookup type to set up a lookup code that you can use to control the validation. For example, you can use this lookup code to add multiple country tags to a validation. Alternately, if the validation is no more valid for the country, remove the previously added country tag from the lookup code.

Note: If you don't add a country tag, the application doesn't trigger any validation.

Validation Types

The validations can be simple or complex.

The application triggers simple validations if you haven't provided a value for an attribute required for a report or a process. For example, the Tax Reporting Registration Number is missing at the organization level or the National Identifier value is missing for a worker. You can create a simple validation by using the delivered formula 'Global Attribute Mandatory Check' and the appropriate database item group.

The application triggers complex validations when there's more than one attribute included in the validation. For example, a value is missing for a National Identifier Type pertaining to a worker.

For coding complex validations, Oracle recommends that you use data elements of type Rule with a user-defined Rule Formula to perform the validation. You must deliver these data elements in a record of type Formula.

User-Defined Rule Formula

For coding complex validations, Oracle recommends that you use extract attributes of type Rule with a user-defined Rule Formula to perform the validation. Consider the following for coding user-defined Rule Formula:

Check if the formula is of type Extract Rule.
Check that the lookup code exists for the short code of the data element, and is enabled for the legislation code, for which the report is run.
Check if the formula is associated with the correct data element. Since this is a user-defined formula, check and run only if short code matches.
Perform the validation to return validation message text or return a NULL value. The message text should be fewer than 240 characters or the application considers only the first 240 characters of the message.

Data Security

By default the report is submitted through an elevated user that has full data access and is secured through the list of values on the report parameters. However, you can configure the Data Validation Report to run based on the profile of the user who submits the report. For example, if a user has access to only employees within a specific payroll or department, you can configure the report to check data only for those employees.