Setup SCC4 ( logical system)???

Hi all,
I couldn't setup logical system for the test system because the production & test systems use the same client key (for example:100). The logical system for production is setup already and use 100 for the client key.
Any suggestion?
Thank you

Hi Suneel!
IT it not advised by sap to assign a client to multiple Logical systems . I am posting the excerpt from SAP IMG for Logical system node.
Logical system
 The distribution of data between systems makes it necessary to identify each system as a unique logical system.
 A logical system is an application system in which the applications are coordinated to work in one common database. In SAP terms, a logical system corresponds to a client.
 The logical system is important in the following SAP areas:
 o Communication between two or more logical systems
 ALE business process (e.g. Cost Center Accounting): defines the system in which a particular application is running. Only in this system can master data can be changed.
 Business Object Repository: The name of the logical system in which an object is located is always contained in the key of that Workflow object. In the following steps, you must define each client as a logical system by first of all defining logical systems and then assigning the clients to the corresponding logical systems.
 Note 
 Assignments must be unique (that is, one client can only be assigned to one logical System.
 o More than one client must never be assigned to the same logical system.
 o The logical system must be unique across the company. It must not be used by any other system in the ALE network.
 The same applies to pre-production systems and production systems: the pre-production system must be assigned to a different logical system from the production system.
 o If the logical system of a document reference is not initial and is different from your own system, the system assumes that the document is located on another system.
Recommendation 
Ensure that the assignment of IDs with the authorization to maintain logical systems is monitored (that is, only one person should have authorization to do this).
Hope it makes the things clear
with regards
ashwin

Similar Messages

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*

Event trace error: own logical system not defined ?

Hello,
i am trying to start a workflow when the status of a document changes to "completed". I was checking the event trace with transaction code : "SWEL" and i found out that the workflow is trying to start but there is some kind of error and the event trace is saying :
Your own logical system has not been defined for this client. Most of the ALE functions therefore cannot be used. No links can be written.
Any suggestiobns on what can be the problem ?
points are awarded
Regards

Sounds like you need to setup your client as a logical system, to do so..
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

Idoc setup::Partner profile for Logical system

HI All,
I am using Idocs to transmit my invoice details from ECC to PI, but every time I do this for a new customer I have to setup a partner profile for the customer whose invoice is to be sent. I setup the partner profile using WE20, I setup the partner profile for partner type KU(Customer) in the we20,
Is there any way we can setup partner profile for LS(Logical system) in we20 & I don't have to setup partner profile for each & every customer for which Idoc is to be generated.
Please provide some useful information/help to handle this business scenario.
Regards,
Saurav Singh

Hi Saurabh,
Please refer SAP Note 1103146 and check.
Please also refer the below link:-
http://www.sapgeek.net/2011/07/sap-idoc-tutorial-maintain-partner-profile/
Thanks & regards,
Rahul Verulkar

Use and impact of the logical system (SCC4)

An error has been made in our SAP system (production environment), transaction SCC4. The field «Logicial system» has been changed from «PRD460» to «QAS460». It has been left this way for few weeks and when we realized the mistake, we changed it back from «QAS460» to «PRD460».
For few hours, the document numbers in MM (t-code MIGO) were generated, but were not found in t-code MB03. We were able to generate them manually in t-code SM13 and the problem was solved.
What is the use of the «Logicial system» ? What could have been the impact on our database and on the integrity of our system of having the wrong logical system set to our production environment for few weeks ?
Thanks.

Hi,
Logical System Names
When data is distributed between different systems, each system within a network has to be clearly identifiable. The u201Clogical systemu201D deals with this issue.
A logical system is an application system in which the applications work together on a common data basis. In SAP terms, the logical system is a client.
Since the logical system name is used to identify a system uniquely within the network, two systems cannot have the same name if they are connected to each other as BW systems or as source systems, or if there are plans to connect them in any way.
Although SAP does not recommend that you connect test systems to production systems, a test system can have the same name as a production system. This makes copying production systems to test systems a lot simpler.
You are only allowed to change the logical system name of a system if the system is not connected to any other systems, because changing the logical system name would render all the connections to other systems useless.
Anil

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

Setup Logical System from blank

the default logical system of client 100 is blank
now we have to set a logical system for ALE and BW data transfer
but we found that some documents will not be transfer and some document cound not be found
eg: we cant found the FI documents from material document as MB53
debug the program we found that the programe check the logical system
is there any way to change the old documents logical system to new?
i found there is a sap note to describe how to change the logical system from a old value to new
but it not suit the situation of set new logical system from blank value.

HI ,
You need to create the logical system name and assign that to that client.
This can be done in Transaction :SALE.
Have a look at the t-code SALE and its options....
SALE->Basic settings->Logical system---- we have three options.
one is for creation ,assigning itto client ,other one is coversion.:Last one is only called BDLS .(little critical)
Thanks.

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

Assigning logical system to a client in CUA

Hi All,
I have got a doubt in the basic configuration in the setup of CUA.
I have performed all the steps that is given in the CUA cook book.
In, assiging the logical system to a client, whether this step shoud be done only in the central system alone.
Or the assignment should be done in the child system also.
When i created the all the steps in central system, logical system is created automatically in child system. but in the client assignment i didn't find information. in cookbook also they have do it in all the SAP system.
kindly advice.
Thanks and Regards,
Subhashini.

>
> So creating clients in Central system is enough for the child system.
The term you used "Creating Client" is technically wrong in this regard. You already have a client which is in use as Central system - right? You need to maintain the details of Logical system names of all the Child system in Central system to keep the central system updated with the knowledge of type and name of the Child systems it has. This definition can be done by using TCode BD54 which is table maintenance view ( V_TBDLS ) of the table TBDLS.
There is nothing to do or even can be done like Creating Client within a client (here your central system).
> Since there is noe transfer of user master from child to central system no need to create a client for the logical system.
>
Its true that there will no transfer of user master from child to central system. But of course the similarly here you are not creating any client within the child system. You are just creating the logical system name (tcode BD54) for this client (child system) and mapping it with the client in tcode SCC4.
Let us know your question. Also as suggested by Barnherd, please go through the SAP Help documentation on CUA. Also try to get an overview of Client in SAP (from SAP Help or SAP course ADM100) and Logical Systems.
Regards,
Dipanjan

An RFC destination could not be specified for the logical system

Hello Experts,
I am trying post goods receipt in EWM system in a simple inbound delivery process. It is not getting posted back in ECC. I have my RFC connection setup properly(I assume since I was able to transfer inbound delivery to EWM in first place).It seems some setting related to Outbound queue in EWM is missing.Can anyone tell me in detail what settings are required?Is it something to do with WE20 transaction?I am not sure what settings should be done there.The error log is as below-
An RFC destination could not be specified for the logical system
SB3CLNT011
Message No. B1550
Diagnosis
An RFC destination should be specified for the logical system SB3CLNT011.
This could not be done in this case. SB3CLNT011 is not your local logical system
and this system is not included in the relevant Customizing tables.
Procedure
Check:
RFC
destination
Port
definitions
oubound partner profile of
message type SYNCH for this logical system
Regards,
Khushboo

Hi Oritra and Suraj,
I have checked remote connection in SM59 for both the logical system.It works fine.I understand this is more of a technical issue,but I don't have A local basis team to help me so reaching out to experts here.Can you guide me what technical settings could be checked for EWM-->ECC connection?When I execute BD82 for SB3CLNT011 it shows me green status with message "No messages have been defined for the selection conditions in the model".
Although when I do this for EWM logical system SB3CLNT012 it shows me this with all green status-
System SB3CLNT011 as a partner type already exists
System SB3CLNT012 as a partner type already exists
Port A000000018 with RFC destination SB3CLNT011 already exists
Outbound parameters for message type SHP_IBDLV_CHANGE SHP_IBDLV_CHANGE01 already
Outbound parameters for message type SHP_IBDLV_SAVE_REPLICA SHP_IBDLV_SAVE_REPLI
Outbound parameters for message type SYNCH SYNCHRON already exist
Am I missing something in WE20?
Regards,
Khushboo

Why do we create logical systems in ALE?

Hi All,
i got this question in interview.
Why do we create logical systems in ALE?
Thanks & Regards
suresh

Hi
In addition to above .
A 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).
/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
http://help.sap.com/saphelp_nw04/helpdata/en/b5/1d733b73a8f706e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/69/c24ca94ba111d189750000e8322d00/content.htm
http://72.14.203.104/search?q=cache:J-uDLyT0w54J:www.topxml.com/biztalkutilities/walkthroughs/SAP%2520Configuration.pdfwhatislogicalsystems+(SAP)&hl=en&gl=in&ct=clnk&cd=5
http://help.sap.com/saphelp_nw04/helpdata/en/78/217dc151ce11d189570000e829fbbd/content.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/d7/9c73631d6c11d2a56e0060087832f8/content.htm
This guide is really good shows step by step procedure.
http://72.14.203.104/search?q=cache:Xyl0zxpyEXsJ:www.sappoint.com/abap/ale.pdfLogicalsystem(ALE)&hl=en&gl=in&ct=clnk&cd=9
for one client config
http://www.sappro.com/downloads/OneClientDistribution.pdf#search=%22Logical%20system(ALE)%22
Please reward for the same.

R/3 Logical Systems in BW

Hi All,
I have an idea that we have to create logical systems(SALE) for all BW clients and R/3 clients in BW system. After that, we will assign the BW logical systems to the respective BW Clients in SCC4. But we are not using the logical systems of R/3 system in BW anywhere(please correct me if I am wrong). Then what is the point in creating the logical systems for R/3 in BW?
Thanks,
RPK.

Hi RPK,
I think here you are getting confused..
You have to create logical system for R3 in R3 system only , and Logical system for BW in BW only.
The name you used for the source system (logical system) must be used again for the creation of the source system in the Administrator Workbench for the BW and vice versa..so that BW and R3 can understand each other...
I hope i am clear to you now ..please let me know If I am not....
Regards,
BRB

Multiple Logical Systems in Partner Profile for one instance

Can we create multiple Logical Systems in Partner Profile (WE20) for one instance or one System? If it is possible, can we create Logical System with respect to Plant/Country?

I am not quite sure if I understood your problem completley. But let's see...
Usually you use on on MSCS Cluster Group per SAP instance. So you have your already existing NW 7.0 ABAP stack in a separated Cluster Group, and you create a new Cluster Group for your new Java system.
You can find more information about it in this guide here on SDN:
Link: [High Availability;
More information about High Availability Setups for SAP System can be found here on SDN:
Link: [High Availability]
If you want to use the same database for your clustered ABAP stack and your new Java stack you can do a MCOD installation.
Please see Link: [SAP Note 388866 - Multiple Components on One Database - Installation|https://service.sap.com/sap/support/notes/388866]
Hope this helps.
Best regards,
Mathias

Can we add new logical system in Entitlement tab in SAP Authentication.

Hi ,
We already Installed and configured sap integration kit and every thing works fine. My question is as of now we connected our sap BW Dev system to BOBJ but we would like to connect to BW Prod System to same BOBJ System. What are the steps we need to follow to do this.
Can we just add the new logical system in entitlement tab of sap authentication in BOBJ 3.1? and import the roles and login to BOBJ USING THE Newly added SYSTEM Credentials. Thanks in Advance.
Thanks,
SK.

Hi Ingo,
Thanks for the information.
Are there any specific steps you need to follow when you are adding one more system to sap authentication. can you please give the steps we need to follow to setup this in right way. Thanks in advance.
Is there any thing we need to configure on sap side other than sap logon ticket parametre. If you can please provide the steps it will be great. Thankyou very much In advance.
Thanks,
SK.
Edited by: Vallabhaneni SK on Jul 14, 2009 8:53 AM

XI testing for two SAP R/3 systems with same system id/logical system

Hi
We are currently in the process of upgrading our R/3 4.7 to ECC 6.0 and plan to maintain dual landscape for DEV & QA (4.7 & ECC 6.0) for a period for testing and maintaining existing applications for fixes etc. The second DEV & QA (upgraded to ECC 6.0) are copy of respective systems and these systems are created automatically under technical systems in SLD by auto update (RZ70).
The question is, can we use the same XI system for testing inbound/outbound interfaces for both the systems i.e 4.7 & ECC 6.0 at the same time. I am aware of the fact that XI Technical/Business sytems dependent on unique logical systems, so we cannot create new business system for the upgraded DEV-II ECC 6.0 system.
For your information, we have two slds (one for XID/XIQ and second one for XIP).
What are the options without disturbing & maintaining the current XI system set up?
1) Can we change current Business systems e.g DEV010 to use new technical system i.e DEV-II ECC 6.0 for testing for a period and switch it back to DEV-I 4.7 technical system?
2) or change logitical system name of DEV-II ECC 6.0 and create new business sytem in SLD without interfering the existing setup and modify/create interfaces to use this new business system?
3) Do we need to refresh cache from time to time in XI ?
4) Any other implications
We will be upgrading XI to PI 7.1 after ECC 6. 0 Upgrade.
Any views on this would be highly appreciated.
Regards
Chandu

Hi
Technical System was created in the SLD automatically after RZ70 configuration in the new DEV-II system. We then modified Business System to use the new Technical system and carried out following steps:
1)     Original Idoc metadata was deleted from XID
2)     The port definition was deleted
3)     A new port definition was created for new system
4)     The metadata for each idoc type used was re-created in IDX2 , using METADATA -> CREATE
5)     This brought in all known versions of the idoc segments, including the 7.1 version.
I have already checked the guides suggested for our upgrade and we are thinking of going ahead with fresh installation and migrating the interfaces.
Regards
Chandu

Setup SCC4 ( logical system)???

Similar Messages

Maybe you are looking for