SAP CNV_NCE_MAPPING_UI_RFC Function Module for NCE mappings maintenance and synchronization
CNV_NCE_MAPPING_UI_RFC is a standard cnv nce mapping ui rfc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NCE mappings maintenance and synchronization 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 cnv nce mapping ui rfc FM, simply by entering the name CNV_NCE_MAPPING_UI_RFC into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNV_NCE_RFC
Program Name: SAPLCNV_NCE_RFC
Main Program: SAPLCNV_NCE_RFC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CNV_NCE_MAPPING_UI_RFC 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 'CNV_NCE_MAPPING_UI_RFC'"NCE mappings maintenance and synchronization.
EXPORTING
IV_GUID = "NCE project identifier
IV_ACTIVITY = "NCE activity
* IF_EDIT = ' ' "Edit mode
* IF_EXPERT = ' ' "Expert mode
* IV_OBJECTS = ' ' "Process only selected objects
IMPORTING
ET_MSG = "Messages
EV_MAX_ERROR = "Messages, message type
TABLES
* IT_OBJECTS = "Number range Objects
EXCEPTIONS
NO_GUID_PRESENT = 1 GUID_NOT_FOUND = 2 UI_INIT_ERROR = 3 SYSTEM_FAILURE = 4 CANCELED_BY_USER = 5 NO_SYS_INFO = 6 SOURCE_CONNECTION_FAILED = 7 NOT_CONTROL_SYSTEM = 8
IMPORTING Parameters details for CNV_NCE_MAPPING_UI_RFC
IV_GUID - NCE project identifier
Data type: CNV_NCE_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
IV_ACTIVITY - NCE activity
Data type: CNV_NCE_ACTIVITYOptional: No
Call by Reference: No ( called with pass by value option)
IF_EDIT - Edit mode
Data type: CNV_NCE_EDITDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IF_EXPERT - Expert mode
Data type: CNV_NCE_BOOLDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_OBJECTS - Process only selected objects
Data type: CNV_NCE_BOOLDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CNV_NCE_MAPPING_UI_RFC
ET_MSG - Messages
Data type: CNV_NCE_T_MSGOptional: No
Call by Reference: No ( called with pass by value option)
EV_MAX_ERROR - Messages, message type
Data type: SYMSGTYOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CNV_NCE_MAPPING_UI_RFC
IT_OBJECTS - Number range Objects
Data type: CNV_NCE_S_NROBJOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NO_GUID_PRESENT - GUID value is initial
Data type:Optional: No
Call by Reference: Yes
GUID_NOT_FOUND - GUID does not exist
Data type:Optional: No
Call by Reference: Yes
UI_INIT_ERROR - Error occured during UI initialization
Data type:Optional: No
Call by Reference: Yes
SYSTEM_FAILURE - SAP table lock failed
Data type:Optional: No
Call by Reference: Yes
CANCELED_BY_USER - Dialog was canceled by user
Data type:Optional: No
Call by Reference: Yes
NO_SYS_INFO - No information about systems found
Data type:Optional: No
Call by Reference: Yes
SOURCE_CONNECTION_FAILED - Connection to a source system failed
Data type:Optional: No
Call by Reference: Yes
NOT_CONTROL_SYSTEM - Execution in this system is not permitted
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CNV_NCE_MAPPING_UI_RFC 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_et_msg | TYPE CNV_NCE_T_MSG, " | |||
| lv_iv_guid | TYPE CNV_NCE_GUID, " | |||
| lt_it_objects | TYPE STANDARD TABLE OF CNV_NCE_S_NROBJ, " | |||
| lv_no_guid_present | TYPE CNV_NCE_S_NROBJ, " | |||
| lv_iv_activity | TYPE CNV_NCE_ACTIVITY, " | |||
| lv_ev_max_error | TYPE SYMSGTY, " | |||
| lv_guid_not_found | TYPE SYMSGTY, " | |||
| lv_if_edit | TYPE CNV_NCE_EDIT, " SPACE | |||
| lv_ui_init_error | TYPE CNV_NCE_EDIT, " | |||
| lv_if_expert | TYPE CNV_NCE_BOOL, " SPACE | |||
| lv_system_failure | TYPE CNV_NCE_BOOL, " | |||
| lv_iv_objects | TYPE CNV_NCE_BOOL, " SPACE | |||
| lv_canceled_by_user | TYPE CNV_NCE_BOOL, " | |||
| lv_no_sys_info | TYPE CNV_NCE_BOOL, " | |||
| lv_source_connection_failed | TYPE CNV_NCE_BOOL, " | |||
| lv_not_control_system | TYPE CNV_NCE_BOOL. " |
|   CALL FUNCTION 'CNV_NCE_MAPPING_UI_RFC' "NCE mappings maintenance and synchronization |
| EXPORTING | ||
| IV_GUID | = lv_iv_guid | |
| IV_ACTIVITY | = lv_iv_activity | |
| IF_EDIT | = lv_if_edit | |
| IF_EXPERT | = lv_if_expert | |
| IV_OBJECTS | = lv_iv_objects | |
| IMPORTING | ||
| ET_MSG | = lv_et_msg | |
| EV_MAX_ERROR | = lv_ev_max_error | |
| TABLES | ||
| IT_OBJECTS | = lt_it_objects | |
| EXCEPTIONS | ||
| NO_GUID_PRESENT = 1 | ||
| GUID_NOT_FOUND = 2 | ||
| UI_INIT_ERROR = 3 | ||
| SYSTEM_FAILURE = 4 | ||
| CANCELED_BY_USER = 5 | ||
| NO_SYS_INFO = 6 | ||
| SOURCE_CONNECTION_FAILED = 7 | ||
| NOT_CONTROL_SYSTEM = 8 | ||
| . " CNV_NCE_MAPPING_UI_RFC | ||
ABAP code using 7.40 inline data declarations to call FM CNV_NCE_MAPPING_UI_RFC
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.| DATA(ld_if_edit) | = ' '. | |||
| DATA(ld_if_expert) | = ' '. | |||
| DATA(ld_iv_objects) | = ' '. | |||
Search for further information about these or an SAP related objects