SAP EHS00_MPC04_ENTRY Function Module for









EHS00_MPC04_ENTRY is a standard ehs00 mpc04 entry 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 ehs00 mpc04 entry FM, simply by entering the name EHS00_MPC04_ENTRY into the relevant SAP transaction such as SE37 or SE38.

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



Function EHS00_MPC04_ENTRY 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 'EHS00_MPC04_ENTRY'"
EXPORTING
I_ACTYPE = "
* I_TRTYPE = "

EXCEPTIONS
PARAMETER_ERROR = 1
.



IMPORTING Parameters details for EHS00_MPC04_ENTRY

I_ACTYPE -

Data type: RCGDIALCTR-ACTYPE
Optional: No
Call by Reference: Yes

I_TRTYPE -

Data type: RCGDIALCTR-TRTYPE
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

PARAMETER_ERROR -

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

Copy and paste ABAP code example for EHS00_MPC04_ENTRY 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_i_actype  TYPE RCGDIALCTR-ACTYPE, "   
lv_parameter_error  TYPE RCGDIALCTR, "   
lv_i_trtype  TYPE RCGDIALCTR-TRTYPE. "   

  CALL FUNCTION 'EHS00_MPC04_ENTRY'  "
    EXPORTING
         I_ACTYPE = lv_i_actype
         I_TRTYPE = lv_i_trtype
    EXCEPTIONS
        PARAMETER_ERROR = 1
. " EHS00_MPC04_ENTRY




ABAP code using 7.40 inline data declarations to call FM EHS00_MPC04_ENTRY

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.

"SELECT single ACTYPE FROM RCGDIALCTR INTO @DATA(ld_i_actype).
 
 
"SELECT single TRTYPE FROM RCGDIALCTR INTO @DATA(ld_i_trtype).
 


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!