SAP Community - NW ABAP Business Rule Framework (BRFplus)

Purchase order output management via BRF+ in S4

2021-06-28T18:31:34+02:00

Introduction :

In this article, I will explain the complete set up required for output management to work for Purchase order in SAP S/4HANA using BRF+.

1. Definition of BRF+

BRF+ is an application programming interface (API) and user interface for defining and processing business rule. It allows us to model rules in an intuitive way and to reuse these rules in different applications.

BRF plus is also used in output management to

Issue business documents in response to certain business events

External communication such as printouts, faxes, and e-mails with a print preview option

Alerts

Workflow

Its main characteristics are:

It offers a unified solution for all output-related tasks across the product.

It can be natively integrated into SAP Fiori apps (and SAPGUI apps).

It provides a new option for form templates (separation of static layout & content).

It supports ready-to-use output scenarios (pre-delivered configuration).

It supports standard extensibility for configuration & documents (form & email templates).

It provides central monitoring tools.

It runs in a cloud or an on-premise environment.

With SAP S/4 HANA a new Output Management approach is in place. The complete configuration differs from the configuration that is used when output management is based on NAST (condition technique). The configuration is based on BRF+. In SAP S/4 HANA, the target architecture is based on Adobe Document Server and Adobe Forms only. For the form determination rules (along with other output parameters) BRF+ functionality is used.

2.1 Key Benefits:

All output parameters can be automatically determined via a configuration activity based on BRFplus. The benefits are:

You can send multiple messages to multiple recipients using multiple channels at the same time.

You can configure anything without the need for ABAP exits.

You can base each determination step on application-specific fields that can be extended.

You can use predelivered content/determination rules to simply run output control out of the box.

Extensibility via CDS is supported.

2.2. Conversion NAST to BRF+

ECC to HANA for new Output there is no tools available at the moment

When converting to HANA from ECC only New PO’s will be coming in BFR+ if activated

In 1511 only Sales Invoice and PO and available

When it comes to 1709 12+ XML Forms and added

3. Prerequisites:

bgRFC configuration has been set up and prefixes for OM_QBGRFC_INBOUND_DEST (Define Inbound Dest.) are not modified (default value: OM_QUEUE)

Storage system and category has been maintained (KPRO)

BRFplus is active and usable

Adobe Document Services are available (only when using Adobe Forms)

4. Configuration Steps:

4.1. Switching from NAST to BRF+

In order to switch from NAST to BRF+, we need to activate in IMG

If It’s switched, we will not be able to use old way of NAST for output.

For Purchase orders, go to IMG → Integration with Other SAP Components → Business Network Integration → Integration with the Ariba Network Application-specific settings → Define Message Output Control → Method 2: Use SAP S/4HANA-Based Output Management → Activate or Deactivate SAP S/4HANA-Based Output Management

Mode needs to be new output management is active

4.2. Steps for configuring BRF+

Storage repository settings.

Import of BRF Plus application

Activation of object type.

Assign Output channel

Define determination of Form master template

Business Rules for output determination

4.2.1. Storage system and repository.

SAP Menu: SPRO > Cross-Application Components > Document Management > General Data > Settings for Storage Systems > Maintain Storage System

OR transaction Code: OAC0

Create new entry SOMU_DB with following data (part of standard SAP )

Storage type: SAP System Database
Storage subtype: Normal
Version: 0047
Content table: SFORM_A_STORAGE

Now Go to transaction OACT and assign the content repository thus created to category SOMU

4.2.2. Import of BRF Plus application:

Download relevant application file from SAP note – 2248229 – SAP S/4HANA output management – BRFplus files. Save these in your local system drive.

If this is not uploaded, you will not see the output type in OPD transaction

For Purchase order the file will be OPD_EF_PURCHASE_ORDER.xml:

This will require a workbench TR

4.2.3. Object type activation :

Below Node of SPRO will be used for all configuration of output type

IMG customization -> Cross-Application Components -> Output Control -> Manage Application Object Type Activation

In the path go to New entry and specify the object type as Purchase order and status as application active .

4.2.4. Create output type:

An output type represents a business document of a single application and defines the output parameters for that document.

In new entry enter object type as Purchase_order and assign it to output type Purchase_order .

4.2.5. Assign Output Channels:

In this step output channels selected wrt supported channels by output types. To prevent the end user from selecting output channels that are not applicable for a output type, only those output channels that can actually be used should be displayed in the applications.

4.2.6. Define Rules for Determination of Master Form Template:

Every time a document is output by the end user in an application, these rules identify the master form template that is to be used. The rules are based on several parameters: sender data, channel, and form template.

Note: Master form templates can contain placeholders for static data, for example, a logo and a footer. This data is displayed on each form page. In this activity, you can assign SAPscript texts and graphics to these placeholders.

4.2.7. Assign Form Templates:

With this activity, you can ensure that business applications use the correct predelivered and custom form templates.

( If this is not maintained correctly the output type will be in error Message no. APOC_OR_MESSAGES354)

4.2.8. Define business rules for output determination:

Business rules are created and maintained in BRFplus decision tables. These rules are used to determine the output parameters of specific business objects. Each rule comprises several determination steps connected to specific parameters. If you leave a column in the decision table blank, any value is deemed as satisfying the condition.

The customization for this is done in following customization menu path

IMG customization à Cross-Application Components à Output Control à Define business rules for output determination

Transaction Code : OPD

It opens in browser

After selecting Purchase order determination steps can be configured

i. Rules for Output type :

Document type and Dispatch time can be set as per requirement, It needs to be activated

ii. Rules for Receiver:

In drop down for show rules for select Purchase_order and in drop down for determination steps select receiver

Change the mode to Edit mode

Specify output type as Purchase order and role as “LF” for vendor.

iii. Rules for channel determination:

Specify output type as Purchase order, role as “LF” for vendor and channel as Email, Print and IDOC in three different rows, if required.

iv. Rules for Printer settings:

n drop down for show rules for select Purchase_order and in drop down for determination steps select Printer settings

Change the mode to Edit mode and create required entries

Specify output type as Purchase_order, role as “LF”, purchase organizations for which print must be generated and assign the default printer and no. of copies to be printed.

The out put device assigned should allow PDF

V. Rules for Email settings:

In this step you define Email address wrt output type, partner role

In drop down for show rules for select Purchase_order and in drop down for determination steps select E-mail settings

Change the mode to Edit mode and create required entries

Specify output type as Purchase_order, role as “LF”, and leave all other fields blank if the email address is to be taken from business partner master data.

(* Make sure that email address is maintained in BP master data and in customization of purchasing group)

vi. Rules for Form Template settings :

4.3. BgRFC settings:

· Create RFC destination

In SALE transaction, go to communication, create rfc connections :

(part of standard SAP)

Start transaction SBGRFCCONF

(part of standard SAP )

5.1. Limitations for printing via spool:

Please note that printing via spool is not available in release S4CORE 1.00 SP00. Upgrade to S4CORE 1.00 SP01 or higher.

Currently, a PDF is always created for any kind of form.
This has the following impact:

Previewing the document from the spool request is only possible when the device type is PDF1 or PDFUC.

Using another device type can lead to alignment issues for SAPscript and Smart Forms.

Printer tray handling is not supported.

Frontend output is currently not supported, as the output is processed via bgRFC

5.2. Configuring the PDF printer in SPAD transaction:

SAP printing process basically involves the spool work process transferring the output data to a host spool system (operating system spooler) which in turn prints the output on the printer attached to it. There are various combinations (printing method) for this depending on where the host spool system resides. SAPLPD is the transfer program which accepts print data and forwards it to the host spooler on Microsoft Windows platforms. Host spooler in the frontend system is used for downloading PDF files. Add a new output device using the SPAD transaction with device type set to PDF1. Other device types maybe required for PDF files containing characters from languages like chinese, arabic etc. Create an output device as shown in the screenshots below. In this case “PDF_printer” value is maintained in “Host printer” field of the access method tab since the FILE printer we just created was named so.. If this FILE printer has been set as the default printer in the frontend system, then value “_DEFAULT” can be maintained in this field irrespective of the name given to the printer.

The device type in out put device needs to be PDF1 or PDFUC to see print preview ( or get pdf)

After configuration, Create a PO and check in messages

Display document will show the print preview

For scheduled output , transaction ME9FF can be used

Conclusion :

After setting this output type , you can create a new purchase order and see the out put triggered in messages and also check print preview or take print out after configuring printer.

Reference SAP Notes:

2294198 - SAP S/4HANA output control - customized forms

2292539 - SAP S/4HANA output control – configuration

2228611 -Output Management in SAP S/4HANA

2292571 - SAP S/4HANA output control - technical setup

2248229 - SAP S/4HANA output management - BRFplus files

For customizing output types below given blog can be referred:

https://blogs.sap.com/2019/03/17/s4hana-output-management-part-ii/

BRF+ for Business Users

2021-09-20T15:47:38+02:00

What is BRF+

BRF+ stands for Business Rules Framework. It is a standard tool from SAP with the intention of separating the business rules from the coding. All the config tables like TVARVC etc potentially fit into this.
It not only helps developers but also business users. It speeds up the development process by providing inbuilt features like file upload, change management etc without writing a single line of code. Adding to that business users avail the flexibility of maintaining business rules in different formats, which best suits their requirement.

BRF+ vs Config tables

Historically we have tried to fit all the business rules into tables. By using BRF+ we can maintain config not only in a table format, known as Decision Table in BRF+, but also in other formats Boolean expression, Decision Table, Decision Tree, Case statement etc.

Advantages of BRF+

Versioning

BRF+ provides inbuild versioning capability for almost all of the object types from Application to Expression. Versioning comes with capabilities like comparison, activating a previous version etc.

Multiple Rules in a Rule Set

Each ruleset can be assigned with multiple rules and can be processed in a sequence.
Each rule in a rule set can process a different type of expression.
Each rule can be activated, processed based on a condition.
Each rule can be set to be active only for a particular date range.

Check Rule below.

Upload and download features on Decision Tables

Provides inbuilt excel upload and download functionality for Decision Table expression.

Simulation

Every rule set can be tested via assigned Function, before activation, to make sure the new config is behaving as expected.

Access BRF+ workbench

Use TCODEs BRF+ or BRFPLUS to access BRF+ workbench. Workbench is a webdynpro application which opens in a browser.

Terminology of BRF+

There are a few different types of objects in BRF+ but the important ones are

Application

Function

Rule Set

Rules

Expression

Application

Application groups related Functions and other objects. In the below 'Sample Application' we got one function 'Get Rate' and related data objects.

Function

Function is the top most element which defines the context of our business function. In other words the context is the input and output parameters. This is a developers job and we move this change via transport. The context involves Date, Site, Commodity etc.

Below function 'Get Rate' takes 2 input parameters Customer, Quantity and calculates the Rate.

Rule Set

Defines the set of rules that are assigned to a function. One function can contain one or more rule sets. If a function contains more than one rule set, we can define priority to define the execution order of the rule sets. We can even enable or disable a rule set.

One rule set is assigned to the below example function.

Rule

Business rules where we define our rule logic. Any number of rules can be assigned to a rule set. Each rule can have an optional validity period.

In the below example, 2 rules, Rule 1 and Rule 2 are assigned to a rule set. One with limited validity period and other with unlimited validity period.

Expression

There are many different expressions in BRF+ like below. These are different ways we can define the business rules.

Boolean

Decision Table

Decision Tree

Case

DB lookup

Loop

Formula

In Rule 1, we are processing a formula expression if the customer is not 99991.

In Rule 2, we are processing a decision table to calculate the amount

SAP Central Finance – Replication Enhancement via BRF+

2021-10-03T22:35:46+02:00

Introduction:

In Central Finance S/4 HANA Replication, we always get additional business requirement, which is not achievable using standard configuration setups. This triggers the use of different enhancement options to implement business logic,in order to have successful replication. There are different ways of custom enhancement in Central Finance:

Using MDG Mapping – By Creating custom mapping entity, if there is simple one- or two-level mapping requirement

Using BRF+ in combination with Replication BADI

Using Custom Tables in combination with Replication BADI

This blog focuses on how to use BRF+(Business Rule Framework) in replication of documents in Central Finance.

Approach:

Example:

In this blog, usage of BRF+ will be explained based on below use case:

Company Code	Account Type	Change the Value of Item Text(SGTXT)
1000	K(Vendor)	SET

Whenever company code is 1000 and line item account type is K(Vendor), then change the value of SGTXT(Item Text) to value SET. Please note that this is just an example of usage of BRF+ in Central Finance Replication. It can be used for complex business logic as well.

Step 1: Create BRF+ Application using transaction Code BRF+

Step 2: Create Decision Table based on Business Logic

Step 3: Define the Ruleset using Decision Table

Step 4: Create Function and assign Ruleset

Step 5: Call this function in FI Replication BADI BADI_FINS_CFIN_AC_INTERFACE. In this case, method MAP_VALUES

Sample Code for changing line items data using BRF+ Function:

Step 6: Sample Document Posted in Source and Replicated in Central Finance after BRF+ implementation using BADI

Document posted in Source ECC System

Replicated document in Central Finance

Conclusion:

BRF+ can be implemented and linked to any replication processes (Finance, CO, AUFK, etc.)

These business logics can be implemented using custom tables as well. However, with custom tables and logics written in BADI, makes it more technical.

If BRF+ is implemented using all the relevant parameters of BADI, then complete business logic requirement like profit centre determination, clearing any field, document type re-direction, etc, can be met by only working in BRF+ with business and functional expertise. There will be no requirement of changing ABAP code with new addition of any source systems/company codes or with change of existing business logic.

I hope this blog post was helpful for you!

Aberrations:

CFIN: Central Finance

BRF+: Business Rule Framework

MDG: Master Data Governance

BADI: Business Addins

FI: Finance

CO: COBK Replication

Raise Workflow event from BRF plus

2022-01-11T11:20:16+01:00

Sometimes it is more efficient to link BRF plus and SAP business workflow to establish close integration and simplify the rules for triggering workflows available. It should be clear to explain and maintain for an experienced SAP user.

There are two options to call SAP business workflow from BRF plus:

starting workflow directly (WS*),

triggering a workflow event.

In comparison to starting workflow directly, a workflow event can trigger several workflows based on the Linkage maintained ( transaction SWETYPV - Type Linkages ).

In this blog article, you can get a quick have a look at How to raise a Workflow event from BRF Plus.

It is assumed that a workflow scenario is already created for the ABAP class's event. So the question is only how to call it from BRF plus.

In a test scenario, a test function WS_ATP_SIGNAL processes lines with available quantity for materials. As the input data, it receives a table to analyze the situation for availability for several materials using the set of predefined rules. The return parameter is Action as it is expected that during processing the function will run actions only.

In the assigned Rule set it is the Loop expression 'ATP_LINES' that processes each line of the input table and decides on the action. The action raises as an event for a workflow.

To link the Business workflow and BRF plus, create an expression with the type Raise Workflow Event (Action). In this example, it is WS_SEND_NOTIFICATION and WS_PIR_CREATION.

When the condition has been fulfilled the expression to raise and the workflow event will be executed.

Each expression will contain a Business workflow ABAP object ( it can be also a Business object ). In this example, it is the ABAP Class technique. Set the ABAP class and the event.

The ABAP class should contain Interface IF_WORKFLOW as the other class that is supposed for SAP Business workflow scenarios.

The object instance is used to create an instance of the class, it is needed to assign the key for the object. In this case, it is the combination of Plant and Material. The key can be built with a formula expression using the data objects (elements) from the function's context.

FDT_E_SIBFBORIID = CONCATENATE ( IT_LINES-PLANT, IT_LINES-MATERIAL ).

After setting ABAP class and Event, press the button to Update the container. It will read import data for the event and will propose the binding. ZBS_TS_ATPV_VIEW is the structure line of the input table from the function. The same type of structure is assigned to the event of the ABAP class.

When these prerequisites are fulfilled, the event will be raised during BRF plus function call or during BRF plus simulation with performing Actions. The event creation can be caught with a breakpoint in the FM SWW_WI_CREATE_VIA_EVENT_IBF.

Import Event Push of Configuration Text Tables to External Database

2022-02-09T22:39:46+01:00

Introduction

I was recently posed with a problem that needed a new solution for our planned S4 migration in a few weeks. How to get the configuration domain text data to an external database to retain some existing reporting capabilities? I'm betting that a lot of folks work in heterogenous landscapes and sometimes it requires getting creative with how to tackle a problem. I have seen a couple of approaches in the past and have to admit that I'm not a fan of either, but I'll let you decide for yourself which one is least preferred. First example - two synchronous ABAP Proxies of megalith proportions statically defined to return data on several dozen configuration domains based on daily or weekly frequency. The second - several recurring job instances throughout the day (four or five maybe) that extract the data whenever change pointers are detected on dependent business objects, and saved as files on the application server, which requires some other process to fetch the data and load it. Is a many times daily, daily, or weekly cadence appropriate given the relatively infrequency that configuration tables are updated in a productive environment?

Proposal

What if there were an event that could push the data for a pit stop into Integration Suite for some transformation before reaching its final destination in the external database? I spent a few hours pondering the question and came up with the following: Implement BADI CTS_IMPORT_FEEDBACK along with BRF+ to evaluate customizing requests and push table names to Integration Suite. Start with an iterating splitter, and sprinkle a little graphical mapping, content enricher via OData, and XSL transform and arrive at XML that can be processed by the JDBC adapter to initiate stored procedures for UPSERT. What follows is the culmination of a day and a half of build, learning, and experimentation with a couple of gotchas along the way.

ABAP

The original intent was to execute the entirety of ABAP within this BADI method, but after I had completed the full service layer in Integration Suite and worked backward into this method, I discovered that it executes in client 000, and received a ST22 dump when the BRF+ application could not execute. The BRF+ code was pushed into the RFC function module. Consequently, after working in SAP software for 14 years and having never logged in to client 000, I have for the first time (SM59 destination), and doubtful I ever would again. You may also wonder why I wouldn't simply read keys and use a combination of RTTS and web services to push the data to Integration Suite. Beyond avoiding the megalith mentioned above, dealing with situations where some columns are ignored for certain tables, and determining appropriate structure, it certainly wouldn't be blog worthy and you wouldn't be reading this! After following the remaining steps I think it will be clear why I decided to go with the chosen route.

METHOD if_ex_cts_import_feedback~feedback_after_import.



  DATA: corr   TYPE trwbo_request,

        tables TYPE tt_tabnames.



* Read object keys for import

  CLEAR: tables.

  LOOP AT requests INTO DATA(request).

    CLEAR corr.

    CALL FUNCTION 'TR_READ_REQUEST'

      EXPORTING

        iv_read_objs_keys = 'X'

        iv_trkorr         = request-trkorr

      CHANGING

        cs_request        = corr

      EXCEPTIONS

        error_occured     = 1

        no_authorization  = 2

        OTHERS            = 3.



    IF sy-subrc = 0.

*     Record any tables for evaluation in BRF+

      LOOP AT corr-keys INTO DATA(key)

              WHERE object = 'TABU'.

        APPEND key-objname TO tables.

      ENDLOOP.

    ELSE.

*     Should never happen based on data requested in FM

    ENDIF.

  ENDLOOP.



* Sort and remove duplicates and pass to RFC for

* communication

  SORT tables.

  DELETE ADJACENT DUPLICATES FROM tables.

  CALL FUNCTION 'ZCA_WS_CONFIG_UPDATE_DISPATCH'

       DESTINATION 'CFGUPDDISP'

    EXPORTING

      table = tables.



ENDMETHOD.

Originally, this RFC was only intended to be a shell for my enterprise service consumer proxy generation (we do not have an ESR), but after experiencing the client 000 problem it became a suitable surrogate to execute the BRF+ application in the appropriate client, as well as the ABAP proxy.

 FUNCTION zca_ws_config_update_dispatch.

*"----------------------------------------------------------------------

*"*"Local Interface:

*"  IMPORTING

*"     VALUE(TABLE) TYPE  TT_TABNAMES

*"----------------------------------------------------------------------



  DATA:timestamp    TYPE timestamp,

       t_name_value TYPE abap_parmbind_tab,

       name_value   TYPE abap_parmbind,

       r_data       TYPE REF TO data,

       input        TYPE zzca_ws_config_update_dispatch,

       proxy        TYPE REF TO zco_zws_config_update_dispatch.



  CONSTANTS: function_id TYPE if_fdt_types=>id VALUE '005056977E091EECA1F05A7D5FE1B25F'.



* Set timestamp for processing and move input data into reference

  GET TIME STAMP FIELD timestamp.

  name_value-name = 'TT_TABNAMES'.

  GET REFERENCE OF table INTO r_data.

  cl_fdt_function_process=>move_data_to_data_object( EXPORTING ir_data             = r_data

                                                               iv_function_id      = function_id

                                                               iv_data_object      = '005056977E091EECA1F05DC93384D25F' "TT_TABNAMES

                                                               iv_timestamp        = timestamp

                                                               iv_trace_generation = abap_false

                                                               iv_has_ddic_binding = abap_true

                                                     IMPORTING er_data             = name_value-value ).

  INSERT name_value INTO TABLE t_name_value.

  CLEAR name_value.



  TRY.

*   Execute BRF+ function

    cl_fdt_function_process=>process( EXPORTING iv_function_id = function_id

                                                iv_timestamp   = timestamp

                                      IMPORTING ea_result      = input-table-item

                                      CHANGING  ct_name_value  = t_name_value ).



*   Only execute proxy if any tables of interest are found

    IF input-table-item[] IS NOT INITIAL.

      CREATE OBJECT proxy.

      CALL METHOD proxy->zca_ws_config_update_dispatch

        EXPORTING

          input  = input.



      COMMIT WORK.

    ENDIF.



    CATCH cx_fdt.

*     Do what on error?

    CATCH cx_ai_system_fault.

*     Do what on error?

  ENDTRY.



ENDFUNCTION.

BRF+

I find BRF+ to be an often underutilized gem in the system. If I have a simple question for the system to answer, pass the necessary input and let it determine the outcome. The true beauty is that I can add or remove a table for this scenario without writing a single line of ABAP!!

Integration Flow

The first two steps of the flow are setup steps to determine the backend OData host and split the incoming message by each table. The last three steps will be presented in more detail below.

Full E2E Integration Process

Graphical Mapping

This mapping serves the purpose of mapping a backend table name into four corresponding bits of data... stored procedure, OData service name, resource, and query using a combination of the fixValues function and a couple of simple Groovy scripts. Folks could be wondering why not use value mapping, but I feel like that is a lot of overkill to maintain several input fields instead of simple 1:1 mappings with fixValues. Also, note the use of the query parameter is used because for one table we don't want the full field list. If we use $select query options for one table in the OData adapter we must maintain it for all (Tried the empty string and it did not work). This leaves me with a choice dilemma:

Option 1 - Add a query parameter, which is more stuff to maintain in the graphical mapping

Option 2 - Do not add query parameter and handle stripping of extra fields in XSL transform

Since I'd rather not select fields and transport extra data over the network that is of no consequence, I went with the first option.

Graphical mapping for OData/Stored procedure determination

The setHeader function should be self explanatory, but the joinContexts function is to establish a queue like some of the older PI/PO functions. I could not find an equivalent in Integration Suite, so I constructed my own (Feel free to share if there is some out of the box option that I could not find).

// Insert message headers

def void setHeader(String[] keys, String[] values, Output output, MappingContext context){

  def i = 0;

  while(i < keys.size()) {

    context.setHeader(keys[i], values[i]);

    i++;

  }

}



// Create context queue to match keys with values

def void joinContexts(String[] input1, String[] input2, String[] input3, Output output, MappingContext context){

  output.addValue(input1[0]);

  output.addValue(input2[0]);

  output.addValue(input3[0]);

}

Content Enricher via OData

The first image includes basic host and service metadata that is handled in the first step, and the graphical mapping step. I was unsure if externalized parameters and headers would be concatenated like two headers, so I went with this option. If externalized parameters do work in this way, then I could eliminate the first step in the flow. The second image shows the processing tab with the other metadata required for the OData service call. You may be wondering at this point... what about V2 vs. V4? For the 10 tables I need to push, I was able to identify 2 services that are both V2. If I have to cross that bridge in the future, I can manage with the addition of a version metadata field in the graphical mapping and an appropriate routing step.

OData Connection Information

OData Processing Information

The following XML is the result after the content enricher via OData using the combine algorithm. The nice feature/outcome being that I did not have to statically define any table structures or field types anywhere in the solution.

<?xml version='1.0' encoding='UTF-8'?>

<multimap:Messages xmlns:multimap="http://sap.com/xi/XI/SplitAndMerge">

  <multimap:Message1>

    <Root>

      <StoredProcedure>sp_TVV1T</StoredProcedure>

    </Root>

  </multimap:Message1>

  <multimap:Message2>

    <AdditionalCustomerGroup1> 

      <AdditionalCustomerGroup1> 

        <AdditionalCustomerGroup1_ID>T01</AdditionalCustomerGroup1_ID>

        <AdditionalCustomerGroup1Text>Tier 1</AdditionalCustomerGroup1Text> 

      </AdditionalCustomerGroup1> 

      <AdditionalCustomerGroup1> 

        <AdditionalCustomerGroup1_ID>T02</AdditionalCustomerGroup1_ID>

        <AdditionalCustomerGroup1Text>Tier 2</AdditionalCustomerGroup1Text> 

      </AdditionalCustomerGroup1> 

      <AdditionalCustomerGroup1> 

        <AdditionalCustomerGroup1_ID>T03</AdditionalCustomerGroup1_ID> 

        <AdditionalCustomerGroup1Text>Tier 3</AdditionalCustomerGroup1Text> 

      </AdditionalCustomerGroup1> 

      <AdditionalCustomerGroup1> 

        <AdditionalCustomerGroup1_ID>T04</AdditionalCustomerGroup1_ID> 

        <AdditionalCustomerGroup1Text>Tier 4</AdditionalCustomerGroup1Text> 

      </AdditionalCustomerGroup1> 

      <AdditionalCustomerGroup1> 

        <AdditionalCustomerGroup1_ID>T05</AdditionalCustomerGroup1_ID>

        <AdditionalCustomerGroup1Text>Tier 5</AdditionalCustomerGroup1Text>

      </AdditionalCustomerGroup1> 

      <AdditionalCustomerGroup1>

        <AdditionalCustomerGroup1_ID/>

        <AdditionalCustomerGroup1Text/> 

      </AdditionalCustomerGroup1> 

    </AdditionalCustomerGroup1>

  </multimap:Message2>

</multimap:Messages>

XSL Transform

For the sake of brevity, I have included a truncated XSL transform that only includes 3 tables despite my requirement being 10 tables. If you happen to be a savvy XSL veteran, and find my work to be rudimentary, keep in mind that this is my first XSL transform after spending 30 minutes reading and learning on W3Schools. I did implement the XSL transform in such a way that empty string key records would be removed from the stream.

<?xml version="1.0" encoding="UTF-8"?>



<xsl:stylesheet version="1.0"

xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:multimap="http://sap.com/xi/XI/SplitAndMerge">



<xsl:template match="/">

  <root>

    <StatementName>

      <storedProcedureName action="EXECUTE">

        <table><xsl:value-of select="multimap:Messages/multimap:Message1/Root/StoredProcedure"/></table>

        <ProcedureParameter type="CLOB">

          <xsl:text disable-output-escaping="yes">&lt;![CDATA[</xsl:text>



          <!-- TVM4T Procedure -->

          <xsl:for-each select="multimap:Messages/multimap:Message2/AdditionalMaterialGroup4">

            <List>

              <xsl:for-each select="AdditionalMaterialGroup4[AdditionalMaterialGroup4_ID!='']">

                <Item>

                  <MaterialGroup4><xsl:value-of select="AdditionalMaterialGroup4_ID"/></MaterialGroup4>

                  <MaterialGroup4Text><xsl:value-of select="AdditionalMaterialGroup4Text"/></MaterialGroup4Text>

                </Item>

              </xsl:for-each>

            </List>

          </xsl:for-each>

          

          <!-- TVM5T Procedure -->

          <xsl:for-each select="multimap:Messages/multimap:Message2/AdditionalMaterialGroup5">

            <List>

              <xsl:for-each select="AdditionalMaterialGroup5[AdditionalMaterialGroup5_ID!='']">

                <Item>

                  <MaterialGroup5><xsl:value-of select="AdditionalMaterialGroup5_ID"/></MaterialGroup5>

                  <MaterialGroup5Text><xsl:value-of select="AdditionalMaterialGroup5Text"/></MaterialGroup5Text>

                </Item>

              </xsl:for-each>

            </List>

          </xsl:for-each>



          <!-- TVV1T Procedure -->

          <xsl:for-each select="multimap:Messages/multimap:Message2/AdditionalCustomerGroup1">

            <List>

              <xsl:for-each select="AdditionalCustomerGroup1[AdditionalCustomerGroup1_ID!='']">

                <Item>

                  <CustomerGroup1><xsl:value-of select="AdditionalCustomerGroup1_ID"/></CustomerGroup1>

                  <CustomerGroup1Text><xsl:value-of select="AdditionalCustomerGroup1Text"/></CustomerGroup1Text>

                </Item>

              </xsl:for-each>

            </List>

          </xsl:for-each>



          <xsl:text disable-output-escaping="yes">]]&gt;</xsl:text>

        </ProcedureParameter>

      </storedProcedureName>

    </StatementName>

  </root>

</xsl:template>



</xsl:stylesheet>

The resulting XML is JDBC adapter ready

<root xmlns:multimap="http://sap.com/xi/XI/SplitAndMerge">

  <StatementName>

    <storedProcedureName action="EXECUTE">

      <table>sp_TVV1T</table>

      <ProcedureParameter type="CLOB">

        <![CDATA[

        <List>

          <Item><CustomerGroup1>T01</CustomerGroup1><CustomerGroup1Text>Tier 1</CustomerGroup1Text></Item>

          <Item><CustomerGroup1>T02</CustomerGroup1><CustomerGroup1Text>Tier 2</CustomerGroup1Text></Item>

          <Item><CustomerGroup1>T03</CustomerGroup1><CustomerGroup1Text>Tier 3</CustomerGroup1Text></Item>

          <Item><CustomerGroup1>T04</CustomerGroup1><CustomerGroup1Text>Tier 4</CustomerGroup1Text></Item>

          <Item><CustomerGroup1>T05</CustomerGroup1><CustomerGroup1Text>Tier 5</CustomerGroup1Text></Item>

        </List>

        ]]>

      </ProcedureParameter>

    </storedProcedureName>

  </StatementName>

</root>

JDBC

Disclaimer: This part has not actually been tested, but instead the above XML was dumped to an FTP site for extraction during unit testing.

Once the DB admins are able to create the necessary stored procedures I will include an editorial update. In the past, I have used the JDBC adapter in PI/PO where we can do bulk inserts, but I did stumble upon some blog/answer posts, and an OSS note indicating that bulk inserts are not supported in Integration Suite unless using a splitter in batch mode. I referred to the following blog on the topic of using stored procedures, which I had used in the past in PI/PO - Stored procedure as XML Type I opted not to split an already split message, along with the fact that this approach fares far better from a performance perspective.

Conclusion

After reaching a point where I can successfully unit test the full solution outside of of the JDBC handling, I'm pleased with the outcome. For future's sake, if I need to add a new table in the future the process is quite simple:

Add table to BRF+ expression

Identify/build an OData service - Note: if you have spent inordinate amounts of time working backward from tables to a usable OData service, then you are not alone, and I would rather reuse than build. I don't need draft capabilities for this type of thing and I'm still presented with choosing from multiple options... whatever happened to software reusability, but that's a topic for another day

Add four bits of metadata (maybe five if versioning enters the picture) for OData and a stored procedure into the graphical mapping step

Add a new block to the XSL transform

Get a DB Admin to create the required stored procedure

Hope folks can get something useful out of this... enjoy!

S/4HANA - OPD - Procedure creation and consumption

2022-03-23T17:30:15+01:00

Hello fellow community members,

In this blog I would like to share my experience on the creation as well as consumption of a procedure call in BRF+ which is used by the OPD transaction.

A little background, OPD is the newer equivalent of NACE in S/4HANA used for configuring and issuing outputs. NACE is used in ECC to configure output controls and map forms with driver programs and trigger the output.

Back to the topic - Here, I will give an illustrative document on how to create procedures and use them. As an example I have done this on Central Purchase Contracts business object available in the Central Procurement solution -

The steps will be divided as below -
A. Creation of Element and Procedure
B. Creation of application logic
C. Embedding the created procedure in the OPD transaction

In Detail,

A. Creation of Element and Procedure

1. Open BRF+ transaction in SAP GUI.
URL will look like - https:///sap/bc/webdynpro/sap/fdt_wd_workbench?sap-language=EN&sap-client=<3 digit client id>#

2. Put application - OPD_MM_CENTRAL_CONTRACT and search

3. Creation of Element

-> This creates an element.

4. Creation of Procedure

-> This creates a procedure and also assigns the above created element as the result data object.

B. Creation of application logic

1. Creation of class and static method

-> This creates the placeholder for the application logic

2. Map the parameters which will be used in application logic

-> Newly added parameters are mapped.

-> Upon activation, message is displayed.

C. Embedding the created procedure in the OPD transaction

1. Launch the OPD transaction in SAP GUI

2. Choose the business object as 'Central Purchase Contract' and the determination step as 'Output Type'

3. Go to Edit – Table Settings – Pull the custom expression which was created above and maintain values in same.

Finally, to conclude - the issued outputs will look like rows in below table in Manage Central Purchase Contracts app -

Tips for working with expressions -

1. A 'blank' is different from a 'false' in the decision tables.
2. If values are not maintained (left as 'blank') then the expression class is not called, and the static method is not invoked.

Other Tips -

1. The Function Module - CNTRL_CONTRACT_OM_TRIGGER gets triggered for Central Purchase contracts for issuing output. It can be debugged for any behaviour conceptualization.
2. Always put an external breakpoint on SAP_WFRT (Workflow User) and analyse.

To further ignite the passion, I would like to highlight few practical use cases - this approach can be used to dynamically control output issuance like issue output only if Distribution Lines in a Contract are active, send emails to different recipients based on priority, etc.

Please provide your valuable feedback.

Thanks.

Transport changes related to BRF+ object

2022-03-25T09:02:42+01:00

In OPD UI there is no way with which you can change the transport request hence, in this document I am going to show you a workaround

One option is to use transaction FDT_HELPERS which is explained in the blog post here

In this blog post I am suggesting another way to write your changes related to decision tables to a TR

First, you need to fetch the object id for a decision table which you can get by following the below steps

In OPD transaction, select the object and determination step

Click more> display object version

Expand General section and copy the object id or make a note of it

Execute BRF+ Tcode in SAP gui and switch the user mode to expert (KBA2830979)

Go to workbench and select open object

Search with the object id copied above

From here you can write your changes to a TR by clicking transport

Once you click on transport, a pop up will appear where you can enter your TR number to which you want to write your changes.

Tip- You can use this method instead of OPD (once you find the object id) as this screen offers more features than OPD UI

Bonus Tip- While importing the OPD related changes make sure the OPD screen is not open otherwise the changes wont be copied in the target client

Thank you, Please provide your valuable feedback or do let me know if you have any questions

Thanks,

Siddhant S.

PFCG based agent rule on steroids :)

2022-04-27T09:21:45+02:00

Requirement: Many clients do not have one to one or one to many assignment of roles to role owners rather they have some specific logic to define role owners. In our setup, GRC approvers are defined based on functional area, business process, connector etc. For easy maintenance of GRC approvers role-based agent rule was created.

Resolution: Create a BRF+ Agent rule that will fetch approvers, based on decision table criteria and dummy role assignment.

BRF+ Design:

Below Steps will be followed to achieve required results:

Step 1: Create Structure “AGR_USERS”

Step 2: Create a decision table to provide “dummy role name” based on suitable selection.

Step 3: Create a DB lookup on table “AGR_USERS” to fetch users assigned to appropriate dummy roles.

Step 4: Create a “Ruleset” to process DB lookup and return approvers.

BRF+ Configuration:

You have to generate the BRF+ Rule via Transaction SPRO in GRC system. Follow the below steps in your GRC system.

Run the transaction SPRO, go to IMG => Governance, Risk and Compliance =>Access Control =>Workflow for Access Control => Define Workflow related MSMP rules.

Or

Directly execute TCode GRFNMW_DEV_RULES

Fill generation criteria (Process ID, Rule type, etc.)

Specify Generation options

Generate rule shell (Execute button)

After successful rule generation, goto BRF+ to check newly created BRFPlus Application

Function Signature update:

In BRF+ function, change the mode to “Event Mode” and activate the function as shown below.

Since Function mode has been changed to “Event mode,” the result data object has changed automatically, so it has to be reset manually

In “Signature” tab of BRF Function, change the result data object to GRFN_MW_T_AGENT_ID

Create Structure:

From context menu of BRF+ application, create a Structure and bind it to AGR_USERS.

Save and activate this structure.

Create a Decision Table:

From context menu of BRF+ application, create an Expression of type “Decision Table”

Add “Condition” as well as “Result” column based on requirement

Note that AGR_NAME in result column can only be selected if structure AGR_USERS has already been created.

Create dummy roles in GRC backend system and assign to approvers

Populate the decision table with business data as required

Create DB Lookup:

From context menu of BRF+ application, create an Expression of type “DB Lookup”

Add below details to the DB Lookup, here we are applying DB lookup based on result received from ZROLEOWNER on table AGR_USERS and inserting user ID into GRFN_MW_T_AGENT_ID

Save and generate the DB Lookup

Create Ruleset:

Click “Create and Navigate To Object”

Create Rule as below:

Assign the ruleset to the function

Go to the function and under assigned ruleset you should be able to fine “GET_APPROVER” ruleset.

Simulate BRF+ rule:

Provide mandatory context values like Business Process, Functional Area, Connector.

The function should return users IDs of the role owner as per the settings in decision table.

Conclusion: This custom agent rule will allow us to skip standard role owner maintenance process in GRC and simply assign approvers by assigning them dummy roles created in GRC system. Dummy roles can be created as per our requirement for example based on system\client, departments, business process etc.

Transportation Management : Dynamic determination of PPF profiles using BRFPlus

2022-08-10T11:24:49+02:00

Hello Everyone,

Welcome to the technical series of the SAP Transportation Management .

With this blog post, we will learn how to assign the BRFPlus application which can be used to determine the PPF action profiles dynamically.

We had the requirement where PPF profiles need to be determined based on TOR Type.

Lets get started and create the BRFPlus application using Tcode BRFPlus

Create the BRF+ Application and then create the Function inside the same app

BRF+ Function

We created the BRF+ Function as ZFUNC_PPF_GET_PPF_PROFILES with below signature

Here, IT_KEY and IT_KEY_DELETED and ET_PPF_PROFILES are mandatory parameters for BRF+ Function

Other two parameters, ZT_FREIGHT_DATA and ZT_PPF_PROFILES are like internal tables ( created for intermediate processing)

ET_PPF_PROFILES is the exporting parameter which will hold the PPF Profiles.

Next step is to create Ruleset inside the BRF+ Function

Ruleset

We created Ruleset ZRS_GET_PPF_PROFILE

First Rule is to read the BOPF data as we need to get the TOR type. Here, you can call any Procedure to read the data

So, we have basically called procedure to get the TOR details and stored it into ZT_FREIGHT_DATA

Now, after getting the data, we need to Loop on the data, and need to get the PPF profiles using the decision table. So Rule2 is as below

Inside the loop, Decision table is called to get the profiles.

Decision table is as below:

Please note, here, am not giving much complex details of each Rule as that's completely developer's logic to write in his own way. I would like to focus more on the concept.

Configuration:

After BRF+ Application is created, we need to assign the app and function in the configuration so that PPF action profiles can be determined by calling this BRF+ Function based on TOR type of the document that gets created.

Path is Open SPRO and then follow below path :

SPRO

In the Maintain Output Management Adapter Settings, below config is required with Business Object and node :

Assign BRF+ app

In the Func. for Act. Prof. field, enter the BRFplus selection function that returns the
list of PPF profiles for a given BO node.

BRF+ application name.BRF+ Function name

After successful configuration and maintenance, PPF profiles will be determined via BRF+ at runtime.

Hope you enjoyed reading.

Part1 of the series : Transportation Management : Read Freight documents from Delivery | SAP Blogs

Part2 of the series : PART2 – Transportation Management : Read Carrier details from Freight Order | SAP Blogs

Part3 of the series : PART3 – Transportation Management : Get Route details from freight Unit | SAP Blogs

Thank You

Ishani

How to Use Dynamic SO10 Text in BRF+ Adobe Form Output

2022-09-30T13:09:07+02:00

Hi,

In this post ,I would like to share with you, how to use dynamic SO10 text elements on standard Adobe form that you maintain with SFP tcode and also show you, how to achieve same thing with BRF+ Adobe form outputs those need to be maintained in Adobe Live Cycle application.

SFP PART

For non BRF+ cases, If you want to use SO10 text elements with their styles in Adobe form, you can go to SFP transaction, create a form and add TEXT element to context, bind that text element to a text object on layout. That is it, it will work nicely.

You can drag and drop from context to layout. It will create necessary element on layout with bindings.

First lets see, how we can do it with SFP tcode.

To Add Text to Context

Non BRF+ Form

Layout Object properties for TEXT element

And sample code to read to text for the case above

  METHOD fill_doc_ship_type_txt.

    DATA: exref TYPE REF TO cx_root.

    TRY.

        CLEAR docstc-ship_type_text_name.

        IF docstc-vstel IS NOT INITIAL AND docstc-vsart IS NOT INITIAL.

          

          "Some logic to determine name

          docstc-ship_type_text_name = 'ZDLVY_XYZ' && docstc-vstel && '_' && docstc-vsart.

          CONDENSE docstc-ship_type_text_name NO-GAPS.



          IF langu IS INITIAL.

            langu = 'E'.

          ENDIF.



          docstc-ship_type_text_langu = langu.



          CALL FUNCTION 'READ_TEXT'

            EXPORTING

              id                      = 'ST'

              language                = docstc-ship_type_text_langu

              name                    = docstc-ship_type_text_name

              object                  = 'TEXT'

            TABLES

              lines                   = docstc-ship_type_text "Contains text lines, type TSFTEXT

            EXCEPTIONS

              id                      = 1

              language                = 2

              name                    = 3

              not_found               = 4

              object                  = 5

              reference_check         = 6

              wrong_access_to_archive = 7

              OTHERS                  = 8.

          IF sy-subrc <> 0.



            IF langu NE 'E'.

              result = fill_doc_ship_type_txt( langu = 'E' ).

            ELSE.

              result-status = c_stat_warning.

              IF NOT sy-msgid IS INITIAL.

                MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno

                      WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4

                      INTO result-status_text.

              ENDIF.

            ENDIF.



          ELSE.

            result-status = c_stat_success.

          ENDIF.



        ELSE.

          result-status = c_stat_error.

        ENDIF.



      CATCH cx_root INTO exref.

        result-status = c_stat_error.

        result-status_text = exref->get_text( ).

    ENDTRY.

  ENDMETHOD.

That is it for SFP form. With those steps above, you can use TEXT element with dynamic text objects in non BRF+ forms.

BRF+ PART

But, if you want to have same functionality with BRF+, you need to download your form from fiori app "Maintain Form Templates" and then edit form in Adobe Live Cycle Designer. Once you complete editing you need to upload them back. The problem is, Adobe Live Cycle Designer does not have context to add TEXT object. It does not know about SAP SO10.

There is a solution! 🙂 You can pass string that contains html tags such as <b></b> and run Javascript code events to interpret the string as html.

Now lets see how to do that.

First we need to add tags to our SO10 text.

in Word Editor

In XYZ_get_entityset method we will read our text and concatenate it according SO10.

method xyz_get_entitsey.

............



CALL FUNCTION 'READ_TEXT' 

      EXPORTING 

        id                      = 'ST' 

        language                = 'E' 

        name                    = name 

        object                  = 'TEXT' 

      TABLES 

        lines                   = texts-tdlines 

      EXCEPTIONS 

        id                      = 1 

        language                = 2 

        name                    = 3 

        not_found               = 4 

        object                  = 5 

        reference_check         = 6 

        wrong_access_to_archive = 7 

        OTHERS                  = 8. 

 

    IF sy-subrc IS INITIAL. 

 

      CALL FUNCTION 'CONVERT_ITF_TO_STREAM_TEXT' 

        EXPORTING 

          language     = 'E' 

          lf           = abap_true 

        IMPORTING 

          stream_lines = texts-strlines 

        TABLES 

          itf_text     = texts-tdlines. 



      "Add Lines to entityset table      

      DATA: newline TYPE LINE OF zcl_zfdp_ef_purchase_o_mpc=>tt_pofixtext. 

      LOOP AT texts-strlines ASSIGNING FIELD-SYMBOL(<wa>). 

        CLEAR newline. 

        newline-seqno = sy-tabix. 

        newline-tdline = <wa>. 

 

        "Some sort of logic to open close tags for each line, in case if user forgets to add                

        "Javascript event will work for each line,therefore tags needs to exists for each line

        IF newline-tdline CP '*<b>*' AND NOT newline-tdline CP '*</b>*'. 

          newline-tdline = newline-tdline && '</b>'. 

        ELSEIF newline-tdline CP '*</b>*' AND NOT newline-tdline CP '*<b>*'. 

          newline-tdline = '<b>' && newline-tdline. 

        ENDIF. 

 

        IF newline-tdline CP '*<u>*' AND NOT newline-tdline CP '*</u>*'. 

          newline-tdline = newline-tdline && '</b>'. 

        ELSEIF newline-tdline CP '*</u>*' AND NOT newline-tdline CP '*<u>*'. 

          newline-tdline = '<u>' && newline-tdline. 

        ENDIF. 

 

        IF newline-tdline CP '*<i>*' AND NOT newline-tdline CP '*</i>*'. 

          newline-tdline = newline-tdline && '</b>'. 

        ELSEIF newline-tdline CP '*</i>*' AND NOT newline-tdline CP '*<i>*'. 

          newline-tdline = '<i>' && newline-tdline. 

        ENDIF. 

 

        APPEND newline TO et_entityset. 

      ENDLOOP. 

    ENDIF. 

..........

endmethod.

Add a table to list rows, as you would do for any table view.

shows Tdline element of table

And just add a javascript initialize event with following code.

// Form.FixText.xyz.Tdline::initialize - (JavaScript, client)

if(this.rawValue != null)

{

	var envelope = "<?xml version='1.0' encoding='UTF-8'?>" +

	  "<exData contentType='text/html' xmlns='http://www.xfa.org/schema/xfa-template/2.8/'" +

	  "><body xmlns='http://www.w3.org/1999/xhtml' xmlns:xfa='http://www.xfa.org/schema/xfa-data/1.0/' " +

	  "xfa:APIVersion='Acroform:2.7.0.0' xfa:spec='2.1'>" +

	  "<p>"+ this.rawValue +"</p></body></exData>";

	

	this.value.exData.loadXML(envelope,1,1);

}

And if you print, you will see;

PDF Output

There were blog posts and answers to give clues on solving BRF+ and SO10 case. But there was not a complete answer. Therefore I decided to write a post. Hope that helps you.

If you know an alternative solution, please add it to comments.

Thanks for reading.

Links:

A blog post on dynamically placing image on form from se78.

And this class is quite useful : cl_ssf_xsf_utilities , check the methods.

Using BRFplus in SAP Adhoc Query

2022-11-09T19:45:44+01:00

SAP has two powerful frameworks to support a functional consultant. These are:

BRFplus

SAP Adhoc query.

In this blog I would like to share my experience in calling a BRFplus function within an SAP Adhoc query. This I hope with help in extending the reach that BRFplus and SAP Adhoc query can provide for your requirements.

Scenario:

I am using an Adhoc query based on a simple table based infoset to display a set of fields. The query reads data from a custom table used in a custom application developed with ABAP. Now in the underlying infoset used by the adhoc query, I have created an 'additional field' called 'staff' which is populated by a call to a BRFplus function.

Of course, there are other means to populate this additional field but the use of BRFplus is just to illustrate the power in using the combination of SAP Adhoc query with BRFplus.

A: Create a simple BRFplus application:

While this blog is focused mainly to show the use of both the above frameworks in tandem, I will not be going through in detail to create the brfplus artifacts. So only the high-level steps are shown.

This involves:

1. Creating an application in BRFplus (the transaction code is brfplus)

2. Create the Function:

This function has the input of 'User' (based on field UserID) and outputs 'PERNR' (based on fied PERNR). The ruleset used (ZJB01RS) consists of a 'Rule' that reads table 'PA0105' (standard table in HCM) passing User (UserID) and Subtype and fetching PERNR from table PA0105.

The RULESET called ZJB01RS.

The Database lookup "FETCHPERNR" used in rule above.

Once the BRFplus artifacts are saved and activated the 'simulation' to check the application is below.

Now that the BRFplus application works, the 'Class' to be generated as below. Use the "Generate Function" to do this under the "Code Generation' tab

Now to display the "code template' to be used in our infoset in the SAP Adhoc query. Click on the "Create Code Template' button (see the above image).

The code template is as shown below. Copy this code to be later used in our 'INFOSET'.

B: The SAP ADHOC Query:

The adhoc query creation has 2 steps:

1.Create the Infoset:

The infoset created using transaction 'SQ02' is based on a simple table as shown below.

I have added the required fields from the table and also create an 'Additional field' called 'staff'.

I will populate this field called 'Staff' using the brfplus function created earlier. Right click on the field "staff" and go to "field code".

Copy and paste the 'Code Template"" that we created in the brfplus to the below and make minor modifications in the code.

The modifications needed to read the data from the brfplus is below:

There is a field in the infoset called "Name of the person who changed the object". This field is of the type "UserID'. Use the technical name of the field and assign to the input parameter of the code.

Similarly assign the output parameter as below. Field 'Staff' is assigned to the importing field 'ea_result".

  TRY.

      cl_fdt_function_process=>process( EXPORTING iv_function_id = lv_function_id

                                                  iv_timestamp   = lv_timestamp

                                        IMPORTING ea_result      = staff 

                                        CHANGING  ct_name_value  = lt_name_value ).

      CATCH cx_fdt into lx_fdt.

Save and Generate the infoset and assign to the appropriate 'User Group".

2. Create the query based on the above infoset.

Create the Query based on the above infoset

The fields used

Now execute the query. You will see the field "Staff" getting populated from the brfplus as below.

This blog post only provides a high-level overview of the creation of the BRFplus application and SAP Query since the idea was to only provide how BRFplus can be used in SAP Query and expand the reach of these two frameworks. Should you need details on the creation of the above artifacts, I am happy to provide.

If you have any questions, you can comment below. I would love to hear from you on how you were able to use this option to provide more value to your business.

Some useful and important tips to overcome issues and challenges while configuring business rules in SAP SuccessFactors employee central (EC)

2022-12-05T04:43:02+01:00

This article has been written assuming the reader has fair amount of knowledge about Employee central and business rules. This can be handy for every functional configurator while working on business rules. Business rules can become highly complex sometimes, not in terms of writing the logic but testing as well. I would like to share some important points in this article that can be helpful for every configurator including a beginner.

1. It is always suggested to choose the application specific category from rule scenario instead of directly taking a basic rule. This will be helpful to avoid unexpected issue or rework later. Choosing a rule category restricts the base objects for you.

2. It's very common at every client to configure background elements. Before you take a requirement to update these elements, please keep in mind that business rules are currently NOT supported for background elements.

3. Make sure you choose the Model base objects ex. Job information model to write logic on field properties (ex. required, visibility, previous). System can only work on values with non-model objects ex. Job information.

4. Make sure to choose 'Rule for Hire/Rehire' from rule category if you want your rule to get triggered only during new hire or rehire. This will restrict the base object to only Employee Information" and "Employee Information Model". But it does not mean that rules with other Base Objects will not trigger in during New Hire. All rules related to employee data (ex. with base entity job info or job info model), will trigger during new hire and rehire.

5. To write business rules for complex requirements, variables can be explored to start with. Storing variables initially, helps reduce the processing logic. I would recommend starting to write the logic flow on a piece of paper and start configuring the rule. You may also come across some limitations of business rules while configuring so sooner the better you start configuring it.

6. Make sure you don't configure more than 5 cross entity business rules for an HRIS element ex. Job information portlet. System will give an error if you assign more than 6 cross entity rules. So, it is very important to make sure you haven't chosen cross entity rule from rule category when requirement can be met with a basic rule.

7. Cross entity rules are triggered onSave. Limited functionality is given for onChange. Please note that cross entity rules assigned OnSave to Job info portlet are triggered from Position to Job Info sync rule. Support for onchange cross portlets is introduced for a limited functionality. It works for Job information, Compensation Information and Pay component Recurring when both Job Information and Compensation Information Change checkboxes are selected in MSS UI (Take action).

8. To compare the values in the rule logic it is very important that data type of both fields match. Ex. you want to compare value from an MDF record using operator (<,>) with amount on recurring compensation information portlet, if you are not able to select amount on right side then try using any operator ex. Divide. In this case you will be able to select dividend from employee's comp info and divisor can be 1.

9. Always use Business rule execution log (rule trace) to debug the rule. Most of the issues can be solved reviewing the trace. Make sure to enter your business rule name if you want to review only your rule logic. In case you want to review the whole log including all rules triggered during a transaction then don't enter the rule name.

10. You can use the export and import utility to quickly export your business rule from one instance and import into another. Select the object 'Rule' to export the rules. The column' body' in the csv export will have the business rule logic.

11. As you know 'Lookup' is used to read records from a table. Please note that this function works with only MDF but not Foundation objects.

12. Never delete a business rule from an instance if it is assigned to an HRIS element for ex. Job information portlet. If you do you won't be able to open the configuration screen. In this example if you delete a business rule that has been assigned on job info portlet then when you open Manage business configuration and clock Job info you will get an error. In this case create a dummy rule with same name, remove the assignment from job info portlet and then delete the dummy rule.

13. You may come across a requirement to modify the employment dates like hire date, employment end date using a business rule but try to avoid doing that because it may lead to data issues and inconsistencies.

14. Always try to search existing business rule that can be modified or updated to include new requirement instead of directly creating a new rule. For ex. if you have a default a value on Job Info based on value in another field then assess similar existing rules instead of creating a new one. More the number of business rules, more is the execution time for a transaction. Number of business rules is inversely proportional to performance.

15. Make use of 'Context' for business rules to prevent unnecessary triggering of business rules. You can select context by clicking details in Manage business configuration.

For ex. you may not want a workflow rule to trigger during mass changes of data. In that case select 'Mass changes' No so that rule is not triggered during mass changes. Another example could be related to data conversion or imports. If you don't want a particular rule to get triggered during Imports, then select 'No' for imports.

16. If you come across a requirement to trigger a rule based on event reason attribute on Job info but you don't see event reason field from manage business configuration (MBC) then enable it. This field is hardcoded in data model so it's not necessary to enable in from MBC unless you want to configure 'onChange' rule on this field.

17. If you have multiple if else conditions in your rule, then try to keep those conditions on top that belongs to major employee population i.e., condition that narrows down the criteria the most.

18. If you have a requirement to default a job relationship during hire/rehire, then it is suggested to add matrix relationship to the position of new hire employee. During new hire the matrix relationships from position are synced to job relationships (enable this setting in Position management settings). You cannot set the user id for a relationship in job relationship portlet during hire/rehire due to system limitation.

19. If you have a requirement to set the field property editable, read only etc. for an MDF attribute then you have to create a configuration UI (Manage configuration UI) for the MDF and create a UI rule as shown below as an example.

20. If you have integration from Employee Central to Employee Central payroll and you have a requirement to make person id 8 digits through a business rule, then use the format function in business rule as shown below. Template %08d means that total digits in person id will be 8 digits.

Ex if your person id range (in sequence MDF) starts from 1000 then this rule will make that value 00001000.

Utility for copying MDG BRF+ workflow Decision Tables

2023-02-15T13:15:07+01:00

If for any reason, you have a fairly detailed segmentation of BP types and activities in MDG, there's a chance you have had to copy over BRF+ workflows.

Now, this is not a terribly difficult thing to do as the Import/Export functionality in BRF+ is a great feature. However minor changes can be a headache and I was getting tired of clicking the Import/Export button every time that happens.

Below is a little code I used to quickly copy over data the workflow BRF+ decision tables from one Change Request Workflow into another.

It's obviously rough. The error management could be improved, but it's good enough for occasional adjustment activity.

Helper Class

This is the local class I used as a helper.

CLASS lcl_brf DEFINITION.

  PUBLIC SECTION.

    METHODS get_reference_decision_tab

      IMPORTING iv_crtype TYPE string

      RAISING   zcx_mdg.

    METHODS get_decision_tab_object

      IMPORTING iv_name          TYPE string

      RETURNING VALUE(ro_object) TYPE REF TO cl_fdt_decision_table

      RAISING   zcx_mdg.

    METHODS get_decision_tab_data

      IMPORTING iv_name                TYPE string

      RETURNING VALUE(rt_decision_tab) TYPE if_fdt_Decision_table=>ts_table_data

      RAISING   zcx_mdg.

    METHODS copy_to

      IMPORTING iv_crtype TYPE string

      RAISING   zcx_mdg.

    METHODS copy_decision_table

      IMPORTING iv_name         TYPE string

                it_decision_tab TYPE if_fdt_Decision_table=>ts_table_data

      RAISING   zcx_mdg.



    METHODS constructor.



  PRIVATE SECTION.

    DATA mo_brf_query TYPE REF TO if_fdt_query.

    DATA mo_brf_factory TYPE REF TO if_fdt_factory.

    DATA mt_user_agent TYPE if_fdt_decision_table=>ts_table_data.

    DATA mt_non_user_agent TYPE if_fdt_decision_table=>ts_table_data.

    DATA mt_single_value TYPE if_fdt_decision_table=>ts_table_data.

ENDCLASS.



CLASS lcl_brf IMPLEMENTATION.

  METHOD constructor.

    mo_brf_factory ?= cl_fdt_factory=>if_fdt_factory~get_instance(  ).

    mo_brf_query ?= mo_brf_factory->get_query( ).

  ENDMETHOD.

  METHOD get_decision_tab_data.

    DATA : o_decision_table TYPE REF TO cl_fdt_decision_table.

    mo_brf_query->get_ids(

      EXPORTING

        iv_name   = CONV #( iv_name )

        iv_object_type = if_fdt_constants=>gc_object_type_expression

      IMPORTING

        ets_object_id = DATA(app_ids) ).

    o_decision_table ?= mo_brf_factory->get_expression( app_ids[ 1 ] ) .

    o_decision_table->if_fdt_decision_table~get_table_data( IMPORTING ets_data = rt_decision_tab ).

  ENDMETHOD.

  METHOD  get_reference_decision_tab.

    DATA : o_ref_decision_table TYPE REF TO cl_fdt_decision_table.

    mt_user_agent     = get_decision_tab_data( |DT_USER_AGT_GRP_{ iv_crtype }| ).

    mt_non_user_agent = get_decision_tab_data( |DT_NON_USER_AGT_GRP_{ iv_crtype }| ).

    mt_single_value   = get_decision_tab_data( |DT_SINGLE_VAL_{ iv_crtype }| ).

  ENDMETHOD.

  METHOD get_decision_tab_object.

    mo_brf_query->get_ids(

      EXPORTING

        iv_name   = CONV #( iv_name )

        iv_object_type = if_fdt_constants=>gc_object_type_expression

      IMPORTING

        ets_object_id = DATA(app_ids) ).

    ro_object ?= mo_brf_factory->get_expression( app_ids[ 1 ] ) .

  ENDMETHOD.

  METHOD copy_decision_table.





    DATA : o_decision_table TYPE REF TO cl_fdt_decision_table.

    TRY.

        o_decision_table = get_decision_tab_object( iv_name  ).

        o_decision_table->if_fdt_transaction~enqueue( ).

        o_decision_table->if_fdt_decision_table~set_table_data( EXPORTING its_data = it_decision_tab ).

        o_decision_table->if_fdt_transaction~activate(

            EXPORTING iv_deep              = abap_true

            IMPORTING et_message           = DATA(messages)

            ev_activation_failed = DATA(lv_actv_failed) ).

        if lv_actv_failed = abap_true.

          MESSAGE e000(zmdg) WITH 'Error updating' iv_name INTO zcl_messages=>sv_message_text.

          RAISE EXCEPTION TYPE zcx_mdg

            EXPORTING

              mo_messages = NEW zcl_messages( )->set_system_message( ).

        endif.



        o_decision_table->if_fdt_transaction~save( ).

        o_decision_table->if_fdt_transaction~dequeue( ).

      CATCH cx_fdt.

        MESSAGE e000(zmdg) WITH 'Error updating' iv_name INTO zcl_messages=>sv_message_text.

        RAISE EXCEPTION TYPE zcx_mdg

          EXPORTING

            mo_messages = NEW zcl_messages( )->set_system_message( ).

    ENDTRY.

  ENDMETHOD.

  METHOD copy_to.



    copy_decision_table( iv_name = |DT_USER_AGT_GRP_{ iv_crtype }|

                         it_decision_tab =  mt_user_agent ).



    copy_decision_table( iv_name = |DT_NON_USER_AGT_GRP_{ iv_crtype }|

                         it_decision_tab =  mt_non_user_agent ).



    copy_decision_table( iv_name = |DT_SINGLE_VAL_{ iv_crtype }|

                         it_decision_tab =  mt_single_value ).



  ENDMETHOD.

ENDCLASS.

Execution

Below is a sample code for using the class above.

START-OF-SELECTION.

  TRY.

      DATA(o_brf) = NEW lcl_brf( ).



      o_brf->get_reference_decision_tab( 'ZCR1' ).

      o_brf->copy_to( 'ZCR2' ).

      o_brf->copy_to( 'ZCR3' ).

    CATCH /gerp/cx_mdg INTO DATA(o_error).

      o_error->mo_messages->show_as_log( ).

  ENDTRY.

With that utility, I can update one workflow and then use the utility to copy to all the others.

This approach can be used in decision tables outside of MDG, but note that (1) the structure has to be the same and (2) you have to identify the application name is those situations as the Decision Table Name is not unique.

[BRF+ New Output Management]: Use DDIC Interface based Regular Custom Adobe Form – Handle ‘Spool request could not be found APOC_OR_MESSAGES 145’

2023-03-10T22:34:24+01:00

INTRODUCTION:

For the last few weeks, I have been working on a requirement that required a custom Adobe form for a standard GR label through NACE but later, we had to opt for new BRF+ O/P management. The ideal approach is to use fragmented Adobe form, but the number of fields was not there in the standard service interface. So, we opted for the DDIC interface option available in ‘Assign Form Templates’.

Challenge: To achieve this requirement, I had faced a couple of challenges:

Spool request could not be found - APOC_OR_MESSAGES (145): Discussed in this blog.
Dump - /BOBF/CX_FRW_FATAL – CLASS CL_APOC_OR_A_ITEM_GET_DOCUMENT: Create a Z* Driver program for the form individually and check the issue there – for my case, ADS Configuration was the issue, handled by me and basis tech guy
Bar code center alignment: Centre Alignment of BARCODE blog.

In this blog post we will cover the steps to print GR Label and handle Spool request could not be found - APOC_OR_MESSAGES (145).

MAIN CONTENT:

Firstly, get the name of the standard program – subroutine (Form routine) that you would be triggered in the back-end from the business process. You can later, choose any other sub-routine as well, if that one has better parameters as per your requirement. Make sure the sub-routine you are choosing has *PDF or ADOBE* naming pattern to have the FP_JOB_OPEN/CLOSE else you must manually change the printout subroutine.

** In my case, I have used Program – SAPM07DR, Routine - ENTRY_WE03_PDF.

2. Create an executable report ZAB_IM_SAPM07DR replicating subroutine-pool SAPM07DR, Includes ZIN_IM_M07DRTOP, ZIN_IM_M07DRSON_PDF from M07DRTOP, M07DRSON_PDF resp. and replace the std. includes with them in program ZAB_IM_SAPM07DR.

3. Go to SFP, create a DDIC interface as per the parameters exported in the sub-routine, handle the required processing logic, and create the required layout in ADOBE form to the interface.

4. Point of solution: In the subroutine, FORM_OPEN_PDF, just before FP_JOB_OPEN – handle the output parameters as below, as per SAP KBA 3016791 - Error 'Spool request could not be found.':

  gs_outputparams-getpdf   = abap_false.
  gs_outputparams-reqnew   = abap_true.
  gs_outputparams-covtitle = nast-tdcovtitle.
  gs_outputparams-nodialog = abap_true.
  gs_outputparams-preview  = abap_false.

Activate the program.

5. Share the name to functional or manage it in SPRO.

Application Area: 'Cross-Application Components'

Sub Application Area: 'Output Control'

Select the configuration step 'Assign Form Templates' (SSCUI 102313)

Maintain

(Don’t forget to transport the config data with customizing transport in testing client – Tcode SCC1).

Now functional will go to transaction OPD or below process, that will trigger Fiori launchpad.

And edit the entry for the configured form under ‘Form Template’ for Rules for ‘GOODS_MOVEMENT’ replacing the standard form and activate it.

Outcome:

Now create a document in the test client for Material document and go to MIGO, enter MBLNR -> output-> Display Outputs.

Enter a row with Preparation status & and details as per configuration.

Select the row and click Display document (pdf icon)

GR_LABEL - Z*FORM*

Reference links:

2736938 - Settings for processing program and form templates in billing document in new output management

2294198 - SAP S/4HANA output control - customized forms

2608890 - Standard S/4HANA Output Control settings for Purchasing (output forms and processing programs)

Topic page:

ABAP Topic: https://community.sap.com/topics/abap,

post and answer questions https://answers.sap.com/tags/833755570260738661924709785639136.

Follow me at Robin Thakral

IDOC Configuration for Sales Order via New Output Management

2023-05-16T10:08:34+02:00

In this blog I would like to share my knowledge and learning for triggering IDOCs for Sales Order using BRF+ OPD concept.

The document will focus on following points

Configuring Output type

Configuring Output type for Sales Order in OPD

Required Custom Code Changes

Mandatory system configuration

Debugging hints

Configuration steps for creating Z Output type

SPRO->Cross-Application Components->Output Control

Define Output Type

2.Assign Output Channels

Configuration steps for Output Type via transaction code OPD.

1. Run transaction OPD, Select Determination Step as Output Type

2. Determination Step: Receiver

3. Determination Step: Channel

4. Determination step: Output Relevance

Output Relevance is based on the business requirement, but entry must exist in this step.

If there is no specific business requirement, we can create it with generic condition like Overall Header = C (as mentioned in above screenshot).

Output type is attached to Sales Order once above steps are complete.

To enable new output management for sales order we need to activate it using following SPRO steps

SPRO->Cross-Application Components->Output Control->Manage Application Object Type Activation

Mark status as Application Active for Sales Document.

Custom Code Changes

At the time of defining Output Type, we can add a Z callback class. Create a Class by coyping standard class CL_SD_SLS_OUTPUT and add same under Z Output Type

In case of IDOC we need to modify method GET_LEGACY_DATA of class ZCL_CL_SD_SLS_OUTPUT

ET_LEGACY_DATA should be populated with Z output type.

Mandatory System Configuration

Customizing for SOMU

Check if the Content Repository "SOMU_DB" exists in transaction OAC0.
The recommendation is the following:
Description: Output Management DB Storage
Storage type: SAP System Database
Storage subtype: Normal
Version: 0047
Content table: SFORM_A_STORAGE

Check if the Content Repository "SOMU_DB" is assigned to Category "SOMU" in transaction OACT.

Refer Note 2279725 for more details.

2. Open transaction SBGRFCCONF to check if supervisor destination and Inbound destination is defined or not.

Supervisor destination should exist in SM59.

For detailed steps follow Note 2292571.

Once above steps are followed, it will trigger IDOC for sales order.

Debugging Hints

Following are the debugging points which can be used if trigger output does not work for any reason

First and easiest: Breakpoint at constructor in call back class.

2. Breakpoint at function module APOC_OR_ISSUE_OUTPUT. This will trigger in update task so update breakpoint should be activated first.

I have tried covering all the issues which I have encountered during my Research. Hope it is helpful for you. Happy Learning!!

Syniti RDG provides a new functionality-Importing of UI Field Property Rules by Change Request Step from one change request to another change request.

2023-09-07T11:04:10+02:00

Concento Rapid Data Governance(RDG) is a a SAP endorsed app based on SAP Master Data Governance. SAP Master Data Governance is a powerful solution to improve the quality and consistency of information across organizations by consolidating and centrally governing master data.

This blog illustrates a copy feature in RDG. It involves multiple transactions and steps in SAP application for creating UI field rules in BRF+ and is considered as a complex process. With this feature, we can copy the field property rules from one change request to another change request type by change request step in a single screen.

Below are the steps to copy the field property rules from one change request to another change request by CR step in RDG:

In the main RDG menu, select “Field Property Configuration.”

Users must select the change request type to copy the field property rules from the existing change request type.

Select the “By CR Step Type” option in Select Rule Type dropdown.

After selecting the change request type, the user must select the CR step to copy the rules.

After selecting the CR Step, click on “Import” button to start the process of copying the rules.

After clicking on import button, select the source change request, source change request step and the entities and click on “Save”.

Select the suitable package.

The UI property rules are copied from source cr to target cr .

The copied rule is generated in BRF+ automatically when we do the above process in RDG UI.

Concento RDG is a certified SAP BTP solution and is available on SAP App Store

Your opinions and feedback are highly appreciated, and feel free to post them in the comments section.

Please follow and read more interesting blogs at https://blogs.sap.com

You can also find and post questions about the product here: SAP Master Data Governance Community

MDG-S: MDG rule-based workflow

2023-10-01T11:29:15+02:00

Introduction:

This blog post will describe in detail how to trigger email using using Rule Base Workflow(WS60800086)

Requirement:

Bank data in vendor master data when changed (Account no., IBAN, A/C holder name, etc), or deleted, an email notification to be triggered to the vendor

Email available in the general section of vendor (LFA1) to be used to send the notification.

Email to be triggered to the SPU owners.

Solution:

For this requirement, I have enhanced the existing sub-workflow WS90100004 using transaction SWDD and the step already defined where BRFplus workflow (WS60800086) to call the sub-workflow. I did not pursue the BADI approach. Set up is already there I just enhance the existing subworkflow WS90100004

Steps to be followed:

Tcode: MDGIMG

Based on the CR type check the decision table

Single Value Decision Table

Non-User Agent Decision Table

Sub-workflow WS90100004 Overview

Enhance Subworkflow WS90100004

This WS90100004 workflow has 2 steps added:
- Check for CR Status – Condition steps: Check the status of the CR if status equal = 'AM' (changed by vendor MD team) then trigger email to Vendor and SPU owners
- NOTIFICATION OF BANK ACCOUNT CHANGE – Activity steps: All the ABAP logic ( (Email recipient and email content) placed here in the class /BPMDG/SU_CL_BANK_CHANG_NOTIF and method SEND_NOTIF_BANK_ACCOUNT_CHANGE.
- Workflow End

Created 1 Workflow containers: CR_STATUS

I hope this blog was useful for those of you trying to get email notification configured for MDG.

Syniti RDG provides a new functionality-copying the business rules from one change request to another change request

2024-01-15T16:04:05+01:00

Concento Rapid Data Governance(RDG) is a SAP endorsed app based on Data Governance. It also helps business users to automate many of important steps to implement the MDG.

For example, the user can create different types of business rules effectively to the respective change request in less amount of time. RDG provides a user-friendly interface where all its functionalities would be in a single screen.

In traditional SAP MDG system, the user with low technical knowledge is considered as a high technical task of copying the business rules from one change request to another change request type. RDG is now capable to copy different types of rules in easier way and in less amount of time effectively.

Below are the additional steps to copy the business rules from one change request to another change request in RDG:

In the main RDG menu, select “Manage Business Rules”.

Select change request type to which user want to copy the business rules from existing change request type.

After selecting the change request type, click on import button to copy the rules.

After selecting the existing change request type, the different types of business rules present in that change request can be seen. Then we have to select the rules which we want to copy to the current change request type and click on save button.

A status window will be popped up by displaying the status of business rules.

The rules which we selected are copied from existing change request to current change request and got generated automatically in Business Rule Framework Plus to respective change request type.

Below are the some standard screens related to brf+ where the copied rules generated automatically.

Concento RDG is certified SAP BTP solution and is available on SAP App Store

MDG DQM: Troubleshooting DQM validation rules for central governance - Product Master S/4 HANA

2024-01-30T16:03:50.529000+01:00

Hi All,

Season's greetings!!

In 2023 I focussed on sharing my insights on the data quality management module of SAP Master Data Governance through multiple blogs( "as if it was used be called in the old website"). If you have missed some of these then here is a quick link to all of the content published earlier.

As I start 2024, I have delved a little deeper into this topic and with the new community platform launched, I was excited to share some of the insights from SAP Master Data Governance data quality management on this new platform.

So without further Adieu let's dive in !!

INTRODUCTION

In this blog post we will cover a few steps on how we can troubleshoot the BRF+ validations which is the underlying framework for MDG DQM. This module of MDG is still evolving rapidly as we move towards cloud first and a clean core approach. As MDG developers we are still pretty comfortable with classical BADI's for doing validations and we all know it's quite easy to troubleshoot the rules. But when it comes to DQM we might wonder how do my rules get called? how can i troubleshoot my rules if they are not working as expected?

So let's see how we can troubleshoot the rules.

MAIN CONTENT

DQM rules will be triggered when we click the check button on our MDG UI.
Once click on check the MDQ adapter CL_MDQ_COMMON_ADAPTER_PROD class will be called which will in turn call the MDQ rule engine class CL_MDQ_RULE_ENGINE_CHECK.
This rule engine check method will internally call many other methods and one of the methods which gets called is CL_MDQ_BRFPLUS_HANDLER, this class is responsible for executing the BRF+ functions by calling other standard methods. In this class, we can put a breakpoint in the execute_function method.
Inside execute_function we will find an FDT method which processes the BRF+ function.
Inside the process method, we will get the class name associated with the BRF function ID.
Using this class name we will call the process_dynamic method of the FDT.
Inside this method look for the process_pure method which will have the entire BRF+ generated code for a rule which you have created in DQM.

By following these steps you can easily navigate through the DQM validation rule framework troubleshoot your rules and make sure they are working perfectly fine.

Scenarios which need troubleshooting:

1. You import your rule from one system to another, the rule is approved and enabled for check-in change requests but still doesn't work.

2. You modified your BRF+ logic as per your requirements after the initial build, however, the latest rules don't reflect this.

System details:

S/4 HANA 2023 FPS00.

CONCLUSION

By following the above steps you will be easily able to troubleshoot DQM rules for SAP Master Data Governance central governance.

Hope you find this information useful.

Regards

Anirban

Business Rule Framework Plus(BRF+)

2024-04-16T12:38:55.042000+02:00

What is BRF Plus? Why we need to use BRF+ ?

There will always be some amount of custom business logic available in the SAP system, even if we strive to minimize customization. Such ABAP-based customization must be handled carefully in order to prevent duplication of business logic and to keep it in line with other functional areas. Herein lies the value of SAP Business Rules Framework Plus (BRF Plus), a feature that enables centralized and reusable management of all custom business logic.

In general, BRF Plus features can be accessed on any SAP NetWeaver-based system with the relevant enhancement pack installed.

Both technical users (programmers, system administrators) and business users who manage operational business processes (like bidding, procurement, tax form validation, etc.) can benefit from BRF Plus's unified modeling and run-time environment for business rules.

The application programming interface and user interface that BRF+, or Business Rule Framework Plus, offers is extensive for defining business rules. We can define business rules with it without having to write ABAP code.

Application : In BRF+, to start anything first we must have to create the application.

Type of Storage Types :

Storage Type	Client	Transport Request	Cross-Application Usage
System	Client-Independent	Transportable or Local	Can use system objects.
Customizing	Client-Dependent	Transportable or Local	Can use system and customizing objects
Master Data	Client-Dependent	Local	Can use system, customizing, and master data objects

Data Objects: Describes data types of the variable. They are the data carriers helping in signature or context of a function, variables in a rule or rulesets, building blocks for Decision tables, Etc. You can create data objects by defining attributes like element type, length, decimals or you can directly bind to existing DDIC elements.

Expressions: Expressions are the computational units with well-defined logic. Usually, expressions are self-sustained and process the user input and gives result back to the caller.

Rules: Rule is a central entity in BRF+ which builds the business logic. Evaluation of rule gives you the decision for the question in context

Rule sets: Simply, collection of rules. Each rule set can be assigned to exactly one function. Priority can be set at rule set level for defining the order of execution.

To Create Application : BRF+ or BRFPLUS is the transaction code to access the application.

Next, we click the Create Application Pushbutton. Below Pop-up will opened up and enter the required fields.Click on Create and Navigate To Object after filling out Name, Short Text, Text, and Development Package for Software Component. Another option is to store in the Temporary($tmp) Package.
Next, we'll press the "Save & Activate" button.

Next, within this application, we will talk about the following elements.
1. Create an element in the data object.
2. Create a structure in the data object.
3. Make a Table Data Object
4. Produce a Decision Table Expression

There are 3 ways to bind the data object in Binding Type :

Create an element in the data object : The following steps are shown in the figure below after you right-click on the application: After completing all the required fields, we will click the designated button.

There are three options under this option, which is called Binding type.
Bind to DDIC Element: Select a DDIC Element that shares your attributes.

Bind to an Existing BRF+ Element: Select an Existing BRF+ Element that possesses the same attributes.

No Binding: Maintain the details freely.
Therefore, in this case, if we select any of the first two options 1 or 2 Name, Text, Element Length, and Element Type will be automatically filled in from the DDIC element or an already-existing BRF+ element.
However, if we select the No Binding option, we will have to enter all necessary information, including the element name, text, short text, element length, and element type.

After entered all the required fields, click on Create and Navigate To Object button and then click Save & Activate buttons to activate it.

Structure Creation: The same application should be used to create the structure.
It is not necessary to build a structure if our result contains just one column. There is also no need to create a structure if the output for a single condition is a single row. If more than one column appears in our result, we should make a structure with all of those columns. Additionally, a structure must be shown if the output consists of multiple rows. The generated structure must be used to create a table in order to produce multiple rows as output.

To Create a Structure, Select our application and follow the instructions shown in the figure below After that, we must complete the required fields to create the structure. However, before that once more, there is a choice named Binding Type, which has the following options:-

a) Bind to Structure Type (DDIC)
b) No Binding
c) Binding to CDS View: Not to be used

For Option a & c, The required fields (Name, Short Text, Text) will automatically be filled in from the DDIC structure or the CDS View.
However, if we select option b, which is No Binding, we will have to manually fill in every required field.

Once all of these have been filled out, click Create And Navigate To Object, and lastly Save and Activate this structure.

Table Creation: In order to have multiple result rows based on a single condition in our decision table, we can create a table in the same application. Therefore, table creation is necessary in our case.
Select our application, then follow the instructions shown in the figure below.After that, fill out the fields required to create the table. We must first verify the Binding Type.
There are two options for creating tables in Binding Type:
a) No Binding
b) Binding to Table Type (DDIC)

If we select option b "Binding to Table Type (DDIC)" All required fields (Name, Short Text, Text, Table Line Type) from the DDIC Table Type are automatically filled.
If we select option a "No Binding" then it will have to manually fill out all required fields.
Therefore, choose Table line from the application in order to display Multiple Rows. Once all required fields have been filled out, click Create And Navigate To Object, and then save and activate this table.

Decision Table Creation :
The next important step is to construct our Decision Table using our application as well. Select the Decision Table and follow the steps outlined in the figure below.

Once Name, Short Text, and Text are entered, click on the Highlighted button.In the table settings, we can do the below enablement.

There is a checkbox labeled "Return all matches found" in Settings. If we don't select this option, even though multiple rows may exist based on the same condition, only one row will ever display for that condition.
Select the Result Data Object located in the same application as our recently created Table. Next, include the Condition Column.
Select the Application Data Element's Column:

To Select an object as the Condition Column, select it and then click OK. Declare a field as required in the condition column, indicating which column's value will be used to retrieve the value of the result columns.
Thus, the Condition Column's input needs to be required and selected columns comes as result.Select these components from the table.Click OK once all of the table's objects have been selected.Click the OK button to proceed. All of the selected columns now appear as Result Columns.
Save and Activate all Decision Table modifications after adding Table Contents. Now update this Decision Table with the Table Contents and Next, select "Start Simulation" to see if our decision table functions.

After entering the program name, select Execute. Will get the matched records as output.

Use of Decision Table in ABAP Program: In order to obtain the required output rows, we must now use our Decision Table in an ABAP program and pass the condition column value from the program.
In the same application, a function must be created for that.

Function Creation: To begin, right-click on the application, then follow the instructions in the figure below.

After entering the Name, Short Text, and text, press the Create and Navigate To Object button.
Next, fill in the remaining necessary fields, as indicated in the figure belowSelect our created Decision Table in Expression and Mode as Functional Mode. Next, select the Data Element for the Condition Column and the Table of Result Columns after adding the Context from existing Data Object. Next, select our result columns, which are tables from the same application that we created, under Result Data Object then save and activate every modification.

After that, we must select Create Code Template, copy the sample code, and utilize it in our ABAP programAt last, we need to save and apply all of the modifications. Following the use of this template in an ABAP program, all of the resultant columns and expected result values should appear in the program.

Rules and RuleSets : It contains set of rules which can be executed as soon as our BRF+ application Function is getting executed. Rules must be contained in the ruleset, as expressions (IF-THEN-ELSE logic). If-THEN rules are another name for plain rules.
A ruleset is an assemblage of rules. Select Event Mode by default. The Assign Ruleset option is under Event Mode. The function must then be given a ruleset. Please select the "Create Ruleset" button after selecting the "Assigned Rulesets" tab in the screenshot above. After giving the new ruleset a name, the screen below will appear. Following the creation of the ruleset, fill in the Name, Short Text, and Text fields. Then, click the Create and Navigate To Object button below.

Save and Activate the Ruleset function.
Next, utilize this ruleset in ABAP code from the function using the Code Generation Template.

Decision Tree: A binary tree of expressions can be defined using a decision tree expression. Condition Nodes are non-leaf nodes. The result is a Boolean. Left & Right nodes will move forward in accordance with the outcome. When a leaf node is reached, the designated expression is executed, and the result of the entire expression is returned as the corresponding result. A decision tree has two nodes at all times: left and right. Every node has decisions that are True (Yes) or False (No). Depending on that new branches (nodes) will proceed.

We can define business rules using the BRF+ interface without having to write ABAP code. These generated business rules can be used as substitution/validation rules or integrated into other SAP programs.

Use cases of BRF+ that can be used into S4HANA:
Output management for Billing and Purchasing – Output determination (SAP S/4HANA).
Integration with IMG transaction.
SAP business Workflows.
Cloud based Environment.

Conclusion on BRF+ :

It enables us to represent rules in an understandable manner and apply them again in various contexts.
BRF+ eliminates the need to create and maintain custom tables for validation. It also does away with the traditional developer approach of hardcoding values.
In essence, BRF+ is used to make decisions, and decision input and output values are kept up to date in Decision Tables, which have sophisticated validation features.

Roles that are required
SAP_BC_FDT_ADMINISTRATOR
WD Configuration :
/sap/bc/webdynpro/sap/fdt_wd_workbench
/sap/bc/webdynpro/sap/fdt_wd_object_manager
/sap/bc/webdynpro/sap/fdt_wd_catalog_browser