on 12-11-2014 5:02 AM
Dear Expert
As the activation of integration of i models is taking long time to execute for pds batches materials .before it use to execute in 1 to 2minutes .As there are no queues has been stucked in ecc side or apo side also even though it is taking long time >how to overcome these issue .please suggest
Thanks in advance
Regards
virender
Hi Virender,
Have you checked the material list considered in the I model.
If any new materials are added directly in Int. models or any material extensions newly happened in ECC side, this also make job to run more time.
Also check for delta changes happened in material master of ECC.
Thanks,
Bala.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Virender,
Sometimes it does take a little longer, however i would recommend you to use Tcode : SM38 and execute the Program : RIMODINI and try to execute the IM from there. I hope then the issue should be resolved.
Thanks & regards,
NH.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you are running in foreground you can run in background now. Or try to clear other failed queues first and then activate this IM. You can try with putting only one material in the CIF IM...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Check how many of inactive model you have for this IM. I guess you have multiple inactive versions of the newest IM generated. So, when you run the activation job in the background (without generating a new IM, RIMODGEN), it will start to activate all the inactive version of the newest model.
Hence multiple jobs of the same program of the same data-set run in parallel, which cause locking. Combination of all these a long runtime and sometime a job failure.
Now you should goto CFM7 and delete all the inactive model except one. Then try to activate the model. You should not face any issue this time.
Hopes this helps.
Thanks,
Satyajit
If you have access check your queue registration with SMQR. In SMQ2 it may be sufficient to STOP the queue (lock immediately with F8), then unlock with F5. This forces re-registration and can often kick-off a queue that is 'hung'.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Expert
As the activation of integration of i models is taking long time to execute for pds batches materials .before it use to execute in 1 to 2minutes .As there are no queues has been stucked in ecc side or apo side also even though it is taking long time >how to overcome these issue .please suggest
Thanks in advance
Regards
virender
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Virender,
1) Are you using the parallelized transfer options provided in CFM2 while activating the Integration models? If not try to add activate with parallelization.
2) Check the CIF User exits and BADI's, there might be a customized code in the user exits or BADI which is leading to increase in run time of activation report.
Regards,
TP
Hi prakash
Yeh i am using parallelized transfer options provided in CFM2 even though it is taking long time.
2) Check the CIF User exits and BADI's, there might be a customized code in the user exits or BADI which is leading to increase in run time of activation report.
how to check point please guide me
Hello Virender,
To check user exits
Go to transaction SMOD give the below exits and check the code inside the custom includes.
Below is the list of User exits related to CIF.
CIFBTC01
CIFCID3
CIFCNF01
CIFEVT01
CIFIMO01
CIFIRQ01
CIFLOC01
CIFMAT01
CIFMAT02
CIFORD01
CIFORD02
CIFORD03
CIFPIR01
CIFPIR02
CIFPUR01
CIFPUR02
CIFSLS02
CIFSLS03
CIFSLS04
CIFSTG01
CIFSTK01
to check BADI go to tranasaction SE18 --> give the below BADI names and check if there is any active implementations of the BADI.
CIF_CCR_STOCK_MODIF
CIF_ENHANCE_BATCH_CHAR
CIF_ENHANCE_FCC
CIF_EXT_IS_INTERNAL
CIF_MRPDS
Take a help of ABAPer to check the implementations in depth to understand whether there is any performance issues in the customized code implemented.
Regards,
TP
User | Count |
---|---|
9 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.