BC420_46C - 004Batch Input Processing

8/11/2019 BC420_46C - 004Batch Input Processing

1/31

0

SAP AG 1999

Batch input sessions

Batch input monitor

Contents:

Batch Input Processing

SAP AG BC420 4-1


2/31

0.2

SAP AG 1999

Explain the structure of batch input sessions

Process and analyze batch input sessions usingthe batch input monitor

t the conclusion of this unit! you "ill be able to:

Batch Input Processing: #nit $b%ecti&es

SAP AG BC420 4-2


3/31

0.'

SAP AG 1999

Course $&er&ie" (iagram

(aten)bernahme

(* +or,bench

- / +or,bench

Principles of tandard(ata ansfer

( i r e c

t I n p u

t

B PI

0

1 e c o r d e r

Course $&er&ie"

B a

t c h I n p u

t

C a

l l 0 r a n s a c

t i o n

'

E(I

Basics

3

4 506

50

6

55

53

5'

52

55

52

5

2

33

55

SAP AG BC420 4-3


4/31

0.3

SAP AG 1999


Batch Input essionsBatch Input essions

Batch Input /onitor Batch Input /onitor

SAP AG BC420 4-4


5/31

0.7

SAP AG 1999

$&er&ie": Batch Input Processing

(B

Processing with the

BI monitor 1 B(C #B

Automatic processing

Batch input, also known as Batch Data Communication (BDC) is an automated process used fordialog-free transfer of data to the SAP System

!n order to ensure the same checks and updates are e"ecuted as in dialog processing, a user dialog issimulated

#he central component of this method is the $atch input session

#hese sessions are created using a $atch input program and contain all data necessary to simulate theuser dialog

Processing the sessions using the BI monitor:#hen you use the the $atch input monitor to process the sessions %rom here the data is transferred tothe &' data$ase

Automatic processing:ith program &SBDCS*B B! sessions can $e processed automatically (see also +Special ethods +and +Batch+ in the appendi")

SAP AG BC420 4-5


6/31


7/31

0.

SAP AG 1999

9ormat of Batch Input ession

TransactionTransaction

ession complete

Client in "hich the session can be processedession name-oc, date#ser for the bac,ground processingtill ,eep session ;

ess ion header

Transactionession body

500 200 '00

A $atch input session consists of a header part (session header descri$ed $y the ABAP Dictionarystructure AP0!) and a data part (transactions descri$ed $y the ABAP Dictionary structure AP0D)

#he session header contains general data a$out the whole session

#he session $ody contains all the application-specific transaction data

#he session complete closes the session1 it can now $e processed in the $atch input monitor totransfer it into the &' data$ase

SAP AG BC420 4-7


8/31

0.4

SAP AG 1999

Creating Batch Input ession

$pen batch input session

Insert data for transactions

Close batch input session

2ach $atch input session must $e opened and closed

#he data for the application functions (transactions) is inserted into the $atch input session

#he $atch input session contains screen data from indi idual transactions

Data is inserted into the $atch input session for each transaction 3ne transaction is inserted at at imeinto the session header

A $atch input program can create one or more $atch input sessions in succession

Batch input sessions cannot $e created in parallel

SAP AG BC420 4-8


9/31

0.6

SAP AG 1999

tructure of B(C able

P/902( 0507 *1902( 00 000051902( B#


10/31

0.50

SAP AG 1999

Processing a Batch Input ession

-og

ransaction 5 ransaction n

........

Monitor

Queue ID

20000502....20000505....

(B

A $atch input session gathers the indi idual screens of a transaction together

5ou process these sessions using the $atch input monitor #his process is the same as when youe"ecute the corresponding application transaction on foreground1 the data is passed through thescreens and is then posted into the rele ant SAP ta$les and the status records are written to the logfile

#he $atch input function starts the application functions specified in that session (transactionsidentified $y their transaction codes)

#he data from the session is then merged into the screens of the specified online transaction

ith change transactions the data from the SAP data$ase is first merged and then the data from thesession is merged into the screens

ith the $atch input procedure data is always posted synchronously ith other procedures, whichwill $e descri$ed later, data can also $e posted asynchronously

SAP AG BC420 4-10


11/31

0.55

SAP AG 1999


Batch Input essionsBatch Input essions

Batch Input /onitor Batch Input /onitor

SAP AG BC420 4-11


12/31

0.52

SAP AG 1999

F !orite"

SAP ##

SAP SAP asy asy Access Access

Cre te "e""ion

De$ete "e""ion

%"er &ro'i$e

Ser!i(e"

###

)e&ortin*

###

Batch input

F "t in&ut

Dire(t in&ut

Menu +,it F !orite" + tr S."te/ e$&

essions

-ogs

1ecorder

1estart transaction

(elete transaction

=ext transaction

Process foreground

(isplay errors only

Expert mode on

Expert mode off

CancelInitial screen of the!atch input monitor "S#$%&

These functions areonly acti'e during (Process foreground) of a session

he Batch Input /onitor

Monitor

#he $atch input monitor can $e called from the system menu

#he functions greyed out are only a aila$le when $atch input sessions are processed in theforeground

SAP AG BC420 4-12


13/31

0.5'

SAP AG 1999

Batch input sessionsBatch input run logs-oc,ed sessions

Batch input sessionsBatch input run logs-oc,ed sessions

$&er&ie"$&er&ie"

(isplay session contents

(isplay batch input data-ogs extended logFtatistics

(isplay session contents

(isplay batch input data-ogs extended logFtatistics

nalyzenalyze

(elete sessions selecti&eF-oc, sessions1elease sessions

(elete sessions selecti&eF-oc, sessions1elease sessions

dmindmin

Process in foreground(isplay errors onlyProcess in bac,ground

Process in foreground(isplay errors onlyProcess in bac,ground

ProcessProcess

9unctions of the Batch Input /onitor

Monitor

#he $atch input monitor pro ides a range of functions for processing the sessions

Sessions can $e processed further with the $atch input monitor 5ou can get information a$out thestatus, screen se@uence, screen contents, processors (users), processing mode, ser er and which userhas $een used for the user authori ation

#he system always flags transactions that cannot $e processed $ecause of errors #hese transactionsremain the session (error session) 5ou can correct the errors and reprocess these transactions

#he functions can $e accessed from $uttons'menus in the monitor

SAP AG BC420 4-13


14/31

0.53

SAP AG 1999

Se""ion

An $. e

Se$e(tion

Fro/ 01#01#1999

Pro(e"" St ti"ti(" o*

o 27#09#1999 Fir"t

...

e it error" Pro(e""e, In &ro(e"" B ( *roun, In (re tion o( e,ll

Se""ion n /e Cre tor i/e o( , teBC320?/ P5

D te Aut ori # St tu"2 .0 .5666

BC420:MAP2BC420:0815Se""ion-7###


15/31

0.57

SAP AG 1999

Process@foreground

De"tin tion

1un mode

(isplay errors only

Bac,ground

+ ten,e, $o*

+ &ert /o,e

D.n&ro "t n, r, "i e

Process

Pass to !ac,ground processing- lea'e field (Target computer( free so that load is automatically distri!uted.

nlineDisplays dialog steps only if there are error or termination messages All message types are

included later in log

The screen standard si/eis used for processing data.

Processing /ode

#he following processing modes can $e selected/

Processing mode:

Process in foreground/ transactions run in a foreground dialog (interacti e processing of thesession)

Display errors only/ transactions run in the $ackground !f an error is encountered, the appropriatescreen is displayed in the foreground for user correction

Background/ transactions run in a $ackground process#arget system/ optionally allows you to specify the target computer for $ackground processing ofthe session !f you do not specify this parameter, the system will choose an application ser er

$ased on automatic load $alancing (recommended )

Additional functions:

2"tended log/ , +! and +S messages can also $e recorded in addition +2 messages 5ou canalso use this option when processing files in the $ackground

2"pert mode/ the e"pert mode only works in interacti e $atch input !t switches the error message off - that is, you can e"ecute additional functions in $atch input without getting the message

each time - + Batch input data is not available for this screen +

Screen standard si e/ automatic creation of screen standard si e when processing in dialog(rele ant for ta$le controls or step loops)

SAP AG BC420 4-15


16/31

0.58

SAP AG 1999

F !orite"

SAP###

SAP asy AccessSAP asy Access

Cre te "e""ion

+n, "e""ion

%"er &ro'i$e

Ser!i(e"

%ti$itie"

)e&ortin*

Qui( ;ie er


17/31

0.5

SAP AG 1999

End running batch input transactionand flag as incorrectEnd running batch input transaction

and flag as incorrect

(elete running batch input transaction in the session

(elete running batch input transaction in the session

End batch input processing andflag session as incorrect

End batch input processing andflag session as incorrect

"itch display mode from H(isplay errors onlyHafter HProcess in foregroundH

"itch display mode from H(isplay errors onlyHafter HProcess in foregroundH

"itch display mode from process in foregroundHto H(isplay errors onlyH

"itch display mode from process in foregroundHto H(isplay errors onlyH

=ext transaction=ext transaction

(elete transaction(elete transaction

CancelCancel

Process in foregroundProcess in foreground

(isplay only errors(isplay only errors

Functions 0 allowed , codes Description

Expert mode

Expert mode

+hen lea&ing BI processingerror messages are suppressed

+hen lea&ing BI processingerror messages are suppressed

@n

@bdel

@bend

@bda

@bde

he 9unctions and $< codes

1estart transaction1estart transaction @bbeg Bac, to start of transactionBac, to start of transaction

@bdx

!f you are processing a session interacti ely, you can correct the transactions online or flag them asincorrect transactions #he corrections will $e included in the session log

!f you are processing a session interacti ely (process in foreground or display errors only), the26#2& $utton must $e pressed to $e a$le to switch $etween screens 3n each screen you can correctdata, or process the session using specific menu functions (see slide) or 39 code entries

SAP AG BC420 4-17


18/31

0.54

SAP AG 1999

=e"=e" ession created! but not yet processedession created! but not yet processed

Error Error ession processed! some transactionscontain errorsession processed! some transactions

contain errors

ProcessedProcessed ession processed successfullyession processed successfully

In processingIn processing ession currently being processedession currently being processed

In bac,groundIn bac,ground ession currently being processed inbac,groundession currently being processed inbac,ground

CreationCreation ession currently being createdby a BI program or recordingession currently being created

by a BI program or recording

-oc,ed-oc,ed ession is loc,ed andcannot be processedession is loc,ed andcannot be processed

ession tatuses

A session is assigned a status, displayed in the session o er iew, $efore, during, and after processing

#he sessions are sorted $y the date and time they were created and displayed according to status

!n the o er iew, the following information is displayed for each session/

Session name/ 6ame of the session

Date and time/#he data and time the session was created

8ocked/

Session is locked until this date and cannot $e processed until thenCreated $y/*ser who created the session

#ransaction and screen/ 6um$er of transactions and screens

Authori ation/#he user whose authori ation is used to process the session (only for $ackground processing)

SAP AG BC420 4-18


19/31

0.56

SAP AG 1999

(o not branch to other transactions @n... F

Paging only possible using NT 1

In 1@' 1elease 3.8! corrections during foreground processing are noted in log

=otes for Processing BI essions in 9oreground

=ote:(ata from the sessionis displayed in red

Do not na igate to other transactions (using 'n"""" or 'o"""" while processing a $atch input session

hen processing in foreground, mo e from screen to screen $y pressing ENTER

SAP AG BC420 4-19


20/31

0.20

SAP AG 1999

St tu" r n" (tion" S(reen"

+rror 0 0

Pro(e""e, 1 7

De$ete, 0 0

Sti$$ to =e &ro(e""e, 1 7

ot $ 2 14

tatistics

Session Statistics BC420_Map1

The session statistics show the num!er and status of the transactions in the !atch input session.

ession tatistics

Statistics can $e displayed for e ery session #his includes the total num$er of transactions in thesession as well which transactions/

Ea e errors

ere processed

ere deleted

Still need to $e processed

SAP AG BC420 4-20


21/31

0.25

SAP AG 1999

-og

/e

-og ttributes

%"er )o=ert"BC320?/ap5

Cre te, on Queue ID 1129273223##02.55.5666

ime /essage13 34 25

13 34 45

13 35 0313 35 04

13 35 0413 35 04

>>> Fie$, )F02D-?% ) C n*e, -88-10002 @ Pre!iou"$. -88-10001

>>> Se""ion BC420:M &1 )un =. )o=ert" in Se""ion A on ###

Pro(e""in* "t ti"ti(" 1 tr n" (tion re ,

1 tr n" (tion &ro(e""e,0 tr n" (tion" @ it error"0 tr n" (tion" ,e$ete,13 35 04

Se$e(t o* 'or B t( In&ut Se""ion

13 34 46 Cu"to/er -00-80002 Cre te, in Co/& n. Co,e 0001

ession -og

A log is generated for e ery $atch input session run

!f there are errors during processing, the session is marked with status +2rror !f the session is processed again, an additional log is generated

All error messages from transactions in the session are logged in the session log #his log alsocontains $atch input error messages generated due to pro$lems during processing of transactions#he transaction error information includes the transaction code and the screen where the erroroccurred #he log also contains +#otal statistics

SAP AG BC420 4-21


22/31

0.22

SAP AG 1999

ession nalysis

nalysis

$&er&ie" of all transactions contained in the session

$&er&ie" of transactions in session that ha&e errors

creen description list of fields for each transactionF

creen display for each screen in the transactionEasy na&igation to the transaction logs

5ou can go to the session analysis e en $efore you choose +Process ' foreground #his allows youto display the transactions and screens

After the session is run, you can display se eral different o er iews of errors that occurred duringthe run as well as a list of the transactions not yet processed in the session

SAP AG BC420 4-22


23/31


24/31

0.23

SAP AG 1999

S(reen"

creens o* 'or 13#08#1999r n" (tion"

Pro*r /

SAPMF02D 0105

S(reen

BDC:C%)S


25/31

0.27

SAP AG 1999

creen Se$e(t @or ,ou=$e-($i(

imulation of creen P/902( 0507

-88-10001Customer

0001Company code

?% Account group

e/&$ te

...

ession nalysis creen (isplay

#o choose +Screen simulation (screen display) dou$le-click a screen

SAP AG BC420 4-25


26/31


27/31

0.2

SAP AG 2001

1@'+cel

ther tools

+porting 2 importing BI sessions at operating system le'elsfor further processing with other tools

+ternal system

Exporting and Importing BI essions

*nder Utilities -> Export /import sessions (in $atch input monitor) session contents can $e importedand e"ported at the operating system le el

%urther processing would $e possi$le with an e"ternal software tool

SAP AG BC420 4-27


28/31

0.24

SAP AG 1999

Import or Export of Batch Input $b%ects

BC320 /ap5

%ti$itie" Import @ Export session

Export

$b%ectession

1ecording$b%ect name

Import

-ocation of the file to be imported or "ritten

9ile from application ser&er -ogical file nameor

@tmp@B(C?$BKEC ?1$BE1Physical file name

. . .

This BI session is to !ee+ported to thisdirectory under this filename

Import @ Export Program $ptions

!mport and e"port are e"ecuted on the application ser er using physical or logical file names, whichare set in &' Basis Customi ing (transaction %!82)

SAP AG BC420 4-28


29/31

0.26

SAP AG 1999

Explain the structure of batch input sessions

Process and analyse batch input sessions usingthe batch input monitor

Batch Input Processing: #nit ummary

ou are no" able to:

SAP AG BC420 4-29


30/31

ExercisesUnit: Batch Input Processing

Topic: Working with Batch Input essions

orking with the Batch !nput onitor

&unning of Batch !nput Sessions

#he $atch input session, which has $een created out of the D.- B, isrun with the $atch input monitor #his is how the legacy data are

transfered to the &' system

Processing a B! session with the B! monitor

< Copy the run B!-JJ of your proKect %!-JJ into the same proKect and su$proKect under runB!-JJ-C3P5

G Delete task SC-JJ (B! session processing)in the run B!-JJ-C3P5

Start the run and create B! sesssion B!-JJ-!6#

Process the B! session B!-JJ-!6#

-< !mport the B! session that you created $efore in the FDisplay all modeF in the &'systemhile the system is running the session, change one address field of a customer,e g change the place of residence#hen switch the processing mode to FDisplay errors onlyF

-G Analy e the log of the run and find out if errors occured Eas the change of thecustomer address $een recorded during the runL ::::::::::

- Analy e the session statistics

M Create more B! sessions, $y starting the run again and processsing them in differentmodes

SAP AG BC420 4-30


31/31

olutions

!hapter: Batch Input Processing

< Start the D.- B

!n the tree structure select run B!-JJ in your proKect %!-JJ

Choose Copy to copy the runSelect your proKect %!-JJ and su$proKect D2B!-JJ 4i e the run a new name/ B!-JJ-C3P5 Choose Continue to confirm the name

#he run has now $een copiedG Delete task S*B-HH Select this task in your run and choose !elete tas"

Select run B!-JJ-C3P5 and start it Create the B! session B!-JJ-!6#

!n a new session start the Batch !nput onitor (#A/S M)

-< Select your session B!-JJ-!6# Process the session with the processing mode #rocess in $ore%round

During the B! session change a customer location and switch to F3nly displayerrorsF/Choose &'ystem->'ervices->Batch (nput->)nly display errors& or enter thefunction code &/B!E& in the command field All su$se@uent customerss are

processed in the $ackground 5ou can see the result in the log

-G Choose $utton *o% to $ranch to the B! session log %ield changes are logged #hesession has the status FprocessedF after changes in foreground processing

- 4o to the statistics ($utton 'tatistics )

Documents

BC420_46C - 004Batch Input Processing