cancel
Showing results for 
Search instead for 
Did you mean: 

PIAFXD1 getting The ABAP/4 Open SQL array insert results in duplicate database records in PI

former_member187447
Participant
0 Kudos

Hi All,

I have seen this scenario before in SAP r/3 side, but this time i see it in PI sm58. My scenario is a flat file to IDOC scenario and i see the IDOC is created in sxmb_moni but the overall status is red and shows error in idoc adapter. But when i actually look in sm59 of PI i see messages failed with status"ABAP/4 Open SQL array insert results in duplicate database records in PI". please suggest what could be the reason.

Regards

Kalyan.

Accepted Solutions (1)

Accepted Solutions (1)

Harish
Active Contributor
0 Kudos

Hi Kalyan,

adding to Ram's reply, please also have a look on the below discussions.

Duplicate database records. | SCN

regards,

Harish

former_member187447
Participant
0 Kudos

Harish,

So, Is this R/3 issue still where in they have some number range issue and thus the data that i am using is duplicate?

Former Member
0 Kudos

Yes kalyan, The error is received while calling the BAPI at ECC, ABAP guys should be able to check the exact cause of the issue looking into the BADI code.

former_member187447
Participant
0 Kudos

I see the following dumps in PI.

Former Member
0 Kudos

Double click and check the error details of dump. Try to discuss with your abap team on the error.

Regards,

Pranav

former_member187447
Participant
0 Kudos

I see some dumps even in R/3 relating to duplicates issue. Will keep you posted.

Former Member
0 Kudos

Hi Kalyan

As mentioned in the posts above , duplicate database entry records could be due to :

a)  The data records actually exist in the DB level and there is an attempt to insert the same thing which is being blocked --->  ABAP Team can help for this by debugging the process when the queue is being re-attempted to be processed.

b) Also I have seen that it is sometimes due to number range issues mostly after any client copy ..

Can you please let us know if that is the scenario in your case ? Was there any previous activity before you started seeing the error / or did it start appearing under normal conditions.

Thanks

Rishi

former_member187447
Participant
0 Kudos

Yes, It is the Number range issue of the IDOCs. The issue is fixed now Thank You.

Answers (1)

Answers (1)

Former Member
0 Kudos

Kalyan,

Check this thread http://scn.sap.com/thread/213532

Regards,

Pranav