SAP DB_BCONT_SELECT_PARTNER Function Module for









DB_BCONT_SELECT_PARTNER is a standard db bcont select 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 db bcont select partner FM, simply by entering the name DB_BCONT_SELECT_PARTNER into the relevant SAP transaction such as SE37 or SE38.

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



Function DB_BCONT_SELECT_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 'DB_BCONT_SELECT_PARTNER'"
EXPORTING
* X_ACTUAL = "
* X_DATEFROM = "
* X_DATETO = "
* X_MAXCOUNT = "
X_PARTNER = "
* X_OBJTYPE = "
* X_OBJKEY = "
* X_OBJSEARCHCONTROL = "

IMPORTING
Y_COUNT = "

TABLES
YT_BCONT = "

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for DB_BCONT_SELECT_PARTNER

X_ACTUAL -

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

X_DATEFROM -

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

X_DATETO -

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

X_MAXCOUNT -

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

X_PARTNER -

Data type: BCONT-PARTNER
Optional: No
Call by Reference: No ( called with pass by value option)

X_OBJTYPE -

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

X_OBJKEY -

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

X_OBJSEARCHCONTROL -

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

EXPORTING Parameters details for DB_BCONT_SELECT_PARTNER

Y_COUNT -

Data type: BCONTGEN-MAXCOUNT
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for DB_BCONT_SELECT_PARTNER

YT_BCONT -

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

EXCEPTIONS details

NOT_FOUND -

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

Copy and paste ABAP code example for DB_BCONT_SELECT_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_y_count  TYPE BCONTGEN-MAXCOUNT, "   
lv_x_actual  TYPE BCONTGEN-ACTUAL, "   
lt_yt_bcont  TYPE STANDARD TABLE OF BCONT, "   
lv_not_found  TYPE BCONT, "   
lv_x_datefrom  TYPE BCONT-CTDATE, "   
lv_x_dateto  TYPE BCONT-CTDATE, "   
lv_x_maxcount  TYPE BCONTGEN-MAXCOUNT, "   
lv_x_partner  TYPE BCONT-PARTNER, "   
lv_x_objtype  TYPE BCONT_OBJ-OBJTYPE, "   
lv_x_objkey  TYPE BCONT_OBJ-OBJKEY, "   
lv_x_objsearchcontrol  TYPE BCONTGEN-KENNZX. "   

  CALL FUNCTION 'DB_BCONT_SELECT_PARTNER'  "
    EXPORTING
         X_ACTUAL = lv_x_actual
         X_DATEFROM = lv_x_datefrom
         X_DATETO = lv_x_dateto
         X_MAXCOUNT = lv_x_maxcount
         X_PARTNER = lv_x_partner
         X_OBJTYPE = lv_x_objtype
         X_OBJKEY = lv_x_objkey
         X_OBJSEARCHCONTROL = lv_x_objsearchcontrol
    IMPORTING
         Y_COUNT = lv_y_count
    TABLES
         YT_BCONT = lt_yt_bcont
    EXCEPTIONS
        NOT_FOUND = 1
. " DB_BCONT_SELECT_PARTNER




ABAP code using 7.40 inline data declarations to call FM DB_BCONT_SELECT_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 MAXCOUNT FROM BCONTGEN INTO @DATA(ld_y_count).
 
"SELECT single ACTUAL FROM BCONTGEN INTO @DATA(ld_x_actual).
 
 
 
"SELECT single CTDATE FROM BCONT INTO @DATA(ld_x_datefrom).
 
"SELECT single CTDATE FROM BCONT INTO @DATA(ld_x_dateto).
 
"SELECT single MAXCOUNT FROM BCONTGEN INTO @DATA(ld_x_maxcount).
 
"SELECT single PARTNER FROM BCONT INTO @DATA(ld_x_partner).
 
"SELECT single OBJTYPE FROM BCONT_OBJ INTO @DATA(ld_x_objtype).
 
"SELECT single OBJKEY FROM BCONT_OBJ INTO @DATA(ld_x_objkey).
 
"SELECT single KENNZX FROM BCONTGEN INTO @DATA(ld_x_objsearchcontrol).
 


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!