Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

'Dialog allowed' in TCODE BD51

Former Member
0 Kudos

I wonder the usage of the check box 'dialog allowed' in TCODE BD51. Is there anyone know that?

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Idocs are usually processed through background jobs.

Using that checkbox, individual Idoc can be processed in dialog mode, which helps in debugging.

8 REPLIES 8

former_member209119
Active Participant
0 Kudos

Hey,

Check the below link. Might be useful for you.

https://scn.sap.com/thread/1714037

0 Kudos

Sorry, this link didn't explain the check box

Former Member
0 Kudos

Idocs are usually processed through background jobs.

Using that checkbox, individual Idoc can be processed in dialog mode, which helps in debugging.

0 Kudos

thank you for you answer. I still have a question, how does it help us to debug the program? Goto SM50 to debug it or just create the break-point in the inbound function module?

0 Kudos

SM50 would be needed for long running background job.

For foreground debugging, idoc can be processed from BD87 transaction.

0 Kudos

Hi Manish, I don't need to mark the check box, I can still use BD87 to debug the idoc inbound function...

0 Kudos

I did a where-used search on TBD51 table, and found that FM IDOC_MANUAL_INPUT checks for that field.

This FM is called by program RBDMANI2, which is used to reprocess error inbound idocs.

BD87 also calls FM IDOC_MANUAL_INPUT while reprocessing error inbound idoc.

When reprocessing is done in BD87 using process button, the calls happen in no_dialog mode.

In order to do it in dialog mode, "Restrict and process" needs to be done instead of "Process".

0 Kudos

Brilliant!!!!  Thank you very much!