Editing expressions in non-development systems.

Question

Our first use of BRF+ met a large success among our business key users and  they are requesting now the maintenance of some decision tables.
We therefore followed the guidelines of document "editing BRF+ component in non-development systems" and implemented interface IF_FDT_APPLICATION_SETTINGS.
All went fine on this part, but we hit major troubles with the authorization parts.
Due to the fact that our application was defined as 'customizing', we keep having message "System settings do not allow changes for customizing objects" and asks for authorization object S_TRANSPRT in production.
Having the application set to 'customizing' was not the best idea, as all objects created afterwards inherited automatically from this property.
Is there any way to force the status of specific expressions (not all at it would not make sense) from customizing to master data ?

Answer 1

As Christian explained you may split your use case in two applications.
I anyway recommend for bigger use cass to put function and (shared) data objects into a system application and rules into a customizing application. In scenarios where you frequently need to change rules you can also use a master data application, not only customizing.
However, we have seen several issues with customers changing rules in the productive system (be it master data or be it customizing with the application exit). The problems are
missing checks for activation of changes (although customers could implement exist for any specific checks they want)
conflicts with imports (again, customers could implement custom code in exits to prevent some of the issues)
missing activation workflow (also here custom solutions may help)
times where BRFplus may fall back into interpretation mode because of changes happening in parallel
As a consequence I generally do not recommend changing rules in productive systems directly. Instead my recommendation is NW Decision Service Management which provides you all the tools to perform your changes, test them, deploy (with or without release workflow) and use them (always generated code).
- Features of DSM