Level 4 · 15 levels · Practitioner · about 75 minutes
Level 4 — How Maximo stores data: objects, attributes, domains and object structures
By the end: Explain how Maximo keeps its data: objects and attributes in the database, MBOs that hold the business rules, why nobody writes SQL to Maximo, domains and synonym domains such as WOSTATUS, relationships, organisations and sites (and why a user "cannot see" a record), and the object structures, MXAPI ones first, that programs use.
Screens, the REST API and integrations all send changes through the MBO business rules layer, which checks them before they reach the database. A direct SQL arrow that tries to skip the rules is blocked with a red cross.
Lesson 1
The database, objects and attributes
Under every Maximo screen sits a relational database: IBM Db2, Oracle Database or Microsoft SQL Server. A relational database keeps data in tables, which are like spreadsheets with strict rules. Each table has named columns, and each row is one record. Maximo has a lot of them: a MAS 9.2 system with a few industry add-ons, read for this course, had more than two thousand objects.
Maximo does not ask you to think in tables. It thinks in objects. An object is one kind of record, such as WORKORDER, ASSET, LOCATIONS or INVENTORY. Each object has attributes: the fields of the record, such as WONUM (the work order number), DESCRIPTION, STATUS, ASSETNUM and SITEID. Most objects sit on one database table and most attributes on one column. Administrators see and change them in the Database Configuration application.
The WORKORDER object drawn as a card of attributes: WONUM, DESCRIPTION, STATUS, ASSETNUM, LOCATION, SITEID, WORKTYPE. STATUS opens a list of allowed values from its domain, WOSTATUS.
| Attribute | Type | Length | Required | What it holds |
|---|---|---|---|---|
| WONUM | UPPER | 25 | Yes | The work order number. Left empty, Maximo fills the next number in its sequence (autokey). |
| DESCRIPTION | ALN | 100 | No | What the job is, in free text |
| STATUS | UPPER | 16 | Yes | Where the work order is in its life. Values come from the WOSTATUS domain. |
| SITEID | UPPER | 8 | Yes | The site the work order belongs to |
| ORGID | UPPER | 8 | Yes | The organisation above that site |
| ASSETNUM | UPPER | 25 | No | The asset the work is on |
| WORKORDERID | BIGINT | 19 | Yes | A unique number for the row, set by Maximo |
The type says what a value can hold. UPPER is text that Maximo turns into capitals, which is why asset numbers and statuses always look like PUMP-102 and APPR. ALN is text that keeps its case. YORN is yes or no, stored as 1 or 0. INTEGER and DECIMAL are numbers, AMOUNT is money, DURATION is hours, and DATETIME is a date with a time. On the 9.2 system we read, UPPER and ALN together made up more than half of every attribute in Maximo.
Persistent or not. A persistent attribute is stored in a database column. A nonpersistent attribute has no column: Maximo works it out each time you look. On MAS 9.2, the INVENTORY attributes CURBALTOTAL (current balance) and AVBLBALANCE (quantity available) are nonpersistent. Maximo adds up the storeroom bins and takes off what is reserved, every time you ask. Whole objects can be nonpersistent too: WOCHANGESTATUS, behind the Change Status dialog, holds its values only while you use it.
A storeroom shelf with items. Some are tagged as reserved for other work orders. Current balance counts every item on the shelf; available balance counts only the untagged ones.
Changing the structure. When an administrator adds an attribute in Database Configuration, nothing changes in the database until they select Apply Configuration Changes. Bigger structural changes need admin mode. When the work is done, admin mode must be turned off again: IBM's setup guide warns that cron tasks fail while it stays on.
Remember: Persistent attributes can be used in a query filter. Nonpersistent ones can only be read. Ask the REST API to filter on curbaltotal and a MAS 9.2 system answers BMXAA4185E - Cannot query on field CURBALTOTAL. You will meet this again in Level 5.
The mistake: Assume every field you see on a screen is a column you can search and sort on. Do this instead: Check in Database Configuration (or the object structure's JSON schema) whether the attribute is persistent. Computed fields such as available balance can be read, not filtered.
Lesson 2
MBOs: where the business rules live, and why nobody writes SQL to Maximo
Between the screens and the database sits Maximo's business layer. Each object is handled by Java code called an MBO, short for Maximo Business Object. One MBO is one record, such as one work order. An MboSet is a set of them, such as the list of work orders a query returned. The MBO classes ship inside Maximo in a file called businessobjects.jar.
The MBO holds the rules. Which fields are required. Which values are allowed. Which status changes are legal: the work order status rules are coded in a Java class called WOStatusHandler. What happens when a value changes: put an asset on a work order and its location fills in. And what else must be written: change a work order's status and Maximo also writes a row to the status history (the WOSTATUS object), with who changed it, when, and an optional memo.
| From | Can move to (IBM's allowable status changes) |
|---|---|
| WAPPR | APPR, INPRG, WMATL, WPCOND, COMP, CLOSE or CAN |
| APPR, WSCH, WMATL, WPCOND | Each other, WAPPR, INPRG, COMP or CLOSE |
| INPRG | WAPPR, WMATL, COMP or CLOSE. Never CAN: work that has started cannot be cancelled |
| COMP | CLOSE only |
| CLOSE, CAN | Nothing. They are final |
IBM notes that these rules also apply to any synonyms you add for the standard statuses. Practitioners also report that APPR and its neighbours can go to CAN while the work order has no actual labour, materials or costs recorded. Two moves surprise new people: a waiting work order can go straight to CLOSE, and an in-progress one can never be cancelled.
Screens, the REST API and integrations all send changes through the MBO business rules layer, which checks them before they reach the database. A direct SQL arrow that tries to skip the rules is blocked with a red cross.
- A person, a program or a message asks for a change
- The MBO checks required fields, domains and status rules
- The MBO runs the side effects: history, defaults, related records
- Only then is the row written to the database
One change, through the business layer
Every row also carries a rowstamp, a number that changes each time the row is saved. The REST API shows it on every object as _rowstamp, and IBM's REST guide says it is there for handling dirty updates: someone saving over a change they never saw. You will use it in Level 5.
Now you can see why we never write to the Maximo database with SQL. An UPDATE statement goes straight to the table. It skips every check, so it can store a status that is not in the domain, or a move the status rules forbid. It skips every side effect, so there is no status history row, no defaults and no related changes. It carries no Maximo user, so security and the "changed by" fields mean nothing. And other parts of Maximo never hear about it: IBM's documentation for Maximo Mobile says changes not made through an MBO, such as direct SQL updates, are not detected by enhanced delta refresh, so phones keep showing the old data.
| Through the business layer (screen, REST API, script, integration, data load) | Straight SQL into the tables |
|---|---|
|
|
A work order status machine: WAPPR to APPR to INPRG to COMP to CLOSE, with WSCH and WMATL as side statuses and dashed arrows to CAN from WAPPR and APPR. A token moves along allowed arrows. Once the work order is in progress, an attempt to cancel it is refused and shakes red, and the allowed moves are listed: WAPPR, WMATL, COMP, CLOSE.
Reading is a different matter. Where your team has read access to a copy of the database, SQL is a fine way to explore and count. The rule is about writing: every write goes through the business layer.
The mistake: Fix bad data in production with an UPDATE statement because the screen is slow. Do this instead: Fix it through the business layer: the screen, the REST API, an automation script or a data load. It takes longer to type, and every rule, history row and sync still runs.
Lesson 3
Domains, and synonym domains such as WOSTATUS
A domain is a list or a rule that says which values an attribute may hold. It is attached to the attribute in Database Configuration. When someone types a value, or a program sends one, the MBO checks it against the domain. If the value is not allowed, Maximo refuses with a message. Two real ones from a MAS 9.2 system: "BMXAA4190E - Status COMPLETE is not in the value list." and "BMXAA0211E - 1 is not defined in the domain DEFECTCLASS."
| Domain type | What it holds | For example |
|---|---|---|
| ALN | A fixed list of text values | A list of failure classes |
| NUMERIC | A fixed list of numbers | A short list of allowed pressure ratings |
| NUMRANGE | Ranges of numbers, not single values | A percentage from 0 to 100 |
| TABLE | Values read from another table through a where clause | Only the storerooms of the current site |
| CROSSOVER | Like TABLE, and it also copies other fields across | IBM's example: copy an asset's serial number from the ASSET table into another record |
| SYNONYM | Internal values the code relies on, plus your own names for them | WOSTATUS, LOCTYPE, LOCASSETSTATUS |
The WORKORDER object drawn as a card of attributes: WONUM, DESCRIPTION, STATUS, ASSETNUM, LOCATION, SITEID, WORKTYPE. STATUS opens a list of allowed values from its domain, WOSTATUS.
Synonym domains are special. IBM describes them as domains reserved by the system, whose internal values are used by the business logic of the product. The work order status rules are written against internal values: WAPPR, APPR, WSCH, WMATL, INPRG, COMP, CLOSE, CAN and HISTEDIT. You cannot add a new internal value. What you can do is add a synonym: your own value that means the same thing as an internal one, shown to your users in its place.
A customer value such as AWAITPARTS maps to Maximo's internal value WMATL. The screen shows the customer's word; the business rules use the internal value.
| Value (what users see) | Internal value (what the rules use) | Description |
|---|---|---|
| WAPPR | WAPPR | Waiting on approval |
| APPR | APPR | Approved |
| WPCOND | APPR | Waiting on plant condition |
| WSCH | WSCH | Waiting to be scheduled |
| WMATL | WMATL | Waiting on material |
| INPRG | INPRG | In progress |
| COMP | COMP | Completed |
| CLOSE | CLOSE | Closed |
| CAN | CAN | Cancelled |
| HISTEDIT | HISTEDIT | Edited in history |
That table is WOSTATUS as a MAS 9.2 system holds it. Look at WPCOND: it is a synonym of APPR. To the business rules, a WPCOND work order is approved. That has a sharp edge for code. If an automation script or an integration checks status == "APPR", it misses every WPCOND work order. Compare the internal value instead. In a script, Maximo's translator turns any synonym into its internal value. In the REST API, IBM's guide describes a domaininternalwhere parameter that filters on internal values.
Synonym-safe status check
# Jython automation script: compare the internal value, not the word on screen
from psdi.server import MXServer
translator = MXServer.getMXServer().getMaximoDD().getTranslator()
internal = translator.toInternalString("WOSTATUS", mbo.getString("STATUS"))
if internal == "APPR":
# true for APPR and for every synonym of it, such as WPCOND
passIBM's rules for synonym domains are short. You cannot delete a synonym domain. You can delete only synonym values that are not the default. Do not delete a synonym value that records still use. A domain value can also be limited to one organisation or site; leave those fields blank unless you mean it, because IBM notes that setting them can create access restrictions nobody intended. Other synonym domains you will meet early: LOCTYPE for location types (OPERATING, STOREROOM, VENDOR and more) and LOCASSETSTATUS for asset status (OPERATING, NOT READY, DECOMMISSIONED).
The mistake: The customer wants a status called AWAITPARTS, so you ask for AWAITPARTS to be added to WOSTATUS as a new internal value. Do this instead: Add AWAITPARTS as a synonym of the internal value WMATL. Users see their own word, and every rule for "waiting on material" keeps working.
Lesson 4
Relationships: how one record finds another
A relationship is a named link from one object to related records. It lives in Database Configuration on the parent object, and it is a small piece of SQL: a where clause that runs against the child object, with values filled in from the parent record. IBM puts it simply: to retrieve data on objects, you must define the relationships between objects.
| Relationship on WORKORDER | Child object | Where clause (MAS 9.2) |
|---|---|---|
| ASSET | ASSET | assetnum = :assetnum and siteid=:siteid |
| LOCATION | LOCATIONS | location = :location and siteid=:siteid |
| WOACTIVITY | WOACTIVITY | parent=:wonum and siteid=:siteid |
| MODIFYWORKLOG | WORKLOG | recordkey=:wonum and class=:woclass and siteid=:siteid |
| SHOWPLANLABOR | WPLABOR | Planned labour for the work order and its tasks |
The words that start with a colon are bind variables. :assetnum means "the ASSETNUM of the work order I am standing on". So for work order 1201, on asset 11400 at site BEDFORD, the ASSET relationship runs assetnum = '11400' and siteid = 'BEDFORD' against the ASSET object. Notice siteid in almost every clause. An asset number is unique only within its site, so the link must say which site.
The WORKORDER object drawn as a card of attributes: WONUM, DESCRIPTION, STATUS, ASSETNUM, LOCATION, SITEID, WORKTYPE. STATUS opens a list of allowed values from its domain, WOSTATUS.
Relationships are used everywhere. Screens use them to show the asset's description on a work order. Automation scripts use them: mbo.getMboSet("ASSET") returns a work order's asset without writing a join. The REST API uses them too: oslc.select=wonum,asset.description reads a field through the ASSET relationship, and oslc.where=asset.status="OPERATING" filters through it.
Some relationships return at most one record: a work order has one asset. Others return many: a work order can have many tasks and many lines of planned labour. In the REST API, a one-to-many relationship comes back as a list. IBM's guide uses rel.<name>{fields} for that, for example rel.openwo{wonum,description} on an asset to list its open work orders.
A site contains a building, which contains a plant room, which contains locations. A pump asset sits in one location, then moves to another, and its history moves with it.
A relationship used from code
# Automation script on WORKORDER: read the asset through the relationship
assetSet = mbo.getMboSet("ASSET") # runs: assetnum = :assetnum and siteid = :siteid
if not assetSet.isEmpty():
asset = assetSet.getMbo(0)
print("Asset " + asset.getString("ASSETNUM") + " is " + asset.getString("STATUS"))The mistake: Write a new relationship as assetnum = :assetnum and leave out the site. Do this instead: Include siteid=:siteid whenever the key is unique only within a site. Without it, the link can return another site's asset with the same number.
Lesson 5
Organisations, sites, and why users "cannot see" a record
Maximo is built for big companies with many places. IBM describes three levels: the system, organisations and sites. An organisation is usually a financial entity: all of its money is kept in one base currency. A site is a part of an organisation that tracks its own inventory and work, such as a plant, a depot or a hospital campus. When you create an organisation, you create at least one site with it.
| Level | What lives there | How you can tell on the record |
|---|---|---|
| System | What every organisation shares: users, security groups, and domains left at system level | No SITEID or ORGID |
| Item set and company set | The item master and company master, shared by one or more organisations | ITEM carries ITEMSETID |
| Organisation | Money: currency, general ledger accounts, companies | COMPANIES carries ORGID |
| Site | Day-to-day work: work orders, assets, locations, PMs, storeroom balances, purchase orders | WORKORDER, ASSET, PM, INVENTORY and PO carry a required SITEID |
IBM's rules for sets: create at least one item set and one company set before any organisation. Each organisation uses exactly one item set and one company set, and several organisations can share the same ones. That is how two companies in one group can buy from one list of suppliers and stock one catalogue of parts, while keeping their money and their work apart.
An organisation holds two sites. Work orders, assets and locations belong to one site. A user with access to only one site sees that site's records; the other site's records are greyed out.
Users reach records through security groups. A group grants applications, such as Work Order Tracking, and sites. Usually a user's groups add up, so they get what any one of their groups allows; a group marked as independent of other groups keeps its own sites and applications paired instead. Each user also has a default insert site, the site new records land in. From MAS 9.2, sites can also be assigned to security groups at the suite level.
- Site. The record is on a site that none of their security groups grants. This is the most common cause by far.
- Application. They can reach the list but not the application the record lives in, or not the action they need.
- The query. The list opened with a saved or default query that filters the record out. Clear the filters and search again.
- The key. Work order numbers are unique only within a site. WONUM 1042 at one site and WONUM 1042 at another are two different work orders.
- Data restrictions. An administrator has hidden certain records or fields from their groups.
The same rules apply to programs. An API key belongs to one Maximo user, and IBM's REST documentation says calls made with it respect all of that user's permissions. If an integration gets fewer records than the screen shows, check the integration user's sites and groups before anything else.
An organisation holds two sites. Work orders, assets and locations belong to one site. A user with access to only one site sees that site's records; the other site's records are greyed out.
The mistake: Give the user access to every site and every application so the complaint goes away. Do this instead: Find which site and application the record needs, and grant exactly that through the right security group. The least access that does the job.
Lesson 6
Object structures: how programs see the data, and the MXAPI ones
Programs outside Maximo do not talk to MBOs directly. They talk to object structures. IBM's definition: an object structure is the common data layer that the integration framework uses for messages in and out, and it consists of one or more related business objects that define the content of an XML or JSON message. In short, a named bundle of objects: a main object at the top, children underneath, joined by relationships.
The MXAPIWODETAIL object structure drawn as a box holding WORKORDER with its children: tasks (WOACTIVITY), planned labour (WPLABOR) and planned materials (WPMATERIAL). An API call reads the whole bundle in one answer.
| In the JSON | Object | Through relationship | What it is |
|---|---|---|---|
| woactivity | WOACTIVITY | WOACTIVITY | The work order's tasks |
| wplabor | WPLABOR | SHOWPLANLABOR | Planned labour: craft and hours |
| wpmaterial | WPMATERIAL | SHOWPLANMATERIAL | Planned materials: items and quantities |
| wptool | WPTOOL | SHOWPLANTOOL | Planned tools |
| worklog | WORKLOG | WOWORKLOG | Work log notes |
| invreserve | INVRESERVE | MXINTINVRES | Storeroom items reserved for the job |
| doclinks | DOCLINKS | DOCLINKS | Attached documents |
IBM describes MXAPIWODETAIL as "Maximo API for Work Orders with Plans and Reservations". On MAS 9.2 its JSON schema lists 634 attributes and 24 child lists, a few of which are in the table above. Its key is siteid plus wonum, and its unique id is workorderid. You can ask any Maximo for the schema of an object structure: GET /maximo/oslc/jsonschemas/mxapiwodetail.
Object structures whose names start with MXAPI are the ones IBM ships for the REST API. You will use these all the time: MXAPIWODETAIL for work orders, MXAPIASSET for assets, MXAPILOCATIONS for locations, MXAPIINVENTORY for storeroom balances, MXAPIITEM for items, MXAPIPM for preventive maintenance, MXAPIJOBPLAN for job plans, MXAPISR for service requests and MXAPIPERSON for people. Older integration structures without API in the name, such as MXWO and MXASSET, come from the integration framework and are still in use. Teams also build their own, often by copying an MXAPI one and trimming it.
Reading a bundle, and asking for its schema
# One call: the work order and two of its child lists
curl -H "apikey: $MAXIMO_APIKEY" \
"https://your-maximo.example.com/maximo/api/os/mxapiwodetail?lean=1&oslc.select=wonum,status,woactivity{taskid,description},wplabor{craft,laborhrs}&oslc.pageSize=1"
# The shape of the bundle, from Maximo itself
curl -H "apikey: $MAXIMO_APIKEY" "https://your-maximo.example.com/maximo/oslc/jsonschemas/mxapiwodetail"Object structures have their own security. The user, or the user behind an API key, needs access to the object structure itself. Without it, MAS 9.2 answers BMXAA9301E: the user of the transaction is not authorized for the object structure, with the advice to configure authorization in the Object Structures application. Ask for a structure that is not on that system and you get, for example, "BMXAA4216E - Unknown Object named MXAPIROUTE." Both are real answers from MAS 9.2, and both mean "check the name and the access", not "Maximo is broken".
An interactive query builder: tick fields to select, pick a status to filter on and a page size. The address builds itself as you click, and a small result table changes to match.
Because every read and write through an object structure goes through the MBOs, the same rules apply whether a person uses a screen or a program uses the API. A status move the screen refuses, the API refuses too. Try the three missions on this level: ask for a field that does not exist and watch the sim fail closed, list the operating assets with their locations, and read the storeroom balances.
The mistake: Use oslc.select=* on MXAPIWODETAIL "to be safe". Do this instead: Name the fields and child lists you need. With 634 attributes on offer, * makes every answer huge and every call slow.
Level 4 missions in the Maximo sim
- Ask for a field that does not exist. Ask for work orders with a made-up field called zz_ghost. A good system refuses.
- Operating assets and where they live. List the assets in OPERATING status with their location.
- What is on the shelf. Read the storeroom balances: item, storeroom, current balance and available balance.
Real practice on the Maximo SIM
Tasks you do by hand on the training Maximo, with the evidence your trainer checks.
- Look inside the WORKORDER object (DEV). Database Configuration is where an object's attributes, their types and their domains live. Reading it is a daily developer habit.
- Open the object structure behind the API (DEV). The REST API reads object structures, not tables. See which objects MXAPIWODETAIL bundles.
Check yourself: the Level 4 quiz
17 questions. Pass mark 70%.
- Look at the red arrow. Why is it stopped? (picture: Every change goes through the rules)
- SQL straight into the tables skips the business rules, history and security
- SQL is too slow for Maximo
- The database is read-only on Mondays
- Only Java may read the database
- What is an MBO?
- A database table
- The Java business object that holds the rules for one kind of record
- A report template
- A user role
- On MAS 9.2, INVENTORY's CURBALTOTAL is nonpersistent. What does that mean for you?
- It is stored twice
- It has no column: Maximo computes it, so you can read it but not filter on it
- It can never be shown on a screen
- It is deleted every night
- Look at the lit attribute. Its allowed values come from a list. What is that list called? (picture: An object and its attributes)
- A relationship
- A domain
- An object structure
- A security group
- Look at the picture. Which value do the business rules act on? (picture: Synonym domains)
- The customer's word
- The internal value
- Whichever was typed last
- Neither: rules ignore status
- An automation script checks status == "APPR". A work order has status WPCOND, a synonym of APPR. What happens?
- The check matches
- The check misses it, though the rules treat it as approved
- Maximo converts WPCOND to APPR on save
- The script throws an error
- A customer wants a new work order status called AWAITPARTS. What do you do?
- Add AWAITPARTS as a new internal value of WOSTATUS
- Add AWAITPARTS as a synonym of the internal value WMATL
- Create a new attribute called STATUS2
- Update the WORKORDER table with SQL
- Which domain type validates a value against another table and also copies other fields across?
- ALN
- NUMRANGE
- CROSSOVER
- SYNONYM
- The WORKORDER relationship ASSET has the where clause assetnum = :assetnum and siteid=:siteid. What is :assetnum?
- A fixed asset number typed by an administrator
- The ASSETNUM of the work order the relationship starts from
- A database password
- The newest asset in the system
- Look at the picture. This user's groups grant site A only. What do they see of site B's work orders? (picture: Organisations and sites)
- Everything, read-only
- Nothing: to them those records are not there
- Only the closed ones
- Only the descriptions
- Which picture shows a user who can work on records in both sites?
- Picture A
- Picture B
- Which of these is shared between organisations through a set?
- Work orders
- Items in the item master
- Storeroom balances
- Purchase orders
- A planner can find work order 1042, but a colleague at another depot opens a different job under the same number. How is that possible?
- The database is corrupt
- Work order numbers are unique only within a site, so each site can have its own 1042
- Someone copied it
- Maximo reuses numbers every year
- Look at the bundle. What do you get from one API call to it? (picture: An object structure bundles objects)
- Only the work order header
- The work order with its tasks, planned labour and planned materials
- Every table in Maximo
- A PDF of the work order
- An integration call answers BMXAA9301E: the user is not authorized for the object structure. What is the fix?
- Retry until it works
- Grant the integration user access to that object structure through its security group
- Switch to SQL
- Rename the object structure
- A call answers "BMXAA4216E - Unknown Object named MXAPIROUTE." What does that tell you?
- The server is down
- That object structure is not on this system, or the name is wrong
- Your API key expired
- The record was deleted
- Look at the picture. A script, a screen and an API call each try this move. What happens? (picture: The work order lifecycle)
- Only the screen is refused
- Only the API call is allowed
- All three are refused, because the same MBO status rules run for every channel
- All three succeed
Remember it as a picture
- MBO: Maximo Business Object: the Java layer that checks rules and writes history before anything reaches the database.
- Never write SQL to Maximo: It skips checks, status history, security and mobile sync. Read with SQL if you must; write through the business layer.
- Object and attribute: An object is a kind of record (WORKORDER); attributes are its fields (WONUM, STATUS, SITEID).
- Nonpersistent attribute: No column; computed when read. CURBALTOTAL and AVBLBALANCE can be read, not filtered.
- Domain: The allowed values for an attribute. STATUS on WORKORDER uses WOSTATUS.
- Synonym domain: Your words mapped onto internal values. Users see AWAITPARTS; the rules see WMATL.
- WPCOND means APPR: A synonym of APPR. Code must compare internal values, or it misses every synonym.
- Relationship: A named where clause from parent to child: ASSET is assetnum = :assetnum and siteid=:siteid.
- SITEID: Work orders, assets, locations, PMs and balances belong to one site. Keys are unique only within it.
- Organisation and site: An organisation keeps one base currency; its sites track their own work and inventory.
- "I cannot see that record": First question: which site is it on, and do this user's security groups grant it?
- Object structure: A named bundle of related objects that programs read and write. MXAPIWODETAIL: work orders with plans.
- MXAPI object structures: The ones IBM ships for the REST API: MXAPIWODETAIL, MXAPIASSET, MXAPIINVENTORY, MXAPIPM and more.
Where these facts come from
- IBM Docs (Maximo Manage): Synonym domains
- IBM Docs (Maximo Manage): Creating relationships between parent and child tables
- IBM Docs (Maximo Manage): Levels in the hierarchy (system, organisation, site)
- IBM Docs (Maximo Manage): Working with sets
- IBM Support: Allowable status changes for work orders
- IBM Docs (Maximo Manage): Object structures
- IBM Docs: Enabling enhanced delta refresh (direct SQL updates are not detected)
- Assetize record: Maximo 9.1 domain WOSTATUS
Try it on the real tools
How did Level 4 go?
Rate the level and say what worked, what did not, what you liked and what you did not. Send it now, or with your full report.