CNV_NCE_SYNCHRONIZE_RNG_DATA SAP Function module - Synchronize NRIV intervals data

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

Associated Function Group: CNV_NCE_RFC
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM CNV_NCE_SYNCHRONIZE_RNG_DATA - CNV NCE SYNCHRONIZE RNG DATA

CALL FUNCTION 'CNV_NCE_SYNCHRONIZE_RNG_DATA' "Synchronize NRIV intervals data
  EXPORTING
    iv_guid =                   " cnv_nce_guid  NCE project identifier
*   it_objects =                " cnv_nce_t_nrobj  Number range objects
  EXCEPTIONS
    GUID_NOT_FOUND = 1          "               GUID does not exist
    OBJECT_LOCKED = 2           "               Object is locked
    NO_SYS_INFO = 3             "               No information about systems found
    SOURCE_CONNECTION_FAILED = 4  "             Connection to a source system failed
    TARGET_CONNECTION_FAILED = 5  "             Connection to a target system failed
    NOT_CONTROL_SYSTEM = 6      "               Execution in this system is not permitted
    .  "  CNV_NCE_SYNCHRONIZE_RNG_DATA

ABAP code example for Function Module CNV_NCE_SYNCHRONIZE_RNG_DATA

The ABAP code below is a full code listing to execute function module CNV_NCE_SYNCHRONIZE_RNG_DATA 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_iv_guid) = 'Check type of data required'.

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

CALL FUNCTION 'CNV_NCE_SYNCHRONIZE_RNG_DATA'
  EXPORTING
    iv_guid =                    ld_iv_guid
*   it_objects =                 ld_it_objects
  EXCEPTIONS
    GUID_NOT_FOUND =             1
    OBJECT_LOCKED =              2
    NO_SYS_INFO =                3
    SOURCE_CONNECTION_FAILED =    4
    TARGET_CONNECTION_FAILED =    5
    NOT_CONTROL_SYSTEM =         6
    .  "  CNV_NCE_SYNCHRONIZE_RNG_DATA

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 6. "Exception
  "Add code for exception here
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_iv_guid
 
 TYPE CNV_NCE_GUID ,
ld_it_objects
 
 TYPE CNV_NCE_T_NROBJ .


ld_iv_guid = 'Check type of data required'.
ld_it_objects = 'Check type of data required'.