Issue on T-Code VCH1 BDC call

[Former Member]

Good day to all,

I have a problem on the below BDC call for t-code VCH1.

After using RACOMMIT = 'X', the program still did not wait the update task to finish execute and continue to next loop pass.

Hence during the second loop pass, the second record will still get the same classification Object number

and lead to update dump (ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC) duplicate record.

Anyone face this problem and how to solve this issue ???

*refresh messtab.*

*clear: gw_ctu_params.*

*gw_ctu_params-defsize = 'X'.*

*gw_ctu_params-dismode = p_mode.*

*gw_ctu_params-updmode = 'S'.*

*gw_ctu_params-racommit = 'X'.*

*call transaction 'VCH1' using bdcdata*

*options from gw_ctu_params*

*messages into messtab.*

[Former Member]

HI

Use

WAIT UP TO 5 SECONDS

If requiered Increase the Time (May be helpful)

Hope this would serve your purpose

Ram

[Former Member]

Hi Ram,

WAIT UP TO *** SECOND is very subjective as it depends on the hardware and server performance.

Is there any way that we can WAIT for the UPDATE TASK to finish execution only continue to the next loop pass ?

For normal submit to update task we will use COMMIT WORK AND WAIT.

Can this be apply to main program which call transaction ???

BH

[gabo2050]

Hi

I have modified some data of the client at the transactions VCH1 and LS51, this means I change the date or activate option. But when i saved the indormation it sends a message that the "Uploading has been cancelled" and the changes are not saved.

And also i have that message:

"the error SAPSQL_ARRAY_INSERT_DUPREC indicates he was these are very common errors and can be ignored"

present in both transactions.

How can I solve this problem

Regards