Using SAP DSM to deploy rules/maintain decision table changes into Production.

[Tush_30]

Hi Experts,

I understand that we can use DSM to do hot deployment to Production if we want to give business users the ability to make changes in decision tables.

By this approach, my concern is the following:

1. In order for business users to make changes in decision tables, this can be done from DEV environment and then do a hot deploy to PROD so those changes are immediately available in Prod (DSM config will be an RFC from DEV to Prod.. correct?) . In doing this approach, are we not running a risk of breaking PROD if something goes wrong?

Can I get some thoughts on how can we still use DSM to deploy the rules in PROD from DEV(or any suggestion) in a more controlled way? How do we keep all the systems in sync?? The requirement is to business users the ability to change a boolean to true or false in a decision table without the interversion of a developer and TMS.

OR: Anyone can suggest how this can be achieved using DSM?

PS: We do not want to do XML upload or download using type MASTER DATA.

Our current landscape is:

1. ECC(DSM Installed)

2. BW

Rules to be deployed in BW(Target system)

Thank you.

TM

[christianlechne · Accepted solution]

Hi Tush,

SAP Decision Service Management follows the "philosophy" that you model your rules in your DSM system. As the system is connected to all managed systems via RFC this allows you to access data from any of these systems to model, but also to test your rules and simulate the execution in a managed system.

The approach would therefore be:

• Model your rules in your DSM System
• When finished test your rules by executing them in simulation mode on a managed system
• When the tests are successful, deploy the rules to your productive system

This is the safest way to deploy rules directly to production as you can test/simulate them in the system you deploy to. This is not possible via BRFplus alone or the mechanisms you mentioned

You also have you test case management in DSM, in order to make sure that future changes do not break the existing code.

In case everything goes wrong you also have the option to delete the service deployment which switches back to the prior version of the deployed service (if there is one)

So summing up: using DSM is the safest way to deploy the app. The safety net is as usual test cases that with DSM can be executed in simulation mode on PROD, which should show you if your rules break something or not.

BR

Christian