FTR_TEX_REXP_OVERVIEW_UI SAP Function module - Raw Exposure Overview Screen FM

FTR_TEX_REXP_OVERVIEW_UI 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 FTR_TEX_REXP_OVERVIEW_UI into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FTR_TEX_RAW_EXPOSURE_UI
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM FTR_TEX_REXP_OVERVIEW_UI - FTR TEX REXP OVERVIEW UI

CALL FUNCTION 'FTR_TEX_REXP_OVERVIEW_UI' "Raw Exposure Overview Screen FM
  EXPORTING
    is_ranges =                 " texs_selections  Range Selections
*   is_variant =                " disvariant    Layout (External Use)
*   iv_subit_level = ' '        " flag          Details at sub item level?
*   iv_display_all = ' '        " flag          Display all versions?
*   iv_creation_indicator =     " ftr_creation_indicator  Raw Exposure Creation Indicator
*   iv_with_text = 'X'          " flag          With text selection
* CHANGING
*   cs_variant =                " disvariant    Layout (External Use)
    .  "  FTR_TEX_REXP_OVERVIEW_UI

ABAP code example for Function Module FTR_TEX_REXP_OVERVIEW_UI

The ABAP code below is a full code listing to execute function module FTR_TEX_REXP_OVERVIEW_UI 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(ld_cs_variant) = 'Check type of data required'.

DATA(ld_is_ranges) = 'Check type of data required'.

DATA(ld_is_variant) = 'Check type of data required'.

DATA(ld_iv_subit_level) = 'Check type of data required'.

DATA(ld_iv_display_all) = 'Check type of data required'.

DATA(ld_iv_creation_indicator) = 'Check type of data required'.

DATA(ld_iv_with_text) = 'Check type of data required'.
.

CALL FUNCTION 'FTR_TEX_REXP_OVERVIEW_UI'
  EXPORTING
    is_ranges =                  ld_is_ranges
*   is_variant =                 ld_is_variant
*   iv_subit_level =             ld_iv_subit_level
*   iv_display_all =             ld_iv_display_all
*   iv_creation_indicator =      ld_iv_creation_indicator
*   iv_with_text =               ld_iv_with_text
* CHANGING
*   cs_variant =                 ld_cs_variant
    .  "  FTR_TEX_REXP_OVERVIEW_UI

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_cs_variant
 
 TYPE DISVARIANT ,
ld_is_ranges
 
 TYPE TEXS_SELECTIONS ,
ld_is_variant
 
 TYPE DISVARIANT ,
ld_iv_subit_level
 
 TYPE FLAG ,
ld_iv_display_all
 
 TYPE FLAG ,
ld_iv_creation_indicator
 
 TYPE FTR_CREATION_INDICATOR ,
ld_iv_with_text
 
 TYPE FLAG .


ld_cs_variant = 'Check type of data required'.
ld_is_ranges = 'Check type of data required'.
ld_is_variant = 'Check type of data required'.
ld_iv_subit_level = 'Check type of data required'.
ld_iv_display_all = 'Check type of data required'.
ld_iv_creation_indicator = 'Check type of data required'.
ld_iv_with_text = 'Check type of data required'.