cancel
Showing results for 
Search instead for 
Did you mean: 

IDOCS not reaching XI (IDEX-GE Content)

Former Member
0 Kudos

If I send IDOCS from I/SU to XI no IDOC is reaching XI.

IDX5 doesn't show any incoming IDOC. There is no error neither in XI nor in the log viewer of Visual Administrator.

The Sender system says in WE02: Datatransfer to port ok.

I checked the port and its RFC: The correct RFC (the one to XI) is set and RFC is working (sm59: test connection is ok, Remote Login from I/SU to XI is working).

IDOCS from a second backend are visible in IDX5. This backend is configured like the first backend (same RFC).

Did anyone have a solution?

Thanks

Ralf

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

use we14 transaction to dispatch the idoc,

then check the sm58, if nothing apperas in sm58 then check the status in we05,

that will give u correct info about idoc status..

try this out..

Former Member
0 Kudos

as per the above reply ur target system isnt defined correctly..thats why its not able to recognize the idoc ..

for an R3 idoc sender system u need to do ALE configurations,

that comprises of (defining target system[logical system] in SALE txn, partner profile, RFC destination,distribution model [model view] SALE txn) ..

Former Member
0 Kudos

If I compare the settings in SALE with the backend that works with XI I cannot find any mistakes but I agree that there has to be one or more!

Former Member
0 Kudos

generally when it says <i>data passed to the port</i> and when u stil r not able to view idoc ,

its all bcos either partner profile is wrong or target system not defined correctly,

so check it as some configuration at sender is missing

vikas_agarwal
Contributor
0 Kudos

Hi,

These are the complete steps for IDoc communication, check if you have missed any one...

SAP XI

1) RFC Destination (SM59)

a) Choose create.

b) Specify the name of the RFC destination

c) Select connection type as 3 and save

d) In the technical settings tab enter the details SAP SID/URL and system number#.

e) Enter the Gateway host as same details above SID/URL.

f) Gateway service is 3300+system number#.

g) In the Logon /Security tab, enter the client user & Password details of Destination system.

h) Test the connection and remote logon.

2) Create Port (IDX1)

a) Select create new button

b) Enter the port name as SAP+SID (The starting char should be SAP)

c) Enter the destination client.

d) Enter the RFC Destination created in SAP R/3 towards other system.

e) Save

3) Load Meta Data for IDOC (IDX2) a) Create new

b) IDOC Message Type

c) Enter port created in IDX1.

SAP R/3

1) RFC Destination (SM59)

a) Choose create.

b) Specify the name of the RFC destination

c) Select connection type as 3 and save

d) In the technical settings tab enter the details SAP SID/URL and system number#.

e) Enter the Gateway host as same details above SID/URL.

f) Gateway service is 3300+system number#.

g) In the Logon /Security tab, enter the client user & Password details of Destination system.

h) Test the connection and remote logon.

2) Create Port (We21)

a) First Select Transactional RFC and then click create button

b) Enter the destination port name as SAP+SID (The starting char should be SAP)

c) Enter the destination client.

d) Enter the RFC Destination created in SAP R/3 towards other system.

e) Save

3) Create Partner Profile (WE20)

a) Create New

b) Create the Partner no. name as same the logical system name of the destination system.

c) Select Partner type LS

d) Enter details for Type: US/USER, Agent, and Lang.

e) Click on the + button to select the message type.

f) Select Partner no. and LS which ever create above.

g) Select Message type

h) Select Process code related to the Message type.

I) save.

In SLD

TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system

Name.

BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.

Check these steps

Regards

Vikas

Former Member
0 Kudos

Hi,

I found it!!!!

In IDX1 the name of the port was not correct. We named it SAPXXX_yyy where XXX was the system and yyy the client.

The system made SAPXXX_yyy_yyy of it and could not use the port.

Thanks for your good advices!!

Bye

Ralf

Former Member
0 Kudos

Thanks for your immediate response!

I think so. The RFC, that is behind the port lead to XI. I could proof that by using Remote Login in sm59: I got an ABAP-Login in the Integration Engine.

I came to TA SM59 by doubleclicking the RFC Destination in the port settings. So destination and user/password settings registered seem to be correct.

Former Member
0 Kudos

have u made settings in IDX1 and IDX2? for port and IDoc

please check it out.

RP

Former Member
0 Kudos

I checked out IDX1 and idx2 in the integration engine.

There are settings in idx1: RFC is leading to the correct backend (Test is ok, remote login not possible because reg user is not a dialog user).

idx2 show the idoc-Types and the client.

former_member214364
Active Contributor
0 Kudos

Hi Ralf,

Could you please execute SM58 tcode in ISU and try to find if there are any errors

Cheers,

Jag

Former Member
0 Kudos

Yeah! a first error message:

TA sm58 says:

No target system

No IDOC to process

Former Member
0 Kudos

Hi Ralf,

A small suggestion: Could you please check the RFC destination in your partner profile.. Is it targeting to XI Integration Engine.

Regards

Pushkar