I would think about creating a permission in the Inventory Usage application because group names will often change. But writing a script that prevents users from issuing a rotating asset in a DEFECTIVE status to a Work Order could be accomplished with an Object Launch Point automation script on INVUSELINE with the Event as Validate Application.
The script language is jython and the syntax would be something like this:
profile=mbo.getProfile()
groupNames=profile.getGroupNames()
restrictedGroups=["MAXADMIN","TECHNICIAN"]
if mbo.getString("USETYPE")=="ISSUE" and mbo.getString("WONUM") and mbo.getString("ROTASSETNUM"):
for group in restrictedGroups:
if groupNames.contains(group) and mbo.getString("ROTASSET.STATUS")=="DEFECTIVE":
service.error("nvm","defectAssetToWO")
The first two lines are used to get the logged in user's security groups. getGroupNames returns a Java HashSet that we later use
The third line of restrictedGroups is a list of group names that we want to prevent anyone in from being able to issue to a work order if the asset is defective. We later loop through this list to determine if they are in the group.
Then our first if statement is checking that it's an ISSUE transaction (not a transfer), that a WONUM is referenced, and that a rotating asset is provided. These values will all be in memory and can be returned quickly.
If that criteria is true, we then check the group names to see if our user is in at least one group that we want to prevent. We do this before checking the asset status because it's also in memory and can be retrieved quickly.
If the user is in a group that we want to restrict, then we check that the asset status is DEFECTIVE. We do this last because it will initialize a new MBO which is the most expensive logic in the entire script.
If that is true, then we throw an error. You would configure this message in the Database Configuration application with a user-friendly error message to display to the user.
------------------------------
Steven Shull
Naviam
------------------------------
Original Message:
Sent: 01-21-2026 09:03
From: Oumayma Azouz
Subject: Restrict End user to issue defective rotating assets to work orders
Thanks Steven for your reply.
For specific security groups in Maximo, I need to restrict them from issuing rotating assets with status='Defective'
to work orders in operating locations.
But, on the other hand, they can issue the Defective asset to only vendor location, and not work order (that auto populates the operating location linked to it)
------------------------------
Oumayma Azouz
AtkinsRealis
Original Message:
Sent: 01-20-2026 08:19
From: Steven Shull
Subject: Restrict End user to issue defective rotating assets to work orders
Can you clarify the use case a bit further? Are you saying that you have something like a status called DEFECTIVE on assets and you want to prevent most users from issuing that asset against any work order in the INVUSELINE application, but allow some users with a special permission (either signature option, group membership, etc.)?
Automation scripts here are really the ideal approach because you're trying to prevent invalid values. You could create a custom lookup that adds additional criteria to not show the other assets, but it doesn't prevent someone from manually typing in an invalid value nor from importing something that violates the rule.
You could add a table domain or retrieve list automation script to the ROTASSETNUM attribute, but then you're replacing some of the out of the box logic from the java class.
Automation scripts on an attribute validation/action like this are efficient, provided the script itself performs well. If you can help clarify the first part (how to determine who can/can't issue the asset and what makes the asset a problem) I can help with a script that should be efficient.
------------------------------
Steven Shull
Naviam
Original Message:
Sent: 01-18-2026 08:41
From: Oumayma Azouz
Subject: Restrict End user to issue defective rotating assets to work orders
Hello Experts,
Any one have an idea on how to restrict a storekeeper to issue defective rotating assets to work orders (operating locations) ? For reasons of system performance, I want to use only data restrictions instead of automation scripts.
Actually I need to apply a data restriction on INVUSELINE object, but it is not working fine.
Thank you.
#Administration
#Inventory
------------------------------
Oumayma Azouz
AtkinsRealis
------------------------------