SAP CNV_NCE_GET_ME_SOBJ_MAP_OBJ Function Module for Check if ME mappings have been changed

Search SAP Function Modules

CNV_NCE_GET_ME_SOBJ_MAP_OBJ is a standard cnv nce get me sobj map obj SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check if ME mappings have been changed 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 get me sobj map obj FM, simply by entering the name CNV_NCE_GET_ME_SOBJ_MAP_OBJ into the relevant SAP transaction such as SE37 or SE38.

Function Group: CNV_NCE_BAS_SP1
Program Name: SAPLCNV_NCE_BAS_SP1
Main Program: SAPLCNV_NCE_BAS_SP1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CNV_NCE_GET_ME_SOBJ_MAP_OBJ 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_GET_ME_SOBJ_MAP_OBJ'"Check if ME mappings have been changed
  EXPORTING
   IV_GUID =  "NCE project identifier GUID
   IV_OBJECT =  "Name of number range object
*  IF_SAVE = 'X' "Save data
*  IF_COMPARE =  "Compare new mappings with existing ones

 IMPORTING
   ET_SOMAPS =  "Subobject mappings
   ET_SOCHGS =  "Changes in subobject mappings
   ET_NRMAPS =  "NR range mappings
   ET_NRCHGS =  "Changes in NR range mappings
   EF_ANALYSIS =  "DB analysis should be repeated
   EF_NO_MAP =  "Subobject mappings not maintained

EXCEPTIONS
   GUID_NOT_FOUND = 1    OBJ_NOT_FOUND = 2    CLASS_NOT_FOUND = 3    NO_CLASS = 4    ERROR = 5 

.

IMPORTING Parameters details for CNV_NCE_GET_ME_SOBJ_MAP_OBJ

IV_GUID - NCE project identifier GUID

Data type: CNV_NCE_GUID
Optional: No
Call by Reference: Yes

IV_OBJECT - Name of number range object

Data type: NROBJ
Optional: No
Call by Reference: Yes

IF_SAVE - Save data

Data type: ABAP_BOOL
Default: 'X'
Optional: Yes
Call by Reference: Yes

IF_COMPARE - Compare new mappings with existing ones

Data type: ABAP_BOOL
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for CNV_NCE_GET_ME_SOBJ_MAP_OBJ

ET_SOMAPS - Subobject mappings

Data type: CNV_NCE_T_SOBJ_MAP
Optional: No
Call by Reference: Yes

ET_SOCHGS - Changes in subobject mappings

Data type: CNV_NCE_T_SOMAP_CHANGE
Optional: No
Call by Reference: Yes

ET_NRMAPS - NR range mappings

Data type: CNV_NCE_T_NRID_MAP
Optional: No
Call by Reference: Yes

ET_NRCHGS - Changes in NR range mappings

Data type: CNV_NCE_T_NRMAP_CHANGE
Optional: No
Call by Reference: Yes

EF_ANALYSIS - DB analysis should be repeated

Data type: ABAP_BOOL
Optional: No
Call by Reference: Yes

EF_NO_MAP - Subobject mappings not maintained

Data type: ABAP_BOOL
Optional: No
Call by Reference: Yes

EXCEPTIONS details

GUID_NOT_FOUND - GUID does not exist

Data type:
Optional: No
Call by Reference: Yes

OBJ_NOT_FOUND - Object is not found

Data type:
Optional: No
Call by Reference: Yes

CLASS_NOT_FOUND - Mapping class is not found

Data type:
Optional: No
Call by Reference: Yes

NO_CLASS - Mapping class is not provided

Data type:
Optional: No
Call by Reference: Yes

ERROR - Error returned by internal FM calls

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CNV_NCE_GET_ME_SOBJ_MAP_OBJ 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.

ABAP code using 7.40 inline data declarations to call FM CNV_NCE_GET_ME_SOBJ_MAP_OBJ

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