00 671: ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC while uploading DTR

[former_member746110]

Hi

While uploading duty rate files provided by the data provider customs info ,at the time of saving , its throwing the below error .

00 671: ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC .

There is no duplicate data in the XML file and data provider has also confirmed the same. Let me know if anybody has come across the same issue .

Thanks in advance.

Regards,

Vani

[Former Member · Accepted solution]

Hello,

Depending on which version of GTS version you run and which is your current support pack, check SAP Service Marketplace. There are several SAPnotes addressing such situations due to error in standard code.

Regards,

Branio

[former_member746110 · Accepted solution]

Hi

Notes 1279407 solves this issue and the files can be loaded again .

Regards,

Vanathi

[Former Member]

Hi Vanitha,

Did you check if you have any records for the same Duty type and validity already in the system.

If so, then take a quick look at the short dump in ST22, it might give you a rough idea of the record causing the issue.

Regards,

Jasmit

[former_member746110]

Hi Jasmit

Yes , as you have mentioned ,

After HTS data upload for 2012 through XML file ,system had 2 validity periods 2012-01-01 9999-12-30 and 2012-01-01 2012-12-31 . Hence now there is a issue of duplicate record ,since both periods are valid .

But the data provider customs info has confirmed they have sent only one record with validity period 2012-01-01 2012-12-31 .in the XML file .

How the record with validity period 2012-01-01 9999-12-30 is now there in the system

Is there a chance that the XML upload pgm in our system has generated this record ? How the upload pgm works ?

Regards,

Vanathi

[former_member215181]

Hi Vanathi,

I checked the program /SAPSLL/TLC_CUSB_UPL. The upload logic includes checks for overlap of periods, and messages are issued if the new file contains duplicate or overlapping entries. You should check the upload log to see if any such messages were issued, but from what I can see, it looks unlikely that the standard program would be able to generate duplicate entries.

But to move forward, you could consider deleting some or all entries in tables /SAPSLL/LC_CUSB1 and /SAPSLL/LC_CUSB2, and start the upload again. You would need to write a small program to delete the existing entries, but please first consider carefully which entries can be removed, in case you need to keep the history for any reason.

Regards,

Dave