Ansicht
Dokumentation

CRM_BRF_INIT - BAdI: Initialize BRF Actions

CRM_BRF_INIT - BAdI: Initialize BRF Actions

ROGBILLS - Synchronize billing plans   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in the Business Rules Framework (CRM-BTX-BF-BRF).

Every time a BRFevent is triggered, the corresponding rules are evaluated, and for every fulfilled rule a corresponding action is processed. If you do not use initialization actions, you must use additional rules to ensure that the results of an action that has been carried out (for example, writing a message to the log) are reversed if the rule is no longer fulfilled. This BAdI offers an exit for the purpose of executing initializations for an action that is to be carried out, or for rolling back the results of an action that is no longer to be carried out. The BAdI is called up in two cases:

  • After a BRF event is triggered for each rule to be evaluated (irrespective of whether the expression returns true or false).
  • Every time there are rules to be executed for a BRF event that is no longer relevant.

The interface provides the following information:

  • Filter value (FLT_VAL,,)
    The BAdI is filter-dependent. The filter value is issued when an implementation is created, and you assign it to the rule in Customizing under Configure Business Rule Framework.
  • Rule data (IS_RULE_DATA)
    The parameter is only filled if the BRF event is no longer relevant. This may be the case, for example, when the rule relevant for event determination is no longer fulfilled.
  • Event (IR_EVENT)
    The parameter is only filled if the event is still relevant.
  • Categorization of context data (IV_CONTEXT_STRUCTURE)
    An action can also write context data during execution (for example, when action "Message" is carried out, the message class, message number, and so on). Data is provided to the initialization action in the form of a table. The line type of the table is contained in this parameter.
  • Context data (IT_CONTEXT_TAB)
    The data that an action updated when it was processed. An action can potentially execute several processing steps (for example, several messages). Therefore, the transfer takes place in table form.
  • Action executed (IV_ACTION_REQUIRED)
    The parameter indicates whether the corresponding action is still being executed. If the BRF event is no longer relevant, the parameter is always FALSE. If, on the other hand, it is still relevant, the value is TRUE if the corresponding action is then executed, or FALSE if the expression of the rule is no longer fulfilled and the action is therefore not processed.

You use the BRF, and the initialization action must be assigned to the BRF rule.

In the standard configuration, an active BAdI implementation for resetting messages is delivered (filter value: INIT_MESSAGE). This implementation can be used as an initialization action for actions of type "CRM: Simple Message Output".

Minimum quantity check: A BRF rule checks that the quantity of an item has to be >= 10. If the quantity is smaller, an error message is written to the log. If the quantity is then changed to a value that is >= 10, the message should automatically be removed. To achieve this, you assign the initialization action (INIT_MESSAGE) to the rule.






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

Length: 3713 Date: 20240606 Time: 112825     sap01-206 ( 79 ms )