SAP BUPA_DESCRIPTION_GET Function Module for

Search SAP Function Modules

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

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

Function BUPA_DESCRIPTION_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 'BUPA_DESCRIPTION_GET'"
  EXPORTING
*  IV_PARTNER =  "Business Partner Number
*  IV_PARTNER_GUID =  "Business Partner GUID
*  IV_VALDT = SY-DATLO "

 IMPORTING
   EV_DESCRIPTION =  "Short Name of Business Partner
   EV_DESCRIPTION_NAME =  "
   EV_DESCRIP_NAME_LONG =  "
   EV_DESCRIPTION_LONG =  "
   EV_NAME_CITY_LONG =  "

TABLES
   ET_RETURN =  "Return Parameters

.

IMPORTING Parameters details for BUPA_DESCRIPTION_GET

IV_PARTNER - Business Partner Number

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

IV_PARTNER_GUID - Business Partner GUID

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

IV_VALDT -

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

EXPORTING Parameters details for BUPA_DESCRIPTION_GET

EV_DESCRIPTION - Short Name of Business Partner

Data type: BU_DESCRIP
Optional: No
Call by Reference: Yes

EV_DESCRIPTION_NAME -

Data type: BU_DESCRIP
Optional: No
Call by Reference: Yes

EV_DESCRIP_NAME_LONG -

Data type: BU_DESCRIP_NAME_LONG
Optional: No
Call by Reference: Yes

EV_DESCRIPTION_LONG -

Data type: BUS000FLDS-DESCRIP_LONG
Optional: No
Call by Reference: Yes

EV_NAME_CITY_LONG -

Data type: BUS000FLDS-DESCRIP_LONG
Optional: No
Call by Reference: Yes

TABLES Parameters details for BUPA_DESCRIPTION_GET

ET_RETURN - Return Parameters

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

Copy and paste ABAP code example for BUPA_DESCRIPTION_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.

ABAP code using 7.40 inline data declarations to call FM BUPA_DESCRIPTION_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.

Search for further information about these or an SAP related objects