Technical Name of Business Function |
|
Type of Business Function |
Enterprise Business Function |
Available As Of |
SAP enhancement package 1 for SAP CRM 7.0 |
Technical Usage |
CRM Core |
Application Component |
Financial Services, Business Transaction (CRM-IFS-BTX) |
Directly Dependent Business Function Requiring Activation in Addition |
|
With this business function, you can:
Optimize system performance when processing quotations and contracts for a large number of documents and items
Create and process multiple-asset contracts
Bill and pass-through payments from third-party business relationships
Trigger calculation of the payment schedule for the service item as well as calculate broken periods for the service item
Note
You can only use the business function Performance Improvements
(CRM_FS_PERF_1
) if you have implemented SAP Leasing.
You have installed the following components as of the version mentioned:
Type of Component |
Component |
Is Needed Only for the Following Features |
Software component |
BBPCRM 701 |
|
Software component |
SAP_APPL 605 |
|
Software component |
EA_APPL 605 |
You must activate the business function in Customizing for SAP CRM under:
.
Customizing
The business function is delivered with standard settings. If you have created customer-specific Customizing settings (such as your own transaction types and item categories), you must adjust Customizing. You use SAP Solution Manager to configure the solution. For more information about the required Customizing settings, see SAP Solution Manager under
as well as Customizing for SAP CRM.See also the information in the following release notes:
CRM_FS_PERF_1: Performance Improvements for Quotation and Contract Processing (New)
CRM_FS_PERF_1: Multiple-Asset Contract (New)
CRM_FS_PERF_1: Billing of Payments from Third-Party Business Relationships (New)
CRM_FS_PERF_1: Harmonization of Financing and Service Item (New)
New features that optimize system performance are available in the following areas:
Payment schedule billing
Performance-optimized pricing
Action determination
Partner determination
Dates
Determination of third-party programs
You can use these new features to suit your requirements. Payment schedule billing is the central element for the performance optimization of the contract management system.
Payment schedule billing
When the system creates the billing due list in billing, it uses the payment schedule as the data source. Previously, all billing-relevant data came from the billing request items (BRIs) only. The leasing document now no longer contains BRIs, with the exception of the condition-based BRIs (such as for an upfront one-time tax payment) that are still generated. Instead, billing-relevant fields have been added to the payment schedule. You activate payment schedule billing for each item category. You can use the old billing type (BRI) and the new billing type (payment schedule) in parallel but not in the same document. This is made possible by using different item categories. If you want to use both billing types in parallel, you must create user-specific item categories for payment schedule billing and activate these for payment schedule billing.
Example
Contract A with item categories a: billing using BRIs
Contract B with item categories b: payment schedule billing
Note
You cannot adapt existing item categories that are already being used in transactions to payment schedule billing. These items are still processed according to the old processing method (generation of BRIs in document).
Payment schedule billing is available for the object types BUS2000301
and BUS2000137
. Standard Customizing provides new item category groups and item categories for creating financing and service products. Before you can use payment schedule billing, you must create new financing and service products in the master data that are based on the new item categories.
If you want to use your own item categories, you must make additional settings in Customizing after you have activated the business function.
If you want to use payment schedule billing, you must also activate the business function Performance and Large Contracts
(CRM_PERFORMANCE
).
Performance-optimized pricing
Note
If you want to use performance-optimized pricing, you have to activate the business function Performance and Large Contracts
(CRM_PERFORMANCE
).
Configurable mapping between the document fields and condition fields allows you to configure pricing so that the system only calls it if the relevant document fields have been changed. You activate the new pricing for each transaction type. 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.
Before you can use performance-optimized pricing, you must make additional settings in Customizing after you have activated the business function.
Note
You can continue to use the old pricing after you have activated the business function. 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.
Action determination
New action profiles and actions are available. Furthermore, actions are no longer determined using the rule type WF, Workflow Conditions
but are now determined using the rule type COD, Conditions Using Business-Add-In (BAdI)
.
Performance-optimized action determination is available once you have activated the business function.
Partner determination
The settings in standard Customizing have been converted. Internal processes for the processing of business partners have also been optimized.
Performance-optimized partner determination is available once you have activated the business function.
Dates
The initialization of dates has been optimized for the object type BUS2000114
. The Business Add-In (BAdI) BADI_CRM_DATES_RTO
has been implemented for this purpose. Internal processes for the processing of dates have also been optimized.
This new feature is available once you have activated the business function.
Determination of third-party programs
Standard Customizing has been adjusted so that third-party programs are only found for leases and no longer for lease quotations. The check on the alternative product category as a determination criterion used to determine third-party programs is now mapped in the access sequence in Customizing. The determination and assignment of third-party programs has been optimized and made more flexible. For example, a third-party program that has already been assigned is not simply deleted when determination is performed again but the user can decide whether they want to keep it after changing the determination criterion (such as contract start date). This prevents the unnecessary deletion and reassignment of a valid third-party program. Internal processes have also been optimized to improve system performance.
The performance-optimized determination of third-party programs is available once you have activated the business function.
You use the multiple-asset contract for leasing customers who want to lease a large number of the same type of non-configurable objects in one business transaction (such as forklifts or company cars of a particular make). The new transaction types FSM1
, Multiple-Asset Contract
and FSO2
, Object Container
are available for this purpose.
A multiple-asset contract contains at least one financing package; you can create more than one financing package. The financing package consists of one reference and financing product, one or more service products (optional), financing options (optional), and the object list. The object list contains the object items.
You can add the individual information for the object items manually or upload this information from an external file using a report. The system creates FS contracts for the object items. You can specify in Customizing the number of object items to be contained in an FS contract. The same conditions (such as term, classification, and third-party program) apply to all the object items in a financing package.
Performance-optimized processing of the multiple-asset contract
When you process a multiple-asset contract, the object items are grouped in the background in processing packages. The packages are then processed in parallel on multiple servers. Processing is optimized in this way. You define the size of a package in Customizing. The package size depends on various factors, such as the number of financing and service items, financing options, as well as pricing. Therefore, the package size must be configured according to the customer-specific system and hardware capacity, the product constellation, and the timeout settings.
Example
Example of the performance-optimized processing of the multiple-asset contract
If a multiple-asset contract contains 300 object items, the package size has been set to 50, and one object has been defined for each FS contract, the system creates 300 FS contracts, each containing one object item. Each processing package contains 50 FS contracts and these are processed in parallel.
For more information, see Multiple-Asset Contract.
The following scenarios are supported:
Billing of subsidy payments to third parties (such as dealers). These are debit payments (on the debit side).
Billing of participation payments to third parties (such as dealers or sales agents). These are credit payments (on the credit side).
Forwarding of payments to third parties for which the lessee is billed periodically, such as to the party who actually performed a service. These are credit payments (on the credit side).
Note
Before you can bill payments from third-party business relationships, you must activate payment schedule billing for the item category used. You must also activate the business function Performance and Large Contracts
(CRM_PERFORMANCE
).
The structure of the service item has been enhanced to include the financial-mathematics elements of payment schedule, payment structure, and cash flow, and the financing item has been adjusted accordingly. You can use an action to trigger the calculation of the payment schedule at service item level. You can also calculate broken periods for the service product and therefore create uniform contract dates and durations.