FDT_CC_GENERATE_MANY_FUNCTIONS SAP Function module - BRFplus: Ensure that Functions are Generated

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

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

Pattern for FM FDT_CC_GENERATE_MANY_FUNCTIONS - FDT CC GENERATE MANY FUNCTIONS

CALL FUNCTION 'FDT_CC_GENERATE_MANY_FUNCTIONS' "BRFplus: Ensure that Functions are Generated
* EXPORTING
*   iv_system_objects = ABAP_TRUE  " abap_bool
*   iv_master_data_obj = ABAP_FALSE  " abap_bool
*   iv_customizing_obj = ABAP_FALSE  " abap_bool
*   iv_enforce_new_generation = ABAP_FALSE  " abap_bool
*   iv_trace_generation = ABAP_FALSE  " abap_bool
*   it_filter_ids =             " if_fdt_types=>t_object_id
  IMPORTING
    et_message =                " if_fdt_types=>t_message
    .  "  FDT_CC_GENERATE_MANY_FUNCTIONS

ABAP code example for Function Module FDT_CC_GENERATE_MANY_FUNCTIONS

The ABAP code below is a full code listing to execute function module FDT_CC_GENERATE_MANY_FUNCTIONS 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_et_message  
 
 TYPE IF_FDT_TYPES=>T_MESSAGE
.


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

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

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

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

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

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

CALL FUNCTION 'FDT_CC_GENERATE_MANY_FUNCTIONS'
* EXPORTING
*   iv_system_objects =          ld_iv_system_objects
*   iv_master_data_obj =         ld_iv_master_data_obj
*   iv_customizing_obj =         ld_iv_customizing_obj
*   iv_enforce_new_generation =    ld_iv_enforce_new_generation
*   iv_trace_generation =        ld_iv_trace_generation
*   it_filter_ids =              ld_it_filter_ids
  IMPORTING
    et_message =                 ld_et_message
    .  "  FDT_CC_GENERATE_MANY_FUNCTIONS

IF SY-SUBRC EQ 0.
  "All OK
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_et_message
 
 TYPE IF_FDT_TYPES=>T_MESSAGE ,
ld_iv_system_objects
 
 TYPE ABAP_BOOL ,
ld_iv_master_data_obj
 
 TYPE ABAP_BOOL ,
ld_iv_customizing_obj
 
 TYPE ABAP_BOOL ,
ld_iv_enforce_new_generation
 
 TYPE ABAP_BOOL ,
ld_iv_trace_generation
 
 TYPE ABAP_BOOL ,
ld_it_filter_ids
 
 TYPE IF_FDT_TYPES=>T_OBJECT_ID .


ld_iv_system_objects = 'Check type of data required'.
ld_iv_master_data_obj = 'Check type of data required'.
ld_iv_customizing_obj = 'Check type of data required'.
ld_iv_enforce_new_generation = 'Check type of data required'.
ld_iv_trace_generation = 'Check type of data required'.
ld_it_filter_ids = 'Check type of data required'.