0

Batch Input Processing

Contents:
 Batch input sessions
 Batch input monitor

 SAP AG 1999

© SAP AG BC420 7-1

0.2
Batch Input Processing: Unit Objectives

At the conclusion of this unit, you will be able to:

 Explain the structure of batch input sessions

 Process and analyze batch input sessions using
the batch input monitor

 SAP AG 1999

© SAP AG BC420 7-2

0.3
Course Overview Diagram

Call Transaction
Batch Input

Direct Input

TA Recorder
12 IDoc BAPI
77 9
10
11 12
Principles of Standard 4
Data Tansfer

DX Workbench 11
3 5
LSM Workbench
8 10 11

6 13
Basics

2 Datenübernahme 14

1 Course Overview

 SAP AG 1999

© SAP AG BC420 7-3

0.4
Batch Input Processing (1)

Batchinput
Batch inputsessions
sessions

Batchinput
Batch inputmonitor
monitor

 SAP AG 1999

© SAP AG BC420 7-4

0.5
Overview: Batch Input Processing

Monitor

DB
 SAP AG 1999

 Batch input, also known as Batch Data Communication (BDC) is an automated process used for
dialog-free transfer of data to the SAP System.
 In order to ensure the same checks and updates are executed as in dialog processing, a user dialog is
simulated.
 The central component of this method is the batch input session.
 These sessions are created using a batch input program and contain all data necessary to simulate the
user dialog.
 After the batch input sessions are created, you use the batch input monitor to process the sessions.
During processing, the online transactions are used to transfer the data to the R/3 database.

© SAP AG BC420 7-5

0.6
Batch Input Program

ABAP
ABAP Dictionary
BDC table

Structure
BDCDATA

 SAP AG 1999

 The data is transferred into the session by batch input programs. For standard transfer these
programs are provided in the DX-WB and for individual transfers they have to be created.
 Batch input programs have the following functions:
 They provide structured work areas for the data to be transferred in the form of an internal table
(BDC table).
 They import the data.
 They put the imported data into the BDC table.
 They transfer the filled BDC table into the session.
 The BDC table has always the same structure and contains the relevant transaction data for the
data transfer.

© SAP AG BC420 7-6

0.7
Format of Batch Input Session

Session - header
 Client in which the session can be processed
 Session name
 Lock date
 User for the background processing
 Still keep session ?

Transaction
Transaction
Session - body
Transaction

100 200 300

Session - complete

 SAP AG 1999

 A batch input session consists of a header part (session header described by the ABAP Dictionary
structure APQI) and a data part (transactions described by the ABAP Dictionary structure APQD).
 The session header contains general data about the whole session.
 The session body contains all the application-specific transaction data.
 The session complete closes the session; it can now be processed in the batch input monitor to
transfer it into the R/3 database.

© SAP AG BC420 7-7

0.8
Creating Batch Input Session

Open batch input session

Insert data for transactions

Close batch input session

 SAP AG 1999

 Each batch input session must be opened and closed.

 The data for the application functions (transactions) is inserted into the batch input session.
 The batch input session contains screen data from individual transactions.
 Data is inserted into the batch input session for each transaction. One transaction is inserted at at ime
into the session header.
 A batch input program can create one or more batch input sessions in succession.
 Batch input sessions cannot be created in parallel.

© SAP AG BC420 7-8

0.9
Structure of BDC Table

Program Screen No. Start of Field Name Field Value

Name Screen
PROGRAM
PROGRAM DYNPRO
DYNPRO DYNBEGIN
DYNBEGIN FNAM
FNAM FVAL
FVAL

SAPMF02D
SAPMF02D 0105
0105 XX
RF02D-KUNNR
RF02D-KUNNR Z-00-00001
Z-00-00001
RF02D-BUKRS
RF02D-BUKRS 0001
0001
RF02D-KTOKD
RF02D-KTOKD KUNA
KUNA
BDC_OKCODE
BDC_OKCODE /00
/00
SAPMF02D
SAPMF02D 0110
0110 XX
KNA1-ANRED
KNA1-ANRED Mr
Mr
KNA1-NAME1
KNA1-NAME1 Treusch
Treusch
KNA1-SORTL
KNA1-SORTL Axel
Axel
KNA1-NAME2
KNA1-NAME2
KNKA1-STRAS
KNKA1-STRAS Main
Main St.
St.
KNKA1-PFACH
KNKA1-PFACH
KNKA1-ORT01
KNKA1-ORT01 New
New York
York
KNKA1-PSTLZ
KNKA1-PSTLZ 69190
69190
KNKA1-ORT02
KNKA1-ORT02
...
...

 SAP AG 1999

 The data is structured within a BDCDATA table according to the screens in the transaction. Each
screen that is processed in the transaction must be identified in a BDCDATA record. This record uses
the fields PROGRAM, DYNPRO and DYNBEGIN. A separate BDCDATA record for each value
that can be entered in a field comes after this record. These records use the fields FNAM and FVAL.
 The field name for the OK code is always BDC_OKCODE for all screens. The field value of the OK
code when a function key is pressed is made up of the backslash '/' and the number of the function
button (e.g. '/11'). For other types of application actions (menu choices, pressing the SAVE icon etc.)
the field value of the OK code is an ‘=‘ followed by the function code (e.g. ‘=save’).
 The BDCDATA structure is defined in the ABAP Dictionary as follows:
 Field Name Data Element Type Length Short Description
 PROGRAM BDC_PROG CHAR 40 BDC Module pool
 DYNPRO BDC_DYNR NUMC 4 BDC Screen number
 DYNBEGIN BDC_START CHAR 1 BDC Start of screen
 FNAM FNAM_____4 CHAR 132 BDC Field name
 FVAL BDC_FVAL CHAR 132 BDC Field value

© SAP AG BC420 7-9

0.10
Processing a Batch Input Session

Monitor

........
Transaction 1 Transaction n

Queue ID
20000101....
20000102.... Log

DB
 SAP AG 1999

 A batch input session gathers the individual screens of a transaction together.

You process these sessions using the batch input monitor. This process is the same as when you
execute the corresponding application transaction on foreground; the data is passed through the
screens and is then posted into the relevant SAP tables and the status records are written to the log
file.
 The batch input function starts the application functions specified in that session (transactions
identified by their transaction codes).
 The data from the session is then merged into the screens of the specified online transaction.
 With change transactions the data from the SAP database is first merged and then the data from the
session is merged into the screens.
 With the batch input procedure data is always posted synchronously. With other procedures, which
will be described later, data can also be posted asynchronously.

© SAP AG BC420 7-10

0.11
Batch Input Processing

Batchinput
Batch inputsessions
sessions

Batchinput
Batch inputmonitor
monitor

 SAP AG 1999

© SAP AG BC420 7-11

0.12
The Batch Input Monitor

Menu Edit Favorites Extra System Help

Create session
Delete session
SAP Easy Access
User profile
Services Reporting
... ...
Favorites
SAP ..

Batch input Sessions

Fast input Logs
Direct input Recorder
Restart transaction
Delete transaction
Next transaction
Process foreground
Display errors only
Expert mode on
Expert mode off
Initial screen of the
Cancel
batch input monitor
(SM35)
Monitor
These functions are
only active during
“Process foreground"
of a session
 SAP AG 1999

 The batch input monitor can be called from the system menu.
 The functions greyed out are only available when batch input sessions are processed in the
foreground.

© SAP AG BC420 7-12

0.13
Functions of the Batch Input Monitor

Batch
Batch input
input sessions
sessions
Overview
Overview Batch
Batch input
input run
run logs
logs
Locked
Locked sessions
sessions

Process
Process in
in foreground
foreground
Process
Process Display
Display errors
errors only
only
Process
Process in
in background
background

Display
Display session
session contents
contents
Monitor Display
Display batch input
batch input data
data
Analyze
Analyze Logs
Logs (extended
(extended log)
log)
Statistics
Statistics

Delete
Delete sessions
sessions (selective)
(selective)
Admin
Admin Lock
Lock sessions
sessions
Release
Release sessions
sessions

 SAP AG 1999

 The batch input monitor provides a range of functions for processing the sessions.
 Sessions can be processed further with the batch input monitor. You can get information about the
status, screen sequence, screen contents, processors (users), processing mode, server and which user
has been used for the user authorization.
 The system always flags transactions that cannot be processed because of errors. These transactions
remain the session (error session). You can correct the errors and reprocess these transactions.
 The functions can be accessed from buttons/menus in the monitor.

© SAP AG BC420 7-13

0.14
Initial Screen of Batch Input Monitor

From the list of BI sessions a session can be selected

and, for example, processed.

Analyze Process Statistics Log ...

Selection
Session * From: 01.01.1999 To: 27.09.1999 First *

All New With errors Processed In process Background In creation Locked

Session name Creator Date Time Lock date Authoriz. Status

BC420_MAP1 Klingels 27.07.1999 07:14 Klingels new
BC420_MAP2 ...
BC420_0815 ...
Session-7 ...
...

 SAP AG 1999

 On the initial screen of the batch input monitor you can select and process single sessions or look at
the logs of sessions already processed.

© SAP AG BC420 7-14

0.15
Processing Mode

Displays dialog steps only

Process Online if there are error or
termination messages All message types are
included later in log

Run mode
Process/foreground Extended log
Display errors only Expert mode
Background
Destination Dynpro standard size

Pass to background processing; leave field “Target

computer“ free so that load is automatically distributed.
The screen standard size
is used for processing
data.
 SAP AG 1999

 The following processing modes can be selected:

 Processing mode:
- Process in foreground: transactions run in a foreground dialog (interactive processing of the
session).
- Display errors only: transactions run in the background. If an error is encountered, the appropriate
screen is displayed in the foreground for user correction.
- Background: transactions run in a background process.
Target system: optionally allows you to specify the target computer for background processing of
the session. If you do not specify this parameter, the system will choose an application server based
on automatic load balancing (recommended!).
 Additional functions:
- Extended log: W”, “I” and “S” messages can also be recorded in addition “E” messages. You can
also use this option when processing files in the background.
- Expert mode: the expert mode only works in interactive batch input. It switches the error message
344 off - that is, you can execute additional functions in batch input without getting the message each
time - “Batch input data is not available for this screen“.
- Screen standard size: automatic creation of screen standard size when processing in dialog
(relevant for table controls or step loops).

© SAP AG BC420 7-15

0.16
Menu Functions for Processing in Foreground

Menu Edit Favorites Extras System Help

Create session
End session
SAP Easy Access
User profile
Services Reporting
Utilities QuickViewer
Favorites
SAP... Output controller
Table maintenance
Batch input Sessions
Fast entry Logs
Direct input Recorder
Restart transaction
Delete transaction
Next transaction
Process/foreground
Display errors only
Export mode on
Expert mode off
Active when processing batch Cancel

input sessions in foreground

 SAP AG 1999

 Additional session functions are available when processing batch input sessions in the foreground.
These can also be called from the command line using special OK codes.

© SAP AG BC420 7-16

0.17
The Functions and OK codes
Functions & allowed Ok codes Description

Next
Next transaction
transaction End
End running
running batch
batch input
input transaction
transaction
/n and flag as incorrect
and flag as incorrect

Delete
Delete transaction
transaction Delete
Delete running
running batch
batch input
input transaction
transaction
/bdel in the session
in the session

Cancel
Cancel End
End batch
batch input
input processing
processing and
and
/bend flag
flag session
session as
as incorrect
incorrect

Process
Process in
in foreground
foreground Switch
Switch display
display mode
mode from
from ”Display
”Display errors
errors only”
only”
/bda after ”Process in foreground”
after ”Process in foreground”

Display
Display only
only errors
errors Switch
Switch display
display mode
mode from
from process
process in
in foreground”
foreground”
/bde to ”Display errors only”
to ”Display errors only”

When
When leaving
leaving BI
BI processing
processing
Expert
Expert mode
mode error
error messages
messages are
are suppressed
suppressed

Restart
Restart transaction
transaction
/bbeg Back
Back to
to start
start of
of transaction
transaction
 SAP AG 1999

 If you are processing a session interactively, you can correct the transactions online or flag them as
incorrect transactions. The corrections will be included in the session log.
 If you are processing a session interactively (process in foreground or display errors only), the
ENTER button must be pressed to be able to switch between screens. On each screen you can correct
data, or process the session using specific menu functions (see slide) or OK code entries.

© SAP AG BC420 7-17

0.18
Session Statuses

New
New Session
Session created,
created, but
but not
not yet
yet processed
processed

Session
Session processed,
processed, some
some transactions
transactions
Error
Error contain
contain errors
errors

Processed
Processed Session
Session processed
processed successfully
successfully

In
In processing
processing Session
Session currently
currently being
being processed
processed

Session
Session currently
currently being
being processed
processed in
in
In
In background
background background
background

Session
Session currently
currently being
being created
created
Creation
Creation by
by a BI program or recording
a BI program or recording

Session
Session is
is locked
locked and
and
Locked
Locked cannot be processed
cannot be processed

 SAP AG 1999

 A session is assigned a status, displayed in the session overview, before, during, and after processing.
 The sessions are sorted by the date and time they were created and displayed according to status.
 In the overview, the following information is displayed for each session:
Session name:
Name of the session
Date and time:
The data and time the session was created.
Locked:
Session is locked until this date and cannot be processed until then.
Created by:
User who created the session.
Transaction and screen:
Number of transactions and screens.
Authorization:
The user whose authorization is used to process the session (only for background processing).

© SAP AG BC420 7-18

0.19
Notes for Processing BI Sessions in Foreground

 Do not branch to other transactions ("/n...")

 Paging only possible using ENTER

 In R/3 Release 4.6, corrections during foreground

processing are noted in log

Note:
Data from the session
is displayed in red

 SAP AG 1999

 Do not navigate to other transactions (using /nxxxx or /oxxxx while processing a batch input session.
 When processing in foreground, move from screen to screen by pressing ENTER.

© SAP AG BC420 7-19

0.20
Session Statistics

Statistics
The session statistics show the number and
status of the transactions in the batch input
session.

Session Statistics BC420_Map1

Status Transactions Screens

Error 0 0
Processed 1 7
Deleted 0 0
Still to be processed 1 7

Total 2 14

 SAP AG 1999

 Statistics can be displayed for every session. This includes the total number of transactions in the
session as well which transactions:
 Have errors
 Were processed
 Were deleted
 Still need to be processed

© SAP AG BC420 7-20

0.21
Session Log

Log Select Log for Batch Input Session

Log Attributes
Name BC420_Map1 User Roberts

Created on 02.11.1999 Queue ID 1129273223..

Time Message
13:34:25 >>> Session BC420_Map1 Run by Roberts in Session A on ...
13:34:45 >>> Field RF02D-KUNNR Changed: z-88-10002 ( Previously: z-88-10001 )
13:34:46 Customer Z-00-80002 Created in Company Code 0001
13:35:03 Processing statistics
13:35:04 1 transaction read
13:35:04 1 transaction processed
13:35:04 0 transactions (with errors)
13:35:04 0 transactions deleted

 SAP AG 1999

 A log is generated for every batch input session run.

 If there are errors during processing, the session is marked with status “Error”. If the session is
processed again, an additional log is generated.
 All error messages from transactions in the session are logged in the session log. This log also
contains batch input error messages generated due to problems during processing of transactions.
The transaction error information includes the transaction code and the screen where the error
occurred. The log also contains “Total” statistics.

© SAP AG BC420 7-21

0.22
Session Analysis

Analysis

 Overview of all transactions contained in the session

 Overview of transactions in session that have errors
 Screen description (list of fields for each transaction)
 Screen display for each screen in the transaction
 Easy navigation to the transaction logs

 SAP AG 1999

 You can go to the session analysis even before you choose “Process / foreground”. This allows you
to display the transactions and screens.
 After the session is run, you can display several different overviews of errors that occurred during
the run as well as a list of the transactions not yet processed in the session.

© SAP AG BC420 7-22

0.23
Session Analysis

Analysis

Display
All Incorrect

Transactions Screens Log for 13.08.1999

Session information
Index Trans Status
Name Test session
1 XD01 Error Created on 13.08.1999
2 XD01 Error Created at 12:24:54
Created by Roberts
3 XD01 Error ...
Statistics
Transactions Screens
Total 5 35
Incorrect 3 21
Processed 0 0
Deleted 0 0

 SAP AG 1999

 The session analysis is divided into three tabbed areas:

 “Transactions”: Provides a list of all transactions in the session along with their status.
 “Screen”: Displays an overview of the screens in each transaction. You can simulate (display) each
screen including the data it contains.
 “Log”: Provides a list of all session logs.

© SAP AG BC420 7-23

0.24
Session Analysis - Screen Field List

Screens Display Field List

Transactions Screens Log for 13.08.1999

Program Screen Field Value

SAPMF02D 0105
BDC_CURSOR RF02D-KTOKD
BDC_OKCODE /00
RF02D-KUNNR Z-88-10001
RF02D-BUKRS 0001
RF02D-KTOKD KUNA
SAPMF02D 0110 ...
BDC_CURSOR KNA1-SPRAS
BDC_OKCODE /00
KNA1-ANRED Ms.
KNA1-NAME1 Roberts
...

 SAP AG 1999

 The field list display under the “Screens” tab displays the screen data according to the BDCDATA
structure.

© SAP AG BC420 7-24

0.25
Session Analysis - Screen Display

Screen Select (or double-click)

Simulation of Screen SAPMF02D 0105

Customer Z-88-10001

Company code 0001

Account group KUNA

Template
...

 SAP AG 1999

 To choose “Screen simulation” (screen display) double-click a screen

© SAP AG BC420 7-25

0.26
User Settings in BI Monitor

Utilities Default values

Settings for user “Miller“

Initial screen Session name

Gen. overview BC420_*
New
Incorrect Created by
Processed Miller
In processing
In background
Being created
Locked

 SAP AG 1999

 Each user can specify in the “default settings" his own basic setttings for the batch input monitor. For
example, only sessions with the prefix "BC420*" may be selected.

© SAP AG BC420 7-26

0.27
Exporting and Importing BI Sessions

External system
Other
Excel tools

R/3

Exporting / importing BI sessions at operating system levels

for further processing with other tools

 SAP AG 1999

 Under Utilities -> Export /import sessions (in batch input monitor) session contents can be imported
and exported at the operating system level.
 Further processing would be possible with an external software tool.

© SAP AG BC420 7-27

0.28
Import / Export Program Options

Utilities Import / Export session

Import or Export of Batch Input Objects

Export
Object This BI session is to be
Session exported to this
Recording directory under this file
Object name BC420-Map1 name

Import

Location of the file to be imported or written

File from application server
Logical file name
or
Physical file name /tmp/BDC_OBJECT_ROBERTS
...

 SAP AG 1999

 Import and export are executed on the application server using physical or logical file names, which
are set in R/3 Basis Customizing (transaction FILE).

© SAP AG BC420 7-28

0.29
Batch Input Processing: Unit Summary

You are now able to:

 Explain the structure of batch input sessions

 Process and analyse batch input sessions using
the batch input monitor

 SAP AG 1999

© SAP AG BC420 7-29

 Exercises
Unit: Batch Input Processing
Topic: Working with Batch Input Sessions

 Working with the Batch Input Monitor.

 Running of Batch Input Sessions.

The batch input session, which has been created out of the DX-WB, is
run with the batch input monitor. This is how the legacy data are
transfered to the R/3 system.

1 Run the BI session BC420SES-## (see BGR00 record layout).

1-1 Import the BI session that you created before in the "Display all mode" in the
R/3 system. (Name: BC420SES-## see BGR00 record layout)
While the system is running the session, change one address field of a debtor,
e.g. change the place of residence.
Then switch the processing mode to "Display errors only".
1-2 Analyze the log of the run and find out if errors occured. Has the change of the
debtor address been recorded during the run? __________
1-3 Analyze the session statistics.

2 Optional: Repeat a BI session with errors.

2-1 Start the run of the previous task again in the DX-WB:
A new file with debtor data must be read. On the selection screen, use the file
BC420_DEBI_ERR.LEG as the. Use it to generate the debtors “Z-##-20001”
bis “Z-##-20010”, by changing the prefix on the selection screen. Create
another BI session again.
2-2 Switch to the BI monitor and run the session in the background.Wechseln Sie in
den BI-Monitor und spielen Sie die.
2-3 Analyze the log of the run. What kind of errors occurred?
_________________________________________________________

Correct the errors by running the session again in the "Display all mode"!

© SAP AG BC420 7-30

 Solutions

Chapter: Batch Input Processing

1 Run the BI session BC420SES-## (see BGR00 record file).

1-1 Change a customer location and switch to "Only display errors" during
the BI session:
choose the path "System->Services->Batch Input->Only display errors"
or enter the function code "/BDE" in the command field. All subsequent
customers are processed in the background. You can see the result in the
log.
1-2 Field changes are logged. The session has the status "processed" after
changes in foreground processing.

2 Optional: Repeat a BI session with errors.

2-2 A BI session has errors.
a) The first customer in the old file had no customer number and was
classified as with errors by the conversion program. See the error file
(extension "ERR") This customer is not entered in the record file and the
BI session.
b) The last (ninth) customer had no country in the address data. This
record and its transaction are flagged as errors in the BI session.

2-3 The session has the status "error".

The log contains: "Fill all required fields" "transaction error". You can
display the filled fields of the screen in the screen view.

© SAP AG BC420 7-31