Additional Blogs by Members
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member

Thank god!  SAP finally put an end to the performance horror stories with IPC in large order and contracts scenario with EHP1. 

I blogged about how persisted cumulative values of an order or contract in a table  solved the performance nightmares caused by the cumulative values being calculated each time an order or contract is opened.   Let’s understand further the pricing related performance improvements in EHP1.

Pricing totals are in the header of service contractor with EHP1: You have “Pricing Totals” assignment block to show the cumulated values prior to EHP1.  Large contracts with several 100’s of line items caused performance issues as system calculated the totals whenever a contract is opened. Now the totals are part of the header based on the persistent cumulated values in a table and the problem was solved.  Get access to EHP1 OKP if interested to know the technical details behind it.

New Pricing Interface: I had hard time answering a customer’s questions such as “Why pricing was called when I was updating non-pricing fields in an order, Is there a way to stop it as it is slowing the system?  Those questions will no more rises after implementing EHP1. Pricing is only called when changes are made to the pricing relevant fields with the new interface and it is now checked against the buffer also. Sales and service quotes and orders, package quote, financing contract and quote and multiple asset contracts are covered under the new pricing interface.  A mapping table is available to maintain the pricing relevant fields to add any of the object specific definitions. A mapping table to define project specific or customer specific definitions is also available.  In addition BAdI’s are available to implement customer specific pricing logic.

Option to disable cross-item pricing : Any customer using the cross-item pricing  knows  how painfully slow the system  is when an order or contract has multiple items  as system checks the cross-item pricing for a newly entered, or updated line item.  EHP1 provided an option to temporarily disable the cross-item function while entering, editing or deleting a line item(s).A user can enable the cross-item pricing at the end of processing the document or directly save the document which triggers the cross-item pricing for the whole document and displays/saves the document.

Delayed item load mode: Load the line items into IPC buffer on demand vs. loading all the line items into the buffer when an order or contract is opened in the earlier versions.  No need to explain how faster and efficient the new mode is.

Other pricing improvements that are worth mentioning, improved reading of item pricing data, changed logic to get product hierarchies and categories.

Get access to SAP CRM 7.0 EHP1 and read SAP note 1436942 if you are interested in deep diving into the above functionalities.