CJDB_TEST_RUN_PROTOCOL SAP Function module - Display results from LDB PSJ test run

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

Associated Function Group: CJDB
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM CJDB_TEST_RUN_PROTOCOL - CJDB TEST RUN PROTOCOL

CALL FUNCTION 'CJDB_TEST_RUN_PROTOCOL' "Display results from LDB PSJ test run
  EXPORTING
    i_counter_pd =              " i
    i_counter_vb =              " i
    i_counter_pr =              " i
    i_counter_np =              " i
    i_counter_or =              " i
    i_counter_nv =              " i
    i_counter_vs =              " i
    .  "  CJDB_TEST_RUN_PROTOCOL

ABAP code example for Function Module CJDB_TEST_RUN_PROTOCOL

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

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

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

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

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

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

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

CALL FUNCTION 'CJDB_TEST_RUN_PROTOCOL'
  EXPORTING
    i_counter_pd =               ld_i_counter_pd
    i_counter_vb =               ld_i_counter_vb
    i_counter_pr =               ld_i_counter_pr
    i_counter_np =               ld_i_counter_np
    i_counter_or =               ld_i_counter_or
    i_counter_nv =               ld_i_counter_nv
    i_counter_vs =               ld_i_counter_vs
    .  "  CJDB_TEST_RUN_PROTOCOL

IF SY-SUBRC EQ 0.
  "All OK
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_i_counter_pd
 
 TYPE I ,
ld_i_counter_vb
 
 TYPE I ,
ld_i_counter_pr
 
 TYPE I ,
ld_i_counter_np
 
 TYPE I ,
ld_i_counter_or
 
 TYPE I ,
ld_i_counter_nv
 
 TYPE I ,
ld_i_counter_vs
 
 TYPE I .


ld_i_counter_pd = 'Check type of data required'.
ld_i_counter_vb = 'Check type of data required'.
ld_i_counter_pr = 'Check type of data required'.
ld_i_counter_np = 'Check type of data required'.
ld_i_counter_or = 'Check type of data required'.
ld_i_counter_nv = 'Check type of data required'.
ld_i_counter_vs = 'Check type of data required'.