SAP RMXT320_MAP_VALIDATION Function Module for NOTRANSL: Set up formula X>MIN AND X
RMXT320_MAP_VALIDATION is a standard rmxt320 map validation SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Set up formula X>MIN AND X
See here to view full function module documentation and code listing for rmxt320 map validation FM, simply by entering the name RMXT320_MAP_VALIDATION into the relevant SAP transaction such as SE37 or SE38.
Function Group: RMXT320
Program Name: SAPLRMXT320
Main Program: SAPLRMXT320
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RMXT320_MAP_VALIDATION 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 'RMXT320_MAP_VALIDATION'"NOTRANSL: Set up formula X>MIN AND X EXPORTING
* IR_GR_OBJ = "Common Interface for the ROM
* IS_PP = "ROM: Attributes of the Process Parameter Object
* IS_PP_CHARS = "RMXM-TRF: Characteristic Value Assignment of Process Params
CHANGING
* CS_PI_PLFV_GR = "DE-EN-LANG-SWITCH-NO-TRANSLATION
EXCEPTIONS
ERROR_WHEN_MOVING = 1
.
IMPORTING Parameters details for RMXT320_MAP_VALIDATION
IR_GR_OBJ - Common Interface for the ROM
Data type: IF_RMXM_ROM_OBJECT
Optional: Yes
Call by Reference: Yes
IS_PP - ROM: Attributes of the Process Parameter Object
Data type: RMXMS_ROM_PP
Optional: Yes
Call by Reference: Yes
IS_PP_CHARS - RMXM-TRF: Characteristic Value Assignment of Process Params
Data type: RMXMS_ROM_PP_CHARS
Optional: Yes
Call by Reference: Yes
CHANGING Parameters details for RMXT320_MAP_VALIDATION
CS_PI_PLFV_GR - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: RMXMS_PLFV_GR
Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
ERROR_WHEN_MOVING - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:
Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RMXT320_MAP_VALIDATION 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_ir_gr_obj TYPE IF_RMXM_ROM_OBJECT, " lv_cs_pi_plfv_gr TYPE RMXMS_PLFV_GR, " lv_error_when_moving TYPE RMXMS_PLFV_GR, " lv_is_pp TYPE RMXMS_ROM_PP, " lv_is_pp_chars TYPE RMXMS_ROM_PP_CHARS. "
  CALL FUNCTION 'RMXT320_MAP_VALIDATION' "NOTRANSL: Set up formula X>MIN AND X
EXPORTING IR_GR_OBJ = lv_ir_gr_obj IS_PP = lv_is_pp IS_PP_CHARS = lv_is_pp_chars CHANGING CS_PI_PLFV_GR = lv_cs_pi_plfv_gr EXCEPTIONS ERROR_WHEN_MOVING = 1 . " RMXT320_MAP_VALIDATION
ABAP code using 7.40 inline data declarations to call FM RMXT320_MAP_VALIDATION
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!
RMXT320_MAP_VALIDATION is a standard rmxt320 map validation SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Set up formula X>MIN AND X
See here to view full function module documentation and code listing for rmxt320 map validation FM, simply by entering the name RMXT320_MAP_VALIDATION into the relevant SAP transaction such as SE37 or SE38.
Function Group: RMXT320
Program Name: SAPLRMXT320
Main Program: SAPLRMXT320
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 
Function RMXT320_MAP_VALIDATION 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 'RMXT320_MAP_VALIDATION'"NOTRANSL: Set up formula X>MIN AND X.EXPORTING
* IR_GR_OBJ = "Common Interface for the ROM
* IS_PP = "ROM: Attributes of the Process Parameter Object
* IS_PP_CHARS = "RMXM-TRF: Characteristic Value Assignment of Process Params
CHANGING
* CS_PI_PLFV_GR = "DE-EN-LANG-SWITCH-NO-TRANSLATION
EXCEPTIONS
ERROR_WHEN_MOVING = 1
IMPORTING Parameters details for RMXT320_MAP_VALIDATION
IR_GR_OBJ - Common Interface for the ROM
Data type: IF_RMXM_ROM_OBJECTOptional: Yes
Call by Reference: Yes
IS_PP - ROM: Attributes of the Process Parameter Object
Data type: RMXMS_ROM_PPOptional: Yes
Call by Reference: Yes
IS_PP_CHARS - RMXM-TRF: Characteristic Value Assignment of Process Params
Data type: RMXMS_ROM_PP_CHARSOptional: Yes
Call by Reference: Yes
CHANGING Parameters details for RMXT320_MAP_VALIDATION
CS_PI_PLFV_GR - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: RMXMS_PLFV_GROptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ERROR_WHEN_MOVING - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RMXT320_MAP_VALIDATION 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_ir_gr_obj | TYPE IF_RMXM_ROM_OBJECT, " | |||
| lv_cs_pi_plfv_gr | TYPE RMXMS_PLFV_GR, " | |||
| lv_error_when_moving | TYPE RMXMS_PLFV_GR, " | |||
| lv_is_pp | TYPE RMXMS_ROM_PP, " | |||
| lv_is_pp_chars | TYPE RMXMS_ROM_PP_CHARS. " |
|   CALL FUNCTION 'RMXT320_MAP_VALIDATION' "NOTRANSL: Set up formula X>MIN AND X |
| EXPORTING | ||
| IR_GR_OBJ | = lv_ir_gr_obj | |
| IS_PP | = lv_is_pp | |
| IS_PP_CHARS | = lv_is_pp_chars | |
| CHANGING | ||
| CS_PI_PLFV_GR | = lv_cs_pi_plfv_gr | |
| EXCEPTIONS | ||
| ERROR_WHEN_MOVING = 1 | ||
| . " RMXT320_MAP_VALIDATION | ||
ABAP code using 7.40 inline data declarations to call FM RMXT320_MAP_VALIDATION
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