SAP EMMA_CCAT_LONGTEXT_MAINTAIN Function Module for









EMMA_CCAT_LONGTEXT_MAINTAIN is a standard emma ccat longtext maintain 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 ccat longtext maintain FM, simply by entering the name EMMA_CCAT_LONGTEXT_MAINTAIN 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_CCAT_LONGTEXT_MAINTAIN 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_CCAT_LONGTEXT_MAINTAIN'"
  EXPORTING
   IV_CCAT =  "Case Category
*  IV_DISPLAY =  "
*  IT_CONT =  "

 IMPORTING
   ES_THEAD =  "SAPscript: Text Header
   ET_TLINE =  "Smart Forms: Text
   EV_TEXT_CHANGED =  "General Indicator

EXCEPTIONS
   SYSTEM_ERROR = 1
.



IMPORTING Parameters details for EMMA_CCAT_LONGTEXT_MAINTAIN

IV_CCAT - Case Category

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

IV_DISPLAY -

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

IT_CONT -

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

EXPORTING Parameters details for EMMA_CCAT_LONGTEXT_MAINTAIN

ES_THEAD - SAPscript: Text Header

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

ET_TLINE - Smart Forms: Text

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

EV_TEXT_CHANGED - General Indicator

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

EXCEPTIONS details

SYSTEM_ERROR - System Error

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for EMMA_CCAT_LONGTEXT_MAINTAIN 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_ccat  TYPE EMMA_CCAT, "   
lv_es_thead  TYPE THEAD, "   
lv_system_error  TYPE THEAD, "   
lv_et_tline  TYPE TSFTEXT, "   
lv_iv_display  TYPE FLAG, "   
lv_it_cont  TYPE SWCONTTAB, "   
lv_ev_text_changed  TYPE FLAG. "   

  CALL FUNCTION 'EMMA_CCAT_LONGTEXT_MAINTAIN'  "
    EXPORTING
         IV_CCAT = lv_iv_ccat
         IV_DISPLAY = lv_iv_display
         IT_CONT = lv_it_cont
    IMPORTING
         ES_THEAD = lv_es_thead
         ET_TLINE = lv_et_tline
         EV_TEXT_CHANGED = lv_ev_text_changed
    EXCEPTIONS
        SYSTEM_ERROR = 1
. " EMMA_CCAT_LONGTEXT_MAINTAIN




ABAP code using 7.40 inline data declarations to call FM EMMA_CCAT_LONGTEXT_MAINTAIN

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!