cancel
Showing results for 
Search instead for 
Did you mean: 

Issue - Logical system name changed,see oss note 588701

Former Member
0 Kudos

Hello Experts,

We have an issue in ECC system

>> outboundque  smq1 ,>> in that ques status are showing as SYSFAIL, and the information is      '""""logical system name changed,see oss note 588701""",


In the note the resolution is mentioned below, but not sure where to correct, change logical system name / or make any entry.  Please advise.


Resolution

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.

Appreciate your response.

Thanks and Regards

DJ

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi

Issue resolved by correcting the wrong logical system entry in the CRMPRLS table in ECC system.

Thanks for the reply

DJ

Answers (2)

Answers (2)

former_member158363
Active Contributor
0 Kudos

Hello Dnyanesh,

this error never ocurr by itself, what was changed in you landscape prior this error?

Typically, this error occurs after system copy, when there are unprocessed BDocs from original system copied to the new landscape.

Is the error in your production environment?

Each system/client has written its own logical system in table T000 (transaction SCC4). Please, check if that logical name there fits to the one defined in CRM subscriptions (in CRM, transaction SMOEAC), or vice versa, in table CRMRFCPAR (in ECC, transaction SM30, enter CRMRFCPAR, check detail of some entry pointing to CRM and down on detail screen you should see logical system of connected CRM system).

Please, come back if you get stuck and maybe bring more details - SID of your systems, clients used, logical names...

Regards,

Dawood.


former_member182985
Contributor
0 Kudos

Dear Dnyanesh,

Regarding the error "logical system name changed,see oss note 588701", you could check the resolution in note 765018. Please apply the suitable resolution in your system corresponds to the situation described under "Reason and Prerequisites".

Best regards,

Julin Xin