0% found this document useful (0 votes)
51 views

Data Transfer Techniques

Batch Data Communication (BDC) is a process that transfers large amounts of data between SAP systems or from non-SAP systems to SAP systems. BDC uses normal transaction codes to transfer data asynchronously in batches. There are two main types of BDC - classical batch input, which processes transactions sequentially without database updates until all are complete, and call transaction, which processes each transaction immediately with database updates.

Uploaded by

PRASHANT KUMAR
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
51 views

Data Transfer Techniques

Batch Data Communication (BDC) is a process that transfers large amounts of data between SAP systems or from non-SAP systems to SAP systems. BDC uses normal transaction codes to transfer data asynchronously in batches. There are two main types of BDC - classical batch input, which processes transactions sequentially without database updates until all are complete, and call transaction, which processes each transaction immediately with database updates.

Uploaded by

PRASHANT KUMAR
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 33

DATA TRANSFER TECHNIQUES

BATCH DATA COMMUNICATION

02-Sep-09
Data Transfer Techniques

 External Files
 Batch Data Communication
 RFC
 BAPI
 LSMW
 Direct Input

02-Sep-09 2
Batch Data Communication

(Sequential)
Flat File
for
Data Transfer

Conversion
SAP Data Transfer

Legacy System(s) R/3 System

02-Sep-09 3
Objective

 Batch Data Communication

 Types of BDC and differences between them

02-Sep-09 4
Definition

Batch Data Communication (BDC) is the process of


transferring data from one SAP System to another SAP system or
from a non-SAP system to SAP System.

02-Sep-09 5
Features

 BDC is an automatic procedure.

 This method is used to transfer large amount of data that is


available in electronic medium.

 BDC can be used primarily when installing the SAP system and
when transferring data from a legacy system (external system).

 BDC uses normal transaction codes to transfer data.

02-Sep-09 6
Types of BDC

 Classical Batch Input (Session Method)

 Call Transaction

02-Sep-09 7
Batch Input method

 This method is also called as ‘CLASSICAL METHOD’.

Features:
 Asynchronous processing.
 Synchronous Processing in database update.
 Transfer data for more than one transaction.
 Batch input processing log will be generated.
 During processing, no transaction is started until the previous
transaction has been written to the database.

02-Sep-09 8
Batch Input method

Batch Input Processing

Sequential
file

Batch
Batch input
input program
program

Queue file

Batch
Batch input
input function
function

SAP
SAP R/3
R/3

Flight
Customer connections Reservation
data data

02-Sep-09 9
Steps Involved in Classical Batch Input

 Analyze the data that is to be transferred to the SAP system to


determine how the existing data should be mapped to the SAP
data structure.
 Generate SAP data structures for incorporation into the data
export program (SAP provides one method called Recording to
generate the SAP data structure and transaction code for this is
SHDB).
 Read data in, often from a sequential file that has been exported
from another system or prepared by a data transfer program.

02-Sep-09 10
Steps Involved in Classical Batch Input

 Perform data conversions, if necessary.


 Prepare the data for batch input processing by storing the data in
the batch input data structure, BDCDATA.
 Generate a batch input session using the function modules
BDC_OPEN_GROUP, BDC_INSERT and
BDC_CLOSE_GROUP (the parameters to these function modules
explained in the next slide).
 Process the session from System  Services  Batch Input
(Transaction code is SM35 ).

02-Sep-09 11
Session Methodology

Function Modules & Parameters for Session Method

BDC_OPEN_GROUP
BDC_OPEN_GROUP
Client
Client CLIENT
CLIENT
Session
Sessionname
name GROUP
GROUP
Lock
Lock date
date HOLD
HOLD
Delete
Delete session
sessionafter
after KEEP
KEEP
processing
processing
BDC
BDCuser
user name
name USER
USER

BDC_INSERT
BDC_INSERT
Transaction
Transaction code
code TCODE
TCODE
BDC
BDC table
table DYNPROTAB
DYNPROTAB

BDC_CLOSE_GROUP
BDC_CLOSE_GROUP

02-Sep-09 12
Structure of BDC Data

BDC Table
Program
Program Screen
Screen Start
Start Field
Field name
name Field
Fieldcontents
contents

<program
<program name>
name> <number
<number1>
1> xx
<field
<field 11>
11> <value
<value11>
11>
<field
<field 12>
12> <value
<value12>
12>
...
... ...
...
<program
<program name>
name> <number
<number2>
2> xx
<field
<field 21>
21> <value
<value21>
21>
<field
<field 22>
22> <value
<value22>
22>
...
... ...
...
...
... ...
...

02-Sep-09 13
Recording(Transaction code SHDB)

 Recording is a process that is provided by the SAP system to


generate the SAP data structure for batch data communication.

 A sample recording for the transaction XK01 is explained below.

02-Sep-09 14
Recording Steps
Recording Step 1:
Starting screen of the recording (Transaction code SHDB)
Click “New Recording” button to new recording.

02-Sep-09 15
Recording Steps
Recording Step 2 : Enter the recording name and the transaction for
which you want the recording and click “Start Recording” Button.

02-Sep-09 16
Recording Steps
Recording Step 3 : Enter sample data for the transaction.
Every key stroke will be recorded.

02-Sep-09 17
Recording Steps
Recording Step 4 : After entering all data for the transaction (here XK01),
the recording overview screen will be displayed. Then save the recording.
And click the “Program” button.

02-Sep-09 18
Recording Steps
Recording Step 5 : Enter the program name.

02-Sep-09 19
Recording Steps

02-Sep-09 20
Vendor Creation

First screen of the transaction XK01(Vendor Creation)

02-Sep-09 21
Vendor Creation

02-Sep-09 22
Vendor Creation

02-Sep-09 23
Vendor Creation

02-Sep-09 24
Background processing

 RSBDCSUB
 In SM35 we can only process one session at a time.
 By calling RSBDCSUB ,we can process multiple Session at a time
in Background.

02-Sep-09 25
Call Transaction Method

This is another method to transfer data from the legacy system.

Features:
 Synchronous processing : The system performs a database
commit immediately before and after the CALL
TRANSACTION USING statement.
 Updating the database can be either synchronous or
asynchronous. The program specifies the update type.
 Transfer data for a single transaction.
 Transfers data for a sequence of dialog screens.
 No batch input processing log is generated.

02-Sep-09 26
Error Tracking in Call Transaction

 By looping the internal table of BDCMSGCOLL we can track


the Errors and also what actually happened at end of the
transaction.

 This table has Type, Message ID, Messages

02-Sep-09 27
Conversion Routine

Some Conversion routines are to be done during data Upload.

Ex : Materialnumber (Preceeds Zero’s)

1. CONVERSION_EXIT_ALPHA_INPUT
2. CONVERSION_EXIT_ALPHA_OUTPUT

02-Sep-09 28
Common Validation

 Date format and Decimal notation should be validated according to


the System Default User setting.
Table : USR01.

 All Keyfields should be validated.

02-Sep-09 29
Real-time Scenarios
 Material Master Conversion –MM01

 Purchase Order-ME21

 Sales order-VA01

 Source List-ME01

 Customer master-XD01

 Condition Records –Pricing-VK11

 Vendor Master-XK11

 Asset creation-AS91

 Accounts Receivable-FB01

 Goods movement-MB11

02-Sep-09 30
Exercise for Practice

 Material Master Conversion in BDC


(Both in Call Transaction and BatchInput)
 Upload Data for 2 views,(Fill Only Mandatory Fields)
1.Basic Data View 1
2.Basic data View 2.
Validations :
− Avoid Duplicate entries of Material.
− Conversion routine for material.

02-Sep-09 31
Exercise for Practice

Report :
1. Error Record Should be Downloaded to Application server.
2. Number of legacy Records,
Number of Success Records,
Number of Failure Records.
Tables : Mara.
Fields : Matnr,Mbrsh,Maktx,Mtart,Meins,Matkl

02-Sep-09 32
THANK YOU

02-Sep-09 33

You might also like