topic Re: RBDAPP01 SAPSQL_ARRAY_INSERT_DUPREC in Application Development and Automation Discussions

RBDAPP01 SAPSQL_ARRAY_INSERT_DUPREC

manubhutani — Fri, 22 May 2009 17:46:45 GMT

Hi Gurus

Please help me if possible.

There's a job scheduled for program RBDAPP01 which processes the idocs in status 64.

But the job is getting failed with error 'sapsql_array_insert_duprec'.

It processed few idocs successfully, then got cancelled, the job log at the bottom we could find

'material document data and PO data do not match' and we also found idocs(status 51) which had this error.

In the job log we found one more idoc no which is still in status 64, so we thought that dump came due to this idoc no, but not which is in error(status 51) .

We again ran the job and again the same error but diff idoc came into status 51 and in the job log we found another idoc no.

Now we are not able to get whether job is getting failed due to idoc which came in status 51 or idoc mentioned in the job log which is still in status 64.

Now we dont know if job gets failed when an error is encountered, logically idoc should come in status 51 and it should go to next idoc. Please help..

Thanks

Re: RBDAPP01 SAPSQL_ARRAY_INSERT_DUPREC

Former Member — Fri, 22 May 2009 18:11:18 GMT

If you are getting the following dump ''sapsql_array_insert_duprec''

it means that SAP is trying to make an entry in the table but an entry with the same key already exists.

Just check in which table it is trying to update and what is the duplicate entry?

Regards,

Ankur Parab

Re: RBDAPP01 SAPSQL_ARRAY_INSERT_DUPREC

Former Member — Fri, 22 May 2009 18:30:05 GMT

Hi,

Program RBDAPP01 only take care of idocs which are in 64 status and after processing by this program idoc comes in 53 status from 64 status. If you are getting idocs in 51 status and the same idoc automatically coming in 53 status from 51 without manully processing, it indicate there some job for program RBDMANI2 is running in background. If the same idoc is not coming in 53 status from 51 status after manunally processing in BD87 then there is some problrm with data record of an idoc.

Thanks,

Asit Purbey.

Re: RBDAPP01 SAPSQL_ARRAY_INSERT_DUPREC

manubhutani — Sat, 23 May 2009 08:44:09 GMT

Thanks for the reply..

Are you sure there is a problem with the data.

Is the case that we need to apply any SAP NOTE for the same.

Thanks

Re: RBDAPP01 SAPSQL_ARRAY_INSERT_DUPREC

manubhutani — Sat, 23 May 2009 09:00:50 GMT

Thanks for the reply.

Job running RBDAPP01(status 64 processing) is getting failed with error data mismatch

same error is there in idoc and we can see one idoc no in the dump of sapsql_array_insert_duprec.

which is still in status 64, so we thought tht dump is due to this idoc but not because of idoc which is coming in error (51)

so do u know if job can get failed due to idoc coming in error

but logically after processing idoc (idoc coming whether is status 51 or 53), it should process next idoc.

Thanks

Re: RBDAPP01 SAPSQL_ARRAY_INSERT_DUPREC

Former Member — Sun, 24 May 2009 06:17:47 GMT

Manu,

On thing I can say here is you are getting error Because of idoc mentioned in the job log which is still in status 64. Its is not able to process the IDOC and keeping the session status to 64 all the time.

One quick turnaround could be delete the data related to IDOC in recopient system and try to repost the IDOC it will work fine.

If you goto SAP it may take some time as SAP will require to get into your system and may end up saying this is becasue of data inconsistancy in Recipient system.

Hope this helps!

S hital

Re: RBDAPP01 SAPSQL_ARRAY_INSERT_DUPREC

manubhutani — Sun, 24 May 2009 15:33:23 GMT

Thanks for the reply

the dump is at line -> insert nast from table lt_insert(in FM rv_message_update).

But in NAST table time at which record is created is also a primary key..

then how can it give a dump of sapsql_array_insert_duprec ?

I am in confusion with this..

Thanks a lot..

Re: RBDAPP01 SAPSQL_ARRAY_INSERT_DUPREC

Former Member — Sun, 24 May 2009 17:27:09 GMT

Well if its giving error saying its Duplicate then it has to be duplicate thats all I can say. You are having the muliple records in internal table for which the primary key fields are same and as you are executing INSERT as a single command for entire Internal table it will fail to update. Not a single record will be updated in database.

Why dont you try deleting the existing data in receiver system related to this IDOC?