cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with IDOC

Former Member
0 Kudos

Hi There,

Im triggering a Basic IDOC from one system to the other system,

One system is R/3 system and the other is PI system.

But these both are having same client 100.

When working on with the IDOCs we need to create a logical sender system and the receiver system of R/3 and logical sender and logical receiver for the PI.

But as these two belong to the same client, we are unable to create 2 logical systems.

We are unable to make a cross connection between these two systems.

Could you please help us in this regard.

Thanks in Advance

Divya

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

hi divya,

1) in r/3 side:-

u create logical system for the r/3 system and assigne this logical system to the client (100) there in r/3. but here this client belong to r/3 system and does not vaving any relation ship with pi logical system.

here in r/3 u just need to maintain the logical system name of ur pi system and need not to be assigne to any client.

similarlly at pi side u have to create logical system name for ur pi system and need to assigne the client (100 if PI sys) . here also u need to maintain the logical system name for both the systemr/3 and pi.

regards,

navneet

Former Member
0 Kudos

Navneet,

How can we create a logical system without giving the client?

Even if we do so, what is the purpose of creating the logical system.

There should be some cross client connection.

Without giving the client, how can we go with creating partner profiles?

Former Member
0 Kudos

hi,

u need to just maintained the logical system of partner and no client should be assigmened to it.

this is just to maintaine the record for the partner system.. and dont be used for any configuration..

all the configuration is done like rfc destination ,pp, port around the logical system of the its won.

regards,

navneet

Former Member
0 Kudos

Hi Divya,

One hint - you have probably forgotten BD64 Just having a destination in SM59 does not help. You need to specify what IDocs should be send to the remote system (Inbound). The Distribution Model tells your SAP ECC system how the communication has to run.

In BD64 you can lay down this communication by specifying that your IDoc has to go FROM System A TO System B.

T00th

Former Member
0 Kudos

Yes Sameer,

As you said i havent done with the BD64 model view connection, but still stucked up with the same error.

As Navneet previously said, we have done with giving the logical systems without assigning the client to it.

But even this dint solve our problem.

Kindly let me know if there is any other alternative.

Thanks in advance

Former Member
0 Kudos

hi Divya,

if u r deling with one sender and one receiver and if u r configuring r/3 to xi using IDOC than in that case BD64 doen't required.

please check ur rfc destination is configured properly or not...

regards

navneet

Former Member
0 Kudos

hi divya,

please close the thread if u got the ans....

regards,

navneet

Answers (3)

Answers (3)

Former Member
0 Kudos

Thanks everyone for the help.

Regards,

Divya

Former Member
0 Kudos

Hi Divya,

From R/3 side check the following:

1. In WE20 check whether the port number you have provided under Outbound Idoc is correct.

2. In WE21 check whether the RFC in the above mentioned Port has credentails that are pointing to XI or not.

3. In WE19 check the control records which you have used for triggering the IDOC.

4. In SM58 check if any log is created.

-Indrani.

prateek
Active Contributor
0 Kudos

But these both are having same client 100.

Does not matter. Just create one logical system for each sender and PI system. Thats it.

Regards,

Prateek

Former Member
0 Kudos

Yes i have create one logical system and triggered the IDOC.

Its giving me an error like:

IDOC has been saved, but it cannot or should not be sent.