SAP ISGP_VZGPO_READ Function Module for NOTRANSL: Lesen VZGPO zu Objekt
ISGP_VZGPO_READ is a standard isgp vzgpo 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 NOTRANSL: Lesen VZGPO zu Objekt 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 isgp vzgpo read FM, simply by entering the name ISGP_VZGPO_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVZ8
Program Name: SAPLFVZ8
Main Program: SAPLFVZ8
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function ISGP_VZGPO_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 'ISGP_VZGPO_READ'"NOTRANSL: Lesen VZGPO zu Objekt.
EXPORTING
I_SNUMOBJ = "Key for number range object
* I_SOBJEKT = "Internal Object Number
* I_DATE = "ABAP System Field: Current Date of Application Server
* I_END_DATE = "ABAP System Field: Current Date of Application Server
TABLES
YVZGPO = "Partner/role object relationship
* R_PARTNER = "Ranges Structure for Partner Number
* R_ROLETYP = "Ranges Structure for Role Category
* R_ROLE = "Ranges Structure for Role Type
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for ISGP_VZGPO_READ
I_SNUMOBJ - Key for number range object
Data type: VZGPO-SNUMOBJOptional: No
Call by Reference: No ( called with pass by value option)
I_SOBJEKT - Internal Object Number
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
I_DATE - ABAP System Field: Current Date of Application Server
Data type: SY-DATUMOptional: Yes
Call by Reference: No ( called with pass by value option)
I_END_DATE - ABAP System Field: Current Date of Application Server
Data type: SY-DATUMOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISGP_VZGPO_READ
YVZGPO - Partner/role object relationship
Data type: VZGPOOptional: No
Call by Reference: No ( called with pass by value option)
R_PARTNER - Ranges Structure for Partner Number
Data type: BPAR_PART1Optional: Yes
Call by Reference: No ( called with pass by value option)
R_ROLETYP - Ranges Structure for Role Category
Data type: BPAR_ROLE1Optional: Yes
Call by Reference: No ( called with pass by value option)
R_ROLE - Ranges Structure for Role Type
Data type: BPAR_ROLE2Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND - No entries found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISGP_VZGPO_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.DATA: | ||||
lt_yvzgpo | TYPE STANDARD TABLE OF VZGPO, " | |||
lv_i_snumobj | TYPE VZGPO-SNUMOBJ, " | |||
lv_not_found | TYPE VZGPO, " | |||
lv_i_sobjekt | TYPE VZGPO, " | |||
lt_r_partner | TYPE STANDARD TABLE OF BPAR_PART1, " | |||
lv_i_date | TYPE SY-DATUM, " | |||
lt_r_roletyp | TYPE STANDARD TABLE OF BPAR_ROLE1, " | |||
lt_r_role | TYPE STANDARD TABLE OF BPAR_ROLE2, " | |||
lv_i_end_date | TYPE SY-DATUM. " |
  CALL FUNCTION 'ISGP_VZGPO_READ' "NOTRANSL: Lesen VZGPO zu Objekt |
EXPORTING | ||
I_SNUMOBJ | = lv_i_snumobj | |
I_SOBJEKT | = lv_i_sobjekt | |
I_DATE | = lv_i_date | |
I_END_DATE | = lv_i_end_date | |
TABLES | ||
YVZGPO | = lt_yvzgpo | |
R_PARTNER | = lt_r_partner | |
R_ROLETYP | = lt_r_roletyp | |
R_ROLE | = lt_r_role | |
EXCEPTIONS | ||
NOT_FOUND = 1 | ||
. " ISGP_VZGPO_READ |
ABAP code using 7.40 inline data declarations to call FM ISGP_VZGPO_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."SELECT single SNUMOBJ FROM VZGPO INTO @DATA(ld_i_snumobj). | ||||
"SELECT single DATUM FROM SY INTO @DATA(ld_i_date). | ||||
"SELECT single DATUM FROM SY INTO @DATA(ld_i_end_date). | ||||
Search for further information about these or an SAP related objects