SAP ISGP_LOAD_PARTNER Function Module for NOTRANSL: Partner zu einem Objekt laden (von Datenbank lesen)
ISGP_LOAD_PARTNER is a standard isgp load partner 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: Partner zu einem Objekt laden (von Datenbank lesen) 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 load partner FM, simply by entering the name ISGP_LOAD_PARTNER 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_LOAD_PARTNER 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_LOAD_PARTNER'"NOTRANSL: Partner zu einem Objekt laden (von Datenbank lesen).
EXPORTING
* I_DATE = SY-DATUM "ABAP System Field: Current Date of Application Server
* I_FUTURE = 'X' "DE-EN-LANG-SWITCH-NO-TRANSLATION
* I_LOAD_HVP = ' ' "DE-EN-LANG-SWITCH-NO-TRANSLATION
* I_PARTNR = ' ' "Business Partner Number
* I_SNUMOBJ = ' ' "Key for number range object
* I_SOBJEKT = ' ' "Internal Object Number
* ROLLE_HVP = ' ' "Business Partner Role Category
* ENTRIES_INTO_MEMORY = ' ' "DE-EN-LANG-SWITCH-NO-TRANSLATION
IMPORTING
PARTNR_HVP = "Business Partner Number
XPARTNER_HVP = "Address line
TABLES
* YVZGPO = "Partner/role object relationship
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for ISGP_LOAD_PARTNER
I_DATE - ABAP System Field: Current Date of Application Server
Data type: SY-DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FUTURE - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_LOAD_HVP - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PARTNR - Business Partner Number
Data type: VZGPO-PARTNRDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SNUMOBJ - Key for number range object
Data type: VZGPO-SNUMOBJDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SOBJEKT - Internal Object Number
Data type: VZGPO-SOBJEKTDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
ROLLE_HVP - Business Partner Role Category
Data type: TPZ3-ROLETYPDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
ENTRIES_INTO_MEMORY - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISGP_LOAD_PARTNER
PARTNR_HVP - Business Partner Number
Data type: VZGPO-PARTNROptional: No
Call by Reference: No ( called with pass by value option)
XPARTNER_HVP - Address line
Data type: ADRS-LINEKOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISGP_LOAD_PARTNER
YVZGPO - Partner/role object relationship
Data type: VZGPOOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISGP_LOAD_PARTNER 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: | ||||
| lv_i_date | TYPE SY-DATUM, " SY-DATUM | |||
| lt_yvzgpo | TYPE STANDARD TABLE OF VZGPO, " | |||
| lv_not_found | TYPE VZGPO, " | |||
| lv_partnr_hvp | TYPE VZGPO-PARTNR, " | |||
| lv_i_future | TYPE VZGPO, " 'X' | |||
| lv_xpartner_hvp | TYPE ADRS-LINEK, " | |||
| lv_i_load_hvp | TYPE ADRS, " ' ' | |||
| lv_i_partnr | TYPE VZGPO-PARTNR, " ' ' | |||
| lv_i_snumobj | TYPE VZGPO-SNUMOBJ, " ' ' | |||
| lv_i_sobjekt | TYPE VZGPO-SOBJEKT, " ' ' | |||
| lv_rolle_hvp | TYPE TPZ3-ROLETYP, " ' ' | |||
| lv_entries_into_memory | TYPE TPZ3. " SPACE |
|   CALL FUNCTION 'ISGP_LOAD_PARTNER' "NOTRANSL: Partner zu einem Objekt laden (von Datenbank lesen) |
| EXPORTING | ||
| I_DATE | = lv_i_date | |
| I_FUTURE | = lv_i_future | |
| I_LOAD_HVP | = lv_i_load_hvp | |
| I_PARTNR | = lv_i_partnr | |
| I_SNUMOBJ | = lv_i_snumobj | |
| I_SOBJEKT | = lv_i_sobjekt | |
| ROLLE_HVP | = lv_rolle_hvp | |
| ENTRIES_INTO_MEMORY | = lv_entries_into_memory | |
| IMPORTING | ||
| PARTNR_HVP | = lv_partnr_hvp | |
| XPARTNER_HVP | = lv_xpartner_hvp | |
| TABLES | ||
| YVZGPO | = lt_yvzgpo | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " ISGP_LOAD_PARTNER | ||
ABAP code using 7.40 inline data declarations to call FM ISGP_LOAD_PARTNER
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 DATUM FROM SY INTO @DATA(ld_i_date). | ||||
| DATA(ld_i_date) | = SY-DATUM. | |||
| "SELECT single PARTNR FROM VZGPO INTO @DATA(ld_partnr_hvp). | ||||
| DATA(ld_i_future) | = 'X'. | |||
| "SELECT single LINEK FROM ADRS INTO @DATA(ld_xpartner_hvp). | ||||
| DATA(ld_i_load_hvp) | = ' '. | |||
| "SELECT single PARTNR FROM VZGPO INTO @DATA(ld_i_partnr). | ||||
| DATA(ld_i_partnr) | = ' '. | |||
| "SELECT single SNUMOBJ FROM VZGPO INTO @DATA(ld_i_snumobj). | ||||
| DATA(ld_i_snumobj) | = ' '. | |||
| "SELECT single SOBJEKT FROM VZGPO INTO @DATA(ld_i_sobjekt). | ||||
| DATA(ld_i_sobjekt) | = ' '. | |||
| "SELECT single ROLETYP FROM TPZ3 INTO @DATA(ld_rolle_hvp). | ||||
| DATA(ld_rolle_hvp) | = ' '. | |||
| DATA(ld_entries_into_memory) | = ' '. | |||
Search for further information about these or an SAP related objects