Conflict Management in Database Update New from DB 39.5.14

Information

• In database update, each individual customizing adjustment made to a standard object in the customer’s PLANTA system leads to a conflict which must be resolved.
• With the help of the new conflict management procedure, such conflicts can be found, checked, and resolved by applying individual adjustments or new changes made to the standard. Furthermore it is possible to configure the found conflicts in a way that they automatically adapt individual changes in the next update. The conflicts in question are then automatically marked as resolved.
• The conflict management procedure replaces the previously required individual ICOU, which had to be written and carried out manually after each update. The new procedure therefore allows for faster and cleaner database updates.

Tracking Changes Made to Standard Objects (Conflicts)

Information

• In order to identify individual adjustments to PLANTA standard objects which lead to conflicts in database update, the files from three database statuses are compared:
  • The state of the customer with its individual adjustments
  • The reference state, i.e. a PLANTA Standard system with the same DB version as used by the customer
  • The state of the new PLANTA Stamdard customizing to which you want to update
• This results in an automatically generated ICOU which lists all individual adjustments made to standard objects per data table. These conflicts must now be checked and resolved manually. For more information on this subject, see the following chapter.

Notes

• In updates from a DB release > DB 39.5.14 to a later release, conflicts are automatically identified in database updates without any action being required on the part of the person who initiated the update.
• When updating from a DB release earlier than < DB 39.5.14 to DB 39.5.14 or later, manual action is required to identify conflicts. The appropriate reference status for the system must be imported.
  • The reference states are made available by PLANTA.

Conflict Solution

Information

• PLANTA provides a special conflict module, designed for checking and resolving identified conflicts:
  • one conflict module each per data table,
  • a collective Conflicts module, in which all conflicts of all databases can be displayed and all already configured conflicts can be resolved at once.
• You configure a conflict by selecting one of the proposed solutions.
• You solve a conflict by applying the selected solution.
  • If the conflict management procedure is used in an update for the first time, all found conflicts must be checked, configured and resolved by clicking on the buttons in the respective module.
  • When you use conflict management for the first time, you can determine how the conflicts will be treated in the next update by configuring the conflicts. By selecting an option, you can define that individual adjustments are automatically applied in any further update, so that the position in question is treated as a resolved conflict from te beginning without any action being required on the part of the person who carries out the update. Apart from these automatic conflict solutions, new conflicts can be identified in any further update, which will then be checked, configured, and resolved as well.

Note

• If the individual adjustment equates to the new PLANTA Standard, the conflict is marked by the conflict management procedure as resolved.