Use
As of SAP enhancement package 1 for SAP CRM 7.0, business function Performance and Large Contracts
• BUS2000112
(CRM_PERFORMANCE), system performance during pricing is optimized by the functions described below. These functions are available for transaction types that are configured on the basis of the following business objects (transaction categories):
Service Contract
• BUS2000115
(service contracts, service contract quotations) Sales
• BUS2000116
(sales orders, quotations) Service Process
• BUS2000121
(service orders, service order quotations, package quotations)
• BUS2000231
Sales Contract
• BUS2000230
License Acquisition Contract License Sales Contract
• BUS2000232
• BUS2000308
License Usage Confirmation
• BUS2000114
Financial Services Main Contract CRM
New Pricing Interface
CRM Financing Contract
A new technical interface between business transaction and pricing engine improves system reaction time during editing of transactions. Configurable mapping between the transaction fields and condition fields allows you to set up pricing so that the system only calls the pricing engine for pricing-relevant changes, based on the transaction's pricing procedure. You activate the new pricing interface for individual transaction types.
You can continue to use the old pricing interface after you have activated the business function Performance and Large Contracts (CRM_PERFORMANCE). Conversion to the new pricing can require some configuration effort and the reimplementation of Business Add-Ins (BAdIs), and should only be made after detailed analysis.
Note:
Delayed Cross-Item Pricing
Before actively using performance-optimized pricing, we recommend that you perform regression testing to check price calculations.
You can enable business users to delay price calculations that require aggregated cross-item data (calculations where group conditions apply). By doing this they can improve system reaction time during editing of transactions, in particular transactions with a large number of items. The following are examples of cross-item pricing calculations:
• Taxes based on the gross transaction value
• Discounts and surcharges based on the total value of multiple items value (for example, total weight)
• Distribution of rounding differences
Processing of structure conditions and manually-entered header conditions is also delayed.
Business users can switch cross-item pricing on and off with the option More -> Disable Cross-Item Pricing / Enable Cross-Cross-Item Pricing (however, this option is not available with SAP Intellectual Property Management). When the user enables cross-item pricing again or saves the transaction, cross-item pricing takes place if necessary, that is, if price data is not
up-to-date.
When cross-item pricing is disabled, the following apply:
• Price totals are not displayed in the transaction when a pricing-relevant change is made.
• On transaction header level, price conditions (Prices assignment block) and data in the Price Details
Effects on Existing Data
assignment block cannot be changed.
When you convert to performance-optimized pricing, you must reimplement your BAdIs (see
"Effects on Customizing"). When you reimplement your BAdIs, you must ensure that you obtain the same result.
Effects on System Administration
To override the default setting (cross-item pricing active) for a user, set the user parameter CRM_DIS_CROSSITM_PRC to X
New Pricing Interface
. Cross-item pricing is disabled for all transactions displayed by this user, unless the user manually enables it again using the menu option on the UI.
You make settings for the new pricing interface in Customizing for Customer Relationship Management under
A default assignment of standard transaction fields to standard condition fields is defined in the standard system in the activity
Basic Functions -> Pricing -> Pricing in the Business Transaction ->
Performance-Optimized Condition Processing and Pricing.
Display System Default Mapping of Condition Fields. If you have created customer-specific transaction or condition fields in the activity Maintain Field Catalog, you assign these in the activity Define Customer-Specific Mapping of Condition Fields
The BAdIs in the above Customizing section replace the BAdI CRM_COND_COM_BADI (which is located under
. You can also change the assignment of standard transaction fields and conditions here.
The configuration you make here overrides the default assignment.
Customer Relationship Management -> Basic Functions -> Pricing ->
Define Settings for Pricing -> Adopt User-Defined Fields
The new pricing interface does not support the following BAdIs, in addition:
).
• CRM_COND_COM_MULT
• CRM_CONFIG_GRID_PRICE
• CRM_PRIDOC_NAMEVALUE
• CRM_PRIDOC_GRP_PROC (only method MAIN_ITEM_PRICING is not supported)
• CRM_PRIDOC_COM_BADI
• TAX_PARTNER_SELECT
You make settings for performance-optimized pricing in Customizing for Note for Leasing:
Customer Relationship Management -> Financial Services -> Basic Functions -> Performance-Optimized Condition Processing and Pricing.
The standard system contains new, performance-optimized pricing procedures. Before you can use the new pricing interface, you must assign the performance-optimized pricing procedure to your sales organization under
This section contains some activities with Leasing-specific Customizing fields.
Customer Relationship Management -> Basic Functions ->
Pricing -> Pricing in the Business Transaction -> Determine Pricing Procedures
In addition making the Customizing settings described above, you need to check your search .
strategies for customer-specific settings. Search strategies are used in the activities in which you define the mapping of condition fields (Define Customer-Specific Mapping of Condition Fields and Display System Default Mapping of Condition Fields). It is therefore important to check the completeness of the search strategies used with regard to customer-specific entries (such as item categories). If, for example, the customer-specific item categories are not assigned to a search strategy, we cannot guarantee that pricing will function correctly. We recommend you use the standard Customizing as a template: Customer Relationship Management -> Financial Services -> Basic Functions -> Cross-Item Functions -> Define and Assign Search Strategies -> Steps: Define Search Strategy and Override Default Assignment of Search Strategy
Delayed Cross-Item Pricing
.
You make settings for cross-item pricing under Customer Relationship Management ->
Basic Functions -> Pricing -> Pricing in the Business Transaction ->
Performance-Optimized Condition Processing and Pricing -> Enable Performance-Performance-Optimized Condition Processing and Pricing.