SAP BBP_UPDATE_ATTRIBUTES Function Module for
BBP_UPDATE_ATTRIBUTES is a standard bbp update attributes 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 bbp update attributes FM, simply by entering the name BBP_UPDATE_ATTRIBUTES into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_ATTR_PDORG
Program Name: SAPLBBP_ATTR_PDORG
Main Program: SAPLBBP_ATTR_PDORG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_UPDATE_ATTRIBUTES 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 'BBP_UPDATE_ATTRIBUTES'".
EXPORTING
* IS_OBJECT = "
* USER_ID_P = "
* ORGUNIT_ID_P = "
* SCENARIO_P = 'BBP' "
* START_DATE_P = SY-DATUM "
* END_DATE_P = '99991231' "
* REPLACE_P = ' ' "
TABLES
* IT_ATTR_P = "
EXCEPTIONS
OBJECT_NOT_FOUND = 1 TIMES_INVALID = 2 UPDATE_ERROR = 3
IMPORTING Parameters details for BBP_UPDATE_ATTRIBUTES
IS_OBJECT -
Data type: SWHACTOROptional: Yes
Call by Reference: No ( called with pass by value option)
USER_ID_P -
Data type: BALUSEROptional: Yes
Call by Reference: No ( called with pass by value option)
ORGUNIT_ID_P -
Data type: OBJEC-OBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
SCENARIO_P -
Data type: OM_ATTRSCNDefault: 'BBP'
Optional: Yes
Call by Reference: No ( called with pass by value option)
START_DATE_P -
Data type: BAPILOGOND-GLTGVDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
END_DATE_P -
Data type: BAPILOGOND-GLTGBDefault: '99991231'
Optional: Yes
Call by Reference: No ( called with pass by value option)
REPLACE_P -
Data type: FLAGDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BBP_UPDATE_ATTRIBUTES
IT_ATTR_P -
Data type: BBP_ATTRIBUTESOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
OBJECT_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
TIMES_INVALID -
Data type:Optional: No
Call by Reference: Yes
UPDATE_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_UPDATE_ATTRIBUTES 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: | ||||
| lv_is_object | TYPE SWHACTOR, " | |||
| lt_it_attr_p | TYPE STANDARD TABLE OF BBP_ATTRIBUTES, " | |||
| lv_object_not_found | TYPE BBP_ATTRIBUTES, " | |||
| lv_user_id_p | TYPE BALUSER, " | |||
| lv_times_invalid | TYPE BALUSER, " | |||
| lv_orgunit_id_p | TYPE OBJEC-OBJID, " | |||
| lv_update_error | TYPE OBJEC, " | |||
| lv_scenario_p | TYPE OM_ATTRSCN, " 'BBP' | |||
| lv_start_date_p | TYPE BAPILOGOND-GLTGV, " SY-DATUM | |||
| lv_end_date_p | TYPE BAPILOGOND-GLTGB, " '99991231' | |||
| lv_replace_p | TYPE FLAG. " ' ' |
|   CALL FUNCTION 'BBP_UPDATE_ATTRIBUTES' " |
| EXPORTING | ||
| IS_OBJECT | = lv_is_object | |
| USER_ID_P | = lv_user_id_p | |
| ORGUNIT_ID_P | = lv_orgunit_id_p | |
| SCENARIO_P | = lv_scenario_p | |
| START_DATE_P | = lv_start_date_p | |
| END_DATE_P | = lv_end_date_p | |
| REPLACE_P | = lv_replace_p | |
| TABLES | ||
| IT_ATTR_P | = lt_it_attr_p | |
| EXCEPTIONS | ||
| OBJECT_NOT_FOUND = 1 | ||
| TIMES_INVALID = 2 | ||
| UPDATE_ERROR = 3 | ||
| . " BBP_UPDATE_ATTRIBUTES | ||
ABAP code using 7.40 inline data declarations to call FM BBP_UPDATE_ATTRIBUTES
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 OBJID FROM OBJEC INTO @DATA(ld_orgunit_id_p). | ||||
| DATA(ld_scenario_p) | = 'BBP'. | |||
| "SELECT single GLTGV FROM BAPILOGOND INTO @DATA(ld_start_date_p). | ||||
| DATA(ld_start_date_p) | = SY-DATUM. | |||
| "SELECT single GLTGB FROM BAPILOGOND INTO @DATA(ld_end_date_p). | ||||
| DATA(ld_end_date_p) | = '99991231'. | |||
| DATA(ld_replace_p) | = ' '. | |||
Search for further information about these or an SAP related objects