SAP TRIGGER_UPDATE_FOR_PROFILE Function Module for Triggers update tasks for a profile









TRIGGER_UPDATE_FOR_PROFILE is a standard trigger update for profile SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Triggers update tasks for a profile processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for trigger update for profile FM, simply by entering the name TRIGGER_UPDATE_FOR_PROFILE into the relevant SAP transaction such as SE37 or SE38.

Function Group: SRT_WSP_MASS_CONFIG_API
Program Name: SAPLSRT_WSP_MASS_CONFIG_API
Main Program: SAPLSRT_WSP_MASS_CONFIG_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function TRIGGER_UPDATE_FOR_PROFILE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'TRIGGER_UPDATE_FOR_PROFILE'"Triggers update tasks for a profile
EXPORTING
IM_PROFILE_NAME = "WSP Name of Profile Configuration
IM_PROFILE_VERSION = "Profile Version

IMPORTING
EX_RESULT = "Table of WSP QNames

EXCEPTIONS
CANNOT_TRIGGER_UPDATE = 1
.



IMPORTING Parameters details for TRIGGER_UPDATE_FOR_PROFILE

IM_PROFILE_NAME - WSP Name of Profile Configuration

Data type: SRT_WSP_PROFILE_CONFIG_NAME
Optional: No
Call by Reference: No ( called with pass by value option)

IM_PROFILE_VERSION - Profile Version

Data type: SRT_WSP_PROFILE_CONFIG_VERSION
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for TRIGGER_UPDATE_FOR_PROFILE

EX_RESULT - Table of WSP QNames

Data type: SRT_WSP_WKL_ITEM_KEYS
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

CANNOT_TRIGGER_UPDATE - Cannot trigger update for profile

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TRIGGER_UPDATE_FOR_PROFILE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_ex_result  TYPE SRT_WSP_WKL_ITEM_KEYS, "   
lv_im_profile_name  TYPE SRT_WSP_PROFILE_CONFIG_NAME, "   
lv_cannot_trigger_update  TYPE SRT_WSP_PROFILE_CONFIG_NAME, "   
lv_im_profile_version  TYPE SRT_WSP_PROFILE_CONFIG_VERSION. "   

  CALL FUNCTION 'TRIGGER_UPDATE_FOR_PROFILE'  "Triggers update tasks for a profile
    EXPORTING
         IM_PROFILE_NAME = lv_im_profile_name
         IM_PROFILE_VERSION = lv_im_profile_version
    IMPORTING
         EX_RESULT = lv_ex_result
    EXCEPTIONS
        CANNOT_TRIGGER_UPDATE = 1
. " TRIGGER_UPDATE_FOR_PROFILE




ABAP code using 7.40 inline data declarations to call FM TRIGGER_UPDATE_FOR_PROFILE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!