FM_DC_FUNCTION_VALIDITY_GET SAP Function module

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

Associated Function Group: FMDC
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM FM_DC_FUNCTION_VALIDITY_GET - FM DC FUNCTION VALIDITY GET

CALL FUNCTION 'FM_DC_FUNCTION_VALIDITY_GET' "
  EXPORTING
    i_function =                " fkber
*   keydate = SY-DATUM          " fmfctr-datbis  FM: Valid-To Date
*   comp_code =                 " bukrs         Company Code
  IMPORTING
    e_begda =                   " sy-datum      Current Date of Application Server
    e_endda =                   " sy-datum      Current Date of Application Server
    e_expiry_date =             " sy-datum      Current Date of Application Server
  EXCEPTIONS
    NOT_FOUND = 1               "
    .  "  FM_DC_FUNCTION_VALIDITY_GET

ABAP code example for Function Module FM_DC_FUNCTION_VALIDITY_GET

The ABAP code below is a full code listing to execute function module FM_DC_FUNCTION_VALIDITY_GET 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_e_begda  
 
 TYPE SY-DATUM
,
ld_e_endda  
 
 TYPE SY-DATUM
,
ld_e_expiry_date  
 
 TYPE SY-DATUM
.


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

SELECT single DATBIS 
  FROM FMFCTR 
  INTO @DATA(ld_keydate).


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

CALL FUNCTION 'FM_DC_FUNCTION_VALIDITY_GET'
  EXPORTING
    i_function =                 ld_i_function
*   keydate =                    ld_keydate
*   comp_code =                  ld_comp_code
  IMPORTING
    e_begda =                    ld_e_begda
    e_endda =                    ld_e_endda
    e_expiry_date =              ld_e_expiry_date
  EXCEPTIONS
    NOT_FOUND =                  1
    .  "  FM_DC_FUNCTION_VALIDITY_GET

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_e_begda
 
 TYPE SY-DATUM ,
ld_i_function
 
 TYPE FKBER ,
ld_e_endda
 
 TYPE SY-DATUM ,
ld_keydate
 
 TYPE FMFCTR-DATBIS ,
ld_e_expiry_date
 
 TYPE SY-DATUM ,
ld_comp_code
 
 TYPE BUKRS .


ld_i_function = 'Check type of data required'.

SELECT single DATBIS 
  FROM FMFCTR 
  INTO ld_keydate.

ld_comp_code = 'Check type of data required'.