Controlling Implicit Enhancements versus Modifications.

[Former Member]

Hi All,

I would appreciate any help/views on the following question/issue.

We have a relative big development team. And previously we managed modifications by only allowing the SAP manager and team leads (with the correct sign-off docs) to get object keys to allow for modifications. (As this obviously impacted on SAP support)

I have a relative good overview of the new enhancement framework.

But now with implicit enhancements there is no way of stopping any developer from changing almost any standard code. (And this is an issue as some developers are a cowboy breed by default) As there are no authorization objects differentiating between implicit and explicit enhancements, it can't be controlled by authorizations. I also assume this will be seen by SAP in the same way as a mod, resulting in any future problems with the standard program/function to become a consulting issue. (thus no standard support) How do you people go about this?

-

---

And secondly, are there any tool (not se80 or se20) to see all implicit enhancements made, other that looking at table ENHCROSS?

Thanks in advance.

[Former Member]

Hi All,

I would appreciate any help/views on the following question/issue.

We have a relative big development team. And previously we managed modifications by only allowing the SAP manager and team leads (with the correct sign-off docs) to get object keys to allow for modifications. (As this obviously impacted on SAP support)

I have a relative good overview of the new enhancement framework.

But now with implicit enhancements there is no way of stopping any developer from changing almost any standard code. (And this is an issue as some developers are a cowboy breed by default) As there are no authorization objects differentiating between implicit and explicit enhancements, it can't be controlled by authorizations. I also assume this will be seen by SAP in the same way as a mod, resulting in any future problems with the standard program/function to become a consulting issue. (thus no standard support) How do you people go about this?

-

---

And secondly, are there any tool (not se80 or se20) to see all implicit enhancements made, other that looking at table ENHCROSS?

Thanks in advance.

[Former Member]

Although, there is no control on implementing implicit enhancements, these reside in customer namespace.This is what makes it different from modification.

What is the need of stopping the developer from implementing these enhancements?

are there any tool (not se80 or se20) to see all implicit enhancements made, other that looking at table ENHCROSS?

SE80-> package-> enhancements.

This will provide all the implementations(residing in this package) done for the enhancements.

G@urav.

[Former Member]

Hi Gaurav,

Thanks for your reply.

>

> What is the need of stopping the developer from implementing these enhancements?
> 

I'll answer with a question: Why do SAP require a key to make a modification?

>

> SE80-> package-> enhancements.
> This will provide all the implementations(residing in this package) done for the enhancements.
>

(not se80 or se20)

I know of this. But not what I want.

I only want to see all the implicit enhancements in the customer namespace.

[Former Member]

I understand your requirement...

SAP asks for a key for modification..if not asked we all can imagine our system open for all to play

Let us compare it with prior enhancement options like CMOD or BADI. Anybody can implement it and change the flow of transaction. There also we need to have track of active implementations existing in the system. Similar is the case with enhancement framework.

Additionally,it is saving us from upgrade issues by powering us to have our custom code in standard programs without modification.

Not sure if we can see only implicit enhancement implementations... have you tried SPAU_ENH?

G@urav.

[mvoros]

Hi,

I really understand your worries about this issue. I was thinking about security implications of new enhancement framework for a long time. As you mentioned with this new powerful framework every developer can change almost everything.

Definitely with new SAP systems QA checks for each transport have to performed. Someone with responsibility should check and review each transport for all enhancements. I know that sometimes this is not possible, very often developers have authorization to release transport directly to QA. So my idea is to implement method CHECK_BEFORE_RELEASE of BADI CTS_REQUEST_CHECK. It will check if a transport contains any implicit enhancement. If yes you can log it somewhere or not allowed to release transport without approval from team lead. But to fight against developer on DEV system is really hard. Usually developer on DEV can use debugger and rewrite variables in it so he can easily go over any check. Sometimes developer are not allowed to rewrite variables in debugger on QA system. Therefore implementing this check before release to Production system will help.

Cheers

[Former Member]

>

>So my idea is to implement method CHECK_BEFORE_RELEASE of BADI CTS_REQUEST_CHECK. It will check if a transport contains any implicit enhancement. If yes you can log it somewhere or not allowed to release transport without approval from team lead. But to fight against developer on DEV system is really hard. Usually developer on DEV can use debugger and rewrite variables in it so he can easily go over any check.
>

Hi Martin,

Thanks for this, I was thinking along the same lines, but didn't have the details yet.

You might consider putting this in a macro (with editor lock enabled), thus stopping anybody from manipulating the variables or even the code as this check will be needed in Development.