Professional Documents
Culture Documents
Home If your browser does not support the SDS Knowledge Base menu, click here for an alternative.
Knowledgebase
Personnel Management
About SDS
Benefits
Links
Sitemap
Knowledgebase
Search Q
Query Tools Data Tools Human Resources FI/CO Cross System Miscellaneous BW
Your Input
We are always up our articles and a new ones to the li Please let us kno is a particular arti would like to see.
Scree n Modifications
There are many tabs within the Benefits Infotypes and these can often hold data that is not relevant to a company's bus iness requirements. These tabs can be hidden to simplify the recording of the data for end us ers . 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 s creen 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 mis cellaneous plan has been chosen, the tabs that are not relevant to that plan are dynamically hidd en without any entries made in table T588M.
How the attributes define the av ailable fie lds for WTs, using SE16N
When as signing wage types to Benefit Plans so that the correct values are fed through to the payroll, it can be confus ing 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.
You run the check by Benefit Area or Plan and it will warn the us er 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 s lightly confusing at firs t, but they do make sense if you think about what they are telling you.