SAP BBP_UI_CTRL_PARTNER Function Module for









BBP_UI_CTRL_PARTNER is a standard bbp ui ctrl partner 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 ui ctrl partner FM, simply by entering the name BBP_UI_CTRL_PARTNER into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_UI_CTRL_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 'BBP_UI_CTRL_PARTNER'"
EXPORTING
IV_OBJTYPE = "
IV_GUID = "
* IS_PARTNER = "
IV_MODE = "
IV_FIELDNAME = "
* IV_PROGNAME = "
* IV_DYNPNAME = "

CHANGING
CV_SCREEN_INVISIBLE = "
CV_SCREEN_INPUT = "
.



IMPORTING Parameters details for BBP_UI_CTRL_PARTNER

IV_OBJTYPE -

Data type: BBP_SEARCH_OBJTYP
Optional: No
Call by Reference: Yes

IV_GUID -

Data type: BBP_GUID
Optional: No
Call by Reference: Yes

IS_PARTNER -

Data type: BBP_PDS_PARTNER_LIST_D
Optional: Yes
Call by Reference: Yes

IV_MODE -

Data type: C
Optional: No
Call by Reference: Yes

IV_FIELDNAME -

Data type: DYNFNAM
Optional: No
Call by Reference: Yes

IV_PROGNAME -

Data type: SY-REPID
Optional: Yes
Call by Reference: Yes

IV_DYNPNAME -

Data type: SY-DYNNR
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for BBP_UI_CTRL_PARTNER

CV_SCREEN_INVISIBLE -

Data type: C
Optional: No
Call by Reference: Yes

CV_SCREEN_INPUT -

Data type: C
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BBP_UI_CTRL_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_iv_objtype  TYPE BBP_SEARCH_OBJTYP, "   
lv_cv_screen_invisible  TYPE C, "   
lv_iv_guid  TYPE BBP_GUID, "   
lv_cv_screen_input  TYPE C, "   
lv_is_partner  TYPE BBP_PDS_PARTNER_LIST_D, "   
lv_iv_mode  TYPE C, "   
lv_iv_fieldname  TYPE DYNFNAM, "   
lv_iv_progname  TYPE SY-REPID, "   
lv_iv_dynpname  TYPE SY-DYNNR. "   

  CALL FUNCTION 'BBP_UI_CTRL_PARTNER'  "
    EXPORTING
         IV_OBJTYPE = lv_iv_objtype
         IV_GUID = lv_iv_guid
         IS_PARTNER = lv_is_partner
         IV_MODE = lv_iv_mode
         IV_FIELDNAME = lv_iv_fieldname
         IV_PROGNAME = lv_iv_progname
         IV_DYNPNAME = lv_iv_dynpname
    CHANGING
         CV_SCREEN_INVISIBLE = lv_cv_screen_invisible
         CV_SCREEN_INPUT = lv_cv_screen_input
. " BBP_UI_CTRL_PARTNER




ABAP code using 7.40 inline data declarations to call FM BBP_UI_CTRL_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 REPID FROM SY INTO @DATA(ld_iv_progname).
 
"SELECT single DYNNR FROM SY INTO @DATA(ld_iv_dynpname).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!