FTR_GDPDU_CHECK_OVERLAP SAP Function module

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

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

Pattern for FM FTR_GDPDU_CHECK_OVERLAP - FTR GDPDU CHECK OVERLAP

CALL FUNCTION 'FTR_GDPDU_CHECK_OVERLAP' "
  EXPORTING
*   im_application = 'TR-TM'    " applk_bf
    im_company_code =           " bukrs
*   im_user = SY-UNAME          " usnam
*   im_program = SY-CPROG       " progname
    im_start_date =             " ftr_gdpdu_start_date
*   im_end_date =               " ftr_gdpdu_end_date
  IMPORTING
    ex_flg_tax_auditor =        " flag
  EXCEPTIONS
    NO_AUTHORITY = 1            "
    WRONG_INPUT = 2             "
    .  "  FTR_GDPDU_CHECK_OVERLAP

ABAP code example for Function Module FTR_GDPDU_CHECK_OVERLAP

The ABAP code below is a full code listing to execute function module FTR_GDPDU_CHECK_OVERLAP 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_ex_flg_tax_auditor  
 
 TYPE FLAG
.


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

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

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

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

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

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

CALL FUNCTION 'FTR_GDPDU_CHECK_OVERLAP'
  EXPORTING
*   im_application =             ld_im_application
    im_company_code =            ld_im_company_code
*   im_user =                    ld_im_user
*   im_program =                 ld_im_program
    im_start_date =              ld_im_start_date
*   im_end_date =                ld_im_end_date
  IMPORTING
    ex_flg_tax_auditor =         ld_ex_flg_tax_auditor
  EXCEPTIONS
    NO_AUTHORITY =               1
    WRONG_INPUT =                2
    .  "  FTR_GDPDU_CHECK_OVERLAP

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_ex_flg_tax_auditor
 
 TYPE FLAG ,
ld_im_application
 
 TYPE APPLK_BF ,
ld_im_company_code
 
 TYPE BUKRS ,
ld_im_user
 
 TYPE USNAM ,
ld_im_program
 
 TYPE PROGNAME ,
ld_im_start_date
 
 TYPE FTR_GDPDU_START_DATE ,
ld_im_end_date
 
 TYPE FTR_GDPDU_END_DATE .


ld_im_application = 'Check type of data required'.
ld_im_company_code = 'Check type of data required'.
ld_im_user = 'Check type of data required'.
ld_im_program = 'Check type of data required'.
ld_im_start_date = 'Check type of data required'.
ld_im_end_date = 'Check type of data required'.