You shouldn't really see these actions, but there are some issues where conditions weren't properly applied so this shows up (similar for consultant user flag and such showing up in the User application). This for Maximo Multitenant ONLY and you should ignore/hide the options.
The purpose, just so you're aware, is that in Maximo Multitenant you have many different tenants inside of a single Maximo application. In standard Maximo, if you needed to add a field to WORKORDER for example, you would just add a field to WORKORDER. But because structural changes to the database take the entire environment down (including other tenants) so they had to come up with a different approach. The administrator (not of the tenant, but of the overall system) instead creates an extension table for each object they want users to be able to add attributes too. This extension table has a variety of fields of different data types (ALN, YORN, etc.). When a user adds an attribute, instead of making a structural change to add in a new attribute, Maximo maps that new attribute to an unused field by this tenant in the extension table. So Tenant A, Tenant B, & Tenant C can all be using ALN1 (I forget the column names on the extension table, but it's generic like this) and each one could have different sizes, required vs not, etc. that are managed purely at a metadata level. This allows tenants to "add" attributes without taking down any other tenant.
------------------------------
Steven Shull
Director of Development
Projetech Inc
Cincinnati OH
------------------------------