Single Host for netweaver/xi & Idoc settings in ale

[ravi_raman2]

HI,

In the case of a single system which is the R/3 system as well as the xi system...what settings are to be done from ALE to enable idoc processing...is this the same as a dual system configuration..or ?

I am pasting some of the steps suggested for the ale configuration.

Can anyone re-organize this or format this so that it applies for a single system that is the db host, Xi Host, and r/3 host.

There are several ways of doing it, all eventually leading to the same conclusion..but in the case of a non-distrubuted system, there are some differences..<b>Can someone put some clarity here</b>...as i have tried the steps and not all of them clearly apply in the case of a single host.

link1) https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&

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

3) ALE settings.==> Author( Raghavesh Reddy )

SAP XI1) 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 XI 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 – System Landscape Directory

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

Ts for Third Party (Logical system):-

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

BS for Third Party (Logical system):-Enter the XI logical system name.

In Transaction SALE

Define and Assign the logical system name.

[Former Member · Accepted solution]

If you want to configure your R/3 system to send IDocs to XI the first thing you have to do is configure the basic ALE:

<b>Logical System</b>

-Representation of a system R/3 will communicate with

-Every R/3 client used in ALE must have a logical system associated

-BD54 – change logical systems (add), SCC4 – change clients (attach logical system)

-Stored in tables TBDLS and TBDLST

<b>Ports</b>

-Logical representation of a communication channel

-How you refer tie together RFC destinations with partner system

-WE21 or WEDI

<b>Partner Profile</b>

-Ties together many pieces of the ALE puzzle

-Message types, IDoc types, process codes, partner functions, application identifiers, message function, output type, and port

-Maintain inbound and outbound parameters (partner type, port, transfer immediately or collect IDocs)

-WE20, WEDI, or SALE

-Viewed as a gateway, routes a particular message of a specific IDoc type to the given port and invoking the appropriate function modules

The next thing you have to do is configure the IDoc adapter in XI to prepare the system to accept IDoc's into the integration builder from other SAP systems.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6f...