Logical system change history

Hi gurus
I need to find out WHO changed the logical system in one of our clients, this happened in the past, we changed to the right one this past weekend so its working now.
I have checked "SLG1", but i cant find anything but the change we made...
Also "SCC4" entry shows the right one and its from a couple of months ago...
I dont know if theres any way to find out this :-S...
Thanks in advance
Gabriel

Thanks Satya and Sushil
I checked last night SALE and is not showing any lines cause the logging is off....
I checked the SLG1 but as i mentioned it only shows the changes we made.
I believe we wont see any other logs than that cause 1) the logs could be old enough so they are no longer there, 2) the logging WAS and IS OFF....
Thanks and Regards
Gabriel
Edited by: Gabriel Lopez on Jun 23, 2009 7:19 PM

Similar Messages

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

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.
can anyone please give me the solution
thanks and regards
n,chakradhar

Also u need to delete the entry with the old logical system name in TABLE CRMPRLS in MM.
Check SAP Note # 765018

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

BW / SolMan Logical System Change

Hello all, I am having a BW related issue and would really appreciate some advice. I realize some of this is for the solMan forums and will cross post (I normally dont)
ENVIRONMENT
New installation of Solution Manager EhP1 (19). System name is ED0. We are running Windows / MS SQL
System is only for Solution Manager ops (client 001), and CUA master (client 950).
BACKGROUND
We want to use full SolMan capabilities. This seems to include some limited BW interaction. We do not use BW in the landscape, so will rely on the "internal" BW in SolMan.
During installation, our person made a new client (000 > 400), set it as default (login/system_client), then ran tc:RSA1 and activated the content. (This sets the client)
Client 400 HAS NOT BEEN USED FOR ANYTHING other than the initial installation, and subsequent activation of BW. It has no connections to other systems, no data, cubes, or anything
PROBLEM
We were NOT AWARE that he had ran RSA1 and activated content, and began using client ED0_001 as our PRODUCTION SolMan client.
We are now unable to run RSA1 in anything but client 400.
We are unable to change the client 001 logical system name because Solution Manager has been built around it.
TROUBLESHOOTING
We changed table RSADMINA / field BWMANDT to 001 from 400. This changed the error from "You can only run in client 400" to "The logical system name has changed" (exit only)
In sandbox I duplicated this problem, then deleted the 400 client (with T000 entry). Changed the login/system_client to 001, RSDAMINA to 001, and ran function module RS_MANDT_UNIQUE_SET (set i_mandt to 001). After restart, RSA1 gives same error, logical system name changed"
On same sandbox after #2 above I attempted tc: BDLS to see if it would let me assign an exisiting logical system. It did not
QUESTIONS
Will it have any impact on Solution Manager operations to have the "BW Client" on ED0_400 while Solution Manager production is on ED0_001?
Is it possible to change the BW operating client to 001 from 400? (said another way, can I change the current logical systems BW is keyed with to a different, but existing, logical system)
Assuming the answer to Q1 is yes, and the answer to Q2 is no, what steps need to be performed to make BW fulfill the SolMan requirements?

Updated Information - Answer to Question #1.
I am embarrased I missed this section in the master guide the first time around. I will leave the question unanswered in case someone has an easy rememdy to changing the BI client logical system, as I would like to have it in my productive client if possible. However I am relieved I have the option of running it separately in case that can't be done.
There are three major options to consider when planning your system landscape in regards to BI.
BI in the Productive SAP Solution Manager Client
In this scenario, BI is used in the same productive client as SAP Solution Manager. This option allowsfor simpler configuration, and isolates the BI activities conducted for solution life cycle management from the data on a production BI instance. This is SAPu2019s recommendation.
BI in a Separate Client on SAP Solution Manager
In this scenario, BI activities are conducted in a separate client on the SAP Solution Manager system. This scenario provides increased security, as user access is more restricted. However, you must maintain users separately and this increased your administration effort. There is no technical benefit.
BI in a Separate, Non-Productive BI System
In this scenario, the BI activities are conducted in a separate, nonproductive BI system in the landscape. Data is sent to this system from the SAP Solution Manager system via RFC. This is only needed in rare cases for sizing purposes.

Logical system changed and replication became useless

Hi all,
We have integrated sap crm 7.0 system and R/3 system. Then we have noticed that logical system is wrongly defined and we have changed it by using bdls txn. But now no data is exchanged, no data is triggered to be replicated.
In other words, integration is useless now.
What can we do in order to make integration active now?
Regards

Hi.
Can you please give more details about which logical system was redefined? CRM or R/3?
Try to set SMOEAC site again and R/3 table CRMRFCPAR to get the new logical system ID.
Have you cleaned up R/3 table CRMPRLS and CRM table CRMMLSGUID before start a new intial load of any customizing object ? If no, do this and then start a new initial load of any customizing object.
Regards,
Susana Messias

How to adjust logical system after coping PRD to QAS in tabels

Hello
I wonder how to adjust logical system after coping PRD to QAS in tabels. I know (the logical system changes) but there is a transaction which adjustes entries in tabeles...

>
Tina Tajnist wrote:
>...but there is a transaction which adjustes entries in tabeles...
SE14

New outputs generated when changing logical system in output master record

Hi!
We are sending documents from ECC 5 to a legacy system via XI/PI. We are about to move from an old XI installation to a new PI installation. The output record used (for example in a billing document) is set up based on logical system. When moving from the old to the new platform, we need to change the output records from the old logical syste to the new logical system. However this leads to generation of new outputs in all billing docs when opened in change mode. This goes also for billing docs where we already generated outputs via lthe old logical system in the past. Is there any solution to prevent the automatic generation of outputs for documents where the condition type already was successfully processed (as it works when the logical system is not changed)?
Best regards
/Björn

Normally the same output is not supposed to be generated, unless 'Multiple issuing' checkbox is checked in the output type configuration.
Also you can probably add a requirement in the output determination procedure and check if output record already exists. Take a look at the standard 'Reprint' routine, kind of the opposite is needed in this case.

JDBC to Idoc scenario - change of logical system name

Hi,
I have a JDBC to idoc scenario that worked. Now i had to change the logical system name from my sender system from ABC_123 into ABC123 in the SLD (Business System - Integration - Logical System name). I did so and also refreshed my Cache.
Afterwards I started the process, but it failed in the Receiver system. The idoc is correct expect of the partner name. My receiver system expect ABC123 - as I changed in the SLD - but PI send ABC_123.
If io look in SXI_CACHE - Services my Business System still got the "old" name (ABC_123).
Did i miss something resp. how can i load the current configuration from SLD?
Thanks in advance
Michael

Hi Michael,
Again Import the changed logical system in the Integration directory of you PI system.
And check the scenario (Sender Agreement, Receiver agreement ) what system they are reflecting.
If they are showing old system then you have to replace the business system in all the scenario.
Edited by: Rajhans Abhay on Jan 7, 2010 3:14 PM

Logical system name change

Hi all,
Now my BI development is pointing to R/3 development. R/3 logical sytem name is bbbclnt100. Now all my datasources are pointing to this logical system. Our basis people are going to change the logical system of R/3. Please tell me the repercussions? what will happen to my datasources?
Thanks in advance

Anni,
Change logical system name and run BDLS job to adjust. Do not change souce system. If you change source system all transfer rules will get deactivated.
Check: [Conversion of Logical Systems|http://help.sap.com/saphelp_nw70/helpdata/en/33/c823dbaea911d6b29500508b6b8a93/frameset.htm]
Search forum for more links.
Srini

Logical system name changes

All,
Has anyone faced a scenario where you need to change the logical name for any SAP system?
For instance:
System      Logical Name                                                    System      Logical name B
BW                      A                     system is pointing to            ECC                  B
ECC will be upgraded and system name will changed to C
Is that possible? If so do you forsee any issues? Can we switch ECC B to ECC C with no issues?
I appreciate any help.
Regards

Hello Mike,
please elaborate a little more your inquiry. Are you talking about the ALE logical name changing? For this, please check the following notes:
#544509 ALE: Converting the name of the "logical system"
#121163 UTI: Logical System names
If you're referring to a domain name changing (like a Windows domain name change) or a hostname change, please refer to the following notes:
#96317:   Host names during R/3 upgrade, tips & tricks
#1275273: Hostname change on 7.10/7.11 java stacks
#757692: Changing the hostname for J2EE Engine 6.40/7.0 installation
#8307:    Changing host name on R/3 host: What do you do?
#1070561: SMD: Best practice for planned domain name changes
and on the following SDN threads:
/message/9196590#9196590 [original link is broken]
Re: Domain name change
Re: Change the Domain Controller
How to change hostname
Change Domain Controller
Or, lastly, you're talking about a SID change? On this case, you must perform a system copy to change de SID, please refer to the following note:
#11692: Renaming the system ID
(Sorry for the long and generic answer)
I hope this information helps.
Best regards,
Tomas Black

Logical System Name changing

Dear Team,
We had upgraded BI system from 3.0B to BI 7.0. At the time of upgrade dev
copy(shadow system) logical system was not changed because most of the data is coming from ETL. Now we want to test the extraction from R/3 Dev.
R/3 Dev is already connectwed to BW dev 3.0B, Now we need to test
extraction from R/3 Dev to BW dev copy server( NW2004SR1 ).
Here we are facing a problem with Logical system. While upgrading the
same logical sys was copied to BW dev copy.
What is the procedure to change the existing logical system name in BW
dev copy and establish connectivity with R/3 dev?
what is the impact if we run BDLS transaction.
Thanks& Regards,
Satish.K.Neni

Hi Satish,
Go to transaction SALE -> Basic settings -> Logical systems -> execute "Define logical system" to create a new logical system -> then execute "Assign Logical System to Client"
That should solve your problem
Regards
Juan
Please reward with points if helpful

Logical system Name Change Via Transport

Hi All,
Recently we made changes in parallel processing profile customizing table (/SAPAPO/SDP_PAR) and created entries for Macro Jobs and CIF.
For Application "CIF Delta Report", Logical system is mandatory and in Dev we gave the APO Dev Logical System Name (AD1XXX). Now when we moved the changes to Quality, expectation was that Logical system name for CIF Entry in the table would change to AQ1XXX - However, it still shows as AD1XXX there. Moreover AD1XXX entry is not a valid entry in Quality System and even when we see Drop Down values for that column (Press F4) - Only APO and ECC Quality systems names are appearing.
Please suggest how can this logical system name be corrected. One option is running BDLS, but when this TR moves to Production there also we might end up in same scenario (Logical system as AD1XXX instead of AP1XXX) and running BDLS in Production wont be approved.
Please suggest if there is any other option to handle this.
Regards,
Alok

Hi Alok,
we describe a solution in our
SAP Rapid Deployment Solutions (RDS)
Quick Link
                Access SAP Rapid Deployment Solutions (RDS) directly via
                  http://service.sap.com/rds
SAP Demand and Supply Network Planning rapid-deployment solution
Quick Link
    Access this area directly via
http://service.sap.com
/rds-dpa
In confgiguration guide
Central Master Data Replication (SCO)
you can read how it is done with
Create Entries in Table
TVARVC for Logical System Variable in Variants
Frank

Logical system name has been changed for this system

Hi gurus,
I am fasing problem in BI7 system. we created a new client in the system & want to set it for BI development.
System Response
The transaction is canceled.
Procedure
Change the name of the logical system (table T000) for client back to BID500. This enables you to continue working with the system.
If you really want to change the logical name, than you can, if and when you:
change the system name back to BID500,
delete all existing connections between this system and other systems,
delete all transfer structures that still exist, and
do not use ALE or Workflow.
Regards,
Darshan..

Sorry, BI is a one client system. You cannot have a prod client and a dev client within one SAP system.
But...
...NO, you can't!
Best regards
Michael
EDIT: just to add, there is an exception if you have a SCM/APO type system [522569 - BW: Working in several clients (especially APO 4.x/SCM 4.x)|https://service.sap.com/sap/bc/bsp/spn/sapnotes/index2.htm?numm=522569]

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 history

Similar Messages

Maybe you are looking for