Performance-Optimized Pricing

You can achieve improved system reaction times during editing of business transactions by implementing the performance-optimized pricing functions, which are described in detail below. These functions are available for transaction types that are configured on the basis of the business objects listed in SAP Note 1436942.

Performance-Optimized Pricing Interface

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. If you have previously used the standard pricing interface, you can continue to use it for existing transaction types and activate the performance-optimized pricing interface for new transaction types.

Option to Delay Cross-Item Pricing

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 Start of the navigation path More Next navigation step Disable Cross-Item Pricing End of the navigation path or Enable 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 business transaction when a pricing-relevant change is made.
On transaction header level, price conditions (Prices assignment block) and data in the Price Details assignment block cannot be changed.

The option to switch cross-item pricing on and off is only active on the user interface if the following apply:

The option to delay cross-item pricing is activated in Customizing (see “Prerequisites” below).
Group conditions apply to the transaction items, as determined from the pricing procedure.

Prerequisites

You have activated the business function Performance and Large Contracts (CRM_PERFORMANCE).

Performance-Optimized Pricing Interface

Note Note

Conversion to the performance-optimized pricing interface can require some configuration effort and the reimplementation of Business Add-Ins (BAdIs), and should only be made after detailed analysis.

If you use your own transaction types and have large contracts, we recommend that you activate performance-optimized condition processing and pricing for these transaction types also.

End of the note.

Recommendation

Before actively using performance-optimized pricing, we recommend that you perform regression testing to check price calculations.

End of the recommendation.

In the activity Enable Performance-Optimized Condition Processing and Pricing you activate the new pricing interface for individual transaction types.
If you have created customer-specific transaction or condition fields (under Pricing Define Settings for Pricing Maintain Field Catalog ), you assign these in the activity Define Customer-Specific Mapping of Condition Fields.
You can also change the assignment of standard transaction fields and conditions here. The configuration you make here overrides the default assignment.
The BAdI definitions provided under Business Add-Ins (BAdIs) replace the BAdI CRM_COND_COM_BADI (which is located under Pricing Define Settings for Pricing Adopt User-Defined Fields ). The performance-optimized 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_SELEC

Settings for Leasing

If you are using payment schedule billing and want to execute pricing for the payment schedule (to calculate taxes, for example), you must activate performance-optimized pricing.
You make settings for performance-optimized pricing in Customizing for Customer Relationship Management under Financial Services Basic Functions Performance-Optimized Condition Processing and Pricing . This section contains some activities with Leasing-specific Customizing fields.
For more information about the required Customizing settings, see SAP Solution Manager under Solutions/Applications SAP for Banking Scenarios Transaction Banking Lease Operations .

Delayed Cross-Item Pricing

You make settings in Customizing for Customer Relationship Management under Start of the navigation path Basic Functions Next navigation step Pricing Pricing in the Business Transaction Performance-Optimized Condition Processing and Pricing Enable Performance-Optimized Condition Processing and Pricing End of the navigation path . For more information, see the documentation for this activity.

Recommendation

We recommend that you also select the Cross-Item Pricing checkbox in Customizing for all transactions that use pricing procedures without group conditions, since this setting has performance benefits not only for transactions with group conditions. Performance can be improved especially when only a subset of items are changed in a transaction with a large number of items. Note, however, that the effect on performance depends on the number of items that require repricing.

End of the recommendation.