Skip to end of metadata
Go to start of metadata

Purpose

This is to explain the standard behavior of the new function Service Bundling ,and will also provide some trouble shooting tips and importent programs.

Overview

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.

Reason

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:

•End user is confused about having different service item indifferent system for the same Purchase Order. Users see multiple service line items in SRM and single service item in ERP.
•Different account assignment for each service item not possible.
•Different vendor flags cannot be assigned for each service item.
•Creation of follow on documents: confirmation and invoice from SRM causes problem as one to one mapping of service items is not maintained between SRM and ERP
•Maintaining 'Document History' and updating 'Statistic Information' at item level is not feasible
 

Benefits

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 each service item in SRM, an item will be created in ERP with item category 'D' and service item will be replicated as service line under it.
–For each limit in SRM, an item will be created with category 'D' and it will be replicated as limit.
–The behavior for material items remains the same
–From end user perspective, same number of items are displayed in both systems
–Different account assignment for each item is possible
–Different vendor flags can be assigned to each item.
–As one on one mapping is maintained for service items in both systems, creation of follow on documents is devoid of issue
–It is possible to maintain 'Document History' and update 'Statistics Information' at item level
–Confirmation/service entry sheet will be created for each of the service items
–Existing Purchase Orders before the activation of Service Bundling Functionality will continue to behave as it was earlier. There will be no impact of service bundling
 
 

Customizing 

 

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

BBP_PD_PO_CREATE

LBBP_BD_DRIVER_46AF16

LBBP_BD_DRIVER_46AF68

LBBP_PDMAPF01

LBBP_PDMAPF14

 

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:

Related Content

Related Documents

Related SAP Notes/KBAs

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