February 11, 2013 3 minute read

New key figure: Analyzing/Monitoring exceptions during billing due processing

Similar to what I wrote in my previous blog about the delivery due processing (http://scn.sap.com/community/it-management/alm/solution-manager/blog/2013/02/11/new-key-figures-analyzingmonitoring-exceptions-during-delivery-due-processing), the SAP system also logs error messages during every billing due processing – no matter if performed in dialog or background mode. For many, many years you could only analyze those messages via transaction V.21 or report SDSAMAN4 – the later is probably not known to many of you. Anyway this “old” transaction V.21 has several limitations

On the selection screen you can only filter on creation user and creation date
No context information like billing type or SOrg etc. is provided in the output list
No information is given if the exception is still valid or if the document has been posted meanwhile
No reference date (like billing date) is available in the output list
No overview about exception messages is given
No differentiation between order-related , delivery-related, inter-company billing is made.

All these limitations have been overcome with a new SAP Solution Manager key figure “Exceptions during billing due processing” that is shipped with the latest ST-A/PI 01Q*. The new ST-A/PI can be downloaded via the SAP Service Marketplace http://service.sap.com/supporttools. You can use this new key figure for Business Process Analytics or Business Process Monitoring in SAP Solution Manager. You can find the new key figures in the setup environment at

Application Area “Sales & Services” > SD Invoices (AR) > Exceptions during billing due processing

This key figure provides log information with different context information. Every entry in the result list still requires a billing document creation, i.e. the corresponding sales order or delivery is still in table VKDFS. The column Number of shows how often the same exception for the same item was raised within the selected time frame. The Error Message Text immediately indicates the problem, e.g. proof of delivery missing, blocking situation, incomplete order, master data not maintained, a certain delivery type cannot be invoiced with the selected billing type. The column Billing Block can provide some additional insights on the blocking reason and Proof of Delivery Status can be used as cross-check if that the POD is really missing.

Example screenshots

An example detail list for “Exceptions during billing due processing” could look as follows:

New key figure: Analyzing/Monitoring exceptions during billing due processing

Example screenshots

Further reading

Assigned Tags