DNL_CUST_PROD1 failing

Question

Hi,
We are on SRM 7.0 and ECC 6.0. We have done the middleware setup but when we run the load for DNL_CUST_PROD1, we get an error message in SMQ2 (inbound queue) of SRM : The error is with a system fail status and it says : "The ABAP/4 Open SQL array insert results in duplic ate database records. r".
Pl let us know how to resolve this.
Regards,
Sivakumar

Answer 1

we may need to delete  the CRMPRLS in R/3,
Kindly double check with some thread and take action in the note
Symptom
1. In the SMQ1 outbound queue in the R/3 back-end system, there are queue entries with SYSFAIL and error message "Logical system changed, see SAP Note 588701".
2. In the SMQ2 inbound queue of the CRM system, there are entries with SYSFAIL and the thrown exception "GUID_FOR_LOGSYS_CHANGED".
            Other terms
C_056
Reason and Prerequisites
You have made a client copy or system copy and therefore cannot change the logical system as described in Note 588701.
You have not yet transferred any data from the R/3 back-end system to the CRM system and there is no data from another R/3 back-end system in the CRM system.
Solution
Warning: You can use the following procedure only if the details specified under "Reason and Prerequisites" correspond to your situation. If you implement the changes when your situation is not the same, we cannot guarantee data consistency. Also note that you must not execute the changes in a productive system landscape.
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: