Interview Questions

[Former Member]

Can anyone plz tell me the answers of following questions which I have often faced in interviews.Plz answers,point will be awarded undoubtedly.

1.Can we do ALV report without using function modules.

2.what is table control in BDC and how do we handle it.

3.How to add search help to a report.

4.How to make screen resolution independent in BDC.

5.what is your client process.

6.can anyone plz tell me the steps for performance tuning.

7.what is output determination.

8.what are the events used in ALV reports.

9.How to determine whether to store table or view in buffer.

10.If BAPI can be used at a point, can we use call transaction at that place.

11.If break-point is used within select-endselect,then will it show any error.

12.if we can write something by hard-coding it in write statement,then why we use text-001,002,etc.

[Former Member]

Hi,

1.Can we do ALV report without using function modules?

Ans : these are function modules in alvs

1.reuse_alv_fieldcatelog_merge

2.reuse_alv_list_display

3.reuse_alv_grid_display.

4.reuse_alv_commentary_write

5.reuse_alv_variant_default_get

6.reuse_alv_variant_f4

7.reuse_alv_variant_existence

8.reuse_alv_events_get

9.reuse_alv_pop_upto_select.

The function module ALV uses FM to trigger display and

sorting appending think for alv report,

where as Methods are used in the OOPs concept fo the ALV.

the other difference is the user has more flexablity fi he

uses the OOPS ALV than the FM ALV.

2.what is table control in BDC and how do we handle it?

Ans :-

a) 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)'

indicates 1st line of table control is going to be used for transaction which is Line index of Table Control

b)Table control is used for entering multiple line items in

BDC.

c) Table control is used to enter multiple line items in BDC.

In the loop statement for BDC_INSERT we have to go for one

more loop with in this loop. An make sure is there any ADD

button is there for the table control. And write statements

accordingly.

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

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

3.How to add search help to a report.

ans : - Elementary search helps defines a search path where we will define the table from which the data has to be read and the selection criteria. Through import and export parameters. Used when we gets the data rom a single table.

4.How to make screen resolution independent in BDC.

5.what is your client process.

6.can anyone plz tell me the steps for performance tuning.

7.what is output determination.

8.what are the events used in ALV reports.

9.How to determine whether to store table or view in buffer.

10.If BAPI can be used at a point, can we use call transaction at that place.

11.If break-point is used within select-endselect,then will it show any error.

12.if we can write something by hard-coding it in write statement,then why we use text-001,002,etc.

Regards,

Chandru

[Former Member]

Hi,

Here are the answers for some of ur questions....

1) Events in ALV

print_end_of_list:Define output text to be printed at thend of the entire list

print_top_of_list:Define output text to be printed at the beginning of the entire list

print_end_of_page:Define output text to be printed at the end of each page

print_top_of_page:Define output text to be printed at the beginning of each page

subtotal_text:Define self-defined subtotals texts

Only events with a form routine name are processed.

The I_EVENTS table returns with the following possible constants:

1. Slis_ev_item_data_expand TYPE slis_formname VALUE 'ITEM_DATA_EXPAND'.

Only relevant for hierarchical-sequential lists using the layout parameter IS_LAYOUT-EXPAND_FIELDNAME of the structure IS_LAYOUT. Exit for passing item entries (ITEM table) for a header record that was expanded interactively by the user.

2. Slis_ev_reprep_sel_modify TYPE slis_formname VALUE 'REPREP_SEL_MODIFY'.

RS_SELFIELD-TABINDEX contains the header table index for which the item entries are to be put in the global item output table (T_OUTTAB_SLAVE). The Callback is only called if ALV has no items for a header that is to be expanded.

RFLG_ALL is passed with 'X' if the user shows all items. The application must ensure that entries are not repeated in the item table.

RS_SELFIELD is initial in this case.

3. Slis_ev_caller_exit_at_start TYPE slis_formname VALUE 'CALLER_EXIT'.

Is called at the beginning of the function module to make special settings. It is not usually used.

4. Slis_ev_user_command TYPE slis_formname VALUE 'USER_COMMAND'.

As this is a frequently-used Callback event, the form routine can also be passed directly in the interface by passing the user command in the IMPORTING parameter I_CALLBACK_USER_COMMAND.

5. Slis_ev_top_of_page TYPE slis_formname VALUE 'TOP_OF_PAGE'.

Equivalent to the list processing TOP-OF-PAGE event.

6. Slis_ev_top_of_coverpage TYPE slis_formname VALUE 'TOP_OF_COVERPAGE'.

The selection information and list status are output together (if they exist) on a separate page by default

7. Slis_ev_end_of_coverpage TYPE slis_formname VALUE 'END_OF_COVERPAGE'.

Analogously to TOP_OF_COVERPAGE the user can add other information

to the information output by ALV (selection information, list status) at this event.

8. Slis_ev_foreign_top_of_page TYPE slis_formname VALUE ‘FOREIGN_TOP_OF_PAGE'.

The Top-of-page event is always processed in ALV and is only passed to the caller via the Callback mechanism. This is still the case if the caller, e.g. by a user action, processes a branch list which was not formatted by ALV (e.g. a popup with additional information about the list record selected and displayed by ALV).

In this case, top-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event top-of-page still occurs in ALV. When ALV notices a top-of-page which was not caused by an ALV output, the form routine in FOREIGN_TOP_OF_PAGE is called.

9. Slis_ev_foreign_end_of_page TYPE slis_formname VALUE 'FOREIGN_END_OF_PAGE'.

The event end-of-page is always processed in ALV and only passed to the caller via callback. This is still the case, e.g. when the caller processes a details list which was not formatted by ALV (e.g. a popup with further information about selected list records which were displayed by ALV).

In this case, end-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event end-of-page still occurs in ALV. When ALV notices an end-of-page that was not caused by an ALV output, the form routine in FOREIGN_END_OF_PAGE is called.

10. Slis_ev_pf_status_set TYPE slis_formname VALUE 'PF_STATUS_SET'.

If a user list status is to be set, it must be done in the form routine assigned to this event. The ALV function codes, which must not be active, are in the Parameter RT_EXTAB. This table must be passed with the SET PF-STATUS command (with inactive user function codes as well, if necessary).

The STANDARD status of the function group SALV should be used as a template for a user-specific status. As this is a frequently used Callback event, its form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_PF_STATUS_SET.

11. Slis_ev_end_of_page TYPE slis_formname VALUE 'END_OF_PAGE'.

Information output at the end of a page. This is only called for printing.

12. Slis_ev_end_of_list TYPE slis_formname VALUE 'END_OF_LIST'.

Information output at the end of the list

13. Slis_ev_subtotal_text TYPE slis_formname VALUE 'SUBTOTAL_TEXT'.

Performance Tuning

There are various performance tuning tips and tricks to make the ABAP programs efficient in doing their work.

Use of selection criteria

Instead of selecting all the data and doing the processing during the selection, it is advisable to restrict the data to the selection criteria itself, rather than filtering it out using the ABAP code.

Not recommended

Select * from zflight.

Check : zflight-airln = ‘LF’ and zflight-fligh = ‘BW222’.

Endselect.

Recommended

Select * from zflight where airln = ‘LF’ and fligh = ‘222’.

Endselect.

One more point to be noted here is of the select *. Often this is a lazy coding practice. When a programmer gives select * even if one or two fields are to be selected, this can significantly slow the program and put unnecessary load on the entire system. When the application server sends this request to the database server, and the database server has to pass on the entire structure for each row back to the application server. This consumes both CPU and networking resources, especially for large structures.

Thus it is advisable to select only those fields that are needed, so that the database server passes only a small amount of data back.

Also it is advisable to avoid selecting the data fields into local variables as this also puts unnecessary load on the server. Instead attempt must be made to select the fields into an internal table.

Use of aggregate functions

Use the already provided aggregate functions, instead of finding out the minimum/maximum values using ABAP code.

Not recommended

Maxnu = 0.

Select * from zflight where airln = ‘LF’ and cntry = ‘IN’.

Check zflight-fligh > maxnu.

Maxnu = zflight-fligh.

Endselect.

Recommended

Select max( fligh ) from zflight into maxnu where airln = ‘LF’ and cntry = ‘IN’.

Check this link for more....

http://www.thespot4sap.com/Articles/SAPABAPPerformanceTuning_Introduction.asp

About setting breakpoint witihn select and endselect

You can set breakpoint within select and endselect statement. It is possible. It wont give any error. But it is not advisable to use select..endselect statement due to performance issue.

if we can write something by hard-coding it in write statement,then why we use text-001,002,etc.

Instead of using text-elements, we can hard code the values. But if u hard code the values, the LANGUAGE TRANSLATION will not happen . The string which you put inside quotes will remain in the same language. When you login into some other language, it will not be translated into that language. So it is not adviced to hard code the values.

Regards,

Shanthi.P

• Reward points if useful ****