CPE_TEST_CLEAR_VMC_BUFFER_RECS SAP Function module - CPE: Test of Clearing VMC Buffer for a Given Database Record

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

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

Pattern for FM CPE_TEST_CLEAR_VMC_BUFFER_RECS - CPE TEST CLEAR VMC BUFFER RECS

CALL FUNCTION 'CPE_TEST_CLEAR_VMC_BUFFER_RECS' "CPE: Test of Clearing VMC Buffer for a Given Database Record
  EXPORTING
*   iv_vmc_rfc_dest = ''        " rfcdest       Logical Destination (Specified in Function Call)
    iv_tabname =                " tabname       Table Name
    it_keys =                   " cpet_namevalueattr_40_tab  CPE Caller - Table Type for Name Value Attributes ( L=40)
  EXCEPTIONS
    JAVA_API_ERROR = 1          "               Error occurred during call of Java API
    .  "  CPE_TEST_CLEAR_VMC_BUFFER_RECS

ABAP code example for Function Module CPE_TEST_CLEAR_VMC_BUFFER_RECS

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

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

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

CALL FUNCTION 'CPE_TEST_CLEAR_VMC_BUFFER_RECS'
  EXPORTING
*   iv_vmc_rfc_dest =            ld_iv_vmc_rfc_dest
    iv_tabname =                 ld_iv_tabname
    it_keys =                    ld_it_keys
  EXCEPTIONS
    JAVA_API_ERROR =             1
    .  "  CPE_TEST_CLEAR_VMC_BUFFER_RECS

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_vmc_rfc_dest
 
 TYPE RFCDEST ,
ld_iv_tabname
 
 TYPE TABNAME ,
ld_it_keys
 
 TYPE CPET_NAMEVALUEATTR_40_TAB .


ld_iv_vmc_rfc_dest = 'Check type of data required'.
ld_iv_tabname = 'Check type of data required'.
ld_it_keys = 'Check type of data required'.