SAP CACS_WFCASE_TRIGGER_RUN Function Module for NOTRANSL: Workflow for Case: Trigger

Search SAP Function Modules

CACS_WFCASE_TRIGGER_RUN is a standard cacs wfcase trigger run 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 for Case: Trigger 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 cacs wfcase trigger run FM, simply by entering the name CACS_WFCASE_TRIGGER_RUN into the relevant SAP transaction such as SE37 or SE38.

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

Function CACS_WFCASE_TRIGGER_RUN 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 'CACS_WFCASE_TRIGGER_RUN'"NOTRANSL: Workflow for Case: Trigger
  EXPORTING
*  ID_APPL =  "Commission Application Identification
*  ID_EXT_RUN_ID =  "Identification Number of External Processing Run
   ID_THRESHOLD_SINGLE =  "Threshold Value: Single Record Processing
*  IB_IGNORE_THRESHOLD = ' ' "Indicator: Ignore Threshold Values
*  IB_UPDATE_TASK = 'X' "Boolean Variables (X=true, space=false)
*  IB_SIMULATION = ' ' "Boolean Variables (X=true, space=false)
*  IB_COMMIT_WORK = 'X' "Boolean Variables (X=true, space=false)
*  IB_SHOW_LOG = 'X' "Boolean Variables (X=true, space=false)

CHANGING
*  CO_LOG =  "CACS: Application Log

EXCEPTIONS
   CX_CACS_BAL_EX = 1 

.

IMPORTING Parameters details for CACS_WFCASE_TRIGGER_RUN

ID_APPL - Commission Application Identification

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

ID_EXT_RUN_ID - Identification Number of External Processing Run

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

ID_THRESHOLD_SINGLE - Threshold Value: Single Record Processing

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

IB_IGNORE_THRESHOLD - Indicator: Ignore Threshold Values

Data type: CACS_WFTHRESIGNORE
Default: SPACE
Optional: Yes
Call by Reference: Yes

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

Data type: BOOLEAN_FLG
Default: 'X'
Optional: Yes
Call by Reference: Yes

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

Data type: BOOLEAN_FLG
Default: SPACE
Optional: Yes
Call by Reference: Yes

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

Data type: BOOLEAN_FLG
Default: 'X'
Optional: Yes
Call by Reference: Yes

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

Data type: BOOLEAN_FLG
Default: 'X'
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for CACS_WFCASE_TRIGGER_RUN

CO_LOG - CACS: Application Log

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

EXCEPTIONS details

CX_CACS_BAL_EX - CACS: Application Log Exceptions

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CACS_WFCASE_TRIGGER_RUN 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.

ABAP code using 7.40 inline data declarations to call FM CACS_WFCASE_TRIGGER_RUN

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