SAP DVM_BOF_SET_STATUS Function Module for Modify the status of a run
DVM_BOF_SET_STATUS is a standard dvm bof set status SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Modify the status of a run 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 dvm bof set status FM, simply by entering the name DVM_BOF_SET_STATUS into the relevant SAP transaction such as SE37 or SE38.
Function Group: DVM_BOF_MAIN
Program Name: SAPLDVM_BOF_MAIN
Main Program: SAPLDVM_BOF_MAIN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function DVM_BOF_SET_STATUS 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 'DVM_BOF_SET_STATUS'"Modify the status of a run.
EXPORTING
* I_VARIANT_ID = "GUID in character mode
* I_STATUS = "Status of background job
* I_BW_UPLOAD = "Flag for BW upload
IMPORTING Parameters details for DVM_BOF_SET_STATUS
I_VARIANT_ID - GUID in character mode
Data type: CHAR32Optional: Yes
Call by Reference: No ( called with pass by value option)
I_STATUS - Status of background job
Data type: BTCSTATUSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BW_UPLOAD - Flag for BW upload
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DVM_BOF_SET_STATUS 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_i_variant_id | TYPE CHAR32, " | |||
| lv_i_status | TYPE BTCSTATUS, " | |||
| lv_i_bw_upload | TYPE CHAR1. " |
|   CALL FUNCTION 'DVM_BOF_SET_STATUS' "Modify the status of a run |
| EXPORTING | ||
| I_VARIANT_ID | = lv_i_variant_id | |
| I_STATUS | = lv_i_status | |
| I_BW_UPLOAD | = lv_i_bw_upload | |
| . " DVM_BOF_SET_STATUS | ||
ABAP code using 7.40 inline data declarations to call FM DVM_BOF_SET_STATUS
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