Change Processes

Use

You use this function to change existing lease contracts. Each change process has a different effect on the further processing of the lease, both in contract management and in accounting.

In SAP Customer Relationship Management (SAP CRM), change processes with similar functions are grouped in the leasing scenario and are copied to generic change processes. This reduces the number of business transactions and change processes in the CRM application without restricting the range of functions.



The TERM process uses a specific assignment rule to handle the ETER process.

For more information, see Overview of Mid-Lease Change Processes .

In the Lease Accounting Engine (LAE, SAP ERP), none of the change processes have been changed. A Business Add-In (BAdI) (enhancement spotCRM_FS_ACC_CHANGE_PROC) is used to assign the generic business transactions and change processes from SAP CRM to the processes in the Lease Accounting Engine. The rules used to assign the processes correctly are defined in the BAdI. When a change process is executed, the BAdI is called. In CRM, the BAdI writes the result to data segmentCHNGPROC_I, from where it is read by the middleware, and transferred to the ERP application.

You can use your own custom BAdI implementations to change the way in which the LAE processes are assigned.

Prerequisites

You have made all the required settings in Customizing for Customer Relationship Management under Financial Services → Leasing → Change Processes → Basic Settings for Change Processes → Make Settings for Change Processes .

The settings you make here control all the change processes.

To execute the change processes, you must have at least one active lease.

Features

Time-driven execution of change processes

You can start most of the change processes during the contract term. Depending on the contract situation, you can also execute the processes at the end of the contract term.

For more information, see Overview of Mid-Lease Change Processes and Overview of End-of-Lease Change Processes .

Manual and automatic execution of change processes

Change processes are not started automatically. You start them manually. However, you can also execute change processes using options. Options are predefined rights, defined together with the lessee, which the system either proposes or executes automatically at a specific exercise time.

You can use options to execute the following change processes:

Base lease extension (RESC)

Early buyout (BUYO)

Purchase of leased object (BUYO)

Continuation (CONT)

Renewal (RNEW)

Early termination with return (TERM)

Change processes with or without financing character

Depending on the change process, the options you can exercise either entail further financing or not.

Change processes with upgrades

For an overview of the change processes that you can execute during (product) upgrades, see Upgrade Processes .

Transaction history

The change processes are executed either in the same item or in a follow-on item/follow-up document. For more information about the change processes that are executed directly in the same item (inbound change), see Change Processes for the Same Item .

In these cases, the system automatically executes the certificate of acceptance and inception.

You have the following processing options (transaction history):

New contract item in initial contract

When you execute the change process, the system immediately creates a new contract item in a new contract.

New contract document

When you execute the change process, the system immediately creates a new contract.

Inbound change

The changes are made directly in the item or header, without a new item or contract being created.

Inbound change with optional quotation

New quotation document; new contract document

When you execute the change process, the system creates a new quotation document. Once the quotation has been created, you must manually create a certificate of acceptance and execute inception (action: Business Transaction Header Activation ).

New quotation document; new contract item in initial contract (item change processes only)

When you execute the change process, the system creates a quotation. Once the quotation has been created, you must manually create a certificate of acceptance and execute inception (action: Business Transaction Header Activation ). When the contract is accepted, a new contract item is created in the initial contract.

Optional quotation document; new contract item in initial contract (item change processes only)

When you execute the change process, the system gives you the option of creating a quotation. This option can be selected on the user interface for change processes. In the case of quotation creation, a new contract item is created in the initial contract when the contract is accepted; in other cases it is created immediately.

Optional quotation document; new contract document

When you execute the change process, the system gives you the option of creating a quotation. This option can be selected on the user interface for change processes. In the case of quotation creation, a new contract item is created in a new contract when the contract is accepted; in other cases it is created immediately.

For all change processes for which a follow-up quotation is to be created, you must manually generate a certificate of acceptance and execute inception (action: Business Transaction Header Activation ). The quotation becomes a contract document only when the contract has been accepted.

Change processes at header or item level

If change processes are executed at header level, the changes apply to the entire contract.

If change processes are executed at item level, the changes apply to the individual contract items.

Change processes for item groups

In a service-oriented scenario, it is important that the various dependent items can be displayed across change processes in the same original document. When groups are processed, services can be offered for financing and can be processed with the financing over the complete lease cycle in the overall view.

When change processes are executed for an item, you can specify that this item and its dependent items are processed together as a group in the Certificate of Acceptance , Inception , and - if applicable - Cancellation . Processing can be carried out with the same change process or a different change process, depending on what is defined in Customizing.

During processing, the system first determines the group to be processed and then verifies which rules are to be used to process the group. To do this, the system uses rules that have been defined in the Business Rule Framework (BRF).

You have performed the Customizing activities under Customer Relationship Management → Financial Services → Leasing → Change Processes → Basic Settings for Change Processes:

Transaction-Dependent Settings for Change Processes

Define Rules for Change Processes



You have a contract that contains one financing item and one service item, whereby the two items are dependent on each other through rules. At the end of the contract term, you give the customer a new financing and service quotation. In the change process to be executed, you want to be able to change only the financing item to meet the customer requirements:

Group determination is defined in such a way that both items of the old contract are found

Group determination is defined in such a way that only the single item is found

On the user interface, the change processes that have been executed for a contract are displayed in the Financing Details assignment block.

Activities

To execute a change process:

Open the required lease contract.

At header level in the contract, choose Change Processes .

Choose Change Processes Header or Change Processes Item . How the system proceeds depends on your Customizing settings and on which change process you selected.

Alternatively, you can schedule a change process as an action in the Show Actions assignment block.