topic Re: give a simple BDC example for CALL TRANSACTION METHOD.. in Application Development and Automation Discussions

give a simple BDC example for CALL TRANSACTION METHOD..

Former Member — Mon, 15 Oct 2007 08:10:27 GMT

GIVE AN EXAMPLE

Re: give a simple BDC example for CALL TRANSACTION METHOD..

Former Member — Mon, 15 Oct 2007 08:12:55 GMT

*Code used to create BDC

&----

*& Report ZBDC_EXAMPLE *

*& *

&----

*& Example BDC program, which updates net price of item 00010 of a *

*& particular Purchase order(EBELN). *

*& *

&----

REPORT ZBDC_EXAMPLE NO STANDARD PAGE HEADING

LINE-SIZE 132.

*----

Data declaration

TABLES: ekko, ekpo.

TYPES: BEGIN OF t_ekko,

ebeln TYPE ekko-ebeln,

waers TYPE ekko-waers,

netpr TYPE ekpo-netpr,

err_msg(73) TYPE c,

END OF t_ekko.

DATA: it_ekko TYPE STANDARD TABLE OF t_ekko INITIAL SIZE 0,

wa_ekko TYPE t_ekko,

it_error TYPE STANDARD TABLE OF t_ekko INITIAL SIZE 0,

wa_error TYPE t_ekko,

it_success TYPE STANDARD TABLE OF t_ekko INITIAL SIZE 0,

wa_success TYPE t_ekko.

DATA: w_textout LIKE t100-text.

DATA: gd_update TYPE i,

gd_lines TYPE i.

*Used to store BDC data

DATA: BEGIN OF bdc_tab OCCURS 0.

INCLUDE STRUCTURE bdcdata.

DATA: END OF bdc_tab.

*Used to stores error information from CALL TRANSACTION Function Module

DATA: BEGIN OF messtab OCCURS 0.

INCLUDE STRUCTURE bdcmsgcoll.

DATA: END OF messtab.

*----

*Screen declaration

SELECTION-SCREEN BEGIN OF BLOCK block1 WITH FRAME

TITLE text-001. "Purchase order Num

SELECT-OPTIONS: so_ebeln FOR ekko-ebeln OBLIGATORY.

SELECTION-SCREEN END OF BLOCK block1.

SELECTION-SCREEN BEGIN OF BLOCK block2 WITH FRAME

TITLE text-002. "New NETPR value

PARAMETERS: p_newpr(14) TYPE c obligatory. "LIKE ekpo-netpr.

SELECTION-SCREEN END OF BLOCK block2.

************************************************************************

*START-OF-SELECTION

START-OF-SELECTION.

Retrieve data from Purchase order table(EKKO)

SELECT ekko_{ebeln ekko}waers ekpo~netpr

INTO TABLE it_ekko

FROM ekko AS ekko INNER JOIN ekpo AS ekpo

ON ekpo_{ebeln EQ ekko}ebeln

WHERE ekko~ebeln IN so_ebeln AND

ekpo~ebelp EQ '10'.

************************************************************************

*END-OF-SELECTION

END-OF-SELECTION.

Check data has been retrieved ready for processing

DESCRIBE TABLE it_ekko LINES gd_lines.

IF gd_lines LE 0.

Display message if no data has been retrieved

MESSAGE i003(zp) WITH 'No Records Found'(001).

LEAVE TO SCREEN 0.

ELSE.

Update Customer master data (instalment text)

LOOP AT it_ekko INTO wa_ekko.

PERFORM bdc_update.

ENDLOOP.

Display message confirming number of records updated

IF gd_update GT 1.

MESSAGE i003(zp) WITH gd_update 'Records updated'(002).

ELSE.

MESSAGE i003(zp) WITH gd_update 'Record updated'(003).

ENDIF.

Display Success Report
**********************
Check Success table

DESCRIBE TABLE it_success LINES gd_lines.

IF gd_lines GT 0.

Display result report column headings

PERFORM display_column_headings.

Display result report

PERFORM display_report.

ENDIF.

Display Error Report
********************
Check errors table

DESCRIBE TABLE it_error LINES gd_lines.

If errors exist then display errors report

IF gd_lines GT 0.

Display errors report

PERFORM display_error_headings.

PERFORM display_error_report.

ENDIF.

&----

*& Form DISPLAY_COLUMN_HEADINGS

&----

Display column headings

----

FORM display_column_headings.

WRITE:2 ' Success Report '(014) COLOR COL_POSITIVE.

SKIP.

WRITE:2 'The following records updated successfully:'(013).

WRITE:/ sy-uline(42).

FORMAT COLOR COL_HEADING.

WRITE:/ sy-vline,

(10) 'Purchase Order'(004), sy-vline,

(11) 'Old Netpr'(005), sy-vline,

(11) 'New Netpr'(006), sy-vline.

WRITE:/ sy-uline(42).

ENDFORM. " DISPLAY_COLUMN_HEADINGS

&----

*& Form BDC_UPDATE

&----

Populate BDC table and call transaction ME22

----

FORM bdc_update.

PERFORM dynpro USING:

'X' 'SAPMM06E' '0105',

' ' 'BDC_CURSOR' 'RM06E-BSTNR',

' ' 'RM06E-BSTNR' wa_ekko-ebeln,

' ' 'BDC_OKCODE' '/00', "OK code

'X' 'SAPMM06E' '0120',

' ' 'BDC_CURSOR' 'EKPO-NETPR(01)',

' ' 'EKPO-NETPR(01)' p_newpr,

' ' 'BDC_OKCODE' '=BU'. "OK code

Call transaction to update customer instalment text

CALL TRANSACTION 'ME22' USING bdc_tab MODE 'N' UPDATE 'S'

MESSAGES INTO messtab.

Check if update was succesful

IF sy-subrc EQ 0.

ADD 1 TO gd_update.

APPEND wa_ekko TO it_success.

ELSE.

Retrieve error messages displayed during BDC update

LOOP AT messtab WHERE msgtyp = 'E'.

Builds actual message based on info returned from Call transaction

CALL FUNCTION 'MESSAGE_TEXT_BUILD'

EXPORTING

msgid = messtab-msgid

msgnr = messtab-msgnr

msgv1 = messtab-msgv1

msgv2 = messtab-msgv2

msgv3 = messtab-msgv3

msgv4 = messtab-msgv4

IMPORTING

message_text_output = w_textout.

ENDLOOP.

Build error table ready for output

wa_error = wa_ekko.

wa_error-err_msg = w_textout.

APPEND wa_error TO it_error.

CLEAR: wa_error.

ENDIF.

Clear bdc date table

CLEAR: bdc_tab.

REFRESH: bdc_tab.

ENDFORM. " BDC_UPDATE

----

FORM DYNPRO *

----

stores values to bdc table *

----

--> DYNBEGIN *
--> NAME *
--> VALUE *

----

FORM dynpro USING dynbegin name value.

IF dynbegin = 'X'.

CLEAR bdc_tab.

MOVE: name TO bdc_tab-program,

value TO bdc_tab-dynpro,

'X' TO bdc_tab-dynbegin.

APPEND bdc_tab.

ELSE.

CLEAR bdc_tab.

MOVE: name TO bdc_tab-fnam,

value TO bdc_tab-fval.

APPEND bdc_tab.

ENDIF.

ENDFORM. " DYNPRO

&----

*& Form DISPLAY_REPORT

&----

Display Report

----

FORM display_report.

FORMAT COLOR COL_NORMAL.

Loop at data table

LOOP AT it_success INTO wa_success.

WRITE:/ sy-vline,

(10) wa_success-ebeln, sy-vline,

(11) wa_success-netpr CURRENCY wa_success-waers, sy-vline,

(11) p_newpr, sy-vline.

CLEAR: wa_success.

ENDLOOP.

WRITE:/ sy-uline(42).

REFRESH: it_success.

FORMAT COLOR COL_BACKGROUND.

ENDFORM. " DISPLAY_REPORT

&----

*& Form DISPLAY_ERROR_REPORT

&----

Display error report data

----

FORM display_error_report.

LOOP AT it_error INTO wa_error.

WRITE:/ sy-vline,

(10) wa_error-ebeln, sy-vline,

(11) wa_error-netpr CURRENCY wa_error-waers, sy-vline,

(73) wa_error-err_msg, sy-vline.

ENDLOOP.

WRITE:/ sy-uline(104).

REFRESH: it_error.

ENDFORM. " DISPLAY_ERROR_REPORT

&----

*& Form DISPLAY_ERROR_HEADINGS

&----

Display error report headings

----

FORM display_error_headings.

SKIP.

WRITE:2 ' Error Report '(007) COLOR COL_NEGATIVE.

SKIP.

WRITE:2 'The following records failed during update:'(008).

WRITE:/ sy-uline(104).

FORMAT COLOR COL_HEADING.

WRITE:/ sy-vline,

(10) 'Purchase Order'(009), sy-vline,

(11) 'Netpr'(010), sy-vline,

(73) 'Error Message'(012), sy-vline.

WRITE:/ sy-uline(104).

FORMAT COLOR COL_NORMAL.

ENDFORM. " DISPLAY_ERROR_HEADINGS

Please reward points,

Thank you,

Gangula Vikram.

Re: give a simple BDC example for CALL TRANSACTION METHOD..

Former Member — Mon, 15 Oct 2007 08:14:30 GMT

Hi Balaji,

Here it is..

form call_md61.

loop at imain into imain_wa.

*MD74 BDCData Preparation

refresh bdcdata.

perform bdc_dynpro using 'RM60RR20' '1000'.

perform bdc_field using 'WERKS-LOW'

imain_wa-werks.

perform bdc_field using 'MATNR-LOW'

imain_wa-matnr.

perform bdc_field using 'DATE1'

ws-dateto.

perform bdc_field using 'HISTFLAG'

' '.

perform bdc_field using 'INACFLAG'

' '.

perform bdc_field using 'TESTFLAG'

' '.

perform bdc_field using 'LISTFLAG'

' '.

perform bdc_field using 'BDC_OKCODE'

'=ONLI'.

call transaction 'MD74' using bdcdata mode 'E'.

refresh bdcdata.

perform bdc_dynpro using 'SAPMM60X' '0100'.

perform bdc_field using 'AM60X-MATNR'

imain_wa-matnr.

perform bdc_field using 'AM60X-WERKS'

imain_wa-werks.

perform bdc_field using 'RM60X-VERSB'

'00'.

perform bdc_field using 'RM60X-DATVE'

ws-datefrom.

perform bdc_field using 'RM60X-DATBE'

ws-dateto.

perform bdc_field using 'RM60X-ENTLU'

'M'.

perform bdc_field using 'BDC_OKCODE'

'/00'.

perform bdc_dynpro using 'SAPLM60E' '0200'.

perform bdc_field using 'RM60X-PLN01(01)'

imain_wa-qty01.

perform bdc_field using 'RM60X-PLN02(01)'

imain_wa-qty02.

perform bdc_field using 'RM60X-PLN03(01)'

imain_wa-qty03.

perform bdc_field using 'RM60X-PLN04(01)'

imain_wa-qty04.

perform bdc_field using 'RM60X-PLN05(01)'

imain_wa-qty05.

perform bdc_field using 'RM60X-PLN06(01)'

imain_wa-qty06.

perform bdc_field using 'BDC_OKCODE'

'=SICH'.

call transaction 'MD61' using bdcdata mode 'E'.

endloop.

endform.

*----

To add Screen Data

*----

form bdc_dynpro using program dynpro.

clear bdcdata.

bdcdata-program = program.

bdcdata-dynpro = dynpro.

bdcdata-dynbegin = 'X'.

append bdcdata.

endform.

*----

To Insert field

*----

form bdc_field using fnam fval.

clear bdcdata.

bdcdata-fnam = fnam.

bdcdata-fval = fval.

append bdcdata.

endform.

Re: give a simple BDC example for CALL TRANSACTION METHOD..

Former Member — Mon, 15 Oct 2007 08:29:21 GMT

this is the common method you can find eample code in the below

the BDC program should be in this format

Transaction Recorder (SHDB)

How to Upload Presentation Server Flat file to SAP R/3 system???

How to upload application server file to R/3 system?

Definition

Example - Call Transaction Method

Transaction Recorder (SHDB)

Before you work with the Batch Input methods, you should know the purpose of the tool

Transaction Recorder.

Use:

You can use the transaction recorder to record a series of transactions and their screens.

Features:

You can use the recording to create

Data transfer programs that use batch input or CALL TRANSACTION

Batch input sessions

Test data

Function modules.

Note: It doesn’t record F1, F4 and Scrollbar movements

Upload Flat file from Presentation Server to SAP R/3

CALL FUNCTION ‘GUI_UPLOAD'

EXPORTING

CODEPAGE = ‘IBM'

FILENAME = P_UFILE

FILETYPE = 'DAT'

TABLES

DATA_TAB = INT_TAB

EXCEPTIONS

CONVERSION_ERROR = 1

FILE_OPEN_ERROR = 2

FILE_READ_ERROR = 3

INVALID_TYPE = 4

NO_BATCH = 5

UNKNOWN_ERROR = 6

INVALID_TABLE_WIDTH = 7

GUI_REFUSE_FILETRANSFER = 8

CUSTOMER_ERROR = 9

OTHERS = 10 .

IF SY-SUBRC NE 0.

MESSAGE E999(FR) WITH 'ERROR IN FILE UPLOAD'.

ENDIF.

Upload file from application server to SAP R/3

Open the the application server file

OPEN DATASET <dsn> FOR INPUT <mode>

Read the data from application server file

READ DATASET <dsn> INTO <wa>

And then close the application server file

CLOSE DATASET <dsn>

Definition- Declaring BDC Table

DATA: BDC_TAB LIKE STANDARD TABLE OF

BDCDATA INITIAL SIZE 6

WITH HEADER LINE .

The internal table used to collect the transaction’s information must be declared “LIKE BDCDATA”.

Filling BDC Table – Method #1

FORM FILL_BDC_TAB.

REFRESH BDC_TAB.

CLEAR BDC_TAB.

BDC_TAB-PROGRAM = ‘SAPMF02K’.

BDC_TAB-DYNPRO = ‘01016’.

BDC_TAB-DYNBEGIN = ‘X’.

APPEND BDC_TAB.

CLEAR BDC_TAB.

BDC_TAB-FNAM = ‘RF02K-LIFNR’.

BDC_TAB-FVAL = ‘TEST1’.

APPEND BDC_TAB.

CLEAR BDC_TAB.

BDC_TAB-FNAM = ‘RF02K-D0010’.

BDC_TAB-FVAL = ‘X’.

APPEND BDC_TAB.

CLEAR BDC_TAB.

BDC_TAB-PROGRAM = ‘SAPMF02K’.

BDC_TAB-DYNPRO = ‘0110’.

BDC_TAB-DYNBEGIN = ‘X’.

APPEND BDC_TAB.

CLEAR BDC_TAB.

BDC_TAB-FNAM = ‘LFA1-STRAS’.

BDC_TAB-FVAL = ‘123 Main St.’.

APPEND BDC_TAB.

CLEAR BDC_TAB.

BDC_TAB-FNAM = ‘BDC_OKCODE’.

BDC_TAB-FVAL = ‘/11’.

APPEND BDC_TAB.

ENDFORM.

Filling BDC Table – Method #2

FORM FILL_BDC_TAB.

REFRESH BDC_TAB.

PERFORM POPULATE_BDC_TAB

USING:

‘1’ ‘SAPMF02K’ ‘0106’,

‘ ‘ ‘RF02K-LIFNR’ ‘TEST1’,

‘ ‘ ‘RF02K-D0010’ ‘X’,

‘1’ ‘SAPMF02K’ ‘0110’,

‘ ‘ ‘LFA1-STRAS’, ‘123 Main St.’,

‘ ‘ ‘BDC_OKCODE’, ‘/11’.

ENDFORM.

FORM POPULATE_BDC_TAB USING FLAG VAR1 VAR2.

CLEAR BDC_TAB.

IF FLAG = ‘1’.

BDC_TAB-PROGRAM = VAR1.

BDC_TAB-DYNPRO = VAR2..

BDC_TAB-DYNBEGIN = ‘X’.

ELSE.

BDC_TAB-FNAM = VAR1.

BDC_TAB-FVAL = VAR2.

ENDIF.

APPEND BDC_TAB.

ENDFORM.

This two subroutine method to fill the BDC table is preferable because the “POPULATE_BDC_TABLE” subroutine is reusable throughout all batch input programs.

Example #1 - Change Vendor (Call Transaction Method)

Example #1- Declaration Section

REPORT Y180DM10.

DATA: BDC_TAB LIKE STANDARD TABLE OF

BDCDATA INITIAL SIZE 6 WITH HEADER LINE.

INFILE(20) VALUE ‘/tmp/bc180_file4’.

DATA: BEGIN OF INREC.

VENDNUM LIKE LFA1-LIFNR.

STREET LIKE LFA1-STRAS.

END OF INREC.

PARAMETERS: DISPMODE DEFAULT ‘A’,

UPDAMODE DEFAULT ‘S’.

START-OF-SELECTION.

OPEN DATASET INFILE

FOR INPUT IN TEXT MODE.

DO.

READ DATASET INFILE INTO INREC.

IF SY-SUBRC < > 0. EXIT. ENDIF.

PERFORM FILL_BDC_TAB.

CALL TRANSACTION ‘FK02’

USING BDC_TAB

MODE DISPMODE

UPDATE UPDAMODE.

IF SY-SUBRC < > 0.

WRITE: /‘ERROR’.

ENDIF.

ENDDO.

CLOSE DATASET INFILE.

synchronous updating

DO.

………

PERFORM FILL_BDC_TAB.

CALL TRANSACTION ‘FK02’

USING BDC_TAB

MODE ‘N’

UPDATE ‘S’.

IF SY-SUBRC < > 0.

WRITE: /‘ERROR’.

ENDIF.

ENDDO.

With synchronous updating, we can check SY-SUBRC to determine the success of the transaction and the actual update to the database.

asynchronous updating

DO.

………

PERFORM FILL_BDC_TAB.

CALL TRANSACTION ‘FK02’

USING BDC_TAB

MODE ‘N’

UPDATE ‘A’.

IF SY-SUBRC < > 0.

WRITE: /‘ERROR’.

ENDIF.

ENDDO.

With asynchronous updating, we can check SY-SUBRC to determine the success of the transaction only, not the actual update to the database.

Error Handling

Write an error report.

Send the record(s) in error to an error file.

Create a batch input session with the record(s) in error.

To store error messages ( CALL TRANSACTION )

data: begin of Tab_Mess occurs 0.

include structure bdcmsgcoll.

data : end of Tab_Mess,

CALL TRANSACTION ‘FK02’ USING BDC_TAB MODE ‘N’ UPDATE ‘S’

MESSAGES INTO TAB_MESS.

IF SY-SUBRC NE 0.

WRITE: / Tab_MESS-TCODE, Tab_MESS-DYNUMB, Tab_MESS-MSGTYP ,

Tab_MESS-MSGID.

ENDIF.

i am giving you example for Change Vendor you practice for ur tcode

For our example, we will use the “Change Vendor” transaction (“FK02”) to add a street address to an already existing vendor.

Step #1

Use “SystemStatus” menu path to determine online program name (SAPMF02K), screen number (0110)

Step #2

Use “F1” key and “Technical Info” pushbutton in each screen field to be filled to determine the field name.

Step #3

Determine how to proceed in the transaction

(save the record by clicking on the ‘Save’ pushbutton or pressing the ‘F11’ key).

BDC Table Contents

After researching the transaction we can determine the contents of the BDC table.

PROGRAM DYNPRO DYNBEGIN FNAM FVAL

SAMPF02K 0106 X

RF02K-LIFNR TEST1

RF02K-D0110 X

SAMPF02K 0110 X

LFA1-STRAS 123 Main St.

BDC_OKCODE /11

Batch Input Methods

“CALL TRANSACTION USING”

STATEMENT

Call transaction - for data transfer

Processing batch input data with CALL TRANSACTION USING is the faster of the two recommended data transfer methods. In this method, legacy data is processed inline in your data transfer program.

Syntax:

CALL TRANSACTION <tcode>

USING <bdc_tab>

MODE <mode>

UPDATE <update>

A Display all

E Display errors only

N No display

S Synchronous

A Asynchronous

L Local update

The process flow of CALL TRANSACTION

A program that uses CALL TRANSACTION USING to process legacy data should execute thefollowing steps:

Prepare a BDCDATA structure for the transaction that you wish to run.

Prepare a internal table to store error messages Tab_Mess like structure of BDCMSGCOLL.

With a CALL TRANSACTION USING statement, call the transaction and prepare the BDCDATA structure. For example:

CALL TRANSACTION ‘MM01' USING BDCDATA MODE 'A' UPDATE 'S'. MESSAGES INTO TAB_MESS.

IF SY-SUBRC <> 0.

<Error_handling>.

ENDIF.

Overview of Batch Input Session

The first batch input method is to create a batch input session. It is the processing of this batch input session that updates the database, not the execution of the batch input program.

REPORT ZRK1CALLTRANS .

TABLES:MARA,MAKT.

DATA:BEGIN OF ITAB OCCURS 0,

MATNR LIKE RMMG1-MATNR,

MBRSH LIKE RMMG1-MBRSH,

MTART LIKE RMMG1-MTART,

MAKTX LIKE MAKT-MAKTX,

MEINS LIKE MARA-MEINS,

MATKL LIKE MARA-MATKL,

END OF ITAB.

DATA : ITAB2 LIKE BDCDATA OCCURS 0 WITH HEADER LINE.

CALL FUNCTION 'WS_UPLOAD'

EXPORTING

CODEPAGE = 'IBM '

FILENAME = 'C:\SUMAN.TXT '

FILETYPE = 'DAT'

HEADLEN = ' '
LINE_EXIT = ' '
TRUNCLEN = ' '
USER_FORM = ' '
USER_PROG = ' '
DAT_D_FORMAT = ' '
IMPORTING
FILELENGTH =

TABLES

DATA_TAB = ITAB

EXCEPTIONS
CONVERSION_ERROR = 1
FILE_OPEN_ERROR = 2
FILE_READ_ERROR = 3
INVALID_TYPE = 4
NO_BATCH = 5
UNKNOWN_ERROR = 6
INVALID_TABLE_WIDTH = 7
GUI_REFUSE_FILETRANSFER = 8
CUSTOMER_ERROR = 9
NO_AUTHORITY = 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.

ENDIF.

LOOP AT ITAB.

WRITE : / ITAB-MATNR,ITAB-MBRSH,ITAB-MTART,ITAB-MAKTX,ITAB-MEINS,

ITAB-MATKL.

REFRESH ITAB2.

CLEAR ITAB2.

ITAB2-PROGRAM = 'SAPLMGMM'.

ITAB2-DYNPRO = '0060'.

ITAB2-DYNBEGIN = 'X'.

APPEND ITAB2.

CLEAR ITAB2.

ITAB2-FNAM = 'RMMG1-MATNR'.

ITAB2-FVAL = ITAB-MATNR.

APPEND ITAB2.

CLEAR ITAB2.

ITAB2-FNAM = 'RMMG1-MBRSH'.

ITAB2-FVAL = ITAB-MBRSH.

APPEND ITAB2.

CLEAR ITAB2.

ITAB2-FNAM = 'RMMG1-MTART'.

ITAB2-FVAL = ITAB-MTART.

APPEND ITAB2.

CLEAR ITAB2.

ITAB2-FNAM = 'BDC_OKCODE'.

ITAB2-FVAL = '/00'.

APPEND ITAB2.

CLEAR ITAB2.

ITAB2-PROGRAM = 'SAPLMGMM'.

ITAB2-DYNPRO = '0070'.

ITAB2-DYNBEGIN = 'X'.

APPEND ITAB2.

CLEAR ITAB2.

ITAB2-FNAM = 'MSICHTAUSW-KZSEL(01)'.

ITAB2-FVAL = 'X'.

APPEND ITAB2.

CLEAR ITAB2.

ITAB2-FNAM = 'BDC_OKCODE'.

ITAB2-FVAL = '=ENTR'.

APPEND ITAB2.

CLEAR ITAB2.

ITAB2-PROGRAM = 'SAPLMGMM'.

ITAB2-DYNBEGIN = '4004'.

ITAB2-DYNBEGIN = 'X'.

APPEND ITAB2.

CLEAR ITAB2.

ITAB2-FNAM = 'MAKT-MAKTX'.

ITAB2-FVAL = ITAB-MAKTX.

APPEND ITAB2.

CLEAR ITAB2.

ITAB2-FNAM = 'MARA-MEINS'.

ITAB2-FVAL = ITAB-MEINS.

APPEND ITAB2.

CLEAR ITAB2.

ITAB2-FNAM = 'MARA-MATKL'.

ITAB2-FVAL = ITAB-MATKL.

APPEND ITAB2.

CLEAR ITAB2.

ITAB2-FNAM = 'BDC_OKCODE'.

ITAB2-FVAL = '=BU'.

APPEND ITAB2.

CLEAR ITAB2.

CALL TRANSACTION 'MM01' USING ITAB2 MODE 'A' UPDATE 'A'.

ENDLOOP.

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

EDIT BATCH INPUT  SERVICES SYSTEM

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.

Define jobs Jobs  Administration Tools

Jobs services System

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 Krishna 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.

Reward if usefull