Programme SAP RPUDECG0PBS_FILL_ME_VARIANTS - Fill ME variants in program RPUDECG0PBS_FILL_COSTS

Purpose
This program creates variants for Multiple Employment runs in the mainconversion program RPUDECG0PBS_FILL_COSTS
. The selection screen layout and processing is almost exactly thesame, so please read that documentation first.

Integration
This program can be used instead of the ME conversion programRPUDECG0PBS_FILL_COSTS_ME. Thisprogram creates all the necessary variants, but then the user still hasto create the batch jobs to run those variants. So this methods is morework for the user, but allows more control, if that is what you require.
The program RPUDECG0PBS_FILL_COSTS_ME simply takes the details of thevariants and instead of creating them actually calls the programRPUDECG0PBS_FILL_COSTS with the details of that variant. In this wayRPUDECG0PBS_FILL_COSTS_ME is a more user friendly option as there is noadditional work for the user to ensure that the ME get convertedcorrectly.
The program works out all the MEs that need to be processed and forwhich payroll periods. It then orders them by payroll period into twoseparate runs; non-primaries first and primaries last.

Selection
The selection screen is almost identical to the main conversion programRPUDECG0PBS_FILL_COSTS except for acouple of differences;
1) The Single Employment / Multiple Employment radio buttons are notdisplayed as only MEs are processed by this program.
2) The Variant Name option at the end of the selection screen allows theuser to dictate what the first 3 characters of the variant identifiersshould be. If this program is re-run with exactly the same parametersthe variants from the previous run are overwritten. So if you wish toretain a set of variants for any reason then these 3 characters shouldbe changed to avoid the original set from being overwritten. This doesalso provide a simple way of identifying who created the variants (i.e.they could be use user's initials).
The variants are created with the following naming conventions;
Non-Primary run
Variant Name ,,,,XXXYYYYMMDD1??
Variant Text (Normal ) ,,??_YYYYPP_1___
Variant Text (Off-cycle) ,,A_B_DDDDDDDD_1
Primary run
Variant Name ,,,,XXXYYYYMMDD2??
Variant Text (Normal ) ,,??_YYYYPP_2___
Variant Text (Off-cycle) ,,A_B_DDDDDDDD_2
XXX is the three characters from the selection screen
YYYYMMDD is the end date of the IN period
?? is the payroll area
YYYYPP is the IN period
A is the off-cycle type
B is the off-cycle identifier
DDDDDDDD is the off-cycle bonus date

Output
CREATED VARIANTS
The variants that will be/have been created are displayed.
When the program is run in background no created variants are displayed.
STATISTICS
All the statistics reflect all contracts of each ME processed, exceptthe "bypassed" statistic which reflects the number of SEs that have beenselected but not processed.
"Selected" = number of ME contracts selected
"Rejected" = number of ME contracts rejected
"Processed" = number of ME contracts processed
Example
If we have three MEs processed,
ME 1 (4 Contracts)
ME 2 (2 Contracts)
ME 3 (3 Contracts)
If none of the contracts fail to be converted then the statistics wouldbe as follows;
Selected,,9
Processed,,9
Rejected,,0
These will not change whether ALL contracts are selected for processingor just one contract of each ME.
If one of the contracts of ME 3 fails to be converted then ALL thecontracts of ME 3 fail the ME is rejected as a whole. So the statisticswould be as follows;
Selected,,9
Processed,,6
Rejected,,3

Activities
This program does support test/simulation mode, so make sure that thevariants are being created to your requirements before running in updatemode.