SAP CNV_NCE_LOAD_MESSAGES_OBJ_RFC Function Module for Load messages









CNV_NCE_LOAD_MESSAGES_OBJ_RFC is a standard cnv nce load messages obj 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 Load messages 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 load messages obj rfc FM, simply by entering the name CNV_NCE_LOAD_MESSAGES_OBJ_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_LOAD_MESSAGES_OBJ_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_LOAD_MESSAGES_OBJ_RFC'"Load messages
  EXPORTING
   IV_GUID =  "NCE project identifier
   IV_ACTIVITY =  "NCE activity
   IV_OBJECT =  "Name of number range object
*  IV_SUBOBJECT =  "Number range object subobject value

 IMPORTING
   ET_MSG_SRC =  "Source system messages
   ET_MSG_TRG =  "Target system messages
   EF_CROSS =  "Cross-system project

EXCEPTIONS
   GUID_NOT_FOUND = 1    JOB_IS_RUNNING = 2    NO_SYS_INFO = 3    SOURCE_CONNECTION_FAILED = 4    TARGET_CONNECTION_FAILED = 5    NOT_CONTROL_SYSTEM = 6
.



IMPORTING Parameters details for CNV_NCE_LOAD_MESSAGES_OBJ_RFC

IV_GUID - NCE project identifier

Data type: CNV_NCE_GUID
Optional: No
Call by Reference: No ( called with pass by value option)

IV_ACTIVITY - NCE activity

Data type: CNV_NCE_ACTIVITY
Optional: No
Call by Reference: No ( called with pass by value option)

IV_OBJECT - Name of number range object

Data type: NROBJ
Optional: No
Call by Reference: No ( called with pass by value option)

IV_SUBOBJECT - Number range object subobject value

Data type: NRSOBJ
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CNV_NCE_LOAD_MESSAGES_OBJ_RFC

ET_MSG_SRC - Source system messages

Data type: CNV_NCE_T_MSG
Optional: No
Call by Reference: No ( called with pass by value option)

ET_MSG_TRG - Target system messages

Data type: CNV_NCE_T_MSG
Optional: No
Call by Reference: No ( called with pass by value option)

EF_CROSS - Cross-system project

Data type: CNV_NCE_BOOL
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

GUID_NOT_FOUND - GUID does not exist

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

JOB_IS_RUNNING - At least one job is still running

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

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

TARGET_CONNECTION_FAILED - Connection to a target 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_LOAD_MESSAGES_OBJ_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_iv_guid  TYPE CNV_NCE_GUID, "   
lv_et_msg_src  TYPE CNV_NCE_T_MSG, "   
lv_guid_not_found  TYPE CNV_NCE_T_MSG, "   
lv_et_msg_trg  TYPE CNV_NCE_T_MSG, "   
lv_iv_activity  TYPE CNV_NCE_ACTIVITY, "   
lv_job_is_running  TYPE CNV_NCE_ACTIVITY, "   
lv_ef_cross  TYPE CNV_NCE_BOOL, "   
lv_iv_object  TYPE NROBJ, "   
lv_no_sys_info  TYPE NROBJ, "   
lv_iv_subobject  TYPE NRSOBJ, "   
lv_source_connection_failed  TYPE NRSOBJ, "   
lv_target_connection_failed  TYPE NRSOBJ, "   
lv_not_control_system  TYPE NRSOBJ. "   

  CALL FUNCTION 'CNV_NCE_LOAD_MESSAGES_OBJ_RFC'  "Load messages
    EXPORTING
         IV_GUID = lv_iv_guid
         IV_ACTIVITY = lv_iv_activity
         IV_OBJECT = lv_iv_object
         IV_SUBOBJECT = lv_iv_subobject
    IMPORTING
         ET_MSG_SRC = lv_et_msg_src
         ET_MSG_TRG = lv_et_msg_trg
         EF_CROSS = lv_ef_cross
    EXCEPTIONS
        GUID_NOT_FOUND = 1
        JOB_IS_RUNNING = 2
        NO_SYS_INFO = 3
        SOURCE_CONNECTION_FAILED = 4
        TARGET_CONNECTION_FAILED = 5
        NOT_CONTROL_SYSTEM = 6
. " CNV_NCE_LOAD_MESSAGES_OBJ_RFC




ABAP code using 7.40 inline data declarations to call FM CNV_NCE_LOAD_MESSAGES_OBJ_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.

 
 
 
 
 
 
 
 
 
 
 
 
 


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!