ALE Configuaration

[Former Member]

hi all,

where we can configure ALE,what are the setting for that?

Regards,

siva,

[claudia_neudeck · Accepted solution]

Dear Customer,

ALE can used for diferent thinks.

You should have a look in the onlinedocumentation:

http://help.sap.com

One Example is to synchronize the customizing for 2 systems. But this is only one example where you can use ALE.

Synchronizing Customizing Data Between Systems

Use

In ALE Administration you can synchronize Customizing data of Customizing objects between systems.

Customizing objects are assigned to distribution groups and transported to the participating systems in transport requests. You have to define distribution groups in Customizing for ALE.

For more information about this topic see Synchronizing Customizing Data Between Systems.

Prerequisites

You have created distribution groups in Customizing for ALE and carried out modeling.

Modeling and Implementing Business Processes

Synchronization of Customizing Data

Procedure

To synchronize Customizing data you have to execute the functions below in both the sending and the receiving systems: Choose Tools ® ALE ® Services ® Customizing Data ® ALE Requests:

In the sending system:

Display outbound ALE Requests

Under Display outbound requests you can display the status details of ALE transport requests for a specified time period for each distribution group and target system.

Generate ALE requests

Under Generate using the selection options and parameters you can generate ALE transport requests and IDocs that notify the receiving systems.

Note on field CTS dummy system

The CTS requires information on the target system, even though in this ALE case, this information is not used because ALE controls the distribution through the info-IDoc itself. Enter an "empty pseudo system" to which usually no transports are made.

Notes on the objects:

Customizing data is assigned to Customizing objects and types are assigned to Customizing objects. Depending on this type, problems could arise when transport requests are generated:

Object Type

Notes

L Logical transport object

No problems

S Table (with text table)

No problems

T Single transaction object

Works with restrictions

(no standard type of request generation defined, no line selection)

V View

Usually no problems

but no line selection possible with objects that are not linked (e.g. SADR* tables).

The objects selected in the system from the Customizing requests which were included in the ALE request and recorded in the request documentation.

In the receiving system:

Display inbound ALE requests

In Display inbound requests you can display the ALE requests and their import status for a specified time period for each distribution group and source system.

Import ALE requests

Under Import you can transport source requests for a specified time period for each distribution group.

Consolidate and forward ALE requests

Under Consolidate you can create a consolidation request from several ALE requests. The consolidation request is used to transport Customizing data imported by ALE requests into quality and production systems.

You can only execute this function in Customizing Systems in which Customizing data has been imported by ALE transports.

The function generates a standard Customizing request that has not been released. The user of the function is also the owner of the consolidation request.

Result

The Customizing objects are identical in all individual systems in your ALE integrated system.

Hope that the information are helpful.

regards

Claudia

[Former Member]

Dear

The ALE can be understanded as a bridge between two systems.It can be SAP or non-SAP.

[iamhe7806]

Hi Stephen,

I am talking about IDOC configuration within same client

Can you anyway help me out on the problem stated above

Regards,

Amit

[Former Member]

Hi,

There are some basic settings that are required for configuring ALE

-> Creation of the Logical system(BD54)

-> Assignment of the client to the Logical system(SCC4)

->Creation of RFC Destination(SM59)

->Creation of Port(WE21)

->Creation of Partner Profile(WE20)

->Distribution Model(BD64)

Thanks

Krithika

[iamhe7806]

Hi Kirthika,

It will be nice if you please help me finding the flaws in my configuration that is not allowing me to get a desired output.

Let me make it step by step:-

1. My desired output:- To see destination partner type as "LI/LF/ vendor name" for the Inbound IDOCs when an IDOC is starts it journey from "KU/WE/customer name" or vice versa

2. Present output:- Inbound IDOC always comes to "LS/ /TS90CLNT800". It means in my case inbound IDOC always comes to Logical System LS instead of LI or KU

How to configure it properly so that I can pass the Inbound IDOCS to other partner type except LS.

Please help.

Here what I have done so far as setting:-

1. Created a Logical System TS90CLNT800 using transaction SALE

2. Assigned it with client 8003. Created one RFC named tZRFC with connection Type "3"

(R/3 connection) using trxn SM59

4. Created a port ZEDI and assiged tZRFC using trxn WE21

5. Created partner profile for Vendors in partner type LI and for Customer in partner type KU

6. Because of getting error " no partner profile for ZEDI LS found" therefore created inbound parameters in parter profile LS for each Message Type.

I am processing IDOC within same client 800 ( both inbound and Outbound)

But I want the Inbound Idocs should come into partner type LI if the the Outbound IDOC is sent from KU and vice versa.

Please help me what config I need to do.

Amit

[Former Member]

Hi,

This is configured under the t.code SALE where you can see everything related to this.

This is purely a techincal job involves both ABAP and Basis expertise majorly.

Regards

vK