Unblocking MMP/OMP Revisions in AMOS

How to clear a stuck Maintenance Program revision safely and quickly

The issue

Teams report that MMP/OMP revision is blocked and no changes are allowed on the Maintenance Program (MP). In AMOS terms, this typically presents as an MMP (baseline) or OMP (operator) revision that cannot be edited, activated, or progressed.

Who’s affected: Planning & Engineering, MP administrators, and Supply Chain stakeholders who depend on current MP data.

Why it happens (in plain language)

A control flag on the MP—activation_blocker_oprev—is set to a non‑zero value. This tells AMOS that a specific Operator Revision (OPREV) is blocking activation. If that OPREV is obsolete, corrupted, or has already been handled, the flag may remain "stuck," keeping the current revision locked.

The fix (overview)

1. Verify and reset the activation_blocker_oprev flag in the database (to 0).

2. Refresh caches in the Operator Maintenance Program (MMP) window to clear client & server cache and re-sync the UI.

⚠️ Safety first

Perform this in non‑production first.

Back up the affected tables/rows before any change.

Use your normal change management process and keep an audit trail (change request, who/when/why).

If in doubt, consult your DBA or AMOS support.

Step‑by‑step procedure

1) Identify the blocker

Use read-only queries to confirm the state of your MP entities and locate any non‑zero activation_blocker_oprev:

-- Review Maintenance Program master data
SELECT * FROM msc_maintenance_program;

-- Review MP revisions (baseline)
SELECT * FROM msc_mp_revision;

-- Review Operator revisions (OPREV)
SELECT * FROM msc_operator_revision;

-- Spot where the activation blocker is set
SELECT *
FROM msc_maintenance_program
WHERE NVL(activation_blocker_oprev, 0) <> 0;

Tip: Note the actual OPREV ID you see in your data. The example below uses a placeholder.

2) Reset the blocker (transactional)

Replace <YOUR_BLOCKER_OPREV_ID> with the value you found (if any). If you’re certain it’s stale/invalid, set it to 0:

Always run in a transaction and take a backup first.
Example: Oracle syntax shown; adapt to your RDBMS as needed.

2a) Quick row-level backup (adjust columns as required)
CREATE TABLE backup_msc_maintenance_program_yyyymmdd AS
SELECT * FROM msc_maintenance_program
WHERE NVL(activation_blocker_oprev, 0) <> 0;

2b) Reset the blocker safely
UPDATE msc_maintenance_program
   SET activation_blocker_oprev = 0
 WHERE activation_blocker_oprev = <YOUR_BLOCKER_OPREV_ID>;

2c) Validate the result
SELECT COUNT(*) AS remaining_blocked
FROM msc_maintenance_program
WHERE NVL(activation_blocker_oprev, 0) <> 0;

2d) Commit (only if validation is OK)
COMMIT;

Important: Your original note showed activation_blocker_oprev = 6801 and later referenced 6081 — that looks like a typo. Use the value present in your system, or target all non‑zero values after verifying they are truly stale.

3) Refresh caches in the AMOS UI

Open MMP → Operator Maintenance Program and click the refresh button in the toolbar. This clears client/server cache and reloads the current MP/OPREV state so your change becomes visible.

Validation checklist (post-fix)

• MMP/OMP revision status is now editable (no longer blocked).

• OPREV lifecycle actions (e.g., prepare, approve, activate) are available again per your process.

• Downstream reports and work packages read the correct MP revision.

• No new integrity errors appear in your MP/OPREV data checks.

Good practice to prevent recurrences

• Close the loop on OPREVs: Ensure obsolete or failed OPREVs are closed/cleaned so the blocker flag doesn’t persist.

• Promote via process: Use your agreed MP governance (prepare → review → approve → activate) to minimize manual DB touch-ups.

• Change control: Log the incident and remediation in your config/change record, including SQL, user, timestamp, and validation evidence.

• Test first: Always validate in a non‑prod environment before promoting to production.

Frequently asked

Will resetting activation_blocker_oprev affect compliance?

No, setting the flag to 0 only removes the spurious block. Your organization must still follow the approved MP/OPREV approval and activation process before changes become effective.

We don’t see a non‑zero blocker but the UI is still stuck.

Trigger the MMP refresh first. If the issue persists, inspect recent OPREV changes, custom triggers, or reach out to AMOS support/DBA to review logs and constraints.

Need help?

• AMOS Admin/DBA: Validate SQL, backups, and transactions.

• Engineering/Planning: Confirm the intended OPREV lifecycle and approvals.

• Change Manager: Record the change and ensure sign‑offs are complete.

Prepared by EXSYN AMOS Competence Centre, keeping your maintenance data clean, connected, and predictive.