cancel
Showing results for 
Search instead for 
Did you mean: 

Configuring scenario to add Sender Party to a message from an IDoc

Former Member
0 Kudos

I want to make sure that when an IDoc is received in the XI system, the message Sender Party is populated. Currently I am trying to do this by associating the IDoc communication channel with a Business Service with a party. I was expecting that this would then force the message to adapt that party as the sender party, but this does not seem to be working.

In the header of the xml message I get this:

<SAP:Sender>

<SAP:Service>EQ1CLNT210</SAP:Service>

<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">ZINVOIC_CU.INVOIC02</SAP:Interface>

</SAP:Sender>

EQ1CLNT210 is the system that the IDoc is sent from, but the Service with Party that I am using has no <Party> subelement in the <Sender> element.

Am I doing this correct, or am I missing a step?

BR,

Tony.

Accepted Solutions (0)

Answers (3)

Answers (3)

prateek
Active Contributor
0 Kudos

U have to configure Business System of type Web AS ABAP for the idoc communication.

Regards,

Prateek

Former Member
0 Kudos

Please cross check your steps with the list below,

if the problem persists, check the metadata

For File to IDOC,

in R/3

1.create rfc connection using sm59

2.create Logical sys using bd54

3.create port using we21

4.create partner profile using we20

in xi

1.create rfc connection using sm59

2.create Logical sys using bd54

3.create port using IDX!

for IDOC to FIle

R/3 side

1.create rfc connection using sm59

2.create Logical sys using bd54

3.create port using we21

4.create partner profile using we20

5.distribute busynessmodel using bd64

for xi side

1.create rfc connection using sm59

2.create Logical sys using bd54

3.create port using IDX!

4.create partner profile using we20

ALE configuration for pushing idocs from SAP to XI

/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

IDOC testing using WE19

/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi

File To IDOC - Part1 (SLD and Design):

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&

File To IDOC - Part2 (Configuration):

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&

File To IDOC - Part3 (Steps required in XI and R3):

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&

SAP R/3

R/3 to 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 (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.

XI to 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 (IDX1) ( Create port to get IDOC Meta data from sender system)

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) (To maintain IDOC Metadata, it is needed by XI because XI needs to construct IDOC-XML from IDOC. It is not needed by any sap system).

a) Create new

b) IDOC Message Type

c) Enter port created in IDX1.

Former Member
0 Kudos

Hi Tony,

Just check out the steps once again.

Plz check out the link ..its very useful for your scenario.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c...

Hope this will help you..you can revert back for further queries.

Plz reward with points in case you are satisfied.

Regards,

Sushama