SAP EMMA_CASE_SOLPATH_UPDATE Function Module for









EMMA_CASE_SOLPATH_UPDATE is a standard emma case solpath update 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 solpath update FM, simply by entering the name EMMA_CASE_SOLPATH_UPDATE into the relevant SAP transaction such as SE37 or SE38.

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



Function EMMA_CASE_SOLPATH_UPDATE 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_SOLPATH_UPDATE'"
EXPORTING
IV_CASENR = "
IT_CSOP = "

EXCEPTIONS
NOT_FOUND = 1 NOT_AUTHORIZED = 2 UPDATE_ERROR = 3
.



IMPORTING Parameters details for EMMA_CASE_SOLPATH_UPDATE

IV_CASENR -

Data type: EMMA_CNR
Optional: No
Call by Reference: No ( called with pass by value option)

IT_CSOP -

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

EXCEPTIONS details

NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

NOT_AUTHORIZED -

Data type:
Optional: No
Call by Reference: Yes

UPDATE_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for EMMA_CASE_SOLPATH_UPDATE 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_iv_casenr  TYPE EMMA_CNR, "   
lv_not_found  TYPE EMMA_CNR, "   
lv_it_csop  TYPE EMMA_CSOP_T, "   
lv_not_authorized  TYPE EMMA_CSOP_T, "   
lv_update_error  TYPE EMMA_CSOP_T. "   

  CALL FUNCTION 'EMMA_CASE_SOLPATH_UPDATE'  "
    EXPORTING
         IV_CASENR = lv_iv_casenr
         IT_CSOP = lv_it_csop
    EXCEPTIONS
        NOT_FOUND = 1
        NOT_AUTHORIZED = 2
        UPDATE_ERROR = 3
. " EMMA_CASE_SOLPATH_UPDATE




ABAP code using 7.40 inline data declarations to call FM EMMA_CASE_SOLPATH_UPDATE

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!