cancel
Showing results for 
Search instead for 
Did you mean: 

Debug CIF - ECC inbound - User exit CIFORD03 - Planned order to process ord

Former Member
0 Kudos

Hi

While Converting planned orders to process orders from APO to ECC, queues are not getting stop in Inbound ECC.. even after setting CIF user as dialog user and maintaining both CIF user and my user ids in /sapapo/c4 to block queues. maintained the same in ECC CIFGPARAMV table. Outbound queues are stopping in APO, but not able to debug APO outbound queues...

I want to debug user exit CIFORD03 (EXIT_SAPLCORD_005 ) in ECC . Please reply.

Thanks

Sreeni

Accepted Solutions (1)

Accepted Solutions (1)

former_member209769
Active Contributor
0 Kudos

Hi Sreeni,

The setting in /sapapo/c4 against your user ID would be relevant in this case.

Debugging should be on, and use detailed logging. Also, your RFC user ID should be a dialog user ID or a Service user ID.

Did you make sure that your user ID and the RFC user ID 'in R/3 for APO' have sufficient debug authorizations (including queue debug authorizations)?

(You can find out the RFC user in SM59 in APO against the RFC connection that you have for R/3. )

You should then see a queue stuck in R/3 inbound, where you could enter in debug mode.

If you go to SMQR in R/3, and see a queue called CF, then it's also possible to deregister this CF queue, and then queues will get stuck in R/3 inbound. You could then use this queue for debug if you have sufficient debug authorizations including queue debug.

Thanks - Pawan

Edited by: Pawan Pathak on Feb 16, 2012 1:32 PM

Former Member
0 Kudos

Pawan,

CIF user authorization was the issue. Problem is solved. Thanks for the quick response. I will close it now and reward the full points.

Thanks,

Sreeni.

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

The blog is very useful, thanks!

There are also here two comprehensive documents on CIF debug goo.gl/iiO7J and on CIF error analysis overall goo.gl/bgylt . You can see a preview to see if it suits your needs.

Cheers

Matthieu

Former Member
0 Kudos
ramesh_mahankali
Active Participant
0 Kudos

Hi,

You can enter into debug mode by writing a infinite loop in the begining of the user exit where you want to debug.

but you should be able to control when to activate the infinite loop by putting it in a if ..endif so that it not struck always.

once you execute the transaction in APO, you will be able to see your infinite loop in SM50/SM51

transaction and will be able to debug from there.

Let me know if this helps.

Thanks,

Ramesh