BE_OBJECT_ID and BE_OBJ_ITEM are not getting updated for some line items in table BBP_PDBEI

[former_member198566]

Hi,

Though we are not facing any errors while document creation but the tables are not getting updated for few PO's and SC's .

BE_OBJECT_ID and BE_OBJ_ITEM are not getting updated for some line items in BBP_PDBEI of Purchase order in SRM.

We are in SRM 7, EHP2, SP14 - Extended Classic Scenario.

Please suggest

Thanks and Regards,

Abhishek

[summer_wang]

Hi Abhishek
Both note are of SAPK-70216INSRMSRV can be applied in your system
2203129 - Backend Logical System Missing in Item
2160920 - Backend Data Missing in Change Version

Best regards

[former_member198566]

Hi Summer,

Sorry for the confusion. We are into SAPK-71314INSRMSRV

Please suggest.

Thanks and Regards,

Abhishek Kumar

[summer_wang]

Hi ,

For PO please ensure the following note are applied. Please ensure user will not edit PO (lock table) during transfer stage.

2207882 Backend data cleared by change version
2205256 Backend data cleared by change version
2203129 Backend Logical System Missing in Item
2160920 Backend Data Missing in Change Version

For shopping cart：

In standard system design the BBP_PDBEI is not updated in this special scenario, that is Create the PO item from "add from old cart".

If you want to change the behavior, please consider badi: BBP_DOC_SAVE_BADI with FUNCTION 'BBP_PD_SC_SET_ITEM_BE_REF' . After the badi there will be commit to update the SC.

There is no standard report to change the original created SC as it is a standard design not considered as inconsistency.

However you can create your own report according to your actual need.

Please refer to example code in an old report in note##1284534.

After calling 'BBP_PD_SC_SET_ITEM_BE_REF', commit work is needed.

************

CALL FUNCTION 'BBP_PD_SC_SET_ITEM_BE_REF'
EXPORTING
iv_item_guid = e_item-guid
iv_be_object_id = i_be_no " initial in case of CLEAR
iv_be_object_type = e_item-be_object_type
iv_be_obj_item = i_be_i " initial in case of CLEAR
iv_be_introw = e_item-be_introw
iv_be_packno = e_item-be_packno
iv_write_relations = gc_no
TABLES
et_messages = lt_messages.
ELSE.
CALL FUNCTION 'BBP_PD_SC_SET_ITEM_BE_REF'
EXPORTING
iv_item_guid = e_item-guid
iv_be_object_id = e_item-be_object_id
iv_be_object_type = e_item-be_object_type
iv_be_obj_item = e_item-be_obj_item
iv_be_introw = e_item-be_introw
iv_be_packno = e_item-be_packno
iv_write_relations = gc_yes
TABLES
et_messages = lt_messages.
ENDIF.

* check return
LOOP AT lt_messages WHERE msgty = c_msgty_a OR
msgty = c_msgty_e.
CLEAR: lv_text1.

lv_text1 = 'Critical error in BBP_PD_SC_SET_ITEM_BE_REF'.

MESSAGE e001(bbp_pu) WITH lv_text2.

ENDLOOP.

......

CALL FUNCTION 'BBP_PD_SC_SAVE'
EXPORTING
iv_header_guid = e_item-header.

COMMIT WORK AND WAIT.

**********

Best regards

Summer Wang

[former_member198566]

Hi Summer,

Looks like Note 2207882 and 2205256 are not opened for all clients, am unable to view these notes. Other two notes are not valid for us as we are in EHP2, SP14.

Please suggest further.

Thanks and Regards,

Abhishek