SAP CPE_TEST_CHECK_VMC_BUFFER Function Module for CPE: Test Checking of VMC Buffer Contents

Search SAP Function Modules

CPE_TEST_CHECK_VMC_BUFFER is a standard cpe test check vmc buffer SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CPE: Test Checking of VMC Buffer Contents processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for cpe test check vmc buffer FM, simply by entering the name CPE_TEST_CHECK_VMC_BUFFER into the relevant SAP transaction such as SE37 or SE38.

Function Group: CPE_TEST_JAVA_API
Program Name: SAPLCPE_TEST_JAVA_API
Main Program: SAPLCPE_TEST_JAVA_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CPE_TEST_CHECK_VMC_BUFFER pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'CPE_TEST_CHECK_VMC_BUFFER'"CPE: Test Checking of VMC Buffer Contents
  EXPORTING
*  IV_VMC_RFC_DEST = '' "Logical Destination (Specified in Function Call)
*  IV_TABNAME =  "Table Name

 IMPORTING
   EV_TEST_ERROR_OCCURRED =  "Single-Character Flag
   ET_BUFFER_CONTENTS =  "CPE Caller - Table Type for Name Value Pairs  (L=255)

EXCEPTIONS
   JAVA_API_ERROR = 1 

.

IMPORTING Parameters details for CPE_TEST_CHECK_VMC_BUFFER

IV_VMC_RFC_DEST - Logical Destination (Specified in Function Call)

Data type: RFCDEST
Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_TABNAME - Table Name

Data type: TABNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CPE_TEST_CHECK_VMC_BUFFER

EV_TEST_ERROR_OCCURRED - Single-Character Flag

Data type: CHAR1
Optional: No
Call by Reference: No ( called with pass by value option)

ET_BUFFER_CONTENTS - CPE Caller - Table Type for Name Value Pairs (L=255)

Data type: CPET_NAMEVALUEPAIRS_255_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

JAVA_API_ERROR - Error occurred during call of Java API

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CPE_TEST_CHECK_VMC_BUFFER Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM CPE_TEST_CHECK_VMC_BUFFER

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects