IDX1 - Port for Subsystem?!

[Former Member]

Hi guys,

well i gonna receive an IDoc from EDI-Server in native IDoc-Format. This i want to just route through without mapping (IDoc-Tunnel).

a. In IDX2 i imported the meta-data for the IDocs which will be received.

b. I made a RFC-Connection Type T pointing to a registerd Server-Program (Connection Test etc. works fine)

b. in IB Design i imported the IDocs

c. in IB Directory i configured a Sender-Channel

When we try to send an IDoc to XI, in my understanding the IDoc-Adapter listens on the RFC and will work with the IDoc. But i guess we forgot sth. because we receiver this error:

<i>Code 3 (RFC_SYS_EXCEPTION) reported from RFC interface at RfcIndirectCall(IDOC_INBOUND_ASYNCHRONOUS) with TID=0A5E0F0B3E94470D2F67173F

rfc_error_info.message="Transaction IDX1: Port EDI_Test, client 100, RFC destination contain errors"</i>

In the Idoc we posted EDI_Test in the Header-Data for SNDPOR. This error seems to point to IDX1 entry but what should i enter there?! Because the Client is mandatory...

Could u give me a hand?! What is wrong in my understanding?!

br

[Former Member]

someone?!

[Former Member]

Carsten,

To understand the concept of PORT, i will give one example which will help you to undersatand when and where we should create the PORT.

<b>Example:</b> When ever YOU (any system) <b>CALLS</b> to some of your friends (some other system) then YOU should have his number (let's say PORT), but it's not important whether he is having your number (PORT) or not?

I hope it will make you clear about the port creation.

Regards,

Sarvesh

***Reward points if it helped you.

[Former Member]

Well ok, i got it - i really appreciate ur help!!

But how to explain the error when the EDI-Program sends an IDoc in native to XI:

<i>Code 3 (RFC_SYS_EXCEPTION) reported from RFC interface at RfcIndirectCall(IDOC_INBOUND_ASYNCHRONOUS) with TID=0A5E0F0B3E94470D2F67173F

rfc_error_info.message="Transaction IDX1: Port EDI_Test, client 100, RFC destination contain errors"</i>

Because IDocs should be accapted it would be obvious to see it in Monitor. But there is nothing!

Any explanation?!

[Former Member]

someone?!

[Former Member]

Carsten,

1. Since EDI is a third party and hence your scenario becomes B2B i.e. outside the firewall, so in most of the case where EDI gets involved people use <b>Seaburger adapter</b> to communicate between EDI and XI.

2. Can you explain how EDI is sending IDOC to XI. Please define all steps involved.

Regards,

Sarvesh

[Former Member]

Sarvesh,

1. --> u r right for normal B2B as i have uesed it some time ago

2. Scenario is as follows:

Because our client has an independent EDI-Server he will use it a little longer than to do the EDI-part via XI. Therefore all incoming EDI-Messages are transformed to native IDoc and will be send to XI, where it will be tunneled and send to target SAP-System. XI here is only a part of monitoring. In the future, EDI-Server will be replaced by Seeburger-Adapter....

So i only need to get/send the IDoc from EDI to XI in native format. But the problem is that the IDoc is not appearing in monitor even though the Sender IDoc-Adapter listens....

br

[Former Member]

Hey Carsten,

just go through this blog and see if you have missed something.

/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact

Also go through this one:

/people/lionel.biennier/blog/2006/07/21/sap-xi-supports-edi-x12

Regards,

Sarvesh

Message was edited by:

Sarvesh Singh

[Former Member]

Carsten,

Just go through this blog by Michal. It's about IDOC tunneling.

/people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get

As mentioned in this blow about setting the XML_CONVERSION parameter to value 2. So plz check if you have done the same.

Regards,

Sarvesh

***Reward Points, if it helped you.

[Former Member]

Hi Carsten,

you said above,EDI server >XI> SAP R/3

I am just wondering why would you need XI in between EDI SERVER and SAP R/3 when you are able to get native IDOC format,which is nothing but a flat file structures as IDOC.you can push directly to SAP R/3 right?

and in general EDI sybsystems use FILE ports ,rather than tRFC ports.

I am just talking about in general approaches.may be your requirement is different.

may be I might be wrong.

-

---

And if it is with XI ,can you try using FILE port using WE21 on XI ather than IDX1.

thank you,

Babu sri

[Former Member]

Hi Babu, well were thinking about monitoring issues to use XI - but its IDoc Tunnel - i don't know if the IDoc will appear in monitor.

> And if it is with XI ,can you try using FILE port

> using WE21 on XI ather than IDX1.

>

> thank you,

>

> Babu sri

U mean we should enter the port in IDoc Header-Segments for sending via IDoc Tunnel to target R/3?! This will work?!

br

[Former Member]

Hi,

Carsten as i have given on blog in my previous reply, Just go through the "comments section of this blog (at the end ) " here you will find few ques and their ans. There is one very intersting ans as <b>"I am wondering though, when you do this, do you still use the tRFC port in WE21 and a standard RFC R/3 connection in SM59? I am trying to do this using the XML HTTP port and HTTP to R/3 System RFC"</b>. I think this make sense.

Also you won't be able to see your message in moni in case of idoc tunneling.

Regards,

Sarvesh

[Former Member]

Carsten,

my point was creating FILE port in XI for EDI serverXI-R3,not in the IDOC header segments.but now,for me it sounds like wrong,I mean creating file port in XI.

if so how data can be picked by XI from EDI server!!!

I got doubt whether can we do IDOC tunneling even between EDI SERVER-XIR3

after looking at this blog

/people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get

looks like only between SAPXI--SAP .

may I know how you approached with your design?

thank you.

Babu Sri

[Former Member]

Hi Sarvesh, well i am nearly desperate on this.

We have to use tRFC because of a Unix-Program on the EDIServer which connects to the RFC-Destination. As described, the connection seems to work.

However, because i am not able to test sending an IDoc from the EDI-System on my own i always have to check the EDI-Guy to send data for testing purposes. Well it's not working yet and i am still not getting what might be wrong.

Even when i give the SNDPOR from WE21 in target R/3 its not working and we get always the same Error message. Again i gonna list what i have done:

<<[all motivated by the IDoc-Tunneling blog from Michal]>>

a. Port added in IDX1 , called EDI_Test and Imported IDoc-Metadata from another R/3 System in IDX2

b. I created a RFC-Connection Type T pointing to a registerd Server-Program (Connection Test etc. works fine)

b. in IB Design i imported the IDocs

c. in IB Directory i configured a Sender-Channel

The EDI-Guy i gave the port-name in XI called EDI_Test but i guess he don't have to use this. Instead he should use Port from target R/3?!

Target R/3 configuration:

a. Working RFC-Connection to XI

b. WE21 'ZXI' for connecting to XI-System

c. WE20 Partner-Type LS, called EDI with outbound-parameter DESADV

So do u think port ZXI should be entered by EDI-Guy for sending the IDoc to Target via XI?!

sorry for my disqualification but its first time i deal with this scenario....

br

[Former Member]

Hi,

"b. I created a RFC-Connection Type T pointing to a registerd Server-Program (Connection Test etc. works fine)" is this on XI and RFC dest pointing to R3

I think type not "T" for IDOCS,its is "3"

"We have to use tRFC because of a Unix-Program on the EDIServer which connects to the RFC-Destination. As described, the connection seems to work."

is this RFCdest on XI?and script ablet o push data from EDI server to XI?

thank you.

[Former Member]

Hi Babu,

well in XI there is this RFC-Dest of Type T which points to a server program of the Unix-Level on EDI-Server.

br

[Former Member]

Carsten,

Kindly check the port mentioned in IDX1 is correct or not? and also test if it is working fine.

Regards,

Sarvesh

[Former Member]

Hi, well thats the point. This port doesn't exists because when i would like to enter a port for EDI_Test (Thid-Party System) i have to enter a client. But this system is no SAP-System!

Or should i enter a port in IB Directory which points to the final system?!

Communication is:

EDISERVER--> XI --> R/3

Please help!

br

[bhavesh_kantilal]

Hi,

Let the client have any value ( say 000 ). Create the port in IDX1 as EDI_Test with Client as 000.

In IDX2, if you cannot load the Idoc metadata (as it is non SAP ), copy the Idoc metadata from someother SAP System's port manually in IDX2

Regards

Bhavesh

[Former Member]

Bhavesh,

Ok i would like to follow ur instructions but the port has to reference an RFC-Destination of Type 3 (ABAP-Connection). But we have type T (TCP/IP). how to solve this?!

In general: When i get the IDoc from EDI does it have to point to a port of XI-System? Or to a port concerning the target-System?!

please help!

br

[Former Member]

Carsten it should point to target system i.e. R/3.

Regards,

Sarvesh