ALE documents

[Former Member]

can anyone send me ALE related documents

[Former Member · Accepted solution]

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]

Hi chintoo candy,

You can search site scribd.com for such documentation.

Search for ALE IDOC Cookbook...good document.

Regards

Arpil

Dont Forget: *Reward POINTS!!!!*

[Former Member]

HI CHINTOO

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.

Reward `with points if found useful

regards

[Former Member]

'logical system' is used to identify an individual client in a system, for ALE

communication between SAP systems. That's why you see a field for 'logical system' in the client master data in SCC4 (table T000). You use logical systems in ALE config

Enterprise business objects of a SAP system are distributed with the help of BAPIs (Business Application Programming Interfaces). ALE acts as a layer that incorporates the inter-linking of business objects at the application level. The ALE layer provides the following services:

Applications services: this layer provides ALE with an interface (for instance: BAPI) to R/3 to facilitate data exchange to or from external R/3 systems.

Distribution services: the onus of filtering and converting messages exchanged between SAP and non-SAP systems is on the distribution layer of ALE. This service is the core service and acts as a sandwich layer between application and communication layers.

Communications services: ALE supports synchronous as well asynchronous communication. Synchronous messaging is used for the direct reading of control data, while asynchronous messaging is used for transmitting or receiving application data.

The implementation of ALE is achieved with the help of external converters (ALE converters), which connect SAP applications to non-SAP applications. In simple words, external converters are generic-format conversion programs, which contain specific converter functions. The capabilities of the external converter will be discussed later in this article.

http://help.sap.com/saphelp_sm32/helpdata/en/78/217df551ce11d189570000e829fbbd/content.htm

A partner profile is an identifier for the sending system that is used for communicating messages. You will be using LS as it is used for ALE communications. Every partner profile used for ALE must be based on existing LS

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

Please follow the below process for configuration:

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)&

Do the following settings:

Pre-requisites for Inbound IDoc to R/3 from PI:

Configuration required at Xi side:

Go to IDX1: configure the port.

Go to IDX2: load the DOC metadata.

Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system

Configiration required at R3 side:

Maintain Logical System for PI (SALE transaction):

Maintain Partner Profile for XI system(WE20):

Pre-requisites for Outbound IDoc from R/3 to PI:

Configurations required in R/3:

Maintain Logical System (SALE)

Define RFC Destination (SM59) which points to PI system

Maintain Port (WE21)

Maintain partner profile. (WE20):

Maintain Distribution Model (BD64):

If u r passing the same idoc strucutre to other R3 system then u can go for IDOC tunneling

IDOC Tunneling:

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

[Former Member]

Hi,

The IDoc interface exchanges business data with an external system.

The IDoc interface consists of the definition of a data structure, along with processing logic for this data structure.

The data structure is the IDoc. The IDoc is the exchange format common to all the communicating systems. You can specify exception handling in the SAP Business Workflow, with IDocs, without the data already having to exist as SAP application documents.

You need the IDoc interface in the following scenarios:

· Electronic data exchange (EDI)

· Connect other business application systems (e.g. PC applications, external Workflow tools) by IDoc

· Application Link Enabling (ALE).

Application Link Enabling (ALE) is a technology to create and run distributed applications.

refer the below link for more information:

http://help.sap.com/saphelp_nw04s/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm

ALE:

Purpose

Application Link Enabling ensures a distributed but integrated SAP installation. It comprises the controlled exchange of business messages and consistent data management in loosely-linked SAP application systems.

Functions

Applications are integrated by synchronous and asynchronous communication, not in a central database.

Application Link Enabling has three layers:

· Application services

· Distribution services

· Communication services

refer the below link for more information:

http://help.sap.com/saphelp_nw04s/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm

7 Steps For ALE Configuration :

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/abap/7%2bsteps%2bfor%2bale%2bconfiguration

Administration of ALE Functions :

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/snippets/administration%2bof%2bale%2bfunctions

XI or ALE....Which one is better ?

/people/aparna.chaganti2/blog/2007/02/06/xi-or-alewhich-one-is-better

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/609e6465-15de-2a10-859d-da7bcbca...

chirag