CIF Error

[former_member188806]

Hi,

When we try to CIF data (R/3 4.7 & SCM 5.1), we're encountering a SYSFAIL....however the problem is that we ar'nt able to view the application log on double clicking the SYSFAIL.

It just shows "application log cannot be written".

We've followed Note 935030 however it hasn't helped.

Pls. help.

Thanks,

Saba.

[Former Member]

Please run the /sapapo/SBALDELETE to delete the existing CIF log in APO and re-process the queue and see if you can get the SYSFAIL again and see if you can read the Log after running this Job..

You may want to schedule this JOB periodically to delete the accumulating application Log...Also you can configure the application log in R3 for number for fields to be written in log using SPRO..

[former_member188806]

Hi everybody,

Thank you so much for the replies..

In SLG1 & CFG1, no log has been written, same applies to double clicking SYSFAIL.

We are encountering this message on the APO side.

/SAPAPO/SBALDELETE is neither a T-code nor a program, how do I execute it?

Thanks a lot,

Saba.

[Former Member]

Sorry about that...please use program SBAL_DELETE in se38.

[Former Member]

Please check error detail in SLG1 log and /SAPAPO/CQ.

One error we faced with the same error message because of Application log is too big to write.

Please split the job into mutliple job to share the load and see if same error is coming .

Manish

[Former Member]

can you please provide us some more details like in which queue you are gettingthis error and also on which side is it APO queue or R/3? please look at the application log (/SAPAPO/C3 in APO or CFG1 in R/3) and check if you get any detailed error message

[Former Member]

Hi,

Hope below link might help you.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0d1265d-db32-2b10-79ba-ccf6fe2c...

Regrads,

Hardik

[Former Member]

Hi,

Double click on the SYSFAIL (in tocde SMQ1 or SMQ2) then in the next screen select any failure records and press debugging icon in the menu bar then you can able to debug the original funciton module , So you can find the exact problem.If required take help from technical guy.

Thanks,

radha.