20.08.2011 Page 1 of 3

SAP Note 765018 - Problems with logical system duringdata exchange

Note Language: English Version: 10 Validity: Valid Since 09.12.2008

Summary

Symptom

1. In the SMQ1 outbound queue in the R/3 back-end system, there are queueentries with SYSFAIL and error message "Logical system changed, seeSAP Note 588701".

2. In the SMQ2 inbound queue of the CRM system, there are entries withSYSFAIL and the thrown exception "GUID_FOR_LOGSYS_CHANGED".

Other termsC_056

Reason and PrerequisitesYou have made a client copy or system copy and therefore cannot change thelogical system as described in Note 588701.You have not yet transferred any data from the R/3 back-end system to theCRM system and there is no data from another R/3 back-end system in the CRMsystem.

Solution

Warning: You can use the following procedure only if thedetails specified under "Reason and Prerequisites" correspondto your situation. If you implement the changes when yoursituation is not the same, we cannot guarantee dataconsistency. Also note that you must not execute the changesin a productive system landscape.

1. If the situation in your system corresponds to the situation describedunder "Reason and Prerequisites" and if symptom 1 occurs, you candelete the table entry from table CRMPRLS table (there is just oneentry). Since there is no maintenance dialog for this table and youcannot maintain it using transaction SE16, you must use a report todelete it. This report is attached to this note as correctioninstructions.Create the report ZZ_DELETE_CRMPRLS in your system and copy the sourcecode from the correction instructions. You cannot implement thissource code using transaction SNOTE.You can use the report in every plug-in or plug-in basis system, evenif it is not specified in the validity section.After you have run the report, you can trigger existing queues againin transaction SMQ1.

2. If the situation in your system corresponds to the situation describedunder "Reason and prerequisite" and if symptom 2 occurs, you candelete the entry from table CRMMLSGUID (there is just one entry).Since there is no maintenance entry for this table and you cannotmaintain it using transaction SE16, you must use a report to deleteit. This report is attached to this note as correction instructions.

20.08.2011 Page 2 of 3

SAP Note 765018 - Problems with logical system duringdata exchange

If they do not yet exist, add the following messages to message classSMOF in your logon language:

Message Message short text303 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 notfound in table T000.

Create the report ZZ_DELETE_CRMMLSGUID in your system and copy thesource code from the correction instructions. You cannot implementthis source code using transaction SNOTE.You can use the report for every release of the CRM system, even if itis not specified in the validity section. The only exceptions are CRMreleases with Support Package versions that are too low such as CRMRelease 3.0 with Support Package 12.After you have run the report, you can trigger existing queues againin transaction SMQ1 of the R/3 back-end system or transaction SMQ2 ofthe CRM system.

If this does not solve your problem or if it causes follow-onproblems, create a message under CRM-MW-ADP.If the situation in your system does not correspond to thesituation described above, contact SAP and do not use thereport because it may lead to serious data inconsistencies.

Header Data

Release Status: Released for CustomerReleased on: 14.06.2010 14:19:24Master Language: GermanPriority: Correction with medium priorityCategory: ConsultingPrimary Component: CRM-MW-ADP Middleware Adapter

Valid Releases

Software Component Release FromRelease

ToRelease

andSubsequent

PI_BASIS 2003.1 2003_1_620

2003_1_620

PI_BASIS 2004.1 2004_1_620

2004_1_640

PI_BASIS 2005.1 2005_1_620

2005_1_700

PI_BASIS 2006.1 2006_1_620

2006_1_710

PI_BASIS 70 701 702

PI_BASIS 71 711 720

20.08.2011 Page 3 of 3

SAP Note 765018 - Problems with logical system duringdata exchange

Software Component Release FromRelease

ToRelease

andSubsequent

PI 2002.1 2002_1_31I

2002_1_470

PI 2003.1 2003_1_31I

2003_1_470

PI 2004.1 2004_1_31I

2004_1_500

PI 2005.1 2005_1_31I

2005_1_31I

SRM_SERVER 500 500 500

SRM_SERVER 550 550 550

BBPCRM 3.0 300 300

BBPCRM 3.1 310 310

BBPCRM 3.5 350 350

BBPCRM 4.0 400 400

BBPCRM 4.0V 4.0V 4.0V

BBPCRM 5.0 500 500

BBPCRM 5.2 520 520

BBPCRM 600 600 600

BBPCRM 700 700 700

BBPCRM 701 701 701

Related Notes

Number Short Text

872533 FAQ: Middleware

588701 Change of the logical system name in R/3 Backend system

Correction Instructions

CorrectionInstructions

Validfrom

Validto

SoftwareComponent

Type*)

ReferenceCorrection

LastChanged

326892 2003_1_620

720 PI_BASIS C 14.06.201019:48:12

327093 2002_1_31I

2005_1_31I

PI C 22.03.200714:14:41

382013 300 701 BBPCRM C PLCK124951 14.06.201019:49:09

*) C Correction, B Preprocessing, A Postprocessing, M Undefined Work