SAP CVVSTART_WORKFLOW_TYPE Function Module for NOTRANSL: Bestimmt den zu verwendenden Workflow
CVVSTART_WORKFLOW_TYPE is a standard cvvstart workflow type SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Bestimmt den zu verwendenden Workflow 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 cvvstart workflow type FM, simply by entering the name CVVSTART_WORKFLOW_TYPE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CVVSTART
Program Name: SAPLCVVSTART
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CVVSTART_WORKFLOW_TYPE 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 'CVVSTART_WORKFLOW_TYPE'"NOTRANSL: Bestimmt den zu verwendenden Workflow.
IMPORTING
BUS_OBJECT = "Object Type
META_BUS_OBJECT = "Object Type
EXPORTING Parameters details for CVVSTART_WORKFLOW_TYPE
BUS_OBJECT - Object Type
Data type: SWO_OBJTYPOptional: No
Call by Reference: Yes
META_BUS_OBJECT - Object Type
Data type: SWO_OBJTYPOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CVVSTART_WORKFLOW_TYPE 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_bus_object | TYPE SWO_OBJTYP, " | |||
| lv_meta_bus_object | TYPE SWO_OBJTYP. " |
|   CALL FUNCTION 'CVVSTART_WORKFLOW_TYPE' "NOTRANSL: Bestimmt den zu verwendenden Workflow |
| IMPORTING | ||
| BUS_OBJECT | = lv_bus_object | |
| META_BUS_OBJECT | = lv_meta_bus_object | |
| . " CVVSTART_WORKFLOW_TYPE | ||
ABAP code using 7.40 inline data declarations to call FM CVVSTART_WORKFLOW_TYPE
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