RIMODGEN job abort caused by user editing model

[Former Member]

hello fellow apo professionals!

to load apo with data we have scheduled every day in the evening a job with repeating steps with RIMODGEN, RIMODAC2 and the corresponding variants for material master data, production orders, etc.

Because we have this in one job, it is a high risk that the whole job can abort.

We now had this problem because a user was editing a integration model and the job aborted here - my question is: is there a possibility to "kick" users out of CFM1/2 in the job as an own step, to make sure, that the integration model will be created and activated?

best regards

[RahulHanda · Accepted solution]

Hi Dominik,

There are two ways to look at this issue:

First - why user is in CFM1/2 itself? Do you need to change your variants very often? Are they not generic example materials with MRP type X0 should go to APO. If they are generic then logically user should not be authorized to go in these transactions. So in this case remove authorization.

Second - Could be you have created certain filters which needs to be updated every now and then, Have we tried making these filters also generic to have right process?

Nevertheless you want to kick out a user, this could be done by SM04 (assuming you have given authorization for CFM1/2 to one or two users, though would work for all but you need to keep in mind). If you go in transaction SM04, select user and click session then it would show all necessary sessions which user is using. By selecting that specific session and click on end session it would kick user out. But then this would mean that work carried out by user would be not saved and this might create inconsistencies. So you can monitor the same and ask user to leave the session before executing of the jobs (example 15mins before the execution, I know its cumbersome process but right way).

On the other hand if you want to automate the same, check the below link.

Let me know if it resolved your issue.

Regards

Rahul

[Former Member]

Hi Dominik,

Have a look at this thread as well. You can create custom program and add it as a initial step of the job which would ask the users to get rid of CFM1/2 before the actual steps of CIF starts

Thanks

Vinoth