How to prevent number range object NRIV from being transported

[sanjay_ram]

Hi,

There is a problem in our landscape that some naive users are transporting number range table NRIV to production.

May i know how can we set that such important tables cannot be included in a transport? If they deliberately try to create a transport on this table, the system should not allow them to do so.

Is there a way to lock such tables from being transported?

[JL23]

why do so naive users get the authority?

[sanjay_ram]

Good question, they are naive consultants to be exact. When they create a new plant, somehow the number range object is also transported.

[JL23]

This does no explain why they have authority...

We used to follow a 4 eye principle, a basis consultant together with a functional. The functional had no authority to maintain number ranges, only the basis consultant could. They had to sit together to maintain number ranges.

Did not really work out well as we are too much distributed location wise. now we are back to have number range maintenance only allowed for long term experienced.

You actually get a pop-up that number ranges are not included into a transport with a longer description of the why and the consultant has to add it manually to a transport. So it usually can't happen by inattention.

[sanjay_ram]

Well SAP being a powerful system, isn't there a locking functionality where we can just lock certain tables preventing them to be included in a transport?