Question & Answer
Question
Stale vs Conflict Item State
Answer
Stale State 
- If the conflict feature is not enabled, user's edited item can be in the Stale state when changes are not committed or another user-committed changes first. User must revert their changes to the item. User can save the item notes if they go ahead with the revert option.
- If the conflict feature is not enabled, user's edited item can be in the Stale state when changes are not committed or another user-committed changes first. User must revert their changes to the item. User can save the item notes if they go ahead with the revert option.Conflict State 
- Item conflict is a state items go into rather than stale when the conflict feature is enabled. A Conflict state occurs when user changes an item without committing it, and another user changes that item and commits it first. An item can also be in conflict when the base record is modified by the host ERP after a refresh. An item that is in a conflict state is removed from the workflow approval process and cannot be approved. User can either revert or resolve your changes to the edited item that is in the conflict state. User can save the item notes if you go ahead with the revert option.
- Item conflict is a state items go into rather than stale when the conflict feature is enabled. A Conflict state occurs when user changes an item without committing it, and another user changes that item and commits it first. An item can also be in conflict when the base record is modified by the host ERP after a refresh. An item that is in a conflict state is removed from the workflow approval process and cannot be approved. User can either revert or resolve your changes to the edited item that is in the conflict state. User can save the item notes if you go ahead with the revert option.Rules for Conflict Item State-
1) Conflict feature must be ON
2) User won’t be able to see fields such as Hidden, Regionally shared hidden, regional hidden and Conflict Hidden, when they are set to true in Data Dictionary.
3) User won’t be able to retain changes if they have modified usage related fields, such as: actual usage, project usage and months.
4) No new Stale state items
2) User won’t be able to see fields such as Hidden, Regionally shared hidden, regional hidden and Conflict Hidden, when they are set to true in Data Dictionary.
3) User won’t be able to retain changes if they have modified usage related fields, such as: actual usage, project usage and months.
4) No new Stale state items
[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3KH6","label":"IBM Maximo MRO Inventory Optimization"},"ARM Category":[{"code":"a8m0z0000001f4RAAQ","label":"MRO\/IO-\u003EMRO IO Features"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
16 July 2024
UID
ibm17160284