MIRO SAPSQL_ARRAY_INSERT_DUPREC

[Former Member]

SM13

1 CKML_F_POST_INDEX V1 (no retry) Error

2 POST_DOCUMENT V1 Initial

3 ISJP_INVSUMIT_SAVE V1 Initial

4 ISJP_INVSUM_SAVE V1 Initial

5 FMCA_UPDATE_FI V1 Initial

6 G_GLDB_POSTING_A V1 Initial

7 ME_UPDATE_INVOICE V1 (no retry) Initial

8 MRM_INVOICE_DOCUMENT_POST V1 Initial

9 SD_SCD_IV_SELCRITERIA_SAVE_DB V1 Initial

10 SWE_EVENT_CREATE_IN_UPD_TASK V1 Initial

I implemented the note 1613559, but the issue is not resolved.

Further analysis showed:

CKMI1

FM CKML_F_POST_INDEX

LOOP AT t_tckmi.

     t_tckmi-awref = i_awref.

     t_tckmi-aworg = i_aworg.

     t_tckmi-vbdatum = sy-datum.

     t_tckmi-vbuzeit = sy-uzeit.

     MODIFY t_tckmi.

   ENDLOOP.

   INSERT ckmi1 FROM TABLE t_tckmi.

CKMI1-UZEIT 14:47:04

T_TCKMI-UZEIT 14:47:10

Why is the program writes the values ​​for the table second time?

[Former Member]

this is trz MIRO

[JL23]

What do you do to get around that issue?Can't you enter this invoice at all, or is  reentering the invoice after the dump going smooth without any issue

[Former Member]

I do not know how to repeat the issue. The problem is not constant.

I want to know what could be the cause and how to find it out.

I doubt that it is user mistake.

Time difference between repeated recordings are visible on the Screenshot (it is 6 second).

[JL23]

I doubt too that is a user error.

But it can be a consultant error, or just a program error.

There are consultants who transport number ranges from DEV to PRD and cause such problems because the last number in the DEV system is usually much lower than the last document number in a production system, which exactly leads to the fact that SAP determines a a new number for which already a document exists.

A program error would usually be repeatable, except it is influenced by the data base or server speed.

I think you should get in contact with SAP

By the way, you did not answer my questions. 

[Former Member]

I can not repeat this issue. This issue was 11 times in six months.

User does not remember, what he was doing.

[Prasoon]

Hi,

   If the latest note: 1613559 - Table CKMI1: check for duplicate entries (ver. 5.00 and up) doesnt solve your issue, I would suggest to raise an OSS ticket to SAP.

   Additionally, refer the note: 1158752 - Deactivating the update of the table CKMI1

Regards,

AKPT

[Former Member]

The issue is not constant. In september the issue was 3 times.

The dump SAPSQL_ARRAY_INSERT_DUPREC in an user does not appear.

I guess that data are recording a second time.

How to test it?