cancel
Showing results for 
Search instead for 
Did you mean: 

DBSQL_DUPLICATE_KEY_ERROR into table KBKO CO11N

anitaarifin04
Participant
0 Kudos
4,792

Dear SAP experts,

Our customer found dump DBSQL_DUPLICATE_KEY_ERROR into KBKO when execute tcode CO11N.

Runtime Errors DBSQL_DUPLICATE_KEY_ERROR

Except. CX_SY_OPEN_SQL_DB

ABAP Program SAPLCYBT

Application Component PP-CRP-SCH

User.................. AD_PFL_02_4

Language key.......... E

Transaction......... CO11N

Short Text

Open SQL array insert produces duplicate records in the database.

What happened?

Error in the ABAP application program.

The current ABAP program "SAPLCYBT" had to be terminated because it found a statement that could not be executed.

what is solution for this dump ?

Please help.

Best regards,

Anita A.

Accepted Solutions (0)

Answers (3)

Answers (3)

RaymondGiuseppi
Active Contributor
0 Kudos

Could you run SM13 to find the exact upgrade FM that raised the error,

  • From SM13 look at the internal table values received by the FM, are there duplicates in the receivd itab, also compare with the range numbers defined in SNRO for the KBED object (and the last allocated numbers).
  • Check if a new Enhancement has been recently activated in your system.
  • If you cannot find the root cause or any relevant OSS notes, as this is a standard error, report an incident to OSS
S_Sriram
Active Contributor
0 Kudos

Hi Anita

Could you share the full dumps as text file attachment?

Regards

SS

DominikTylczyn
SAP Champion
SAP Champion
0 Kudos

Hello anitaarifin_04

See the note: 2517845 - DBSQL_DUPLICATE_KEY_ERROR during order creation in IW31 due to number range inconsistency ...

Most probably the problem is due to capacity requirement number range settings. The note gives detailed resolution steps.

Best regards

Dominik Tylczynski

anitaarifin04
Participant
0 Kudos

Hello 3a9e4ce873a94034b33dc62b0ce600ee ,

Thank you for your feedback. I check SAP notes 2517845 related with transaction IW31.

Meanwhile in my case related with transaction production order confirmation (Tcode CO11N).

Thanks and regards,

Anita A.

DominikTylczyn
SAP Champion
SAP Champion
0 Kudos
anitaarifin_04

I understand that your issue is not with PM, but with PP orders. Still I think the root cause is the same - problem with capacity requirements number range setting.