You can either use the default conflict analysis scenario which is cross-project (project relation Cross
), change type relation Urgent Only
, object type Client-Specific
, or define a specific different scenario in the /TMWFLOW/CONFIG_CSOL
report using the expert mode.
The conflict analysis function differentiates between the following:
Conflicts between transport requests that belong to the same project, and conflicts between transport requests that belong to different projects.
Conflicts for urgent changes, and conflicts between transactions of another type (a conflict between an urgent change and a normal change, or a conflict between normal changes, for example).
Conflicts of the type Customizing
Repository
.
Note
Whether you can continue to change an object depends on the analysis scenario configured and the conflict scenarios involved.
The following list contains descriptions of the different scenarios for the cross-system object lock that you can use. Only conflicts that lead to an error are described. All other conflicts in the scenarios trigger a warning only; the user can decide whether or not to change the object.
Cross-Project, Urgent Only, Cross-Client
If an object conflict arises between urgent changes, the system displays an error and does not allow the user to change the object. This applies only to Repository objects, both within one project and across multiple projects.
Cross-Project, Urgent Only, Client-Specific
If an object conflict arises between urgent changes, the system displays an error and does not allow the user to change the object. This applies to client-specific Customizing, cross-client Customizing and Repository objects, both within one project and across multiple projects.
Cross-Project, Overlapping, Cross-Client
If an object conflict arises between two transport requests for any change type, the system displays an error and does not allow the user to change the object. This applies only to Repository objects, both within one project and across multiple projects.
Cross-Project, Overlapping, Client-Specific
If an object conflict arises between two transport requests and any change type, the system displays an error and does not allow the user to change the object. This applies to client-specific Customizing, cross-client Customizing and Repository objects, both within one project and across multiple projects.
Cross-Project, Partial Overlapping, Client-Specific
If an object conflict arises between two transport requests and at least one of them is an urgent change, the system displays an error and does not allow the user to change the object. This applies to client-specific Customizing, cross-client Customizing, and Repository objects, both within one project and across multiple projects.
Cross-Project, Partial Overlapping, Cross-Client
If an object conflict arises between two transport requests and at least one of them is an urgent change, the system displays an error and does not allow the user to change the object. This applies only to Repository objects, both within one project and across multiple projects.
Project-Specific, Urgent Only, Cross-Client
If an object conflict arises between urgent changes, the system displays an error and does not allow the user to change the object. This applies within one project only, and only for Repository objects.
Project-Specific, Urgent Only, Client-Specific
If an object conflict arises between urgent changes, the system displays an error and does not allow the user to change the object. This applies within one project only, and for client-specific Customizing, cross-client Customizing and Repository objects.
Project-Specific, Partial Overlapping, Cross-Client
If an object conflict arises between two transport requests and at least one of them is an urgent change, the system displays an error and does not allow the user to change the object. This applies within one project only, and only for Repository objects.
Project-Specific, Overlapping, Cross-Client
If an object conflict arises between two transport requests, the system displays an error and does not allow the user to change the object. This applies within one project only, and only for Repository objects.
Project-Specific, Partial Overlapping, Client-Specific
If an object conflict arises between two transport requests and at least one of them is an urgent change, the system displays an error and does not allow the user to change the object. This applies within one project only, and for client-specific Customizing, cross-client Customizing and Repository objects.
Project-Specific, Overlapping, Client-Specific
If an object conflict arises between two transport requests for any change type, the system displays an error and does not allow the user to change the object. This applies within one project only, and for client-specific Customizing, cross-client Customizing and Repository objects.
Different Project, Urgent Only, Cross-Client
If an object conflict arises between urgent changes, the system displays an error and does not allow the user to change the object. This applies to different projects, and only for Repository objects.
Different Project, Urgent Only, Client-Specific
If an object conflict arises between urgent changes, the system displays an error and does not allow the user to change the object. This applies to different projects, and for client-specific Customizing, cross-client Customizing and Repository objects.
Different Project, Partial Overlapping, Cross-Client
If an object conflict arises between two transport requests and at least one of them is an urgent change, the system displays an error and does not allow the user to change the object. This applies to different projects, and only for Repository objects.
Different Project, Overlapping, Cross-Client
If an object conflict arises between two transport requests and no matter what change type they belong to, the system displays an error and does not allow the user to change the object. This applies to different projects, and only for Repository objects.
Different Project, Partial Overlapping, Client-Specific
If an object conflict arises between two transport requests and at least one of them is an urgent change, the system displays an error and does not allow the user to change the object. This applies to different projects, and for client-specific Customizing, cross-client Customizing and Repository objects.
Different Project, Overlapping, Client-Specific
If an object conflict arises between two transport requests and no matter what change type they belong to, the system displays an error and does not allow the user to change the object. This applies to different projects, and for cross-client Customizing and Repository objects.
See the report documentation in /TMWFLOW/CONFIG_CSOL
.