SAP Function Modules

comments icon Comments

FDT_CC_GENERATE_FUNCTION SAP Function module - Generate code for a FDT function and persist it in actual active version







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

Associated Function Group: FDT_CC_SERVICE
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM FDT_CC_GENERATE_FUNCTION - FDT CC GENERATE FUNCTION 





CALL FUNCTION 'FDT_CC_GENERATE_FUNCTION' "Generate code for a FDT function and persist it in actual active version
  EXPORTING
    iv_id =                     " fdt_uuid      UUID of function
    iv_timestamp =              " timestamp     Time Stamp  for which to generate
*   iv_trace_generation = ABAP_FALSE  " char01  Boolean variable
*   iv_with_check = ABAP_FALSE  " char01        Character Field Length 1
*   iv_with_pretty_printer = ABAP_FALSE  " char01  Character Field Length 1
  EXCEPTIONS
    INVALID_INPUT = 1           "               invalid ID, application ID
    GENERATION_ERROR = 2        "               Error in generation or generation not supported
    NO_GENERATION = 3           "               Timestamp represents an obsolete version, no generation!
    SYSTEM_ERROR = 4            "               System error during enqueue
    .  "  FDT_CC_GENERATE_FUNCTION

ABAP code example for Function Module FDT_CC_GENERATE_FUNCTION





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

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

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

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

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

CALL FUNCTION 'FDT_CC_GENERATE_FUNCTION'
  EXPORTING
    iv_id =                      ld_iv_id
    iv_timestamp =               ld_iv_timestamp
*   iv_trace_generation =        ld_iv_trace_generation
*   iv_with_check =              ld_iv_with_check
*   iv_with_pretty_printer =     ld_iv_with_pretty_printer
  EXCEPTIONS
    INVALID_INPUT =              1
    GENERATION_ERROR =           2
    NO_GENERATION =              3
    SYSTEM_ERROR =               4
    .  "  FDT_CC_GENERATE_FUNCTION

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
ELSEIF SY-SUBRC EQ 4. "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_iv_id  TYPE FDT_UUID ,
ld_iv_timestamp  TYPE TIMESTAMP ,
ld_iv_trace_generation  TYPE CHAR01 ,
ld_iv_with_check  TYPE CHAR01 ,
ld_iv_with_pretty_printer  TYPE CHAR01 .




ld_iv_id = 'Check type of data required'.
ld_iv_timestamp = 'Check type of data required'.
ld_iv_trace_generation = 'Check type of data required'.
ld_iv_with_check = 'Check type of data required'.
ld_iv_with_pretty_printer = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name FDT_CC_GENERATE_FUNCTION or its description.


   
 

FDT_CC_GENERATE_FUNCTION - Generate code for a FDT function and persist it in actual active versi
FDT_CC_FIND_UNREFERENCED_CLS - BRFplus: Find Unreferenced Classes
FDT_CC_DELETE_UNUSED_REFERENCE - Delete reference for which no function exists
FDT_CC_DELETE_UNUSED_CLASSES - FDT: Delete Unused Generated Classes
FDT_CC_DELETE_OLD_REFERENCES - Delete Old References to generated Classes
FDT_CC_CLEAR_BUFFER_ONROLLBACK - Clear Buffer on Rollback