A domain on an attribute refuses any value that is not in the domain. The field’s Java class still runs as well; the domain does not replace it. To attach a domain, its type must match the attribute and its length must not be longer.
Versions: On Maximo Application Suite 9.1 we confirmed, read-only, that the same domain types, the example domains, the messages and the seven delivered table domains with 1=1 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. Saving and applying a new domain on an attribute is from documentation only.
IBM’s page: IBM’s current Maximo Manage documentation lists the same domain types: ALN, crossover, numeric, numeric range, synonym and table.
Last checked: 17 November 2026
| Domain type | Example in the lab | Bad value |
|---|---|---|
| ALN | Work order crew | BMXAA4190E “… is not in the value list”. Case-sensitive: lower case failed. |
| SYNONYM | Work order class | BMXAA4190E |
| NUMERIC | Service request reported priority | BMXAA4190E |
| TABLE | A delivered table domain with the where clause 1=1 | Accepted with no error (see below). |
| CROSSOVER | Work order asset | BMXAA0089E alone; with the field’s own class the user sees the class error BMXAA0090E. |
A TABLE or CROSSOVER domain checks a value with its Validation Where Clause: the value passes if the clause finds a row. A clause of 1=1 lets every value pass; both systems we read had the same seven delivered table domains like that. A domain also does not refuse a blank value.
Attaching a domain (tried in memory, not saved):
| Attribute | Domain tried | Result |
|---|---|---|
| Upper-case, length 5 | Upper-case domains of length 1 and 3 | Accepted |
| Upper-case, length 5 | Upper-case domain of length 16; ALN domain of length 12 | BMXAA4191E “not valid for Domain” |
| ALN, length 10 | ALN domain of length 12; upper-case domains | BMXAA4191E |
What we observed in our lab: IBM’s technote gives the data type as the reason a domain is missing from the list. In our lab we observed a length rule too: a longer domain was refused. And a well-known older blog says the field class never runs when a domain is set. On 7.6.1.0 both ran: on the asset field, the class and the domain each refused a bad value.
location=:location and siteid=:siteid. Do not use 1=1 if bad values must be refused.On a Maximo 7.6.1.0 lab system we read the domain definitions, their types and lengths and the table domain where clauses with read-only queries. A test script made work orders in memory, set good and bad values and rolled back. A second test set a domain on two attributes in memory and rolled back; a query afterwards showed nothing pending and no domain stored.
Not tested: saving and applying a domain change, numeric range domains, the Domains and Database Configuration screens. On Maximo Application Suite 9.1 we only read the domain definitions, the attributes 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.