Show TOC

 Initializing Actions

Use

Initializing actions enable you to reset the results of actionsautomatically when they are no longer relevant. Every time a BRF event is triggered, the related rules are evaluated, and the corresponding action is triggered for every rule that is fulfilled. If you do not use initializing actions, you have to manually ensure that the results of an executed action are reset as soon as the BRF event is no longer relevant.

Example Example

An event causes an error message to be written to the application log of a document via an action. Therefore, the document contains errors. To reverse the result of this action, you have to define a counter rule for each rule. In order to avoid this, you can assign an initializing action to a rule when you are defining it which automatically removes the results of the action as soon as the event is no longer relevant.

End of the example.

Prerequisites

  • You have implemented the initializing action with a Business Add-In. To do so, choose the application you use in Customizing for Customer Relationship Management and then go to Start of the navigation path Business Rule Framework Next navigation step Business Add-Ins (BAdIs) Next navigation step BAdI: Initializing Actions End of the navigation path .

  • You have assigned the initializing action to a rule. To do so, choose Start of the navigation path Business Rule Framework Next navigation step Configure Business Rule Framework End of the navigation path in Customizing.

Features

  • Initializing actions can be triggered during the evaluation of every rule in order to reset values if required. The initializing action is triggered independently of the event. Initializing actions can also always be triggered when a BRF event is no longer relevant.

  • In the standard system, SAP delivers the following initializing actions:

    • Remove messages from the application log

    • Change status

      Note Note

      It is not possible to use initializing actions together with subactions. If an action has two subactions (for example write message to application log and set status), you cannot assign an initializing action for each subaction, rather only one initializing action for the higher-level action.

      End of the note.