Debuging IDOCS

[Former Member]

Hi,

Im making a test between two differents SAP systems by using CREMAS IDOCS.

To do that, I modified the code postal by XK02 and then, I created a outbound idoc by BD14 transaction (in source system)...

Where do I could put a break point in order to debug how the DESTINATION system receive and process the new idoc?

Thanks in advance for your help

Leandro.

[amit_khare]

By Using transaction code WE19 .. u can debug the idoc

WE19 (testing tool) is used to test an IDoc and also to simulate an IDoc error if occurs. WE19 is for testing, you can put in an existing Idoc number there and it will make a copy of that Idoc and keep your original Idoc intact.

Lets say you want to test if your function module is working fine, you can build or copy an idoc via WE19 and test.

You can also use BD87 to process an IDOC.

Also chk this thread.

~As found in forum

[Former Member]

Hi Amit Khare ,

Thanks for your quick answer.

I knew that WE19 can be use to test inbound idocs, but in this case is different because I have access to both systems: Source System and Target System.

Then, I want to make a complete test.

To do that, I create an idoc in Source system and I want to debug the receive idoc in target system.

As far as I understand, I get the 2 FM used to process inbound IDOCS type CREMAS:

IDOC_INPUT_CREDITOR

IDOC_INPUT_CREDITOR_MDM

And I set a break point in them. But when I send the idoc in the source system. The debug mode never starts...

Do you have any idea about that?

Thanks again,

Leandro

[Former Member]

You are sending the IDOC from the Source system, once it is passed to the Desination SAP system, the status will be 03 in the source, and it will be created as status 64 in destination system ( provided your Port definition, and RFC settings are correct. )

Now if in the Inbound partner profile in the Destination system, you have selected the batch option, instead of process immediately, the IDOC will stay in 64, else it will be processed automatically, and you will not be able to debug that.

the Status 64 IDOC, you can process using RBDAPP01 program, and if you have the break-point set in there ( destination SAP system ) it will stop at the break point.

[Former Member]

Hi MxG ,

Thanks for your answer.

These idocs are processed automatically.

The strange thing is following:

When I send the idoc in common way. A bug appears because even status result 51 it update postal code in destination system.

On the other hand, when I simulate the execution by WE19, status result 51 too but it doesn't update a thing.

Have you any idea about what could be?

Thanks again,

Leandro

[Former Member]

Whats the Process code and Function module you are using? if its custom, you need to check the code to see if there is commit somehwere in the code which does partial DB update

[Former Member]

Hi MxG

Im using standard function module IDOC_INPUT_CREDITOR. This Fm perform a call transaction to XK02. The strange thing is when I test by WE19 everything works fine ...

[Former Member]

Only thing I can suggest isd to debug one IDOC using RBDAPP01, and see what it is doing. There has to be something which is doing the commit somehwere to have the Postal code updated while putting the IDOC in 51. With XK01 I can think the address would be in General Data, so it migth be hitting Save after general Data before going to other Views - purchasing etc.

[Former Member]

Hi MxG

I found a commit inside an user exit.

this is probably the reason why update data even if status result 51.

thanks for your help

leandro

[Former Member]

Yep, tahts the reason. there shouldn't be that commit in the code. Thast why it is doing partial update even though IDOC is in error