cancel
Showing results for 
Search instead for 
Did you mean: 

Transport abt ALE Config

Former Member
0 Kudos

Hi,

We have done all IDOC to File scenarios

We have configured the ALE settings on SAP R/3's DEv server.

Can i transport these Config to SAP R/3's QTY Server or Should i create them as it is appear in the SAP R/3's DEV server???

Regards

Suman

Accepted Solutions (1)

Accepted Solutions (1)

turmoll
Active Contributor
0 Kudos

Depends ...

e.g. ports, RFC destinations, partner profiles, distribution models etc. will have to be created in Q

e.g. new Z message types, Idocs extensions, new Z segments, etc. will be transported

Regards,

Jakub

Answers (3)

Answers (3)

Former Member
0 Kudos

Ans

former_member240483
Contributor
0 Kudos

Hi there,

You have to create ports partner porofiles and RFC destinations.

regrads

Rao

Former Member
0 Kudos

Hi,

Any Clues

Regards

Suman

former_member238007
Contributor
0 Kudos

Hi Suman..

This was the ALE settings...

Steps

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 – 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.\

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

/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi

regards,

Kishore