An often misused feature of Maximo Database Configuration is the ‘Same as Object’ and ‘Same as Attribute’ fields when defining custom database attributes.
To understand how this works lets consider the ASSET.LOCATION attribute. As you can see from the screenshot below, the LOCATION column of the ASSET table is defined ‘same as’ LOCATIONS.LOCATION’ field.
The direct effect of this is that if you change the size of the LOCATIONS.LOCATION field it will affect all the ‘sameas’ fields defined in other tables.
This is really important to have a consistent data model for your custom fields. Here is an SQL query to help identify missing same-as in the custom objects and attributes.
select objectname, attributename, maxtype, length, sameasobject, sameasattribute from maxattributecfg where objectname like 'XXX%' or attributename like 'XXX%' order by attributename, sameasattribute;
Replace the ‘XXX’ with your custom prefix (hope you have one) and it will list all the custom attributes to be verified.
4 thoughts on “The importance of ‘sameas’ in Database Configuration”
Thanks. This is good to know.
When I am trying to call .Net webserive from Maximo 7.6. i am getting below error.
psdi.util.MXSystemException: BMXAA1481E – Cannot deliver the message to the endpoint.
java.io.IOException: Async IO operation failed (3), reason: RC: 107 Transport endpoint is not connected
at sun.reflect.GeneratedMethodAccessor252.invoke(Unknown Source)
It is throwing in Prod only but not in test environments. Any suggestions please????
Check your Security Settings
thanks, but then what is the difference between same as object and attribute?