outbound queue

[Former Member]

Hi SAP Experts

I am unable to process the queue stuck in CRM to R/3. When I do this it gives me error <b>"The ABAP/4 open sql array results in dupli"</b>

when I check in R/3 it has short dump related to this

"SAPSQL_ARRAY_INSERT_DUPREC

The termination occurred in the ABAP program "SAPLV45V" in "VBFA_BEARBEITEN".

The main program was "SAPMSSY4 ".

The termination occurred in line 1613 of the source code of the (Include)

program "LV45VF0V"

of the source code of program "LV45VF0V" (when calling the editor 16130).

Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred i

the

procedure "VBFA_BEARBEITEN" "(FORM)" but was not handled locally, not declared

in the

RAISING clause of the procedure.

The procedure is in the program "SAPLV45V ". Its source code starts in line

1576

of the (Include) program "LV45VF0V ".

Can someone help me to solve this?

[Former Member]

hi

wait for some time automatically your query get cleared if it's urgent to push use your customised table to push the transaction otherwise you can physically unlock transaction and refresh the page for clearing queue

Regards

Venkat

[Former Member]

Hello Raj,

First thing is to know what was in the queue! Mostly the queue names tell you which object it contains and also the object number. (eg R3AD_SALESDOC_1234567890, this is a sales document with number 123457890)

If the object is import (sales doc or something) and the object does not exist (or is not updated) in R/3 you should manually load the failed object through requests.

You can create a request through R3AR2 and start it through R3AR4.

Now, about the error. The inser duprec dump is because of a duplicate record and can have many sources. It's almost impossible to avoid such short dumps. You should be worried about this, unless the amount of these dumps is abnormally high.

After doing the request you can safely delete the queue entry.

Hope this helps,

Regards,

Joost

[Former Member]

Hi Joost,

Thanks for your reply.Yes this is the sales order.RFCUSER trying to insert values and giving short dumps.I see around 10-15 dumps a day created by RFCUSER.

Any other way I can avoid these dumps.? Like applying notes/changing programme.

Regards

Rajkumar

[Former Member]

Hello Rajkumar,

If this kind of dump occurs 10-15 times a day you clearly have a structural problem! There are quite a lot of OSS notes concerning SAPSQL_ARRAY_INSERT_DUPREC, just search for notes using 'SAPSQL_ARRAY_INSERT_DUPREC' as search criteria and look for a note that is applicable for your release/support pack. If that does not solve the problem you should really create a customer message.

Remember that each dump actually represents a desynchronisation of R/3<->CRM since data was not updated in R/3!

Also, check if these dumps occur for new or already existing sales orders. If this occurs for new sales orders you have a big problem, if the dump only occurs for already existing sales orders the problem is less critical. For already existing sales orders this could indicate that CRM is each time sending this 'update' as a 'create' (->leading to duplicate record since the sales order number already exists) rather than an update.

Look for some OSS notes that are applicable and try to isolate the problem.

P.S. Tip: To synchronize a large amount of orders you can use SDIMA. (this does not solve your problem though!)

Hope this helps,

Regards,

Joost

[Former Member]

Hi Joost,

Thanks for your time.Yeah..the dump is happening for old orders.

Regards

Rajkumar