Topic 35: Absence Quotas (And 6000 real-time SAP Screen shots)

[freesaphr]

Activities

Decide which types of entitlement to time off your employees have.

Define the absence quota types you want to use based on the groupings. Use the
SAP standard entries as a guide. If necessary, define additional absence quota types.

In the field Unit of Time/Measurement define whether you want the entitlement to time off to be maintained in hours or in days.

Assign a time unit to the quota type.

If you define an absence quota type with a time unit in hours, you can enter default
values for the start and end times. These are proposed in the Absence Quotas infotype when you enter absence quotas.

Example: In your enterprise, employees are only allowed to take time off for overtime in the afternoon. Enter 12:00 (noon) to 24:00 (midnight) as the default values for start and end times.

For USA, unit in Hours is usually used for Absence Quotas (Vacations, sick, etc). PTO and Floating Holidays are counted as Days.

Enter the time constraint class for the absence quota type. The step Specify System Reaction to Overlapping Time Infotypes contains information on the concept of defining time constraint classes.

In the field Negative deduction to, specify whether and to what extent there can be negative deduction of entitlement to time off.

In the Rounding field, specify how absences of less than one workday should be deducted from a quota which is maintained in whole days

[freesaphr]

Example

You want to define the entitlement to Annual Leaves for your employee subgroup 1 and personnel subarea 10.

[freesaphr]

Absence Quota Type

An absence quota type forms the subtype of the Absence Quotas infotype.

[freesaphr]

Time/Measurement Unit Text

This field specifies the unit of time or measurement which is to be used as a basis for calculations.

[freesaphr]

Time constraint class

The time constraint class is used to check for collisions between Time Management infotypes (2001 to 2012). It allows you to specify different regulations for checking for collisions between individual subtypes.


The views Time Constraint Reaction to Time Management Infotypes (V_554Y_B) and Global Time Constraint Reaction (V_T554Y) contain rules for the collision check.




Mainly tells in a same period do u want to take two leaves or not...lile

Time Constraint 01 : MUST CONTAIN A RECORD ALWAYS (Like IT0008)

Time Constraint 02 : CAN HAVE RECORDS WITH ANY TIME CAN HAVE SAME RECORDS AT A SAME TIME

Time Constraint 03 : CAN HAVE RECORDS WITH ANY TIME CAN NOT HAVE SAME RECORDS AT A SAME TIME
- Like Leaves can take any time but not two leave at a same time