Kontakt

Ansicht
Dokumentation

CRMV_CND_PRC_ON - Enable Performance-Optimized Condition Processing and Pricing

CRMV_CND_PRC_ON - Enable Performance-Optimized Condition Processing and Pricing

Addresses (Business Address Services)   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you specify the transaction types for which you want to use performance-optimized condition processing and pricing. Performance-optimized condition processing and pricing encompasses the following features that provide improved system reaction times during editing of business transactions:

  • Performance-optimized pricing interface
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.
Migration to the new pricing interface can require some configuration effort and the reimplementation of Business Add-Ins (BAdIs), and should only be made after detailed analysis.
  • Delayed cross-item pricing
Business users can postpone 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-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 (Pricesassignment block) and data in the Price Details assignment block cannot be changed.

Performance-optimized condition processing and pricing are available for transaction types that are configured on the basis of the business objects (transaction categories) listed in SAP Note 1436942.

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

The new pricing interface is activated by default for the following transaction types:

  • SC1 (Service Contract New)
  • SCQ1 (Contract Quot. New)
  • IPMB (IPM Service Contract)
  • IPMC (IPM Usg Confirmation)
  • IPME (IPM Acq. Contract)
  • IPMV (IPM Sales Contract)

A default assignment of standard transaction fields to standard condition fields is defined in the standard system in the activity Display System Default Mapping of Condition Fields.

New Pricing Interface

You activate the new pricing interface for individual transaction types by entering them in this activity.

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. You can also change the assignment of standard transaction fields and conditions here. The configuration you make here overrides the default assignment.

Note:

  • The BAdIs in this Customizing section replace the BAdI CRM_COND_COM_BADI (which is located under 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

When you convert to performance-optimized pricing, you must reimplement your BAdIs and ensure that you obtain the same result as with the previous implementations.
  • If you are using payment schedule billing in Leasing and want to execute pricing for the payment schedule (to calculate taxes, for example), you must activate the new pricing interface.
  • 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.

Cross-Item Pricing

To activate the option to disable cross-item pricing on the UI, you select the Cross-Item Pricing checkbox. For more information about the effects of this setting, see the F1 Help for the chechbox.

If you select the Cross-Item Pricing checkbox, cross-item pricing is enabled by default for all users. To override the default setting for a user, set the user parameter CRM_DIS_CROSSITM_PRC to X. Cross-item pricing is thereby disabled for all transactions displayed by this user, unless the user manually enables it again on the UI.

This setting has performance benefits not only for transactions with group conditions, for which cross-item pricing can be delayed during transaction processing. It can also have performance benefits for transactions without group conditions. For this reason, we recommend that you select the Cross-Item Pricing checkbox for all transactions that use pricing procedures without group conditions.






TXBHW - Original Tax Base Amount in Local Currency   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 7308 Date: 20240606 Time: 151804     sap01-206 ( 112 ms )