BTFR_CORR_CHECK SAP Function module

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

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

Pattern for FM BTFR_CORR_CHECK - BTFR CORR CHECK

CALL FUNCTION 'BTFR_CORR_CHECK' "
  EXPORTING
    package =                   " devclass      Package
*   flag_string =               " btfr_f_string  Object Type
    concept =                   " sotr_conc     Key for Logical Object in the OTR
*   flag_suppress_dialog =      "
  IMPORTING
    flag_local_package =        " btfr_flag
    flag_cancelled =            " btfr_flag
    corr_num =                  " trkorr        Request/Task
    flag_repair =               " btfr_flag
  EXCEPTIONS
    INVALID_PACKAGE = 1         "
    PERMISSION_FAILURE = 2      "
    .  "  BTFR_CORR_CHECK

ABAP code example for Function Module BTFR_CORR_CHECK

The ABAP code below is a full code listing to execute function module BTFR_CORR_CHECK 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_flag_local_package  
 
 TYPE BTFR_FLAG
,
ld_flag_cancelled  
 
 TYPE BTFR_FLAG
,
ld_corr_num  
 
 TYPE TRKORR
,
ld_flag_repair  
 
 TYPE BTFR_FLAG
.


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

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

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

DATA(ld_flag_suppress_dialog) = 'some text here'.
.

CALL FUNCTION 'BTFR_CORR_CHECK'
  EXPORTING
    package =                    ld_package
*   flag_string =                ld_flag_string
    concept =                    ld_concept
*   flag_suppress_dialog =       ld_flag_suppress_dialog
  IMPORTING
    flag_local_package =         ld_flag_local_package
    flag_cancelled =             ld_flag_cancelled
    corr_num =                   ld_corr_num
    flag_repair =                ld_flag_repair
  EXCEPTIONS
    INVALID_PACKAGE =            1
    PERMISSION_FAILURE =         2
    .  "  BTFR_CORR_CHECK

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
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_flag_local_package
 
 TYPE BTFR_FLAG ,
ld_package
 
 TYPE DEVCLASS ,
ld_flag_cancelled
 
 TYPE BTFR_FLAG ,
ld_flag_string
 
 TYPE BTFR_F_STRING ,
ld_corr_num
 
 TYPE TRKORR ,
ld_concept
 
 TYPE SOTR_CONC ,
ld_flag_repair
 
 TYPE BTFR_FLAG ,
ld_flag_suppress_dialog
 
 TYPE STRING .


ld_package = 'Check type of data required'.
ld_flag_string = 'Check type of data required'.
ld_concept = 'Check type of data required'.
ld_flag_suppress_dialog = 'some text here'.