BDC

[Former Member]

What is BDC?

when we create a flat file ie. in notepad.

how is the data transfered ?

I want a clear explanation about the 7th step in BDC .

please do help me .

[Former Member]

<b>What is BDC?</b>

Batch Data Communication or BDC is a batch interfacing technique that SAP developed. It is mainly used for uploading data into the SAP R/3 system. BDC works by simulating the user input from transactional screen via an ABAP program.

The data input data file will come in the form of a flat file which the user save as file type txt file or prn file from the Microsoft Excel program. An Abaper will create a program to read the text file and upload into the SAP system.

Normally, the tcode SHDB will be used to record the transaction code the user used. After, the simulation, the Abaper can generate a sample program and modify from there. It makes the programming easier and faster.

<b>when we create a flat file ie. in notepad</b>.

We create a flat file so that bulk data can be uploaded inti SAP without manual interventin. So all the data from application gets stored in the flat file, and then we read the flat file through BDC to upload data.

<b>how is the data transfered ?</b>

Data is transferred through upload and download FM from your desktop into an internal table defined in the program, and then from that internal table to SAP.

<b>Hope this is helpful, Do reward</b>

[Former Member]

Hi Babu,

<b>Batch Data Communication: Batch Input</b>

Batch input is typically used to transfer data from non-R/3 systems to R/3 systems or to transfer data between R/3 systems.

It is a data transfer technique that allows you to transfer datasets automatically to screens belonging to transactions, and thus to an SAP system. Batch input is controlled by a batch input session.

In simple 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.

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.

Types of BDC :

CLASSICAL BATCH INPUT (Session Method)

CALL TRANSACTION

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.

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.

<b>Batch input session</b>

Groups a series of transaction calls together with input data and user actions . A batch input session can be used to execute a dialog transaction in batch input, where some or all the screens are processed by the session. Batch input sessions are stored in the database as database tables and can be used within a program as internal tables when accessing transactions.

<b>BAPI</b>

BAPIs are standardized programming interfaces (methods) enabling external applications to access business processes and data in the R/3 System.

BAPIs provide stable and standardized methods to achieve seamless integration between the R/3 System and external applications, legacy systems and add-ons.

BAPIs are defined in the BOR(Business object repository) as methods of SAP business object types that carry out specific business functions.

BAPIs are implemented as RFC-enabled function modules and are created in the Function Builder of the ABAP Workbench.

<b>Remote Function Call:</b>

RFC is an SAP interface protocol. Based on CPI-C, it considerably simplifies the programming of communication processes between systems.

RFCs enable you to call and execute predefined functions in a remote system - or even in the same system.

RFCs manage the communication process, parameter transfer and error handling.

<b>BDC and LSMW</b> are the two data migration techniques (from legacy to SAP) . BDC technique is usually done by ABAPers. It consists of three methods.

1) Call Dialog Method

2) Session Method

3) Call Transaction Method

In the case of Session Method , a BDC Session is created , which has the data and info to run it in batch mode. When the user runs this session, every transactions are run in batch mode and tables are updated.

WHile in call transaction, no session is created. Instead , a report prog is created , which takes input from the file and calls the transaction in Batch mode.

Call dialog method is similar to call transaction, except that updation is done by the calling program itself.This method is obsolete.

Advantages of Batch Input Method are

1)Can process large data volumes

2) data integrity is maintained

Just check these links.

LSMW and BDC are vastly different.

BDC (Batch Data Communication) is a technology used for data transfer. it is meant for transferring data thru SAP transactions itself. when u use BDC for data transfer, the sequence of steps is the same as when u use standard sap transaction screens for data upload. the only difference is that u can use different options for foreground/backgrou nd processing.

LSMW on the other hand is a tool that helps migrate data from a legacy system (non-sap system ) to SAP system. it offers u various options to use either batch input, direct input, BAPIs or idocs. it involves a series of some 17-18 steps to migrate data.

LSMW:

The LSM Workbench is an R/3-based tool that supports You when transferring data from non-SAP systems ("Legacy Systems") to R/3 once or periodically.

The tool supports conversion of data of the legacy system in a convenient way. The data can then be imported into the R/3 system via batch input, direct input, BAPIs or IDocs.

Furthermore, the LSM Workbench provides a recording function that allows to generate a "data migration object" in an entry or change transaction.

The main advantages of the LSM Workbench:

• Part of R/3 and thus independent of individual platforms

• A variety of technical possibilities of data conversion:

• Data consistency due to standard import techniques:

Batch input

Direct input

BAPIs (Business Application Programming Interfaces)

IDocs (Intermediate Documents)

The import technique to be used in an individual case depends on the business object.

• Generation of the conversion program on the basis of defined rules

• Clear interactive process guide

• Interface for data in spreadsheet format

• Creation of data migration objects on the basis of recorded transactions

• Charge-free for SAP customers and SAP partners

BDC

http://myweb.dal.ca/hchinni/sap/bdc_home.htm

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&;

http://www.sap-img.com/abap/learning-bdc-programming.htm

http://www.sapdevelopment.co.uk/bdc/bdchome.htm

http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm

http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm

http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html

LSMW

http://help.sap.com/saphelp_nw04s/helpdata/en/87/f3ae74e68111d1b3ff006094b944c8/content.htm

http://www.sap-img.com/sap-data-migration.htm

http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc

http://allsaplinks.com/lsmw.html

http://myweb.dal.ca/hchinni/sap/lsmw_home.htm

<b>Reward Points if Useful</b>

Regards

Gokul

[Former Member]

Hi

BDC stand for BATCH DATA COMMUNICATION

Through this concept we transfer the data into SAP R/3 System

Legacy System -

---

> R/3 System

Batch input is used to transfer large amounts of data into the

SAP system. In this topic, we will learn the basics of batch input.

There are 2 types of transfers Conversions and interfaces.

Conversions: This type of transfer refers to a one-time transfer from a legacy system to the SAP system. In this case, the “legacy” system is the old system that is being replaced by the SAP system.

Interfaces: This type of transfer refers to an ongoing transfer from a complementary system to the SAP system. In this case, the “complementary” system is a system that will run along side the SAP system.

<b>Use</b>

This is used for uploading the master data and different type of application data from legacy system to SAP R/3 system like as:-

Create Vendor using transaction (“FK01”),

Change Vendor using transaction (“FK02”)

<b>Reading data from application server or presentation server </b>

Presentation -

---

WS_UPLOAD

server 1

-- ABAP/4 PROGRAM

1

Application -

---

Read Dataset

server

<b>Dialog Program </b>

A dialog program conducts a dialog with the user. As a result of user input the program executes which in turn displays an output or changes the database in a consistent way.

A transaction code can be connected to dialog program which calls the corresponding program

<b>Procedural steps in data migration</b>

Data analysis

Generate SAP structure

Develop trasfer program

Create sequential file

Creat batch input Program

Process btach input data

Analyse results

The flat file will be created any time

before executing the BDC program

the will be trasferd based on the DAILOG PROGRAMING EXPLAINED above

<b>Reward if useful</b>