SAP EMMA_INTMSG_IMP_V4 Function Module for









EMMA_INTMSG_IMP_V4 is a standard emma intmsg imp v4 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 intmsg imp v4 FM, simply by entering the name EMMA_INTMSG_IMP_V4 into the relevant SAP transaction such as SE37 or SE38.

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



Function EMMA_INTMSG_IMP_V4 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_INTMSG_IMP_V4'"
EXPORTING
IS_EMMA_INT = "
MSGTY = "Message type
OBJECT_TYPE = "Field Name
* X_CGEN = '' "

IMPORTING
ET_EXPORT_V2 = "
ET_MSGLONGTXTPAR = "

EXCEPTIONS
NOT_ALLOW = 1 NO_INTERVAL = 2
.



IMPORTING Parameters details for EMMA_INTMSG_IMP_V4

IS_EMMA_INT -

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

MSGTY - Message type

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

OBJECT_TYPE - Field Name

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

X_CGEN -

Data type: EMMA_XCGEN
Default: ''
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for EMMA_INTMSG_IMP_V4

ET_EXPORT_V2 -

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

ET_MSGLONGTXTPAR -

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

EXCEPTIONS details

NOT_ALLOW -

Data type:
Optional: No
Call by Reference: Yes

NO_INTERVAL -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for EMMA_INTMSG_IMP_V4 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_not_allow  TYPE STRING, "   
lv_is_emma_int  TYPE EMMA_INT, "   
lv_et_export_v2  TYPE EMMA_OBJ_MSG_TAB, "   
lv_msgty  TYPE SYMSGTY, "   
lv_no_interval  TYPE SYMSGTY, "   
lv_et_msglongtxtpar  TYPE EMMA_MSGLONGTXTPAR_TAB, "   
lv_object_type  TYPE FIELDNAME, "   
lv_x_cgen  TYPE EMMA_XCGEN. "   ''

  CALL FUNCTION 'EMMA_INTMSG_IMP_V4'  "
    EXPORTING
         IS_EMMA_INT = lv_is_emma_int
         MSGTY = lv_msgty
         OBJECT_TYPE = lv_object_type
         X_CGEN = lv_x_cgen
    IMPORTING
         ET_EXPORT_V2 = lv_et_export_v2
         ET_MSGLONGTXTPAR = lv_et_msglongtxtpar
    EXCEPTIONS
        NOT_ALLOW = 1
        NO_INTERVAL = 2
. " EMMA_INTMSG_IMP_V4




ABAP code using 7.40 inline data declarations to call FM EMMA_INTMSG_IMP_V4

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_x_cgen) = ''.
 


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!