You add a new synonym of an existing internal value in the WOSTATUS domain. In our lab a new internal value was refused, and so was a new synonym domain.
Versions: On Maximo Application Suite 9.1 we confirmed, read-only, that WOSTATUS has the same internal values and that the same fields and messages are present (17 November 2026). The behaviour described here was tested in our lab on Maximo 7.6.1.0 (3 November 2026); we have not re-run the behaviour test on Maximo Application Suite 9.1.
IBM’s page: IBM’s current Maximo Manage documentation gives the same steps. It says: “Specify the existing internal value for which you want a synonym”, and its note says: “The Internal Value field is used by the product and must be unique.”
Last checked: 17 November 2026
A synonym domain such as WOSTATUS maps the values users see (synonyms) to a fixed set of internal values that Maximo’s code understands. A new status is a new synonym of one of those internal values. It behaves exactly like its internal value.
| What we tried | Result in the lab |
|---|---|
| New row in WOSTATUS: internal value APPR, new value | Accepted. |
| New row with an internal value that is not in the domain | Refused: BMXAA4051E, “The synonym for an existing value must be a new value”. |
| New row reusing a synonym that already belongs to another internal value | Refused: BMXAA6309E. |
| A brand-new SYNONYM domain (through the integration object structure) | Refused with BMXAA4051E every time. Nothing was saved. |
| New row with an organisation filled in | Accepted as one row. |
What we observed in our lab: IBM’s page says to “specify the existing internal value”, and its note says the Internal Value field “must be unique”. In our lab a row was accepted only when its internal value already existed in the domain. A new internal value was refused.
status='APPR' do not see the new synonym. Find and update them.On a Maximo 7.6.1.0 lab system a test script opened the WOSTATUS domain, added rows in memory, ran Maximo’s validation and then rolled back without saving, so the delivered domain was never changed. We also tried to create a new synonym domain through the REST API in four variants; all were refused, and a query confirmed nothing was stored.
Not tested: saving a new synonym on a delivered domain, the dialog’s organisation and site rows, the screens. On Maximo Application Suite 9.1 we only read the domain, the field names and the messages.
This page is part of our Maximo knowledge pages: answers we have checked on a real Maximo system in our lab. For questions about your own Maximo data, see Interpretos for Maximo.