SAP Function Modules

CPE_KNUMVTOGUID_READ_MULTI_DB SAP Function module - CPE_D - KNUMV-Mapping - Read Multiple from DB







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

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


Pattern for FM CPE_KNUMVTOGUID_READ_MULTI_DB - CPE KNUMVTOGUID READ MULTI DB





CALL FUNCTION 'CPE_KNUMVTOGUID_READ_MULTI_DB' "CPE_D - KNUMV-Mapping - Read Multiple from DB
  EXPORTING
    it_knumv_struct =           " cpet_knumv_struct_tab  CPE - Table Type for KNUMV Structure
*   iv_no_buffer = ' '          " char1         Single-character flag
  IMPORTING
    et_knumvtoguid =            " cpet_knumvtoguid_tab  CPE Caller - Table Type for Mapping KNUMV  to GUID concept
  EXCEPTIONS
    NOTHING_FOUND = 1           "
    .  "  CPE_KNUMVTOGUID_READ_MULTI_DB

ABAP code example for Function Module CPE_KNUMVTOGUID_READ_MULTI_DB





The ABAP code below is a full code listing to execute function module CPE_KNUMVTOGUID_READ_MULTI_DB 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_et_knumvtoguid  TYPE CPET_KNUMVTOGUID_TAB .

DATA(ld_it_knumv_struct) = 'Check type of data required'.
DATA(ld_iv_no_buffer) = 'Check type of data required'. . CALL FUNCTION 'CPE_KNUMVTOGUID_READ_MULTI_DB' EXPORTING it_knumv_struct = ld_it_knumv_struct * iv_no_buffer = ld_iv_no_buffer IMPORTING et_knumvtoguid = ld_et_knumvtoguid EXCEPTIONS NOTHING_FOUND = 1 . " CPE_KNUMVTOGUID_READ_MULTI_DB
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_et_knumvtoguid  TYPE CPET_KNUMVTOGUID_TAB ,
ld_it_knumv_struct  TYPE CPET_KNUMV_STRUCT_TAB ,
ld_iv_no_buffer  TYPE CHAR1 .

ld_it_knumv_struct = 'Check type of data required'.
ld_iv_no_buffer = 'Check type of data required'.

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_KNUMVTOGUID_READ_MULTI_DB or its description.