Skip to Content

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 🙂

Introduction:


This feature determines the default wage types of “Basic Pay” infotype based on various criteria like –

/wp-content/uploads/2013/10/p1_289645.png

SAP Documentation says –

/wp-content/uploads/2013/10/p2_289682.png

More information about this feature can be found from the below links –

LGMST-Planned Remuneration | SAP HR Outlook

Define default wage types

Requirement:


On creating the Basic Pay infotype for a Regular employee, I would like to default two wage types(non-editable/non-changeable) .

Solution:

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”–

/wp-content/uploads/2013/10/p3_289683.png

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.

/wp-content/uploads/2013/10/p4_289684.png

As explained in SAP Documentation, we can set the “Mode” for these wage types according to our requirement. Here are available options –

/wp-content/uploads/2013/10/p5_289688.png

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)

/wp-content/uploads/2013/10/p6_289689.png

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 –

/wp-content/uploads/2013/10/p7_289690.png

Conclusion:


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).

Note:

Appropriate Wage Type configuration like defining Wage Type characteristics, defining Wage Type group, etc. should be in place before hitting this feature.


To report this post you need to login first.

6 Comments

You must be Logged on to comment or reply to a post.

  1. Madhava Rao Basava

    Hi

     

    You are right. The topic you have selected is a basic one but still we come across many queries on this. Thanks to the detailed documentation. Hope this would be helpful for everyone.

     

    Thanks,

    Madhav.

    (0) 
    1. Raja Sekhar Kuncham Post author

      Thanks for the feedback.

       

      Yes, I did search with this keyword – LGMST and hunted for any blogs. I didn’t find even a single one.So I decided to put down my thoughts in this blog.

       

      I am sure this would be very helpful for aspiring SAP HCM Consultants.

       

      Regards

      Raja Sekhar

      (0) 
  2. Rémi Corriveau

    Nice document Raja Sekhar.

    To complete, perhaps you should add the Feature’s Initial Screen and mention that you can see the feature’s criteria by selecting the “Attributes” button an then activating the “Display” icon, enabling you to then select the “Struct.” or the “Country/component assignment” icons.

    But these may not be all the possible Decision Criterias available.  To see the extra ones, select the “Attributes” button and then activate the “Change” icon, followed by the “Struct.” icon.  You’ll then see what other standard Decision Criteria that could be added to your Feature.

    (0) 

Leave a Reply