Reg : BDC

Former Member · ‎2008 Mar 05

Hi abapers,

Iam new to BDC.Wat are the steps to follow in BDC..? Plz help me

For Ex : Material Master Creation for different plants

Former Member · ‎2008 Mar 05

hi,

refer to the link.

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

you can refer to the following program

NO STANDARD PAGE HEADING LINE-SIZE 255.

PARAMETERS : p_file TYPE rlgrap-filename.

TYPES : BEGIN OF ty_mara,

matnr TYPE matnr,

maktx TYPE maktx,

meins TYPE meins,

END OF ty_mara.

TYPES : BEGIN OF ty_file,

file(200) TYPE c,

END OF ty_file.

TYPES : BEGIN OF ty_success,

text(250) TYPE c,

END OF ty_success.

TYPES : tt_file TYPE STANDARD TABLE OF ty_file,

tt_success TYPE STANDARD TABLE OF ty_success,

tt_mara TYPE STANDARD TABLE OF ty_mara.

DATA : it_file TYPE tt_file,

it_mara TYPE tt_mara,

wa_file TYPE ty_file,

it_success TYPE tt_success,

wa_success TYPE ty_success,

wa_mara TYPE ty_mara,

g_open TYPE c.

**********************************BDC DECLARATIONS******************

TYPES :tt_bdcdata TYPE STANDARD TABLE OF bdcdata, " table type for the bdcdata

tt_bdcmess TYPE STANDARD TABLE OF bdcmsgcoll. " table type for the BDC Messages

DATA : it_bdcdata TYPE tt_bdcdata,

it_bdcmess TYPE tt_bdcmess,

it_bdcmess1 TYPE tt_bdcmess,

wa_bdcdata TYPE bdcdata,

wa_bdcmess TYPE bdcmsgcoll,

wa_bdcmess1 TYPE bdcmsgcoll.

AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.

PERFORM get_f4 CHANGING p_file.

AT SELECTION-SCREEN.

IF P_FILE IS NOT INITIAL.

PERFORM validate_file USING p_file.

ELSE.

MESSAGE I001(0) WITH' Please enter file name'.

ENDIF.

START-OF-SELECTION.

PERFORM upload_file USING p_file.

*get the data from flatfile internal table to itab

PERFORM get_data USING it_file

CHANGING it_mara.

*PERFORM BDC_OPEN_SESSION.

PERFORM bdc_transaction.

*PERFORM BDC_INSERT.

PERFORM bdc_session.

END-OF-SELECTION.

PERFORM write_messages.

*INCLUDE bdcrecx1.

*

*START-OF-SELECTION.

*

PERFORM close_group.

&----

*& Form GET_F4

&----

text

----

-->P_P_FILE text

----

FORM get_f4 CHANGING pv_file TYPE rlgrap-filename.

DATA : l_file TYPE ibipparms-path.

CALL FUNCTION 'F4_FILENAME'

EXPORTING

program_name = syst-cprog

dynpro_number = syst-dynnr

FIELD_NAME = ' '

IMPORTING

file_name = l_file

.

pv_file = l_file.

ENDFORM. " GET_F4

&----

*& Form validate_file

&----

text

----

-->P_P_FILE text

----

FORM validate_file USING file TYPE c.

DATA: l_result TYPE c ,

l_file(128) TYPE c ,

lv_dir TYPE i,

l_dir TYPE c.

l_file = file .

CALL FUNCTION 'TMP_GUI_GET_FILE_EXIST'

EXPORTING

fname = file

IMPORTING

exist = l_result

isdir = l_dir

filesize = lv_dir

EXCEPTIONS

fileinfo_error = 1

OTHERS = 2.

IF sy-subrc <> 0.

MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno

WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

ENDIF.

IF l_result IS INITIAL.

MESSAGE e000(01) WITH ' file is not vaild'.

ENDIF.

ENDFORM. " validate_file

&----

*& Form upload_file

&----

text

----

-->P_P_FILE text

----

FORM upload_file USING g_file TYPE rlgrap-filename.

DATA : lv_file TYPE string.

lv_file = g_file.

CALL FUNCTION 'GUI_UPLOAD'

EXPORTING

filename = lv_file

filetype = 'ASC'

TABLES

data_tab = it_file.

IF sy-subrc <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

ENDFORM. " upload_file

&----

*& Form get_data

&----

text

----

-->P_IT_FILE text
<--P_IT_MARA text

----

FORM get_data USING l_file TYPE tt_file

CHANGING l_mara TYPE tt_mara.

DATA : lwa_file TYPE ty_file,

lwa_mara TYPE ty_mara.

LOOP AT l_file INTO lwa_file.

lwa_mara-maktx = lwa_file+0(40).

lwa_mara-meins = lwa_file+40(2).

APPEND lwa_mara TO it_mara.

ENDLOOP.

ENDFORM. " get_data

----

Start new screen *

----

FORM bdc_dynpro USING program dynpro.

CLEAR wa_bdcdata.

wa_bdcdata-program = program.

wa_bdcdata-dynpro = dynpro.

wa_bdcdata-dynbegin = 'X'.

APPEND wa_bdcdata TO it_bdcdata.

ENDFORM. "BDC_DYNPRO

----

Insert field *

----

FORM bdc_field USING fnam fval.

IF FVAL <> NODATA.

CLEAR wa_bdcdata.

wa_bdcdata-fnam = fnam.

wa_bdcdata-fval = fval.

APPEND wa_bdcdata TO it_bdcdata.

ENDIF.

ENDFORM. "BDC_FIELD

&----

*& Form GET_MESSAGES

&----

text

----

--> p1 text
<-- p2 text

----

FORM get_messages .

DATA: wa_x_bdcmess TYPE bdcmsgcoll. "Message

DATA : lwa_messages TYPE char480.

LOOP AT it_bdcmess INTO wa_bdcmess WHERE msgtyp = 'S'.

CALL FUNCTION 'FORMAT_MESSAGE'

EXPORTING

id = wa_bdcmess-msgid

lang = '-D'

no = wa_bdcmess-msgnr

v1 = wa_bdcmess-msgv1

v2 = wa_bdcmess-msgv2

v3 = wa_bdcmess-msgv3

v4 = wa_bdcmess-msgv4

IMPORTING

msg = lwa_messages

EXCEPTIONS

not_found = 1

OTHERS = 2.

IF sy-subrc <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

wa_success-text = lwa_messages.

APPEND wa_success TO it_success.

APPEND wa_bdcmess TO it_bdcmess1.

CLEAR wa_bdcmess.

ENDLOOP.

ENDFORM. " GET_MESSAGES

&----

*& Form BDC_TRANSACTION

&----

text

----

--> p1 text
<-- p2 text

----

FORM bdc_transaction .

LOOP AT it_mara INTO wa_mara.

PERFORM bdc_dynpro USING 'SAPLMGMM' '0060'.

PERFORM bdc_field USING 'BDC_CURSOR'

'RMMG1-MATNR'.

PERFORM bdc_field USING 'BDC_OKCODE'

'/00'.

PERFORM bdc_field USING 'RMMG1-MBRSH'

'C'.

PERFORM bdc_field USING 'RMMG1-MTART'

'VKHM'.

PERFORM bdc_dynpro USING 'SAPLMGMM' '0070'.

PERFORM bdc_field USING 'BDC_CURSOR'

'MSICHTAUSW-DYTXT(01)'.

PERFORM bdc_field USING 'BDC_OKCODE'

'=ENTR'.

PERFORM bdc_field USING 'MSICHTAUSW-KZSEL(01)'

'X'.

PERFORM bdc_dynpro USING 'SAPLMGMM' '4004'.

PERFORM bdc_field USING 'BDC_OKCODE'

'=BU'.

PERFORM bdc_field USING 'MAKT-MAKTX'

wa_mara-maktx . "'DESCRIPTIONS'.

PERFORM bdc_field USING 'BDC_CURSOR'

'MARA-MEINS'.

PERFORM bdc_field USING 'MARA-MEINS'

wa_mara-meins . "'BT'.

PERFORM bdc_field USING 'MARA-MTPOS_MARA'

'NORM'.

CALL TRANSACTION 'MM01' USING it_bdcdata

MODE 'N'

UPDATE 'S'

MESSAGES INTO it_bdcmess.

PERFORM get_messages.

*

REFRESH :it_bdcdata,

it_bdcmess.

CLEAR : wa_mara, wa_bdcdata, wa_bdcmess.

ENDLOOP.

ENDFORM. " BDC_TRANSACTION

&----

*& Form WRITE_MESSAGES

&----

text

----

--> p1 text
<-- p2 text

----

FORM write_messages .

LOOP AT it_success INTO wa_success.

WRITE : / wa_success-text.

ENDLOOP.

ENDFORM. " WRITE_MESSAGES

&----

*& Form BDC_SESSION

&----

text

----

--> p1 text
<-- p2 text

----

FORM bdc_session .

CALL FUNCTION 'BDC_CLOSE_GROUP'

EXCEPTIONS

not_open = 1

queue_error = 2

OTHERS = 3.

IF sy-subrc <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

ENDFORM. " BDC_SESSION

&----

*& Form BDC_OPEN_SESSION

&----

text

----

--> p1 text
<-- p2 text

----

FORM bdc_open_session .

DATA : w_group TYPE apqi-groupid.

CONCATENATE 'ZMM01' sy-datum sy-uzeit INTO w_group.

w_group = 'ZMM01_TEST'.

CALL FUNCTION 'BDC_OPEN_GROUP'

EXPORTING

client = sy-mandt

DEST = FILLER8

group = w_group

HOLDDATE = FILLER8
KEEP = FILLER1

user = sy-uname

RECORD = FILLER1
PROG = SY-CPROG
DCPFM = '%'
DATFM = '%'
IMPORTING
QID =
EXCEPTIONS
CLIENT_INVALID = 1
DESTINATION_INVALID = 2
GROUP_INVALID = 3
GROUP_IS_LOCKED = 4
HOLDDATE_INVALID = 5
INTERNAL_ERROR = 6
QUEUE_ERROR = 7
RUNNING = 8
SYSTEM_LOCK_ERROR = 9
USER_INVALID = 10
OTHERS = 11

.

IF sy-subrc <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ELSE.

g_open = 'X'.

ENDIF.

ENDFORM. " BDC_OPEN_SESSION

&----

*& Form BDC_INSERT

&----

text

----

--> p1 text
<-- p2 text

----

FORM bdc_insert .

IF g_open = 'X'.

CALL FUNCTION 'BDC_INSERT'

EXPORTING

tcode = 'MM01'

POST_LOCAL = NOVBLOCAL
PRINTING = NOPRINT

TABLES

dynprotab = it_bdcdata

EXCEPTIONS
INTERNAL_ERROR = 1
NOT_OPEN = 2
QUEUE_ERROR = 3
TCODE_INVALID = 4
PRINTING_INVALID = 5
POSTING_INVALID = 6
OTHERS = 7

.

IF sy-subrc <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

endform.

regards,

sreelakshmi

Former Member · ‎2008 Mar 05

hi,

Step by step procedure:

BDC RECORDING METHOD:

________________________

This is a predefined tool to create BDC code and screens for data migration. BDC Recording method allows the user to record the keystrokes done during data migration. This method can use only existing screens, i.e. predefined screens.

MM01 - Create Material

XD01 - Create Customer

XK01 - Create Vendor

VA01 - Create Sales Order

SHDB is the Transaction code to call Recording Method.

Navigations to use Recording Method:

-

SHDB -> Opens an interface -> Click on New Recordings pushbutton from appn. toolbar -> Specify Recording Name -> Specify Tcode (MM01) -> Click on Continue -> Opens MM01 Screen -> Specify Sample Data -> Click on Select View pushbutton from appn. toolbar -> Opens an interface -> Select First view (Basic Data 1) -> Click on Continue -> Opens another interface -> Specify short description for the material -> Specify units of measurement -> Save -> Opens an interface with defined field and their values -> Save -> Come back -> Select Recording Object -> Click on Program pushbutton from appn. toolbar to autogenerate the BDC source code -> Opens an interface -> Specify Program Name -> Select Transfer From Recording radiobutton -> Click on Source Code pushbutton -> Opens SE38 Editor with autogenerated code -> Specify following code after include statement:

include bdcrecx1.

DATA : BEGIN OF ITAB OCCURS 0,

STR(255),

END OF ITAB.

DATA ITAB1 LIKE MARA OCCURS 0 WITH HEADER LINE.

Specify following code after start-of-selection statement:

start-of-selection.

CALL FUNCTION 'UPLOAD'

EXPORTING

FILENAME = 'C:\COUP.TXT'

FILETYPE = 'ASC'

TABLES

DATA_TAB = ITAB.

LOOP AT ITAB.

SPLIT ITAB-STR AT ',' INTO ITAB1-MATNR ITAB1-MBRSH ITAB1-MTART

ITAB1-MEINS.

APPEND ITAB1.

ENDLOOP.

Specify Loop-Endloop statement for the bdc-dynpro, bdc-field and bdc_transaction statements as follows:

perform open_group.

LOOP AT ITAB1.

.

ENDLOOP

perform close_group.

-> Save -> Activate -> Execute -> Choose Call Transaction or Session method to process the datas.

The advantage of Recording Method is finally after executing the program, we can choose either Session method or Call Transaction method to upload the datas using predefind Tcode (MM01, MK01, VA01, XD01, XK01).

LEGACY SYSTEM MIGRATION WORKBENCH (LSMW):

-

This is also a BDC predefined tool for data migration. There are 14 steps followed to perform data upload using this tool. LSMW is the Tcode to perform data migration using this tool.

LSMW -> Create Project , Subproject, object -> Click on New Entry from appn. toolbar -> Enter short description for each -> Continue -> Execute -> Opens an interface with 20 steps initially (only 14 steps are used for data migration) -> Select first radiobutton.

1. Maintain Object Attributes : In this step, we create a recording object inside the tool to hold the sample datas along with field names. This is an important step.

Select first radiobutton -> Execute -> Opens an interface -> Select Batch Input Recording radiobutton -> Click on Goto Menu -> Recordings Overview -> Create New -> Specify Recording Object name -> Continue -> Specify Tcode (MM01) -> Opens MM01 initial screen -> Specify sample datas -> After creating sample datas, Click on Default All pushbutton from appn. toolbar -> Automatically enters Sample Datas with Field Names into the Recording object -> Save -> Come back -> Specify Recording object name -> Save -> Come back.

2. Maintain Source Structures : In this step, we specify the name of the internal table (source structure).

Select Second radiobutton -> Execute -> Click on Create Structure pushbutton from appn. toolbar -> Specify internal table name and short description -> Save -> Come back.

3. Maintain Source Fields : In this step, we specify fields for the internal table created.

Select Third radiobutton -> Execute -> Opens an interface -> Select internal table name -> Click on Create Fields pushbutton from appn. toolbar -> Specify field names for the sample datas created in MM01 screen -> Specify data length and type for each field -> Save -> Come back.

4. Maintain Structure Relations : In this step, we create a relationship between the source structure and recording object created earlier. The purpose is to reflect whatever values entered in the source structure inside recording object.

Select Fourth radiobutton -> Execute -> Save -> Come back.

5. Maintain Field Mapping and Conversion Rules -> In this step, we create a mapping between each field of source structure with the corresponding fields of recording object.

Select Fifth radiobutton -> Execute -> Select first recording object field -> Click on Source Field pushbutton from appn. toolbar -> Opens an interface -> Select corresponding field name -> Click on Continue -> Repeat the same step for all other fields -> Finally Save -> Come back.

6. Maintain Fixed Values, Translations, User-Defined Routines : This is an optional step in LSMW. There is no need for us to specify anything in this step. To change the value of field names in internal table dynamically in real time, this step is used.

Select Sixth radiobutton -> Execute -> Come back.

7. Specify Files : In this step, we define the path for the flat file.

Select Seventh Radiobutton -> Execute -> Select Legacy Data On the PC -> Click on Add Entry pushbutton from appn. toolbar -> Opens an interface -> Specify path of the flat file (C:\COUP.TXT) -> Enter short description for the flat file structure -> Specify the separator radiobutton -> Click on Continue -> Save -> Come back.

8. Assign Files : In this step, we assign the flat file records to the source structure created earlier.

Select Eigth Radiobutton -> Execute -> Save -> Come back.

9. Import Data : In this step, records from source structure are imported into recording object created earlier.

Select Ninth Radiobutton -> Execute -> Again Execute -> Displays the status as READ -> Come back -> Again Come back.

In this step, a file called "LSMWPROJ_LSMWSUBPROJ_SHABANA.lsmw.read" is generated which means the records from the source structure have been imported into Recording object.

10. Display Imported Data -> In this step, if we execute, the imported datas are displayed.

Select Tenth radiobutton -> Execute -> Again continue -> All the datas will be displayed in YELLOW color which specifies the datas have been imported into recording object -> Come back.

11. Convert Data : In this step, the imported datas are converted into LSMW recording object format.

Select Eleventh radiobutton -> Execute -> Again execute -> Displayes converted status -> Come back -> Again Come back.

In this step, a file called "LSMWPROJ_LSMWSUBPROJ_SHABANA.lsmw.conv" is generated which means the imported datas have been converted into LSMW format.

12. Display Converted Data : In this step, the converted datas are displayed in GREEN color.

Select Twelvth radiobutton -> Execute -> Continue -> Displays datas in GREEN color -> Come back.

13. Create Batch Input Session : In this step, to perform data migration, a session is created.

Select Thirteenth radiobutton -> Execute -> Select the Checkbox "Keep Batch Input Folder" -> Execute -> Displays a message as 'Batch input folder is created with number of transactions' -> Click on Continue.

14. Run Batch Input Session : In this step, we finally perform data migration using Session Method.

Select Radiobutton -> Execute -> Opens Session Method -> Select Session -> Execute.

In LSMW, the session created cannot be processed again unlike the recording method. Once we got the error session, we have to go and manually correct the transaction errors in the screen used (MM01).

Hope this helps u,

Regards,

Arunsri

Former Member · ‎2008 Mar 05

Hi,

Check This...

BDC or Batch Input Program Tips and Tricks

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.

Learning BDC Programming

I want to learn how to upload data using BDC. If I have a excel data file how will upload it using BDC. I don't know the full process of doing it, if someone help me in this. I want it using BDC session process and processing that session. I was trying to upload material master other day. But could not follow the process of uploading using BDC though I know LSMW. Please explain me the BDC process in details with examples.

For a BDC upload you need to write a program which created BDC sessions.

Steps:

1. Work out the transaction you would use to create the data manually.

2. Use transaction SHDB to record the creation of one material master data.

Click the New recording button or the Menu - Recording - Create

3. Save the recording, and then go back a screen and go to the overview.

4. Select the recording and click on Edit - Create Program. Give the program a Z name, and select transfer from recording.

5. Edit the program. You will see that all the data you entered is hard-coded into the program. You need to make the following changes:

5.1 After the start-of-selection, Call ws_upload to upload the file (the excel file needs to be saved as TAB separated).

5.2 After the open-group, Loop on the uploaded data. For each line, perform validation checks on the data, then modify the perform bdc_field commands to use the file data.

5.3. After perform bdc_transaction, add the endloop.

Execute the program. It will have options to create a batch session or to process directly.

These are all my finds . Might be it will be useful to you.

Direct call of transactions, session handling:

/nxxxx This terminates the current transaction, and starts transaction xxxx

/n This terminates the transaction. This generally corresponds to pressing F15 to go back.

/nend This termiantes all separate sessions and logs off (corresponds to System - Logoff).

/nex This terminates all separate sessions and logs off immediately (without any warning!).

/oxxxx This opens a new session and starts transaction xxxx in This session.

/o This lists existing sessions and allows deletion or opening of a new session.

/i This terminates the current session (corresponds to System End

/i1, /i2,... This terminates the session with the number given.

.xyzw Fast path: 'xyzw' refers to the underlined letters in the menus. This type of navigation is uncommon and is provided more for emergencies (such as a defective mouse).

Batch

The following commands can be entered in correction mode ('Process in foreground' or 'Display errors only') when processing a batch input session:

/n This terminates the current batch input transaction and characterizes it as

/bdel This deletes the current batch input transaction.

/bend This terminates batch input processing and sets the session to Failed

/bda This switches from Display errors only to Process in foreground

/bde This switches from Process in foreground to Display errors only

ABAP/4

/h This switches into debugging mode.

/hs This switches into debugging mode and activates the debugging of system functions.

Buffer

WARNING: Resetting buffers can significantly change the performance of the entire system for a long time.

It should therefore only be used where there is a good reason tdso. As of release 3.0B system administator authorization is required (authorization object (S_ADMI_FCD). The action is noted in the system log.

/$SYNC This resets all buffers of the application server

/$CUA This resets the CUA buffer of the application server

/$TAB This resets the TABLE buffers of the application server

/$NAM This resets the nametab buffer of the application server

/$DYNP This resets the screen buffer of the application server

and also see these following links.

For 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.sap-img.com/abap/learning-bdc-

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

Reward if helpful,

Gaurav J.

Former Member · ‎2008 Mar 05

Hi,

BATCH DATA COMMUNICATION

About Data Transfer In R/3 System

When a company decides to implement the SAP R/3 to manage business-critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.

In the process of replacing current applications and transferring application data, two situations might occur:

• The first is when application data to be replaced is transferred at once, and only once.

• The second situation is to transfer data periodically from external systems to SAP and vice versa.

• There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.

The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called “batch input” or “batch data communication”.

1. SESSION METHOD

2. CALL TRANSACTION

3. DIRECT INPUT

Advantages offered by BATCH INPUT method:

1. Can process large data volumes in batch.

2. Can be planned and submitted in the background.

3. No manual interaction is required when data is transferred.

4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.

To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a “data transfer” program must map the data from the external system into the data structure required by the SAP batch input program.

The batch input program must build all of the input to execute the SAP transaction.

Two main steps are required:

• To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.

• To pass the table to SAP for processing.

Prerequisite for Data Transfer Program

Writing a Data Transfer Program involves following prerequisites:

Analyzing data from local file

Analyzing transaction

Analyzing transaction involves following steps:

• The transaction code, if you do not already know it.

• Which fields require input i.e., mandatory.

• Which fields can you allow to default to standard values.

• The names, types, and lengths of the fields that are used by a transaction.

• Screen number and Name of module pool program behind a particular transaction.

To analyze a transaction::

• Start the transaction by menu or by entering the transaction code in the command box.

(You can determine the transaction name by choosing System – Status.)

• Step through the transaction, entering the data will be required for processing your batch input data.

• On each screen, note the program name and screen (dynpro) number.

(dynpro = dyn + pro. Dyn = screen, pro = number)

• Display these by choosing System – Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.

The technical info pop-up shows not only the field information but also the program and screen.

• For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.

Note the following information:

- The field name for batch input, which you’ll find in its own box.

- The length and data type of the field. You can display this information by double clicking on the Data Element field.

• Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).

Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.

In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.

You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.

Once you have program name, screen number, field name (screen field name), you can start writing.

DATA TRANSFER program.

Declaring internal table

First Integral Table similar to structure like local file.

Declaring internal table like BDCDATA

The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.

The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.

This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:

• Create a BDCDATA structure

• Write the structure out to a session or process it with CALL TRANSACTION USING; and then

• Create a BDCDATA structure for the next transaction that is to be processed.

Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.

The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:

• Data that is entered into screen fields.

• Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.

The BDCDATA structure contains the following fields:

• PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.

• DYNPRO: Screen Number. Set this field only in the first record for the screen.

• DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to ‘ ‘ (blank) for all other records.)

• FNAM: Field Name. The FNAM field is not case-sensitive.

• FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.

Transferring data from local file to internal table

Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.

Population of BDCDATA

For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.

All these five initial steps are necessary for any type of BDC interface.

DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.

First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.

SESSION METHOD

About Session method

In this method you transfer data from internal table to database table through sessions.

In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.

Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.

When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.

Unless session is processed, the data is not transferred to database table.

BDC_OPEN_GROUP

You create the session through program by BDC_OPEN_GROUP function.

Parameters to this function are:

• User Name: User name

• Group: Name of the session

• Lock Date: The date on which you want to process the session.

• Keep: This parameter is passed as ‘X’ when you want to retain session after

processing it or ‘ ‘ to delete it after processing.

BDC_INSERT

This function creates the session & data is transferred to Session.

Parameters to this function are:

• Tcode: Transaction Name

• Dynprotab: BDC Data

BDC_CLOSE_GROUP

This function closes the BDC Group. No Parameters.

Some additional information for session processing

When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.

However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.

If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.

CALL TRANSACTION

About CALL TRANSACTION

A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by

Call transaction <tcode> using <BDCTAB>

Mode <A/N/E>

Update <S/A>

Messages into <MSGTAB>.

Parameter – 1 is transaction code.

Parameter – 2 is name of BDCTAB table.

Parameter – 3 here you are specifying mode in which you execute transaction

A is all screen mode. All the screen of transaction are displayed.

N is no screen mode. No screen is displayed when you execute the transaction.

E is error screen. Only those screens are displayed wherein you have error record.

Parameter – 4 here you are specifying update type by which database table is updated.

S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.

A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).

Parameter – 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:

1. Tcode: Transaction code

2. Dyname: Batch point module name

3. Dynumb: Batch input Dyn number

4. Msgtyp: Batch input message type (A/E/W/I/S)

5. Msgspra: Batch input Lang, id of message

6. Msgid: Message id

7. MsgvN: Message variables (N = 1 - 4)

For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).

Steps for CALL TRANSACTION method

1. Internal table for the data (structure similar to your local file)

2. BDCTAB like BDCDATA

3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)

4. Loop at itab.

Populate BDCTAB table.

Call transaction <tcode> using <BDCTAB>

Mode <A/N/E>

Update <S/A>.

Refresh BDCTAB.

Endloop.

(To populate BDCTAB, You need to transfer each and every field)

The major differences between Session method and Call transaction are as follows:

SESSION METHOD CALL TRANSACTION

1. Data is not updated in database table unless Session is processed. Immediate updation in database table.

2. No sy-subrc is returned. Sy-subrc is returned.

3. Error log is created for error records. Errors need to be handled explicitly

4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.

Error Handling in CALL TRANSACTION

When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:

Steps for the error handling in CALL TRANSACTION

1. Internal table for the data (structure similar to your local file)

2. BDCTAB like BDCDATA

3. Internal table BDCMSG like BDCMSGCOLL

4. Internal table similar to Ist internal table

(Third and fourth steps are for error handling)

5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)

6. Loop at itab.

Populate BDCTAB table.

Call transaction <tr.code> using <Bdctab>

Mode <A/N/E>

Update <S/A>

Messages <BDCMSG>.

Perform check.

Refresh BDCTAB.

Endloop.

7 Form check.

IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).

Call function Format_message.

(This function is called to store the message given by system and to display it along with record)

Append itab2.

Display the record and message.

DIRECT INPUT

About Direct Input

In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.

You can start a Direct Input program in two ways;

Start the program directly

This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.

Starting the program via the DI administration transaction

This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).

Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.

First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:

- Create variant

- Define job

- Start job

- Restart job

Common batch input errors

- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.

- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.

- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.

- The BDCDATA structure contains fields, which are longer than the actual definition.

- Authorization problems.

RECORDING A BATCH INPUT

A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.

You can either use SHDB transaction for recording or

SYSTEM ? SERVICES ? BATCH INPUT ? EDIT

And from here click recording.

Enter name for the recording.

(Dates are optional)

Click recording.

Enter transaction code.

Enter.

Click Save button.

You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.

• Click Get Transaction.

• Return to BI.

• Click overview.

• Position the cursor on the just recorded entry and click generate program.

• Enter program name.

• Click enter

The program is generated for the particular transaction.

BACKGROUND PROCESSING

Need for Background processing

When a large volume of data is involved, usually all batch inputs are done in background.

The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.

Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.

There are several reasons to submit programs for background execution.

• The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.

• You can use the system while your program is executing.

This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.

The transaction for background processing is SM36.

Or

Tools ? Administration ? Jobs ? Define jobs

Or

System ? services ? Jobs

Components of the background jobs

A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.

• Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.

• Job class. Indicates the type of background processing priority assigned to the job.

The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.

• Job steps. Parameters to be passed for this screen are as follows:

Program name.

Variant if it is report program

Start criteria for the job: Option available for this are as follows:

Immediate - allows you to start a job immediately.

Date/Time - allows you to start a job at a specific name.

After job - you can start a job after a particular job.

After event - allows you to start a job after a particular event.

At operation mode - allows you to start a job when the system switches to a particular operation mode.

Defining Background jobs

It is two step process: Firstly, you define the job and then release it.

When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.

When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.

HANDLING OF POP UP SCREEN IN BDC

Many times in transaction pop up screen appears and for this screen you don’t pass any record but some indication to system telling it to proceed further. For example: The following screen

To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.

Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.

BDC_CURSOR is also used to place cursor on particular field.

AN EXAMPLE WITH SESSION METHOD

Following program demonstrates how data is passed from flat file to SAP transaction and further to database table by using SESSION method.

The transaction is TFBA (to change customer).

A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.

Prerequisite to write this BDC interface as indicated earlier is:

1. To find screen number

2. To find screen field names, type of the field and length of the field.

3. To find BDC_OKCODE for each screen

4. Create flat file.

Flat file can be created in your hard disk as follows:

1 Vinod Hyderabad

2 Kavitha Secunderabad

3 Kishore Hyderabad

(Where 1st character field is Customer number, 2nd field is Customer name and 3rd field is City.)

To transfer this data to database table SCUSTOM following interface can be used.

REPORT DEMO1.

Following internal table is to upload flat file.

DATA: BEGIN OF ITAB OCCURS 0,

ID(10),

NAME(25),

CITY(25),

END OF ITAB.

*Following internal table BDCDATA is to pass date from internal table to session.

DATA: BDCTAB LIKE BDCDATA OCCURS 0 WITH HEADER LINE.

Variables

DATA: DATE1 LIKE SY-DATUM. DATE1 = SY-DATUM - 1. “ This is for Hold Date

To upload flat file to internal table.

CALL FUNCTION UPLOAD

EXPORTING

FILE NAME = ‘C:FF.TXT’

FILE TYPE = ‘ASC”

TABLES

DATA_TAB = ITAB

EXCEPTIONS

CONVERSION_ERROR = 1

INVALID_TABLE_WIDTH = 2

INVALID_TYPE = 3

NO_BATCH = 4

UNKNOWN_ERROR = 5

OTHERS = 6.

If sy-subrc = 0.

Calling Function to Create a Session

CALL FUNCTION ‘BDC_OPEN_GROUP’

EXPORTING

CLIENT = SY-MANDT

GROUP = ‘POTHURI’

HOLDDATE = DATE1

KEEP = ‘X’

USER = SY-UNAME

EXCEPTIONS

CLIENT_INVALID = 1

DESTINATION_INVALID = 2

GROUP_INVALID = 3

GROUP_IS_LOCKED = 4

HOLDDATE_INVALID = 5

INTERNAL_ERROR = 6

QUEUE_ERROR = 7

RUNNING = 8

SYSTEM_LOCK_ERROR = 9

USER_INVALID = 10

OTHERS = 11.

If sy-subrc = 0.

*--

MAIN Logic--

LOOP AT ITAB

PERFORM GENERATE_DATA. “ Populating BDCDATA Table

CALL FUNCTION ‘BDC_INSERT’

EXPORTING

TCODE = ‘TFBA’

TABLES

DYNPROTAB = BDCTAB

EXCEPTIONS

INTERNAL_ERROR = 1

NOT_OPEN = 2

QUEUE_ERROR = 3

TCODE_INVALID = 4

PRINTING_INVALID = 5

POSTING_INVALID = 6

OTHERS = 7.

REFRESH BDCTAB

ENDLOOP.

Calling function to close the session

CALL FUNCTION ‘BDC_CLOSE_GROUP’

EXCEPTIONS

NOT_OPEN = 1

QUEUE_ERROR = 2

OTHERS = 3.

Endif.

&----

*& Form GENERATE_DATA

&----

Create BDC Data

&----

FORM GENERATE_DATA

Passing information for 1st screen on BDCDATA

BDCTAB-PROGRAM = ‘SAPMTFBA’.

BDCTAX-DYNPRO = 100.

BDCTAP-DYNBEGIN = ‘X’.

APPEND BCDTAB.CLEAR BDCTAB.

Passing field information to BDCDATA

BDCTAB-FNAM = ‘SCUSTOM-ID’

BDCTAB-FVAL = ITAB-ID.

APPEND BDCTAB.CLEAR BDCTAB.

Passing BDC_OKCODE to BDCDATA

BDCTAB-FNAM = ‘BDC_OKCODE’.

BDCTAB-FVAL = ‘/5’.

APPEND BDCTAB.CLEAR BDCTAB.

Passing screen information for next screen to BDCDATA

BDCTAB-PROGRAM = ‘SAPMTFBA’.

BDCTAB-DYNPRO = 200.

BDCTAB-DYNBEGIN = ‘X’.

APPEND BDCTAB.CLEAR BDCTAB.

Passing screen information to BDCDATA

BDCTAB-FNAM = ‘SCUSTOM-NAME’.

BDCTAB-FVAL = ITAB-NAME.

APPEND BDCTAB.CLEAR BDCTAB.

Passing screen information to BDCDATA

BDCTAB-FNAM = ‘SCUSTOM-CITY’.

BDCTAB-FVAL = ITAB-CITY.

APPEND BDCTAB.CLEAR BDCTAB.

Passing BDC_OKCODE to BDCDATA

BDCTAB-FNAM = ‘BDC_OKCODE’.

BDCTAB-FVAL = ‘SAVE’.

APPEND BDCTAB.CLEAR BDCTAB.

ENDFORM. “GENERATE_DATA

AN EXAMPLE WITH CALL TRANSACTION

Same steps to be repeated for CALL TRANSACTION

The only difference between the two types of interface is in Session method, you create session and store information about screen and data into session. When session is processed the data is transferred to database. While in CALL TRANSACTION, data is transferred directly to database table.

REPORT DEMO1.

Follow above Code till MAIN Logic. Even the Subroutine should be copied

LOOP AT ITAB

PERFORM GENERATE_DATA, “Populating BDCDATA Table

Call transaction ‘TFBA’ using BCDDATA Mode ‘A’ Update ‘S’.

REFRESH BDCTAB

ENDLOOP.

For 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

Check these link:

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

http://www.sap-img.com/abap/question-about-bdc-program.htm

http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/

http://www.planetsap.com/bdc_main_page.htm

Cheers,

vasavi.

Kindly rewrad if helpful.

Former Member · ‎2008 Mar 05

Hi,

BATCH DATA COMMUNICATIONS (BDC):

-

To perform data migration from legacy database to new SAP database, BDCs are used. There are three methods in BDC as follows:

1. DIRECT INPUT METHOD

2. CALL TRANSACTION METHOD

3. SESSION METHOD

There are predefined tools used to perform data migration in SAP. They are:

1. RECORDING METHOD (SHDB)

2. LEGACY SYSTEM MIGRATION WORKBENCH (LSMW)

FUNCTION MODULES USED IN BDC:

-

1. UPLOAD

2. BDC_OPEN_GROUP

3. BDC_INSERT

4. BDC_CLOSE_GROUP

DIRECT INPUT METHOD:

-

This method is used to perform bulk data transfer from the flat file into the database table.
During data transfer, no manual intervention is required.

Eg. code:

-

DATA : BEGIN OF ITAB OCCURS 0,

STR(65535),

END OF ITAB.

DATA IT_KNA1 LIKE KNA1 OCCURS 0 WITH HEADER LINE.

CALL FUNCTION 'UPLOAD'

EXPORTING

FILENAME = 'C:\KNA.TXT'

FILETYPE = 'ASC'

TABLES

DATA_TAB = ITAB.

LOOP AT ITAB.

SPLIT ITAB-STR AT ',' INTO IT_KNA1-KUNNR IT_KNA1-NAME1 IT_KNA1-ORT01

IT_KNA1-LAND1.

APPEND IT_KNA1.

ENDLOOP.

LOOP AT IT_KNA1.

INSERT INTO KNA1 VALUES IT_KNA1.

IF SY-SUBRC = 0.

WRITE 😕 'RECORDS ARE INSERTED'.

ELSE.

WRITE 😕 'RECORDS ALREADY EXISTS'.

ENDIF.

*WRITE 😕 IT_KNA1-KUNNR, IT_KNA1-NAME1, IT_KNA1-ORT01, IT_KNA1-LAND1.

ENDLOOP.

ERROR RECORDS:

-

Records already existing in the database table are called as Error Records. Such Error Records can be handled efficiently using CALL TRANSACTION statement.

ADVANTAGES OF DIRECT INPUT METHOD:

-

1. We can perform data migration for large number of records.

2. No manual intervention is required during data transfer.

3. Data migration is very fast using this method.

DISADVANTAGES:

-

1. Error Records cannot be modified during runtime.

CALL TRANSACTION METHOD:

-

The error records from the flat file can be handled using this method. Whenever SAP comes across error records, these are displayed in a user-defined screen.

CALL TRANSACTION <tcode> statement is used to call the user-defined screen to populate the error records.

DATA : BEGIN OF ITAB OCCURS 0,

STR(255),

END OF ITAB.

DATA ITAB1 LIKE KNA1 OCCURS 0 WITH HEADER LINE.

DATA ITAB2 LIKE BDCDATA OCCURS 0 WITH HEADER LINE.

DATA ITAB3 LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.

CALL FUNCTION 'UPLOAD'

EXPORTING

FILENAME = 'C:\KNA.TXT'

FILETYPE = 'ASC'

TABLES

DATA_TAB = ITAB.

LOOP AT ITAB.

SPLIT ITAB-STR AT ',' INTO ITAB1-KUNNR ITAB1-NAME1 ITAB1-ORT01

ITAB1-LAND1.

APPEND ITAB1.

ENDLOOP.

LOOP AT ITAB1.

INSERT INTO KNA1 VALUES ITAB1.

IF SY-SUBRC = 0.

WRITE 😕 'RECORDS ARE INSERTED'.

ELSE.

PERFORM PROGINFO USING 'SAPMZCALLTRANSACTION' '100'.

PERFORM FLDINFO USING 'WA-KUNNR' ITAB1-KUNNR.

PERFORM FLDINFO USING 'WA-NAME1' ITAB1-NAME1.

PERFORM FLDINFO USING 'WA-ORT01' ITAB1-ORT01.

PERFORM FLDINFO USING 'WA-LAND1' ITAB1-LAND1.

CALL TRANSACTION 'ZCALLTRANS' USING ITAB2 MODE 'N' MESSAGES INTO ITAB3.

ENDIF.

ENDLOOP.

LOOP AT ITAB3.

WRITE 😕 ITAB3.

ENDLOOP.

FORM PROGINFO USING PROGNAME SCRNUM.

CLEAR ITAB2.

REFRESH ITAB2.

ITAB2-PROGRAM = PROGNAME.

ITAB2-DYNPRO = SCRNUM.

ITAB2-DYNBEGIN = 'X'.

APPEND ITAB2.

ENDFORM.

FORM FLDINFO USING FLDNAME FLDVALUE.

CLEAR ITAB2.

ITAB2-FNAM = FLDNAME.

ITAB2-FVAL = FLDVALUE.

APPEND ITAB2.

ENDFORM.

3. BDC SESSION METHOD:

-

Function modules used in SESSION METHOD are:

1. BDC_OPEN_GROUP - This FM is used to create a session with flat file records in the Application Server. While creating session using this FM, we have to specify the CLIENT NUMBER, USERNAME and SESSION NAME.

2. BDC_INSERT - This FM is used to insert the internal table records into the session created in AS.

3. BDC_CLOSE_GROUP - This FM is used to save and activate the session to be processed later.

Eg. code to perform data migration using SESSION METHOD:

-

DATA : BEGIN OF ITAB OCCURS 0,

STR(255),

END OF ITAB.

DATA ITAB1 LIKE KNA1 OCCURS 0 WITH HEADER LINE.

DATA ITAB2 LIKE BDCDATA OCCURS 0 WITH HEADER LINE.

CALL FUNCTION 'UPLOAD'

EXPORTING

FILENAME = 'C:\KNA.TXT'

FILETYPE = 'ASC'

TABLES

DATA_TAB = ITAB.

LOOP AT ITAB.

SPLIT ITAB-STR AT ',' INTO ITAB1-KUNNR ITAB1-NAME1 ITAB1-ORT01

ITAB1-LAND1.

APPEND ITAB1.

ENDLOOP.

CALL FUNCTION 'BDC_OPEN_GROUP'

EXPORTING

CLIENT = SY-MANDT

GROUP = 'OURSESSION'

KEEP = 'X'

USER = SY-UNAME.

LOOP AT ITAB1.

PERFORM PROGINFO USING 'SAPMZCALLTRANSACTION' '100'.

PERFORM FLDINFO USING 'WA-KUNNR' ITAB1-KUNNR.

PERFORM FLDINFO USING 'WA-NAME1' ITAB1-NAME1.

PERFORM FLDINFO USING 'WA-ORT01' ITAB1-ORT01.

PERFORM FLDINFO USING 'WA-LAND1' ITAB1-LAND1.

CALL FUNCTION 'BDC_INSERT'

EXPORTING

TCODE = 'ZCALLTRANS'

TABLES

DYNPROTAB = ITAB2.

ENDLOOP.

CALL FUNCTION 'BDC_CLOSE_GROUP'.

FORM PROGINFO USING PROGNAME SCRNUM.

CLEAR ITAB2.

REFRESH ITAB2.

ITAB2-PROGRAM = PROGNAME.

ITAB2-DYNPRO = SCRNUM.

ITAB2-DYNBEGIN = 'X'.

APPEND ITAB2.

ENDFORM.

FORM FLDINFO USING FLDNAME FLDVALUE.

CLEAR ITAB2.

ITAB2-FNAM = FLDNAME.

ITAB2-FVAL = FLDVALUE.

APPEND ITAB2.

ENDFORM.

-> Save -> Activate -> Execute -> A session is created in the application server with specified name.

To Process the session, use SM35 tcode.

SM35 -> Opens Batch Input: Session Overview screen -> Select the session -> Click on Process pushbutton from appn. toolbar -> Opens an interface -> Select mode (A,E,N) -> Click on Process -> Opens specified screen if A or E is selected -> Perform batch input of records -> Finally opens a message -> to view the log, click on SESSION OVERVIEW pushbutton -> Opens SM35 interface -> Select processed session -> Click on LOG pushbutton from appn. toolbar -> Opens another interface specifying detailed analysis.

Function module used to upload flat file records from Excel sheet:

-

ALSM_EXCEL_TO_INTERNAL_TABLE

TOOLS USED IN BDC:

-

1. RECORDING METHOD (SHDB):

-

Predefined Screens:

-

MM01 - Create Material.

XD01 - Create Customer.

XK01 - Create Vendor.

BDC Recording method is a SAP tool used to perform data migration. Using this method, a recording object is created for any one of the above predefined screens. The sample values entered in the screen input fields are taken to create a BDCDATA structure. Based on the structure created, the source code is automatically generated by the system.

In this method, we cannot use user-defined screens to populate the error records.

NAVIGATIONS TO PERFORM DATA MIGRATION USING RECORDING METHOD:

-

SHDB -> Click on New Recording Pushbutton from appn. toolbar -> Opens an interface -> Name the Recording object -> Specify Transaction Code for which the recording is done (MM01) -> Continue -> Opens Specified SCreen (MM01) -> Enter Sample Values (Material number (MATNR), material type (MTART) and industry sector (MBRSH)) -> Click on Select View pushbutton from appn. toolbar -> Select BAsic DAta 1 from the interface -> Continue -> Opens second screen -> Enter Material Description (MAKTX) and Measurement (MEINS) -> Click on Save -> Opens another interface with BDCDATA structure filled with sample values -> Save the Recording -> Come back -> Select the Recording object -> Click on Program pushbutton from appn. toolbar -> Opens an interface -> Enter Program NAme -> Select TRANSFER FROM RECORDING radiobutton -> Continue -> Enter short description -> Click on SOURCE CODE pushbutton -> Opens SE38 editor with autogenerated code.

After the INCLUDE statement, specify following code:

include bdcrecx1.

DATA : BEGIN OF ITAB OCCURS 0,

STR(255),

END OF ITAB.

DATA ITAB1 LIKE MARA OCCURS 0 WITH HEADER LINE.

After the START-OF-SELECTION event, specify following code:

start-of-selection.

CALL FUNCTION 'UPLOAD'

EXPORTING

FILENAME = 'C:\MARA.TXT'

FILETYPE = 'ASC'

TABLES

DATA_TAB = ITAB.

LOOP AT ITAB.

SPLIT ITAB-STR AT ',' INTO ITAB1-MATNR ITAB1-MTART ITAB1-MBRSH

ITAB1-MEINS.

APPEND ITAB1.

ENDLOOP.

Specify LOOP AT ITAB1-ENDLOOP statement as follows:

perform open_group.

LOOP AT ITAB1.

**Replace all the sample values for the fields with internal table name.*

ITAB1-MATNR

ITAB1-MTART

ITAB1-MBRSH

ITAB1-MEINS

ENDLOOP.

perform close_group.

-> Save -> Activate -> Execute.

Using REcording method, we can perform data migration in the following two ways:

1. Session method.

2. Call transaction method.

When Session Method is selected, SPECIFY SESSION NAME -> Check KEEP BATCH INPUT SESSION CHECKBOX -> Execute.

To Process the session, goto SM35 Tcode.

Regards,

priya.

By Category

Related Content

Activity Groups

Industry Groups

Influence and Feedback Groups

Interest Groups

Location Groups

Customer Only Groups

Forums

Related Resources

Products

Learning and Support

About

My SAP Profile

My SAP Profile

Reg : BDC