SAP EMMA_CASE_TRANSACTION_START Function Module for
EMMA_CASE_TRANSACTION_START is a standard emma case transaction start SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 emma case transaction start FM, simply by entering the name EMMA_CASE_TRANSACTION_START into the relevant SAP transaction such as SE37 or SE38.
Function Group: EMMA_CASE_TRANSACTION
Program Name: SAPLEMMA_CASE_TRANSACTION
Main Program: SAPLEMMA_CASE_TRANSACTION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EMMA_CASE_TRANSACTION_START 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 'EMMA_CASE_TRANSACTION_START'".
EXPORTING
* IV_CASENR = "Case
* IV_CCAT = "Case Category
* IV_TEMPLATE_CASE = "Case
IV_WMODE = "Work Mode for Case Transaction
* IV_ALLOW_TOGGLE_DISPCHAN = ' ' "Permit Switch between Display and Change Mode
* IV_NEXT_PREV_CASE = '0' "Ind: '1' and '3' Next Case, '2' and '3' Previous Case
IMPORTING
EV_CASENR = "Case Number
EV_OKCODE = "Function Code That Triggered PAI
EXCEPTIONS
CASE_NOT_FOUND = 1 INCORRECT_WORKMODE = 2 INCORRECT_PARAMETERS = 3
IMPORTING Parameters details for EMMA_CASE_TRANSACTION_START
IV_CASENR - Case
Data type: EMMA_CNROptional: Yes
Call by Reference: Yes
IV_CCAT - Case Category
Data type: EMMA_CCATOptional: Yes
Call by Reference: Yes
IV_TEMPLATE_CASE - Case
Data type: EMMA_CNROptional: Yes
Call by Reference: Yes
IV_WMODE - Work Mode for Case Transaction
Data type: EMMA_CTXN_WMODEOptional: No
Call by Reference: Yes
IV_ALLOW_TOGGLE_DISPCHAN - Permit Switch between Display and Change Mode
Data type: FLAGDefault: ' '
Optional: Yes
Call by Reference: Yes
IV_NEXT_PREV_CASE - Ind: '1' and '3' Next Case, '2' and '3' Previous Case
Data type: NUM1Default: '0'
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for EMMA_CASE_TRANSACTION_START
EV_CASENR - Case Number
Data type: EMMA_CNROptional: No
Call by Reference: Yes
EV_OKCODE - Function Code That Triggered PAI
Data type: SYUCOMMOptional: No
Call by Reference: Yes
EXCEPTIONS details
CASE_NOT_FOUND - Case Not Found
Data type:Optional: No
Call by Reference: Yes
INCORRECT_WORKMODE - Incorrect Work Mode
Data type:Optional: No
Call by Reference: Yes
INCORRECT_PARAMETERS - Incorrect Parameter
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for EMMA_CASE_TRANSACTION_START 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_ev_casenr | TYPE EMMA_CNR, " | |||
| lv_iv_casenr | TYPE EMMA_CNR, " | |||
| lv_case_not_found | TYPE EMMA_CNR, " | |||
| lv_iv_ccat | TYPE EMMA_CCAT, " | |||
| lv_ev_okcode | TYPE SYUCOMM, " | |||
| lv_incorrect_workmode | TYPE SYUCOMM, " | |||
| lv_iv_template_case | TYPE EMMA_CNR, " | |||
| lv_incorrect_parameters | TYPE EMMA_CNR, " | |||
| lv_iv_wmode | TYPE EMMA_CTXN_WMODE, " | |||
| lv_iv_allow_toggle_dispchan | TYPE FLAG, " ' ' | |||
| lv_iv_next_prev_case | TYPE NUM1. " '0' |
|   CALL FUNCTION 'EMMA_CASE_TRANSACTION_START' " |
| EXPORTING | ||
| IV_CASENR | = lv_iv_casenr | |
| IV_CCAT | = lv_iv_ccat | |
| IV_TEMPLATE_CASE | = lv_iv_template_case | |
| IV_WMODE | = lv_iv_wmode | |
| IV_ALLOW_TOGGLE_DISPCHAN | = lv_iv_allow_toggle_dispchan | |
| IV_NEXT_PREV_CASE | = lv_iv_next_prev_case | |
| IMPORTING | ||
| EV_CASENR | = lv_ev_casenr | |
| EV_OKCODE | = lv_ev_okcode | |
| EXCEPTIONS | ||
| CASE_NOT_FOUND = 1 | ||
| INCORRECT_WORKMODE = 2 | ||
| INCORRECT_PARAMETERS = 3 | ||
| . " EMMA_CASE_TRANSACTION_START | ||
ABAP code using 7.40 inline data declarations to call FM EMMA_CASE_TRANSACTION_START
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.| DATA(ld_iv_allow_toggle_dispchan) | = ' '. | |||
| DATA(ld_iv_next_prev_case) | = '0'. | |||
Search for further information about these or an SAP related objects