SAP Function Modules

comments icon Comments

CPE_BASIS_TEST SAP Function module - To test CPE_BASIS function modules







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

Associated Function Group: CPE_TEST
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM CPE_BASIS_TEST - CPE BASIS TEST 





CALL FUNCTION 'CPE_BASIS_TEST' "To test CPE_BASIS function modules
  EXPORTING
    iv_appserv = ' '            " char1         Single-character flag
    iv_presserv = 'X'           " char1         Single-character flag
    iv_source =                 " char100       Character 100
*   iv_displaylist =            " char1         Single-character flag
    iv_logsys =                 " tbdls-logsys  Logical system
  IMPORTING
    ev_test_error_occurred =    " char1         Single-character flag
* TABLES
*   et_result =                 " cpet_java_objects  CPE - Interface for JAVA Objects (Field, Key, Text)
    .  "  CPE_BASIS_TEST

ABAP code example for Function Module CPE_BASIS_TEST





The ABAP code below is a full code listing to execute function module CPE_BASIS_TEST 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_ev_test_error_occurred    TYPE CHAR1
,
it_et_result    TYPE STANDARD TABLE OF CPET_JAVA_OBJECTS,"TABLES PARAM
wa_et_result  LIKE LINE OF it_et_result
.




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

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

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

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

SELECT single LOGSYS 
  FROM TBDLS 
  INTO @DATA(ld_iv_logsys).

 

"populate fields of struture and append to itab
append wa_et_result to it_et_result.
.

CALL FUNCTION 'CPE_BASIS_TEST'
  EXPORTING
    iv_appserv =                 ld_iv_appserv
    iv_presserv =                ld_iv_presserv
    iv_source =                  ld_iv_source
*   iv_displaylist =             ld_iv_displaylist
    iv_logsys =                  ld_iv_logsys
  IMPORTING
    ev_test_error_occurred =     ld_ev_test_error_occurred
* TABLES
*   et_result =                  it_et_result
    .  "  CPE_BASIS_TEST

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_ev_test_error_occurred  TYPE CHAR1 ,
ld_iv_appserv  TYPE CHAR1 ,
it_et_result  TYPE STANDARD TABLE OF CPET_JAVA_OBJECTS ,
wa_et_result  LIKE LINE OF it_et_result,
ld_iv_presserv  TYPE CHAR1 ,
ld_iv_source  TYPE CHAR100 ,
ld_iv_displaylist  TYPE CHAR1 ,
ld_iv_logsys  TYPE TBDLS-LOGSYS .




ld_iv_appserv = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_et_result to it_et_result.
ld_iv_presserv = 'Check type of data required'.
ld_iv_source = 'Check type of data required'.
ld_iv_displaylist = 'Check type of data required'.

SELECT single LOGSYS 
  FROM TBDLS 
  INTO ld_iv_logsys.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name CPE_BASIS_TEST or its description.


   
 

CPE_BASIS_TEST - To test CPE_BASIS function modules
CPE_BAPI_PRICEQUOT_TO_BAPIMTCS - CPE_M - Mapping BAPI_CPE_PRICEQUOT to BAPIMTCS
CPE_BAPI_PRICEQUOT_FR_BAPIMTCS - CPE_M - Mapping BAPI_CPE_PRICEQUOT from BAPIM
CPE_APPL_F4_EXIT_RULE - F4-Search Help Exit for CPE Rules
CPE_APPL_ACTIVATED_CHECK_CB - CPE_C - CPE Application Settings: Read "Activated"-Flag
CPE_APPLSETTING_READ_CB - CPE_C - CPE Application Settings: Read Customizing Buffer