SAP CNV_NCE_SIMULATE_RFC Function Module for Analyse numbers in all systems
CNV_NCE_SIMULATE_RFC is a standard cnv nce simulate 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 Analyse numbers in all systems 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 simulate rfc FM, simply by entering the name CNV_NCE_SIMULATE_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_SIMULATE_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_SIMULATE_RFC'"Analyse numbers in all systems.
EXPORTING
IV_GUID = "NCE project identifier
IV_ACTIVITY = "NCE activity
* IV_JOBS_MAX = 6 "
IMPORTING
ET_JOBS = "Jobs in source system
ET_OBJ = "Objects to be processed in source system
ET_MSG = "Source system messages
EXCEPTIONS
GUID_NOT_FOUND = 1 NO_BKG_PROCESSES = 2 JOBS_NOT_CREATED = 3 KB_IS_EMPTY = 4 OBJECT_LOCKED = 5 NO_SYS_INFO = 6 TARGET_CONNECTION_FAILED = 7 NOT_CONTROL_SYSTEM = 8
IMPORTING Parameters details for CNV_NCE_SIMULATE_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)
IV_JOBS_MAX -
Data type: IDefault: 6
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CNV_NCE_SIMULATE_RFC
ET_JOBS - Jobs in source system
Data type: CNV_NCE_T_JOBSOptional: No
Call by Reference: No ( called with pass by value option)
ET_OBJ - Objects to be processed in source system
Data type: CNV_NCE_T_NCE_JOBSOptional: No
Call by Reference: No ( called with pass by value option)
ET_MSG - Source system messages
Data type: CNV_NCE_T_MSGOptional: 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)
NO_BKG_PROCESSES - No free background processes
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
JOBS_NOT_CREATED - Jobs creation failed
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
KB_IS_EMPTY - No data in a local knowledge base
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_LOCKED - Object is locked
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: No ( called with pass by value option)
TARGET_CONNECTION_FAILED - Connection to a target system failed
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_CONTROL_SYSTEM - Execution in this system is not permitted
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CNV_NCE_SIMULATE_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_jobs | TYPE CNV_NCE_T_JOBS, " | |||
| lv_iv_guid | TYPE CNV_NCE_GUID, " | |||
| lv_guid_not_found | TYPE CNV_NCE_GUID, " | |||
| lv_et_obj | TYPE CNV_NCE_T_NCE_JOBS, " | |||
| lv_iv_activity | TYPE CNV_NCE_ACTIVITY, " | |||
| lv_no_bkg_processes | TYPE CNV_NCE_ACTIVITY, " | |||
| lv_et_msg | TYPE CNV_NCE_T_MSG, " | |||
| lv_iv_jobs_max | TYPE I, " 6 | |||
| lv_jobs_not_created | TYPE I, " | |||
| lv_kb_is_empty | TYPE I, " | |||
| lv_object_locked | TYPE I, " | |||
| lv_no_sys_info | TYPE I, " | |||
| lv_target_connection_failed | TYPE I, " | |||
| lv_not_control_system | TYPE I. " |
|   CALL FUNCTION 'CNV_NCE_SIMULATE_RFC' "Analyse numbers in all systems |
| EXPORTING | ||
| IV_GUID | = lv_iv_guid | |
| IV_ACTIVITY | = lv_iv_activity | |
| IV_JOBS_MAX | = lv_iv_jobs_max | |
| IMPORTING | ||
| ET_JOBS | = lv_et_jobs | |
| ET_OBJ | = lv_et_obj | |
| ET_MSG | = lv_et_msg | |
| EXCEPTIONS | ||
| GUID_NOT_FOUND = 1 | ||
| NO_BKG_PROCESSES = 2 | ||
| JOBS_NOT_CREATED = 3 | ||
| KB_IS_EMPTY = 4 | ||
| OBJECT_LOCKED = 5 | ||
| NO_SYS_INFO = 6 | ||
| TARGET_CONNECTION_FAILED = 7 | ||
| NOT_CONTROL_SYSTEM = 8 | ||
| . " CNV_NCE_SIMULATE_RFC | ||
ABAP code using 7.40 inline data declarations to call FM CNV_NCE_SIMULATE_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_iv_jobs_max) | = 6. | |||
Search for further information about these or an SAP related objects