ALE - Error - Assign client to logical system

Hi All,
When i am working in ALE [SAP IDES]. In SALE transaction when i try to do ' Assign client to logical system' -
in the second screen 'Change View: clients details' after i give all the details, it's showing error
'An entry already exists in the same key' & the cursor is in the client field [i entered 800 as i m working in client 800],
Kindly help.

Hi,
You did create a client in SCC4.
firstly,
1. did you create a logical system via BD54 and then did you assign that logical system to this newly created client ?
2. did you perform a local client copy to put data into this new client from an old or from a standard client like 000 ?
If you didn't perform above two things, then please do.
Hope it works!!
Regards,
Amruta

Similar Messages

Tcode to assign Client to Logical System (except SCC4)

Hi all,
I have created logical system for sender and receiver in SALE Tocde.
Now my receiver client is not listed in SCC4 Tocde and I am not suppose to create it there also but I need to assigning my logical system to my receiver client.
I am told that there is another way to assign So can anyone tell me which is the other way to assigning logical system to client except SCC4.
Thanks,
Maharshi

Hi,
You did create a client in SCC4.
firstly,
1. did you create a logical system via BD54 and then did you assign that logical system to this newly created client ?
2. did you perform a local client copy to put data into this new client from an old or from a standard client like 000 ?
If you didn't perform above two things, then please do.
Hope it works!!
Regards,
Amruta

Create a client and logical system for BW

Hi all,
Can anyone show me how to create a BW client?
create a BW client and logical system for BW client.
create sourcesystems for the other clients in BW.
I have follow some documents
B84: BI Connectivity
B03: General Settings BI Integration
But it's not working the data can't flow to BW server.

hi,
check out the following thread's. it will guide you
Connection steps for SAP BW and R/3
Info required while creating source system
R/3 Source system creation error in BW 7.0
regards
harikrishna N

In ale client and logical system

Hi,
do we need to assing logical system to client in ale configuration.
thanks,
Jigar

Hi,
Yes, you need to define and assign logical system for ALE client.
Path: SALE -> Basic Settings -> Logical Systems -> Define Logical System
Path: SALE -> Basic Settings -> Logical Systems -> Assign Logical System to Client
Regards,
Ferry Lianto

ALE: Logical system

Hi
I want to send IDOCS from SAP(client100) to a non-SAP system through an RFC port.
I created 2 logical systems.
100SAP : Sending system
NONSAP : Receiving system
Am i correct to say that i need to assign LS-NONSAP to client100. or should it be LS-100SAP ?
Message was edited by: Giovanni Baumann
Message was edited by: Giovanni Baumann

Hai
Check the following Setting
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Thanks & regards
Sreenivasulu P

Assign logical systems

hi,
why we have to assign client to logical system

In setting up and distributing the distribution model, we assign client to logical system.
This is a mandatory step in the configuration of ALE.
Regards,
Pavan

Difference between client system and logical system

Hi all
Can any one explain about the client system and logical system??
When this message type will comes in to picture at the time idoc processing??
Thanks and Regards
Arun Joseph

hi Arun,
I am giving the complete info on idoc.pls chk once.then ur issue will be solved.ok
and to know the diffrence between client and logical system very keenly go thru this link
https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=abouttheclientsystemandlogicalsystem&adv=false&sortby=cm_rnd_rankvalue
IDOC Administration
Step 1: Tcode: WE 46
Setting the Global Parameter for IDOC Interface
Step 2: Maintaing a Logical System
Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
Logical Systems, Define Logical systems
Go to Spro transaction
Step 3: Allocating Logical systems to the Client
Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
Logical Systems, Assign Client to Logical systems
Go to Spro transaction
Step 4: Setting up an RFC destination
Tcode: SM 59
Path: From the ALE Customizing in IMG, choose Communication, Define RFC
Destination
You can also do the Advanced Settings in the RFC Destination
Step 5: The PORT definition
TCode: WE 21
Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
Systems in Network, Asynchronous Processing, Assign Ports, Define Port
Step 6: Generating Partner Profiles
TCode: BD 82
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, PArtner Profiles and Time of Processing, Generate Partner Profiles
Step 7: Distributing the Model
TCode: BD 64
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, Maintain Distribution Model and Distribute Views
Technques for Distributing the Master Data:
Technique 1: The Push Approach
Executing the Process:
TCode: BD 10
Path: from the ALE Main Menu, choose Material Data Distribution, Cross
Application, Material, Send
Technique 2: The Change Pointer Technique
Enable Change Pointers Globally
TCode: BD 61
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution, Replication of Modified Data, Activate
Change Pointers
Enable Change Pointers Globally
TCode: BD 50
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution, Replication of Modified Data, Activate
Change Pointers for Message Type
Specify the Fields for which Change Pointers are to be written
TCode: BD 52
Path: From the ALE main Menu, Choose ALE Development, IDOCs, Change , Define
Change-Relevant Fields
How the Classification system works:
Creating a Class Type
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
Maintaing Status for the Class Types:
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
Maintaing Classification Status:
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
Maintaing Classes:
TCode: CL 01 (it is zero)
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Maintain Classes
Allocating classes to the Logical Syatems
TCode: BD 68
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Assign classes
to Logical systems
Filering at the IDOC level:
Identify the Filter Object:
TCode: BD 59
Path: From the ALE main Menu, Choose ALE Development, IDOCs,Data Filtering, Assign Filter Objects
Type to IDOC Field
Modify the Distribution model
How Segment Filtering Works:
Configuration:
Configring the segment-filtering technique is a one-step process.Just specify the segments to be filtered
TCode: BD 56
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Scope of the Data for Distribution, Filter IDOC Segments
The Reduced IDOC Type:
The reduced IDOC type allows to get down to the field level and specify the fields a recieving system does not need.
The System still needs the fields, but this has no effect on the recieving system because each field has a null value,
represented by a forward slash(/) in the field.
TCode: BD 53
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Scope of the Data for Distribution, Message Reduction,
Create Reduced Message Type
IDOC:
Complete Documentaion on any IDOC using TCode: WE 60
IDOC Display Tool: TCode: WE 02 or WE 05
IDOC DEfinition components:
Segment Components:
1. Segment Type (E1, Z1)
2. Segment Definition(E2, Z2)
3. Segment Documentation(E3, Z3)
E- SAP Defined
z- Custom Defined
IDOC runtime componets:
control Record:
Data Record:
Staus Record:
First Create the Segments using TCode: WE 31
and then create the IDOC using TCode: We3 30
first release the segments and then IDOC.
Creating a new Basic IDOC Type:
STEP 1: Analyze the Data:
STEP 2: Create Data Elements:
STEP 3: Create Segments:
STEP 4: Create Basic IDOC Type:
1. Execute TCode: WE 30
2. Select the Create new option and enter a description for your basic IDOC type
3. click the IDOC name, and click the create icon.
Enter the segment type and its attributes.
4. Keep on adding the segments as in step 3.
5. Save the basic IDOC type
Step 5: Release the Segment Type and Basic IDOC Type
STEP 6: Transport the Segments and Basic IDOC Type
Extending a Basic IDOC type:
STEP 1: Analyze the Data:
STEP 2: Create Custom Segments:
STEP 3: Create the IDOC Type:
STEP 4: Release the custom Segment and IDOC Extension
Develop the function module for fteching the Data and then inserting the data into IDOC using
EDIDD(for control Record) and EDIDC table(for DATA Record)
Configuring the Systen for IDOCs
Configure an Outboubd Process that uses Message Control
Step 1: Create a new Message Type
TCode: We 81
Path: From the Area menu of EDI, choose Development, IDOC Type/ Message
Step 2: link the IDOC type to the Message Type
TCode: We 82
Path: From the Area menu of EDI, choose Development, IDOC Type/ Message
Step 3: Create a new Process Code
TCode: We 41
Path: From the Area menu of EDI, choose Control,Outbound Process COde
Step 4: Create or Change a Partner Profile
TCode: We 41
Path: From the Area menu of EDI, choose IDOC,Partner Profile
Configure an Outboubd Process for Stand-Alone Programs
1. Create a new message type
2. Link the IDOC type to the Message Type
3. Add the message to the ALE Distribution Model(use BD 64)
4. Create or change the Partner Profile
go through the following site to have screen shots.
http://www.****************/Tutorials/ALE/ALEMainPage.htm
thanks
karthik
reward me points if usefull

Logical system on QAS after remote client copy from PRD to QAS

I wander after remote client copy from PRD to QAS do I have to change Logical system on QAS. Do I have to run some postprocessing program?
Thank you in advance

Hi Branko,
After the system copy, go to transaction SALE -> Sending and receiving Systems -> Logical systems -> Define Logical System , click New Entries and create a new logical system for your QAS; then go to SALE -> Sending and receiving Systems -> Logical systems -> Assign Client to Logical System, click on the client, click change and assign the new Logical system.
Other activities, check Jobs, RFC's, etc...
Regards
Juan
Please reward with points if helpful

Assign a logical system in RFC

How to assign a logical system to a client in RFC?
Regards,
pandu.

Hi,
Use following
Transaction code - SALE
-> Node - Sending and Receiving System
-> Logical System
-> Assign Client to Logical System.
Enjoy SAP.
Pankaj Singh.

Local logical system is not defined

Hello
We are trying to setup a logical system - created or defined the logical system
when we try the BD64 it gives out the error "Local Logical system not defined"
I am using ECC 6 version
IS there any way to bypass and do the setup ?

HI Anil,
Best Methodology for creating a RFC Destination that also includes setting up Logical System is:
Use Transaction -> SALE /b]
1) Define Logical system :
Select Idoc Interface / Application Link Enabling (ALE) -> Basic Setting -> Logical System -> Define Logical System

2) Assign Client to Logical system:
Select Idoc Interface / Application Link Enabling (ALE) -> Basic Setting -> Logical System -> Assign Logical System to Client
3) Create RFC Destination: T-CODE (SM59)
Select Idoc Interface / Application Link Enabling (ALE) -> Basic Setting -> Communication -> Create Rfc Connection
Follow steps in sequence. Hope it answers every thing.
Cheers,
*RAJ*
*POINTS IF FOUND HELPFULL*

How to create logical system

Hi,
How to create logical system.
Please help me with the steps for logical system creation in R3 system.
Thanks,
Kelly

Hi,
First make your client modifiable, then follow the below procedure.
Go to transaction SALE or BD54 -> Sending and Receiving Systems -> Logical Systems -> You'll see "Define Logical System" and "Assign Client to Logical System".
For more information use below link.
http://help.sap.com/saphelp_nw70/helpdata/en/da/5990df015b5b43a36f6ce7fa1ee8c0/content.htm
Thanks,
Mano

How to Assign Logical System to a Client in SALE Transaction

Hi ABAP/EDI Specialists,
1How to Assign Logical System to a Client. In the SALE transaction window.
I didn't see any Receiving and Sending Systems(Tree). But I can see Logical Systems. In the Definition and Assign Subtree are there. I created two Logical Systems STUD_S and STUD_R. When I executed Assign Logical Systems. I got a window, Where I can see a list of Clients. I got confused, how to Assign those Two Logical Systems to Client 800 and 810. Finally I double Clicked on each client and in the next window. I changed the Logical System to STUD_S for Client 800 and Logical System STUD_R for client 810. and saved them.
Is this procedure correct???
Why I need this is, While generating partner profiles in ALE Model (BD64), I am getting no list at all. When I executed I got no list.
"No messages have been defined for the selection conditions in the Model"
I got struck at this point.
Please help me to come out of it.
Thanks,
Chinna

Hi Chinna,
Thanks for such a valuable information. I am able to move further. But i got struck while generating parntner profiles from ALE distribution model.
Log For Partner Profile Generation:
Partner:
Partner ZVK_SS_800 as partner has been Created ( Sending System)
Partner ZVK_SS_820 as partner has been Created (Receiving System)
Port:
Port Cloud not be Created
RFC destination ZVK_SS_820 not specified for system ZVK_SS_820
Enter the RFC destination and Restart the generation
It is not recognizing the RFC port, even though i followed all the steps correctly.
While creating RFC destination, can someone tell me How to fix the above error and what is the Client No, Username and Pasword i have to give.
Thanks
Chinna
Edited by: Chinna on Jun 6, 2008 7:43 PM

ALE logical system to client

Hi,
Is assignment of SAP logical system to client mandatory...
I understand that we can give dummy names like SAP_A as logical systems but is it mandatory to assign them to clients..
I think Idoc can be sent to the respective SAP system through ports instead of a particular LS

this client assignment to logical system is about your sending system.
the steps for ALE config are following only:
1) IMG > SAP NetWeaver > Application Server > IDoc Interface / Application Link Enabling (ALE) > Basic Settings > Logical systems > Define Logical System
2) IMG > SAP NetWeaver > Application Server > IDoc Interface / Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Configure Predefined ALE Business Processes > Logistics > Logistics <-> External Systems > External Transportation Planning Systems > Maintain ALE Port Definition (Transaction WE21)
3) IMG > SAP NetWeaver > Application Server > IDoc Interface / Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Global Organizational Units > Cross-System Company Codes (Transaction OB72, SALE, OBB5)
4) IMG > SAP NetWeaver > Application Server > IDoc Interface / Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Maintain Distribution Model and Distribute Views (Transaction BD64)
5) IMG > SAP NetWeaver > Application Server > IDoc Interface / Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Configure Predefined ALE Business Processes > Logistics > Master Data Distribution > Proposal for distribution model: Customer and vendor masters (Transaction WYL2)
6) IMG > SAP NetWeaver > Application Server > IDoc Interface / Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Configure Predefined ALE Business Processes > Logistics > Logistics <-> External Systems > External Transportation Planning Systems > Maintain ALE Partner Profiles (Transaction WE20)

Assign a Logical System Name of a production client

Hi everybody,
We have an ERP system (now upgraded to ECC 6.0) that is in productive use since 7 years. Until now, no Logical System Name have been assigned to the production client - the field in transaction SCC4 is empty/blank.
Now we plan to implement a BW, so a test and a productive BW systems have been installed. According to the attached file and content of note 184447 we choose to use "Option 1: Uniform Logical System names clients by system type" for naming convention for LSN's.
All the systems/clients (BW test and productive, ERP test only) now are assigned with corresponding LSN's, except the production ERP client. It is still without LSN and the client is not defined as Source System for productive BW system.
So, my question is:
Should I expect any problems if the LSN of the production client is set up now, after long time, effective productive use?
I would mention that this is infact initial setup, not a change of LSN. Therefore transaction BDLS is not relevant, I think.
Thanks in advance

Hi DB49,
I already did an initial setup of LSN in the test ERP client (that client is copy of the productive ERP client, i.e. the LSN has not been set). And everything seems to be OK.
But the documentation says that ".... In a production system, the logical system must not be changed ...".
"Changed" is not "ïnitial setup" of course, so there will not be any problems I hope, but ...
SCC4 --> LSN field --> F1 -->
"System in which applications run integrated on a shared data basis.
The distribution of data between systems requires that each system in the network has a unique identification. The logical system is used for this purpose.
In the SAP System the client corresponds to a logical system. You can assign a logical system to a client in the client maintenance (choose Goto -> Detail).
The logical system is relevant in the following SAP areas:
ALE general: two or more logical systems communicate with one another.
ALE - ALE business processes (for example, cost center accounting): definition of a system where a specific application runs. Changes to master data can only be made in this system, for example.
Workflow objects: the logical system in which the object is located is always included in an object's key.
When maintaining the logical system, note the following:
The logical system must be unique company-wide. It must not be used by any other system in the ALE integrated group. In a production system, the logical system must not be changed. If the logical system of a document reference is not set to initial and does not match your own, the system assumes the document is located in a different system."

"Logical System" & "Assign Logical System to Client"

Hi Experts,
I'm new to Basis, I have the following systems installed:
1. EBP and SUS are installed in same server with different client:
    EBP: E01 with client 100
    SUS: E01 with client 200
2. ECC system is installed at a separate setver
    ECC: D01 with client 100
My question is, in EBP client which logical systems and client assigments need to be done?
What I confused is, for the EBP and ECC they have same client number 100, in EBP client , the client number 100
should be assigned to EBP or to ECC?
Kindly please guide.
Thanks and best regards
Jack

Hello Jacky,
                   You can assign the client number 100 to EBP and ECC systems, it doesn't create any problem. Because when you logical system in EBP, you need to create two logical systems one for EBP and ECC, but you need to assign client 100 to EBP only, same goes to the other side also.
Regards,
Prasanna

ALE - Error - Assign client to logical system

Similar Messages

Maybe you are looking for