SAP PVBE_DATA_SELECTION Function Module for NOTRANSL: Ermittlung PVB-Objekt Daten zu gegeben PVB-Objekt Schlüsseln

Search SAP Function Modules

PVBE_DATA_SELECTION is a standard pvbe data selection SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Ermittlung PVB-Objekt Daten zu gegeben PVB-Objekt Schlüsseln 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 pvbe data selection FM, simply by entering the name PVBE_DATA_SELECTION into the relevant SAP transaction such as SE37 or SE38.

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

Function PVBE_DATA_SELECTION 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 'PVBE_DATA_SELECTION'"NOTRANSL: Ermittlung PVB-Objekt Daten zu gegeben PVB-Objekt Schlüsseln
  EXPORTING
   IV_MAX_WERKS =  "Maximum number of plants per read transaction

CHANGING
   CV_NEXT_WERKS =  "Plant

TABLES
*  IN_WERKS_LIST =  "Plant
*  OUT_PVBE_TAB =  "Production Supply Area
*  OUT_PVKT_TAB =  "Supply Area Short Text
*  INOUT_WERKS_TAB =  "Structure for CIF_IMPVBE Keys

EXCEPTIONS
   NO_PVBE = 1    WRONG_NEXT_WERKS = 2 

.

IMPORTING Parameters details for PVBE_DATA_SELECTION

IV_MAX_WERKS - Maximum number of plants per read transaction

Data type: SEL_FIELDS-MAX_WERKS
Optional: No
Call by Reference: Yes

CHANGING Parameters details for PVBE_DATA_SELECTION

CV_NEXT_WERKS - Plant

Data type: T001W-WERKS
Optional: No
Call by Reference: Yes

TABLES Parameters details for PVBE_DATA_SELECTION

IN_WERKS_LIST - Plant

Data type: CIF_IMPVBK
Optional: Yes
Call by Reference: Yes

OUT_PVBE_TAB - Production Supply Area

Data type: PVBE
Optional: Yes
Call by Reference: Yes

OUT_PVKT_TAB - Supply Area Short Text

Data type: PVKT
Optional: Yes
Call by Reference: Yes

INOUT_WERKS_TAB - Structure for CIF_IMPVBE Keys

Data type: CIF_IMPVBK
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NO_PVBE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

WRONG_NEXT_WERKS -

Data type:
Optional: No
Call by Reference: Yes

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

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