This is to explain the standard behavior of the new function Service Bundling ,and will also provide some trouble shooting tips and importent programs.
In Extended Classic/Classic (excluding service procurement) Scenario, when SRM Purchase Order or Requisition with Service items were replicated to ERP, they were bundled as service lines under a single service item with item category 'D'. After the activation of the new Service Bundling function, SRM service items will not be bounded and can be posted to ECC PO in separate items.
In Extended Classic/Classic(excluding service procurement) Scenario, when SRM Purchase Order or Requisition with Service items were replicated to ERP, they were bundled as service lines under single service item with item category 'D'.
The drawback caused due to this behavour are:
With implementation of 'Service Bundling‘, each line item in SRM Purchase Order or Requisitions shall be replicated to ERP as different service items(D type) and will not bundled under single service item.
For this customizing, it is also necessary to activate the Business Function SRM_CONT_IMPR_2. For more details, check the documentation.
Programs and Trouble Shooting
1,Header field No_srv_boudling will be filled when PO is created.
2,During Transfer , in LBBP_BD_DRIVER_46AF16 both the header and customizing is checked.
3, Each item is grouped and mapped separately in LBBP_BD_DRIVER_46AF68
4, BAPI_POservice is mapped in LBBP_PDMAPF14
5 PO_ITEM is information mapped:
1771547 - SRM_Service bundling Interface note
1743852 - SRM Enablement- Service bundling
1881416 - Unlimited indicator not set for PO's with Service Bundling
1742388 - Undelete not available for deleted items in PO
1730712 - Undelete button inactive for deleted items in PO
1770653 - Deleted service items not transferred to ERP