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: 

IDOC not sent to receiving server

Former Member
0 Kudos

in source clientZ1, we maintain RFC connection RZ1, RZ1 is pointing to the target client Z2 's IP address

in target client Z2, we maintain the RFC connection RZ1, it is the same as source client, RZ1 is assigned to WE21 for port A000000004

when I runWE19 for IDOC 20001 in source client Z1, I click pushbutton "stanadrd oubound processing", IDOC 200076 is generated, these two idocs can be seen from Z1, but I can't see idoc 2000076 in Z2 client(which is target client), why?

how to see idoc 2000076 in Z2?

8 REPLIES 8

soumya_jose3
Active Contributor
0 Kudos

Hi,

Check the status of idoc 200076 in Z1 using tcode WE02. If it is in status '03' (data passed to port ok), the idoc must have reached the destination Z2. Note that the idoc number in Z2 destination might not be the same as 200076. A different idoc number must have been generated in Z2.

Regards,

Soumya.

0 Kudos

Check the status of idoc 200076 in Z1 using tcode WE02. If it is in status '03' (data passed to port ok), the idoc must have reached the destination Z2.

@Soumya: Not true at all. You should be running the dispatch checking program, RBDMOIND. An '03' status IDOC could be stuck in the tRFC queue of the outbound system. The dispatch update program checks this state and converts the status to '12 - Dispatch OK'.

0 Kudos

Source clien Z1: IDOC 20001 status is 30, partner no: Z2, port: A000001, generated in Apr.2010,

IDOC 20076 status is 03, partner no: Z2, port: A000001, generated in March, 2011

I click pushbutton "stanadrd oubound processing" to generate 20076, but in Z2, we can't see 20076, I think my configuration in Z2 is not correct,

in Z2, WE21 is pointing to Z2(which is himself), should we change to Z1?

+++++++++++++++++++++++++

in source clientZ1, we maintain RFC connection RZ1, RZ1 is pointing to the target client Z2 's IP address

in target client Z2, we maintain the RFC connection RZ1, it is the same as source client, RZ1 is assigned to WE21 for port A000000004

when I runWE19 for IDOC 20001 in source client Z1, I click pushbutton "stanadrd oubound processing", IDOC 200076 is generated, these two idocs can be seen from Z1, but I can't see idoc 2000076 in Z2 client(which is target client), why?

how to see idoc 2000076 in Z2?

0 Kudos

furthermore, in Z2, we didn't maintain partner profile for Z1, we only maintain RFC to point to Z1

but in Z1, we maintain partner profile for Z2

0 Kudos

Check SM58 tcode in Z1, idoc might be hanging up there or must be in some error, just push it manually or use program RSARFCEX to push it.

0 Kudos

no. SM58 shows nothing for the past of five years.

should we create partner profile in Z2 (inbound) ? when I add a partner profile, it says : partner number not valid for partner type LS, how to add a new partner number?

since 200001 IDOC has been used, how to create a idoc for we19 testing? or can we reverse back 2000076, and use 200001 for the second test?

0 Kudos

Yes, of course, you have to maintain a logical system for the sending system in the inbound client and also configure the inbound settings in the partner profile; otherwise, your system has no clue what to to with the IDOC transmission.

Former Member
0 Kudos

closed