RMXT320_MAP_VALIDATION_EXT SAP Function module

RMXT320_MAP_VALIDATION_EXT is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name RMXT320_MAP_VALIDATION_EXT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: RMXT320
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM RMXT320_MAP_VALIDATION_EXT - RMXT320 MAP VALIDATION EXT

CALL FUNCTION 'RMXT320_MAP_VALIDATION_EXT' "
* EXPORTING
*   ir_gr_obj =                 " if_rmxm_rom_object
*   is_pp =                     " rmxms_rom_pp
*   is_pp_chars =               " rmxms_rom_pp_chars
*   it_pp_chars =               " rmxmty_rom_pp_chars
* CHANGING
*   cs_pi_plfv_gr =             " rmxms_plfv_gr
  EXCEPTIONS
    ERROR_WHEN_MOVING = 1       "
    .  "  RMXT320_MAP_VALIDATION_EXT

ABAP code example for Function Module RMXT320_MAP_VALIDATION_EXT

The ABAP code below is a full code listing to execute function module RMXT320_MAP_VALIDATION_EXT including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA(ld_cs_pi_plfv_gr) = 'Check type of data required'.

DATA(ld_ir_gr_obj) = 'Check type of data required'.

DATA(ld_is_pp) = 'Check type of data required'.

DATA(ld_is_pp_chars) = 'Check type of data required'.

DATA(ld_it_pp_chars) = 'Check type of data required'.
.

CALL FUNCTION 'RMXT320_MAP_VALIDATION_EXT'
* EXPORTING
*   ir_gr_obj =                  ld_ir_gr_obj
*   is_pp =                      ld_is_pp
*   is_pp_chars =                ld_is_pp_chars
*   it_pp_chars =                ld_it_pp_chars
* CHANGING
*   cs_pi_plfv_gr =              ld_cs_pi_plfv_gr
  EXCEPTIONS
    ERROR_WHEN_MOVING =          1
    .  "  RMXT320_MAP_VALIDATION_EXT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_cs_pi_plfv_gr
 
 TYPE RMXMS_PLFV_GR ,
ld_ir_gr_obj
 
 TYPE IF_RMXM_ROM_OBJECT ,
ld_is_pp
 
 TYPE RMXMS_ROM_PP ,
ld_is_pp_chars
 
 TYPE RMXMS_ROM_PP_CHARS ,
ld_it_pp_chars
 
 TYPE RMXMTY_ROM_PP_CHARS .


ld_cs_pi_plfv_gr = 'Check type of data required'.
ld_ir_gr_obj = 'Check type of data required'.
ld_is_pp = 'Check type of data required'.
ld_is_pp_chars = 'Check type of data required'.
ld_it_pp_chars = 'Check type of data required'.