I am working on a project site with NetWeaver 7.31 SP06.
And I have a question about BRM and I think you can give me the solution or idea.
When we develop rules with rules composer, we write rules with values by hard cording.
For example, there are two decision tables like below
DecisionTable 1
-----------------------------------------------------------------------------------------------
condition : action
-----------------------------------------------------------------------------------------------
Customer Type : Bonus Point
-----------------------------------------------------------------------------------------------
C01 : 500
C02 : 1000
C03 : 1500
------------------------------------------------------------------------------------------------
DecisionTable 2
-----------------------------------------------------------------------------------------------
condition : action
-----------------------------------------------------------------------------------------------
Customer Type : Bonus Point
-----------------------------------------------------------------------------------------------
Normal Customer : 500
Important Customer : 1000
Very Important Customer : 1500
------------------------------------------------------------------------------------------------
For business manager who manages this rule with rules manager, decision table 2 is better than decision table 1 because description value is better to understand than code value.
But, if the code value changes, rule also should be changed with rules composer or rulesmanager.
If there are many rules using this code, it could be a big burden.
In our case, most of these code values are defined in abap domian type.
So, when UI(WDJ) application or BPM calls the rule, UI or BPM send codes as rule input paramters.
Here is my question.
Is there any way to use abap domain type as enumeration type in rules composer ?
I think If we can use abap domain type as enumeration type in rules composer, the problem which I described above could be cleared.