Approval Resets Price to zero

Question

Hi,
We have a problem in our shopping cart approval. For some materials, there is already a price and a vendor based on a contract. So once the shopping cart is created and approved, it will automatically be converted to a PO. What is happening is that once the shopping cart is approved, the price in the newly created PO becomes zero and it is routed back to the buyer for sourcing.
Why is it that the price resets to zero once the shopping cart has been approved?
Any help would be greatly appreciated.
Thanks in advance.

Answer 1

hi,
  Pls refer note 550071.
Some info pertaining to your problem---
The following logic has been designed for price transfer when you transfer shopping baskets from EBP component:
a) If a valid source is assigned to the shopping basket item (for example, an info record or a contract), the price is transferred to the purchase order from the source of supply - unless, the item is created via a catalog and it contains the catalog price.
b) All other items (for example via the free form entry or items with a material number) received the price in the purchase order from the source of supply.
Due to many customer requests, the logic has been changed a little:
a) As soon as an item contains a price higher than 0 - regardless of how the item is created (free entry or catalog) - this is transferred to the purchase order.
b) An exception is items with a material number since the valuation price can never be the purchase price.
c) All items without an explicit price receive the price from the info record or contract.
Reasoning :
A price determination in connection with the assigned source of supply is not carried out since this would mean several remote calls, to determine the correct price. Both info record and outline agreement contain master conditions. This means that the valid price must be determined together with the quantity and the delivery date again (because of price-quantity scales, header conditions, validity periods and so on). A completely new price determination would have to be carried out each time if the user changed the quantity or the date again - this is not carried out for reasons of performance. Since the purchase order resulting from the shopping basket contains the correct price from info record or outline agreement, this only affects creation of the shopping basket and may under certain circumstances influence the release(Workflow).
However in case of local Purchase Orders it can be done without any performance overhead and hence is supported.
If a different behavior is desired, you can implement the BAdI BBP_APPEND_ITEM to get the price of a Shopping Cart item with assigned source of supply from the backend. However the price won't show up in the online transaction while the user creates the Shopping Cart. It is updated by the BAdI when the Shopping Cart is saved.  Please evaluate the usage of this BAdI against performance concerns.
HTH.
BR,
Disha.
Pls reward points for useful answers.