SAP BAPI_BUPA_STATUS_GETDETAIL Function Module for Business Partner: Read Status
BAPI_BUPA_STATUS_GETDETAIL is a standard bapi bupa status getdetail SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Business Partner: Read Status 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 bupa status getdetail FM, simply by entering the name BAPI_BUPA_STATUS_GETDETAIL 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: 07-Feb-2002
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function BAPI_BUPA_STATUS_GETDETAIL 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_BUPA_STATUS_GETDETAIL'"Business Partner: Read Status.
EXPORTING
BUSINESSPARTNER = "Business Partner Number
TABLES
STATUS = "BAPI Transfer Structure: Business Partner Status (Read)
* RETURN = "Messages
IMPORTING Parameters details for BAPI_BUPA_STATUS_GETDETAIL
BUSINESSPARTNER - Business Partner Number
Data type: BAPIBUS1006_HEAD-BPARTNEROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_BUPA_STATUS_GETDETAIL
STATUS - BAPI Transfer Structure: Business Partner Status (Read)
Data type: BAPIBUS1006_CRM_JEST_GETOptional: No
Call by Reference: Yes
RETURN - Messages
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_BUPA_STATUS_GETDETAIL 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_status | TYPE STANDARD TABLE OF BAPIBUS1006_CRM_JEST_GET, " | |||
lv_businesspartner | TYPE BAPIBUS1006_HEAD-BPARTNER, " | |||
lt_return | TYPE STANDARD TABLE OF BAPIRET2. " |
  CALL FUNCTION 'BAPI_BUPA_STATUS_GETDETAIL' "Business Partner: Read Status |
EXPORTING | ||
BUSINESSPARTNER | = lv_businesspartner | |
TABLES | ||
STATUS | = lt_status | |
RETURN | = lt_return | |
. " BAPI_BUPA_STATUS_GETDETAIL |
ABAP code using 7.40 inline data declarations to call FM BAPI_BUPA_STATUS_GETDETAIL
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_businesspartner). | ||||
Search for further information about these or an SAP related objects