OSP and OMP 
OSP and OMP
Purpose
The OSP/OMP component allows you to perform OSP and OMP processing automatically. It allows you to maintain, apply, and monitor employee's absence schemes (coverage packages) using the standard customizing, absence entry, and payroll functionality provided by Payroll Ireland.
The OSP/OMP functionality reflects the standard business practices used for operating occupational absence payment schemes (OSP/OMP).
Implementation Considerations
To set up your system appropriately for using the OSP/OMP functionality, you must carry out the steps in Customizing for Payroll: Ireland under Sickness Payments ® Occupational Sick Pay and Occupational Maternity Pay. This involves creating the absence schemes you wish to use in your company, attaching and refining them appropriately, and setting up the necessary absence scheme rules.
Features
Automatic OSP/OMP processing allows absences to be split automatically across payment bands. When an employee is absent from work, the Absences (2001) infotype subtype you enter refers only to the absence type and not the rate at which the absence should be paid. The system automatically calculates when the absence should move to a new payment band, for example to half or nil pay. When payroll is run, the absence is split into the correct payment bands according to the absence evaluation scheme rules that you have set up in Customizing. This means that an employee will automatically move to the subsequent payment band unless positive action is taken to prevent this.
When entering an absence for an employee in the Absences (2001) infotype, you can run the Absence Breakdown report, which uses the same calculation as in payroll, to find out whether the employee will move to a new payment band during the absence. This report will produce exactly the same splits that would occur during payroll. However, if you do not want an employee to automatically move to a lower payment band, you can enter an extension for a specific payment band in the Absence Scheme Override (0572) infotype. This will prevent their pay from decreasing below the current rate.
The OSP/OMP component also allows you to perform OSP/OMP processing manually. In this case, an absence is only paid at a single rate of payment directly related to the Absences (2001) infotype subtype. If the rate of payment should need to change because an employee has used all their entitlement to that rate of payment, then the old absence has to be delimited and a new Absences (2001) infotype subtype used to derive a new single rate of payment. As you specifically report who needs to be moved to a new payment band, manual processing allows you to maintain strict "manual" control over the whole process.
Process Flow
1. An employee reports that he or she will be absent from work for a period of time.
2. The clerk creates an Absences (infotype 2001) record for this period with the appropriate absence subtype.
The clerk can see immediately whether the employee is in an absence scheme (Absence Scheme text shown in the infotype). He or she can do on-the-spot checks using the following reports:
3. The employee's absences are processed via payroll.
The clerk can check to see which employees do not have much entitlement left or are on long-term sickness as follows:
The absence history necessary to perform the processes above is generated automatically. The payroll results store sufficient history up to the end of the last payroll that has been run for the employee concerned. The amount of history generated for each absence record depends on the employee's personal calendar date, personal retroactive payroll calculation date, and the absence start date.
4. The clerk may need to give en employee extra entitlement (infotype 0572 Absence Scheme Override).
5. If the absence scheme changes at the end of the year, the Customizing settings which have been made will need to be reviewed.