Scenario as follows:
1. As per DWS if any employee works on a off day then compensatory off will be added as 1 but its validity only next 3 days.
2. In public holiday if any employee works then compensatory off will be added as 1 bt its validity will be calendar year.
3. Combine with 1st and 2nd one. DWS=0+15th August then cm off will be added as 2 where 1 cm off validity is next 3 days and another one is calendar year.
Suggested steps:
a) Create time types
9COF Comp off - for the day only, no accumulation
b) V_T559L - select for the relevant pers sub area grpg's:
b-1) Quota types - Ensure an abs quota type for comp off is created. Select generation.
b-2) Abs quota entl - use the t/type 9COF for the day.
b-3) Dedn/validity periods - for both - from the day + 1 after accrual
- to 3 days validity
b-4) Generation rules -
b-4-1) Accrual tab - select daily
b-4-2) Transfer to entl - select accrual day.
c) In time eval schema that you are using: after functions TIMTP, PBRKS, etc and before CUMBT,
c-1) call a PCR say ZATT, using RTIP (RTIP ZATT GEN) to do as below:
- If the proc type is for normal attendance (usually 'S', you may have some other proc type for hol attendance; include this also), and the day is an off day or a holiday add the one day to t/t 9COF
- If the abs type and quota type is in hrs, then you need to convert one day to hrs.
For this conversion, you need to check your business rules. You may use the average daily hrs from IT 7 for the employee or standard daily hrs for the empl's pay scale area. (see below).
grpg */*****
D OUTTPVTYPE - check proc type
* - other;
S Z GCY ZATTJ - attendance. check further
grpg J/****
D VARSTHOLCL - Normal attnd. Holiday?
* Z GCY ZATTL - -Yes;proc further
0 D VARSTFREE - -No;off day?
0 *
0 Y Z GCY ZATTL - - -yes;proc further
grpg L/****
HRS=1 - One day
HRS*IDAHRS - x avg daily hrs from IT 7
ADDDB9ATT -accum att hrs
Notes:
The multiplication by IDAHRS is required only if the abs type and quota type is in hrs.
The pcr ZCAB needs to be made as per my suggestion above. You can break it to 3 pcr's, if you want. What I have shown puts everything in one pcr.
The PCR require proper structuring. If a decision is satisfied, you can do several actions with one decision.
A PCR with decision operations and action operations is like a decision table. The decision table can be used for configuring a PCR, feature or a program routine. When a feature is generated, it creates a subroutine pool member, which is called by the routine which calls the feature.
