SAP BUP_PARTNER_GET Function Module for









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

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



Function BUP_PARTNER_GET 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 'BUP_PARTNER_GET'"
  EXPORTING
*  I_PARTNER =  "Partner Number
*  I_CP_EXCLUDE = ' ' "
*  I_IS_EXCLUDE = ' ' "
*  IV_REQ_BLK_MSG = ' ' "
*  I_PARTNERGUID =  "
*  I_OPERATION =  "
*  I_ADDRNUMBER =  "
*  I_ADDRGUID =  "
*  I_XMEMORY = ' ' "
*  I_XWA = ' ' "
*  I_VALDT = '00000000' "Validity Date
*  I_VALDT_SEL = SY-DATLO "

 IMPORTING
   E_BUT000 =  "General Data I
   E_BUT000_INT =  "
   E_BUT001 =  "General Data II
   E_BUT000_GLOBAL =  "
   E_BUT000_ADDRESS =  "
   E_BUT000_VALIDITY =  "

TABLES
*  T_ADTEL =  "
*  T_ADSSF =  "
*  T_ADURI =  "
*  T_ADPAG =  "
*  T_BUT000 =  "
*  T_BUT000_INT =  "
*  T_ADFAX =  "
*  T_ADTTX =  "
*  T_ADTLX =  "
*  T_ADSMTP =  "
*  T_ADRML =  "
*  T_ADX400 =  "
*  T_ADRFC =  "
*  T_ADPRT =  "

EXCEPTIONS
   PARTNER_NOT_FOUND = 1    WRONG_PARAMETERS = 2    INTERNAL_ERROR = 3    BLOCKED_PARTNER = 4
.



IMPORTING Parameters details for BUP_PARTNER_GET

I_PARTNER - Partner Number

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

I_CP_EXCLUDE -

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_IS_EXCLUDE -

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_REQ_BLK_MSG -

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PARTNERGUID -

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

I_OPERATION -

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

I_ADDRNUMBER -

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

I_ADDRGUID -

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

I_XMEMORY -

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_XWA -

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_VALDT - Validity Date

Data type: SY-DATLO
Default: '00000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_VALDT_SEL -

Data type: SY-DATLO
Default: SY-DATLO
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BUP_PARTNER_GET

E_BUT000 - General Data I

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

E_BUT000_INT -

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

E_BUT001 - General Data II

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

E_BUT000_GLOBAL -

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

E_BUT000_ADDRESS -

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

E_BUT000_VALIDITY -

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

TABLES Parameters details for BUP_PARTNER_GET

T_ADTEL -

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

T_ADSSF -

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

T_ADURI -

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

T_ADPAG -

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

T_BUT000 -

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

T_BUT000_INT -

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

T_ADFAX -

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

T_ADTTX -

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

T_ADTLX -

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

T_ADSMTP -

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

T_ADRML -

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

T_ADX400 -

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

T_ADRFC -

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

T_ADPRT -

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

EXCEPTIONS details

PARTNER_NOT_FOUND - Partner Not Found

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

WRONG_PARAMETERS - Wrong parameter passed

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR - An internal error has occurred

Data type:
Optional: No
Call by Reference: Yes

BLOCKED_PARTNER -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BUP_PARTNER_GET 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_t_adtel  TYPE STANDARD TABLE OF ADTEL, "   
lv_e_but000  TYPE BUS000, "   
lv_i_partner  TYPE BUT000-PARTNER, "   
lv_partner_not_found  TYPE BUT000, "   
lt_t_adssf  TYPE STANDARD TABLE OF ADSSF, "   
lv_i_cp_exclude  TYPE BOOLE-BOOLE, "   SPACE
lt_t_aduri  TYPE STANDARD TABLE OF ADURI, "   
lv_i_is_exclude  TYPE BOOLE-BOOLE, "   SPACE
lt_t_adpag  TYPE STANDARD TABLE OF ADPAG, "   
lv_iv_req_blk_msg  TYPE BOOLE-BOOLE, "   SPACE
lt_t_but000  TYPE STANDARD TABLE OF BUS000_TD, "   
lt_t_but000_int  TYPE STANDARD TABLE OF BUS000_INT_TD, "   
lt_t_adfax  TYPE STANDARD TABLE OF ADFAX, "   
lv_e_but000_int  TYPE BUS000_INT, "   
lv_i_partnerguid  TYPE BUT000-PARTNER_GUID, "   
lv_wrong_parameters  TYPE BUT000, "   
lt_t_adttx  TYPE STANDARD TABLE OF ADTTX, "   
lv_e_but001  TYPE BUS001, "   
lv_i_operation  TYPE TB008S-OPERATION, "   
lv_internal_error  TYPE TB008S, "   
lt_t_adtlx  TYPE STANDARD TABLE OF ADTLX, "   
lv_i_addrnumber  TYPE BUT020-ADDRNUMBER, "   
lv_blocked_partner  TYPE BUT020, "   
lv_e_but000_global  TYPE BUS000_GLB, "   
lt_t_adsmtp  TYPE STANDARD TABLE OF ADSMTP, "   
lv_i_addrguid  TYPE BUT020-ADDRESS_GUID, "   
lv_e_but000_address  TYPE BUS000_EXT, "   
lt_t_adrml  TYPE STANDARD TABLE OF ADRML, "   
lv_i_xmemory  TYPE BOOLE-BOOLE, "   SPACE
lv_e_but000_validity  TYPE BUS000_VALIDITY, "   
lv_i_xwa  TYPE BOOLE-BOOLE, "   SPACE
lt_t_adx400  TYPE STANDARD TABLE OF ADX400, "   
lv_i_valdt  TYPE SY-DATLO, "   '00000000'
lt_t_adrfc  TYPE STANDARD TABLE OF ADRFC, "   
lt_t_adprt  TYPE STANDARD TABLE OF ADPRT, "   
lv_i_valdt_sel  TYPE SY-DATLO. "   SY-DATLO

  CALL FUNCTION 'BUP_PARTNER_GET'  "
    EXPORTING
         I_PARTNER = lv_i_partner
         I_CP_EXCLUDE = lv_i_cp_exclude
         I_IS_EXCLUDE = lv_i_is_exclude
         IV_REQ_BLK_MSG = lv_iv_req_blk_msg
         I_PARTNERGUID = lv_i_partnerguid
         I_OPERATION = lv_i_operation
         I_ADDRNUMBER = lv_i_addrnumber
         I_ADDRGUID = lv_i_addrguid
         I_XMEMORY = lv_i_xmemory
         I_XWA = lv_i_xwa
         I_VALDT = lv_i_valdt
         I_VALDT_SEL = lv_i_valdt_sel
    IMPORTING
         E_BUT000 = lv_e_but000
         E_BUT000_INT = lv_e_but000_int
         E_BUT001 = lv_e_but001
         E_BUT000_GLOBAL = lv_e_but000_global
         E_BUT000_ADDRESS = lv_e_but000_address
         E_BUT000_VALIDITY = lv_e_but000_validity
    TABLES
         T_ADTEL = lt_t_adtel
         T_ADSSF = lt_t_adssf
         T_ADURI = lt_t_aduri
         T_ADPAG = lt_t_adpag
         T_BUT000 = lt_t_but000
         T_BUT000_INT = lt_t_but000_int
         T_ADFAX = lt_t_adfax
         T_ADTTX = lt_t_adttx
         T_ADTLX = lt_t_adtlx
         T_ADSMTP = lt_t_adsmtp
         T_ADRML = lt_t_adrml
         T_ADX400 = lt_t_adx400
         T_ADRFC = lt_t_adrfc
         T_ADPRT = lt_t_adprt
    EXCEPTIONS
        PARTNER_NOT_FOUND = 1
        WRONG_PARAMETERS = 2
        INTERNAL_ERROR = 3
        BLOCKED_PARTNER = 4
. " BUP_PARTNER_GET




ABAP code using 7.40 inline data declarations to call FM BUP_PARTNER_GET

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 PARTNER FROM BUT000 INTO @DATA(ld_i_partner).
 
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_cp_exclude).
DATA(ld_i_cp_exclude) = ' '.
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_is_exclude).
DATA(ld_i_is_exclude) = ' '.
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_iv_req_blk_msg).
DATA(ld_iv_req_blk_msg) = ' '.
 
 
 
 
 
"SELECT single PARTNER_GUID FROM BUT000 INTO @DATA(ld_i_partnerguid).
 
 
 
 
"SELECT single OPERATION FROM TB008S INTO @DATA(ld_i_operation).
 
 
 
"SELECT single ADDRNUMBER FROM BUT020 INTO @DATA(ld_i_addrnumber).
 
 
 
 
"SELECT single ADDRESS_GUID FROM BUT020 INTO @DATA(ld_i_addrguid).
 
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xmemory).
DATA(ld_i_xmemory) = ' '.
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xwa).
DATA(ld_i_xwa) = ' '.
 
 
"SELECT single DATLO FROM SY INTO @DATA(ld_i_valdt).
DATA(ld_i_valdt) = '00000000'.
 
 
 
"SELECT single DATLO FROM SY INTO @DATA(ld_i_valdt_sel).
DATA(ld_i_valdt_sel) = SY-DATLO.
 


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!