SAP CACSWF_CASE_WORKFLOW_TRIGGER Function Module for NOTRANSL: Workflow: Trigger Provisionsfall









CACSWF_CASE_WORKFLOW_TRIGGER is a standard cacswf case workflow trigger 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: Workflow: Trigger Provisionsfall 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 cacswf case workflow trigger FM, simply by entering the name CACSWF_CASE_WORKFLOW_TRIGGER into the relevant SAP transaction such as SE37 or SE38.

Function Group: CACSWF_WFCASE
Program Name: SAPLCACSWF_WFCASE
Main Program: SAPLCACSWF_WFCASE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CACSWF_CASE_WORKFLOW_TRIGGER 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 'CACSWF_CASE_WORKFLOW_TRIGGER'"NOTRANSL: Workflow: Trigger Provisionsfall
  EXPORTING
   ID_IMPORT_YEAR =  "Year Commission Case Reported
   ID_TRI_METH_TYP =  "Processing Type
   IB_UPDATE_TASK =  "Boolean Variables (X=true, space=false)
   IB_MASS_PROCESS =  "Boolean Variables (X=true, space=false)
   IB_SIMULATION =  "Boolean Variables (X=true, space=false)
   ID_CASE_ID =  "Case Identification
   ID_CASE_VERS =  "Version of Master Data or Customizing Object
*  ID_PREV_IMPORT_YEAR =  "Year Commission Case Reported
*  ID_PREV_CASE_ID =  "Case Identification
*  ID_PREV_CASE_VERS =  "Version of Master Data or Customizing Object
   ID_BUSOBJ_TYPE =  "Business Object Category that Triggers Commission
   ID_EXT_RUN_ID =  "Identification Number of External Processing Run
   ID_STATUS_WORK =  "Object Version Processing Status
.



IMPORTING Parameters details for CACSWF_CASE_WORKFLOW_TRIGGER

ID_IMPORT_YEAR - Year Commission Case Reported

Data type: CACSIMPYEAR
Optional: No
Call by Reference: Yes

ID_TRI_METH_TYP - Processing Type

Data type: CACSOPTYPE
Optional: No
Call by Reference: Yes

IB_UPDATE_TASK - Boolean Variables (X=true, space=false)

Data type: BOOLEAN_FLG
Optional: No
Call by Reference: Yes

IB_MASS_PROCESS - Boolean Variables (X=true, space=false)

Data type: BOOLEAN_FLG
Optional: No
Call by Reference: Yes

IB_SIMULATION - Boolean Variables (X=true, space=false)

Data type: BOOLEAN_FLG
Optional: No
Call by Reference: Yes

ID_CASE_ID - Case Identification

Data type: CACSCASEID
Optional: No
Call by Reference: Yes

ID_CASE_VERS - Version of Master Data or Customizing Object

Data type: CACSVERSION
Optional: No
Call by Reference: Yes

ID_PREV_IMPORT_YEAR - Year Commission Case Reported

Data type: CACSIMPYEAR
Optional: Yes
Call by Reference: Yes

ID_PREV_CASE_ID - Case Identification

Data type: CACSCASEID
Optional: Yes
Call by Reference: Yes

ID_PREV_CASE_VERS - Version of Master Data or Customizing Object

Data type: CACSVERSION
Optional: Yes
Call by Reference: Yes

ID_BUSOBJ_TYPE - Business Object Category that Triggers Commission

Data type: CACSBUSOBJTYP
Optional: No
Call by Reference: Yes

ID_EXT_RUN_ID - Identification Number of External Processing Run

Data type: CACSBATCHEXT
Optional: No
Call by Reference: Yes

ID_STATUS_WORK - Object Version Processing Status

Data type: CACSSTATUSWORK
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CACSWF_CASE_WORKFLOW_TRIGGER 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_id_import_year  TYPE CACSIMPYEAR, "   
lv_id_tri_meth_typ  TYPE CACSOPTYPE, "   
lv_ib_update_task  TYPE BOOLEAN_FLG, "   
lv_ib_mass_process  TYPE BOOLEAN_FLG, "   
lv_ib_simulation  TYPE BOOLEAN_FLG, "   
lv_id_case_id  TYPE CACSCASEID, "   
lv_id_case_vers  TYPE CACSVERSION, "   
lv_id_prev_import_year  TYPE CACSIMPYEAR, "   
lv_id_prev_case_id  TYPE CACSCASEID, "   
lv_id_prev_case_vers  TYPE CACSVERSION, "   
lv_id_busobj_type  TYPE CACSBUSOBJTYP, "   
lv_id_ext_run_id  TYPE CACSBATCHEXT, "   
lv_id_status_work  TYPE CACSSTATUSWORK. "   

  CALL FUNCTION 'CACSWF_CASE_WORKFLOW_TRIGGER'  "NOTRANSL: Workflow: Trigger Provisionsfall
    EXPORTING
         ID_IMPORT_YEAR = lv_id_import_year
         ID_TRI_METH_TYP = lv_id_tri_meth_typ
         IB_UPDATE_TASK = lv_ib_update_task
         IB_MASS_PROCESS = lv_ib_mass_process
         IB_SIMULATION = lv_ib_simulation
         ID_CASE_ID = lv_id_case_id
         ID_CASE_VERS = lv_id_case_vers
         ID_PREV_IMPORT_YEAR = lv_id_prev_import_year
         ID_PREV_CASE_ID = lv_id_prev_case_id
         ID_PREV_CASE_VERS = lv_id_prev_case_vers
         ID_BUSOBJ_TYPE = lv_id_busobj_type
         ID_EXT_RUN_ID = lv_id_ext_run_id
         ID_STATUS_WORK = lv_id_status_work
. " CACSWF_CASE_WORKFLOW_TRIGGER




ABAP code using 7.40 inline data declarations to call FM CACSWF_CASE_WORKFLOW_TRIGGER

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!