SAP FLBP_LOAD_PARTNER Function Module for Load Partner for an Object (Read from Database)
FLBP_LOAD_PARTNER is a standard flbp 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 Load Partner for an Object (Read from Database) 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 load partner FM, simply by entering the name FLBP_LOAD_PARTNER 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_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 'FLBP_LOAD_PARTNER'"Load Partner for an Object (Read from Database).
EXPORTING
* I_DATE = SY-DATUM "Date on which the rel.ship is valid
* I_FUTURE = 'X' "'X also partner with begin date in the future
* I_LOAD_HVP = ' ' "'X' load only main loan partner
* I_PARTNR = ' ' "Key Partner Number
* I_SNUMOBJ = ' ' "Key Number Range Object
* I_SOBJEKT = ' ' "Internal Object Number
* I_ROLLE = ' ' "Required Role Category
* I_ROLE = "Required Partner Role Category
* ENTRIES_INTO_MEMORY = ' ' "Keep selected entries in buffer
IMPORTING
PARTNR_HVP = "Partner number main loan partner
XPARTNER_HVP = "Main loan partner in print view
TABLES
* ET_VZGPO = "filled in FM
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for FLBP_LOAD_PARTNER
I_DATE - Date on which the rel.ship is valid
Data type: SY-DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FUTURE - 'X also partner with begin date in the future
Data type:Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_LOAD_HVP - 'X' load only main loan partner
Data type:Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PARTNR - Key Partner Number
Data type: VDGPO-PARTNRDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SNUMOBJ - Key Number Range Object
Data type: VDGPO-SNUMOBJDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SOBJEKT - Internal Object Number
Data type: VDGPO-SOBJEKTDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_ROLLE - Required Role Category
Data type: TB003A-ROLECATEGORYDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_ROLE - Required Partner Role Category
Data type: TB003-ROLEOptional: Yes
Call by Reference: Yes
ENTRIES_INTO_MEMORY - Keep selected entries in buffer
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FLBP_LOAD_PARTNER
PARTNR_HVP - Partner number main loan partner
Data type: VDGPO-PARTNROptional: No
Call by Reference: No ( called with pass by value option)
XPARTNER_HVP - Main loan partner in print view
Data type: SZAD_FIELD-ADDR_SHORTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FLBP_LOAD_PARTNER
ET_VZGPO - filled in FM
Data type: VDGPOOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND - No partner found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FLBP_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_et_vzgpo | TYPE STANDARD TABLE OF VDGPO, " | |||
| lv_not_found | TYPE VDGPO, " | |||
| lv_partnr_hvp | TYPE VDGPO-PARTNR, " | |||
| lv_i_future | TYPE VDGPO, " 'X' | |||
| lv_xpartner_hvp | TYPE SZAD_FIELD-ADDR_SHORT, " | |||
| lv_i_load_hvp | TYPE SZAD_FIELD, " ' ' | |||
| lv_i_partnr | TYPE VDGPO-PARTNR, " ' ' | |||
| lv_i_snumobj | TYPE VDGPO-SNUMOBJ, " ' ' | |||
| lv_i_sobjekt | TYPE VDGPO-SOBJEKT, " ' ' | |||
| lv_i_rolle | TYPE TB003A-ROLECATEGORY, " ' ' | |||
| lv_i_role | TYPE TB003-ROLE, " | |||
| lv_entries_into_memory | TYPE TB003. " SPACE |
|   CALL FUNCTION 'FLBP_LOAD_PARTNER' "Load Partner for an Object (Read from Database) |
| 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 | |
| I_ROLLE | = lv_i_rolle | |
| I_ROLE | = lv_i_role | |
| ENTRIES_INTO_MEMORY | = lv_entries_into_memory | |
| IMPORTING | ||
| PARTNR_HVP | = lv_partnr_hvp | |
| XPARTNER_HVP | = lv_xpartner_hvp | |
| TABLES | ||
| ET_VZGPO | = lt_et_vzgpo | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " FLBP_LOAD_PARTNER | ||
ABAP code using 7.40 inline data declarations to call FM FLBP_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 VDGPO INTO @DATA(ld_partnr_hvp). | ||||
| DATA(ld_i_future) | = 'X'. | |||
| "SELECT single ADDR_SHORT FROM SZAD_FIELD INTO @DATA(ld_xpartner_hvp). | ||||
| DATA(ld_i_load_hvp) | = ' '. | |||
| "SELECT single PARTNR FROM VDGPO INTO @DATA(ld_i_partnr). | ||||
| DATA(ld_i_partnr) | = ' '. | |||
| "SELECT single SNUMOBJ FROM VDGPO INTO @DATA(ld_i_snumobj). | ||||
| DATA(ld_i_snumobj) | = ' '. | |||
| "SELECT single SOBJEKT FROM VDGPO INTO @DATA(ld_i_sobjekt). | ||||
| DATA(ld_i_sobjekt) | = ' '. | |||
| "SELECT single ROLECATEGORY FROM TB003A INTO @DATA(ld_i_rolle). | ||||
| DATA(ld_i_rolle) | = ' '. | |||
| "SELECT single ROLE FROM TB003 INTO @DATA(ld_i_role). | ||||
| DATA(ld_entries_into_memory) | = ' '. | |||
Search for further information about these or an SAP related objects