SAP MEREP_DEFAULTVALUE_GET Function Module for Get a Default Value
MEREP_DEFAULTVALUE_GET is a standard merep defaultvalue get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get a Default Value processing and below is the pattern details for this FM, 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 merep defaultvalue get FM, simply by entering the name MEREP_DEFAULTVALUE_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: MEREP_RUNTIME
Program Name: SAPLMEREP_RUNTIME
Main Program: SAPLMEREP_RUNTIME
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MEREP_DEFAULTVALUE_GET 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 'MEREP_DEFAULTVALUE_GET'"Get a Default Value.
EXPORTING
VALUEID = "SAP Mobile: Value ID
IMPORTING
PARAVALUE = "SAP Mobile: Parameter value
TABLES
I_VALUE = "SAP Mobile: Loaded defalt values
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for MEREP_DEFAULTVALUE_GET
VALUEID - SAP Mobile: Value ID
Data type: MEREP_406-VALUEIDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MEREP_DEFAULTVALUE_GET
PARAVALUE - SAP Mobile: Parameter value
Data type: MEREP_407-PARAVALUEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MEREP_DEFAULTVALUE_GET
I_VALUE - SAP Mobile: Loaded defalt values
Data type: MEREP_DVALSOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MEREP_DEFAULTVALUE_GET 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: | ||||
| lt_i_value | TYPE STANDARD TABLE OF MEREP_DVALS, " | |||
| lv_valueid | TYPE MEREP_406-VALUEID, " | |||
| lv_not_found | TYPE MEREP_406, " | |||
| lv_paravalue | TYPE MEREP_407-PARAVALUE. " |
|   CALL FUNCTION 'MEREP_DEFAULTVALUE_GET' "Get a Default Value |
| EXPORTING | ||
| VALUEID | = lv_valueid | |
| IMPORTING | ||
| PARAVALUE | = lv_paravalue | |
| TABLES | ||
| I_VALUE | = lt_i_value | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " MEREP_DEFAULTVALUE_GET | ||
ABAP code using 7.40 inline data declarations to call FM MEREP_DEFAULTVALUE_GET
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 VALUEID FROM MEREP_406 INTO @DATA(ld_valueid). | ||||
| "SELECT single PARAVALUE FROM MEREP_407 INTO @DATA(ld_paravalue). | ||||
Search for further information about these or an SAP related objects