Conflict Handling 
Use
A configuration conflict is an inconsistency in the configuration process of a configurable product, a contradiction that arises during the configuration process.
For example, when configuring a car, a conflict arises if you select a sunroof for a convertible.
The function supports especially the occasional user of the interactive configuration, both with analysing and solving occurring configuration conflicts.
Conflict handling allows the planning of particular conflicts, which, during the interactive configuration, provide the user with deeper insights into and more information about the configurable product.
As a rule, configuration models should be constructed conflict-free. However, this may be hard or even impossible to do. Sometimes, it may even offer advantages to allow a conflict and use it to explain to the user of the interactive configuration in detail, why certain product options (characteristic values) are incompatible, and thus to provide the user with more information about the configurable product.
Conflict handling enables you to anticipate typical conflict situations for each product and to intentionally allow them in the configuration, either to simplify the model or to explicitly provide background information.
Conflict handling is no substitute for good modeling – on the contrary, if you use conflicts as a modeling instrument, you must adhere to certain basic modeling rules.
Integration
You use conflict handling in the interactive configuration of Web-based IPC scenarios, such as Internet Sales.
The product configuration area in the Mobile Sales scenarios provides extensive analysis tools that allow experienced users to intensively analyse configuration conflicts of any complexity level, including complex product models.
This documentation describes how the occasional user of Web scenarios can use conflict handling.
Prerequisites
· Conflict handling and its functionality is activated for interactive configuration on your Web-based user interface.
In the customizing, you can explicitly activate or deactivate the various functions for conflict handling. For more information, see IPC Configuration Support on the SAP Service Marketplace.
· The product model on hand must be of type easily configurable product.
· The used dependency refers exclusively to the root object. You may use dependencies that copy characteristics to class node components.
· Selection of components via dependency and procedural dependencies are not used.
Features
Conflict Analysis
The occurring conflicts are analysed in two different ways, syntactically and semantically. These analyses are the basis for conflict handling in the Web scenarios.
Mobile Sales scenarios support only syntactical analysis.
See
Conflict Handling
In case a conflict occurs in the interactive configuration, the conflicting options and characteristics are highlighted. The user of the interactive configuration can solve the conflict by deselecting some of the options selected during the configuration.
· Web scenario: The occasional user of the interactive configuration can achieve a conflict solution with the help of a comprehensible presentation of the conflict analysis on the Conflict Handling screen.
· Mobile Salesscenario: The experienced user of the Sales Configuration Engine can view the detailed results of the conflict analysis to achieve a conflict solution.
See
Conflict Handling in the Interactive Configuration
Shortened Conflict Handling (Web Scenario)
In certain conflicts, the Option Selection screen can offer a shortened conflict handling version, which recommends that the user accepts an automatically set option in favor of an option selected by the user. If the user accepts this proposal, the conflict is immediately solved and the configuration can proceed without a screen change.
See
Shortened Conflict Handling (JSP UI)
Activities
An intelligent usage of the conflict handling requires planning of the conflicts as early as in the modeling stage. There are different types of conflicts, some of which can be handled differently.
See