UMC_PERIODICITY_GET_DETAIL SAP Function module

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

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

Pattern for FM UMC_PERIODICITY_GET_DETAIL - UMC PERIODICITY GET DETAIL

CALL FUNCTION 'UMC_PERIODICITY_GET_DETAIL' "
  EXPORTING
    i_periodicity =             " umc_y_periodicity
  IMPORTING
    es_periodicity =            " umc_ru100
    es_periodicity_txt =        " umc_ru100t
    e_ltxt =                    " umc_y_ltxt
    et_interval =               " umc_yt_ru101
    et_interval_txt =           " umc_yt_ru101t
  EXCEPTIONS
    NOT_FOUND = 1               "
    .  "  UMC_PERIODICITY_GET_DETAIL

ABAP code example for Function Module UMC_PERIODICITY_GET_DETAIL

The ABAP code below is a full code listing to execute function module UMC_PERIODICITY_GET_DETAIL 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_es_periodicity  
 
 TYPE UMC_RU100
,
ld_es_periodicity_txt  
 
 TYPE UMC_RU100T
,
ld_e_ltxt  
 
 TYPE UMC_Y_LTXT
,
ld_et_interval  
 
 TYPE UMC_YT_RU101
,
ld_et_interval_txt  
 
 TYPE UMC_YT_RU101T
.


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

CALL FUNCTION 'UMC_PERIODICITY_GET_DETAIL'
  EXPORTING
    i_periodicity =              ld_i_periodicity
  IMPORTING
    es_periodicity =             ld_es_periodicity
    es_periodicity_txt =         ld_es_periodicity_txt
    e_ltxt =                     ld_e_ltxt
    et_interval =                ld_et_interval
    et_interval_txt =            ld_et_interval_txt
  EXCEPTIONS
    NOT_FOUND =                  1
    .  "  UMC_PERIODICITY_GET_DETAIL

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_es_periodicity
 
 TYPE UMC_RU100 ,
ld_i_periodicity
 
 TYPE UMC_Y_PERIODICITY ,
ld_es_periodicity_txt
 
 TYPE UMC_RU100T ,
ld_e_ltxt
 
 TYPE UMC_Y_LTXT ,
ld_et_interval
 
 TYPE UMC_YT_RU101 ,
ld_et_interval_txt
 
 TYPE UMC_YT_RU101T .


ld_i_periodicity = 'Check type of data required'.