Skip to Content

I am sure I am not the first one facing issues when configuring IT0008 – Basic Pay, so I decided to put down few tips together in this blog that would help many consultants like me. Before I go ahead listing the tips, I would like to share my recent stint with IT0008 issues.

Mystery around CPIND – Planned Compensation Type


Assumption –

You are using Pay Scale structure configured in T710 table and this part is configured in TARIF Feature by setting the Planned Remuneration Type is set as “S”. More information on this is provided in the link.

Expectation –

Since we are using the Pay Scale Structure from T710, we should be maintaining the appropriate values for the Job maintained in Planned Compensation Infotype (1005). These values i.e. Pay Scale Structure should be defaulted based on Employee’s Job in Basic Pay Infotypes.  All this works fine (assuming the pay scale information is maintained for employee’s job in HRP1005) i.e. the Pay Scale Structure is getting defaulted, when we try maintaining this infotype directly in PA30.

Mystery –

Assuming that all is working as expected at least till this point, I went ahead pretty confidently configuring my might IT0008 fields in my HRASR Process. With lots of enthusiasm, I have added the below fields with “Change” Operation –

I0008_ANSAL with default value as “CUR” as per our requirement

I0008_ANZHL with default value as “CUR” as per our requirement

I0008_BETRG with default value as “CUR” as per our requirement

I0008_BSGRD with default value as “CUR” as per our requirement

I0008_EINHT with default value as “CUR” as per our requirement

I0008_EITXT with default value as “DEF” to get this value defaulted based on the Unit selected

I0008_LGART with default value as “CUR” as per our requirement

I0008_LGTXT with default value as “DEF” to get this value (Wage Type Text) defaulted based on the Wage Type selected

I0008_TARTX with default value as “DEF” to get this value (Pay Scale Type Text) defaulted based on the Pay Scale Type selected

I0008_TGBTX with default value as “DEF” to get this value (Pay Scale Area Text) defaulted based on the Pay Scale Area selected

I0008_TRFAR with default value as “DEF” to get this value (Pay Scale type) defaulted from TARIF feature.

I0008_TRFGB with default value as “DEF” to get this value (Pay Scale Area) defaulted from TARIF feature.

I0008_TRFGR with default value as “DEF” to get this value (Pay Scale Group) defaulted from T710 as per the Planned Remuneration Type (‘S’ in our case) configured in TARIF feature.

I0008_TRFST with default value as “DEF” to get this value(Pay Scale Level) defaulted from T710 as per the Planned Remuneration Type(‘S’ in our case) configured in TARIF feature.

I0008_WAERS with default value as “CUR” as per our requirement

Happily did my Unit testing once the form design is done to find the below weird errors –

/wp-content/uploads/2013/04/p1_207839.png

I started wondering why I am getting these errors only from the beautiful HRASR Framework. Also, my mighty dropdowns for Pay Scale Group and Pay Scale Level are absolutely working as expected i.e. they are  displaying the values configured from T710 itself.

Thanks to my colleague and Senior Developer – Padmavathi Madham who debugged this issue to realize that if the Planned Compensation is not passed to HRASR framework an additional check is done ensuring that the entered Pay Scale Group and Pay Scale Level are maintained from T510 which causes these errors. There you go, she precisely found the resolution i.e. add the CPIND(Planned Compensation Type) field to the configuration with the default value to be populated from IT1005 based on the value maintained.

Tips…


I might have mentioned the below tips already in this blog, I decided to re-emphasize again as they can be very important –

a. If you are planning to update IT0008 especially “Create”, you may want to set the default value as “DEF” for the below fields –

  • LGART – Wage Type ( This automatically get determined using LGMST feature)
  • LGTXT – Wage Type Text
  • CPIND – Planned Compensation Type
  • EITXT – Unit description
  • TARTX – Pay Scale Type Text (If displayed on form)
  • TGBTX – Pay Scale Area Text (If displayed on form)
  • TRFAR – Pay Scale Type
  • TRFGB – Pay Scale Area
  • TRFGR – Pay Scale Group
  • TRFST – Pay Scale Level

b. When designing the form, keep in mind that you create the form type based on the field type i.e. if the field belongs to MAIN structure, add this field to “FORM” form type; if the field belongs to LINE structure (say BETRG, LGART, LGTXT, etc), add this field to “LINE” form type(Table).

I shall write one more blog(This one should be on “Annual Salary” 🙂 ) with more tips, so stay tuned guys!

To report this post you need to login first.

3 Comments

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

  1. Madhava Rao Basava

    Hi Raja sekhar,

    Its a good document explained well and with error descriptions. Keep posting..

    Finally include some screenshots of IT0008 and the respective configs. This will give a clear view.

    Thanks,

    Madhav.

    (0) 
    1. Raja Sekhar Kuncham Post author

      Thanks Madhav,

      Well, there is nothing missing from what I have mentioned above in terms of screenshot except the “Field Attribute”, which doesn’t really matter.

      Let me know if you are precisely looking for any detailed information. Shall try to provide that information.

      Regards

      Raja Sekhar

      (0) 
  2. Kurt Dukes

    So can you possibly unravel the mystery around the Pay Scale and Pay Grade fields as they relate to the 0EMPLOYEE_ATTR DataSource?

    As I understand it, Pay Scale fields in the DataSource is fro non-exempt folks whereas Pay Grade fields are for exempt folks.

    I am a BW Administrator and my HCM counterparts are saying I am loading ‘the wrong fields’ but I say I am loading a ‘bone stock’ DataSource.

    Can anyone help?

    Cheers,

    Kurt Dukes

    (0) 

Leave a Reply