How does SAP MDG prevent the same object from being processed in different change requests?

When an object is assigned to a change request in SAP Master Data Governance (MDG), it is locked to prevent it from being processed in any other concurrent change request. This locking mechanism is essential for maintaining data integrity and ensuring that no conflicting updates occur simultaneously. This means that during the time the object remains locked, other change requests that attempt to modify or interact with the same object will be unable to proceed.

This approach helps maintain a clear and controlled environment for managing changes, allowing only one change process to be executed at any given time for that specific object, thus avoiding inconsistencies and enabling better tracking of modifications.

In contrast, marking an object as inactive or requiring supervisor approval does not inherently prevent concurrent processing; these options focus on governance and approval workflows but do not enforce locking at the data level. The automatic rejection of change requests does not apply in this context, as the goal is to manage changes while allowing for the potential of future processes once the object is unlocked.