SAP BBP_LOCATION_BY_PARTNER_COMP Function Module for

Search SAP Function Modules

BBP_LOCATION_BY_PARTNER_COMP is a standard bbp location by partner comp SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 location by partner comp FM, simply by entering the name BBP_LOCATION_BY_PARTNER_COMP into the relevant SAP transaction such as SE37 or SE38.

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

Function BBP_LOCATION_BY_PARTNER_COMP 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_LOCATION_BY_PARTNER_COMP'"
  EXPORTING
   IV_PARTNER_NO =  "
*  IV_LOGSYS =  "
*  IV_USER =  "
*  IV_USER_PARTNER =  "
*  IV_USER_PARTNER_GUID =  "
*  IV_COMPANY_ORGUNIT =  "

 IMPORTING
   EV_LOCATION =  "

TABLES
*  ET_LOCATIONS =  "

EXCEPTIONS
   PARAMETER_ERROR = 1 

.

IMPORTING Parameters details for BBP_LOCATION_BY_PARTNER_COMP

IV_PARTNER_NO -

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

IV_LOGSYS -

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

IV_USER -

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

IV_USER_PARTNER -

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

IV_USER_PARTNER_GUID -

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

IV_COMPANY_ORGUNIT -

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

EXPORTING Parameters details for BBP_LOCATION_BY_PARTNER_COMP

EV_LOCATION -

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

TABLES Parameters details for BBP_LOCATION_BY_PARTNER_COMP

ET_LOCATIONS -

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

EXCEPTIONS details

PARAMETER_ERROR -

Data type:
Optional: No
Call by Reference: Yes

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

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