To use absence tracking, you must first set up a user table to store default re-integration actions for each absence category you want to use. As a minimum you must set up one user table for the absence category of Sickness.

The re-integration actions you set up here are displayed in the Absence Tracking pages for absence records with the relevant absence category. Using the Absence Tracking pages you can use these actions and update them, add more actions to the absence record or delete the actions from the record.

Note: Only the default re-integration actions you set up for an absence category using the user tables appear for the absence records. Any actions you add, update or delete to an absence record using the Absence Tracking pages appear only for that record.

Set up the default re-integration actions user tables as follows:

Name each user table: NL_ABS_ACTION_(category code). The absence category code relates to the relevant lookup code in the Absence Category Lookup Type. For example, the category code for Sickness is 'S'.
Set the match type as Match and the key units of measure as Text.

Set up the following four columns and values:

Column Name	Required Values	Example Values
ROW_NUMBER	NA	This column uniquely identifies the ACTION. You can enter alpha and numercial values, for example 1, 1A, 1B etc.
ACTION	NA	This column describes the re-integration action, for example Progression Plan.
TIME_PERIOD	NA	This column describes the number of time units. For example, for the action Progression Plan, you set up a time period of 1 and a time unit of 'M' for months, this means you have one month to perform the action for the employee from the start of the absence record.
TIME_UNITS	'D' for Days, 'W' for Weeks, 'M' for Months	NA

Set up row labels for each row in the Exact field, and set up the order you want the rows to appear in the table using the Sequence field. The number of rows you set up determines the number of values you can enter.
For every date effective row you set up in the user table, you must also set up a date effective value for each column. This is to ensure that when you use the Absence Tracking pages on a date that is on or later than the effective dates set up, then the user table displays the default actions and their values.

Note: If you use the Absence Tracking pages on a date that is earlier than the effective dates set up in the user table, an error message displays to indicate that the user table is incorrectly set up.

See: User and Extensible Lookups, Oracle HRMS Configuring, Reporting, and System Administration Guide

See: Setting Up User Tables, Columns and Rows, Oracle HRMS Configuring, Reporting, and System Administration Guide

See: Tracking Absences

Step 3: Set Up Dutch Organizations for Social Insurance and Tax

You must set up your organizations correctly to enable you to:

Record the correct tax and social insurance information for your employers and employees.
Process the tax deductions and social insurance contributions.

See: Setting up Tax, Social Insurance, and Private Health Insurance Organizations

See: Setting Up Social Insurance Days

Step 4: Set up Statutory Deductions

If you are using Oracle Payroll, you must set up your statutory tax and social insurance deductions.

See: Setting up Tax and Social Insurance Deductions

To enable flat rate taxation in Oracle Payroll, you must set up elements and balances related to flat rate tax.

See: Setting Up Flat Rate Taxation

Step 5: Set Up Pension Schemes

You can set up the pension schemes available to your employees. This enables you to process pension contributions in the payroll run. To review the functionality available, see: Savings and Retirement Overview. For the setup steps, see: Setting Up Pension and Savings Schemes

Step 6: Disable Full Name Formats Optional Step

You can disable full name formats that you do not wish to use in the User Types and Statuses window. The full name formats that you disable, do not appear in the Full Name Format field in the People window.

See: Disabling Full Name Formats

See: Entering Additional Personal Information (People Window)

Step 7: Set Up Information for the Wage Report Required Step

Some setup tasks are necessary before you can run the Dutch Wage Report.

See: Setting Up the Dutch Wage Report

Step 8: Link Predefined Elements Required Step

You must link the following predefined elements:

Labour Handicap Discount, which holds the calculated discount value for labor handicapped employees
Retro Labour Handicap Discount, which holds changes made retrospectively to the Labour Handicap Discount element

Note: You do not need to attach these elements to assignments eligible for labor handicap discount. The application checks for eligibility during SI processing and generates results for eligible elements. Ensure you link the elements for costing purposes.

You need to attach the predefined element, SI Override Days to assignments to enter override days manually. The application uses this information in case of the following:

For long-term unpaid leave
If an employee has more than three active assignments and a time gap exists between assignments, for example, the employee has one or more days between the payroll start date (or employee period of service start date if earlier than period start date) and payroll end date (or employee period of service end date if later than period start date) where no active assignment exists.

Note: You do not need to use this element if the assignments remain active throughout the payroll period and period of service.

Step 9: Set Up Information for Health and Disability Insurance Contributions Required Step

Some setup tasks are necessary before the payroll process can calculate health and disability insurance contributions.

See: Setting Up ZVW, WGA, IVA, and UFO Contributions

Step 10: Set Up First Day Report Required Step

You need to set up the first day report for enabling you to electronically send the employee information to tax authorities.

See: Setting Up the First Day Report

Step 11: Create a User Table for Each Dutch Business Group for Deriving Maximum SI Wage. Required Step

As the maximum SI wage is retrieved from a user defined table instead of deriving it from a global value, you must create a user table for each Dutch business group in the format given below and keep it updated:

Table : PAY_NL_MAXIMUM_SI_WAGE
Key Units of Measure : Text
Column Name : FREQUENCY
Exact : Day, Week, FourWeek, Month, Quarter, Year

You must ensure that a row is defined for each payroll frequency used in the business group and mandatorily specify day.

Step 12: Set up the Special and Non-tax Elements Required Step

For Savings Schemes, currently elements such as '% Standard Tax Adjustment' only feeds balance 'Standard Taxable Income'. You must ensure that the balance feed 'SI Income Standard Tax Adjustment' is also added. You must set up the Special and Non-tax elements similarly as shown below:

Element Name Like	Additional Balance feed effective from 1-Jan-2013	Add or Subtract
%Standard Tax Adjustment	SI Income Standard Tax Adjustment	Subtract
%Special Tax Adjustment	SI Income Special Tax Adjustment	Subtract
%Non Tax Adjustment	SI Income Non Tax Adjustment	Subtract

Step 13: Set up Value for Action Parameter - Maximum Errors Allowed Required Step

Ensure that you specify the number of assignment action failures that can happen during the Magtape process. The Magtape processes, Payment Output File (Dutch) and Dutch SEPA XML File and Report, consider the Action Parameter 'Maximum Errors Allowed' for assignment level errors. The payroll process completes successfully if the number of assignment action failures do not exceed the value mentioned in the Action Parameter 'Maximum Errors Allowed'. This enables you to correct the individual assignment failures. If you do not specify any value for this action parameter, then the complete payroll process fails in case the Magtape Process encounters any single assignment action failure.

Index

Oracle HRMS for Netherlands Supplement

Contents

Implementation

Additional Implementation Steps for the Netherlands

Additional Implementation Steps

Step 1: Configure the Title Field

Step 2: Configure User Tables for Default Absence Actions