SAP START_TRIGGER_PUT_FROM_UI Function Module for FM to trigger PUT using a new task









START_TRIGGER_PUT_FROM_UI is a standard start trigger put from ui SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for FM to trigger PUT using a new task 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 start trigger put from ui FM, simply by entering the name START_TRIGGER_PUT_FROM_UI into the relevant SAP transaction such as SE37 or SE38.

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



Function START_TRIGGER_PUT_FROM_UI 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 'START_TRIGGER_PUT_FROM_UI'"FM to trigger PUT using a new task
EXPORTING
IS_PUT_HDR = "Post-upgrade test execution Header
* IS_TASKLIST = "Tasklist Indicator
.



IMPORTING Parameters details for START_TRIGGER_PUT_FROM_UI

IS_PUT_HDR - Post-upgrade test execution Header

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

IS_TASKLIST - Tasklist Indicator

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

Copy and paste ABAP code example for START_TRIGGER_PUT_FROM_UI 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_is_put_hdr  TYPE START_A_PUT_HDR, "   
lv_is_tasklist  TYPE CHAR1. "   

  CALL FUNCTION 'START_TRIGGER_PUT_FROM_UI'  "FM to trigger PUT using a new task
    EXPORTING
         IS_PUT_HDR = lv_is_put_hdr
         IS_TASKLIST = lv_is_tasklist
. " START_TRIGGER_PUT_FROM_UI




ABAP code using 7.40 inline data declarations to call FM START_TRIGGER_PUT_FROM_UI

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!