SAP GOS_EXECUTE_SERVICE Function Module for









GOS_EXECUTE_SERVICE is a standard gos execute service SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 gos execute service FM, simply by entering the name GOS_EXECUTE_SERVICE into the relevant SAP transaction such as SE37 or SE38.

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



Function GOS_EXECUTE_SERVICE 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 'GOS_EXECUTE_SERVICE'"
  EXPORTING
   IP_SERVICE =  "Name of generic service
   IS_OBJECT =  "BOR Object
   IP_NO_COMMIT =  "
   IP_POPUP =  "
*  IP_RWMOD =  "SGOS: Display/Change Mode of Generic Object Services
*  IT_SERVICE_SELECTION =  "SGOS: Selection Criteria for Service Selection
*  IP_VSI_PROFILE =  "

 IMPORTING
   EP_EVENT =  "
   EP_STATUS =  "SGOS: Status of a service object
   EP_ICON =  "Icon for a Generic Object Service
   EP_MESSAGE =  "

EXCEPTIONS
   EXECUTION_FAILED = 1
.



IMPORTING Parameters details for GOS_EXECUTE_SERVICE

IP_SERVICE - Name of generic service

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

IS_OBJECT - BOR Object

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

IP_NO_COMMIT -

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

IP_POPUP -

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

IP_RWMOD - SGOS: Display/Change Mode of Generic Object Services

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

IT_SERVICE_SELECTION - SGOS: Selection Criteria for Service Selection

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

IP_VSI_PROFILE -

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

EXPORTING Parameters details for GOS_EXECUTE_SERVICE

EP_EVENT -

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

EP_STATUS - SGOS: Status of a service object

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

EP_ICON - Icon for a Generic Object Service

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

EP_MESSAGE -

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

EXCEPTIONS details

EXECUTION_FAILED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for GOS_EXECUTE_SERVICE 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_ep_event  TYPE I, "   
lv_ip_service  TYPE SGS_SRVNAM, "   
lv_execution_failed  TYPE SGS_SRVNAM, "   
lv_ep_status  TYPE SGS_STATUS, "   
lv_is_object  TYPE BORIDENT, "   
lv_ep_icon  TYPE SGS_ICON, "   
lv_ip_no_commit  TYPE SGS_CMODE, "   
lv_ip_popup  TYPE SGS_CMODE, "   
lv_ep_message  TYPE SYMSG, "   
lv_ip_rwmod  TYPE SGS_RWMOD, "   
lv_it_service_selection  TYPE TGOS_SELS, "   
lv_ip_vsi_profile  TYPE VSCAN_PROFILE. "   

  CALL FUNCTION 'GOS_EXECUTE_SERVICE'  "
    EXPORTING
         IP_SERVICE = lv_ip_service
         IS_OBJECT = lv_is_object
         IP_NO_COMMIT = lv_ip_no_commit
         IP_POPUP = lv_ip_popup
         IP_RWMOD = lv_ip_rwmod
         IT_SERVICE_SELECTION = lv_it_service_selection
         IP_VSI_PROFILE = lv_ip_vsi_profile
    IMPORTING
         EP_EVENT = lv_ep_event
         EP_STATUS = lv_ep_status
         EP_ICON = lv_ep_icon
         EP_MESSAGE = lv_ep_message
    EXCEPTIONS
        EXECUTION_FAILED = 1
. " GOS_EXECUTE_SERVICE




ABAP code using 7.40 inline data declarations to call FM GOS_EXECUTE_SERVICE

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!