SAP Note 15999 - Processing batch input sessions in the background

Symptom:

You want to perform the following steps in background processing:
- Process a batch input session -with-
- Subsequent processing

It doesn't work?

Reason and Prerequisites

The batch input session disappears when started and does not return to the requesting program.
This means that processing a batch input session can only take place within one job (only one step).

Solution
Because no standard solution exists, we recommend the following procedure.
If you would like to do one of the following, this note is relevant for you.
Do you want to process several batch input sessions in a row in the background?
or
You want to start a subsequent session after processing a batch input session?

Information:
1. It is not possible to serialize processing using service report
RSBDCSUB. Why not? The report ends before the session is
processed.

2. There is no solution for the above questions.

Procedure:
1. You have to write you own report capable of starting batch input
sessions. Assume the report is called ZZBDCJOB.

2. Report ZZBDCJOB is the only step of a job.
Why? The batch input starts in the application, but does not
return to the requesting program.

3. How do you write report ZZBDCJOB?

The report contains the following steps:
1. The unique session name should be entered via the selection
screen. Example:
PARAMETERS: MAPPE LIKE APQI-GROUPID.
2. The folder name is used to select field APQI-QUD from screen
APQI
Example:
SELECT * FROM APQI
WHERE GROUPID EQ MAPPE.
ENDSELECT.
3. Once the field contents of APQI-QID have been selected, call
report RSBDCBTC and pass on the screen contents.
Example:
SUBMIT RSBDCBTC
WITH QUEUE-ID EQ APQI-QID.
(Note: As of Basis Release 6.10, the RSBDCBTC parameter is
QUEUE_ID rather than QUEUE-ID)
4. That describes reoughly the functionality of report ZZBDCJOB.

4. What does the job look like?
e.g. job name ZZBDCJOB: only one step with program ZZBDCJOB.

5. Job chains?
Defined using precedessor or successor jobs in the function
"Job definition" or transaction SM36.

Comment:
Even when the batch input disappears and no longer returns to the
requesting job, every job ends after processing a batch input
session.

Two example of job chains:

1. Example:
You want to process several batch input sessions in a row.
Your job chain appears as follows:
- JOB1 Report ZZBDCJOB
Process batch input session no. 1
- JOB2 Report ZZBDCJOB
Process batch input session no. 2
- JOB3 Report ZZBDCJOB
Process batch input session no. 3
etc.

2. Example:
You want to
- create a batch input session
- process that session and
- start a follow-on processing
Your job chain appears as follows:
- JOB1 Report ZZ??????
Create the batch input session
- JOB2 Report ZZBDCJOB
Process the batch input session
- JOB3 Report ZZ??????
Follow-on processing, analyze processing. etc.