Basis question - Config object locking

[JaanaK]

Hi all Basis gurus out there!

I have the following problem and would appreciate your help.

We created a transport for a configuration object (pricing condition types). When someone made some changes to the same object, the system did not warn that the object was being edited and did not prompt to create a new task under the transport.

This resulted in two separate transports being created for the same object.

Our understanding is that the system should give a warning message and prompt to create a subtask to the transport.

We have been told that transports related to data and views are not usually locked and that customizing does not follow the same locking mechanism as for Workbench transports.

Is this correct?

Many thanks in advance.

Kind regards

Jaana

[Samikhya]

Hi Team

Can any one suggest the best way to avoid these configuration objects getting locked in 2 separate TRs if handled by 2 separate teams ?

Example :-- If team 1 adds some entries and Team 2 deletes then both should go but if the delete one over writes then this will create an issue in PRD.

How can we prevent this from happening in DEV environment itself ?

With Regards

Sami