Ansicht
Dokumentation

CRM_IC_053 - Define Repository

rdisp/max_wprun_time - Maximum work process run time   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

In this Customizing activity, you configure the repository. The repository defines objects that are used for processing rule policies, and, in some cases, for integrating with the rule engine for background processing. You must complete this Customizing step before you create rule policies.

If you want to define new attributes, you must have created fact-gathering services in Define Services.

If you want to create new actions, you must have created services in Define Services.

All settings in this activity are delivered with standard Customizing entries. Areas you may want to define further are:

• Authorization Groups

• Attributes

• Actions

• Input Support for Conditions

1. Edit standard contexts

During initial Customizing, we recommend that you use the standard implementation as your basis and then adapt it in the corresponding client.

1. Define context properties

No standard entries are available. Context properties allow you to define variables (based upon the context defined in the last step) that can be used in the rule engine. This gives you more flexibility when working with rule policies without having to modify the rule engine directly. It is mainly used for actions or fact-gathering services.

1. Define authorization groups

You define authorization groups that are used in determining policy authorization levels in the rule policies. You assign the authorization group to both a policy and a role. The role determines the specific authorization level, for example, delete or change, for each authorization group. Any users assigned to the role then inherit the authorizations. If you do not assign authorization groups to policies, all users can see all policies.

1. Define attributes

You can create and define attributes that are used in the rule policies to help define conditions in rules and in the fact base. Generally, you only select or deselect the Show Attributes indicator. However, if you want to create new attributes, you must create a Fact-Gathering Service. The services must follow specific conventions that determine the rule engine used for a specific context.
For each new attribute (and for each parameter for the action), you may need to define an input support class with different characteristics if one of the following conditions applies:

• When you use dropdown list boxes, a method is needed to determine the value to be displayed

• When you switch between internal and external display, for example, dates are displayed internally as 20171224, but may appear as 12/24/2017 in the external view.

• You use an ABAP value help

• You want to check input values

• You want to display a description field next to a value field.

If you create a new attribute, you may need to limit the permitted operators. You can do this by defining an attribute extension class which is then assigned to the attribute.

1. Define actions

You define the actions that can be selected when creating rule policies and assign them to a class which provides the technical details about what the action does when triggered. Generally, only the Show Action indicator is either selected or deselected, based on your requirements. It is selected by default. This displays the action when rule policies are created. If you create a new action, you need to create an Action Handling service. This service must follow specific conventions that depend on which rule engine is used for the context.

1. Define action parameters

You define and maintain parameters for each action you defined in the previous step, you determine the type of possible entry help for each action parameter value, and you determine the sequence in which the parameters are shown in the rule preview.

1. Define input support for conditions

Input support determines the behavior for the attribute Value field in the Conditions page area when you create rule policies. Based on the operator/attribute combination, you can configure the type of value field and the type of value help available.

There are three types of combinations you can configure. When the user selects an attribute and an operator in the condition, they are evaluated. The system starts at the first combination and if it is not met, it continues to the next one until one is met:

• An attribute and operator of the condition

• An initial attribute and operator of the condition

• An attribute of the condition and an initial operator

Unless there are entries that match the three combinations above, the Valuefield is input only, without any value help.

If you want to assign a new operator, you must create the operator first in the last folder of this activity.

1. Assign operators to context

You select which operators are valid for the context you are using. We recommend that you use the default Customizing.

1. Define actions and action parameters for the rule policy call hierarchy.

This makes it possible to graphically display rule policy relationships for a selected action and action parameter in a specific context. A common use case would be to set the APPLY_POLICYaction and the Invoke Policyparameter to show the relationships between rule policies that call other rule policies. However, other actions and action parameters can also be defined.

1. Define operators

The rule engine only recognizes the default operators. We recommend that you use the default Customizing and do not change the standard settings.

1. Regenerate rules

If you make changes to this activity after you have defined policies and rules, you must use the transaction Regenerate Rules.

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 7474 Date: 20240523 Time: 155022     sap01-206 ( 134 ms )