Contents

Introduction ................................................................................................................................................. 2
Setup RV60SBAT as a batch job ............................................................................................................ 5
Difference in billing batch job compared to any other batch job ............................................................ 5
How to find batch jobs ............................................................................................................................. 6
List of collective run ................................................................................................................................. 7

Introduction
Most of the business organizations would like to create their customer invoices in a batch job
(Background job). This batch job can be setup in a way that it executes in a pre-defined frequency (eg:
Once a day at night) and pick all documents that are due for billing. Such billing due documents can be
comprise of;

Sales orders in case of the third party orders for order related billing
Credit / Debit memo requests which does not have Billing block for order related billing
Post goods issues deliveries in case of delivery related billing

We can execute the as billing due list in SAP via transaction VF04.

If you execute this transaction manually, you have 3 options to choose.

 1. - One delivery document to one billing document online processing
2. - Combine multiple delivery documents in to one billing document
background processing
3. - Combine multiple delivery documents in to one billing document online
processing

Today lets look at how we can setup this transaction as a background job and key differences in this
billing batch job against any other.

If we look at the program assigned to VF04 transaction, thats SDBILLDL. But this is not the program
that you will have to setup as a batch job.

SAP has provided a separate program for invoice creation in background called RV60SBAT. This
program can be accessed via transaction VF06.


This program has all different tabs available in VF04 transaction under one screen

Setup RV60SBAT as a batch job

First you need to define a variant for this program based on your organization elements.

Transaction: SE38
Program: RV60SBAT

Then you can schedule that program as a batch job using transaction SM36

Please click here to see how you can set up any program as a batch job

Difference in billing batch job compared to any other batch job

When you schedule program RV60SBAT as a background job, it is not the actual program that creates
billing document via batch job.

The RV60SBAT program creates a new background job dynamically and schedule that new job for
invoice creation.

Eg:

Thats the program, which actually creates those invoices in SAP.
How to find batch jobs
Transaction: SM37

First you need to find your batch job that you have scheduled for RV60SBAT program. Using the spool
list of that program, you should be able to locate the name of the new batch job.

From the SM37 output screen, you can double click on the Icon.

From the result screen, when you double click on the Icon to view details.

You can see the new job name as shown below.

Now if you search that job name in Transaction SM37, you will see the new time that it was scheduled.

List of collective run

As an example, if you schedule billing documents in batch job using program RV60SBAT, you can view
those billing documents that got created using transaction V.21

Author: Anupa Wijesinghe

E-Mail: anupaw@gmail.com / anupaw@learnsaptips.com

Website: www.learnsaptips.com

View my profile in LinkedIn

Follow me on Twitter


Disclaimer

This article is done based on my research and readings, unless otherwise stated. The views expressed
are my own and not of anyone else.
Author accepts no liability for the content of the articles in this website or for the consequences of any
actions taken on the basis of the information provided. Using this information is at the users own
discretion and responsibility.