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

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

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

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 Regarding Logical System Names

HI all,
I read the blogs regarding Logical System Name, even I am having the some problems in my system.
For PI system client is 100.
R/3 System Client is 100 is created.
IN PI when I checked the sale->basic setting-> LOgical Settings-> Assign Logical Systems
I found there is only one client 100, and it is having the same logical system name as 'PICLNT100'.
In SLD one Business System is created for Client 100 and having the Logical System Name is 'PICLNT100'.
When I checking in the R/3 system that logical system Name ('PICLNT100') is not there and for r/3 client 100 having the different logical system name.
IN ID when I found the Goto ID->File Buinsess system and Menu ->Services->Adapter Specific Identifiers->Logical Ssytem,
It is different from the SLD logical System Name.
How Can I know in PI, that Logical System is belongs to r/3 or PI client 100,
when I running the sceanrio it is giving error as ATTRIBUTE_INV_SND_SERV while doing the file to Idoc scenario.
How I have to maintain the logical system names in this case?
please help me in this.
Regards,
Sree

hi.
each r3 system has his own SLN (PI,BI,ECC,etc). this name identify each R3 sytem.
http://help.sap.com/saphelp_nw04/helpdata/en/78/217dc151ce11d189570000e829fbbd/frameset.htm
IN ID when I found the Goto ID->File Buinsess system and Menu ->Services->Adapter Specific Identifiers->Logical Ssytem,
to export data of your R3 system to SLD, just do it from TCODE RZ70 in your r3 system, not PI.
once you configure it all data from r3 system is exported to SLD.
if the SLN does not match in Adapter Specific Identifiers->Logical Ssytem, edit the Bussines System (press in the little pencil) go to Adapter Specific Identifiers->Logical Ssytem and prees in the little hand icon. in the SLN in not refresh, go to menu enviroment--> CLEAR SLD DELTA CACHE. and repeat the steps before.
each time you send data to an R3 system and the sender system is a legacy. in your receiver communication channel>header mapping>sender system--> select the PI Bussines system and try again.
hope its helps
Rodrigo
PD: rewards points if useful

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 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 system in CLEAN_REQREQ_UP and BBP_GET_STATUS

Hi experts,
Just a very simple question : do you confirm the logical system we have to put in CLEAN_REQREQ_UP and BBP_GET_STATUS variants are that of SRM?
Thanks in advance.

Hi,
CLEAN_REQREQ_UP:
It checks whether the backend documents (namely-PR/PO/RES) have been created in the backend systems. Deletes obsolete table entries in SRM as well as updates document numbers in the Shopping Cart. You can't process the SC in SRM until this update is complete.
BBP_GET_STATUS_2:
It ensures that the information on the back-end documents is up-to-date. Retrieves the updated information from the Back-end systems (for example PO number after it was converted from a PR)
since both the reports checks and picks up data from backend system, we need to specify RFC for backend systems only.
-rgds,
Ravi

PLEASE HELP ME TO FIND THE SOLUTION REGARDING "LOGICAL SYSTEM CHANGED"

HAI EVERYBODY,
PLEASE HELP ME TO FIND THE SOLUTION REGARDING "LOGICAL SYSTEM CHANGED" during the material master replication by using middleware parameters.
step1 : i have taken SRM client 810 and named it as CHINNISRM
step2 : i have taken r3 client 810 and named it as CHINNIR3
step3: During material master replication i maintained tables like crmconsum,crmrfcpar,crmparoltp in r3 and smofparsfa in srm client and filtered the objects and loaded the objects through r3ac3,r3ac1,r3as.
step4 : And later i have checked in r3 queues to activate the objects,but i have seen a message like "LOGICAL SYSTEM CHANGED:SEE 588701".according to the oss instructions i have checked in CRMPRLS table in se16 in R3 .there i found out there is one logical client named with T90CLNT810.
oss :588701
Solution
There are different cases in which different forms of processing are
required or where several options exist:
- The logical system name of an R/3 Backend client was changed in
current operation. In this case, the data hangs in the outbound
queues of the R/3 Backend system as specified under point 1 of
the symptom. In this case, the logical system name must be
changed back to the original value. Then the outbound queues
can be reactivated. If no data was transferred to the EBP/CRM
server before the change, also a correctioin of the check table
is possible.
- The same logical system name was used again in a new client of
an R/3 Backend system that was linked to the EBP/CRM server. In
this case, the data is in the inbound queue of the EBP/CRM
server with the exception GUID_FOR_LOGSYS_CHANGED. In this
case, the queue entries which have status SYSFAIL must be rejected, however, not the entire queues. If the new client of the R/3 Backend system you have linked has exactly the same
data as the old client and if it is meant to replace the old
client (that is, this was deactivated), also a correction of
the check tables is possible. In this case, the inbound queues
can be reactivated after the correction.
oss:765018
1. If the situation in your system corresponds to the situation described
under "Reason and Prerequisites" and if symptom 1 occurs, you can
delete the table entry from table CRMPRLS table (there is just one
entry). Since there is no maintenance dialog for this table and you
cannot maintain it using transaction SE16, you must use a report to
delete it. This report is attached to this note as correction
instructions.
Create the report ZZ_DELETE_CRMPRLS in your system and copy the source
code from the correction instructions. You cannot implement this
source code using transaction SNOTE.
You can use the report in every plug-in or plug-in basis system, even
if it is not specified in the validity section.
After you have run the report, you can trigger existing queues again
in transaction SMQ1.
2. If the situation in your system corresponds to the situation described
under "Reason and prerequisite" and if symptom 2 occurs, you can
delete the entry from table CRMMLSGUID (there is just one entry).
Since there is no maintenance entry for this table and you cannot
maintain it using transaction SE16, you must use a report to delete
it. This report is attached to this note as correction instructions.
If they do not yet exist, add the following messages to message class SMOF in your logon language:
Message Message short text
303 User &1 is not allowed to change table &2.
304 User &1 IS not allowed to display table &2.
305 Logical system &1 was not found in table &2.
306 System error! The current client was not
found in table T000.
Create the report ZZ_DELETE_CRMMLSGUID in your system and copy the
source code from the correction instructions. You cannot implement
this source code using transaction SNOTE.
You can use the report for every release of the CRM system, even if it
is not specified in the validity section. The only exceptions are CRM
releases with Support Package versions that are too low such as CRM
Release 3.0 with Support Package 12.
After you have run the report, you can trigger existing queues again
in transaction SMQ1 of the R/3 back-end system or transaction SMQ2 of
the CRM system.
so what should i do to do the replication.please suggest me .untill and unless i solve my problem i cant move to the further activity.i hope you people can solve my problem.thanks in advance.
thanks and best regards,
n.chakradhar

Hi chakradhar,
Did you find a solution to your issue? We are facing a similar issue and looking to figure out how this can be resolved.
BR// 420

RFC destination Could not be SPecified for Logical System

Hello there
i am traying to costomize Transaction Luancher for some of the report which is been devloped in ECC (wich is ARD 100)
when on Transaction launcher Wizard--> techincal
i am having a logical system as ARD100(my r.3 system where report is devloped and which is connected to CRM )
while chosing the OBJ.TYpe :   and Method:
it says shows three erroe :
1) RFC destination could not be specified for the logical system ARD100
2) Object type and Method is not available
i have checked RFC , in SM59 entriesu2026u2026 There is an RFC named ARD100 and the connection test works. I also did an authorization test and it also works. I also checked to make sure the logical system name ARD100 exists
could you please help me to resolved the same
Regards
Rajiv

Hi Rajeev,
In a system landscape it's important and necessary to use the logical system names consistently throughout all systems!
Therefore please make sure, that you always use the same name for a logical system in all systems (CRM and R/3 systems).
The following steps are required before a RFC call is made from the CRM system to the R/3 system :
    o Use transaction SM59 to create an RFC destinations for the remote
       system.
    o Use transaction BD54 to create the logical system.
    o Use transaction BD97 to link the RFC destination created in SM59
       with the logical system created in BD54.
I hope this helps.
Best Regards
Gavin

RFC and Logical System names

Hello......is it necessary to have RFC and Logical system name for the connected system to be identical?Is there any explanation behind this if thats true....

Hi Gaurav,
It is recommended, but not mandatory, right, Muthuraman?
The system uses some transactions to determine which RFC will be used for the communication between one system and another, for example, in transaction 'Define backend systems' in SPRO, you can define that the current SRM client has an ECC backend system named X and the RFC destination for this X system is Y (not necessarily the same name).
Regards,

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

Logical System is not in the list of CentralSystem(CUA)

Hi,
I am trying to create Central User Administration (CUA) in my landscape.
CentralSystem:-
I was created one client 007 with user name CUA_ADM as Administrator and i have been defined a logicalsystem and assigned to it and created RFC connecitons to clients in childsystem.
ChildSystems:-
In this way in child systems also created users, RFC connections and define logicalsystem and assigned to clients.
1) My problem is i am trying to use transaction SCUA in that these logical system of child system is not available.
2) The logical system that is assigned for local clients is available after choosing those logicalsystems it giving error message like cannot reach system PRDCLNT000 by RFC
Any one please give me the suggestions regarding how to solve it.
Thanks,
Vivek . Nellore
Edited by: vivek.nellore on Mar 17, 2008 4:54 PM

Hi Vivek,
Please ensure that RFC destinations named same as the logical systems of child clients are created in master client.These RFC destination will be of type 3 and will point out to thee respective child clients. Similarily you may also create an RFC destination corresponding to master client in the child clients.
While it is not necessary to have 1:1 relationship in naming of RFC destination and logical systems it makes the job very easy. Other wise you need to check for ports involved in respective partner profiles(WE20) and then make sure that the ports are pointing to correct RFC destinations(which will be checked using WE21).
Regards.
Ruchit.

Clarification on Logical System naming

Similar Messages

Maybe you are looking for