Scribd
Upload
10 views1 page

Add Cus Fields

Uploaded by

Moorthy Esakky
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
10 views1 page

Add Cus Fields

Uploaded by

Moorthy Esakky
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

To add custom fields to the BRF+ application, specifically to the process_POB decision table in SAP BRIM, you generally

need to
follow these steps:

1. Enhance the Underlying Data Structure


You must extend the DDIC structure that the decision table uses as its context or parameter structure. For example, in
OPD (Output Parameter Determination) scenarios, the standard structure like S_APPL_PARAMETER pointing to a CDS
consumption view (e.g., C_BILLINGDOCUMENTOMPARAMDET) can be extended by creating a new CDS view extension
that adds your custom fields. This extended structure will then be available for use in the decision table

2. Refresh the Binding in BRF+


After enhancing the DDIC structure, go to the BRF+ application and refresh the binding of the decision table to the
updated structure. This will allow you to add the new custom fields as columns in the decision table via the table settings
(Insert Column from Data Object)[2].

3. Add Custom Fields to Decision Table Columns


Once the binding is refreshed, you can add your custom fields as input or output columns in the decision table. This step is
necessary to make your fields available for rule evaluation and decision logic[3][2].

4. Handle Transient Data for Custom Fields


If your custom fields require calculations or data that is not directly available in the standard transient data, you may need
to enhance or create an exit or helper class method (e.g., GET_TRANSIENT_DATA_BRF in
CL_FDP_V3_BD_TRANS_DATA_HELPER) to populate these fields before the decision table logic runs[1].

5. Activate and Test the BRF+ Application


After adding the fields and updating the decision table, activate the BRF+ application and test the process to ensure your
custom fields are correctly considered in the decision logic.

Additional Notes:

 The CDS view extension should be of the consumption type and can be annotated with VDM.viewExtension : true to
support further extensions.

 If you are working within the Output Parameter Determination (OPD) framework, ensure your custom fields are also
integrated there for full processing

 For release strategy or workflow scenarios, you may need to map BRF+ functions to characteristics and classes accordingly

In summary, the key is to extend the underlying data structure (usually via CDS view extension), refresh the BRF+ decision table
bindings, add the custom fields as columns, and handle any required data population via exits or helper methods before the BRF+
logic executes.

This approach is confirmed by SAP community discussions and technical blogs where users have successfully added custom fields

to BRF+ decision tables by enhancing CDS views and structures, refreshing bindings, and implementing necessary data

provisioning logic.

You might also like