Ansicht
Dokumentation

CRMC_LOYV_LPE_CUST - Rule Object Mapping

ABAP Short Reference   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

In this Customizing activity, you can do the following:

• Map tier groups to condition groups

• Map tier qualifying point types to condition groups

• Map point types to condition groups

Condition groups identify the grouping of condition attributes and are used in applications during rule execution for filling context and action execution. For example, if a rule has the condition group MSH (membership), the system calls the membership data and fills the rule context for rule evaluation.

For each membership, there can be multiple objects of the same type (such as tier groups, tiers and point types). The condition group mapping ensures that each object type is mapped correctly to a specific instance of the object, to return the correct value during processing.

When the loyalty engine processes a member activity and a point account balance for a particular point type is needed during rule evaluation, the condition group mapping enables the determination of the point balance from the correct point type.

• You have defined your condition groups and you have made settings in Customizing for Customer Relationship Management under CRM Cross-Application Components -> Rule Builder.

• You have made settings in Customizing for Customer Relationship Management under Marketing -> Loyalty Management -> Loyalty Programs.

A condition group has a group ID, a BOL (Business Object Layer) object name, and component name. For more information on the component name, see Customizing under Customer Relationship Management->CRM Cross-Application Components -> Generic Interaction Layer/Object Layer -> Basic Settings.

• If the BOL object is provided, the allowed attributes specific to that object are shown in an input help for the creation of conditions.

• If the BOL object is not provided, attributes need to be defined without an input help.

BOL object names can be overwritten by an application, by redefining the application handler method GET_OBJECTS.

Example in loyalty management:

You have set up a loyalty program with the following attributes:

Tier Group	Tier	Tier Qualifying Point Type

BASIC	BASIC	MILES
	SPECIAL
SILVER	MILES
	SPECIAL
MM_MILER	1_MM	MILES
	SPECIAL
2_MM	MILES
	SPECIAL

• The tier qualifying point type is not defined, but each tier inherits all available point types.

• The used point types are: MILES and SPECIAL.

• The rule builder Customizing remains the same.

In the condition group mapping for point types, the following mapping applies:

Point Type	Condition Group
MILES	PTACT1
POINTS	PTACT1

• You create a reward rule version as follows:

If Basic Tier Miles.Balance > 5000, Then Change Tier to Silver.

• In the loyalty engine this means:

If PTACT1.BALANCE > 5000 Then ChangeTier (Silver).

PTACT1.BALANCE = Condition Group.Condition Attribute.

• When the loyalty engine executes this rule, it has to substitute the value of Basic Tier Miles.Balance. In this case, the mapping between the condition group and point type is used to determine the correct point type from which value has to be selected in the above example MILES.BALANCE.

POINTS

• A loyalty program membership can be active in two tier groups: basic and million miler.

• In the rule builder, End Date is used as a rule attribute for a condition group of type Tier Group (BOL Object Name: MEMS_TIER).

• During activity processing, the loyalty engine needs to determine for which tier group the end date has to be evaluated. Condition group mapping enables the loyalty engine to achieve this.

• In this Customizing activity, you map each of the tier groups to a condition group, to enable the loyalty engine to update points in the correct tier group.

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

Length: 6504 Date: 20240523 Time: 160213     sap01-206 ( 83 ms )