cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to save Delivery Note

former_member418015
Participant
0 Kudos

Hi,

need some help.

I have a sales order but when i am doing my delivery, system will give me a DN number but when i search the system for the document. It does not exist.

Then i went to ST22 to view the short dump, there is a error saying that

"The ABAP/4 Open SQL array insert results in duplicate database records."

when i go to the line in the code where the error occurs, it shows that there is error when they try to insert into LIPS table and i assume it found duplicate records.

I search OSS notes and it says when you combine 2 sales order into 1 delivery, duplicate records might occur due to the item number being identical. But the thing is i am doing 1 order 1 delivery, there should not be identical item number.

Pls help.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

looks like problem at LIKP and LIPS table ,activate the table in se11 ,and check the transaction again in VL01N and see the results.

if not then talk to basis guy

Answers (5)

Answers (5)

Former Member
0 Kudos

Hi,

The SAP Note you should read carefully is:

575667 - FAQ: Runtime error in delivery processing

Best Regards

Nikhilesh

former_member418015
Participant
0 Kudos

i don't think it could be with authorisation. User is able to create delivery for that plant but once in a while it just does not work

Former Member
0 Kudos

Hi Dylan,

Kindly check if there are any user exits creating this problem

prasanna

former_member418015
Participant
0 Kudos

I checked SM13 and found that the system is trying to insert 2 lines of 0040 into LIPS but on the delivery note, it shows as 1 line.

Is there anyway to prevent this from happening?

Former Member
0 Kudos

Hi Dylan,

Check any user related authorization constraints as well..This could be at plant level.

Thanks & Regards,

CLN

Former Member
0 Kudos

Hi Dylan,

Please check in SM13 for any update termination. You can find the log of update terminations. In this log, you will find the reason for update terminations.

Most of the times, this update terminations might be due to text objects. Check in your line item level, whether any mandatory texts are not maintained.

This can also happen due to printers no longer in use and are still mentioned in condition types.

Please check in this direction.

Hope this helps,

Thanks & Regards,

CLN

former_member418015
Participant
0 Kudos

funny thing is this does not happen always. But once in a while this happens to my delivery. so it is hard to pinpoint the problem. And when i use the user's id, i am unable to save properly. But when i use my own id(more powerful), i am able to save without problem.

Unable to simulate in my testing server because i do not know where the error lies.

Former Member
0 Kudos

The error you are getting is SAP_SQL_DUPREC. This most probably happens in the partner determination area, and mostly due to incorrect coding in user-exits. You can search for the *DUPREC text in SAP Notes and you will find one Note which explains how to correct this error.