Hi Mayank
I'm glad to hear that you have a working solution but I still get the feeling that this could have been achieved using the decision table condition functionality rather than just using the decision table for data storage only.
If you're happy to leave it there then so am I but if you want to continue the discussion then I have more comments/questions... (I won't be offended if you decide to close this thread. 
)
Comments/questions:
You agree, above, that the decision table rows "should be in an order such that the most precise rules take preference" but the only way to do this is to reorder your decision table rows so that your row 2 (more specific) becomes row 1 (more generic) and vice versa. You said that "the functional users do not want to update the rule sets and want to use the same rules in BRF+". Does this mean that the users don't want the decision table rows reordered? If not. why not? Is there a technical reason for this?
Regards
Glen