Kontakt

Ansicht
Dokumentation

CRM_LEASE_CHNG_BRF - Define Rules for Change Processes

CRM_LEASE_CHNG_BRF - Define Rules for Change Processes

General Material Data   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

Use

In this IMG activity, you can define rules that dictate how change processes will run at item level. The fields you can influence are:

  • Change process
  • Effective date
  • Term
  • Installment calculation procedure

When you define these rules, you can also define cross-item checks and/or definitions.

The rules define the following types of restrictions and settings:

  • Value range definition of included/excluded single values or intervals.
  • When you define included single values, you can set one of the values as the default. This value is set automatically when the change process is executed, as well as in the user interface.
  • Option to set one value as a (unique) required entry. In this case, only one specific entry is allowed.
  • When you set single values and upper/lower limits, you can either enter values directly or use expressions to retrieve data.

Rules are used to find these restrictions and settings themselves, which means you can differentiate them dependent on the specific situation.

Requirements

If you support a cross-item scenario such as Full-Service Leasing, you should first check whether one of the provided search strategies (see Define and Assign Search Strategies) fits your scenario. In particular the item categories have to be defined sensibly here.

Two rules are defined and provided:

  1. If the change process at financing item level is Termination (TERM) (IF part), then:
    1. The change process at service item level must also be Termination (TERM) (unique) (THEN part)
    2. The service item must be terminated on the same date as the financing item (THEN part)
  2. (For bundle scenarios): If the change process at bundle item level is Termination (TERM), then:
    1. The change process at financing item level must also be Termination (TERM) (THEN part)

Activities

For an optimized setup, perform the following steps:

  • In the implementation project, define who is supposed to make changes to the rules (and in which intervals) and which data will be used to define the rules.
  • In the implementation project, define a tag expression for all the relevant data in event 0EVENT1 in application class CRM_CHANGE_PROCESS. You can use expression 0TAG001 as an example. If data that you need to model the tag expressions is missing in the hierarchy structure, use the following steps to add it to the hierarchy structure:

If this is not possible, you can define your own stack class and make it available through the Customizing for the hierarchy structure.
Make sure that you model not only the input values of the rule (or change process at bundle level), but also the output values (or change process at financing item level that you want to restrict) as expressions.
  • Once all the rule-relevant data is available as instructions, you should define various value constraints in the form of actions (implementing class: 0CRMFS001; see above). To do so, you first have to specify an expression that contains the field you want to restrict. You can then use the value range restrictions to define single values and/or intervals.
  • You define the rule in the last step. To do so, define a condition part as an expression (IF part) and assign it a value range restriction in the form of the action (THEN part).

Example

See delivery Customizing






PERFORM Short Reference   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 4665 Date: 20240523 Time: 165816     sap01-206 ( 70 ms )