SAP FLBP_VDGPO_READ Function Module for Read VDGPO for Object: Successor of ISGP_VZGPO_READ

Search SAP Function Modules

FLBP_VDGPO_READ is a standard flbp vdgpo 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 Read VDGPO for Object: Successor of ISGP_VZGPO_READ 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 flbp vdgpo read FM, simply by entering the name FLBP_VDGPO_READ into the relevant SAP transaction such as SE37 or SE38.

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

Function FLBP_VDGPO_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 'FLBP_VDGPO_READ'"Read VDGPO for Object: Successor of ISGP_VZGPO_READ
  EXPORTING
*  I_SNUMOBJ =  "Key for Number Range Object
*  I_SOBJEKT =  "
*  I_DATE =  "Date and Time, Current (Application Server) Date
*  I_END_DATE =  "Date and Time, Current (Application Server) Date
*  IT_ROLE_RNG =  "Ranges Table Type for BP Role
*  IT_RLCAT =  "BP Role Categories

TABLES
   YVDGPO =  "will be filled in FM
*  R_PARTNER =  "Range Table for Partner < 255 Entries
*  R_ROLETYP =  "(do not use) Range Table für Role Category < 255 Entries
*  R_ROLE =  "Ranga Table for Role Type < 255 Entries

EXCEPTIONS
   KEY_NOT_FILLED = 1    ENTRY_NOT_FOUND = 2 

.

IMPORTING Parameters details for FLBP_VDGPO_READ

I_SNUMOBJ - Key for Number Range Object

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

I_SOBJEKT -

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

I_DATE - Date and Time, Current (Application Server) Date

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

I_END_DATE - Date and Time, Current (Application Server) Date

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

IT_ROLE_RNG - Ranges Table Type for BP Role

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

IT_RLCAT - BP Role Categories

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

TABLES Parameters details for FLBP_VDGPO_READ

YVDGPO - will be filled in FM

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

R_PARTNER - Range Table for Partner < 255 Entries

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

R_ROLETYP - (do not use) Range Table für Role Category < 255 Entries

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

R_ROLE - Ranga Table for Role Type < 255 Entries

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

EXCEPTIONS details

KEY_NOT_FILLED - Key is not completely specified

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

ENTRY_NOT_FOUND - No Entry for specified Key in VDGPO found

Data type:
Optional: No
Call by Reference: Yes

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