TESTPROXY_EXECUTION_CREATE SAP Function module - Foreground Scheduler: Create an entry for execution

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

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

Pattern for FM TESTPROXY_EXECUTION_CREATE - TESTPROXY EXECUTION CREATE

CALL FUNCTION 'TESTPROXY_EXECUTION_CREATE' "Foreground Scheduler: Create an entry for execution
  EXPORTING
    is_job_info =               " ettp_testproxy_job_rfc  Job for test executions
    it_execution_data =         " ectp_job_data_tabtype  Data for TWB jobs for test execution
  IMPORTING
    es_job_info =               " ettp_testproxy_job_rfc  Foreground Scheduler: An Execution (for RFC)
  EXCEPTIONS
    DATABASE_ERROR = 1          "               Error accessing database
    MISSING_PARAMETERS = 2      "               Parameters are missing
    ECATT_NOT_ALLOWED_IN_TARGETSYS = 3  "       eCATT is not allowed in target system/client
    .  "  TESTPROXY_EXECUTION_CREATE

ABAP code example for Function Module TESTPROXY_EXECUTION_CREATE

The ABAP code below is a full code listing to execute function module TESTPROXY_EXECUTION_CREATE 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_es_job_info  
 
 TYPE ETTP_TESTPROXY_JOB_RFC
.


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

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

CALL FUNCTION 'TESTPROXY_EXECUTION_CREATE'
  EXPORTING
    is_job_info =                ld_is_job_info
    it_execution_data =          ld_it_execution_data
  IMPORTING
    es_job_info =                ld_es_job_info
  EXCEPTIONS
    DATABASE_ERROR =             1
    MISSING_PARAMETERS =         2
    ECATT_NOT_ALLOWED_IN_TARGETSYS =    3
    .  "  TESTPROXY_EXECUTION_CREATE

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
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_es_job_info
 
 TYPE ETTP_TESTPROXY_JOB_RFC ,
ld_is_job_info
 
 TYPE ETTP_TESTPROXY_JOB_RFC ,
ld_it_execution_data
 
 TYPE ECTP_JOB_DATA_TABTYPE .


ld_is_job_info = 'Check type of data required'.
ld_it_execution_data = 'Check type of data required'.