oracle - "Update Terminated" on /nva01 transaction -

while running sap-sd benchmarking process on 3 tier sap setup, number of transactions fired automated users. following steps executed,

6  /nva01             (create sales order)     [enter]  7  order type           or     sales organization   0001     distribution channel 01     division             01     [enter]  8  sold-to party        sdd00000     po number            perf500     req.deliv.date       22.12.2009     deliver.plant        0001      material         order quantity     sd000000         1     sd000001         1     sd000002         1     sd000003         1     sd000004         1     [f11] (save)  9  [f3] (back)     (this dialogstep needed 4 dialogsteps va01 defined      sd benchmarks) 

whenever [f11] pressed after entering information saves when [f3} pressed, shows error “unable update”

then manually tried execute same steps

6  /nva01             (create sales order)     [enter]  7  order type           or     sales organization   0001     distribution channel 01     division             01     [enter]  8  sold-to party        sdd00000     po number            perf500     req.deliv.date       22.12.2009     deliver.plant        0001      material         order quantity     sd000000         1     sd000001         1     sd000002         1     sd000003         1     sd000004         1 

on pressing [f11] saves. when [f3] pressed go previous screen, gives “update terminated” error.

  [f11] (save) 9  [f3] (back) 

then locate root cause of error, sm13 transaction , shows following details error

there large number of same error in logs,and update key error entries same “4a08b4400c022793e10000000fd5f53d” normal..?

on googling found out possible reason error

1. key exists in table , duplicate entry disallowed. table affected transaction..? how resolve..?
2. document number ranges issue document number range modify..? how resolve..?

kindly advise how resolve this

edit including system log--

runtime errors sapsql_array_insert_duprec exception

cx_sy_open_sql_db date , time 12.05.2009 06:59:27

---------------------------------------------------------------------------------------------------- |short text
| | abap/4 open sql array insert results in duplicate database

records. |

---------------------------------------------------------------------------------------------------- |what happened?
| | error in abap application program
| |
| | current abap program "saplv05i" had terminated because has | | come across statement unfortunately cannot executed.

|

---------------------------------------------------------------------------------------------------- |what can do?
| | note down actions , inputs caused error.
| |
| |
| | process problem further, contact sap system
| | administrator.
| |
| | using transaction st22 abap dump analysis, can look
| | @ , manage termination messages, , can also
| | keep them long time.

|

---------------------------------------------------------------------------------------------------- |error analysis
| | exception occurred explained in detail below.
| | exception, assigned class 'cx_sy_open_sql_db', not caught | | in
| | procedure "sd_partner_update" "(function)", nor propagated raising | | clause.
| | since caller of procedure not have anticipated | | exception occur, current program terminated. | | reason exception is:
| | if use abap/4 open sql array insert insert record in | | database , record exists same key, | |
results in termination.
| |
| | (with abap/4 open sql single record insert in same error | | situation, processing not terminate, sy-subrc set

to 4.) |

---------------------------------------------------------------------------------------------------- |how correct error
| | use abap/4 open sql array insert if sure none of | | records passed exists in database. | | | | if error occures in non-modified sap program, may able | | find interim solution in sap note. | |
if have access sap notes, carry out search following | | keywords:
| |
| | "sapsql_array_insert_duprec" "cx_sy_open_sql_db"
| | "saplv05i" or "lv05iu15"
| | "sd_partner_update"
| |
| | if cannot solve problem , want send error | | notification sap, include following information: | |
| | 1. description of current problem (short dump)
| |
| | save description, choose "system->list->save->local file | | (unconverted)".
| |
| | 2. corresponding system log
| |
| | display system log calling transaction sm21.
| | restrict time interval 10 minutes before , 5 minutes | | after short dump. choose "system->list->save->local file | | (unconverted)".
| |
| | 3. if problem occurs in problem of own or modified sap | | program: source code of program | |
in editor, choose "utilities->more
| | utilities->upload/download->download".
| |
| | 4. details conditions under error occurred or | | actions , input led error. | |
| | exception must either prevented, caught within proedure | | "sd_partner_update" "(function)", or possible occurrence must declared | | in the
| | raising clause of procedure.
| | prevent exception, note following:

|

---------------------------------------------------------------------------------------------------- |system environment
| | sap-release 701
| |
| | application server... "hpvm-202"
| | network address...... "15.213.245.61"
| | operating system..... "hp-ux"
| | release.............. "b.11.31"
| | hardware type........ "ia64"
| | character length.... 16 bits
| | pointer length....... 64 bits
| | work process number.. 10
| | shortdump setting.... "full"
| |
| | database server... "ghoul3"
| | database type..... "oracle"
| | database name..... "e64"
| | database user id.. "sapsr3"
| |
| | terminal.......... "hpvmmsa"
| |
| | char.set.... "c"
| |
| | sap kernel....... 701
| | created (date)... "feb 24 2009 21:53:01"
| | create on........ "hp-ux b.11.23 u ia64"
| | database version. "oci_102 (10.2.0.4.0) "
| |
| | patch level. 32
| | patch text.. " "
| |
| | database............. "oracle 9.2.0.., oracle 10.1.0.., oracle 10.2.0.." | | sap database version. 701
| | operating system..... "hp-ux b.11"
| |
| | memory consumption
| | roll.... 2013408
| | em...... 0
| | heap.... 0
| | page.... 0
| | mm used. 1966160
| | mm free. 24336

|

---------------------------------------------------------------------------------------------------- |user , transaction
| |
| | client.............. 900
| | user................ "sap_perf000"
| | language key........ "e"
| | transaction......... "va01 "
| | transactions id..... "4a08b9bc0c022793e10000000fd5f53d"
| |
| | program............. "saplv05i"
| | screen.............. "rsm13000 3000"
| | screen line......... 2

|

---------------------------------------------------------------------------------------------------- |information on terminated
| | termination occurred in abap program "saplv05i" - in "sd_partner_update". | | main program "rsm13000 ".
| |
| | in source code have termination point in line 480
| | of (include) program "lv05iu15".
| | program "saplv05i" started in update system.
| | termination caused because exception "cx_sy_open_sql_db" occurred in | | procedure "sd_partner_update" "(function)", neither handled locally | |
nor declared
| | in raising clause of signature.
| |
| | procedure in program "saplv05i "; source code begins in line | | 1 of (include program

"lv05iu15 ". |

---------------------------------------------------------------------------------------------------- |source code extract
| ---------------------------------------------------------------------------------------------------- |line |sourcecde
| ---------------------------------------------------------------------------------------------------- | 450| posnr = i_xvbpa-posnr
| | 451| parvw = i_xvbpa-parvw. | | 452| if i_yvbpa-stcd1 <> i_xvbpa-stcd1 or
| | 453| i_yvbpa-stcd2 <> i_xvbpa-stcd2 or
| | 454| i_yvbpa-stcd3 <> i_xvbpa-stcd3 or
| | 455| i_yvbpa-stcd4 <> i_xvbpa-stcd4 or
| | 456| i_yvbpa-stcdt <> i_xvbpa-stcdt or
| | 457| i_yvbpa-stkzn <> i_xvbpa-stkzn or
| | 458| i_yvbpa-j_1kfrepre <> i_xvbpa-j_1kfrepre or
| | 459| i_yvbpa-j_1kftbus <> i_xvbpa-j_1kftbus or
| | 460| i_yvbpa-j_1kftind <> i_xvbpa-j_1kftind.
| | 461| move-corresponding i_xvbpa wa_xvbpa3i.
| | 462| append wa_xvbpa3i da_xvbpa3i.
| | 463| endif.
| | 464| endif.
| | 465| endif.
| | 466| when updkz_old.
| | 467| if da_vbpa-adrda ca gcf_addr_ind_comb_man_old or
| | 468| da_vbpa-adrda ca gcf_addr_ind_comb_man_adrc.
| | 469| yadr-adrnr = da_vbpa-adrnr. collect yadr.
| | 470| endif.
| | 471| if da_vbpa-adrda ca gcf_addr_ind_comb_man_old or
| | 472| da_vbpa-adrda ca gcf_addr_ind_comb_man_adrc.
| | 473| xadr-adrnr = da_vbpa-adrnr. collect xadr.
| | 474| endif.
| | 475| endcase.
| | 476| endloop.
| | 477| update (object) table da_xvbpau.
| | 478| update vbpa3 table da_xvbpa3u.
| | 479|
| |>>>>>| insert (object) table da_xvbpai.
| | 481| insert vbpa3 table da_xvbpa3i.
| | 482|
| | 483| if sy-subrc > 0.
| | 484| message a700 object sy-subrc da_xvbpai(21).
| | 485| endif.
| | 486|
| | 487|* sonderfall neue vbpa (vbpa2) für rollen aa und aw
| | 488| loop @ i_xvbpa2.
| | 489| da_vbpa2 = i_xvbpa2.
| | 490| case da_vbpa2-updkz.
| | 491| when updkz_new.
| | 492| if da_vbpa2-adrda ca gcf_addr_ind_comb_man_old or
| | 493| da_vbpa2-adrda ca gcf_addr_ind_comb_man_adrc.
| | 494| xadr-adrnr = da_vbpa2-adrnr. collect xadr.
| | 495| endif.
| | 496| i_xvbpa-mandt = sy-mandt.
| | 497| if i_xvbpa2-vbeln initial.
| | 498| i_xvbpa2-vbeln = f_vbeln.
| | 499| endif.

|

it clear system trying update duplicate record , hence, update termination system popping up. take of abap team , check root cause of issue. if there customization involved in sale order creation process, in case also, happen. have check abap team. alternatively, if have login credentials service marketplace, have @ oss note 330904.