How to handle table control in bdc

[Former Member]

Hi SAP GURUs,

I had a question in one interview how to handle table control in bdc, I know technically that means recording all those, BUT i am not getting how to express that one in interview point of view plz tell me ,

Thanks ,

Prasad.

[Former Member]

An example abap program of handling Table Control during bdc programming.

check if this can help u.

REPORT zmm_bdcp_purchaseorderkb02

NO STANDARD PAGE HEADING LINE-SIZE 255.

----

---

• Declaring internal tables *

----

---

*-----Declaring line structure

DATA : BEGIN OF it_dummy OCCURS 0,

dummy(255) TYPE c,

END OF it_dummy.

*-----Internal table for line items

DATA : BEGIN OF it_idata OCCURS 0,

ematn(18), "Material Number.

menge(13), "Qyantity.

netpr(11), "Net Price.

werks(4), "Plant.

ebelp(5), "Item Number.

END OF it_idata.

*-----Deep structure for header data and line items

DATA : BEGIN OF it_me21 OCCURS 0,

lifnr(10), "Vendor A/c No.

bsart(4), "A/c Type.

bedat(8), "Date of creation of PO.

ekorg(4), "Purchasing Organisation.

ekgrp(3), "Purchasing Group.

x_data LIKE TABLE OF it_idata,

END OF it_me21.

DATA : x_idata LIKE LINE OF it_idata.

DATA : v_delimit VALUE ','.

DATA : v_indx(3) TYPE n.

DATA : v_fnam(30) TYPE c.

DATA : v_count TYPE n.

DATA : v_ne TYPE i.

DATA : v_ns TYPE i.

*include bdcrecx1.

INCLUDE zmm_incl_purchaseorderkb01.

----

---

• Search help for file *

----

---

AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.

CALL FUNCTION 'F4_FILENAME'

EXPORTING

program_name = syst-cprog

dynpro_number = syst-dynnr

IMPORTING

file_name = p_file.

START-OF-SELECTION.

----

---

• To upload the data into line structure *

----

---

CALL FUNCTION 'WS_UPLOAD'

EXPORTING

filename = p_file

filetype = 'DAT'

TABLES

data_tab = it_dummy.

----

---

• Processing the data from line structure to internal tables *

----

---

REFRESH:it_me21.

CLEAR :it_me21.

LOOP AT it_dummy.

IF it_dummy-dummy+0(01) = 'H'.

v_indx = v_indx + 1.

CLEAR it_idata.

REFRESH it_idata.

CLEAR it_me21-x_data.

REFRESH it_me21-x_data.

SHIFT it_dummy.

SPLIT it_dummy AT v_delimit INTO it_me21-lifnr

it_me21-bsart

it_me21-bedat

it_me21-ekorg

it_me21-ekgrp.

APPEND it_me21.

ELSEIF it_dummy-dummy+0(01) = 'L'.

SHIFT it_dummy.

SPLIT it_dummy AT v_delimit INTO it_idata-ematn

it_idata-menge

it_idata-netpr

it_idata-werks

it_idata-ebelp.

APPEND it_idata TO it_me21-x_data.

MODIFY it_me21 INDEX v_indx.

ENDIF.

ENDLOOP.

----

---

• To open the group *

----

---

PERFORM open_group.

----

---

• To populate the bdcdata table for header data *

----

---

LOOP AT it_me21.

v_count = v_count + 1.

REFRESH it_bdcdata.

PERFORM subr_bdc_table USING: 'X' 'SAPMM06E' '0100',

' ' 'BDC_CURSOR' 'EKKO-LIFNR',

' ' 'BDC_OKCODE' '/00',

' ' 'EKKO-LIFNR' it_me21-lifnr,

' ' 'RM06E-BSART' it_me21-bsart,

' ' 'RM06E-BEDAT' it_me21-bedat,

' ' 'EKKO-EKORG' it_me21-ekorg,

' ' 'EKKO-EKGRP' it_me21-ekgrp,

' ' 'RM06E-LPEIN' 'T'.

PERFORM subr_bdc_table USING: 'X' 'SAPMM06E' '0120',

' ' 'BDC_CURSOR' 'RM06E-EBELP',

' ' 'BDC_OKCODE' '/00'.

MOVE 1 TO v_indx.

*-----To populate the bdcdata table for line item data

LOOP AT it_me21-x_data INTO x_idata.

CONCATENATE 'EKPO-EMATN(' v_indx ')' INTO v_fnam.

PERFORM subr_bdc_table USING ' ' v_fnam x_idata-ematn.

CONCATENATE 'EKPO-MENGE(' v_indx ')' INTO v_fnam.

PERFORM subr_bdc_table USING ' ' v_fnam x_idata-menge.

CONCATENATE 'EKPO-NETPR(' v_indx ')' INTO v_fnam.

PERFORM subr_bdc_table USING ' ' v_fnam x_idata-netpr.

CONCATENATE 'EKPO-WERKS(' v_indx ')' INTO v_fnam.

PERFORM subr_bdc_table USING ' ' v_fnam x_idata-werks.

v_indx = v_indx + 1.

PERFORM subr_bdc_table USING: 'X' 'SAPMM06E' '0120',

' ' 'BDC_CURSOR' 'RM06E-EBELP',

' ' 'BDC_OKCODE' '/00'.

ENDLOOP.

PERFORM subr_bdc_table USING: 'X' 'SAPMM06E' '0120',

' ' 'BDC_CURSOR' 'RM06E-EBELP',

' ' 'BDC_OKCODE' '=BU'.

PERFORM bdc_transaction USING 'ME21'.

ENDLOOP.

PERFORM close_group.

----

---

• End of selection event *

----

---

END-OF-SELECTION.

IF session NE 'X'.

*-----To display the successful records

WRITE :/10 text-001. "Sucess records

WRITE :/10 SY-ULINE(20).

SKIP.

IF it_sucess IS INITIAL.

WRITE 😕 text-002.

ELSE.

WRITE 😕 text-008, "Total number of Succesful records

35 v_ns.

SKIP.

WRITE:/ text-003, "Vendor Number

17 text-004, "Record number

30 text-005. "Message

ENDIF.

LOOP AT it_sucess.

WRITE:/4 it_sucess-lifnr,

17 it_sucess-tabix CENTERED,

30 it_sucess-sucess_rec.

ENDLOOP.

SKIP.

*-----To display the erroneous records

WRITE:/10 text-006. "Error Records

WRITE:/10 SY-ULINE(17).

SKIP.

IF it_error IS INITIAL.

WRITE:/ text-007. "No error records

ELSE.

WRITE:/ text-009, "Total number of erroneous records

35 v_ne.

SKIP.

WRITE:/ text-003, "Vendor Number

17 text-004, "Record number

30 text-005. "Message

ENDIF.

LOOP AT it_error.

WRITE:/4 it_error-lifnr,

17 it_error-tabix CENTERED,

30 it_error-error_rec.

ENDLOOP.

REFRESH it_sucess.

REFRESH it_error.

ENDIF.

CODE IN INCLUDE.

----

---

• Include ZMM_INCL_PURCHASEORDERKB01

----

---

DATA: it_BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE.

DATA: it_MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.

DATA: E_GROUP_OPENED.

*-----Internal table to store sucess records

DATA:BEGIN OF it_sucess OCCURS 0,

msgtyp(1) TYPE c,

lifnr LIKE ekko-lifnr,

tabix LIKE sy-tabix,

sucess_rec(125),

END OF it_sucess.

DATA: g_mess(125) type c.

*-----Internal table to store error records

DATA:BEGIN OF it_error OCCURS 0,

msgtyp(1) TYPE c,

lifnr LIKE ekko-lifnr,

tabix LIKE sy-tabix,

error_rec(125),

END OF it_error.

----

---

• Selection screen

----

---

SELECTION-SCREEN BEGIN OF LINE.

PARAMETERS session RADIOBUTTON GROUP ctu. "create session

SELECTION-SCREEN COMMENT 3(20) text-s07 FOR FIELD session.

SELECTION-SCREEN POSITION 45.

PARAMETERS ctu RADIOBUTTON GROUP ctu. "call transaction

SELECTION-SCREEN COMMENT 48(20) text-s08 FOR FIELD ctu.

SELECTION-SCREEN END OF LINE.

SELECTION-SCREEN BEGIN OF LINE.

SELECTION-SCREEN COMMENT 3(20) text-s01 FOR FIELD group.

SELECTION-SCREEN POSITION 25.

PARAMETERS group(12). "group name of session

SELECTION-SCREEN COMMENT 48(20) text-s05 FOR FIELD ctumode.

SELECTION-SCREEN POSITION 70.

PARAMETERS ctumode LIKE ctu_params-dismode DEFAULT 'N'.

"A: show all dynpros

"E: show dynpro on error only

"N: do not display dynpro

SELECTION-SCREEN END OF LINE.

SELECTION-SCREEN BEGIN OF LINE.

SELECTION-SCREEN COMMENT 48(20) text-s06 FOR FIELD cupdate.

SELECTION-SCREEN POSITION 70.

PARAMETERS cupdate LIKE ctu_params-updmode DEFAULT 'L'.

SELECTION-SCREEN END OF LINE.

SELECTION-SCREEN BEGIN OF LINE.

SELECTION-SCREEN COMMENT 3(20) text-s03 FOR FIELD keep.

SELECTION-SCREEN POSITION 25.

PARAMETERS: keep AS CHECKBOX. "' ' = delete session if finished

"'X' = keep session if finished

SELECTION-SCREEN COMMENT 48(20) text-s09 FOR FIELD e_group.

SELECTION-SCREEN POSITION 70.

PARAMETERS e_group(12). "group name of error-session

SELECTION-SCREEN END OF LINE.

SELECTION-SCREEN BEGIN OF LINE.

SELECTION-SCREEN COMMENT 51(17) text-s03 FOR FIELD e_keep.

SELECTION-SCREEN POSITION 70.

PARAMETERS: e_keep AS CHECKBOX. "' ' = delete session if finished

"'X' = keep session if finished

SELECTION-SCREEN END OF LINE.

PARAMETERS:p_file LIKE rlgrap-filename.

----

---

• at selection screen *

----

---

AT SELECTION-SCREEN.

• group and user must be filled for create session

IF SESSION = 'X' AND

GROUP = SPACE. "OR USER = SPACE.

MESSAGE E613(MS).

ENDIF.

----

---

• create batchinput session *

----

---

FORM OPEN_GROUP.

IF SESSION = 'X'.

SKIP.

WRITE: /(20) 'Create group'(I01), GROUP.

SKIP.

*----open batchinput group

CALL FUNCTION 'BDC_OPEN_GROUP'

EXPORTING

CLIENT = SY-MANDT

GROUP = GROUP

USER = sy-uname.

WRITE:/(30) 'BDC_OPEN_GROUP'(I02),

(12) 'returncode:'(I05),

SY-SUBRC.

ENDIF.

ENDFORM. "OPEN_GROUP

----

---

• end batchinput session *

----

---

FORM CLOSE_GROUP.

IF SESSION = 'X'.

*------close batchinput group

CALL FUNCTION 'BDC_CLOSE_GROUP'.

WRITE: /(30) 'BDC_CLOSE_GROUP'(I04),

(12) 'returncode:'(I05),

SY-SUBRC.

ELSE.

IF E_GROUP_OPENED = 'X'.

CALL FUNCTION 'BDC_CLOSE_GROUP'.

WRITE: /.

WRITE: /(30) 'Fehlermappe wurde erzeugt'(I06).

ENDIF.

ENDIF.

ENDFORM. "CLOSE_GROUP

----

---

• Start new transaction according to parameters *

----

---

FORM BDC_TRANSACTION USING TCODE TYPE ANY.

DATA: L_SUBRC LIKE SY-SUBRC.

*------batch input session

IF SESSION = 'X'.

CALL FUNCTION 'BDC_INSERT'

EXPORTING

TCODE = TCODE

TABLES

DYNPROTAB = it_BDCDATA.

WRITE: / 'BDC_INSERT'(I03),

TCODE,

'returncode:'(I05),

SY-SUBRC,

'RECORD:',

SY-INDEX.

ELSE.

REFRESH it_MESSTAB.

CALL TRANSACTION TCODE USING it_BDCDATA

MODE CTUMODE

UPDATE CUPDATE

MESSAGES INTO it_MESSTAB.

L_SUBRC = SY-SUBRC.

WRITE: / 'CALL_TRANSACTION',

TCODE,

'returncode:'(I05),

L_SUBRC,

'RECORD:',

SY-INDEX.

ENDIF.

----

---

• Message handling for Call Transaction *

----

---

perform subr_mess_hand using g_mess.

*-----Erzeugen fehlermappe

IF L_SUBRC <> 0 AND E_GROUP <> SPACE.

IF E_GROUP_OPENED = ' '.

CALL FUNCTION 'BDC_OPEN_GROUP'

EXPORTING

CLIENT = SY-MANDT

GROUP = E_GROUP

USER = sy-uname

KEEP = E_KEEP.

E_GROUP_OPENED = 'X'.

ENDIF.

CALL FUNCTION 'BDC_INSERT'

EXPORTING

TCODE = TCODE

TABLES

DYNPROTAB = it_BDCDATA.

ENDIF.

REFRESH it_BDCDATA.

ENDFORM. "BDC_TRANSACTION

----

---

• Form subr_bdc_table *

----

---

• text

----

---

• -->P_0220 text *

• -->P_0221 text *

• -->P_0222 text *

----

---

FORM subr_bdc_table USING VALUE(P_0220) TYPE ANY

VALUE(P_0221) TYPE ANY

VALUE(P_0222) TYPE ANY.

CLEAR it_bdcdata.

IF P_0220 = ' '.

CLEAR it_bdcdata.

it_bdcdata-fnam = P_0221.

it_bdcdata-fval = P_0222.

APPEND it_bdcdata.

ELSE.

it_bdcdata-dynbegin = P_0220.

it_bdcdata-program = P_0221.

it_bdcdata-dynpro = P_0222.

APPEND it_bdcdata.

ENDIF.

ENDFORM. " subr_bdc_table

----

---

• Form subr_mess_hand *

----

---

• text *

----

---

• -->P_G_MESS text *

----

---

FORM subr_mess_hand USING P_G_MESS TYPE ANY.

LOOP AT IT_MESSTAB.

CALL FUNCTION 'FORMAT_MESSAGE'

EXPORTING

ID = it_messtab-msgid

LANG = it_messtab-msgspra

NO = it_messtab-msgnr

v1 = it_messtab-msgv1

v2 = it_messtab-msgv2

IMPORTING

MSG = P_G_MESS

EXCEPTIONS

OTHERS = 0.

CASE it_messtab-msgtyp.

when 'E'.

it_error-error_rec = P_G_MESS.

it_error-lifnr = it_me21-lifnr.

it_error-tabix = v_count.

APPEND IT_ERROR.

when 'S'.

it_sucess-sucess_rec = P_G_MESS.

it_sucess-lifnr = it_me21-lifnr.

it_sucess-tabix = v_count.

APPEND IT_SUCESS.

endcase.

ENDLOOP.

Describe table it_sucess lines v_ns.

Describe table it_error lines v_ne.

ENDFORM. " subr_mess_hand

Regards

Sravani

[former_member188594]

Hi,

First of all explain what a table control is and its use then in conjunction with BDC you tell like,, we can handle table control using line index ,

Line index indicates which line of Table control is to be use for BDC transaction,

Ex -

perform bdc_field using 'RC29K-AUSKZ(01)'

Here in this example, it indicates that the 1st line of table control is going to be used for transaction which is Line index of Table Control.

Regards,

Sekhar

[Former Member]

Explaining table control means

take example of VA01

In this one I have to explain Fields in that one

Item No , Material No, Order Quantity and Plant no using Table control

In this one First one is the Item for this one is line index is 1

Like this I have to explain right? or wrong

Plz guide me

Thanks

Prasad.

[Former Member]

Durga prasad,

In an interview ,it is not necessary to explain like what you hav in your thoughts.

>take example of VA01

>In this one I have to explain Fields in that one

>Item No , Material No, Order Quantity and Plant no using >Table control

>In this one First one is the Item for this one is line index is 1

Experts assumes that you are not good enough to explain in much effective way...people who knows VA01 are very well understand the fields available..so you hav to be good in explaining Table control...followed by how it is technically used in BDC ..like wat others answered before to my post..

so in an interview be clear in your points..explaining the fields with their index is not a valid point.

-Siva..

[Former Member]

Hi,

I will explain with simple example

for mr21 which is used for material price uploading

for a date company code and plant there exists many materials and price for each material .

so date company code and plant comes under header data where as material number and price comes under item data.

So in this case we need table control to scroll down for item data for each header

Regards

[Former Member]

Hi

theoritically this can help u.

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.

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.

Thanks &Regards

Sravani

[SantoshKallem]

use one internal tables for table control data.

define one variable and increase that in loop until the header key field changes,

and concatenate that to the field and populate data in that.

regards.

santhosh reddy

[Former Member]

Chk this thread..

[Former Member]

Hai Durga Prasad,

While Handling Table Control We Have Take Care of Screen Resolution.

While Recoring for a table control Use + Button Instead Of writing fields Directly and using scrool Bar. .

So That there Will Be no Problem While Handling BDC Table Control.

Regards.

Eshwar.