SAP BAPI_BUPR_RELSHIP_GET_DETAIL Function Module for SAP BP, BAPI: Read General Relationship









BAPI_BUPR_RELSHIP_GET_DETAIL is a standard bapi bupr relship get detail SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for SAP BP, BAPI: Read General Relationship processing and below is the pattern details for this FM, 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 bapi bupr relship get detail FM, simply by entering the name BAPI_BUPR_RELSHIP_GET_DETAIL into the relevant SAP transaction such as SE37 or SE38.

Function Group: BUBA_3
Program Name: SAPLBUBA_3
Main Program: SAPLBUBA_3
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_BUPR_RELSHIP_GET_DETAIL 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 'BAPI_BUPR_RELSHIP_GET_DETAIL'"SAP BP, BAPI: Read General Relationship
  EXPORTING
   BUSINESSPARTNER1 =  "Business Partner 1
   BUSINESSPARTNER2 =  "Business Partner Number 2
   RELATIONSHIPCATEGORY =  "Business Partner Relationship Category
*  VALIDFROMDATE = SY-DATLO "Validity Interval: Valid From
*  VALIDUNTILDATE = '99991231' "Validity Interval: Valid To
*  DIFFERENTIATIONTYPEVALUE =  "BP: Differentiation Type Characteristic (Change Document-Relevant)

 IMPORTING
   RELATIONSHIPTYPE =  "Business Partner Relationship Type

TABLES
*  RETURN =  "Messages
.



IMPORTING Parameters details for BAPI_BUPR_RELSHIP_GET_DETAIL

BUSINESSPARTNER1 - Business Partner 1

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

BUSINESSPARTNER2 - Business Partner Number 2

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

RELATIONSHIPCATEGORY - Business Partner Relationship Category

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

VALIDFROMDATE - Validity Interval: Valid From

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

VALIDUNTILDATE - Validity Interval: Valid To

Data type: BAPIBUS1006002_HEADER-VALIDUNTILDATE
Default: '99991231'
Optional: Yes
Call by Reference: No ( called with pass by value option)

DIFFERENTIATIONTYPEVALUE - BP: Differentiation Type Characteristic (Change Document-Relevant)

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

EXPORTING Parameters details for BAPI_BUPR_RELSHIP_GET_DETAIL

RELATIONSHIPTYPE - Business Partner Relationship Type

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

TABLES Parameters details for BAPI_BUPR_RELSHIP_GET_DETAIL

RETURN - Messages

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

Copy and paste ABAP code example for BAPI_BUPR_RELSHIP_GET_DETAIL 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_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_businesspartner1  TYPE BAPIBUS1006_HEAD-BPARTNER, "   
lv_relationshiptype  TYPE BAPIBUS1006_RELATIONSHIP-RELATIONSHIPTYPE, "   
lv_businesspartner2  TYPE BAPIBUS1006_HEAD-BPARTNER, "   
lv_relationshipcategory  TYPE BUT050-RELTYP, "   
lv_validfromdate  TYPE BAPIBUS1006002_HEADER-VALIDFROMDATE, "   SY-DATLO
lv_validuntildate  TYPE BAPIBUS1006002_HEADER-VALIDUNTILDATE, "   '99991231'
lv_differentiationtypevalue  TYPE BUT050-DFTVAL. "   

  CALL FUNCTION 'BAPI_BUPR_RELSHIP_GET_DETAIL'  "SAP BP, BAPI: Read General Relationship
    EXPORTING
         BUSINESSPARTNER1 = lv_businesspartner1
         BUSINESSPARTNER2 = lv_businesspartner2
         RELATIONSHIPCATEGORY = lv_relationshipcategory
         VALIDFROMDATE = lv_validfromdate
         VALIDUNTILDATE = lv_validuntildate
         DIFFERENTIATIONTYPEVALUE = lv_differentiationtypevalue
    IMPORTING
         RELATIONSHIPTYPE = lv_relationshiptype
    TABLES
         RETURN = lt_return
. " BAPI_BUPR_RELSHIP_GET_DETAIL




ABAP code using 7.40 inline data declarations to call FM BAPI_BUPR_RELSHIP_GET_DETAIL

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 BPARTNER FROM BAPIBUS1006_HEAD INTO @DATA(ld_businesspartner1).
 
"SELECT single RELATIONSHIPTYPE FROM BAPIBUS1006_RELATIONSHIP INTO @DATA(ld_relationshiptype).
 
"SELECT single BPARTNER FROM BAPIBUS1006_HEAD INTO @DATA(ld_businesspartner2).
 
"SELECT single RELTYP FROM BUT050 INTO @DATA(ld_relationshipcategory).
 
"SELECT single VALIDFROMDATE FROM BAPIBUS1006002_HEADER INTO @DATA(ld_validfromdate).
DATA(ld_validfromdate) = SY-DATLO.
 
"SELECT single VALIDUNTILDATE FROM BAPIBUS1006002_HEADER INTO @DATA(ld_validuntildate).
DATA(ld_validuntildate) = '99991231'.
 
"SELECT single DFTVAL FROM BUT050 INTO @DATA(ld_differentiationtypevalue).
 


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!