SCV_CREATE_RESULT_RFC SAP Function module

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

Associated Function Group: SCV_RFC_ACCESS
Released Date: Not Released
Processing type: Remote-Enabled + BasXML supported

Pattern for FM SCV_CREATE_RESULT_RFC - SCV CREATE RESULT RFC

CALL FUNCTION 'SCV_CREATE_RESULT_RFC' "
  EXPORTING
    i_measurement_id =          " cva_uuid
    i_result_name =             " cva_result_name
*   i_program_range =           " cvt_sopro
*   i_package_range =           " cvt_sodev
*   i_component_range =         " cvt_soappl_comp
  IMPORTING
    e_result_id =               " cva_uuid
  EXCEPTIONS
    EXECUTION_ERROR = 1         "
    CALL_ERROR = 2              "
    .  "  SCV_CREATE_RESULT_RFC

ABAP code example for Function Module SCV_CREATE_RESULT_RFC

The ABAP code below is a full code listing to execute function module SCV_CREATE_RESULT_RFC 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_e_result_id  
 
 TYPE CVA_UUID
.


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

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

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

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

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

CALL FUNCTION 'SCV_CREATE_RESULT_RFC'
  EXPORTING
    i_measurement_id =           ld_i_measurement_id
    i_result_name =              ld_i_result_name
*   i_program_range =            ld_i_program_range
*   i_package_range =            ld_i_package_range
*   i_component_range =          ld_i_component_range
  IMPORTING
    e_result_id =                ld_e_result_id
  EXCEPTIONS
    EXECUTION_ERROR =            1
    CALL_ERROR =                 2
    .  "  SCV_CREATE_RESULT_RFC

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
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_e_result_id
 
 TYPE CVA_UUID ,
ld_i_measurement_id
 
 TYPE CVA_UUID ,
ld_i_result_name
 
 TYPE CVA_RESULT_NAME ,
ld_i_program_range
 
 TYPE CVT_SOPRO ,
ld_i_package_range
 
 TYPE CVT_SODEV ,
ld_i_component_range
 
 TYPE CVT_SOAPPL_COMP .


ld_i_measurement_id = 'Check type of data required'.
ld_i_result_name = 'Check type of data required'.
ld_i_program_range = 'Check type of data required'.
ld_i_package_range = 'Check type of data required'.
ld_i_component_range = 'Check type of data required'.