SAP SWF_EVT_HANDLER_START_INTERNAL Function Module for Start event handler









SWF_EVT_HANDLER_START_INTERNAL is a standard swf evt handler start internal SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Start event handler 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 swf evt handler start internal FM, simply by entering the name SWF_EVT_HANDLER_START_INTERNAL into the relevant SAP transaction such as SE37 or SE38.

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



Function SWF_EVT_HANDLER_START_INTERNAL 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 'SWF_EVT_HANDLER_START_INTERNAL'"Start event handler
  EXPORTING
   IM_LINKAGE =  "Event Linkage
   IM_STANDARDS =  "Standard Container Elements of Event Manager
   IM_EVENT_ID =  "ID of an event instance
   IM_NEXT_MODE =  "Character Field Length 1
   IM_CONTAINER_IS_COMPLETE =  "Checkbox Field
   IM_XML_CONTAINER =  "Table for XML Stream of Event Container
*  IM_XML_SIZE =  "
   IM_BOR_CONTAINER =  "Container Table
*  IM_EVT_GUID =  "Event GUID

 IMPORTING
   EX_EVT_GUID =  "Event GUID
.



IMPORTING Parameters details for SWF_EVT_HANDLER_START_INTERNAL

IM_LINKAGE - Event Linkage

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

IM_STANDARDS - Standard Container Elements of Event Manager

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

IM_EVENT_ID - ID of an event instance

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

IM_NEXT_MODE - Character Field Length 1

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

IM_CONTAINER_IS_COMPLETE - Checkbox Field

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

IM_XML_CONTAINER - Table for XML Stream of Event Container

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

IM_XML_SIZE -

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

IM_BOR_CONTAINER - Container Table

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

IM_EVT_GUID - Event GUID

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

EXPORTING Parameters details for SWF_EVT_HANDLER_START_INTERNAL

EX_EVT_GUID - Event GUID

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

Copy and paste ABAP code example for SWF_EVT_HANDLER_START_INTERNAL 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_im_linkage  TYPE SWFDEVLNK, "   
lv_ex_evt_guid  TYPE SWE_EGUID, "   
lv_im_standards  TYPE SWFREVTSTD, "   
lv_im_event_id  TYPE SWE_EVTID, "   
lv_im_next_mode  TYPE CHAR01, "   
lv_im_container_is_complete  TYPE XFELD, "   
lv_im_xml_container  TYPE SWFREVTXML_TAB, "   
lv_im_xml_size  TYPE SWF_XMLSIZ, "   
lv_im_bor_container  TYPE SWCONTTAB, "   
lv_im_evt_guid  TYPE SWE_EGUID. "   

  CALL FUNCTION 'SWF_EVT_HANDLER_START_INTERNAL'  "Start event handler
    EXPORTING
         IM_LINKAGE = lv_im_linkage
         IM_STANDARDS = lv_im_standards
         IM_EVENT_ID = lv_im_event_id
         IM_NEXT_MODE = lv_im_next_mode
         IM_CONTAINER_IS_COMPLETE = lv_im_container_is_complete
         IM_XML_CONTAINER = lv_im_xml_container
         IM_XML_SIZE = lv_im_xml_size
         IM_BOR_CONTAINER = lv_im_bor_container
         IM_EVT_GUID = lv_im_evt_guid
    IMPORTING
         EX_EVT_GUID = lv_ex_evt_guid
. " SWF_EVT_HANDLER_START_INTERNAL




ABAP code using 7.40 inline data declarations to call FM SWF_EVT_HANDLER_START_INTERNAL

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!