SAP GRAC_API_SODUPDATE_WORKFLOW Function Module for Update workflow for SoD request
GRAC_API_SODUPDATE_WORKFLOW is a standard grac api sodupdate workflow SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Update workflow for SoD request 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 grac api sodupdate workflow FM, simply by entering the name GRAC_API_SODUPDATE_WORKFLOW into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRAC_FG_BACKGROUND_JOBS
Program Name: SAPLGRAC_FG_BACKGROUND_JOBS
Main Program: SAPLGRAC_FG_BACKGROUND_JOBS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GRAC_API_SODUPDATE_WORKFLOW 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 'GRAC_API_SODUPDATE_WORKFLOW'"Update workflow for SoD request.
EXPORTING
IV_LOGHNDL = "Application Log: Log Handle
IV_PLANID = "UUID of the GRC object (char32)
IMPORTING Parameters details for GRAC_API_SODUPDATE_WORKFLOW
IV_LOGHNDL - Application Log: Log Handle
Data type: BALLOGHNDLOptional: No
Call by Reference: Yes
IV_PLANID - UUID of the GRC object (char32)
Data type: GRFN_GUIDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for GRAC_API_SODUPDATE_WORKFLOW 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_iv_loghndl | TYPE BALLOGHNDL, " | |||
| lv_iv_planid | TYPE GRFN_GUID. " |
|   CALL FUNCTION 'GRAC_API_SODUPDATE_WORKFLOW' "Update workflow for SoD request |
| EXPORTING | ||
| IV_LOGHNDL | = lv_iv_loghndl | |
| IV_PLANID | = lv_iv_planid | |
| . " GRAC_API_SODUPDATE_WORKFLOW | ||
ABAP code using 7.40 inline data declarations to call FM GRAC_API_SODUPDATE_WORKFLOW
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