SAP BBPU_GET_ATTRIBUTES_ANALOG Function Module for

Search SAP Function Modules

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

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

Function BBPU_GET_ATTRIBUTES_ANALOG 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 'BBPU_GET_ATTRIBUTES_ANALOG'"
  EXPORTING
   IV_OBJECT =  "
   IV_USER_ID =  "
   IV_ORGUNIT =  "

TABLES
   ET_ATTR =  "

EXCEPTIONS
   USER_NOT_FOUND = 1    ORGUNIT_NOT_FOUND = 2    OBJECT_ID_NOT_FOUND = 3    AMBIGUOUS_POSITION = 4 

.

IMPORTING Parameters details for BBPU_GET_ATTRIBUTES_ANALOG

IV_OBJECT -

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

IV_USER_ID -

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

IV_ORGUNIT -

Data type: OBJEC-OBJID
Optional: No
Call by Reference: Yes

TABLES Parameters details for BBPU_GET_ATTRIBUTES_ANALOG

ET_ATTR -

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

EXCEPTIONS details

USER_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

ORGUNIT_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

OBJECT_ID_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

AMBIGUOUS_POSITION -

Data type:
Optional: No
Call by Reference: Yes

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

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