FCOM_ACTTYPE_CREATEMULTIPLE SAP Function module - Create Activity Type

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

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

Pattern for FM FCOM_ACTTYPE_CREATEMULTIPLE - FCOM ACTTYPE CREATEMULTIPLE

CALL FUNCTION 'FCOM_ACTTYPE_CREATEMULTIPLE' "Create Activity Type
  EXPORTING
    it_activitytype =           " tcslap        Update Table for Activity Types
*   it_cslap_old =              " tcslap        Update Table for Activity Types
*   ib_testrun =                " abap_bool     Verknüpfungsfeld für View-Query
*   ib_create = ABAP_FALSE      " abap_bool     check whether need to check main screen data
*   it_exist_acttype =          " tcslap        Update Table for Activity Types
  IMPORTING
    et_message =                " bapirettab    Tabelle mit BAPI Return Informationen
  EXCEPTIONS
    ERROR_OCCURED = 1           "               Error Occured
    .  "  FCOM_ACTTYPE_CREATEMULTIPLE

ABAP code example for Function Module FCOM_ACTTYPE_CREATEMULTIPLE

The ABAP code below is a full code listing to execute function module FCOM_ACTTYPE_CREATEMULTIPLE 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 BAPIRETTAB
.


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

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

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

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

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

CALL FUNCTION 'FCOM_ACTTYPE_CREATEMULTIPLE'
  EXPORTING
    it_activitytype =            ld_it_activitytype
*   it_cslap_old =               ld_it_cslap_old
*   ib_testrun =                 ld_ib_testrun
*   ib_create =                  ld_ib_create
*   it_exist_acttype =           ld_it_exist_acttype
  IMPORTING
    et_message =                 ld_et_message
  EXCEPTIONS
    ERROR_OCCURED =              1
    .  "  FCOM_ACTTYPE_CREATEMULTIPLE

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_et_message
 
 TYPE BAPIRETTAB ,
ld_it_activitytype
 
 TYPE TCSLAP ,
ld_it_cslap_old
 
 TYPE TCSLAP ,
ld_ib_testrun
 
 TYPE ABAP_BOOL ,
ld_ib_create
 
 TYPE ABAP_BOOL ,
ld_it_exist_acttype
 
 TYPE TCSLAP .


ld_it_activitytype = 'Check type of data required'.
ld_it_cslap_old = 'Check type of data required'.
ld_ib_testrun = 'Check type of data required'.
ld_ib_create = 'Check type of data required'.
ld_it_exist_acttype = 'Check type of data required'.