Reference document 83246316 000020 (Error during Insert)

[Former Member]

I am abap developer and my func person told me that he is trying to create the Billing document 83246316 in VF01 and we are getting the following error (Reference document 83246316 000020 (Error during Insert)). Can anyone lemme know how to solve this issue.

[Former Member]

Hi ,

better to check number ranges for billing documents...

83246316 -->might be delivery document no....

regards

prabhu

[Former Member]

This problem occurs when there are duplicate condition types in pricing for that particular reference item. Ask your functional person to check if there are any duplicate pricing condition types.

[Former Member]

I have put a breakpoint in RV60AFZZ and trying to create the billing document and it is not stopping. Lemme know how i can debugg this issue.

[Former Member]

Hi Malla,

Its not about debugging. Check for what are the condition types associated with that item umber in the billing document. I think there shoul dbe error with the conditions that are associated to the process at the time of billing.

If needed, please take help from your functional team.

Regards,

Susanta

[Former Member]

Do you think this would be the issue

XVBRP_KEY = XVBRP.

READ TABLE XVBRP WITH KEY XVBRP_KEY BINARY SEARCH.

CASE SY-SUBRC.

WHEN 4.

INSERT XVBRP INDEX SY-TABIX.

WHEN 8.

APPEND XVBRP.

WHEN OTHERS.

MESSAGE A004 WITH VBAP-VBELN VBAP-POSNR. <<<<<

ENDCASE.

The error occurs due an incorrect SY-SUBRC after reading table XVBRP

(SY-SUBRC not equal to 4 or 8). This means that the content of work area

XVBRP is inconsistent.

The problem is caused by a wrong source code in user exits or custom

copy routine. Please check in programs RV60AFZZ, RV60AFZA, RV60AFZB,

RV60AFZC, and RV60AFZD if you change the content of work area XVBRP.

Please make the same check also in the eventual customized routines

set in copy control.

[Former Member]

My functional person has confirmed that there are no duplicate pricing condition types and number ranges are also correct

[Former Member]

The only possible sy-subrc values in your version of the read statement are 0, 4 and 8.

Since the case statement checks for 4 and 8, sy-subrc must be 0. So you have found a value and need to handle that.

Rob

[Former Member]

Hi Rob,

Excellent!!!!!

Regards,

Susanta

[Former Member]

It works for line item 1 and it throws the error for line item 2.

[Former Member]

There are two line items in the order, we are not getting the error for first line item, but it is failing at the second line item

[Former Member]

XVBRP_KEY hasn't changed, so you are picking up the previous value which has already been inserted and you get sy-subrc = 0.

Rob