cancel
Showing results for 
Search instead for 
Did you mean: 

Incorrect document status of delivery document in billing document document flow

Former Member
0 Kudos

Good day

We have the following situation which occurs not frequently in the production environment.    We are also not able to recreate the problem in the QA system.

If you look at the document flow in a billing document, the status of the delivery document is shown as 'Archived' and it does not show the sales order in the document flow at all.

If you look at the document flow in the delivery document, the status of the delivery document is shown as "Completed" and the sales order and the billing document is in the document flow.

I have execute program  RVDELSTA and also WS_CORR_VBFA_LIEF_01.  I have also run program RVV05IVB but none of the programs did resolve the issue.

I have also look in transaction Vl22 to see if any attempt was made to delete a line item.  But nothing was deleted.

I have attach a file with the example.

Is there any suggestion on how to fix the problem?

Accepted Solutions (0)

Answers (2)

Answers (2)

Jelena
Active Contributor
0 Kudos

This looks like a routine for the delivery/invoice split. I really doubt it could've caused any issues with the document flow. All it does is fills ZUKRI field and then documents are split based on that field. It should have no direct influence on document flow or statuses. It seems to me that data is OK in the delivery but the billing document flow is just not displayed correctly.

I'd check the data in VBFA table and if it looks OK you might want to open an incident with SAP. The document flow should just read the data in VBFA and then display status from VBUP/VBUK tables, seems pretty simple. Also make sure there is no user exit / enhancement in the document flow that could've gone wrong.

Former Member
0 Kudos

Hi All  ....... We found the issue.   The coding in the routine is wrong.   To remove the leading zero's, the field vgbel should have been moved to a temporary field before removing the leading zero's.   By not doing that, the data of the vgbel was changed and SAP was not able to tie it in the background.

Unfortunately there is no fix for this.  To do direct table updates is also to risky and the risk to the business currently is only the document flow for a period of time which is incorrect.

Lakshmipathi
Active Contributor
0 Kudos

Just raise an OSS message with SAP who can provide a program through which you can correct the document flow.

G. Lakshmipathi

moazzam_ali
Active Contributor
0 Kudos

Hi

What is the actual status of this delivery document? If you open it in VL03N or check it in LIKP or LIPS table what is the result?

Thank$

Former Member
0 Kudos

In Vl03N the status is "Completed" which is correct.   Also In LIKP and LIPS the delivery document is available.   The client does not use archiving at all.

Former Member
0 Kudos

Ok ..... I did discover now that a copy routine did cause the problem but I cannot explain why.   I am attach the code of the routine.   Could anyone help and tell me why this would happen?   The areas that are commented out are the areas that did cause the problem.

 

moazzam_ali
Active Contributor
0 Kudos

Hi

Some ABAPER can help in this. I can see the dates which are not too old and if you ask the person who did this then you can have the idea behind this requirement.

Thank$