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

Similar Messages

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

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

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

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

Product category does not exist in logical system

Hello Experts,
Need help in understanding product category change behaviour.
Shopping cart created and approved.
PO created and approved.
Now PO change version created by changing product category.
Please enlighten me whether this change is really allowed on business perspective and SAP perspective.
So far we been told that there is business case to justify this change.
If allowed by SAP, then how do we solve the problem of error occuring in workflow "product category does not exist in logical system XXXX".
Please advise.
Thanks,
Gaurav

Hi
I dont have a system right now to check
1.are you ordering the item from external catalog? ( any mapping between catalog product category to SAP product category )?
2. after approved PO created.
3. Now BUYER could change the product category again?
4. why the BUYER takes push ups for REQUESTER . Let Buyer cancel the PO and ask requester to create a PO.
What is the business process existing in your business ?
Since product category determines purchase group and every thing like gl account etc..
Can you recreate the same issue in development box?
Note 1466155 - GL account not re-determined on change of product categorySymptom
You have an SRM PO with items having multiple account assignment. Go to the PO item overview OR to the item basic data tab and change the product category. However, this does not trigger a new GL account determination for the accounting lines.
Note 1407962 - Category is editable when contract is assigned in PO item
Symptom
When ever a Contract item (Free text or Product Category) is assigned to a Purchase order free text line item, The category modification is not allowed. This is because the product category is always copied from the contract item and overrides the Category for Purchase Order Item. It is confusing for the user as the category is editable and can't be modified.
SAP has different different behaviors . Kindly tell us what type you belongs too...

Transport Logical system DEV To Production

Hi friends,
can you guys tell me how to transport Logical system from DEV system to Production system.
please help me its urgent..
Thanks in Advance

Hi Rashmi,
Go to SALE Transcation and click on basic settings ->logical system
-> define logical system and there u can click on tabe view menu and the transport ... it will ask u for a request ....
regards,
Santosh

Product Category / Logical System

We have taken a copy of our live SRM system and a copy of the ECC system.
We have updated the RFC's and the assignments to systems, but I am having problems with the product categories.
I do not seam to be able to change or delete the exisiting entries or exclude them in the PPOMA_BBP screen, and I need a way to link to the new copied system.
If anyone can help I would be more than greatful.
Nick J

Hi nick,
Are you checked PRCAT
old logical system = XXX
new Logical system (current log system) = YYY
now you must get a report
then only you can replace.
thanks
muthu

Error with Logical System - Long SID - SOLAR01

Hello,
We are using Solman Ehp1, stack 25. We have a problem in using Long SID (same SID) in Solar01
We are creating a new system in the landscape of a project. There was a copy of production system (called PCA) into a sandbox system keeping the same SID for both system PCA
We define a new product system in SMSY and we use a new long SID so that it is called PCAP. This new system recovered the logical system definition for each client which is the same for both PCA and PCAP system. Then we create RFCs for the new PCAP long id, no problem.
Finally we add the new system to the Logical Component Z_ERP with a new role 2 Sandbox system.
We went to the project SOLAR_PROJECT_ADMIN and assign the new system role 2 so that is available to use it in some test.
We go to transaction SOLAR01, switch to the new system role 2, and try to execute any transaction in the new server, it is saying that there is no logical system assigned to PCAP.... which is true, since the logical system is called PCAxxxxx.
Can you help us with that?
Regards
Esteban Hartzstein

Hello Fabricius,
What I did is add the new PCAP system to the current Logical Component with the new system role Sandbox test so that they can perfomed some tests on that role. This system is a complete copy of the original PCA system, so internally everything is PCAP, and since I cannot have same SID in SMSY, I created as PCAP. And that causes a problem with the Logical System definition.
The actual error message is
smsy_ppms_api044
This error message was reported in another post back in 2009
LIink: Error getting RFC destination for logical system SMD XXX
Any ideas?? Help required
Regards
Esteban
Edited by: Esteban Hartzstein on Oct 27, 2011 10:00 AM

Logical systems while implementing charm in solution manager

Hello Everybody,
I just wanted to know how many logical systems we need while implementing charm in solution manager 7.0. I have 3 clients in development , 3 clients in Quality and 1 client in production.
Thank you,
vikram.

Hi Vikram,
Yes, i1n ChaRM we always work with logical systems, I mean clients.
The standard is:
DEV -> QAS -> PRD
However, you can also use:
- Minimum
DEV -> PRD
- Target groups
DEV -> QAS -> PRD
- > TST
DEV -> QA1 -> QA2 -> PRD
DEV -> QA1 -> PR1
-> QA2 -> PR2
There are a lot of combination possible.
BR
Fernando

Logical system and business system

Hi experts, please help me with the below questions---
1) What is the diff between logical system and business system?
2)what is the difference between logical system(defined in R/3) and business system (defined in SLD) in idoc to file scenario.
3) Is it require to give the logical system name of the xi server(Which we define in idx1 port) to the 3rd party system(Application system at the FTP side) to carry out file to idoc scerario?

Hi,
Business System :
1. Business systems are logical systems, which function as senders or receivers within XI. Business systems can be SAP systems or third-party systems. Depending on the associated technical system.
2. Business Systems should be mandatory used when dealing with Idoc's and Proxies .
Business Service:
1. Business Service requires manual adding on Inbound and Outbound Interfaces, Business Systems do not.
2. Business Services are maintained across environments and so, their names cannot be changed. Business Systems names can be changed across environments by providing SLD level transport targets.
3.In the Business Services we cannot maintain the Group and Targets in SLD. For Ease in transporting your ID/Configuration objects Groups and Targets are used in SLD for Business Systems.
4.Business Service has no SLD Entries and No Assigned Products and SWCV's
Regards
Sangeetha

BDLS updating logical systems in CIF models?

Hi
The BDLS tool can be used to update logical system names in systems. As I understand this tool is often used when copying systems (Production system to Q system for instance).
In a situation where you copy the productive system to the Q system:
Does anyone know if BDLS is capable of updating the logical systems in the generated CIF models that you get copied from the productive system? In this case you'd get a big chunk of models that point to the wrong logical name. If you could get the target system changed in the generated model then you could save a lot of time in generating and activating models.
Any comments much appreciated
Simon

Hi,
I am not too sure if this thread is followed. I was looking for some info where we had a similar issue recently when we did a production refersh to Quality and all our integration model variants are pointing to our production system.
Our basis team has taken all the necessary steps like BDLS etc, but we had this issue. I dropped a message to SAP and they gave a report name RCIFVARIANTCHANGE to change the logical system name from old one to the new one for CIF variants.
Thanks,
Murali

Original Logical System Of Product

Similar Messages

Maybe you are looking for