A batch input session is a set of one or more calls to transactions along
with the data to be processed by the transactions. The system normally executes
the transactions in a session non-interactively, allowing rapid entry of bulk
data into an R/3 System.
A session records transactions and data in a special format that can be
interpreted by the R/3 System. When the System reads a session, it uses the data
in the session to simulate on-line entry of transactions and data. The System
can call transactions and enter data using most of the facilities that are
available to interactive users.
For example, the data that a session enters into transaction screens is
subject to the same consistency checking as in normal interactive operation.
Further, batch input sessions are subject to the user-based authorization
checking that is performed by the system.
Generating Sessions
To transfer data with batch-input, the system
that is sending the data uses a data transfer interface provided by an R/3
application program in the receiving system. The interface program in the
application then produces a batch input session.
The interface program in an application is an
ABAP/4 program that sets up the transaction calls and data that make up a
session. If the batch input session contains data from an external source, the
program also reformats the data to meet the requirements of the input fields in
which the data is to be entered. Usually, such programs are provided by the R/3
applications.
Basis Programming Interfaces.
Authorizations
When a session is generated, a client and user are associated with it. If the
session is run in background-processing mode, the system uses this user for
authorization checking as the session runs. This authorization testing applies
whether you sent the job for batch execution or the session was started by a
background job.
Sessions that you process in one of the interactive modes are run with your
authorizations. The interactive modes are described later in this section.
