dump error in mb1a(SAPSQL_ARRAY_INSERT_DUPREC)

[Former Member]

Dear Friends,

We got a dump error(SAPSQL_ARRAY_INSERT_DUPREC)

when relesing particular material of the production order in mb1a. the detail error is as follows.

ABAP runtime errors SAPSQL_ARRAY_INSERT_DUPREC

"SAPSQL_ARRAY_INSERT_DUPREC"

"SAPLIEP1 " or "LIEP1U04 "

"REMAINDER_OF_EQUI_POST"

SAP Release.............. "46C"

Operating system......... "Windows NT"

Release.................. "5.2"

Hardware type............ "8x Intel 80686"

Database type............ "ORACLE"

Database owner........... "SAPR3"

Character set............ "English_United State"

SAP kernel............... "46D"

Created on............... "Jul 10 2006 21:36:37"

Created in............... "NT 4.0 1381 Service Pack 6 x86 MS VC++ 12.00"

Database version......... "OCI_920_SHARE__OCI_7_API "

Patch level.............. "2257"

Patch text............... " "

Transaction......... "MB1A "

000010 FUNCTION REMAINDER_OF_EQUI_POST.

000020 *"

000030 ""Verbuchungsfunktionsbaustein:

000040 *"

000050 ""Lokale Schnittstelle:

000060 *" TABLES

000070 *" SEREQUZ STRUCTURE EQUZ

000080 *" SERILOA STRUCTURE ILOA

000090 *" SEREQKT STRUCTURE EQKT

000100 *"

000110 DATA: RECORDS_POST LIKE SY-DBCNT.

000120 * Anzahl der zu verbuchenden Sätze fest

000130 DESCRIBE TABLE SEREQUZ LINES RECORDS_

000140

000150 * Zeitsegmente hinzufügen

000160

> INSERT EQUZ FROM TABLE SEREQUZ.

please let me know if you know the solution.

Thanks and Regards,

Shans.

[Former Member]

This is an old version of R/3, so hard to say what can have happened. Is this new? Have you searched SAP Notes? There is one that applies to 4.6c, but cannot tell if applies to your situation. Start with SAP Notes search, with the search terms suggested in the dump output.

[nag_r2]

Hi,

I think ur trying to insert duplicate records.

[former_member206439]

Are you getting this short dump in production system or ?

[Former Member]

yes this is a production server!!

[Former Member]

Have you modified the code for the transaction?

Rob

[Former Member]

I am not sure . do we have any way to find the history of program modification?

[Former Member]

Hi,

Look for any enhancement which is implemented and try deactivating the same. Also check the debug the code from which Include the duplicate entries are getting populated.

Shiva

[eduardo_hinojosa]

Hi

Check if BTE 'PM000020' is active in your system.

Regards

Eduardo

[Former Member]

Hi Eduardo

can you please explain in detail.

[eduardo_hinojosa]

Hi

In the report SAPLIEP1 you have the option to call this BTE (search it in SE38 and you could see it). If it's active and you have a Z_* report in tcode FIBF, perhaps it could be the source of error. It's an idea.

Regards

Eduardo

[sjeevan]

Go to transaction code OMBT, click view "Intervals" and make sure the number range for previous fiscal year and current fiscal year is not clashing.

for example:

Year From Number To Number Current Number

2010 4900000000 4999999999 5000533839

2011 5000000000 5999999999 5000135509

In the above case it will give this dump SAPSQL_ARRAY_INSERT_DUPREC. There may be other reason also.

You can also follow this method

  Go to T-code SE16N and input table name MKPF.
  Step find:  Find the highest material document number. 
  Go to T-code SNUM or SNRO.and Input object MATBELEG ( direct OMBT)
  Click on 'Number ranges' button.
  Click on 'Intervals' button.
  Check 'Current number' 
  Now compare it with the highest material document number of STEP FIND.
  Change 'Current number' to a higher number.

From my experience this normally happens when number ranged is transported from DEV to PRD accidentally during some IMG config.

[Former Member]

Hi jeevan,

the above dump not happens for all transactions only for few materials it is going to that dump error ,now can you judge that is because of number range problem ,if yes can i do your suggestions directly in production?

[Former Member]

hi friends i have found the problem help me to solve this.

in equz table mandt equnr datbI and eqlfn are key field and i found equnr should be varried but an existing equinr is tried to insert again and cuasing the duplicate entry dump. can u please help me how to change te equinr or how to rectify this issue.

thanks

[deepak_dhamat]

Hi ,

I think you should consult with your functional team Member for respective module .

regards

Deepak.

[sjeevan]

Since it seems like equipment number range clash.

TRY this: go to table EQUZ in SE16N and find out the highest EQUNR by sorting descending, now to go tcode OIEN and see if "Current Number" is less than highest EQUNR you found using SE16N. If it is then that is causing the problem.

In this case the solution would be to change the current number in the internal number range should be changed to one higher than the highest you found. For example in our case current number is 10026259 and highest number is also 10026259. In your case it could be like this current number 10026259 and highest number 10026269, you need to change this to 10026270.

Edit: I posted before I saw your reply.

Edited by: Jeevan Sagar on Sep 9, 2011 6:21 PM

[Former Member]

Hi Friends,

The issue is resolved , it is a number range problem , the nummber range for the equipment type had crossed its upper limit we increased the limit using the tcode OIEN.

cheers.

[matt]

Changed from closed but not answered to answered, as it clearly has been answered.