Logical systems in production with CUA

Hi,
We have recently implemented CUA and are rolling out ECC 6.0. We created the logical systems for development, QA, and production in the development system and transported them to QA and production.
The solution manager system is the CUA master.
We normally only have production logical systems defined in production and would like to remove the development, QA, and solution manager systems. If we attempt to delete these definitions in production in SALE, it complains that the logical system is still used in distrubution model CUA, although solution manager, not production, is the CUA master.
If we are using CUA, do we have to have all logical systems defined in all client systems?
TIA,
Russ

Hi Pradeep,
I don't think that's quite it. SM1 is the master. I'm in the production system (PE1) trying to delete the development system (DB1). I am not trying to delete SM1. I'm getting the following message.
Logical system DB1CLNT300 must not be deleted
Message no. B1199
Diagnosis
The logical system DB1CLNT300 is still used in distribution model CUA (client 800).
System Response
The deletion cannot be carried out.
Procedure
Confirm that the logical system DB1CLNT300 is really no longer used. Delete it first from distribution model CUA (client 800), then delete it here.
Thanks and best regards,
Russ

Similar Messages

Original Logical System Of Product

Hello,
I am new to GTS and am finding it difficult to find the original Logical System for a Product in GTS. I found table /SAPSLL/TCOGVA, which shows the Logical System to Logical System Group. Then there is /SAPSLL/PNTPR, which shows the Logical System Group and Product. However, I would like to know which logical systems a product was found.
Is this possible in GTS?
Thank you in advance.
Regards, Dean.

Hi,
This is allways an issue, as this information, I beleive, gets lost along the way. So there are 2 hints for you. Either you find it out via the RFC user that created the Product (for that you need a different RFC user for each System, which I woul drecommend anyway), which you will find in the general Tab of the Product master. If you need this information on a constant base, I suggest you transfer it with the material and add it into an additionnal Field.
Let me know if that helps.
Marc

Transaction Launcher: Logical System in Production System does not change

Hi,
I created a transaction launcher in the CRM development system (CRD) to launch the transaction IL02 in the ECC 6.0 system (ECD). Then I transported the changes from CRD to the CRM production system CRP. I also transported the changes from ECD to ECC production system ECP.
However, when I see the transaction launcher in CRP system, it is still configured for the URL of ECD. I want the transaction launcher to connect to ECP. One option I have is to change the class name in the CRP system. However, I am not allowed to create a new ABAP class in the production system. Is there any other way to change the target system automatically in production system?
Thanks,
Rohan.

Thanks Piyush. Could you be a bit more specific? I followed these steps:
1. In transaction CRMS_IC_CROSS_SYS, created a logical system URL for production system
2. In customizing setting Copy/Delete Launch Transactions, deleted the transaction launcher id.
3. In customizing setting Configure Transaction Launcher, created the same transaction launcher id newly.
I still am not able to change the logical system. However, I can do it if I change the class name.
While deleting the transaction launcher id, should I be deleting all dependencies?
Regards,
Rohan.

Logical System Change for Production System

Hi experts
We have new CRM and BI project. Logical System name of our ERP production system is not in naming standart. So we want to change logical system name and run BDLS in production system.
Is there any risk about this prosedure?
Best Regards...

Hi,
It is not advisable to change the logical system in production client once its assigned.
Regards,
Nisit

Wrong logical system for prod categories

We had made a client copy and now the logical system name of R3MATCLASS in t.code COMM_HIERARCHY is still pointing to the old client; How can change we change this to the New client ?

Hello Rahul,
In case of client copy, you have to run transaction BDLS in order to convert old logical system name to new logical system name.
In this way, all tables containing reference to old logical system are updated with new value.
This should be true for logical system assigned to your product categories (table COMM_CATEGORY ).
Regards.
Laurent.

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

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 for Transaction Launcher??

Dear all,
Should we define logical system for Transaction Launcher to call transactions from back end ECC system. If yes, why we do this and where we maintain the logical systems?
Can we use existing ECC logical system, whcih mapped with SAP CRM system?
Where can we define the logical system for Transaction Launcher?
Please clarify my doubts to complete this process successfully, your suggestions will be highly appreciated.
Thank you
Raghu ram.

Hi Raghu Ram
In order to call an transaction from ECC, you should choose the logical system of the ECC System itself. You will get the information regarding the logical name assigned to your ECC System using the tcode SM59. The logical system must have been defined for the ECC System before you integrated CRM to backend ECC.
Check the tcode SM59 and you will find logical name of your ECC System there.
And yes, you are suppose to use the existing ECC logical system, which is mapped with SAP CRM system.
Hope this helps
Regards
Rekha Dadwal

Deletion of logical system

hi friends ,
i created a logical system long back and i have sent idocs succesfully from crm system to Tibco System , recently i have deleted this logical system and i created a new logical system , now the problem is if i trigger an idoc , two idocs are getting generated one with previous logical system and another with new logical system , but the previous logical system is not visible in SALE OR BD54 can u please suggest me how it is getting trigered or i need to delete it at some other tcode please suggest
please help me it is very urgent
with Regards
abaper

hi dilip ,
thanks for your reply ,
actually i deleted the old logical system because it is assigned to a client , and added a new one with out assigning to the client and i have changed in we20 also , and its working fine but the thing is that it triggering two idocs one for the new logical system with status 03 and with 0ld with status 29 or 37 with standard message type CRM_XIF_PARTNER_SAVE AND WITH OLD LOGICAL SYSTEM so please suggest me how can i restrict the older one , and i am unable to know where the system is picking the older logical system even thought i have deleted in SALE
PLEASE REVERT ME YOUR SUGGESTIONS
THANKS,
SRINIVAS

Client Delete and Logical System and CUA

I'm getting ready to do some client clean up in prep for an upgrade from ECC 5 to ECC 6 soon.
Currently we have a 3 system landscape: DV1 QA1 PR1
Clients on these systems are as follows: (not including 000, 001, 066)
PR1:100 - the production client
QA1:100 - Integration Master - not used except for RFC connections for Solution Manager
QA1:110 - Cycle 1 testing - not used
QA1:120 - Cycle 2 testing - not used
QA1:200 - Old training master client - not used
QA1:201 - Old training client - not used
QA1:710 - no longer being used for testing
QA1:720 - client used for system and integration testing
DV1:100 - Configuration - not used
DV1:110 - ABAP development
DV1:120 - Configuration
DV1:700 - Template for test - not used
DV1:710 - Test with prod data
Most have a logical system defined for the client.
I am going to delete those I've underlined above as they are no longer used.
Some of these are setup in the CUA system.
All are showing up in Solution Manager SMSY system landscape.
My plan is to backup the system database first!
Then:
1) Delete the client(s) (SCC5) one by one
2) Remove the client from CUA (SCUA)
3) Remove the logical name (SALE)
What I am unsure about is the order of the process. Should the CUA and ALE modifications come before actually deleting the client?
Does this sound like a reasonable plan to clean up our client landscape?
Thanks in advance for your suggestions and help.
Laurie McGinley

Dear Laurie,
Order should be like below:
1) Remove the client from CUA (SCUA)
2) Delete the client(s) (SCC5) one by one
3) Remove the logical name (SALE)
More over you should delete these clients from Solution Manager also inorder not to have error message when you go to solution Manager for doing anything on that system.
Please revert back for any queries.
Regards
Shailesh Mamidwar

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.

Same logical system name for two productive systems - BW, PI issues

Dear all,
we have a productive system which serves two companies (different company codes). This system is connected both to BW and PI for both companies.
There is a requirement that these two companies must use their own system, so the whole landscape (dev,qa,prd) will be copied to different systems (different server with different system id).
As a result of the above procedure we wll have two different productive systems, as required, but we wll have the same logical system name for the two productive systems, which must be both connect to bw and PI.
However as far as I know:
- we cannot connect systems with same logical system name to BW,PI
- we cannot convert logical system name of the one of the two productive systems as they are productive and so this is not supported.
How can we overcome the problem?
Please advice.

> However as far as I know:
> - we cannot connect systems with same logical system name to BW,PI
> - we cannot convert logical system name of the one of the two productive systems as they are productive and so this is not supported.
Right.
> How can we overcome the problem?
Since you split up systems (or plan to) I highly recommend booking an SLO service (http://service.sap.com/slo). Those people have to the tools and the knowlege to help you. I would not do this on my own.
Markus

Same logical systems for two environments productive

Hi gurus.
I have a question for ALE
There are two production systems a copy of another, who want to connect both to configure the ALE, but by mistake, both systems were the same logical system when they made the copy. Since this change takes months. At the moment I can not make this change in BDLS because it is a productive environment.
When trying to configure the ALE, I am have problems with the logical system name, although one of the settings I gave it another name when you configure the transaction BD64.
Guys, what I find solution to configure the ALE, without changing the logical system to a productive environments ??????
Regards,
Desiré

Hi Mark, thanks for the replay.
I understand also that the solution is to execute the BDLS to change the logical system and convert all tables to new logical system.
I don´t know how the process copy for both system productive.
The problem is that both environments are connected to BW, and other applications and they opened an OSS note to SAP consulting and and the answer given is that they did not recommend changing the logical system.
I thought if there was another way to configure ALE without having the problem of changing the logical system environments.
Regards,
Desiré

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

Problems with CIF (Logical system not assign to BSG)

Hello,
We are sending all master data from ECC to APO. We set up the CIF in DEV and all worked fine. But when we try to send the data from ECC to APO in QA an error appears. It says that the logical system is not assign in the BSG. Apparently the configuration that we have in DEV is the same that we have in QA. The logical systems in all instances (DEV & QA) have the same name. Could this be the problem?
Thanks,
David

Hi David,
1) Check whether BSG is defined in customisation under the below
link
SAP - Implementation Guide > Integration with SAP Components
     > Integration via APO Core Interface (CIF)    >
    Basic Settings for Creating the System Landscape   > Maintain Business System Group
2) Check the BSG is assinged to the logical system under the
spro transaction
SAP - Implementation Guide > Integration with SAP Components
     > Integration via APO Core Interface (CIF)    >
    Basic Settings for Creating the System Landscape   >
Assign Logical System and Queue Type
3) Check BSG is showing in APO material master for a location
product under "Properties" tab.
Regards
R. Senthil Mareeswaran.

Logical systems in production with CUA

Similar Messages

Maybe you are looking for