How do you garanti integrity of ESR Content.

[Former Member]

Hi,

suppose you put an interface into production, you want to be sure to keep the ESR content of this interface

unmodified , until you need to change it again ... exp for a bug fix or a new version.

We can put objects non-modifiable in a software component version but then again.. anybody can switch it back to modifiable and make changes.

Basically, you are not garanteed that no one changed the software component since you put it in production.

Is there a best practice to garanti that your ESR content is not modified... can you search who modified a software component version since a certain date...

How do you do it ?

Thanks.

[stefan_grube · Accepted solution]

You can restrict authorization to a software component.

You can see in history who changed the interface last.

But you should change an interface of a collegue without need?

The project owner or team lead has to create rules.

This is the same for any development, like ABAP or Java.

[Former Member · Accepted solution]

Hi Stefen,

it would be great to have history for all elements of a software component at the same time ...

This way , you could see what has changed in the software component since the last release in production.

I'm curious what kind of rules do people use in PI... do you keep a separate file documenting all changes made to a software component ?

Do you have only one person who is allowed to set the objets to modifiable.

Thanks.