Application Development and Automation 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: 
Read only

Debug in target client being in source client

Former Member
0 Likes
777

Hi,

I am facing problem where i am trying to replicate inbound delivery to different client (same box different client) and it suppose to do something which is not doing correctly, IDOC is successful but inbound delivery not getting replicating.

is there a way where i can debug in target system as soon as i trigger inbound delivery IDOC in source system?

Thanks

sarath

4 REPLIES 4
Read only

vijaymanikandan
Contributor
0 Likes
686

HI,

In the we20 partner settings you can change the posting for this message type to post by background program and then use BD87 to post the IDOC in the target client and you can debug as well.

Hope this solves the problem.

Regards,

Vijay V

Read only

Former Member
0 Likes
686

Vijay thanks for mail.

I don't think its going to work as I am using ALE technic and BAPI its being called first creating Inbound Delivery and then triggering IDOC. So in my case Inbound delivery is not getting created but IDOC is successsful, means I need to have break point even before BAPI touches IDOC.

Thanks

Sarath

Read only

0 Likes
686

Hi

Can you explain more about your scenario.

Changing the IDOC posting to foreground and then debugging must work. The Idoc will remain in status 64 and it is still not posted. Now if you know the Inbound function module then you can set a breakpoint on that and then try to process the IDOC via BD87. This will work and you will know the reason why your Delivery is not created

Regards

Vijay V

Read only

Harsh_Bansal
Contributor
0 Likes
686

Hi,

Place breakpoint in Inbound FM in your Target system.

Now take an IDOC number...goto WE19 (IDOC test tool)

Now do the standard inbound for that idoc, you can debug now.

Regards,

Harsh Bansal