cancel
Showing results for 
Search instead for 
Did you mean: 

DNL_CUST_PROD1 failing

Former Member
0 Kudos

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

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Resolved

Former Member
0 Kudos

Hi,

Can you explain how you resolved this issue? We are also getting same error message when we ran DNL_CUST_SRVMAS. It is strange, it works in our QA system and not in development and Prod system.

Thnaks,

Jagadish

former_member183819
Active Contributor
0 Kudos

First check comm_category table. any of your material group reached there.

i think you might be reprocessing the queue without correcting the issue.thats why you may get this error..

what was the initial queue error ?

update here the filter settings to help you further..

Hope you followed all the procedure given in 720819 note

Former Member
0 Kudos

Hi Muthu,

No Material Groups are present in COMM_HIERARCHY table. Also we have not set any filters as we have only 1 material group to be replicated as product category from ECC.

DNL_CUST_BASIS3 and DNL_CUST_PROD0 loads are successful.

Regards

former_member183819
Active Contributor
0 Kudos

hi

the material groups are stored in comm_category table.

check

SMW01 TCODE as well.

you needto concentrate which tablegot duplicate entry.

ask your technical friend to debug. he can help you to delete the duplicate entry during debug..

Former Member
0 Kudos

Hi Muthu,

I am working with Sivakumar. Currently there are no entries in Comm_Category and also we could not see anything in SMW01 too.

We tried to debug the scenario. The problem comes when the contents of the internal table which holds the material group are transferred to Comm_Category table. The program suddenly exits and as a result no entries are created in Comm_Category!!

Can you help?

Regards,

Nikhil

former_member183819
Active Contributor
0 Kudos

Hi Nikhil

can you try with delta down load . let us see. via R3AR2/R3AR4

Muthu

Former Member
0 Kudos

Hi Muthu,

We are doing the setup in a fresh client now as there were issues with Log Systems earlier. All the setup is now complete and middleware setup is also done. However now we are seeing the following error in Outbound queue of ECC : SYSFAIL. Logical System changed. See note 588701. However we have not changed any Log System names (mentioned in this note). DNL_CUST_BASIS3 is also failing.

Pl help.

Regards,

Nikhil

Edited by: Nikhil RGupta on Feb 8, 2011 12:31 PM

former_member183819
Active Contributor
0 Kudos

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:

Former Member
0 Kudos

Thanks Muthu.

We deleted CRMPRLS entries and it worked! However DNL_CUST_SRVMAS is still running and it triggered a short dump.

ST22 dump shows the following message : "Set type COMM_PR_UNIT is not allowed for product type". Any idea about this?

Regards,

Nikhil

Former Member
0 Kudos

Hi Muthu,

Service Master is still not replicated. There is a BADI : Hierarchy_update_bsp which is to be deactivated to enable service master replication. However I could not find this BADI in SE18. I get a prompt which says that 'This badi does not exist'

Regards

former_member183819
Active Contributor
0 Kudos

I dont know much about service .

Did you transfer MATERIAL successfully.

Note 966072 - Download of material fails - set type COMM_PR_UNIT

but this may not be applicable for you since the note is applicable for only SRM 550

Symptom

Download of materials from the backend to SRM fails and the following message is being issued: "A key was used twice for mulitrow set type COMM_PR_UNIT"(Message no. COM_PRODUCT512).

Other terms

R3AS, COMMPR01, COM_PRODUCT512, DELTA_DOWNLOAD, INITIAL_LOAD

Reason and Prerequisites

Program error.

Solution

Please implement the mentioned support package, or implement this note.

Header Data

Former Member
0 Kudos

Yes Material replication was successful.

This note will not suffice for us.

Regards,

former_member229388
Participant
0 Kudos

Hi,

Pls refer to this thread:

-Dhananjay

Former Member
0 Kudos

Hi,

Please read the message carefully. I am talking about middleware setup not SU01 user creation.

PS : Also DNL_CUST_PROD0 is success.

Regards.