Skip to Content
author's profile photo Former Member
Former Member

Ale tutorial...

Hi All,

Can you please give me step by step ale toturial.



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on Oct 05, 2006 at 10:13 AM

    pls give ur email ID.

    i will send u.

    if hlped mark points



    <b>pls check ur mail box.</b>

    if hlped pls mark points

    Message was edited by: Anversha s

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 05, 2006 at 10:15 AM

    Have a look at below steps:

    Might be useful to you.

    Let us assume we are working with two clients namely Client 100 and Client 200

    System Name : cysap03

    The settings for Decentralized Sales and Centralized Shipping are Done in

    Following Manner.

    The Receiving System is Client 100 and Sending System is client 200 i.e.

    Sales Order created in client 200 initiates a Purchase Order automatically.

    This P.O. is send to client 100 as a Sales Order.

    The following is the step-by-step procedure:


    To do setup the Logical System follow the following steps

    In IMG Settings

    Cross Applications &#61664;&#61472;Distribution (ALE) &#61664;&#61472;Basic Cofiguration.

    Set up ‘Logical System &#61664;&#61472;Maintain Logical System.

    Create New Entries (Eg. ALEINSO receiving system)

    (ALEPOOUT sending system)

    2) ALLOCATE the created logical systems to respective clients.

    ALEINSO assign to client 100

    ALEPOOUT assign to client 200

    3) DEFINE the RFC Destination. Do the following.

    Cross Application &#61664;&#61472;Distribution (ALE)&#61664;Communication.

    Execute RFC Destination.

    Create for R/3 Connections ALEINSO in RFC destination box. Connection

    type as 3.

    Give Target machine as cysap03.

    User: User11 (This is the logon for dist.)

    Client : 100

    Password: *** Enter the client logon password.

    Test connection and remote logon to verify.

    Repeat this procedure for ALEPOOUT for client 200.

    4) Distributing the Customer Model

    &#61656;&#61472;Execute Maintain customer distribution model directly for creating the customer


    &#61656;&#61472;Specify the source logical system (ALEPOOUT) and Create a customer model

    name. (POOUT).

    &#61656;&#61472;Select the target logical system (ALEINSO) from the list.

    &#61656;&#61472;Create Message Type.

    &#61656;&#61472;In the resulting screen, in log message type enter ORDERS, ORDCHG,


    &#61656;&#61472;Transfer and Save.

    &#61656;&#61472;Distribute customer model on the previous screen

    5) Generate Partner Profiles using Cross Application à

    Distribution (ALE)àDistribution Customer Model

    Select generate partner profiles. In customer model box enter the model name that

    you created (POOUT).

    You should get a screen mentioning successful creation of customer model in green


    6) Distribute The Customer Model Again

    Use Customer Model (ALEPOOUT) and Receiving System as (ALEINSO).

    On execution you get the following message

    copy with RFC destination ALEINSO

    model data sent successfully.

    7) Log on to client 100.

    Cross applications&#61664;Distribution ALE&#61664;Communications&#61664;&#61472;generate partner

    profiles for customer model (POOUT).

    The system tells whether inbound parameters have been created or not.

    Besides the above settings Check the following settings and if required do them.

    1) CHECK ISO settings for Currency ,

    Unit of measure in Cross Applications &#61664;&#61472;Distribution (ALE) &#61664;&#61472;Basic Configuration

    &#61664;&#61472;CHECK ISO settings

    a) Currency. Check whether the currency is existing for ISO code.

    b) Unit of Dimension Check whether the unit of measurement is existing, if

    so in the detail screen enter the ISO code and mark the primary code field .

    2) Check ALE Consistency checking in SET UP Sale scenarios.

    3) Set the message types of the sending system for ALE medium in the sending


    Sending System

    Once the settings are through Execute the transaction completely (i.e. S.O.


    Check whether the Idoc has been created and whether it is at the port.

    Dispatch the Idoc using the following path

    Logistics&#61664;Center Functions&#61664;&#61472;Period. Work &#61664;&#61472;Check Idoc Dispatch.

    Receiving System

    Check Whether Idoc has been posted in the application

    Logistics&#61664;Center Functions&#61664;Monitoring &#61664;Idoc Overview

    If the Idoc has not been posted then it can be checked why it is not been posted by


    The path is

    Tools &#61664;Administration&#61664;Process Technology &#61664;&#61472;Idoc &#61664;Idoc Basis&#61664;&#61472;Test &#61664;

    Test Tool

    Here enter the Idoc no and create it.

    On the next screen Function module name has to be entered in debugging mode.

    Best Regards,


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.