Ansicht
Dokumentation
RPUDECG0PBS_FILL_ME_VARIANTS - Fill ME variants in program RPUDECG0PBS_FILL_COSTS
Addresses (Business Address Services) ROGBILLS - Synchronize billing plansThis documentation is copyright by SAP AG.
Purpose
This program creates variants for Multiple Employment runs in the main conversion program RPUDECG0PBS_FILL_COSTS. The selection screen layout and processing is almost exactly the same, so please read that documentation first.
Integration
This program can be used instead of the ME conversion program RPUDECG0PBS_FILL_COSTS_ME. This program creates all the necessary variants, but then the user still has to create the batch jobs to run those variants. So this methods is more work for the user, but allows more control, if that is what you require.
The program RPUDECG0PBS_FILL_COSTS_ME simply takes the details of the variants and instead of creating them actually calls the program RPUDECG0PBS_FILL_COSTS with the details of that variant. In this way RPUDECG0PBS_FILL_COSTS_ME is a more user friendly option as there is no additional work for the user to ensure that the ME get converted correctly.
The program works out all the MEs that need to be processed and for which payroll periods. It then orders them by payroll period into two separate runs; non-primaries first and primaries last.
Prerequisites
Features
Selection
The selection screen is almost identical to the main conversion program RPUDECG0PBS_FILL_COSTS except for a couple of differences;
1) The Single Employment / Multiple Employment radio buttons are not displayed as only MEs are processed by this program.
2) The Variant Name option at the end of the selection screen allows the user to dictate what the first 3 characters of the variant identifiers should be. If this program is re-run with exactly the same parameters the variants from the previous run are overwritten. So if you wish to retain a set of variants for any reason then these 3 characters should be changed to avoid the original set from being overwritten. This does also 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
Standard Variants
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, except the "bypassed" statistic which reflects the number of SEs that have been selected 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 would be as follows;
Selected,,9
Processed,,9
Rejected,,0
These will not change whether ALL contracts are selected for processing or just one contract of each ME.
If one of the contracts of ME 3 fails to be converted then ALL the contracts of ME 3 fail the ME is rejected as a whole. So the statistics would be as follows;
Selected,,9
Processed,,6
Rejected,,3
Activities
This program does support test/simulation mode, so make sure that the variants are being created to your requirements before running in update mode.
Example
CL_GUI_FRONTEND_SERVICES - Frontend Services Addresses (Business Address Services)
This documentation is copyright by SAP AG.
Length: 4846 Date: 20240520 Time: 131849 sap01-206 ( 74 ms )
