Kontakt

Ansicht
Dokumentation

LOYV_ENGINE_PARAMS - Define Loyalty Engine Parameters

LOYV_ENGINE_PARAMS - Define Loyalty Engine Parameters

Fill RESBD Structure from EBP Component Structure   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you make settings for loyalty engine parameters and log levels for corresponding log points. The parameters change the engine response during member activity processing.

The log level value for a log point, in combination with the engine parameter OPTION_LOG_LEVEL, determines how detailed your log is after member activity processing.

The log point determines which detail is logged during member activity processing.

There is a single log for each processed member activity.

An engine parameter can determine settings such as:

  • How to locate the server group
  • How many activity records are read at one time
  • How many records can be processed by a single work process
  • Which log level applies for the processing log in a member activity

A log level can be a value such as:

  • Warning
  • Error

A log point can be an activity detail such as:

  • Processing end time for activity
  • Whether all criteria match the applicable rules
  • Whether all reward rules are being evaluated
  • All reward rule attributes

We recommend that you only change the listed parameters. Changing other parameters changes the default implementation and coding.

Enter the following values for the engine parameters:

  • BATCH_CURSOR_SIZE
Enter any positive integer value >=1, indicating a count of records.
This parameter only affects batch mode processing. It determines the number of records that are read from the activity table during a processing cycle. A database cursor controls this sequencing of records.
  • BATCH_RECORDS_PER_WP
Enter any integer value >= 0, indicating number of dialog work processes.
This parameter only affects batch mode processing. It determines the number of dialog work process available for parallel processing.
When the value is 0, all available work processes are used. Otherwise, a fixed number of work processes are used, as specified by the parameter value.
  • CACHE_INITIAL_LOAD_RANGE
Enter an integer value >=0, specifying number of days.
This parameter is used during initial loading of the loyalty engine cache to restrict the number of loaded reward rule groups and reward rules. Only reward rule groups and reward rules with a start date greater than or equal to are loaded into the cache.
  • COMBINE_POINT_ ATTRIB and COMBINE_POINT_TYPE_ATTRIB
Enter any string.
These parameter values are used in combinability to determine which of the eligible reward rules in a reward rule group can be executed. All eligible reward rule actions are searched to check the attributes specified in Customizing. The combinability logic is applied based on the availability of these attributes in the actions.
  • OPTION_ACTION_EXECUTION_ON
  • X = Action execution is on

  • Empty = Action execution is off

This parameter determines whether actions are to be executed. It can be turned off for example during debugging and performance evaluation.
  • OPTION_ADJUST_ACT_DT_CHECK
Enter an integer value >=0, specifying number of seconds

This parameter determines how many seconds beyond current server time an activity can be processed. The loyalty engine sets any activity in future to error status E_ACT_DATE and does not process it. This parameter eliminates server time synchronization problems.
Example: An activity is created on a system that is 1minute ahead of current time. You have to set the parameter value to >=60 to ensure that activities are processed even if they have a future timestamp.
  • OPTION_BATCH_PSH_TMP_PROC_ON
  • X = Partnership transaction processing during batch processing is switched on (default)

  • Empty= Partnership transaction processing during batch processing is switched off

During batch processing, this parameter switches the temporary partnership transaction table processing on or off. When the parameter is switched off, you have to schedule the report RLOY_ENGINE_PPA_PROCESS, to process the temporary partnership transaction table.
Note: You need to switch on the parameter OPTION_PPA_PROCESSING_ON for this parameter to take effect.

  • OPTION_BULK_PROCESSING_ON
  • X = Bulk processing is on

  • Empty = Bulk processing is off

This parameter determines whether bulk processing is on or off for online and batch modes of loyalty engine processing. If the parameter is turned off, records are always processed serially without any grouping.
  • OPTION_CACHE_LOAD_INTERVAL
Enter an integer value, specifying a number of hours.

This parameter determines the number of hours after which a cache update has to be triggered by the loyalty engine.
  • OPTION_CASCADE_FAILURE_ON
  • X = Cascade failure is on

  • Empty = Cascade failure is off

This parameter determines whether failure of a member activity triggers failure on subsequent member activities of the same point account set.
  • OPTION_LOG_LEVEL
Enter an integer value from 1 to 5.
  • OPTION_LOG_LEVEL = 1: All log points with log levels of 1 to 5 are logged.

  • OPTION_LOG_LEVEL = 2: All log points with log level of 2 to 5 are logged.

For more information, see the log levels description in this Customizing activity.
  • OPTION_PPA_PROCESSING_ON
  • X = Partnership processing on (default)

  • Empty= Partnership processing off

This parameter switches partnership processing on or off. When the parameter is switched off, no partnership transactions are recorded.
  • OPTION_PROCESSING_LOGS_ON
  • X = Logging is on

  • Empty = Logging is off

This parameter determines whether logs are available after processing member activities. You can turn it off during debugging and performance evaluation.
  • OPTION_SCHED_ACT_EXECUTE
  • X = Immediate processing

  • Empty = Set activity status for batch processing

This parameter is used during timed execution of reward rules to determine whether activities are to be processed immediately or by using batch processing. If you set the activity status to batch processing, the activities are processed in the next batch processing cycle.
  • OPTION_UPDT_MSH_TRANS_DT
  • X = Engine updates the last activity date automatically

  • Empty = Manual creation of a reward rule that updates membership

This parameter switches the automatic update of the last activity date on or off and sets the processing date. If you select the automatic update, for each activity that is processed successfully, the loyalty engine sets the last activity date under membership automatically.
When the parameter is switched off, you use the action update membership in the reward rules to update the last transaction date.

  • OPTION_USE_XML_LOGS
  • X = Use XML logging

  • Empty = Use cluster table logging

This parameter is used to determine the type of logging to be used during activity processing.
  • OPTION_WAIT_FOR_PPA_SYNC
  • In batch processing, wait for partnership account sync between cursor reads.

  • X = True(default)

  • Empty= False

During batch processing, you use the value X to stop the processing of the next set of activities until the temporary partnership transaction table processing for the previous set of activities is completed. This ensures that any activity in the subsequent set with reference to partnerships that have crossed the available overdraft limit, will fail.
Note: You need to switch on the parameter OPTION_PPA_PROCESSING_ON for this parameter to take effect.

  • SERVER_GROUP_BATCH
Enter any string value, representing a server group.

This parameter only affects batch mode processing where it determines the servers on which the batch processing mode of the loyalty engine works.
RFC Server Groups Customizing
Use transaction SM59 to define server groups for batch and online processing.
These settings determine values such as:
  • The number of work processes that are free and available

  • System performance during loyalty engine processing

For more information, see SAP Help Portal under Components of SAP Communication Technology -> Classical SAP Technologies (ABAP) -> RFC -> RFC Programming in ABAP -> Maintaining Remote Destinations -> Maintaining Group Destinations.






BAL Application Log Documentation   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 13524 Date: 20240523 Time: 190825     sap01-206 ( 141 ms )