CNV_NCE_SINGLE_MAP_CHECK SAP Function module - Completeness check for a single mapping entry

CNV_NCE_SINGLE_MAP_CHECK 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 CNV_NCE_SINGLE_MAP_CHECK into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM CNV_NCE_SINGLE_MAP_CHECK - CNV NCE SINGLE MAP CHECK

CALL FUNCTION 'CNV_NCE_SINGLE_MAP_CHECK' "Completeness check for a single mapping entry
  EXPORTING
    i_object =                  " nrobj         Name of number range object
    i_log_source =              " cnv_nce_log_source  Source of log entry
    i_row_id =                  " int4          ALV row ID
  IMPORTING
    e_stat =                    " cnv_nce_maint_state  Maintenance state of number range mapping
    e_icon =                    " cnv_nce_maint_icon  Maintenance state icon
  CHANGING
    is_nriv_map =               " cnv_nce_nriv_map  Work structure for NRIV mapping
    it_log_msg =                " cnv_nce_t_msg  Table type for BAL_S_MSG
    .  "  CNV_NCE_SINGLE_MAP_CHECK

ABAP code example for Function Module CNV_NCE_SINGLE_MAP_CHECK

The ABAP code below is a full code listing to execute function module CNV_NCE_SINGLE_MAP_CHECK 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_e_stat  
 
 TYPE CNV_NCE_MAINT_STATE
,
ld_e_icon  
 
 TYPE CNV_NCE_MAINT_ICON
.


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

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

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

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

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

CALL FUNCTION 'CNV_NCE_SINGLE_MAP_CHECK'
  EXPORTING
    i_object =                   ld_i_object
    i_log_source =               ld_i_log_source
    i_row_id =                   ld_i_row_id
  IMPORTING
    e_stat =                     ld_e_stat
    e_icon =                     ld_e_icon
  CHANGING
    is_nriv_map =                ld_is_nriv_map
    it_log_msg =                 ld_it_log_msg
    .  "  CNV_NCE_SINGLE_MAP_CHECK

IF SY-SUBRC EQ 0.
  "All OK
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_is_nriv_map
 
 TYPE CNV_NCE_NRIV_MAP ,
ld_e_stat
 
 TYPE CNV_NCE_MAINT_STATE ,
ld_i_object
 
 TYPE NROBJ ,
ld_it_log_msg
 
 TYPE CNV_NCE_T_MSG ,
ld_e_icon
 
 TYPE CNV_NCE_MAINT_ICON ,
ld_i_log_source
 
 TYPE CNV_NCE_LOG_SOURCE ,
ld_i_row_id
 
 TYPE INT4 .


ld_is_nriv_map = 'Check type of data required'.
ld_i_object = 'Check type of data required'.
ld_it_log_msg = 'Check type of data required'.
ld_i_log_source = 'Check type of data required'.
ld_i_row_id = 'Check type of data required'.