|
If you would like to create a specific benefit plan whilst carrying out a Personnel Action (for example you want to create a Health Insurance Record whilst performing a new starter action) this cannot be done using just the standard infogroups.
The problem lies in the fact that a Benefit Plan is not a subtype of a Benefit Infotype, so it cannot be specified through table V_T588D as part of the info group. A good way around this problem is to create a dynamic action within table T588Z.
There are many tabs within the Benefits Infotypes and these can often hold data that is not relevant to a company's business requirements.
These tabs can be hidden to simplify the recording of the data for end users. To hide these fields, a module pool must be created within table T588M for each different screen within an infotype (each tab is assigned to a screen number - for example the Administration Tab within IT0167, Health Plans, is screen 2020)
To hide the administration tab within IT0167, create an entry in table T588M as below and hide all the fields within that field, the tab will then no longer appear on IT0167.
There are a few exceptions to this rule; the dependents tab on IT0167 and the beneficiaries tab on IT0168, Insurance Plans, cannot be hidden. IT0377, Miscellaneous Plans, works in a different way to the other benefits infotypes - once the miscellaneous plan has been chosen, the tabs that are not relevant to that plan are dynamically hidden without any entries made in table T588M.
The flexible benefits module of SAP can be rather complicated to use and it is often simplified for use by the end users. One piece of functionality that is often removed to aid the users is the dynamic link between IT0171 and the enrolment process. The enrolment process can be used to determine which employees are entitled to enrol in which Benefit Plans, however the process can be a little convoluted and difficult to understand.
The link between IT0171 and the enrolment process is simply carried out by a dynamic action, so in order to remove this link the relevant entries in table V_T588D simply need to be commented out.
When assigning wage types to Benefit Plans so that the correct values are fed through to the payroll, it can be confusing as to which wage types need to be assigned to which Benefit Costs.
The entries that are made in table V_5UBI_A (for Health Plans)
Directly effect the entries that are available for entry in table V_5UBA_WT
Because the 'Employee Cost' and 'Additional Post-Tax' fields are populated in table V_5UBI_A, the relevant WT fields are available for input in table V_5UBA_WT. The wage type fields in table V_5UBA_WT relating to the costs in table V_5UBI_A that are not populated are dynamically hidden.
Accessing table T5UBA through transaction SE16N allows the user to see all the Wage Type fields in table V_5UBA_WT, regardless of the entries in table V_5UBI_A.
A really useful tool when configuring the benefits module within SAP is the Configuration Consistency Check
You run the check by Benefit Area or Plan and it will warn the user of any inconsistencies that may arise from the configuration, for example if there are is not a cost variant created for a particular Benefit Plan. The error and warning messages can appear slightly confusing at first, but they do make sense if you think about what they are telling you.
It is very easy to copy and delete existing Benefit Plans and Areas within SAP using the relevant IMG step within the Benefits Toolset.
This can prove to be very useful if a benefit plan already exists which has similar attributes to a benefit plan which needs to be created. The existing plan can be copied and modified as necessary; this can be a lot simpler than creating a new plan from scratch. The only limitation of this functionality is that you cannot copy a plan into a different benefit area than the original plan.
|
Knowledgebase 
