getting error for migo_gr against po

[Former Member]

Hi ,

When i try to do gr of serialized material against Po for movt 101 I get dump SAPSQL_ARRAY_INSERT_DUPREC .exception CX_SY_OPEN_SQL_DB .

An exception occurred that is explained in detail below :

The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught

in

procedure "SERIALNUMBER_POST" "(FUNCTION)", nor was it propagated by a RAISING

clause.

Cany Anyone help me with this .

I have already checked that the serial number i am entering at the time of gr is unused one .

Thanks and Regards ,

Shikha

[ajitkumar]

did you check whether the serial number entered, though not used, is a valid one and conforms to the prescribed range?

[Former Member]

Hi ,

thanks for reply .

yeah I have checked this .

Thanks and Regards ,

Shikha

[ajitkumar]

if the issue is resolved, pl update the thread with resolution steps

[Former Member]

Hi ,

Ajit issue is still in the system .

Thanks and Regards ,

Shikha

[Former Member]

Hi ,

To all this error is due to serial profile of material ,we have to re assigned the range for the profile to solve the problem .

Thanks and Regards ,

Shikha Singh Chauhan

[Former Member]

Hi,

Please check the serial number which you are trying to accept in system is already available in table.

Check Function module for the same -SERIALNUMBER_POST

Debug the same with your abapor from ST22 and check.

Thanks & Regards,

Sandesh Sawant

[Former Member]

Hi ,

One thing more I want to add to my problem .

I had observed the number against which sap save the gr document is less than the number shown under the tab current number in tcode ombt .

But when I try to see the number through Migo I get msg "the docno. doesnt exist "

Is this thing is causing the error .

Thanks and Regards ,

Shikha

[kunal_ingale]

Hi,

try running report RISTEQ07

[ajitkumar]

why dont you check in MSEG table the doc number, adjacent numbers the last number as per OMBT etc

the duprec error is usually when it will result in a duplicate record for the primary key of the table

are you trying something new or is happening in a running production system. any changes done recently?

[Former Member]

I have tried to run table mseg for the number which I found number near the current number and the number I got while saving .

I didnt get my number but i did get the mat doc whose number is one less than number shown by current number fd of table ombt .

Thanks and Regards ,

Shikha

[Former Member]

Hi,

This short dump is normally caused by the fact that the internal number

range is complete.

Check your serial number range intervals in the customizing

transaction OIEN and compare it against the transaction SE16 for the

table EQUI.

If the relevant number range is already completed, then the system

starts counting from the beginning again, resulting in duplicate

database records.

Also check whether this is your case and, if so, please, use the

customizing transaction OIEN and reset these number range to a higher

value.

I hope this helps.

Regards,

Ashwini.