ERPHive

OIC error explainer

ICS-10994: IAR has been modified outside of the integration design editor

Root cause of ICS-10994, the relationship to the mod base64 hash, and why Oracle Support tells you to recreate from scratch.

Last updated 2026-05-05 · ERPHive docs

ICS-10994 is the user-facing form of the same OIC import-validator failure as ICS-20099. The Designer UI tends to surface ICS-10994 first; the REST API surfaces ICS-20099. Both fire when the import validator decides the IAR is not authentic.

ICS-10994: Import has failed because IAR has been modified outside of the integration design editor

Why it happens

Every IAR carries a mod field at icspackage/project/<PROJECT>/ics_project_attributes.properties. The field is a base64 digest of the canonicalised resource set, computed server-side on every save and export.

If you change anything in the archive — even a single character of whitespace in a transform XSL — the cached mod no longer matches what the server would compute, and the import is rejected.

What Oracle Support says when you open a ticket

Per MOS 2896228.1: Oracle's position is to recreate the integration from scratch in the target environment, or to clone within the same environment via Designer. They will not provide tooling to re-sign an externally edited IAR; this is intentional, not an oversight.

Working around ICS-10994

The realistic options, ordered by sanity:

  1. Re-export from Designer after every edit. The Designer is the only authentic producer of IARs. Treat it like a build tool: open, change, save, export.
  2. Push parameterisable logic into lookups + libraries. Both have REST endpoints that update in place — POST /lookups/{name} and POST /libraries/{id}/archive. Anything you can express as a JS library or a lookup table you can change without touching the IAR.
  3. Switch to a file-based platform for the integrations that move fast. ERPHive and similar tools keep the artifact in plain yaml/json, version-controlled, with proper diffs and review.

What not to do

Stop trying to reverse-engineer the mod hash. We have looked at this carefully — see the mod hash explainer. The derivation involves canonical ordering plus the full resource set, not just the project.xml. Even if you hit it, Oracle reserves the right to change the algorithm in any release. This is a maintenance pit.

Related

Migrate one IAR. See the result in 60 seconds.

ERPHive's public migration tool turns any OIC IAR into a flow.yaml file you can read, diff, and version-control. No login required.

Try the migrator →Talk to us