SAP BUP_PARTNER_CHECK Function Module for

Search SAP Function Modules

BUP_PARTNER_CHECK is a standard bup partner check 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 check FM, simply by entering the name BUP_PARTNER_CHECK 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_CHECK 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_CHECK'"
  EXPORTING
*  I_PARTNER =  "Partner Number
*  IV_CHECK_CHNG_ACTVT =  "
*  I_PARTNERGUID =  "
*  I_RLTYP =  "Role Category
*  I_DFVAL =  "Diff.type characterization
*  I_XMEMORY = ' ' "
*  I_XWA = ' ' "
*  I_VALDT = '00000000' "Validity Date
*  I_VALDT_SEL = SY-DATLO "
*  IV_REQ_BLK_MSG = ' ' "

EXCEPTIONS
   PARTNER_NOT_FOUND = 1    ROLE_NOT_FOUND = 2    ROLE_WITH_DFVAL_NOT_FOUND = 3    WRONG_PARAMETERS = 4    INTERNAL_ERROR = 5    BLOCKED_PARTNER = 6 

.

IMPORTING Parameters details for BUP_PARTNER_CHECK

I_PARTNER - Partner Number

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

IV_CHECK_CHNG_ACTVT -

Data type: BOOLE_D
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_RLTYP - Role Category

Data type: BUT100-RLTYP
Optional: Yes
Call by Reference: Yes

I_DFVAL - Diff.type characterization

Data type: BUT100-DFVAL
Optional: Yes
Call by Reference: Yes

I_XMEMORY -

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_XWA -

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_VALDT - Validity Date

Data type: SY-DATLO
Default: '00000000'
Optional: Yes
Call by Reference: Yes

I_VALDT_SEL -

Data type: SY-DATLO
Default: SY-DATLO
Optional: Yes
Call by Reference: Yes

IV_REQ_BLK_MSG -

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

EXCEPTIONS details

PARTNER_NOT_FOUND -

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

ROLE_NOT_FOUND -

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

ROLE_WITH_DFVAL_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_CHECK 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 BUP_PARTNER_CHECK

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