topic Re: SAPSQL_ARRAY_INSERT_DUPREC error in BAPI_SALESORDER_CREATEFROMDAT2 in Application Development and Automation Discussions

SAPSQL_ARRAY_INSERT_DUPREC error in BAPI_SALESORDER_CREATEFROMDAT2

Former Member — Wed, 04 Sep 2013 16:11:00 GMT

Hi Friends

I am creating sales order using function module BAPI_SALESORDER_CREATEFROMDAT2 in two different programs.

1. First program will be used to create orders in foreground.

2.Second program will be used to create orders in background/Foreground.

When I tried to create sales order via second program its creating DUMP

An exception occurred. This exception is dealt with in more detail below

. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was

neither

caught nor passed along using a RAISING clause, in the procedure

"SD_PARTNER_UPDATE" "(FUNCTION)""

But the program was able to create sales order without any issues in both the cases.before calling this function module I checked the value from boh the palces, I don't find any differences.

Anyone faced similar kind of issues? Anyone have clue for this issue.

Thanks

Gowrishankar

Re: SAPSQL_ARRAY_INSERT_DUPREC error in BAPI_SALESORDER_CREATEFROMDAT2

Former Member — Wed, 04 Sep 2013 16:35:14 GMT

You should check the partenrs data transfered to the BAPI

Where the data are from?

Max

Re: SAPSQL_ARRAY_INSERT_DUPREC error in BAPI_SALESORDER_CREATEFROMDAT2

Former Member — Wed, 04 Sep 2013 16:48:59 GMT

I am passing AG, WE, ZE, KB, Z1 partner details to BAPI, I dont find any difference in the data in both the programs. But if I execute from program 2, its throwing this DUMP( I put a debug point in program ZXCSVU05 ), its getting called two times, when I execute from First program.

Same code I used in both the program, same data is coming till BAPI but its giving dump in one program not in other program.

Thanks

Gowrishankar

Re: SAPSQL_ARRAY_INSERT_DUPREC error in BAPI_SALESORDER_CREATEFROMDAT2

Former Member — Wed, 04 Sep 2013 17:17:44 GMT

This Error may occur with one of the following reasons.

1.Dead Locks.

2.Inserting record and updating the same record in the loop.

3.Table Locks.

4.Not using COMMIT WORK AND WAIT after the INSERT and the UPDATE statements.

5.ROLLBACK WORK if INSERT or UPDATE fails.

Suggestion is to use 'Lock Objects' and 'Commit' after successful insertion/updation and rollback when fails.