Support The Site

Monday, January 6

Infotype 0008 Wage Types Default

When you create a new infotype 0008 record, one or more wage type automatically default into the wage type field. How does this occur and how do you controll it? There are many ways to accomplish this. One way is through user exit custom code, but the standard way is via configuration in the Payroll Data configuration node.

In the SAP IMG configuration node "SPRO -> Personnel Management -> Personnel Administration -> Payroll Data -> Basic Pay -> Wage Types" section you have a series of configuration item to setup Wage Types. On how to setup a Wage Type and their attribute, I'll defer that to another Wiki page at a later date. This page is specifically meant to illustrate how to get the wage type once it is setup to default on infotype 0008 when a new record is created.
  • Wage Type attribute and characteristics are properly setup.
  • Wage Type permissibilities are properly setup

In the node, there is a section called "Enterprise Structure for Wage Type Model" which calls a feature tree (technical name: LGMST). This is a decision tree that return a specific value or set of values. Usually by SAP standard, it utilize key information found on a user infotype 0001 as a decision factor. In this case, we use MOLGA (Country Grouping) and PERSG (Employee Group)

Based upon the tree condition, it will return a set of values to SAP. In the example above it is either "10/HOURLY" or "10/SALARY". The 10 represent the maximum number of wage types it should default into or return back once it find the matches for the value SALARY or HOURLY. The value SALARY or HOURLY are found in the IMG node called "Revised Default Wage Types" also know as table V_T539A.

With the logic above, it will be able to know to default accordingly. So using example record as seen below. The default of the value 1010 - Regulard Salary. You will also notice value 1099 FTE Equivalent also is on this record. This was default using the User Exit Custom Code method for a different purpose.

No comments: