How to replicate IGMOD feature in HR Renewal

[giampierograceffa]

Hi all,

we are implementing HR Renewal 1.0 FP4, we have replicated on Renewal the ECC actions and they are working well, but I have an issue, the feature IGMOD has been implemented on the ECC system for many of these actions to differentiate the infotype sequence in relation to the reasons chosen by the user,

I don't know how I can  replicate the feature IGMOD on the renewal actions..is it possible?

If there isn't a functionality  to reproduce the IGMOD feature, which is the best  way to replicate it on the renewal actions?

Currently the best  way that I have found is to create more time the same action with different  action reason.

In the  HRASR_DT tcode, in the action form scenario, I have set the ‘Attribute for Action Reason’ field on ‘READONLY Output only’ so that the user cannot modify the action reason, and then I have set the infotype sequence, so that when the user create the action with that reason can only create the related infotype sequence, but I don’t like this solution because determines an excessive number of actions in the ‘action’ lane, it’s not user friendly.

Can you help me?

Thanks.

Regards.

Giampiero

[Chetanm1]

Hi,

  Even we are facing a similar issue. We have created multiple forms/process for a single action and populated the same in the lanes. Although these forms and processes can be renamed as Action for Contractor, Action for Regular employee and are meant for the HR administrator this just piles up the action lane of the admin with so many different options. The IGMOD feature worked great and it would be really great to have some option similar, which would support the dynamicity of these actions on the lane based on some input parameters. Thanks Giampiero for raising this.

Regards,

Chetan

[stuart_campbell]

In the case of HCM process and forms - it might be better to have different processes for different countries - unless you are using IGMOD to distinguish employees other than by country ?

[giampierograceffa]

Hi Stuart,

thanks for your reply,

the feature has been implemented in the ECC system only to make it easier for the user to create an action.

We don't use the feature to distinguish employees, we use it as a kind of wizard to help the user  to fill the correct infotype in the action, and I have to replicate this functionality on Renewal.