Feature LGMST – Planned payment specification
After writing back to back blogs on HR Renewal functionality, I decided to get back to basics with this blog i.e. explaining LGMST feature (Though I saw many discussions around this topic, I didn’t find even a single blog that emphasizes this feature). The reason why I chose this topic was – to fulfill my promise that was made in one of my oldest blogs – HCM Processes and Forms – Tips for configuring Basic Pay Infotype 🙂
This feature determines the default wage types of “Basic Pay” infotype based on various criteria like –
SAP Documentation says –
More information about this feature can be found from the below links –
On creating the Basic Pay infotype for a Regular employee, I would like to default two wage types(non-editable/non-changeable) .
As mentioned above, the outcome of this feature is “XX/YYYYYYYY”, where XX stands for “Maximum number of wage types” that can be defaulted and YYYYYYYY stands for “Wage type model”. As per my requirement, I went ahead configuring this feature based on my “Employee Group”–
As mentioned in this screenshot – Lesotho’s Regular Employee can have a maximum of 20 wage types defaulted with wage type model as “—-1LS-“. The mapping between Wage Type model and the actual wage types is maintained in T539A.
As explained in SAP Documentation, we can set the “Mode” for these wage types according to our requirement. Here are available options –
When I try creating Basic Pay infotype record for any Regular employee from Lesotho, I get to see the two default wage types(if you observe carefully, since I have set the mode as “F”, both the wage types are disabled)
Now, let’s say if I enter the Annual Salary as 60000, the automatic wage type amount calculation will not happen instead you get a popup asking us to enter either amount or percentage for each wage type manually –
This feature controls the “Default Wage Types” functionality for Basic Pay Infotype. This is one of the most important features of Basic Pay infotype. In my next blog, I shall try to put down my thoughts around “TARIF” feature (which is one more important feature for Basic Pay Infotype).
Appropriate Wage Type configuration like defining Wage Type characteristics, defining Wage Type group, etc. should be in place before hitting this feature.