To use BRFplus rules, you must first make settings in Customizing, create a higher-level BRFplus application and then create the individual BRFplus functions. The procedure for doing so is described in detail below:
Step 1: Maintain the Customizing table CRMV_ISU_BRF_APP
The meaning of the columns in the table is described below:
Column | Description | Possible Entries |
---|---|---|
BRFplus application name | BRFplus application name | The BRFplus application represents the container in which BRFplus functions are defined and stored. You can choose any name here. |
Application description | Description used for unique identification | You can choose any description here. |
Where-Used | The application usage controls the provision of predefined data elements and structures to simplify the definition of BRF functions. |
|
Usage description | Description of the application usage | Is defined automatically |
Storage | This field controls technical storage of data and the options of transporting it to other systems. | You can store the generated applications locally only or include them in a transport request. The following values are available to you during generation:
|
Locked | The BRFplus application generated can be selected but can no longer be modified. This prevents new functions being created. | Checkbox: |
Generation | Generation of the BRFplus application automatically provides a predefined supply of data objects that are tailored to utilities-specific requirements.
| Selecting a usage and then generating the BRFplus application automatically provides the structures that are relevant for the utilities industry. |
Workbench | Can be used to access the BRFplus workbench directly where the selected application is already defined and positioned automatically. | Additional direct access to the BRFplus workbench |
Use | Where-used list for products and attributes in which this BRFplus application is used. | List that contains all usages of the BRFplus application. |
Step 2: Generate Application
SAP CRM for Utilities distinguishes BRFplus functions according to various usages, such as functions for configuration values input help or functions that are used to determine package components. BRFplus functions are always assigned to a BRFplus application. The application usage is used for structuring purposes.
IWhen generating BRFplus applications, the following application usages are available from the view CRMV_ISU_BRF_APP:
General administrative features of BRFplus applications for SAP CRM for Utilities:
The BRFplus applications generated are assigned the following administrative features for all usages described above:
Properties tab page:
Development package | Blank |
Application Component | Blank |
Software Component | According to the storage entry (not modifiable) |
Application Exit Class | CL_CRM_ISU_BRF_APPL_CHECK |
Default Settings tab page:
Application Log | Blank |
Application Log Object | Blank |
Application Log Sub Object | Blank |
Default Enforcement | No constraints |
Allowed Message Types |
|
Save Log Data | Blank |
Hide External Identification | Blank |
Language Settings | Blank |
Text Dependency Type | Independent of language and version |
Document Dependency Type | Independent of language and version |
Versioning | Blank |
Versioning Mode | Versioning off |
Tab page: Contained Objects
Miscellaneous tab page: | Blank |
Restart Rulesets Enabled | Blank |
Generate Functions
A BRF function must first be generated using product modeling before it can be used in utilities products. It is then transferred to the selected application and provided with the attributes required.
Step 3: Access product modeling in the role UTIL_SALES and generate BRFplus functions for the respective purpose in the application generated