Sap vepvg update

Billing Document Update - VF04 If a document is not displayed at all or incorrectly in the billing-due list, check the following points one after the other: The relevance for billing table TVAP of the document: if this was changed, consider Note For billing documents, you can achieve a redetermination of the status by means of a change of a header field in the billing document Note However, incorrectly, the system did not create an entry in the billing index. This report is described in Note The report can correct the following index tables: Select only what is appropriate as the running time can be quite long.

All rights reserved. All product names are trademarks of their respective companies. The site www. Messages of the type E or W cannot be output. Other notes The deletion of the delivery can no longer be prevented at this point by returning to the dialog, since all the delivery data has already been deleted logically. If the user has to prevent the deletion of the delivery for certain reasons, the system should issue an error message of the type A.

The routine is run exactly once every time the delivery document data is read in change or display mode of the delivery. Exception: The routine is not executed when reading deliveries during the subsequent delivery split and when enhancing deliveries. You have full access to all the data of the delivery that has just been read within the exit.

In principle, you can make changes in this exit to the delivery data read. There are no restrictions placed on the output of error messages and user dialogs in this exit. Note however that the exit is also run in the background:. In these cases, the output of a dialog box may cause processing to terminate because no batch input data is available for the dialog box.

In the case of deliveries with predecessor reference, the copy routine for transferring the preceding data is called once before and once after this exit. When importing data from these tables, make sure that the current header lines of the tables are not changed. Use local structures instead. Therefore, analyze the dependencies before you change standard fields in the table LIKP in this exit. Display of messages The exit must not be used for the direct output of error messages.

If this routine is run in change mode, messages are not output directly but collected in the log. Messages of the type W are not written to the log.

Other notes Note that changing data in the structure LIKP affects the delivery split during delivery creation. Call The routine is run exactly once for each item during the creation of delivery items. When you create items with predecessor reference, the routines of the copy control are called before and after this user exit.

No status information is available for the new item yet. If, prior to the current item, other items were already delivered in the same delivery, you can access the header status of the delivery using the table XVBUK. The status of the items that were generated in the same transaction or that already existed in the delivery can be read from the table XVBUP.

When you change standard fields of the item, note that checks and determinations with reference to these fields may have already been carried out and unchecked changes to these fields may result in data inconsistencies. Therefore, analyze any possible dependencies before making any changes to standard fields. Note that the item number for the new item is already assigned only for items without predecessor reference during the exit call.

It is not useful to change other data of the delivery in this exit. Here, you should only access other data of the delivery in read mode. Make sure that the current header lines of the internal tables are not changed. Define local structures to read data from your own internal delivery tables.

Display of messages The direct output of messages is not allowed in this exit because this can result in document inconsistencies. You can use the routine to determine the batch, which is to be assigned to the delivery item, in accordance with your own criteria.

Within the routine, you can access order item data that is already determined LIPS. The current header lines of the internal tables must not be changed. Use local structures to read data from internal tables instead. The exit must not be used for the direct output of error messages.

This routine can be used for the final change of all delivery data. At the time of the call, the delivery is complete and consistent; only the document number has not yet been determined in the creation case and the final processing of the requirements has not yet taken place.

Therefore, changes to the delivery at this time must be made with particular care because no subsequent checks can prevent possible data inconsistencies. Since requirements processing has not yet occurred, this user exit is, in particular, suitable for changes relevant for requirements when the delivery is saved. With the output of messages or user dialogs, you must make sure that this exit can be run both in the dialog and in the background.

In particular, during goods issue posting, messages or user dialogs must never be output because this may result in incorrect material documents. This routine is the most powerful exit in delivery processing and can be used for the final change of all delivery data.

At the time of the call, the delivery is complete and consistent, only the document number has not yet been determined in the creation case. Since the delivery is about to be saved, all relevant delivery data can be accessed. The current document status is in the X tables and the previous database status is in the corresponding Y tables. Note the following when accessing data:. Therefore standard routines, which require a previous correct positioning of the work areas, can also be called for processing.