S_IMG_PROJECT_ACTIVATE SAP Function module

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

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

Pattern for FM S_IMG_PROJECT_ACTIVATE - S IMG PROJECT ACTIVATE

CALL FUNCTION 'S_IMG_PROJECT_ACTIVATE' "
  EXPORTING
    project_number =            " tproject-project_id
    project_description =       "
*   use_manual_selection = SPACE  " char1
*   activate_also_views = SPACE  " char1
*   activate_asap_views = SPACE  " char1
*   running_in_batch = SPACE    " char1
* TABLES
*   activation_messages =       " hier_mess
    .  "  S_IMG_PROJECT_ACTIVATE

ABAP code example for Function Module S_IMG_PROJECT_ACTIVATE

The ABAP code below is a full code listing to execute function module S_IMG_PROJECT_ACTIVATE 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:
it_activation_messages  
 
 TYPE STANDARD TABLE OF HIER_MESS,"TABLES PARAM
wa_activation_messages
 
 LIKE LINE OF it_activation_messages
.

 

SELECT single PROJECT_ID 
  FROM TPROJECT 
  INTO @DATA(ld_project_number).


DATA(ld_project_description) = 'some text here'.

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

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

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

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

"populate fields of struture and append to itab
append wa_activation_messages to it_activation_messages.
.

CALL FUNCTION 'S_IMG_PROJECT_ACTIVATE'
  EXPORTING
    project_number =             ld_project_number
    project_description =        ld_project_description
*   use_manual_selection =       ld_use_manual_selection
*   activate_also_views =        ld_activate_also_views
*   activate_asap_views =        ld_activate_asap_views
*   running_in_batch =           ld_running_in_batch
* TABLES
*   activation_messages =        it_activation_messages
    .  "  S_IMG_PROJECT_ACTIVATE

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_project_number
 
 TYPE TPROJECT-PROJECT_ID ,
it_activation_messages
 
 TYPE STANDARD TABLE OF HIER_MESS ,
wa_activation_messages
 
 LIKE LINE OF it_activation_messages,
ld_project_description
 
 TYPE STRING ,
ld_use_manual_selection
 
 TYPE CHAR1 ,
ld_activate_also_views
 
 TYPE CHAR1 ,
ld_activate_asap_views
 
 TYPE CHAR1 ,
ld_running_in_batch
 
 TYPE CHAR1 .



SELECT single PROJECT_ID 
  FROM TPROJECT 
  INTO ld_project_number.
 

"populate fields of struture and append to itab
append wa_activation_messages to it_activation_messages.
ld_project_description = 'some text here'.
ld_use_manual_selection = 'Check type of data required'.
ld_activate_also_views = 'Check type of data required'.
ld_activate_asap_views = 'Check type of data required'.
ld_running_in_batch = 'Check type of data required'.