Hello All,
For this particular issue there was a code bug in a part of generated code of decision table. The issue was solved in note 1669944. I have suggested this note in the OSS message raised for this issue. Still waiting for a confirmation on whether the issue is resolved.
Thanks,
Anindya
