SAP Note

Header Data

Symptom

A billing document is created either by VF01 or collective processing, but the document is not available in VF02, VF03; the user receives an express mail reporting an update termination. There is also a gap in invoice number range interval. Transaction SM13 shows that the update termination occurred in function RV_MESSAGE_UPDATE.

Other Terms

VF04, update terminate, express document, VF041

Reason and Prerequisites

This is a problem of the output program. The output programs are processed depending on the field 'Dispatch time'. The Dispatch time can be set: - in the Default values tab of customizing output type (transaction V/40) - in the output master record (transaction VV31, VV32) - directly in the billing document, menu Goto -> Header -> Output If the Dispatch time = '4' - Send immediately (when saving the application), then the output program is performed in update task. In this case, if a problem occurs in output program, an update termination occurs in function RV_MESSAGE_UPDATE. As explained in note 24279, this causes a gap in invoice number range interval.

Solution

By transaction SM13 it is possible to see the data passed to function RV_MESSAGE_UPDATE when termination occurred (button 'Display Update Data' <Ctrl+Shift+F6>). In the internal table MSG_XNAST notice the following fields: - OBJKY is the billing document number (which has not been saved) - KSCHL is the output type - VSZTP is the Dispatch time. The outputs with VSZTP = '4' are the potential responsible for the update termination. To be able to save the billing document, it is enough to change the Dispatch time from '4' to '3' (for example) during VF01. In this way the output program is not performed when the billing document is saved in the database. So the billing document can be saved. The output can be processed afterwards by VF31 (if Dispatch time '3'), once the problem in the output program is resolved. The output program is linked to output type in customizing transaction V/40, option 'Processing routines'. SAP Support only takes care of problems related to standard program/form. For example the standard billing print program/form are: program RVADIN01, form routine ENTRY, form RVINVOICE01; in the case of smartform they are: program RLB_INVOICE, form routine ENTRY, smartform LB_BIL_INVOICE. If custom program/form are used, then this is not SAP Support issue, but consulting issue.

Validity

This document is not restricted to a software component or software component version

References

    423130 - Update termination when create billing document  

Version   2     Validity: 11.11.2013 - active   Language   English (Master)

Released On 11.11.2013 12:54:14

Release Status Released for Customer

Component SD-BIL-GF-OC Output Control Billing

SD-BIL-IV Processing Billing Documents

Priority Recommendations / Additional Info

Category Help for error analysis

Other Components

This document refers to:

SAP Notes

This document is referenced by:

SAP Notes (1)

24279   Missing billing document numbers in VBRK

24279   Missing billing document numbers in VBRK