Ansicht
Dokumentation
CRMV_FDT_CUST - Define Rule Policy Types
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up PERFORM Short ReferenceThis documentation is copyright by SAP AG.
In this Customizing activity, you can create or change rule policy types, to structure your rules for applications such as loyalty management and territory management.
You also use this Customizing activity to make SAP Real-Time Offer Management settings.
You have to define the following for your rules:
- Rule policy type
- Condition groups
- Condition attributes
- Subattributes
- Return values
- Actions
- Action parameter
Loyalty Management
Rules are the basis of reward rules that are used for the calculation of the customer rewards in a loyalty program. During the processing of a member activity, all the rules that are satisfied trigger actions.
A rule policy can have multiple rule sets, which consist of rules and one valid rule version.
Territory Management
In territory management, a rule policy defines the scope of a territory.
SAP Real-Time Offer Management
You set up rules for the definition of your real-time offer.
Complaints and Returns
In complaints and returns, rule policies determine the action to take when a Web shop customer submits a complaint or return. Either the system makes the decision in the backend by means of rules established in the rule builder's Business Rule Framework plus (BRFplus) engine, or a user makes the decision in the backend manually. If the decision is made in the backend by the system, the result and next steps are shown online immediately to the Web shop customer.
To define the conditions, actions and operators for the rules of an application, you create or change the following:
- Condition groups for a rule policy type
- Condition attributes for a condition group and rule policy type
- Subattributes for your condition attributes.
- Note the following for subattributes:
- You can mark a condition attribute as a subattribute in this Customizing activity.
- You can use subattributes as a table element in a rule, but not as a condition attribute in a rule.
- Before you create a condition attribute with the data type table (table attribute), you have to create all your subattributes that you want to use as a table element.
- Once you mark a condition attribute as a subattribute, you cannot change it back to a condition attribute.
- You can only add subattributes to a table attribute from the same condition group.
- Return values for a rule policy type
- Actions for a rule policy type
- Action parameters for an action and a rule policy type
You have to transport the rules that are created in the rule builder WebClient UI by using the transaction Transport of Rule Policy (CRM_FDT_TRANS) after the user has released the rules for transport in the WebClient UI. Note that only rules that have been released for transport in the WebClient UI are available for transport in this transaction. For more information, see transaction documentation.
Example: You create a rule in system A (test system) and you want to transport the rule to system B (production system). You have to go to CRM_FDT_TRANS (in the source system), add the rule created and released for transport in the WebClient UI to a transport request, and release the transport to system B.
You have to specify your rule attributes on a Customizing client and copy them to other clients by using the transaction SCC1 in the target system.
You do this in the following cases:
- After installation or upgrade
- After changing rule attributes
Loyalty Management
You make the Customizing settings for reward rules under CRM -> Marketing -> Loyalty Management - Design -> Basic Settings -> Define Loyalty Types.
We deliver the following Customizing settings in standard:
- Rule Policy Type: LOYMGMT
- Condition Group:
| Condition Group ID | Description | BOL Object Name |
|---|---|---|
| ACTGEN | Member Activity (Generic) | MSH |
| ACTSP | Member Activity (Specific) | MSH |
| MSH | Membership | MSH |
| MSHDYN | Membership (Dynamic) | MSH |
| MSTGR1 | Basic Tier | MSH |
| MSTGR2 | Lifetime Tier | MSH |
| MTQPT1 | Basic Tier Miles | MSH |
| MTQPT2 | Basic Tier Points | MSH |
| MTQPT3 | Lifetime Tier Miles | MSH |
| MTQPT4 | Lifetime Tier Points | MSH |
| PTACT1 | Miles | MSH |
| PTACT2 | Points | MSH |
- The condition group Member Activity (Generic)is a generic Customizing delivery and the condition group Member Activity (Specific) is standard Customizing for airlines.
- The condition group Membershipis generic for loyalty program memberships and the condition group Membership (Dynamic) is for the use of dynamic attributes. See Define Dynamic Attibutes.
- The condition group Basic Tier is a generic tier in a loyalty program that can expire and the condition group Lifetime Tier never expires even if no member activity takes place for a certain time (a tier for life).
- The condition group Basic Tier Miles is for use of basic tiers with miles and the condition group Basic Tier Pointsis for use of basic tiers with points.
- The condition group Lifetime Tier Miles is for use with a lifetime tier with miles and the condition group Lifetime Tier Points is for use with a lifetime tier with points.
- The condition group Milesis for the use of miles in a loyalty program and the condition group Pointsis for the use of points in a loyalty program.
- Condition Attributes:
| Condition Group ID | Condition Attribute ID | Description |
|---|---|---|
| ACTGEN | ACTIVITY_DATE | Date Of Activity |
| ACTIVITY_TIME | Time of Activity | |
| CARD_GUID | Card GUID | |
| CATEGORY | Category | |
| GUID | Activity GUID | |
| MEMBERSHIP_GUID | Membership GUID | |
| MEMBER_GUID | Member GUID | |
| PARTNER_GUID | Partner | |
| PROCESS_TYPE | Type | |
| PROGRAM_GUID | Program GUID | |
| ACTSP | AIRLINE_ID | Airline |
| AMOUNT | Amount | |
| BASE_MILES | Base Miles | |
| BOOKING_CLASS | Booking Class | |
| BOOK_CLASS_MUL | Booking Class Multiplier | |
| CAMPAIGN_CODE | Campaign | |
| CURRENCY | Currency | |
| DEST_AIRPORT | Destination Airport | |
| FARE_BASIS | Fare Basis | |
| FARE_BASIS_MUL | Fare Basis Multiplier | |
| FLIGHT_CATEGORY | Flight Category | |
| FLIGHT_NUMBER | Flight Number | |
| ORIGIN_AIRPORT | Origin Airport | |
| POINTS | Loyalty Points | |
| POINT_QUAL | Loyalty Point Qualification Type | |
| POINT_TYPE | Point Type | |
| PRODUCT_GUID | Product | |
| PRODUCT_QUANTITY | Quantity | |
| PROD_CAT_GUID | Product Category | |
| RETAIL_STORE_ID | Retail Store ID | |
| TICKETING_DATE | Ticketing date | |
| TIER | Tier | |
| TIER_GROUP | Tier Group | |
| MSH | MEMBER_COUNTRY/REGION | Membership Country/Region |
| MEMS_TYPE | Membership Type | |
| MSHDYN | COUNTER | Counter |
| NO_OF_TIMES | Number Of Times | |
| MSTGR1 | END_DATE | Basic Tier End Date |
| START_DATE | Basic Tier Start Date | |
| TIER_LEVEL | Basic Tier Level | |
| MSTGR2 | END_DATE | Lifetime Tier End Date |
| START_DATE | Lifetime Tier Start Date | |
| TIER_LEVEL | Lifetime Tier Level | |
| MTQPT1 | QUALIFYING_POINT | Basic Qualifying Miles |
| MTQPT2 | QUALIFYING_POINT | Basic Qualifying Points |
| MTQPT3 | QUALIFYING_POINT | Lifetime Qualifying Miles |
| MTQPT4 | QUALIFYING_POINT | Lifetime Qualifying Points |
| PTACT1 | BALANCE | Miles Balance |
| CONSUMED | Miles Consumed | |
| EARNED | Miles Earned | |
| EXPIRED | Miles Expired | |
| PTACT2 | BALANCE | Points Balance |
| CONSUMED | Points Consumed | |
| EARNED | Points Earned | |
| EXPIRED | Points Expired |
- Return Value: IS_APPLICABLEchecks whether rules are applicable or not applicable.
- Example: A loyalty program has a reward rule group and a reward rule:
- Reward rule group: Contains a set of applicability rules: Is applicable or not is the return value
- Reward rule: If the reward rule group is applicable, then all the reward rules contained in the reward rule group are used for point evaluation.
- Actions:
| Action ID | Description | Method |
|---|---|---|
| ACCRUE | Earn Points | ACCRUE_POINTS |
| ADDBNF | Add Benefits | ADD_BENEFIT |
| CHTIER | Tier Transition | TIER_TRANSITION |
| CONBNF | Consume Benefits | CONSUME_BENEFIT |
| ERROR | Raise Error | |
| REDEEM | Redeem Points | REDEEM_POINTS |
| REMBNF | Remove Benefits | REMOVE_BENEFIT |
| RESET | Reset Attribute | RESET_ATTRIBUTE |
| RETURN | Return Points | RETURN_POINTS |
| UPDMSH | Update Membership | UPDATE_MEMBERSHIP |
| UPDT_1 | Update Attribute 1 | UPDATE_ATTRIBUTE |
| UPDT_2 | Update Attribute 2 | UPDATE_ATTRIBUTE |
| VOUGTE | Generate Voucher | GENERATE_VOUCHER |
| WARNIG | Raise Warning |
Note: The actions UPDT_1 and UPDT_2 are used to update the counters set up for the dynamic attributes.
- Action Parameters:
| Action ID | Action Parameters | Description |
|---|---|---|
| ACCRUE | ACTIVITY_GUID | Activity GUID |
| ACTUAL_POINTS | Actual Points | |
| CAMPAIGN_GUID | Campaign | |
| CARD_GUID | Card GUID | |
| EXPIRATION_PROC | Expiration Procedure | |
| MA_PROCESS_TYPE | Type | |
| MEMBERSHIP_GUID | Membership GUID | |
| MEMBER_GUID | Member GUID | |
| PARTNERSHIP_GUID | Partnership GUID | |
| PARTNER_GUID | Partner | |
| POINT_TYPE | Point Type | |
| PROGRAM_GUID | Program GUID | |
| QUAL_TYPE | Qualification Type | |
| REASON | Reason | |
| ADDBNF | ACTIVITY_GUID | Activity GUID |
| MEMBERSHIP_GUID | Membership GUID | |
| CHTIER | IV_MEMS_ID | Membership GUID |
| IV_EXPIRATION_PROC | Expiration Procedure | |
| IV_TIER_GROUP | Tier Group | |
| IV_TIER_LEVEL | Tier Level | |
| IV_VALIDITY_TYPE | Validity type of the tier | |
| CONBNF | ACTIVITY_GUID | Activity GUID |
| MEMBERSHIP_GUID | Membership GUID | |
| ERROR | ID | Message Class |
| MESSAGE_V1 | Message Variable 1 | |
| MESSAGE_V2 | Message Variable 2 | |
| MESSAGE_V3 | Message Variable 3 | |
| MESSAGE_V4 | Message Variable 4 | |
| NUMBER | Message Number | |
| REDEEM | ACTIVITY_GUID | Activity GUID |
| ACTUAL_POINTS | Actual Points | |
| CAMPAIGN_GUID | Campaign | |
| CARD_GUID | Card GUID | |
| MA_PROCESS_TYPE | Type | |
| MEMBERSHIP_GUID | Membership GUID | |
| MEMBER_GUID | Member GUID | |
| PARTNER_GUID | Partner | |
| POINT_TYPE | Point Type | |
| PROGRAM_GUID | Program GUID | |
| REASON | Reason | |
| REMBNF | ACTIVITY_GUID | Activity GUID |
| MEMBERSHIP_GUID | Membership GUID | |
| RESET | ATTRIBUTE | Attribute |
| CONTEXT | Context | |
| MEMBERSHIP_GUID | Membership GUID | |
| PROGRAM_GUID | Program GUID | |
| RETURN | ACTIVITY_GUID | Activity GUID |
| ACTUAL_POINTS | Actual Points | |
| CAMPAIGN_GUID | Campaign | |
| CARD_GUID | Card GUID | |
| MA_PROCESS_TYPE | Type | |
| MEMBERSHIP_GUID | Membership GUID | |
| MEMBER_GUID | Member GUID | |
| PARTNER_GUID | Partner | |
| POINT_TYPE | Point Type | |
| PROGRAM_GUID | Program GUID | |
| REASON | Reason | |
| UPDMSH | ATTRIBUTE | Attribute Name |
| DATE_VAL | Date Value | |
| MEMBERSHIP_GUID | Membership GUID | |
| NUMBER_VAL | Number Value | |
| STRING_VAL | String Value | |
| UPDT_1 | ATTRIBUTE | Attribute Name |
| CONTEXT | Context | |
| DATE_VAL | Date Value | |
| MEMBERSHIP_GUID | Membership GUID | |
| NUMBER_VAL | Number Value | |
| PROGRAM_GUID | Program GUID | |
| STRING_VAL | String Value | |
| UPDT_2 | ATTRIBUTE | Attribute Name |
| CONTEXT | Context | |
| DATE_VAL | Date Value | |
| MEMBERSHIP_GUID | Membership GUID | |
| NUMBER_VAL | Number Value | |
| PROGRAM_GUID | Program GUID | |
| STRING_VAL | String Value | |
| VOUGTE | CAMPAIGN_CODE | Campaign ID |
| IV_MEMB_GUID | Member GUID | |
| IV_MEMS_GUID | Membership GUID | |
| IV_PROGRAM_GUID | Program GUID | |
| WARNIG | ID | Message Class |
| MESSAGE_V1 | Message Variable 1 | |
| MESSAGE_V2 | Message Variable 2 | |
| MESSAGE_V3 | Message Variable 3 | |
| MESSAGE_V4 | Message Variable 4 | |
| NUMBER | Message Number |
Territory Management
For territory management, choose the rule policy type TM.
Make all other territory management settings under CRM -> Master Data -> Territory Management -> Territory Attributes -> Maintain Territory Attributes.
SAP Real-Time Offer Management
We deliver the following Customizing settings in standard:
- Rule Policy Type: RTOM
- Condition Group:
| Condition Group ID | Description |
|---|---|
| AGENT | Agent |
| CONTR | Contract |
| CUST | Customers |
| GMT | GMT |
| SECUST | SessionCustomer |
- Condition Attributes:
- You can do the following:
- When you define a new attribute in Customizing, you need to define the external data source for this attribute in the SAP Real-Time Offer Management Application Toolkit. For more information on the SAP Real-Time Offer Management Application Toolkit, see SAP Solution Manager.
- Note: The condition group GMT (current time) is always available and does not depend on an external source.
- You define computed attributes in the WebClient UI. They are not based on external data, but they are computations on regular attributes that were already mapped externally.
- Subattribute:
| Condition Group | Condition Attribute | Attribute ID | |
|---|---|---|---|
| CUST | CONTACTS | CONT_CONTACTNUMBER | |
| CONT_DATEFROM | |||
| CONT_DATETO | |||
| CONT_DEPARTMENT | |||
| CONT_DEPARTMENTNAME | |||
| CONT_FUNCTION | |||
| CONT_FUNCTIONNAME | |||
| CONT_VIP | |||
| EMPLOYEERESPONSIBLE | EMPLOYRES_DEFRELATION | ||
| EMPLOYRES_PARENTGUID | |||
| EMPLOYRES_PARTNER1 | |||
| EMPLOYRES_PARTNER2 | |||
| EMPLOYRES_RELATIONTYPE | |||
| EMPLOYRES_RELCAT | |||
| EMPLOYRES_VALFROMDATE | |||
| EMPLOYRES_VALUNTILDATE | |||
| RELATIONSHIPS | REL_DEFAULTRELATIONSHIP | ||
| REL_PARENTGUID | |||
| REL_PARTNER1 | |||
| REL_PARTNER2 | |||
| REL_RELATIONSHIPTYPE | |||
| REL_RELCAT | |||
| REL_VALFROMDATE | |||
| REL_VALUNTILDATE | |||
| ROLES | ROLES_DIFFTYPEVALUE | ||
| ROLES_PARTNERGUID | |||
| ROLES_PARTNERROLE | |||
| ROLES_PARTNERROLECAT | |||
| ROLES_ROLECATEGORYTITLE | |||
| ROLES_ROLETITLE | |||
| ROLES_VALIDFROM | |||
| ROLES_VALIDTO | |||
| TELCOORDER | TELCOORDER_BUNDLENAME | ||
| TELCOORDER_CURRENCY | |||
| TELCOORDER_DESCRIPTION | |||
| TELCOORDER_NETVALUE | |||
| TELCOORDER_ORDERQUANT | |||
| TELCOORDER_PARTOFBUNDLE | |||
| TELCOORDER_POSTINGDATE | |||
| TELCOORDER_PROCESSQUNIT | |||
| TELCOORDER_PRODDESC | |||
| TELCOORDER_PRODUCT | |||
| TELCOORDER_PRODUCTID | |||
| TELCOORDER_SELECTEDFLAG | |||
| TELCOORDER_TELCOORDERID | |||
| INTERACTIONHISTORY | INTHIST_CATEGORY | ||
| INTHIST_CATEGORYTEXT | |||
| INTHIST_CHANGEDAT | |||
| INTHIST_CONTACTPERSLIST | |||
| INTHIST_CONTACTPERSON | |||
| INTHIST_CONTSTATUSER | |||
| INTHIST_DESCRIPTION | |||
| INTHIST_IMPORTANCE | |||
| INTHIST_IMPORTANCETEXT | |||
| INTHIST_OBJECTKEY | |||
| INTHIST_PERSRESP | |||
| INTHIST_PERSRESPOLIST | |||
| INTHIST_PRIORITY | |||
| INTHIST_PRIORITYTEXT | |||
| INTHIST_PROCESSTYPE | |||
| INTHIST_PROCESSTYPETEXT | |||
| INTHIST_STATUSOPEN | |||
| INTHIST_VALIDFROM | |||
| INTHIST_VALIDTO | |||
| SALESORDERS | REL_VALUNTILDATE | ||
| SALESORDER_CURRENCY | |||
| SALESORDER_DESCRIPTION | |||
| SALESORDER_NETVALUE | |||
| SALESORDER_OBJECTID | |||
| SALESORDER_ORDERQUANT | |||
| SALESORDER_POSTINGDATE | |||
| SALESORDER_PROCESSQUNIT | |||
| SALESORDER_PROCESSTYPE | |||
| SALESORDER_PRODUCT | |||
| SALESORDER_PRODUCTID | |||
| TELCOORDER_TELCOORDERID |
- Return Value: RTOM_RETURN
For further Customizing settings, see Customer Relationship Management-> Marketing-> Marketing Planning and Campaign Management-> SAP Real-Time Offer Management.
Complaints and Returns
You make settings for complaints and returns in Customizing for Customer Relationship Management, under SAP Web Channel Experience Management -> E-Service -> Complaints and Returns:
- Define Settings for Complaints and Returns
- Define Time Frames for Returns and Complaints
We deliver the following Customizing settings in standard delivery:
- Rule policy type: COMPLAINTS
- Condition group:
| Condition Group ID | Description |
|---|---|
| WEC | WEC Complaints and Returns |
- Condition Attributes:
| Condition Attribution ID | Description | |
|---|---|---|
| BILL_DATE | Billing Date | |
| BP_STAR_RATING | Customer Star Rating | |
| CAT1 | Category 1 | |
| CAT2 | Category 2 | |
| CAT3 | Category 3 | |
| COUNTRY/REGION | Country/Region | |
| CURRENCY | Currency | |
| HEADER_GUID | Header GUID | |
| PREDECESSOR | Predecessor Transaction Type | |
| PRICE | Price | |
| PRIORITY | Priority | |
| PRODUCT | Product | |
| QUANTITY | Product Quantity | |
| QUANTITY_UNIT | Product QoM | |
| SHIP_DATE | Shipping Date | |
| TRANSACTION_TYPE | Complaint or Return Transaction Type | |
| WISHED_PROCESSING | Requested Action ID |
You can also prepare the context data that the system sends to the rule builder, in Customizing for Customer Relationship Management, under SAP Web Channel Experience Management -> E-Service -> Complaints and Returns -> Business Add-Ins (BAdIs) -> BAdI: Implement Custom Rule Builder Actions and Attributes.
Loyalty Management
Your organization uses a loyalty program in which a member can earn points by shopping online during the month of May.
You create the following settings in Customizing:
- A condition group: Member activity
- A condition attribute: Date of activity
- A return value: is applicable
- An action: Earn points
- An action parameter: Point type
Territory Management
For territory management examples, see CRM -> Master Data -> Territory Management.
BAL Application Log Documentation ROGBILLS - Synchronize billing plans
This documentation is copyright by SAP AG.
Length: 43662 Date: 20240523 Time: 161356 sap01-206 ( 271 ms )
