Activate Integration model running too long time

[Former Member]

The PGM of activate integration model（Tcd：CFM2) running long long time(1day or 2 days) but no error display because of some reasons

Could I stop the PGM for running?If ok,does any que error or data error will occur?

If couldn't,is there any way to stop it running safety?or let it run complete?

[RahulHanda · Accepted solution]

Hi Yuan,

For which object did you executed the same (example material master/plant etc.)? Also go through the KBA 1637034. It could be you have same issue but for different object.

1637034 - Long runtime of External Procurement Relationship Integration Model Activation

Regards

Rahul

[babu_kilari4]

Hello Yuan,

It makes sense to see what the work process is doing. Is it really pushing the queues into gATP system ?  Or has there been anything that is waiting to be processing which is making the application log not to be written ( which is the last step of CFM2 ) in ECC side. You need to actively check both ECC and gATP system to identify the root cause before killing the process.

Thanks & Best Regards,

Babu Kilari

[Former Member]

Hi Yuan,

As Rahul insisted check whether any high resources consuming jobs are running in parallel.

Get the process ID of the job and Check the following against it

Check the CPU usage. ST06

Application Server Load SM50/SM66

Check whether any progress in sequential read is happening with the DB queries SM50

Check whether any Lock persist for longer time. SM12.

You can conclude from above whether to cancel the job or not. If you're job is not getting canceled from SM37 try cancelling the work process against your process id from SM50-->Cancel Active Process--> with/without core.

You can always reschedule the failed CIF activation job there is no harm in it unless you've all other settings remains fine.

Regards

Vinoth

[Former Member]

Since it has run so long and never completing, in most such cases there is no harm in cancelling the job and scheduling again. May be you can run RIMODINI for the same. Also check if there was some other batch job running at the same time as the last run which could have caused this.