topic logical system in Application Development and Automation Discussions

logical system

Former Member — Mon, 06 Mar 2006 14:33:56 GMT

Guy's i am new to ALE,IDOC,EDI

PLS tell me the step to create Logical system,message type

and IDOC STEP

Re: logical system

Former Member — Mon, 06 Mar 2006 14:45:19 GMT

SAP Documents - ALE

Application Linking and Enabling (ALE)

In this document you will learn the step-by-step procedure to setup the ALE system and

go through a transaction between to clients

For our purpose we have two clients namely Client 100 and Client 200.

System name is cysap03

1) SETUP LOGICAL SYSTEM: To do this follow the following steps

Tools à Business Engg à Customizing.

Click Enterprise IMG button.

Cross Applications à Distribution (ALE) à Basic

Configuration.

Set up ‘Logical System à Maintain Logical System.

Click New Entries Button (E.g. WalMart100 receiving

system)

(Walmart200 sending system)

Enter two logical system names and their description.

Save

Comeback to IMG setting screen.

2) Now you have to allocate the created logical systems to respective clients.

WalMart100 assign to client 100

WalMart200 assign to client 200

To do this, do the following.

Click Allocate logical system to the client.

Ignore the message that comes up on the screen.

Select client 100

SAP Documents - ALE

Click details button on the toolbar icon or press F2.

In the logical system box, enter WalMart100.

Click on the save Icon

Click the back button.

Now select client 200.

Click details icon or press f2.

In logical Systems box, enter WalMart200.

Save

Back.

Come back to the IMG settings screen.

Now define the RFC Destination. Do the following.

Click Cross Application Ü Distribution (ALE).

Click on communication.

Execute RFC Destination.

Click R/3 connections. (Expand it).

Put cursor on R/3 connection.

Click the create button.

Enter WalMart100 in RFC destination box.

Connection type 3

Give a description for the RFC destination.

Language E.

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

Client : 100

Password: Enter the client logon password.

SAP Documents - ALE

Save.

In target machine box enter cysap03 (This is the system

name)

Save.

Click on test connection and remote logon to verify.

Click on Back button.

Position your cursor on R/3 connection.

Click on create to do the above process for WalMart200

logical system for client 200.

Click on the back button.

Click on the distribution customer model.

Execute Maintain customer distribution model directly for

creating the customer model.

Put your cursor in Maintain customer distribution model

directly box.

Click Choose.

Specify the source logical system (WalMart200) and give a

customer model name. (ModelMar10)

Click on create icon.

Select the target logical system (WalMart100) from the list.

Click on create message type.

In the resulting screen, in log message type enter MATMAS.

Click on transfer.

Save.

SAP Documents - ALE

Back to IMG setting screen.

Click distribute customer model.

Select generate partner profiles and click choose.

In customer model box enter the model name that you

created (Modelmar10)

Click execute button.

You should get a screen mentioning successful creation of

customer model in green color.

Click back button

Select distribute customer model and click choose.

In the resulting screen enter customer model (Modelmar10)

Receiving logical system (WalMart200)

Click execute.

You get messages :

copy with RFC destination WalMart100

model data sent successfully.

Click back.

Now execute R/3 and login to client 100.

Execute transaction SPRO.

Click Cross applications à Distribution ALE

Communications à generate partner profiles.

Enter the customer Model (Modelmar10)

Execute

You should get all the resulting messages in green color.

SAP Documents - ALE

Switch back to client 200 Session.

Logistics à MM à Material master

Material à Create(General) à Immediately.

Enter the material name (mat1000)

Industry sector as M

Material Type as Fert.

Click Select views.

In the select views box for materials check basic data or any

other view(s)

Click enter icon.

In the next screen that you get

Give the text of the material

Base unit of measure as PC

In the description area language (E) and material

description.

Click Save.

Come back to the first screen of the session

Logistics à Central Functions à distribution

Master Data à Material à Send.

Enter the material name. (Mat1000)

Message type (Matmas)

Logical System (WalMart100- target logical system)

Click Execute.

SAP Documents - ALE

Switch to Client 100 session to verify.

Logistics à Material Management à Material Master.

Material à Display à Display Current.

Give the name of the material (Mat1000)

Click select views button.

You should get select views screen for the given

material.

Re: logical system

Former Member — Mon, 06 Mar 2006 14:46:10 GMT

SAP Document : ALE

APPLICATION LINKING ENABLING

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:

1) SETUP LOGICAL SYSTEM:

To do setup the Logical System follow the following steps

In IMG Settings

Cross Applications à Distribution (ALE) à Basic Cofiguration.

Set up ‘Logical System à 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 à Distribution (ALE)àCommunication.

Execute RFC Destination.

SAP Document : ALE

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

Ø Execute Maintain customer distribution model directly for creating the customer

model.

Ø Specify the source logical system (ALEPOOUT) and Create a customer model

name. (POOUT).

Ø Select the target logical system (ALEINSO) from the list.

Ø Create Message Type.

Ø In the resulting screen, in log message type enter ORDERS, ORDCHG,

MATMAS, CREMAS, and DEBMAS.

Ø Transfer and Save.

Ø Distribute customer model on the previous screen

SAP Document : ALE

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

color.

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àDistribution ALEàCommunicationsà 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 à Distribution (ALE) à Basic Configuration

à 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.

SAP Document : ALE

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

system.

Sending System

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

àP.R.àP.O.)

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

Dispatch the Idoc using the following path

LogisticsàCenter Functionsà Period. Work à Check Idoc Dispatch.

Receiving System

Check Whether Idoc has been posted in the application

LogisticsàCenter FunctionsàMonitoring àIdoc Overview

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

testing

The path is

Tools àAdministrationàProcess Technology à Idoc àIdoc Basisà Test à

Test Tool

Here enter the Idoc no and create it.

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