Skip to Content
avatar image
Former Member

After sepration system should not allow to create or change any payment related infotype

Hi Experts,

Please suggest the best possible solution for the following issue.

1.    Once employee is terminated through separation action, system should restrict the user to change or create any payment related info type in the system.

2.    Once employment  status is withdrawn or inactive, system should throw an error  while creating or changing payment related info type for that particular employee.

If I change the configuration of info group where currently operation key LIS9 is maintained for separation info group, to EDQ then user can not change or create  the record after running separation action , but at the same time it will not bring these info types in the reports.

Client wants these payment related info type to appear for the employee even after running separation action also.

Please suggest whether it is possible in the standard way or not.

Thanks & Regards,

Prashanti Swain

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    avatar image
    Former Member
    Aug 13, 2015 at 05:38 AM

    Go with BADI or Exit.

    HRPAD00INFTY

    PBAS0001

    We can write many validations, Only thing logic should be given to technical consultant with out impacting the existing system and business process.

    Further once employee got separated or terminated where we do not have planned compensation for an employee from employer prospective and it is neverthless no data should be maintained against IT0008.

    As far as i know, Standard SAP always gives a provision to get the report based on Employment status i.e Till the date he is active system considers him for all the reports and provides us valid information.

    Even though wanted to play around with system We can go ahead with BADI, Exit. The only thing we will have to consider is it should not impact other areas which are working fine.

    Regards

    Venkatesh

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Thanks venkatesh,

      I got the solution in standard, only, here i do not need to go with exit or badi implementation.

      Thanks & Regards,

      Prashanti Swain

  • Aug 12, 2015 at 03:05 PM

    Hi,

    I think you can add an extra code in the Module Pool of the Infotype once STAT2=0.

    Like IT15 module pool program is MP001501.

    Check once with technical consultant on this.

    Regards,

    Sankarsan

    Add comment
    10|10000 characters needed characters exceeded

  • Aug 12, 2015 at 04:26 PM

    I don't believe that your requirement can be met with "standard" configuration.

    As mentioned by Sankarsan, you'd have to ask an ABAP programmer to create some Custom Code at the Infotype level (upon validation of the Infotype or upon saving the Infotype).

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 12, 2015 at 10:39 PM

    Quite often or even mostly as a common practice in many organizations, an employee is not paid or settled fully at the time of separation.   It becomes necessary to pay any balance due later.

    You may restrict this with a certain security profile, or through specific approvals using P&F (or a change request as existed before).

    Add comment
    10|10000 characters needed characters exceeded

    • Hi swain,

      I restricted in pa40 userexit through ABAP code but different scenerio .

      scenerio is those who are in action 7 , 10 , 17 while running action 23 salary rivision action for that employee .It is not applicaple for those who are in ation leave on maternity, On leave, Resignation Intimation.

      Is this helpful for you.


      with regards,

      siva

      Message was edited by: sivakumar M