Reading conflict flags

A conflict is any ERP situation that requires a procurement or production action before the phase-in date can be honoured. Redline detects them automatically and explains each one in plain language.

Types of conflicts

Conflict type	What it means	Action generated
Open PO after phase-in date	A purchase order for the old part is scheduled to arrive after the switch date — stock you will not use	Cancel or amend the PO
Production order after phase-in date	A production run is planned to consume the old part past the switch date	Update the BOM for that production order, or hold and reschedule
Insufficient new part lead time	The new part cannot arrive in time for the calculated phase-in date given its standard lead time	Expedite the new part order, or adjust the phase-in date

Every conflict generates an action

Redline automatically creates a corresponding action item in the action list for each conflict detected. You do not need to manually translate conflicts into tasks — this is done for you. Each action item includes the specific PO number, order ID, quantity, and a plain-language justification sentence.

Conflict indicators in the UI

Conflicts are shown at two levels:

• Item level — each affected item in the Phase-In tab shows a conflict badge with a count
• Strategy level — the comparison view shows the total conflict count per strategy

An item with no conflicts shows a green status indicator. An item with one or more conflicts shows an amber or red badge depending on severity.

Resolving conflicts

You do not need to resolve conflicts before releasing the ECO. The generated action list contains the instructions for each department to resolve them. Releasing the ECO triggers the notifications that start the resolution process.

If you want to reduce conflicts before releasing, reconsider the strategy. The Stop strategy has the most conflicts (write-offs, cancellations). Run-down typically has the fewest because it respects existing commitments.