SAP RF_SW_VEKP_READ Function Module for Select from table VEKP - 1st layer

Search SAP Function Modules

RF_SW_VEKP_READ is a standard rf sw vekp read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Select from table VEKP - 1st layer 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 rf sw vekp read FM, simply by entering the name RF_SW_VEKP_READ into the relevant SAP transaction such as SE37 or SE38.

Function Group: LMSW
Program Name: SAPLLMSW
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RF_SW_VEKP_READ 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 'RF_SW_VEKP_READ'"Select from table VEKP - 1st layer
  EXPORTING
*  I_VENUM =  "Shipping unit number
*  I_EXIDV =  "External shipping unit ID
*  I_VPOBJ =  "Packing object
*  I_VPOBJKEY =  "Key for object to which the shipping unit is assigned
*  I_UEVEL =  "Higher-level shipping unit
*  I_LGNUM =  "Warehouse number / warehouse complex
*  LINE_EXIST = ' ' "if 'x' check only if line exsists
*  LINE_SINGLE = ' ' "'X' for Single search
*  I_MODE = '1' "

 IMPORTING
   O_ANSWR =  "send out 'x' for line exsists in table

TABLES
   EV_VEKP =  "Handling Unit - Header Table

EXCEPTIONS
   NO_ENTRY_FOUND = 1    NO_PARAMETERS_FOUND = 2    FUNCTION_NOT_EXIST = 3 

.

IMPORTING Parameters details for RF_SW_VEKP_READ

I_VENUM - Shipping unit number

Data type: VEKP-VENUM
Optional: Yes
Call by Reference: Yes

I_EXIDV - External shipping unit ID

Data type: VEKP-EXIDV
Optional: Yes
Call by Reference: Yes

I_VPOBJ - Packing object

Data type: VEKP-VPOBJ
Optional: Yes
Call by Reference: Yes

I_VPOBJKEY - Key for object to which the shipping unit is assigned

Data type: VEKP-VPOBJKEY
Optional: Yes
Call by Reference: Yes

I_UEVEL - Higher-level shipping unit

Data type: VEKP-UEVEL
Optional: Yes
Call by Reference: Yes

I_LGNUM - Warehouse number / warehouse complex

Data type: VEKP-LGNUM
Optional: Yes
Call by Reference: Yes

LINE_EXIST - if 'x' check only if line exsists

Data type: C
Default: ' '
Optional: Yes
Call by Reference: Yes

LINE_SINGLE - 'X' for Single search

Data type: C
Default: ' '
Optional: Yes
Call by Reference: Yes

I_MODE -

Data type: C
Default: '1'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for RF_SW_VEKP_READ

O_ANSWR - send out 'x' for line exsists in table

Data type: C
Optional: No
Call by Reference: Yes

TABLES Parameters details for RF_SW_VEKP_READ

EV_VEKP - Handling Unit - Header Table

Data type: VEKP
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_ENTRY_FOUND -

Data type:
Optional: No
Call by Reference: Yes

NO_PARAMETERS_FOUND -

Data type:
Optional: No
Call by Reference: Yes

FUNCTION_NOT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RF_SW_VEKP_READ 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 RF_SW_VEKP_READ

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