Logical System Naming Convention

Hi Guruz,
Is it mandatory to name your logical system starting with SAP system name. I went through SAP Documentation for creating logical system, it says <sap system name>CLNT<client number>. I didn't put my SAP system name for the first part<sap system name> instead some random letters. I know this question may sound stupid but I am right now in the middle of the integration so, I don't want to change it. Please confirm.

I'm work for the customer who has ~4000 logical systems defined (not all represent SAP boxes though). Which I find quite a lot, yet given the rules of naming convention helps a lot.
I would say that having the system name should be used whenever we talk about Logical Systems representing SAP boxes. But in case of external non-SAP applications, it is helpful to represent them by the external system.
Say, you have 20 SAP installations, each sending interface to application A. Then it is easier to monitor in XI/PI interfaces for single receiving logical system 'A'. But if you want to find out messages from given sending SAP system, then using SAP system name is recommended to extract such data quickly.
Regards,
Dominik Modrzejewski

Similar Messages

Logical System Naming In BW

Hello,
CAn any one please update me on 'impact of the "logical system" naming in BW '
Thanks

Hi
Refer this
bw logical system
Regards
N Ganesh

Business Service and logical system naming criteria across environments

Hi !
Imagine this scenario: File-XI-IDOC. There is a file server where files are uploaded by a legacy application. XI polls that directory, converts the file to IDOC and sends it to R/3.
R/3 is a production business system, for example "R3_PROD", the file server is a business SERVICE, because of its abstract nature.
Is it ok to give that business service a name such as "BS_FileServer" and then create the logical system "LS_FileServer" in R/3, to be able to receive IDOCs from the sender business service?
If we need to use 3 different file servers, one for development, one for test and another for production...is it ok to create the business service in each integration directory with SAME name, and the 3 logical systems with same name in each R/3 receiver...because creating business services as "BS_FileServer_DEV", "BS_FileServer_TEST" and "BS_FileServer_PROD" we imagine that could give us problems when transporting scenarios from dev to test, and from test to prod...because we will need to recreate the whole scenario using the new object denomination.. e.g. a scenario including BS_FileServer_DEV in development is called BS_FileServer_TEST in test..or worse..we could have the BS object transported and as a result we would have a BS_FileServer_DEV object in integration directory of our test environment...
Is this the right path?
Thanks,
Matias.

Hey,
When a technical system is defined for a product / s/w comp version we also enter the parameter for logical system name. If a buisness system is defined for a technical system then it in turns refers to the technical system with buisness system assigned to it.
Itz lyk linkage of <b>PRODUCT -> S/W COM VERSION -> TECHNICAL SYSTEM (LOGICAL SYSTEM) -> BUSINESS SYSTEM</b>
As per file to idoc scenario where <b>BUSINESS SERVICE</b> is used it doesn't refer to technical landscape so there is no question of Business system. With relevance to transports.
With File -XI-Idoc scenario the concept of logical system only comes into picture if we have a integration process also involved in the scenario. Where in adapter specific identifiers we specify the logical system name of the sender file system.
Integration Repository.
1) The Software Component version need to be same in all the landscapes that is a prerequisite else transport will fail.
Integration Directory:
2) Assuming that transport is being done for all the objects under a service and the objects has been transported to the test landscape business service with same name will be create in test sys only address and access parameters that have to be entered again and the change list has to be activated.
I haven't tried exporting individual object from ID so no clue.
Please refer the following link<a href="http://help.sap.com/saphelp_nw04/helpdata/en/93/a3a74046033913e10000000a155106/frameset.htm">Transporting XI Objects</a> .
Hope itz helpfull.
Cheers,
*RAJ*
*REWARD POINTS IF FOUND USEFULL*

Clarification on Logical System naming

I have a Web AS ABAP Technical system ES1 with a client 100 assigned as a Logical system ES1CLNT100.
I also have a Business system BS_ES1 running on this with a Logical System name ES1CLNT100 i.e. the same as the technical system (this is a test system and no I did not set this up myself).
I assume that I need to change the logical system ID of the business system to something different, say BSES1. Is that correct?
If I use that BS_ES1 business system as the receiving system for IDocs, do I need to enter the logical system name in SALE for the receiving system that receives the IDocs?
Kind Regards,
Tony.

Were you allowed to create 2 Business Systems in the SLD with the same logical System Name? That is strange?
Even though maybe you can do this at the SLD, when you try to import it into the ID, you will be unable to activate the Business System in ID.
There can be one and only one business system in the ID that uses one Logical System Name.
Regards
Bhavesh

Logical System Name of an Idoc Sender

Hi,
I have seen that For Idoc senders the the Logical System name associated with the sending Client has to be SAP+System Id(For example SAPE05 where System Id = E05).
Is it mandatory? If so how can I have multiple clients in a sender Idoc systems sending data?
Regards.

The logical system nameing convention is:
<System ID>CLNT<Client>.
If your system is ADM, client 070, the name would be:
ADMCLNT070.
Regards,
Jason

Logical system name in SRM system

We are into SRM version 5.(SRM server 5.5) with the backend system as SAP ECC 6.0 .
The logical system is defined as '0000000050' for backend SAP system . All the systems like CRM and BW uses this as the logical system name for backend system . Recently SRM is implemented in our organization and we have no other choice and have to use the logical system name as '0000000050'
When product categories are assigned in the org attributes , the system stores the back end system as 50 and this is the issue. SAP support mentions that this is issue with logical system naming convention and that need to be fixed . But they fail to understand that the same name works fine in all other systems and also in SRM system except product categories .
Is there any OSS note for this fix. I would like to hear your experiences in this scenario.
Thanks
Mani

Hi Mani,
Logical System names are system specific, hence you have a different name in SRM system which will represent your backend system and this is not at all an issue. As suggested by SAP; '0000000050' is not the best name as per best practices.
You should have a name which should be of the pattern: <SID>CLNT<Client Number>.
Now here is the solution/work around. But be very careful and try this in sandbox system before being carried out in Dev/QA/PRD systems. Please make sure no other users are performing any activity while these tasks are being carried out.
In addition, please read through the ["Set up and system copy of SRM server 5.5";|https://websmp204.sap-ag.de/~sapidb/011000358700000310782007E/SRM50_SetupTranspCopy.pdf] guide before you carry out this activity:
The below activities are to be carried out only in SRM system
I assume SRM & Backend are separate instances
1. Create a new logical system name for the backend system in SRM system as per the standard suggested above.
2. Then use the transaction BDLS, to convert the old logical system name to new logical system name in all the tables.
3. Now, the step 2 ensure the logical system name is converted appropriately in all tables except SRM Org Structure related table.
4. Use the report RHOMATTRIBUTES_REPLACE, for replacing all the old logical system value with new logical system value. Please note while providing the inputs in the screen, there will be a Checkbox field called "Sub-String", you must check this one for all attributes you enter in the report. Then when you execute the report, a list will be display, here you have to select all the rows and click the first button on the toolbar. Only then the attributes will be updated.
Please let me know, if further inputs are required.
Regards, Kathirvel

Logical system name of xMII?

Hi,
How can I find logical system name of xMII?
Thanks.

The logical system nameing convention is:
<System ID>CLNT<Client>.
If your system is ADM, client 070, the name would be:
ADMCLNT070.
Regards,
Jason

Logical systems assignment when SRM and ECC are on 2 different servers

Hi SRM guru's,
What is the standard practice for Logical system creation and assignment when ECC and SRM are on 2 different servers.
I could not able to find which i created a logical system in SRM server which i created in ECC
Same for the ECC also.
how do i assign logical system of SRM to ECC
vice versa.
your prompt response is appreciated.
Regards

Hi Sai,
Logical System Naming/Creation procedure is not dependent on the servers but it is just a logical representation of a system.
As you are trying to name logical systems for ECC & SRM, please follow the below procedure which is usually recommeded by SAP and followed.
Logical System : <SID>CLNT<Client Number>
For Example if you have a client 300 in system DE0 (also called SID), the logical system name will be DE0CLNT300. And it will be same for SRM system.
You can refer the below document which eplains the creation of logical system and RFC destinations etc
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
Note: Only while configuring the RFC Destination, the servers will play a crucial role.
Regards
Kathirvel

Logical system name vs. destination name - CUA -

Hey experts,
at the moment I´m thinking about using the CUA in our SAP environment for role distribution.
In this scenario I need destinations to the child systems (of course!). In all manuals I found it say, that i HAVE to create destinations which have the same name as the logical system. However, this is not possible cause this is against corporate name conventions.
So I tried to use different destination names, but when I use the function "text comparison" (SU01->Roles) it always fails and says that the destination to the child system is missing.
So here my question: How can I tell the CUA not to search for destinations named like the logical system????
Thx in advance, nice weekend
Oliver

Hey John,
piece of cake ;).. that's what I thought at first. Unfortunately it´s not that easy. This is because of partially really strict restrictions within the SAP-Software.
At the one Module, you can choose the destination, is used for a particular group of functions. At the next, you simply can´t. SAP says "you need to have a destination, named as the logical system name". And there is no way around.
Maybe I´am the first guy being disturbed by this "feature"....
Of cause, I already placed several posts within the basis section... but still.. no way around. In one case I even opened a ticket at SAP... (I already posted the answer above) ....
Thx anyways!
Oliver

Giving logical system name for PI 7.11 system

Hi,
how can i give logical system name for PI 7.11?
Thanks.

Check if this helps http://help.sap.com/saphelp_nw70/helpdata/en/aa/b4b13b00ae793be10000000a11402f/frameset.htm
if you are loking for naming conventing : use CLNT{client no.} eg: PIDCLNT001
Regards,
Srinivas

Logical System Name for Portal

Hi all,
I am busy documenting System Info for a newly installed Portal (EP6) including values such as SID, Sys No, etc.
I would like to know if a Portal has a Logical System Name.
As far as I know, it does not, but I would like to confirm.
Regards
Sunil

Hi,
As per the naming conventions its defined as <SID>CLNT<Client no>.
Then a system with SID = J2E and client = 000 will have a logical system name J2ECLNT000.
Hope this helps.
Regards
Bharathwaj

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 names after system copy

Hi!
I installed a new SAP system via System Copy (SAPINST) approach.
As a consequence the old logical system names have been copied.
Question:
What is the appropriate approach (tcode, report) to change the logical system names of each clients of SAP system?
Thank you very much!
regards
Jürgen

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.
In BW, you make the settings for the logical system names in the BW Customizing Implementation Guide under Business Information Warehouse ® Connections to other Systems ® General Connection Settings. In the source system, you make the settings for the logical system in the Implementation Guide under Cross Application Components ® Distribution (ALE) ® Basic Settings.
Note SR047 lists names that cannot be given to BW systems, because they are reserved for internal use.
Logical system names must contain capital letters and numbers only. SAP recommends the following naming convention for logical system names: .

Changing the default logical system names for adaptive RFC models

Hello,
When I create an Adaptive RFC model the dialog that asks me to specify the model name, package, source folder, etc. has default values in the "Default logical system name for model instances" and "... RFC metadata".
I know I can type in another name there but I'd like to change the default name to something that fits our naming conventions. Can I change that? If so, can someone tell me where?
Thanks in advance!
David.

Suresh,
Thank you for your response. However, that is not what I was looking for. Sorry if my post was not clear.
I knew that I could change it AFTER the import. I also know that I can type in something else besides the default DURING the import.
What I am asking is if there is a way to change some configuration setting so that the 'default' that comes up in the drop down DURING the import is something different than what comes 'out-of-the-box' with NWDS.
Hope that clears up what I'm looking for.
David.
Message was edited by:
David Z. Pantich

Entitlement Systems Logical System Name

Environment:
- BusinessObjects Edge Series BI 3.1 (standard packge)
- Business Objects XI Integration for SAP Solutions
- Windows Server 2003 x64
I am trying to configure a Logical System Name in the Entitlement Systems of the BusinessObjects Central Management Console.
Our BI 7.01 system uses a different naming convention for the logical system name (not the standard <SID>CLNT<client#>
(i.e. BWQCLNT300). We use BWQ300. How would I override the default configuration (put in a different logical system name) in CMC - SAP Authentication?
Please advise. Thank you in advance.
Francis

Ingo,
That is correct. It generated the logical system name automatically for me.
But our BW system have a logical system name of BWQ300 (not BWQCLNT300).
How would I override this ?
Thank you very much for your reply.
Francis

Logical System Naming Convention

Similar Messages

Maybe you are looking for