Why DMF (DIXF) stopped working after Platform Update 70

After upgrading our lower environments to Platform Update 70 (PU70), something strange happened:

All Data Management Framework (DMF / DIXF) imports suddenly stopped working.
No errors in the UI.
No failed records.
Just… nothing processed.

What was really happening?

PU70 upgraded:

• The batch framework
• The AOS services
• The DMF runtime

But DMF relies heavily on background batch services, not just the UI.

What broke was not the data — it was the execution layer.

Specifically:

• Batch services were not properly synchronized
• DMF execution classes were out of sync with the platform
• Some batch jobs were still running on old binaries

So, when we clicked “Import”, F&O accepted the request — but no engine actually picked it up to run.

Why this is dangerous

This is the worst kind of failure:

The system looks healthy… but does nothing.

No red errors
No failures
But business data stops flowing

If this happened in PROD:

• Invoices wouldn’t import
• Sales orders wouldn’t load
• Integrations would silently fail

The fix

What actually resolved it:

✔ Restarting all batch services
✔ Forcing DMF framework re-initialization
✔ Validating Batch Server Groups
✔ Re-binding DMF batch jobs to the new PU70 services

Once the batch framework and DMF runtime were aligned, all imports started running immediately.

The lesson

After every Platform Update, never assume DMF is healthy just because the UI loads.
Always test:

• DMF import
• DMF export
• Recurring batch jobs

PU upgrades change the engine, not just the screens.

Lesson: Always test DMF imports, exports, and batch jobs after platform updates.