Status 64 - Debug IDOC_INPUT_ORDERS from WE16?

[Former Member]

Hi,

I have added some code to IDOC_INPUT_ORDERS, and when I execute WE16, the IDOC gets stuck in status 64. When, I comment out my code, it successfully completes to status 53. I can run the IDOC stuck in status 64 through program RBDAPP01, and it successfully completes to status 53. If I run an IDOC through WE19, it successfully completes to status 53. If I comment out my code, the IDOC successfully completes to status 53 via transaction we16. I put a breakpoint in IDOC_INPUT_ORDERS to try to see what is the difference, and it will stop at my breakpoint in WE19 and in RBDAPP01. But, when using we16, it will not stop at the breakpoint, even if it is hardcoded (BREAK-POINT) in the code, and if I have Update Debugging turned On. Does anyone know how I can debug what is making it stay in status 64 via we16? It is doing a lot of object oriented code, and I am guessing that it is using BOR IDOC and maybe creating a background process using the workflow id - not sure though.

Any help would be much appreciated!!!

Thanks, Fay

[Former Member]

Hi,

I have added some code to IDOC_INPUT_ORDERS, and when I execute WE16, the IDOC gets stuck in status 64. When, I comment out my code, it successfully completes to status 53. I can run the IDOC stuck in status 64 through program RBDAPP01, and it successfully completes to status 53. If I run an IDOC through WE19, it successfully completes to status 53. If I comment out my code, the IDOC successfully completes to status 53 via transaction we16. I put a breakpoint in IDOC_INPUT_ORDERS to try to see what is the difference, and it will stop at my breakpoint in WE19 and in RBDAPP01. But, when using we16, it will not stop at the breakpoint, even if it is hardcoded (BREAK-POINT) in the code, and if I have Update Debugging turned On. Does anyone know how I can debug what is making it stay in status 64 via we16? It is doing a lot of object oriented code, and I am guessing that it is using BOR IDOC and maybe creating a background process using the workflow id - not sure though.

Any help would be much appreciated!!!

Thanks, Fay

[Former Member]

Hi Fay,

I always use standard program <b>RSEINB00</b> instead of WE16 to process IDoc inbound file. WE16 is a test tool.

Hope this will help.

Regards,

Ferry Lianto

[Former Member]

Hi, Ferry.

This is very good to know. I will use this from now on.

But, in this case, unfortunately, it too is putting the IDOC into status 64 like we16 does, and it too does not stop at my breakpoint in IDOCS_INPUT_ORDERS. But, when I run the IDOC via RBDAPP01, it successfully completes to status 53, and stops at my breakpoint.

Is there a way I can debug IDOC_INPUT_ORDERS from RSEINB00?

Thanks again, Fay

[Former Member]

Hi Fay,

Yes, you can debug from program RSEINB00.

But you need to setup the inbound partner profile (WE20) to trigger immediately instead of by background job (under processing by function module). Then when you run program RSEINB00 in debug mode, just set the break point at function module IDOC_INPUT_ORDERS.

Otherwise, if you setup to trigger by background job then you debug from program RBDAPP01 as you did already.

Again, hope this will help.

Regarsd,

Ferry Lianto

[Former Member]

Hi, Ferry.

I just now checked WE20, and the inbound partner profile is set to trigger immediately already.

Should I check any other parameters also?

Thanks again for your help,

Fay