SAP BBP_IV_PARTNER_SRC_SYS_SET Function Module for Checks if invoicing party or vendor exist locally
BBP_IV_PARTNER_SRC_SYS_SET is a standard bbp iv partner src sys set SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Checks if invoicing party or vendor exist locally 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 bbp iv partner src sys set FM, simply by entering the name BBP_IV_PARTNER_SRC_SYS_SET into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_IV2
Program Name: SAPLBBP_IV2
Main Program: SAPLBBP_IV2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_IV_PARTNER_SRC_SYS_SET 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 'BBP_IV_PARTNER_SRC_SYS_SET'"Checks if invoicing party or vendor exist locally.
EXPORTING
IV_SRC_OBJECT_TYPE = "Objekttyp des Vorlagebelegs
IV_LOG_SYSTEM = "Logisches System des Logistik-Backends
TABLES
CT_PARTNER = "Geschftspartner
IMPORTING Parameters details for BBP_IV_PARTNER_SRC_SYS_SET
IV_SRC_OBJECT_TYPE - Objekttyp des Vorlagebelegs
Data type: BBP_SRC_H_OBJ_TYPOptional: No
Call by Reference: Yes
IV_LOG_SYSTEM - Logisches System des Logistik-Backends
Data type: BE_LOG_SYSTEMOptional: No
Call by Reference: Yes
TABLES Parameters details for BBP_IV_PARTNER_SRC_SYS_SET
CT_PARTNER - Geschftspartner
Data type: BBP_PDS_PARTNEROptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_IV_PARTNER_SRC_SYS_SET 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_ct_partner | TYPE STANDARD TABLE OF BBP_PDS_PARTNER, " | |||
| lv_iv_src_object_type | TYPE BBP_SRC_H_OBJ_TYP, " | |||
| lv_iv_log_system | TYPE BE_LOG_SYSTEM. " |
|   CALL FUNCTION 'BBP_IV_PARTNER_SRC_SYS_SET' "Checks if invoicing party or vendor exist locally |
| EXPORTING | ||
| IV_SRC_OBJECT_TYPE | = lv_iv_src_object_type | |
| IV_LOG_SYSTEM | = lv_iv_log_system | |
| TABLES | ||
| CT_PARTNER | = lt_ct_partner | |
| . " BBP_IV_PARTNER_SRC_SYS_SET | ||
ABAP code using 7.40 inline data declarations to call FM BBP_IV_PARTNER_SRC_SYS_SET
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