SAP Function Modules

VAR_TRANS_REQ_OPT_CNTR_TOP SAP Function module - Variables Geschäft: Top-Of-Page Ausgaben der Muß/Kann-Steuerung setzen







VAR_TRANS_REQ_OPT_CNTR_TOP is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name VAR_TRANS_REQ_OPT_CNTR_TOP into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: JBDVT
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM VAR_TRANS_REQ_OPT_CNTR_TOP - VAR TRANS REQ OPT CNTR TOP





CALL FUNCTION 'VAR_TRANS_REQ_OPT_CNTR_TOP' "Variables Geschäft: Top-Of-Page Ausgaben der Muß/Kann-Steuerung setzen
  EXPORTING
    ip_suetyp =                 " jbtmk_suetyp  Übernahmetyp
  TABLES
    ctp_action =                " jbtmk_action_lines  'Ausführbare' Zeilen
    ctp_selection =             " jbtmk_selection_lines  Selektionen, die geändert werden können
    ctp_appl_fields =           " jbtmk_appl_fields  Vertragsstatus
  CHANGING
    cp_header =                 " slis_t_listheader  TOP-OF-PAGE Info
    cp_fields_status =          " jbtmk_fields_status
    .  "  VAR_TRANS_REQ_OPT_CNTR_TOP

ABAP code example for Function Module VAR_TRANS_REQ_OPT_CNTR_TOP





The ABAP code below is a full code listing to execute function module VAR_TRANS_REQ_OPT_CNTR_TOP including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).

DATA:
it_ctp_action  TYPE STANDARD TABLE OF JBTMK_ACTION_LINES,"TABLES PARAM
wa_ctp_action  LIKE LINE OF it_ctp_action ,
it_ctp_selection  TYPE STANDARD TABLE OF JBTMK_SELECTION_LINES,"TABLES PARAM
wa_ctp_selection  LIKE LINE OF it_ctp_selection ,
it_ctp_appl_fields  TYPE STANDARD TABLE OF JBTMK_APPL_FIELDS,"TABLES PARAM
wa_ctp_appl_fields  LIKE LINE OF it_ctp_appl_fields .

DATA(ld_cp_header) = 'Check type of data required'.
DATA(ld_cp_fields_status) = 'Check type of data required'.
DATA(ld_ip_suetyp) = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_ctp_action to it_ctp_action.

"populate fields of struture and append to itab
append wa_ctp_selection to it_ctp_selection.

"populate fields of struture and append to itab
append wa_ctp_appl_fields to it_ctp_appl_fields. . CALL FUNCTION 'VAR_TRANS_REQ_OPT_CNTR_TOP' EXPORTING ip_suetyp = ld_ip_suetyp TABLES ctp_action = it_ctp_action ctp_selection = it_ctp_selection ctp_appl_fields = it_ctp_appl_fields CHANGING cp_header = ld_cp_header cp_fields_status = ld_cp_fields_status . " VAR_TRANS_REQ_OPT_CNTR_TOP
IF SY-SUBRC EQ 0. "All OK ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_cp_header  TYPE SLIS_T_LISTHEADER ,
ld_ip_suetyp  TYPE JBTMK_SUETYP ,
it_ctp_action  TYPE STANDARD TABLE OF JBTMK_ACTION_LINES ,
wa_ctp_action  LIKE LINE OF it_ctp_action,
ld_cp_fields_status  TYPE JBTMK_FIELDS_STATUS ,
it_ctp_selection  TYPE STANDARD TABLE OF JBTMK_SELECTION_LINES ,
wa_ctp_selection  LIKE LINE OF it_ctp_selection,
it_ctp_appl_fields  TYPE STANDARD TABLE OF JBTMK_APPL_FIELDS ,
wa_ctp_appl_fields  LIKE LINE OF it_ctp_appl_fields.

ld_cp_header = 'Check type of data required'.
ld_ip_suetyp = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_ctp_action to it_ctp_action.
ld_cp_fields_status = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_ctp_selection to it_ctp_selection.

"populate fields of struture and append to itab
append wa_ctp_appl_fields to it_ctp_appl_fields.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name VAR_TRANS_REQ_OPT_CNTR_TOP or its description.