Output Layout and Screen Flow:

Selection Screen: Standard selection screen for LDB PNP
Report Generated: Standard ALV Layout
Download to Excel: Excel in place using BDS technology

Tables

Create tables listed below. You should create a maintenance table or view cluster (Please refer to other documentation on SDN how to create a maintenance table or view cluster) to make an easy user interface.

ZHQUE_TCODE

MANDT MANDT CLNT 3
TCODE TCODE CHAR 20
STEXT STEXT CHAR 40

2. ZHQUE_FIELDS

MANDT MANDT CLNT 3
TCODE TCODE CHAR 20
INFTY INFTY CHAR 4
TABNAME TABNAME CHAR 30
FIELDNAME FIELDNAME CHAR 30
FIELDALIAS ZDE_FIELDALIAS CHAR 30
FIELDNMPY ZDE_FIELDNMPY CHAR 30
FIELDTEXT STEXT CHAR 40
SEQNR SEQNR NUMC 3

3. ZHQUE_WGTYP

MANDT MANDT CLNT 3
FIELDNAME FIELDNAME CHAR 30
OPERATION ZDE_OPERATION CHAR 1
DESCRIPTION TEXT80 CHAR 80
LGART01 ZDE_LGNM CHAR 4
LGART02 ZDE_LGNM CHAR 4
LGART03 ZDE_LGNM CHAR 4
LGART04 ZDE_LGNM CHAR 4
LGART05 ZDE_LGNM CHAR 4
LGART06 ZDE_LGNM CHAR 4
LGART07 ZDE_LGNM CHAR 4
LGART08 ZDE_LGNM CHAR 4
LGART09 ZDE_LGNM CHAR 4
LGART10 ZDE_LGNM CHAR 4
LGART11 ZDE_LGNM CHAR 4
LGART12 ZDE_LGNM CHAR 4
LGART13 ZDE_LGNM CHAR 4
LGART14 ZDE_LGNM CHAR 4
LGART15 ZDE_LGNM CHAR 4
LGART16 ZDE_LGNM CHAR 4
LGART17 ZDE_LGNM CHAR 4
LGART18 ZDE_LGNM CHAR 4
LGART19 ZDE_LGNM CHAR 4
LGART20 ZDE_LGNM CHAR 4

Data Selection Logic

Choose parameters
Click execute in ALV Grid will be displayed
Download to excel, and excel in place will be displayed

Program Code

1. Create program names ZHQU01 (You may change as you like
2. Create screen 9000 and insert Container names “CONTAINER”
3. Create BDS Assignment using TCode SBDSV1 for ZSOFFICEINTEGRATION copied from SOFFICEINTEGRATION
4. Create BDS Template :
a. Class Name : ZSOFFICEINTEGRATION
b. Class Type : OT
c. Object Key : GLOBALREPORT
d. Table Template : Excel File with Name Global Report

5. Create GUI Status with Download to excel button

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

MAIN PROGRAM

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

REPORT zhque01 NO STANDARD PAGE HEADING
MESSAGE-ID aq.
*———————————————————————–
* Global data include
*———————————————————————–
INCLUDE zhque01top.
*———————————————————————–
* SAP ABAP standard include
*———————————————————————–
INCLUDE zibds_top.
INCLUDE zibds.
*———————————————————————–
* Payroll Standard Include
*———————————————————————–
*– International Include
INCLUDE rpc2rx09. “Cluster RP data definition internat. part
INCLUDE rpc2cd09. “Cluster CD data definition
INCLUDE rpppxd00. “Data definition buffer PCL1/PCL2
INCLUDE rpppxd10. “Common part buffer PCL1/PCL2
INCLUDE rpppxm00. “Buffer handling routine
*– Country Specific Include (Malaysia)
INCLUDE rpc2rll0. “Cluster RQ data definition

*———————————————————————–
* User Defined Include
*———————————————————————–
INCLUDE zhque01f01.
INCLUDE zhque01i01.
*———————————————————————–
* Events
*———————————————————————–
INITIALIZATION.
PERFORM f_initialization.

TOP-OF-PAGE.
* perform f_top_of_page.

END-OF-PAGE.
* perform f_end_of_page.
*———————————————————————–
* Start-Of-Selection
*———————————————————————–
START-OF-SELECTION.
PERFORM f_init_data.

GET pernr.
PERFORM f_get_data.

END-OF-SELECTION.
PERFORM f_layout.
PERFORM f_fieldcat.
PERFORM f_display_alv.

*———————————————————————–
* Events on selection screens
*———————————————————————–
AT SELECTION-SCREEN.

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

ZIBDS_TOP

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

TYPE-POOLS: soi, “Desktop-Office-Integration: Type-Pool
sbdst. “Business Document Services: Type-Pool

TYPES: BEGIN OF document_descr,
document_name(80),
END OF document_descr.
DATA: ranges TYPE soi_range_list,
contents TYPE soi_generic_table,
cells TYPE soi_cell_table,
rangesdef TYPE soi_dimension_table.

DATA: struc_ranges TYPE soi_range_item,
struc_generic TYPE soi_generic_item,
struc_cells TYPE soi_cell_item,
struc_rangesdef TYPE soi_dimension_item.

DATA: i_descriptions TYPE STANDARD TABLE OF document_descr.
*DATA: ok_code LIKE sy-ucomm.

*——bds:
DATA: obj_bds TYPE REF TO cl_bds_document_set.
* tables and was:
DATA: i_bds_signature TYPE sbdst_signature,
i_bds_signature_2 TYPE sbdst_signature,
wa_bds_signature LIKE LINE OF i_bds_signature,
i_bds_components TYPE sbdst_components,
wa_bds_components LIKE LINE OF i_bds_components,
i_bds_properties TYPE sbdst_properties,
wa_bds_properties LIKE LINE OF i_bds_properties,
i_bds_uris TYPE sbdst_uri,
wa_bds_uris LIKE LINE OF i_bds_uris,
i_bds_mimetype TYPE bapicompon-mimetype.
* Keys:
DATA: s_bds_classname TYPE sbdst_classname VALUE ‘CM_DEMO1′ ,
s_bds_classtype TYPE sbdst_classtype VALUE ‘OT’,
s_bds_object_key TYPE sbdst_object_key VALUE ‘CM100000′,
v_doc_ver_no TYPE bapisignat-doc_ver_no VALUE ’00000001′,
v_doc_var_id TYPE bapisignat-doc_var_id VALUE ’00000001′,
v_doc_count TYPE bapicompon-doc_count,
v_comp_count TYPE bapicompon-comp_count,
v_comp_id TYPE bapicompon-comp_id.

DATA: s_doc_descr(80) VALUE ‘CM document description’,
s_doc_url LIKE bapiuri-uri.
* Dynpro-Fields:
DATA: n_doc_ver_no TYPE i, n_doc_var_id TYPE i, s_doc_var_tg(2),
s_mimetype(128).

*==================================================================
* —–DOI Constants from Type Goup SOI
DATA: s_retcode TYPE soi_ret_string,
document_type TYPE soi_document_type,
document_format TYPE soi_document_type
VALUE soi_docformat_compound.

DATA: h_control TYPE REF TO i_oi_container_control,
h_container TYPE REF TO cl_gui_custom_container,
h_proxy TYPE REF TO i_oi_document_proxy.

DATA: d_excel TYPE REF TO i_oi_spreadsheet,
d_error TYPE REF TO i_oi_error.

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

ZIBDS

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

*&———————————————————————*
*& Form f_display_bds_document
*&———————————————————————*
FORM f_display_bds_document USING value(fu_clsname)
value(fu_clstype)
value(fu_objkey)
value(fu_screen).

s_bds_classname = fu_clsname.
s_bds_classtype = fu_clstype.
s_bds_object_key = fu_objkey.

CALL SCREEN fu_screen.

ENDFORM. ” f_display_bds_document
*&———————————————————————*
*& Module m_status_9000 OUTPUT
*&———————————————————————*
MODULE m_status_bds OUTPUT.

SET PF-STATUS d_screen.
SET TITLEBAR d_screen WITH c_title.

PERFORM f_initilization USING d_container.
PERFORM f_open_document.
PERFORM f_formating_output.

ENDMODULE. ” m_status_bds OUTPUT
*&———————————————————————*
*& Form F_initialization.
*&———————————————————————*
FORM f_open_document.

TYPES: BEGIN OF typeline,
oleline(128) TYPE c,
END OF typeline.

DATA: oletypes TYPE TABLE OF typeline.
DATA: oletype TYPE typeline,
version(10) TYPE c VALUE ‘ ‘.

CLEAR: wa_bds_signature, wa_bds_components, wa_bds_uris, s_doc_descr.
CLEAR: i_bds_signature, i_bds_signature_2, i_bds_components,
i_bds_uris, i_descriptions.

* Availability of document checked
wa_bds_signature-prop_name = ‘DESCRIPTION’.
wa_bds_signature-prop_value = d_doc.
APPEND wa_bds_signature TO i_bds_signature.

CALL METHOD obj_bds->get_info
EXPORTING
classname = s_bds_classname
classtype = s_bds_classtype
object_key = s_bds_object_key
CHANGING
components = i_bds_components
signature = i_bds_signature
EXCEPTIONS
nothing_found = 1
error_kpro = 2
internal_error = 3
parameter_error = 4
not_authorized = 5
not_allowed = 6.

IF sy-subrc NE 0 AND sy-subrc NE 1.
MESSAGE e001(aq) WITH ‘Error in the Business Document Service (BDS)’.
ENDIF.
IF sy-subrc = 1.
MESSAGE e001(aq) WITH ‘There are no documents that meet the search criteria’.
ENDIF.

*_Get Url Address Of Document.
CALL METHOD obj_bds->get_with_url
EXPORTING
classname = s_bds_classname
classtype = s_bds_classtype
object_key = s_bds_object_key
CHANGING
uris = i_bds_uris
signature = i_bds_signature
EXCEPTIONS
nothing_found = 1
error_kpro = 2
internal_error = 3
parameter_error = 4
not_authorized = 5
not_allowed = 6.
IF sy-subrc NE 0 AND sy-subrc NE 1.
MESSAGE e001(aq) WITH ‘Error in the Business Document Service (BDS)’.
ENDIF.
IF sy-subrc = 1.
MESSAGE e001(aq) WITH ‘There are no documents that meet the search criteria’.
ENDIF.

READ TABLE i_bds_uris INTO wa_bds_uris INDEX 1.
READ TABLE i_bds_components INTO wa_bds_components INDEX 1.

i_bds_mimetype = wa_bds_components-mimetype.
s_doc_url = wa_bds_uris-uri.

CASE i_bds_mimetype.
WHEN ‘application/msword’.
document_format = soi_docformat_compound.
WHEN ‘application/vnd.ms-excel’.
document_format = soi_docformat_compound.
WHEN ‘application/vnd.visio’.
document_format = soi_docformat_compound.
WHEN ‘application/x-rtf’ OR ‘text/rtf’.
document_format = soi_docformat_rtf.
WHEN ‘application/x-oleobject’.
document_format = soi_docformat_compound.
WHEN ‘text/plain’.
document_format = soi_docformat_text.
WHEN OTHERS.
document_format = soi_docformat_native.
ENDCASE.

CALL METHOD c_oi_container_control_creator=>mime_to_ole
EXPORTING
mimetype = i_bds_mimetype
version = version
IMPORTING
oletypes = oletypes.
READ TABLE oletypes INTO document_type INDEX 1.

*__Open Document.
CALL METHOD h_control->get_document_proxy
EXPORTING
document_type = document_type
document_format = document_format
IMPORTING
document_proxy = h_proxy
retcode = s_retcode.
IF s_retcode NE c_oi_errors=>ret_ok.
EXIT.
ENDIF.

CALL METHOD h_proxy->open_document
EXPORTING
document_url = s_doc_url
open_inplace = ‘X’
protect_document = ‘X’
IMPORTING
retcode = s_retcode.
IF s_retcode NE c_oi_errors=>ret_ok.
EXIT.
ENDIF.

CALL METHOD h_control->set_focus.

***_Create Interface.
CALL METHOD h_proxy->get_spreadsheet_interface
IMPORTING
sheet_interface = d_excel
retcode = s_retcode.

CALL METHOD c_oi_errors=>show_message
EXPORTING
type = ‘E’.

ENDFORM. “f_open_document

*&———————————————————————*
*& Form F_initialization.
*&———————————————————————*
FORM f_initilization USING value(fu_container).

*__BDS initialization
IF obj_bds IS INITIAL.
CREATE OBJECT obj_bds.
ENDIF.

*__DOI initialization
IF h_control IS INITIAL.
CALL METHOD c_oi_container_control_creator=>get_container_control
IMPORTING
control = h_control
retcode = s_retcode.
CALL METHOD c_oi_errors=>raise_message
EXPORTING
type = ‘E’.
ENDIF.

IF h_container IS INITIAL.
CREATE OBJECT h_container
EXPORTING container_name = fu_container.

CALL METHOD h_control->init_control
EXPORTING
r3_application_name = ‘BDS-DOI’
inplace_enabled = ‘X’
inplace_scroll_documents = ‘X’
parent = h_container
IMPORTING
retcode = s_retcode.

CALL METHOD c_oi_errors=>raise_message
EXPORTING
type = ‘E’.
ENDIF.

ENDFORM. “f_initilization
*&———————————————————————*
*& Form Create_DOI_Document
*&———————————————————————*
* Create a document using the SAP DOI framework
*———————————————————————-*
FORM f_create_doi_document .

PERFORM f_close_doi_document.

CALL METHOD h_control->get_document_proxy
EXPORTING
document_type = document_type
document_format = document_format
IMPORTING
document_proxy = h_proxy
retcode = s_retcode.
IF s_retcode NE c_oi_errors=>ret_ok.
EXIT.
ENDIF.

CALL METHOD h_control->set_focus.

CALL METHOD h_proxy->create_document
EXPORTING
open_inplace = ‘X’
IMPORTING
retcode = s_retcode.
IF s_retcode NE c_oi_errors=>ret_ok.
EXIT.
ENDIF.

CALL METHOD c_oi_container_control_creator=>ole_to_mime
EXPORTING
oletype = document_type
IMPORTING
mimetype = i_bds_mimetype.
* set handler me->on_close_document for proxy.

ENDFORM. ” Create_DOI_Document
*&———————————————————————*
*& Form Close_DOI_Document
*&———————————————————————*
* text
*———————————————————————-*
FORM f_close_doi_document .

IF NOT h_proxy IS INITIAL.
CALL METHOD h_proxy->close_document
EXPORTING
do_save = ”
IMPORTING
retcode = s_retcode.
IF s_retcode NE c_oi_errors=>ret_ok.
EXIT.
ENDIF.

CALL METHOD h_proxy->release_document
IMPORTING
retcode = s_retcode.
* set handler me->on_close_document for proxy activation ‘ ‘.
ELSE.
s_retcode = c_oi_errors=>ret_document_not_open.
ENDIF.
* Force a reinitialization of document interface
CLEAR h_proxy.
ENDFORM. “f_close_doi_document
*
*&———————————————————————*
*& Module m_user_command_9000 INPUT
*&———————————————————————*
MODULE m_user_command_bds INPUT.
CASE sy-ucomm.
WHEN ‘BACK’ OR ‘CANCEL’ OR ‘EXIT’.
PERFORM f_close_doi_document.
IF sy-ucomm = ‘EXIT’ OR sy-ucomm = ‘CANCEL’.
LEAVE PROGRAM.
ELSE.
LEAVE TO SCREEN 0.
ENDIF.
ENDCASE.
ENDMODULE. ” m_user_command_9000 INPUT
*&———————————————————————*
*& Form f_set_content
*&———————————————————————*
FORM f_set_content USING value(fu_col)
value(fu_row)
fu_value.

DATA: ld_value(255).

struc_generic-column = fu_col.
struc_generic-row = fu_row.
WRITE fu_value TO ld_value.
CONDENSE ld_value.
PERFORM f_convert_minus CHANGING ld_value.
struc_generic-value = ld_value.
APPEND struc_generic TO contents.

ENDFORM. ” f_set_content
*&———————————————————————*
*& Form f_formating_def_tab
*&———————————————————————*
FORM f_formating_def_tab.

LOOP AT contents INTO struc_generic.
struc_rangesdef-rows = 1.
struc_rangesdef-columns = 1.
struc_rangesdef-row = struc_generic-row.
struc_rangesdef-column = struc_generic-column.
struc_generic-row = ’1′.
struc_generic-column = ’1′.
MODIFY contents FROM struc_generic INDEX sy-tabix.

APPEND struc_rangesdef TO rangesdef.

ENDLOOP.

ENDFORM. ” f_formating_def_tab
*&———————————————————————*
*& Form f_Replace_words
*&———————————————————————*
FORM f_replace_words .

CALL METHOD d_excel->set_ranges_data
EXPORTING
ranges = ranges
rangesdef = rangesdef
contents = contents
IMPORTING
retcode = s_retcode.

CALL METHOD c_oi_errors=>show_message
EXPORTING
type = ‘I’.

CLEAR : contents, rangesdef, ranges.
REFRESH : contents, rangesdef, ranges.
ENDFORM. ” f_Replace_words
*&———————————————————————*
*& Form f_format_excel_sheet
*&———————————————————————*
FORM f_format_excel_sheet .

CALL METHOD h_proxy->execute_macro
EXPORTING
macro_string = ‘Module1.grid’
IMPORTING
retcode = s_retcode.

CALL METHOD c_oi_errors=>show_message
EXPORTING
type = ‘E’.

CALL METHOD h_proxy->execute_macro
EXPORTING
macro_string = ‘Module1.clear’
IMPORTING
retcode = s_retcode.

CALL METHOD c_oi_errors=>show_message
EXPORTING
type = ‘E’.

ENDFORM. ” f_format_excel_sheet
*&———————————————————————*
*& Form f_convert_minus
*&———————————————————————*
FORM f_convert_minus CHANGING fc_value.

DATA : ld_len TYPE i,
ld_value(50),
ld_min(1).

CLEAR : ld_len, ld_value, ld_min.

ld_len = STRLEN( fc_value ).
ld_len = ld_len – 1.
IF ld_len GE 0.
IF fc_value+ld_len(1) EQ ‘-’.
SPLIT fc_value AT ‘-’ INTO ld_value ld_min.
CONCATENATE ‘-’ ld_value INTO fc_value.
ENDIF.
ENDIF.

ENDFORM. ” f_convert_minus

*&———————————————————————*
*& Form f_create_range
*&———————————————————————*
* Create a range dynamically in excel sheet
*———————————————————————-*
* –>l_top Begin on row
* –>l_left Begin on column
* –>l_row No of rows
* –>l_column No of columns
* –>l_range Range Name
*———————————————————————-*
FORM f_create_range USING l_top TYPE i
l_left TYPE i
l_row TYPE i
l_column TYPE i
l_range TYPE char255.

* Select area for entries to be displayed
CALL METHOD d_excel->set_selection
EXPORTING
top = l_top
left = l_left
rows = l_row
columns = l_column.

* Define Range
CALL METHOD d_excel->insert_range
EXPORTING
name = l_range
rows = l_row
columns = l_column
IMPORTING
error = d_error.

IF d_error->has_failed = abap_true.
CALL METHOD d_error->raise_message
EXPORTING
type = ‘E’.
ENDIF.

ENDFORM. ” f_create_range

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

ZHQUE01F01

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

*&———————————————————————*
*& Form F_GET_DATA
*&———————————————————————*
* text
*———————————————————————-*
* –> p1 text
* <– p2 text
*———————————————————————-*
FORM f_get_data .
FIELD-SYMBOLS: TYPE STANDARD TABLE,
.
DATA: ldy_table TYPE REF TO data,
ldy_line TYPE REF TO data,
ld_table(5) TYPE c,
ld_field(20).

rp-provide-from-last p0000 space pn-begda pn-endda.
CHECK pnp-sw-found = 1.
IF p_all EQ ‘X’.
ELSEIF p_actv EQ ‘X’.
CHECK p0000-stat2 = ’3′.
ELSEIF p_inac EQ ‘X’.
CHECK p0000-stat2 NE ’3′.
ENDIF.

d_date_input = pn-begda.

ld_field = ‘BEGDA’.
LOOP AT t_infotype.
CONCATENATE ‘P’ t_infotype-infty INTO ld_table.
CREATE DATA ldy_table TYPE STANDARD TABLE OF (ld_table)
WITH NON-UNIQUE DEFAULT KEY.
ASSIGN ldy_table->* TO .
CREATE DATA ldy_line LIKE LINE OF .
ASSIGN ldy_line->* TO .
* Read Infotype
CALL FUNCTION ‘HR_READ_INFOTYPE’
EXPORTING
pernr = pernr-pernr
infty = t_infotype-infty
begda = pn-begda
endda = pn-endda
TABLES
infty_tab =
EXCEPTIONS
infty_not_found = 1
OTHERS = 2.
IF sy-subrc 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF NOT [] IS INITIAL.
SORT BY (ld_field) DESCENDING.
READ TABLE INDEX 1 INTO .
PERFORM f_move_corresponding USING t_infotype-infty

CHANGING .
ENDIF.
CLEAR: , ldy_table.
REFRESH: .
ENDLOOP.

******Get Payroll Cluster*******
** check authority reading payroll cluster for Malaysia
AUTHORITY-CHECK OBJECT ‘P_PCLX’
ID ‘RELID’ FIELD ‘RL’
ID ‘AUTHC’ FIELD ‘R’.

IF sy-subrc EQ 0.

CALL FUNCTION ‘Z_SALARY_RETROACTIVE_THISMONTH’
EXPORTING
fi_pernr = pernr-pernr
fi_date = d_date_input
TABLES
ft_data = t_salary
EXCEPTIONS
OTHERS = 1.

PERFORM f_calculate_salary CHANGING .

ENDIF.

******* Put BADI here ********
* break indra.
GET BADI badi_interface
FILTERS
flt_val = d_tcode.

CALL BADI badi_interface->get_data
EXPORTING
flt_val = d_tcode
pernr = pernr-pernr
begda = pn-begda
endda = pn-endda
CHANGING
dyn_table = .
******************************
APPEND TO .
CLEAR .
ENDFORM. ” F_GET_DATA
*&———————————————————————*
*& Form F_LAYOUT
*&———————————————————————*
* text
*———————————————————————-*
* –> p1 text
* p1 text
* <– p2 text
*———————————————————————-*
FORM f_fieldcat .
DATA: lt_lvc_t_fcat TYPE lvc_t_fcat.
DEFINE lm_fieldcat.
t_fieldcat-fieldname = &1.
t_fieldcat-seltext_l = &2.
t_fieldcat-key = &3.
append t_fieldcat.
clear t_fieldcat.
END-OF-DEFINITION.

SORT t_fields BY seqnr.
LOOP AT t_fields INTO x_fields.
IF x_fields-fieldnmpy EQ ”.
IF x_fields-fieldalias EQ ”.
lm_fieldcat x_fields-fieldname x_fields-fieldtext ”.
ELSE.
lm_fieldcat x_fields-fieldalias x_fields-fieldtext ”.
ENDIF.
ELSE.
lm_fieldcat x_fields-fieldnmpy x_fields-fieldtext ”.
ENDIF.
ENDLOOP.

CALL FUNCTION ‘LVC_TRANSFER_FROM_SLIS’
EXPORTING
it_fieldcat_alv = t_fieldcat[]
IMPORTING
et_fieldcat_lvc = lt_lvc_t_fcat
TABLES
it_data =
EXCEPTIONS
it_data_missing = 1
OTHERS = 2.
IF sy-subrc 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

******* Put BADI here ********
* break indra.

GET BADI badi_interface
FILTERS
flt_val = d_tcode.

CALL BADI badi_interface->field_catalog
EXPORTING
flt_val = d_tcode
CHANGING
field_cat = lt_lvc_t_fcat.
******************************

CALL FUNCTION ‘LVC_TRANSFER_TO_SLIS’
EXPORTING
it_fieldcat_lvc = lt_lvc_t_fcat
IMPORTING
et_fieldcat_alv = t_fieldcat[]
EXCEPTIONS
it_data_missing = 1
it_fieldcat_lvc_missing = 2
OTHERS = 3.
IF sy-subrc 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. ” F_FIELDCAT
*&———————————————————————*
*& Form F_DISPLAY_ALV
*&———————————————————————*
* text
*———————————————————————-*
* –> p1 text
* <– p2 text
*———————————————————————-*
FORM f_display_alv .
CALL FUNCTION ‘REUSE_ALV_GRID_DISPLAY’
EXPORTING
i_callback_program = sy-repid
is_layout = x_layout
i_callback_pf_status_set = ‘SET_PF_STATUS’
i_callback_user_command = ‘F_USER_COMMAND’
i_callback_top_of_page = ‘F_TOP_OF_PAGE’
it_fieldcat = t_fieldcat[]
i_save = ‘X’
is_variant = x_alv_varnt
* i_grid_title = lv_header
TABLES
t_outtab =
EXCEPTIONS
program_error = 1
OTHERS = 2.
IF sy-subrc 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM. ” F_DISPLAY_ALV

**&———————————————————————*
**& Form set_pf_status
**&———————————————————————*
FORM set_pf_status USING fu_rt_extab TYPE slis_t_extab.
DATA ld_extab TYPE LINE OF slis_t_extab.
SET PF-STATUS ‘STANDARD’ EXCLUDING fu_rt_extab.
ENDFORM. ” set_pf_status

*&———————————————————————*
*& Form USER_COMMAND
*&———————————————————————*
FORM f_user_command USING fu_ucomm LIKE sy-ucomm
fu_selfield TYPE slis_selfield.
DATA ld_ans(1).

CASE fu_ucomm.
WHEN ‘&IC1′.
CASE fu_selfield-sel_tab_field.
WHEN ‘T_DATA-FIELD’.
ENDCASE.
WHEN ‘DOWN’.
PERFORM f_download_excel.
WHEN ‘&F03′ OR ‘&F15 ‘ OR ‘&F12′.
LEAVE TO SCREEN 0.
ENDCASE.
fu_selfield-re

Future Proof UI Declaration

Browser, Web Dynpro Client, Mobile Device,…

Client technology independent meta data

Central implementation of user interface standards

Accessibility support

Adobe Forms integration

Centrally provided UI elements

Internationalization support

Supports major platforms

Java (NetWeaver 2004), ABAP (NetWeaver 2004s)

You can see slide show from SAP at download link below.

Download

The following concepts are defined in ABAP HR which is different with other modules.

- Use of Infotypes
- The use of Logical Database
- Use of Macros and Provide statement
- Storage and Access of data
- Authorization checks

There is nothing much difference between abap and hr abap. The way we retrieve the data from data base is deferent.

In general ABAP data is stored in Tables, but coming to HR ABAP employee data is sorted through Infotypes. The way we retrieve the data from infotypes is deferent in hr abap.

In general ABAP we use Logical data base very rare, as in HR ABAP most of the programs use Logical data base to select data from Infotypes by using Get event.

In ABAP we use read statement to read particular record, still in HR ABAP we do use read statement apart from that we have Macros and provide statement.

Macro is pre defined code (like function module) which reads data from internal table (internal infotype) based on dates.

Provide statement is like Select statement but selects data from internal table

Storage and access of data in hr abap is completely deferent in hr abap comparing with ABAP. We use transaction code PA20 and PA30 to maintain data in infotypes.

PA20 is display mode and PA30 is change mode. We can create, change, display, copy, and delete in infotypes with PA30 transaction.

For Infotypes authorizations can be maintained infotype and subtype (field) level as HR data is more sensitive and secrete.

http://abaphr.com/?p=231

The following is the overview; we’ll go over each step in detail afterwards:

1. Sketch It: Napkins are great! I usually use the other side of a recycled piece of photocopied paper—the more basic the better. No fine artist skills required! Perk: Using this sketch you can not only get your graphic interface ideas down, but you can already start to think about how the user will interact with your theme design and re-sketch any new ideas or
changes accordingly.
2. Start with the Structure: I create an ideal, un-styled semantic XHTML document structure and attach a bare bones CSS sheet to it.
3. Add the Text: Lots of text, the more the better! A sample of actual content is best, but Lorem Ipsum is fine too.
4. CSS Typography: Think of your Typography and assign your decisions to the stylesheet. Review! Don’t like how the formatted text looks in-line? Being separated into columns with fancy background graphics won’t make it any better. Get your text to look nice and read well now before moving on to layout.
5. CSS Layout: Set up the Layout—this is where you’ll see upfront if your layout idea from your sketch will even work. Any problems here and you can re-think the design’s layout into something more realistic (and usually more clean and elegant). Perk: Your client will never see, much less become attached to, a layout that would cause you problems down the road in CSS.
6. CSS Color Scheme: Assign your color scheme basics to the CSS. We’re close to needing Photoshop anyway, so you might as well open it up. I sometimes find it useful to use Photoshop to help me come up with a color scheme and get the hex numbers for the stylesheet.
7. Take a Screenshot: Time for Photoshop! Paste the screenshot of your basic layout into your Photoshop file.
8. Photoshop: Have fun creating the graphical interface elements that will be applied to this layout over your screenshot.
9. Send for Approval: Export a .jpg or .png format of the layout and send it to the client. Perk: If the client has text changes, just make them in your CSS (which will update your text globally—no layer hunting for all your headers or links, etc.) and resnap a screenshot to place back in the Photoshop file with the graphic elements. If they have a graphical interface change, well that’s what Photoshop does best! Make the changes and resend for approval.
10. Production: Here’s the best part; you’re more than halfway there! Slice and export the interface elements you created over (or under) your screenshot and apply them with the background image rules in your CSS. Because you worked directly over a screenshot of the layout, slicing the images to the correct size is easier and you won’t discover that you need to tweak the layout of the CSS as much to accommodate the graphic elements.

Reference: WordPress Theme Design by Tessa Blakeley Silver (Page 22)

Create new program using SE 38. You may create as temporary program, or transported program based on your environment policy. Then apply the code below. Execute and find user exit based on TCode. Have a nice try.

*&———————————————————————*
*& Report  ZFIND_USER_EXIT
*&
*&———————————————————————*
*&
*&
*&———————————————————————*

REPORT  ZFIND_USER_EXIT no standard page heading.
tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
tables : tstct.
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
parameters : p_tcode like tstc-tcode obligatory.

select single * from tstc where tcode eq p_tcode.
if sy-subrc eq 0.
select single * from tadir where pgmid = ‘R3TR’
and object = ‘PROG’
and obj_name = tstc-pgmna.
move : tadir-devclass to v_devclass.
if sy-subrc ne 0.
select single * from trdir where name = tstc-pgmna.
if trdir-subc eq ‘F’.
select single * from tfdir where pname = tstc-pgmna.
select single * from enlfdir where funcname =
tfdir-funcname.
select single * from tadir where pgmid = ‘R3TR’
and object = ‘FUGR’
and obj_name eq enlfdir-area.

move : tadir-devclass to v_devclass.
endif.
endif.
select * from tadir into table jtab
where pgmid = ‘R3TR’
and object = ‘SMOD’
and devclass = v_devclass.
select single * from tstct where sprsl eq sy-langu and
tcode eq p_tcode.
format color col_positive intensified off.
write:/(19) ‘Transaction Code – ‘,
20(20) p_tcode,
45(50) tstct-ttext.
skip.
if not jtab[] is initial.
write:/(95) sy-uline.
format color col_heading intensified on.
write:/1 sy-vline,
2 ‘Exit Name’,
21 sy-vline ,
22 ‘Description’,
95 sy-vline.
write:/(95) sy-uline.
loop at jtab.
select single * from modsapt
where sprsl = sy-langu and
name = jtab-obj_name.
format color col_normal intensified off.
write:/1 sy-vline,
2 jtab-obj_name hotspot on,
21 sy-vline ,
22 modsapt-modtext,
95 sy-vline.
endloop.
write:/(95) sy-uline.
describe table jtab.
skip.
format color col_total intensified on.
write:/ ‘No of Exits:’ , sy-tfill.
else.
format color col_negative intensified on.
write:/(95) ‘No User Exit exists’.
endif.
else.
format color col_negative intensified on.
write:/(95) ‘Transaction Code Does Not Exist’.
endif.

at line-selection.
get cursor field field1.
check field1(4) eq ‘JTAB’.
set parameter id ‘MON’ field sy-lisel+1(10).
call transaction ‘SMOD’ and skip first   screen.

*—End of Program

Introduction

Many people ask where they can find data in their SAP system. Because SAP is so often highly customised, the best

answer is “Ask your SAP system itself” Which leads on to the question “How do I do that?”
Steps

If you do not know the transaction code in which the data is used: then use the Data Dictionary tables, in

particular, DD02L and DD02T. Accounts Payable. See examples below.

If you do know any transaction in which (related) data is used: 1) start the transaction 2) position the cursor on

the field you want to have info about 3) press F1, then F9 4) now you see the technical information of the data

element, such as table name and field name. 5) if the table mentioned is what you’re looking for, you’re done. It is

also possible that the data element is in a structure and not in a table. Now you can either analyze the structure

via trx SE11, or you can double click on the ‘data element’ field. In the next screen, use the ‘Where used’ button

to find the tables in which this data element is used.

Additional tip: if you have found the table name, you can use trx SE36 or SLDB or ALDD ( also u can click on the

help u will get information about logical data base tables)to see the relationships of this table to other tables.

You can use these relationships when defining queries, designing custom ABAP programs, etc. If you’re lucky, one or

more standard SAP logical database exist which contain the table you found in the previous steps. Proceed as

follows: 1) start trx SE36 2) use the search help for the logical database name 3) enter the name of the table in

the search help 4) press enter and, if you’re lucky, you’ll see a list of logical databases. Select one, press

enter, select the radio button ‘Structure’ and press the view button. Now you’ll see how this table is related to

other tables.
[edit]
Examples

The following is a (theorectically) complete ABAP dic list.

DD0102V | Generated table for view DD0102V |

DD01D | Dynpro fields for domain |

DD01L | Domains |

DD01LV | Generated table for view DD01LV |

DD01T | R/3 DD: domain texts |

DD01TV | Versioning: foreign languages for domains |

DD01V | Generated table for view DD01V |

DD01VD | Version display: Domain |

DD01VV | Generated table for view DD01VV |

DD01V_OLD | DD01V with old names |

DD02ALL | Table Parameters for ALLBASE |

DD02D | Screen Fields for Table |

DD02DB2 | DB2/390: Table Parameters |

DD02DB6 | Table Parameters for DB2 Version 2 |

DD02INF | Table Parameters for INFORMIX, Version 6 |

DD02L | SAP tables |

DD02MSS | Table Parameters for Microsoft SQL Server |

DD02ORA | Table parameters for ORACLE, version 6 |

DD02SYB | Storage Parameters for Tables in SYBASE |

DD02T | R/3 DD: SAP table texts |

DD02TV | Versioning: foreign languages for tables |

DD02V | Generated table for view DD02V |

DD02VD | Version display: table header |

DD02VV | Generated table for view DD02VV |

DD02V_OLD | DD02V with old names |

DD03D | Dynpro fields for table fields |

DD03K | Generated table for view DD03K |

DD03L | Table Fields |

DD03L_F | BAPI field names for update |

DD03M | Generated table for view DD03M |

DD03MI | Index structure for view DD03M |

DD03N | Generated table for view DD03N |

DD03P | Structure |

DD03P_D | Dictionary Maintenance: Attributes of Structure Fields |

DD03T | DD: Texts for fields (language dependent) |

DD03TV | Versioning: foreign languages for fields |

DD03V | Table fields view |

DD03VT | Generated Table for View DD03VT |

DD03VV | Generated Table for View DD03VV |

DD04D | Dynpro fields for Data Element |

DD04L | Data elements |

DD04T | R/3 DD: Data element texts |

DD04TV | Versioning: foreign languages for data elements |

DD04V | Generated Table for View DD04V |

DD04VD | Version display: Data element |

DD04VV | Generated table for view DD04VV |

DD04VVL | Generated table for view DD04VVL |

DD04VVT | Generated table for view DD04VVT |

DD05M | Interface Structure for DD_TBFK_GET |

DD05P | Generated Table for the View DD05P |

DD05Q | Generated Table for the View DD05Q |

DD05S | Foreign key fields |

DD05V | View on foreign key fields |

DD05VD | Version display: Foreign key fields |

DD06D | Screen fields for SQL table |

DD06L | Pool/cluster structures |

DD06T | R/3 DD: texts on SQL tables |

DD06TV | Versioning: foreign languages for SQL tables |

DD06V | Generated table for view DD06V |

DD06VD | Version display: SQL table |

DD06VV | Generated table for view DD06VV |

DD07D | Screen fields for domain values |

DD07L | R/3 DD: values for the domains |

DD07T | DD: Texts for Domain Fixed Values (Language-Dependent) |

DD07TV | Versioning: foreign languages for domain fixed values |

DD07V | Generated Table for View DD07V |

DD07VD | Version display: Domain fixed values |

DD07VT | DD: Temp. Replacement Structure for VIEW DD07TV |

DD08D | Screen Fields for Foreign Keys |

DD08L | R/3 DD: relationship definitions |

DD08T | Texts on the relationship definitions |

DD08TV | Texts on the relationship definitions |

DD08V | Generated table for view DD08V |

DD08VD | Version display: foreign key |

DD08VV | Generated table for view DD08VV |

DD08VVT | Generated table for view DD08VVT |

DD092526V | Generated table for view DD092526V |

DD09C | ABAP/4: Sytem-dependent attributes of tech. settings |

DD09L | DD: Technical settings of tables |

DD09V | Interface: Technical Settings Table/View |

DD09VD | Version display: Technical settings |

DD09VV | Generated table for View DD09VV |

DD09VVT | Generated table for view DD09VVT |

DD10L | Lock table for DD activation |

DD12D | Screen fields for index maintenance |

DD12DB2 | DB2/390: Index Parameters |

DD12DB6 | Index Parameters for DB2 Universal Database Version 2 |

DD12INF | Index parameter for INFORMIX |

DD12L | R/3 S_SECINDEX: secondary indexes, header; |

DD12MSS | Index Parameters for MS SQL Server |

DD12ORA | Index Parameters for ORACLE |

DD12SYB | Index Parameters for SYBASE System_10 |

DD12T | Text Table for DD12L (Short Descriptions of Sec. Indexes) |

DD12TV | Versioning: foreign languages for secondary indexes |

DD12V | Generated Table for View DD12V |

DD12VD | Version display: index |

DD12VVT | ABAP/4 Repository Information System: Index work structure |

DD14S | R/3 DD: components of SAP objects |

DD14V | R/3 DD: view on SAP object structure |

DD15L | R/3 DD: SAP objects |

DD15T | R/3 DD: texts on SAP objects |

DD15V | R/3 DD: view on SAP objects |

DD16D | Screen fields for SQL table fields |

DD16S | R/3 DD: SQL table fields |

DD16V | Generated table for view DD16V |

DD16VD | Version display: Fields of SQL tables |

DD17S | R/3 S_SECINDEX: secondary indexes, fields |

DD17V | Secondary index fields with language key |

DD20L | Matchcode objects |

DD20T | AS400-T_MCOBJECT: MC Object Texts |

DD20TV | AS400-T_MCOBJECT: MC Object Texts |

DD20V | Generated table for DD20V view |

DD20VD | Version display: matchcode objects |

DD20VVT | Generated table for view DD20VVT |

DD21S | S-MCIDTABLE: Tables for a MC ID |

DD21V | V-MCIDTABLE: View of Tables for a MC ID |

DD21V_VAR1 | Special View on DD21V Tailored to Matchcode ID Generation |

DD22V | Generated table for view DD22V |

DD22VD | Version display: Lock object header |

DD23H | Generated table for view DD23H |

DD23L | Matchcode ID |

DD23LS | Generated table for View DD23LS |

DD23T | AS400_L-MCID: Matchcode ID Texts |

DD23TV | Versioning: foreign languages for matchcode IDs |

DD23V | Generated table for view DD23V |

DD23VD | Matchcode ID |

DD23VVT | Generated table for view DD23VVT |

DD24A | Generated table for view DD24A |

DD24H | Help System View on Fields of a MC ID |

DD24S | Fields of a matchcode ID |

DD24V | S-MCIDFIELD: View of MC ID Fields |

DD2526V | Generated table for view DD2526V |

DD25D | Screen fields for view |

DD25L | Aggregate Header (Views, MC Objects, Lock Objects) |

DD25LS | Generated table for view DD25LS |

DD25T | Short Texts for Views and Lock Objects |

DD25TV | Versioning: foreign languages for views and lock objects |

DD25V | Generated table for view DD25V |

DD25VD | Version display: View header |

DD25VV | Generated table for view DD25VV |

DD25VVT | Generated table for view DD25VVT |

DD25Z | Assignment of superview to subview – no longer required – |

DD26D | Screen fields for lock object maintenance |

DD26E | Interface Structure for Base Tables of a Lock Object |

DD26EVD | Version display: base tables of a lock object |

DD26I | Generated table for view DD26I |

DD26S | Base tables and foreign key relationships for a view |

DD26V | V-VIEWTABLE: View of Base Tables of a View |

DD26VD | Version display: Base tables |

DD27D | Screen fields for view fields |

DD27I | Generated table for view DD27I |

DD27M | Generated table for view DD27M |

DD27P | View of Fields in an SAP Table View |

DD27S | Fields in an Aggregate (View, MC Object, Lock Object) |

DD27SV | Generated table for view DD27SV |

DD27V | V-VIEWFIELD: View of Fields in an SAP View |

DD27VD | Version display: View fields, lock arguments, matchcode fld. |

DD27VV | Generated table for view DD27VV |

DD27VVT | Generated table for view DD27VVT |

DD27VVTSTR | Repository Infosystem: Structure via DD27VVT: View fields |

DD28J | Internal structure for joins of views |

DD28JVD | Version display: Joins of views |

DD28S | Lines of a selection condition |

DD28V | View on a Selection Condition |

DD28VD | Version display: Selection conditions |

DD29L | Selection Condition for Views and MC IDs |

DD29T | AS400_L-SELCOND: Selection Condition Texts |

DD29V | V-SELCOND: View on Header for a Selection Condition |

DD30L | Search helps |

DD30T | Search help texts |

DD30TV | Versioning: foreign languages for search helps |

DD30V | Generated table for view DD30V |

DD30VD | Version Display: General Attributes of Search Helps |

DD30VV | Generated table for view DD30VV |

DD31D | Search help inclusions with texts of included |

DD31S | Assignment of search helps to collective search helps |

DD31V | Assignment of search helps to collective search helps |

DD32P | Interface structure for search help parameters |

DD32S | Search Help Parameter |

DD32V | Search help fields |

DD32VD | Search help fields |

DD33S | Assignment of search help fields |

DD33V | Assignment of search help parameters for srch help inclusion |

DD35L | Search help attachments to structures: Headers |

DD35V | Assignment of structure fields and search helps: Headers |

DD35VD | Version display: search help attachm. to structures: header |

DD35VV | Generated table for view DD35VV |

DD36M | Interface structure for field assignments table-search help |

DD36Q | Generated table for view DD36Q |

DD36S | Parameter-field assignments for search help attachment |

DD36V | Assignment of structure fields and search helps: Fields |

DD36VD | Version display: parameter-field assignm. for s.h. attachm. |

DD40D | Screen Fields for Table Types |

DD40L | Table types (internal tables defined in DD) |

DD40T | Text on table types |

DD40TV | Versioning: foreign languages for table types |

DD40V | DD: Interface structure for table types |

DD40VD | Version display: table types |

DD40VV | Generated table for view DD40VV |

DD41V | Generated table for view DD41V |

DD42S | Key fields for table types (internal tab. defined in DD) |

DD42V | DD: Interface structure for table type key fields (TTKF) |

DD42VD | Version display: table type key fields (TTKF) |

DD42V_EXT | DD: Key Field of a Table Incl. Further Information |

DD50D | Screen Fields for Type Groups |

DD51D | Screen Fields for Lock Objects (Same Fields: DD25D Views) |

DD52D | Interface Structure for Base Tables of a Lock Object |

DD53D | Screen Fields for Lock Object Fields |

DD90L | Header Information for External Index |

DD90T | R/3-DD: Text for External Index |

DD90V | Generated Table for View DD90V |

DD91S | DocID Key Definition of External Index |

DD91V | DocID Key Definition of External Index |

DD92S | Mapping of R/3 Data on External Index |

DD92V | Mapping of R/3 Data on External Index |

DD93S | Attribute of an External Index |

DD93V | Attribute of an External Index |

DD94S | Languages of an Index Category |

DD94V | Languages of an Index Category |

DD96S | Synchronization Tables |

DD96V | Synchronization Tables of an External Index |

DD97S | Statements for Trigger and Stored Procedures |

DDACL | Exclusion times for ABAP/4 Dictionary actions |

DDACTIONS | DD: Structure for display ACTION -> text |

DDACTRES | DD: Activation result incl. dependent propagation |

DDALIAS | DD: Second name for accessing tables |

DDALTER | Information about Reasons for ALTER TABLE |

DDAPPSRC | SE11: Append origin of for. keys and src. help attachments |

DDART | DD: Data Class in Technical Settings |

DDATCHK | Field structure for screen 100 RUTATCHK |

DDAUTHCTRL | Control structure for authorization checks |

DDAUTHTAB | ABAP/4: database actions and flag if this is permitted |

DDBOOK | Output control table manual |

DDBOOL | Reference Structure for Interfaces |

DDBTCMPTIT | Column information for comparison of repeat groups |

DDBT_CFLD | Description of a non-elementary component of a structure |

DDBT_DATA | Information about a component of a complex data object |

DDBT_DATD | Type for packing complex data |

DDBT_FDDES | Type and position of contents of a field |

DDBT_FLD | Information about an elementary component |

DDBT_STDEF | Description of a structured type |

DDBUF | DD: For transferring the new buffering parameters |

DDBYTE | DD: X-fields for each bit of a byte |

DDB_AST | Table Structure for Author. Segm. Trigger |

DDB_AW | Configuration Transac. Data: Fact for Simple Characteristic |

DDB_AZW | Configuration Transaction Data: Fact for Restrictable Char. |

DDB_C00 | Transaction Data: DDDB_HAS_INST |

DDB_C01 | Transaction Data: DDDB_HAS_VAL |

DDB_C02 | DDB Change Messages (Configuration) |

DDB_C03 | Configuration Transac. Data: General Value Set |

DDB_C04 | Value Structure for Reading Characteristic Values from DDB |

DDB_C05 | Presentation Messages for DDB Instances |

DDB_C06 | Describes a characteristic value, as in priority tables |

DDB_C07 | Price Factors for Variant Conditions |

DDB_ITP | DDB: General Object Type |

DDB_PO | Part-of Structure in Configuration (DDB) |

DDB_TO | DDB Configuration: TYPE_OF-Fakt |

DDCACHE | DD: Control String for Read Routines |

DDCCOND | Conditions for Status Switch during Conversion |

DDCCURRSTA | DD: Conversion, statistics, intermediate values |

DDCDIM | DD: Conversion, number of table lines |

DDCHKMESS | ABAP/4 Dict.: contains messages for NA checks |

DDCHK_CNT | DD: Mass Check Statistics Counter |

DDCHK_CTRL | DD: Parameter for (Parallel) Mass Check Program |

DDCLASSES | DD: Structure for mapping CLASS -> text |

DDCLAUSE | SQL clause |

DDCLIENT | Structure for Clients |

DDCNODE | DD: Nodes in Status Graphs of Conversion |

DDCNV | Information why Conversion |

DDCNVBODY | DD: Definition of conversion steps – local attribute |

DDCNVCTRL | DD: Structure for parameters of ICNV |

DDCNVDEFS | DD: Definition of Conversion Steps |

DDCNVEXIT | DD: External conversion methods |

DDCNVKEY | Definition of Conversion Scenario – Key |

DDCNVOPT | Stsructure for Conversion Options |

DDCNVREF | DD: Reference structure for conversion requirements |

DDCNVRESS | DD: Structure for results of FB DD_ICNV_UPGRADE |

DDCNVSTAT | DD: Statistical Data for Conversion |

DDCNVTABL | DD: Contains incr. conv. tables depend. on release/component |

DDCNVTIMES | DD: Exclusion times for conversion |

DDCNVUPGR | DD: Control structure for ICNV steps during upgrade |

DDCNVUSR | DD: Exception table of converter |

DDCOMPARE | Return from generic comparison tool: RS_VERS_COMPARE_TAB |

DDCOMTOTAB | Comment on the Table Rows |

DDCON | Condition for IN operator |

DDCONH | Storage Parameter (condition) |

DDCPRO | DD: Conversion projects |

DDCPROGRES | DD: Conversion, statistics, intermediate values |

DDCPROT | DD: Text on conversion projects |

DDCPROTAB | DD: Table for conversion projects |

DDCPYSTAT | DD: Statistics data for table copy |

DDCQUEUE | DD: Queue for CNV Operations |

DDCSCANSTA | DD: Conversion, scan history |

DDCSTA | DD: Conversion, number of table lines |

DDCSTAT | DD: Statistics table for conversions |

DDCSTAT_I | DD: Statistics Data for Conversions |

DDCSTAT_K | DD: Statistics Data for Conversions – Key Part |

DDCSTAT_T | DD: Statistics Data for Conversions |

DDCT_TYPE | Type Information for LOW and High of a Range Type |

DDCURSOR | DD: Reference structure for cursor area |

DDCVERTIC | Link of Status Graph of Conversion Program |

DDDBOPERA | Virtual table of outstanding DB operations |

DDDBOPS | Virtual table of outstanding DB operations |

DDDBSPACE | Structure for DBSpaces/Tablespaces |

DDDBUTMREQ | Interface for mass processing requests |

DDDBUTREFS | DD: Database utility reference fields |

DDDECIDE | Information about Structure Changes to DB Objects |

DDDEPDESCR | Internal Description of a Dependent Object |

DDDEPRES | DD: result of handling of dependent objects |

DDDEPTAB | DD: Dependencies Sorted By Dependent Objects |

DDDOACTRES | DD: Status of domains (activation result) |

DDDOMSTATE | DD: Status of domains |

DDDOSTATE | Status of Objects |

DDDTRENUPG | DD: Table for Renaming Data Elements During Upgrade |

DDDTSTATE | DD: Status of Data Elements |

DDENA | Lock argument fields |

DDENQS | Lock object structure for Dictionary objects (inc. index) |

DDENQ_LIKE | Ref. Fields for Parameters of the ENQUEUE Function Module |

DDERR | R/3 DDIC: Error Code From Modules |

DDERR_O | Return code structure in consistency layer of the DD |

DDEXTIDXS2 | DocID Key Definition of External Index |

DDEXTIDXS3 | Mapping of R/3 Data on External Index |

DDEXTIDXS4 | Attribute of an External Index |

DDEXTIDXS5 | Synchronization Tables with Stored Proc. for External Index |

DDF4ATTRVA | Document Attribute with Value for Indexing/De-indexing |

DDF4DBTRIG | Tables and Triggers |

DDF4EXIXS3 | Mapping of R/3 Data on External Index |

DDF4IDCTRL | Control Structure for Data Selection for an External Index |

DDF4IDPROT | Structure for Log Table for Updating External Indexes |

DDF4IDXCON | Document Contents for External Index |

DDF4KEYTAB | Key for Selection Module / Search Engines |

DDF4LBBUF1 | List Box Buffer: GUID and Time Stamp for a Table |

DDF4PSALLS | Structure for General Personalization of Search Helps |

DDF4PSINDX | Contains Information for Personalizing the F4 Help |

DDF4SEKEYS | Structure for Document Key of Log Table |

DDF4SERFC | RFC Destinations of a Search Server Relation |

DDF4SYNCIV | Synchronization Interval for External Index |

DDF4TRACE | INDX Structure for Holding F4 Trace (List Box) |

DDF4TRADAT | Data to be Stored in DDF4TRACE |

DDF4TRIGTR | Structure for Tree Representation of DB Trigger |

DDFIELD | DB-relevant description of DD table fields |

DDFIXVALUE | Description of a Fixed Value |

DDFKEYRC | DD: Message numbers for foreign key violations |

DDFLDNAM | Name of a DD table field |

DDFLDSPATH | DD: field information and field name with entire path |

DDFLG1 | Flag byte 1 of nametab for field attributes |

DDFLG2 | Flag byte 2 in nametab for field attributes |

DDFLG3 | Flag Byte 3 of Nametab for Field Attributes |

DDFLG4 | Flag byte 4 of nametab for field attributes? |

DDFLGBYTE | Table attributes in nametab header |

DDFTX | Run-time object with Screen Painter texts |

DDFTYP | DD: Structure to test fields without data elements |

DDGENTAB | DD: Structure of Gentab (Mass Activation Program) |

DDGR_NAME | DD: Names of DD objects for graphic algorithms |

DDGR_OBJ | DD: Object lists for graphic algorithms |

DDGR_REL | DD: Relations list for graphic algorithms |

DDGR_RELIX | DD: Relation over object index for graphic algorithms |

DDHDFLG3 | DD: Header flag 3 expanded |

DDHDFLG4 | DD: Header flag 4 expanded |

DDHDFLG5 | DD: Header flag 5 expanded |

DDHDFLG6 | DD: Header flag 6 expanded |

DDHELPSTRT | Table Fields for Reference |

DDICNVCHE | DD: Condition variables for incremental conversion |

DDICNVCTRL | Control String for Transaction ICNV |

DDICNVDAYS | DD: Days of Week |

DDICNVDIST | Distribution of data records of base tables |

DDICNVENQ | DD: Structure to lock the ICNV |

DDICNVLST | Contains information on converter exits |

DDICNVMON | DD: Structure for ICNV monitor |

DDICNVPREP | DD: Control Structure for ICNV in Upgrade |

DDICNVPROS | Process information for incremental conversion |

DDICNVREF | Reference structure for interfaces of ICNV |

DDICNVRES | DD: Results of ICNV Checks in Upgrade |

DDICNVUPGR | DD: ICNV Control for Upgrade Phase PREPARE |

DDIDELCHK | Control String for Check Whether Fields May Be Deleted |

DDIKEYCHK | Control String for Checking the Key |

DDILTYCHK | Control String for Checking Long Fields |

DDINDEX | Information for indexes |

DDINDXACT | Information what kind of Index is Required in DB |

DDINFO | DD: Info Part of the Navigation Table for DD Objects |

DDINNUCHK | Control String for Checking NOT NULL Flags |

DDIPCLCHK | Control String for Table Type Test with Pool/Cluster |

DDIPOOCHK | Control String for Additional Tests for Pooled Table |

DDIREFCHK | Control String for Checking Reference Fields |

DDIREL | Relation Source and Target Tables in the ICNV |

DDISAACHK | Control String for Checking Fields for SAA Standard |

DDISAHCHK | Control String for Checking Header for SAA Standard |

DDITANCHK | Control String for Table Name Tests (Except SAA) |

DDITEHCHK | Control String for Checking DD02L <-> DD09L/Header Checks |

DDITESCHK | Control String for Checking DD02L <-> DD09L/Field Checks |

DDIVAHCHK | Control String for Checking the Fixed Values (Header) |

DDIVALCHK | Control String for Checking the Fixed Values (Fields) |

DDKONTEXT | Context of DD Maintenance |

DDLBBUFTST | Test: Recognize Access to Buffered Tables |

DDLCH | Logical Channel Info from the R/3 Repos. – Standard Version |

DDLOAD | DD: Reference structure for loading/unloading tables |

DDLOADD | R3load-data table for migration |

DDLOADH | R3load-header table for migration |

DDLOGDEF | DD: Formal definition of log and trace output |

DDLREF | Log Reference in Dictionary – Standard Output |

DDMASS | DD: Structure for mass activator parameters |

DDMASSAC | DD: Control operations for DD objects during mass activation |

DDMASSCTRL | DD: Control Input Par. for DD_MASS_ACT_PARALLEL |

DDMASSTST | DD: Control Structure for Test Mode Mass Activation Program |

DDMATASKCT | DD: Control Parameter for Mass Act. for Each Task |

DDMESS | Message in non-expanded form |

DDMSACTRC | DD: Return Information about Activation |

DDMSCHK | Structure for screen variables of mass checks |

DDMSG | DD: Structure for Messages |

DDMUTEX | DD: Table for implementing reciprocal exclusions |

DDNAMECONF | Return structure for function module DD_NAME_CONFLICT_AREA |

DDNAMES | Structure for Dictionary Checks |

DDNAMETAB | Structure for Display Nametab |

DDNMB | DD: Data records per extent (minimum/maximum number) |

DDNTFLAG | Structure for Explaining Nametab Flags |

DDNTHEADER | Structure for Nametab Header |

DDNTHIST | DD: history nametabs in time interval |

DDNTSACT | DD: Possible actions on nametab byte |

DDNTTHISTS | Nametab history: table information on DB table DDNTT_HIST |

DDNUMFVAL | DD: Structure for numeric fixed values |

DDOBJ | DD: Name of an ABAP Dictionary object |

DDOBJCLASS | Classification of ABAP Dictionary objects |

DDOBJCOST | DD: Relative costs per DD object type |

DDOBJDIR | DD: Structure for Objects in Mass Checks |

DDOBJKEY | DD: Key of DD Objects (Type Name) |

DDOBJPOS | DD: Position of an object |

DDOBJTEXT | Dictionary Objects: Texts |

DDOCC | Occurrence of Table/Field in Aggregates or as Reference |

DDOP | DD: Specification of DDL Operations |

DDOPADMIN | DD: Management Information on an DD/DB Operation |

DDOPER | Lock arguments for DD processes |

DDOPKEY | DD: Key of a DD/DB Operation |

DDOPOBJ | DD: Object on which a DD/DB Operation is Performed |

DDOPTIME | DD: Time of a DD/DB Operation |

DDPAMSCTRL | DD: Controls Parallel Handling during Mass Activation |

DDPAR | R/3 Dict: table of internal parameters |

DDPARLIST | Control structure for outputting parameter values |

DDPART | DD: Partitioned form of TBATG |

DDPARTKEY | DD: Global attributes of table DDPART |

DDPATH | DD: Definition of access paths |

DDPCH | Physical Channel Info from the R3/Repos. – Standard Version |

DDPOPUPT2F | DD: Description of a dialog box with 2 columns and 1 flag |

DDPRH | R/3 DD: Log header |

DDPRH_ALV | Structure for DDPRH for Display with ALV Grid |

DDPRID | DD: Representation of a list of log IDs |

DDPRLOCK | DD: Lock granularity for standard output |

DDPRMASQUE | DD: Mask for overlaying a log line |

DDPROF | DD: Settings for DDIC programs |

DDPROPVAL | DD: Attribute value pairs |

DDPROTOBJ | DD: Object Table for Log Entries in DDPRH, DDPRS |

DDPRS | R/3 DD: log lines |

DDPRT | Structure of ABAP/4 Dictionary logs |

DDPRTENQ | Control string: print lock objects |

DDPRTGEN | Interface: general print options |

DDPRTLIST | Input list for printing DD objects |

DDPRTMC | Control string: print option for matchcodes |

DDPRTPARA | Parameter for print editing |

DDPRTSHLP | Control string: print options for search helps |

DDPRTTAB | Control string: print options for tables |

DDPRTUVAR | User settings for printing DD objects |

DDPRTVIEW | Control string: print options for views |

DDPRTXT | R/3 DD: Log texts |

DDPRT_FRM | Format Definitions for Printing Dictionary Objects |

DDPRT_I | Interface for ABAP/4 Dictionary logger |

DDRANGE | Reference structure for ranges in the ABAP Dictionary |

DDREF | Table/Field and Associated Reference Table/Field |

DDREFSTRUC | DD: General Reference Structure in ABAP Dictionary |

DDREFTAB | ABAP/4 D: Dependencies Sorted by Referenced Objects |

DDRELSTRUC | DD: Relationships between DD objects |

DDRELTAB | DD Dict.: structure for relations |

DDSCR | DD Interface: View of Field Attributes in the Nametab |

DDSECHKKEY | Structure for Comparing Definition of Log Table |

DDSECHKPRT | Log Display Admin. Search Index |

DDSERVERIF | DD: Info for Application Server for Parallel Processing |

DDSERVPERF | DD: Performance Key Figures of Server for Par. Execution |

DDSESELOPT | Selopt Structure for the F4 Help with Search Engines |

DDSETSTATE | Status of Objects |

DDSETYPTAB | Search Type Search Engine |

DDSEVMAP | DD: Map severity for level/STDO |

DDSEVSUM | DD: |

DDSHBUTTON | Buttons on the Hit List |

DDSHCUMAR | Information on Cursor Position and Markings |

DDSHDEFLT | Description of a default value for search help fields |

DDSHDEFSH | Default value – search help per user and collective s.h. |

DDSHDESCR | Interface: elementary search helps of a search help |

DDSHENTITY | Table of data elements which need the value table help |

DDSHEXMPL1 | Structure for F4 help example RUTSHEXP |

DDSHF4CTRL | Control Structure for F4 Process with Search Help Exit |

DDSHF4ENV | Program Environment for F4 Field |

DDSHFPROP | Characteristics of search help parameters |

DDSHHVALUE | Historic Help Values |

DDSHICON | Management of Icon Information |

DDSHIFACE | Interface description of a F4 help method |

DDSHLDB1 | Interface structure search help <-> logical DBs |

DDSHLPVERS | Current Version of Search Help Activator |

DDSHOCXINT | Communications between F4 process and search help OCX |

DDSHOFFLD | Shared buffer for search help for a DDIC field |

DDSHOUTFLD | Interface structure for FM to search help selection |

DDSHPVALUE | Personal Help Values |

DDSHRETVAL | Interface Structure Search Help <-> Help System |

DDSHSELOPT | Selection options for value selection with search help |

DDSHTECINF | Technical information about a search help |

DDSPAR | Storage clause for tables and indexes |

DDSPAR1 | Storage clause for tables and indexes |

DDSPAR2 | Storage clause for tables and indexes |

DDSTATE | Status of Objects |

DDSTATHIST | DD: Statistical Data for Conversion |

DDSTEXTIDX | Header Information of External Index |

DDSTORAGE | Storage clause for tables and indexes |

DDSTORAGE1 | Storage clause for tables and indexes |

DDSTORAGE2 | Storage clause for tables and indexes |

DDSYM10TAB | Symbol table (CHAR10) |

DDSYMTAB | Symbol table (as reference structure) |

DDSYN | Parameters for Buffer Synchronization |

DDTABFDS | DD: Structure/table name – field name with lengths |

DDTABLE | Structure for Table Information |

DDTABNAME | Only table name |

DDTABTVAL | DD: Control string for TABT values checks |

DDTBCLASS | DD: Control String for Checking TABCLASS <-> SQLTAB |

DDTBFD | DD: Table Name, Field Assignment |

DDTBFDCHK | Control String for Table Checks (Fields) |

DDTBFKCHK | Control String for Foreign Key Checks in Table Activator |

DDTBHDCHK | Control String for Table Checks (Header) |

DDTBIXCHK | Control String for the Index Checks |

DDTCCT | DD: Cluster Tables -> Table Clsuter – Assignment |

DDTEMPL | DD: Structure for mapping SKIND -> text |

DDTEXTDATA | Data cluster as text |

DDTIMER | DD: Basic tools, timer structure |

DDTRKORR | DD: Structure for Transport Requests |

DDTTACTRES | DD: Status of Table Types (Activator Results) |

DDTTSTATE | DD: Result when reading the TABT activation set |

DDTYPEDESC | Description of an ABAP Dictionary Type |

DDTYPEGET | Control structure for DD_TYPEINFO_GET |

DDTYPES | Table of all Dictionary types and classes |

DDTYPET | ABAP/4 Dictionary: Texts for type groups |

DDUDMPAR | Parameters for attribute maintenance / partial objects |

DDUDT | DD: Include for user, date, time |

DDVAL | Generated table for view DDVAL |

DDVE1 | Value Table for Domain DDVERINT4 |

DDVEPR | Check Table with Two Key Fields |

DDWHERECND | DD: Lines of where condition |

DDXTF | Nametab field structure for delayed writing |

DDXTT | Nametab header structure for delayed writing |

DDYN | Interface Between ABAPhelp and Help Processor |

DDYTF | Substitution Nametab (shadow-shadow-nametab for DDXTF) |

DDYTT | Substitution Nametab (shadow-shadow-nametab for DDXTT) |

DD_LB_TEST | Generated Table for View DD_LB_TEST |

Conclusion

It is thus possible to use these tables. Please feel free to add or correct any of the above.

Rgds,

Nic

BDC ( Batch Data Communication ) is used for uploading mass data into SAP system. In SAP system BDC also referred to batch input or data tranfer.

Typical Uses

Typical uses of batch input include the one-time import of data from a legacy system into a newly installed R/3 System. Another typical use is for periodic transfers of data from external systems or legacy systems that are still in use into SAP.

Background of BDC

To ensure data consistency in SAP system, we must not update SAP data directly from ABAP program. We must upload data through similar program flow compared to manual input by user. SAP provide this by BDC. BDC works by simulating the user input from transactional screen via an ABAP program. This means that you do not bypass any of the standard SAP consistency checks, authorisations, update conjunction tables, etc.

How it works

Data input entered by user simulated in BDC by data packet. The transaction then started using this internal table as the input and executed in the background.

Data packet is an internal table has a structure of BDCDATA, it has fields:
1. PROGRAM (program name)
2. DYNPRO (screen number)
3. DYNBEGIN (New screen start) X=new screen
4. FNAM (Field name)
5. FVAL (Field value)
Data packet contain of screen by screen packets. One screen packet contain:
1. Screen no
2. Cursor position
3. User command
4. Input fields

It implemented in internal table in this format:
PROGRAM    DYNPRO    DYNBEGIN    FNAM    FVAL
program1    screen1    X
BDC_CURSOR    pos1
BDC_OKCODE    comm1
fieldname1    fieldvalue1
fieldname2    fieldvalue2
program2    screen2    X
BDC_CURSOR    pos1
BDC_OKCODE    comm1
fieldname1    fieldvalue1
fieldname2    fieldvalue2

For example, we want to create a BDC to change ABAP program title.
Here is what we do manually: Go to screen SE38, enter program, select radiobutton “Attributes”, then click “Change”. After that, change title then press “Save” button.
In BDC, we simulate this by following internal table:
PROGRAM    DYNPRO    DYNBEGIN    FNAM    FVAL
SAPLWBABAP    100    X
BDC_CURSOR    RS38M-FUNC_HEAD
BDC_OKCODE    =CHAP
RS38M-PROGRAMM    ZAALTESTBDC
RS38M-FUNC_EDIT
RS38M-FUNC_HEAD    X
SAPLSEDTATTR    200    X
BDC_CURSOR    RS38M-REPTI
BDC_OKCODE    =CONT
RS38M-REPTI    Test change title BDC
TRDIR-SUBC    1
TRDIR-FIXPT    X
SAPLWBABAP    100    X
BDC_CURSOR    RS38M-PROGRAMM
BDC_OKCODE    =BACK
RS38M-PROGRAMM    ZAALTESTBDC
RS38M-FUNC_HEAD    X

To accomodate you to build data packet, SAP provide BDC recording in tcode SHDB.
Do following action:
1. Go to tcode SHDB
2. click “New recording”, enter recording name to identified your record, and TCode to be recorded.
3. You will enter recording mode of the transaction, simulate action you want to perform in this transaction
4. At the end it will result internal table ready to upload to data transfer methods (Call transaction or BDC sessions).

After internal table created then we pass this to data transfer methods. There are two alternatives of data transfer methods, using Call Transaction or BDC session.
Call transaction performed by calling command ‘Call Transaction’. ABAP program must do the error handling based on returning table from call transaction command. It is used for real-time interfaces and custom error handling & logging features. This is suitable when processing sequential update, it means, next data will depend on previous data.
In BDC Sessions, the ABAP program creates a session with all the transactional data, and this session can be viewed, scheduled and processed (using Transaction SM35) at a later time. The latter technique has a built-in error processing mechanism too.

Above explanation taken from http://abap-gallery.blogspot.com.

Here are a complete sample BDC program on ABAP. The sample will update net price of PO item 00010.

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

Contributed by Henrik Frank

For all entries

The for all entries creates a where clause, where all the entries in the driver table are combined with OR. If the number of entries in the driver table is larger than rsdb/max_blocking_factor, several similar SQL statements are executed to limit the length of the WHERE clause.

The plus

• Large amount of data
• Mixing processing and reading of data
• Fast internal reprocessing of data
• Fast

The Minus

• Difficult to program/understand
• Memory could be critical (use FREE or PACKAGE size)

Some steps that might make FOR ALL ENTRIES more efficient:

• Removing duplicates from the driver table
• Sorting the driver table
• If possible, convert the data in the driver table to ranges so a BETWEEN statement is used instead of and OR statement:

FOR ALL ENTRIES IN i_tab

WHERE mykey >= i_tab-low and

mykey <= i_tab-high.

Nested selects

The plus:

· Small amount of data

· Mixing processing and reading of data

· Easy to code – and understand

The minus:

· Large amount of data

· when mixed processing isn’t needed

· Performance killer no. 1

Select using JOINS

The plus

· Very large amount of data

· Similar to Nested selects – when the accesses are planned by the programmer

· In some cases the fastest

· Not so memory critical

The minus

· Very difficult to program/understand

· Mixing processing and reading of data not possible

Use the selection criteria

SELECT * FROM SBOOK.

CHECK: SBOOK-CARRID = ‘LH’ AND

SBOOK-CONNID = ’0400′.

ENDSELECT.

SELECT * FROM SBOOK

WHERE CARRID = ‘LH’ AND

CONNID = ’0400′.

ENDSELECT.

Use the aggregated functions

C4A = ’000′.

SELECT * FROM T100

WHERE SPRSL = ‘D’ AND

ARBGB = ’00′.

CHECK: T100-MSGNR > C4A.

C4A = T100-MSGNR.

ENDSELECT.

SELECT MAX( MSGNR ) FROM T100 INTO C4A

WHERE SPRSL = ‘D’ AND

ARBGB = ’00′.

Select with view

SELECT * FROM DD01L

WHERE DOMNAME LIKE ‘CHAR%’

AND AS4LOCAL = ‘A’.

SELECT SINGLE * FROM DD01T

WHERE DOMNAME = DD01L-DOMNAME

AND AS4LOCAL = ‘A’

AND AS4VERS = DD01L-AS4VERS

AND DDLANGUAGE = SY-LANGU.

ENDSELECT.

SELECT * FROM DD01V

WHERE DOMNAME LIKE ‘CHAR%’

AND DDLANGUAGE = SY-LANGU.

ENDSELECT.

Select with index support

SELECT * FROM T100

WHERE ARBGB = ’00′

AND MSGNR = ’999′.

ENDSELECT.

SELECT * FROM T002.

SELECT * FROM T100

WHERE SPRSL = T002-SPRAS

AND ARBGB = ’00′

AND MSGNR = ’999′.

ENDSELECT.

ENDSELECT.

Select … Into table

REFRESH X006.

SELECT * FROM T006 INTO X006.

APPEND X006.

ENDSELECT

SELECT * FROM T006 INTO TABLE X006.

Select with selection list

SELECT * FROM DD01L

WHERE DOMNAME LIKE ‘CHAR%’

AND AS4LOCAL = ‘A’.

ENDSELECT

SELECT DOMNAME FROM DD01L

INTO DD01L-DOMNAME

WHERE DOMNAME LIKE ‘CHAR%’

AND AS4LOCAL = ‘A’.

ENDSELECT

Key access to multiple lines

LOOP AT TAB.

CHECK TAB-K = KVAL.

” …

ENDLOOP.

LOOP AT TAB WHERE K = KVAL.

” …

ENDLOOP.

Copying internal tables

REFRESH TAB_DEST.

LOOP AT TAB_SRC INTO TAB_DEST.

APPEND TAB_DEST.

ENDLOOP.

TAB_DEST[] = TAB_SRC[].

Modifying a set of lines

LOOP AT TAB.

IF TAB-FLAG IS INITIAL.

TAB-FLAG = ‘X’.

ENDIF.

MODIFY TAB.

ENDLOOP.

TAB-FLAG = ‘X’.

MODIFY TAB TRANSPORTING FLAG

WHERE FLAG IS INITIAL.

Deleting a sequence of lines

DO 101 TIMES.

DELETE TAB_DEST INDEX 450.

ENDDO.

DELETE TAB_DEST FROM 450 TO 550.

Linear search vs. binary

READ TABLE TAB WITH KEY K = ‘X’.

READ TABLE TAB WITH KEY K = ‘X’ BINARY SEARCH.

Comparison of internal tables

DESCRIBE TABLE: TAB1 LINES L1,

TAB2 LINES L2.

IF L1 <> L2.

TAB_DIFFERENT = ‘X’.

ELSE.

TAB_DIFFERENT = SPACE.

LOOP

AT TAB1.

READ TABLE TAB2 INDEX SY-TABIX.

IF TAB1 <> TAB2.

TAB_DIFFERENT = ‘X’. EXIT.

ENDIF.

ENDLOOP.

ENDIF.

IF TAB_DIFFERENT = SPACE.

” …

ENDIF.

IF TAB1[] = TAB2[].

” …

ENDIF.

Modify selected components

LOOP AT TAB.

TAB-DATE = SY-DATUM.

MODIFY TAB.

ENDLOOP.

WA-DATE = SY-DATUM.

LOOP AT TAB.

MODIFY TAB FROM WA TRANSPORTING DATE.

ENDLOOP.

Appending two internal tables

LOOP AT TAB_SRC.

APPEND TAB_SRC TO TAB_DEST.

ENDLOOP

APPEND LINES OF TAB_SRC TO TAB_DEST.

Deleting a set of lines

LOOP AT TAB_DEST WHERE K = KVAL.

DELETE TAB_DEST.

ENDLOOP

DELETE TAB_DEST WHERE K = KVAL.

Tools available in SAP to pin-point a performance problem

· The runtime analysis (SE30)

· SQL Trace (ST05)

· Tips and Tricks tool

· The performance database

Optimizing the load of the database

Using table buffering

Using buffered tables improves the performance considerably. Note that in some cases a statement can not be used with a buffered table, so when using these statements the buffer will be bypassed. These statements are:

· Select DISTINCT

· ORDER BY / GROUP BY / HAVING clause

· Any WHERE clause that contains a sub query or IS NULL expression

· JOIN s

· A SELECT… FOR UPDATE

If you wan t to explicitly bypass the buffer, use the BYPASS BUFFER addition to the SELECT clause.

Use the ABAP SORT Clause Instead of ORDER BY

The ORDER BY clause is executed on the database server while the ABAP SORT statement is executed on the application server. The database server will usually be the bottleneck, so sometimes it is better to move the sort from the database server to the application server.

If you are not sorting by the primary key ( E.g. using the ORDER BY PRIMARY key statement) but are sorting by another key, it could be better to use the ABAP SORT statement to sort the data in an internal table. Note however that for very large result sets it might not be a feasible solution and you would want to let the database server sort it.

Avoid the SELECT DISTINCT Statement

As with the ORDER BY clause it could be better to avoid using SELECT DISTINCT, if some of the fields are not part of an index. Instead use ABAP SORT + DELETE ADJACENT DUPLICATES on an internal table, to delete duplicate rows.

Posted in ABAP, Programming Tagged: abap select, abap select. performance select, select query, select statement ]]> http://indradewaji.wordpress.com/2008/12/09/abap-select-statement-and-performance/feed/ 0 Indra Dewaji http://indradewaji.wordpress.com/2008/12/09/find-sap-user-exit/ http://indradewaji.wordpress.com/2008/12/09/find-sap-user-exit/#comments Tue, 09 Dec 2008 03:34:11 +0000 indradewaji http://indradewaji.wordpress.com/?p=64 ]]> I found a tips how to find user exit on the internet, and I’ll share it for you. To find user exit use function module MOD_SAP_GET_FUNCEXITS in SE37 and execute. Enter the program name (after you find it on SE93 – search base on T-Code) you want to find exit for and execute. A list of all user exits for that program will be displayed.

Have a nice try.

Download here