MCS_ANALYSE_GENER SAP Function module

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

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

Pattern for FM MCS_ANALYSE_GENER - MCS ANALYSE GENER

CALL FUNCTION 'MCS_ANALYSE_GENER' "
  EXPORTING
*   i_flg_refresh_prot = SPACE  " xflag         Refresh log before generation
*   i_flg_show_prot = SPACE     " xflag         Display log after generation
    i_mcinf =                   " tmc4-mcinf    Info structure
*   i_gener_in_customer_name_range = ' '  " sy-datar
  EXCEPTIONS
    MCINF_NOT_FOUND = 1         "               Info structure does not exist
    LOCKED = 2                  "               TMC7 blocked
    GENERATION_FAILED = 3       "               Error during generation
    .  "  MCS_ANALYSE_GENER

ABAP code example for Function Module MCS_ANALYSE_GENER

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

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

SELECT single MCINF 
  FROM TMC4 
  INTO @DATA(ld_i_mcinf).


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

CALL FUNCTION 'MCS_ANALYSE_GENER'
  EXPORTING
*   i_flg_refresh_prot =         ld_i_flg_refresh_prot
*   i_flg_show_prot =            ld_i_flg_show_prot
    i_mcinf =                    ld_i_mcinf
*   i_gener_in_customer_name_range =    ld_i_gener_in_customer_name_range
  EXCEPTIONS
    MCINF_NOT_FOUND =            1
    LOCKED =                     2
    GENERATION_FAILED =          3
    .  "  MCS_ANALYSE_GENER

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
ELSEIF SY-SUBRC EQ 3. "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_i_flg_refresh_prot
 
 TYPE XFLAG ,
ld_i_flg_show_prot
 
 TYPE XFLAG ,
ld_i_mcinf
 
 TYPE TMC4-MCINF ,
ld_i_gener_in_customer_name_range
 
 TYPE SY-DATAR .


ld_i_flg_refresh_prot = 'some text here'.
ld_i_flg_show_prot = 'some text here'.

SELECT single MCINF 
  FROM TMC4 
  INTO ld_i_mcinf.

ld_i_gener_in_customer_name_range = 'some text here'.