SAP for Utilities Blogs
Discover insights and practical tips to optimize operations, reduce costs, and deliver reliable energy with SAP technology. Contribute your own blog post!
Showing results for 
Search instead for 
Did you mean: 
Former Member

Product actions, abbreviated to ‘actions ‘as a standard BRFplus term represent a utilities-specific BRFplus component usage that is assigned to the product header.

For more information about the definition and application of BRFplus usages see Product Modeling for Utilities SAP CRM 7.0 EHP3.

The product action can be used to trigger user-defined actions.

Typical actions in BRFplus include:

  • Call Procedure (execution of user-defined static methods and functions such as setting the status for a document according to specific conditions.)
  • Log Message (such as writing messages to the application log if defined triggers apply.)
  • Raise Workflow Event / Start Workflow (such as an authorization workflow for specific actions or discounts.)
  • Send E-Mail (such as sending an e-mail to an administrator for specific products that are no longer to be sold.)

A specific trigger for the product action is available that is predefined in the function. The trigger can be selected flexibly and can contain any coding. This means that entering a product that is defined for product actions triggers an action or the modification of relevant configuration attributes that are defined in the product action. A product action can also respond to customer or system-specific events. The flexibility of the triggering actions or values for a product action means that they can be used in a variety of different ways.

However, when the product action is executed for this component usage, typically no value is returned or the existing return value is not processed by the system.

You can usually create the product action using a decision table (available as of SP06).

In the decision table, you first choose the type of action to be created, enter the triggering parameters and define the action in detail.
It can be helpful to use the context parameters in the BRFplus editor here.

The following describes a specific product action in detail:

Use Data Entered as a Search Help During Identification

Example demos were made available with SP06 CRM 703 (see PFC Demo Scenarios).

One of these examples refers to an OData Service. In this example, a call center agent checks the data entered using the service by accessing the corresponding task in the inbox. Following this check, the user navigates to the identification where they can identify the business partner and premise or create them if they do not already exist.

The system transfers the data entered here to the corresponding search fields automatically. See slides 7 - 14 of the linked PFC Demo Scenarios document.

This is done using a product action that responds to the event ‘Request for Identification‘ and uses a method call to make entries in the fields in the identification area using the BRFplus rule defined. You find the event registration as a context parameter in the function.

This specific BRFplus rule can be generated manually or automatically and shows an example of how any methods or functions can be called from the BRFplus context.

To create your own mapping rule, proceed as follows:

1.  Log on using the role ‘UTIL_SALES‘.

2. Navigate in the PMU to the product (with the role PDO in this example), switch to the Edit mode and select the first row in the left hand section. The rules at product level appear on the right hand side.

     Choose New in the product actions area.

     On the next screen that appears select the target application (according to the component usage selected) and the

     entry highlighted in yellow here. Now choose ‘Create and Navigate to Object’.

3. The BRFplus rules editor appears. Enhance the context to include the attributes that are to be transferred in the method call. First choose the origin of the parameters.

4. The selection of attributes takes place in the next step, in this case using the first name of the business partner.

5. Assign the search criteria for the business partner under ‘Mapped Parameters‘.

6. You can see the event registration that is generated automatically.

You can select additional parameters in the same way here. Once all attributes required have been included in the contexts, you perform the following steps to assign the attributes to the fields in the identification area.

7. Display the details of the search criteria. Choose a context parameter for the relevant search criteria in the identification (business partner first name in the example).

8. Choose the corresponding object.

9. This completes mapping. The overview shows the search criteria that have been mapped for the identification.

10. Save and activate your BRFplus function for the product action.

11. Check the product action by executing the assigned PDO in the role UTIL_IC, make entries in the fields and navigate to the identification area or create a quotation from the Product Finder and Configurator.