Can we change the contents of a decision table in the situation that the client is set to "No changes allowed" in t-code SCC4?

[former_member561151]

Dear Guys,

Can we change the contents of a decision table in the situation that the client is set to "No changes allowed" in t-code SCC4?

Details explanation:

As we know, in the t-code SCC4, we can maintain the attributes for the clients. If it's a production system, usually it's maintained as below.

I have one decision table which just contains the e-mail address for different company codes. I use it for sending the informing e-mail to the right person according to company code. Sometimes, the e-mail should be updated as the person has been changed. We would like to maintain the e-mail address directly in production system, not by transporting change request. Another reason is that, I don't want to keep the contents of this decision table in Dev system and Quality system. As when they do some operation in Dev and Quality system, they will trigger the sending mail which bothers end users.

Can we do that? As I know that even in production system with "No changes allowed" for the client, we still can modify the finincail periods and exchange rate directly, but I'm not sure whether there is some way to allow me to modify the decision table directly.

Thanks in advance!!!

[anbusivam_s]

Hi David,

You can use custom application exit class to override this. An application exit class should be specified at application level and the class should implement interface IF_FDT_APPLICATION_SETTINGS. You need to use method GET_CHANGEABILITY to override the standard system settings.

To know more details about application exit class and how exactly to implement this method kindly refer link: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0852307-7ad7-2d10-dbb7-cb1f0a214...

Also kindly take special care while overriding the default system setting on who & what objects can be modified with proper authority checks.

Note: I assume that your decision table is neither assigned to local package nor belongs to a master data application type. As with either local data or master data type you will already be able to modify the decision table.

With Regards,

Anbusivam S

[carsten_ziegler]

Although technically possible we do not recommend this approach anymore.

The reason is that customers run into problems when the changed object is imported into the productive system again. An import overwrites the changes. For business people it is not possible to understand when an import arrives and overwrites the objects.

Instead, we provide now SAP NetWeaver Decision Service Management as a tool to master all those requirements where changes in one or multiple productive systems are required to be conducted by non-technical people in a save way.