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

Function BBP_WEIGHT_PUT_PBO 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_WEIGHT_PUT_PBO'".
EXPORTING
* IV_MODE = 'D' "
* IS_HEADER = "
* IS_ITEM = "
* IT_WEIGHT = "
* IT_DYNATTR = "
* IV_DOC_TYPE = "
* IV_VIEW = 'P' "
IMPORTING
EV_PROGNAME = "
EV_SCREEN = "
ET_MESSAGES = "
IMPORTING Parameters details for BBP_WEIGHT_PUT_PBO
IV_MODE -
Data type: CHAR1Default: 'D'
Optional: Yes
Call by Reference: Yes
IS_HEADER -
Data type: BBP_PDS_HEADEROptional: Yes
Call by Reference: Yes
IS_ITEM -
Data type: BBP_PDS_ITEMOptional: Yes
Call by Reference: Yes
IT_WEIGHT -
Data type: BBPT_PDS_WEIGHTOptional: Yes
Call by Reference: Yes
IT_DYNATTR -
Data type: BBPT_PDS_DYNATTRIBUTEOptional: Yes
Call by Reference: Yes
IV_DOC_TYPE -
Data type: CRMD_ORDERADM_H-OBJECT_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_VIEW -
Data type: CHAR1Default: 'P'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BBP_WEIGHT_PUT_PBO
EV_PROGNAME -
Data type: SYREPIDOptional: No
Call by Reference: Yes
EV_SCREEN -
Data type: SYDYNNROptional: No
Call by Reference: Yes
ET_MESSAGES -
Data type: BBPT_PD_MESSAGESOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_WEIGHT_PUT_PBO 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_iv_mode | TYPE CHAR1, " 'D' | |||
| lv_ev_progname | TYPE SYREPID, " | |||
| lv_ev_screen | TYPE SYDYNNR, " | |||
| lv_is_header | TYPE BBP_PDS_HEADER, " | |||
| lv_is_item | TYPE BBP_PDS_ITEM, " | |||
| lv_et_messages | TYPE BBPT_PD_MESSAGES, " | |||
| lv_it_weight | TYPE BBPT_PDS_WEIGHT, " | |||
| lv_it_dynattr | TYPE BBPT_PDS_DYNATTRIBUTE, " | |||
| lv_iv_doc_type | TYPE CRMD_ORDERADM_H-OBJECT_TYPE, " | |||
| lv_iv_view | TYPE CHAR1. " 'P' |
|   CALL FUNCTION 'BBP_WEIGHT_PUT_PBO' " |
| EXPORTING | ||
| IV_MODE | = lv_iv_mode | |
| IS_HEADER | = lv_is_header | |
| IS_ITEM | = lv_is_item | |
| IT_WEIGHT | = lv_it_weight | |
| IT_DYNATTR | = lv_it_dynattr | |
| IV_DOC_TYPE | = lv_iv_doc_type | |
| IV_VIEW | = lv_iv_view | |
| IMPORTING | ||
| EV_PROGNAME | = lv_ev_progname | |
| EV_SCREEN | = lv_ev_screen | |
| ET_MESSAGES | = lv_et_messages | |
| . " BBP_WEIGHT_PUT_PBO | ||
ABAP code using 7.40 inline data declarations to call FM BBP_WEIGHT_PUT_PBO
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.| DATA(ld_iv_mode) | = 'D'. | |||
| "SELECT single OBJECT_TYPE FROM CRMD_ORDERADM_H INTO @DATA(ld_iv_doc_type). | ||||
| DATA(ld_iv_view) | = 'P'. | |||
Search for further information about these or an SAP related objects