Maximo Open Forum

hello EVERYONE, I have this problem when I try to add a task to a WO.
I added the "LOCATION" attribute in the WORKORDER AND WOACTIVITY AND LOCATIONS objects. When I choose an asset, the LOCATION value is automatically displayed. But when I want to add a task, I get this error "Attribute LOCEU does not exist. Gather the logs
from the <HOME> directory and determine the process or app
referencing the invalid attribute.". If I don't add an asset or location on my WO, I can add a task without problem. Can you help me?

Hi @FULGENCE KOFFI This occurs due to invalid relationship have you modified any relationship which refers to the location object.

Since task work order copies values from the parent work order.

Hi @FULGENCE KOFFI!

I can't understand well. In WO, location already exists and in WOACTIVITY as well. You say you have added it. Explain this to me. Or do you mean add the field in the application?
When you add a field that refers to data from another table, if your idea is, for example, to add a location in purchase order (any example comes to mind), you must relate the tables but also, when you add PO.LOCATION You must map the field, indicating where it should be taken from. You do this with the map icon.

When you do, you should restart Maximo for it to take this change (you test it and if it doesn't take the mapping, you restart). I understand that you want to do that but it is not clear to me with your explanation. If you make your need clearer to me, I could try to replicate it.

Regards!

HI @Martin Fabra

Thanks for your reply.

I ADD a attribute named "LIEU" on LOCATIONS OBJECT in database configuration APP. this attribute must fill the attribute "LIEU" of WORKORDER. When i try to create a task on a workpder i get the issue "BMXAA4176E - Attribute LIEU does not exist.". In attachment you can find screenshot.  Where can i find the logs to determine the process or app referencing the invalid attribute.?? I can't launch my PM program.

Hi. I'm going to try to replicate your development.

I just created 2 LIEU fields: WORKORDER.LIEU and LOCATIONS.LIEU. Do you want to copy WORKORDER.LIEU to LOCATIONS.LIEU? Is that so? When completing the creation of both fields, no error occurs, obviously. How have you configured your fields? How have you configured WORKORDER.LIEU to be copied to LOCATIONS.LIEU? A script? Have you added any relationships? Have you inserted any new quest maps? I don't want to develop anything until I fully understand how you have proceeded. My intention is to replicate what you have done and replicate the problem and then give you the solution.

Regards!

Hello @Martin Fabra

I delete the field ( "LIEU") , i update, assembly and deploy MAXIMO , i get the same issue when i try to add ASSET in "ACTIVITIES AND TASK" APPLICATION.

Can you show me where i can trace the event or where i can find a log for this issue??

But look, I have also created 2 LIEU fields, both in WORKORDER and LOCATIONS and it hasn't given me any errors. You, in addition to creating both fields, must have done something else... what is it? What you have done and what I did not do, must be the difference because now it gives you that error and it does not give it to me.

Maybe some relationship between tables? Maybe you have mapped some fields? Something you remember?

Regards!

Hi Martin,

You've used a term that I've never heard of in connection with Maximo.  What are "quest maps"?

Hi Craig! And I don't think you're going to read or listen to it again. Sometimes when I'm in a hurry I use the translator. The translator put it in and since I didn't check it properly... here is the result.

I was referring to when you edit the lookup map in the attributes. The truth is that I don't know how the translator put "quest map".

Regards!

Hi Martin,

I thought you were referring to the lookup map. 

However, in the context of the issue, there is no lookup being used.  The lookup map is about when you use a lookup, selected a value and have the answer return to a field.  In Maximo, it is expecting that the source field and the target field name are the same, but this not always.  An example is the supervisor, the lookup works on the person object that source field is PERSONID, however, the target field is SUPERVISOR.

you may try to check integrity of your database , there may be issue with the attributes are not in sync up with required data dictionary and allied tables.

Hi Fulgence,

Several things are not making sense to me.  In the thread you have mentioned that:

• You have created a new field LOCATIONS.LIEU
• You have created a new field WORKORDER.LIEU
• You have created a new relationship LIEU_REL from LOCATIONS to WORKORDER
• That the LOCATIONS.LIEU must crossover to the WORKORDER.LIEU when the location is added
• You are getting an error that LIEU attribute does not exist when you add a task

Now for my feedback.

1. A relationship does not do any copying.  For that you must use either a crossover domain or an automation script.  There is an existing crossover domain LOC2WO.  Please update this to have the data crossover.
2. Please make the field WORKORDER.LIEU read-only using the application designer, unless you intend it to be edited.
3. You not explained how the relationship LIEU_REL is being used on the work order screen.  The purpose is unclear and seems unrelated to the error that you ar having, however you need to also include the SITEID = :SITEID in the relationship since the locations and the work order are at site level.
4. Have you checked that after configuring the WORKORDER.LIEU field, that it also appears in the database configuration for the WOACTIVITY.LIEU.
5. The screenshot of the relationship NEWACTIVITY has no bearing on the error as this is a standard relationship in Maximo.
6. The logs are recorded on the webserver, you can set-up your own by using the logging application where you will find the loggin location by looking at the root logger (for Maximo 7.6)
7. Why have you used ~NULL~ in the description and title for the LIEU field.  Please use a proper title and description as the value ~NULL~ is usually used in searches to find the row of data when that field has NULL data?  It should not be the cause, but why introduce something that could i.e. reserved words.
8. When you get the error are you selecting the NEW ROW on the child work order of the task work order?

Hi all,

After spending a bit of time with Fulgence, we have resolved the issue.  Though the answer does not make sense.

We were finally able to trap an error in the log "

01 juil. 2024 12:30:01:532 [WARN] BMXAA6694W - The mbovalueinfo for attribute LIEU for object MULTIASSETLOCCI could not be retrieved.

Very strange.  As this should have only involved the LOCATIONS and WORKORDER (based) objects, not the MULTIASSETLOCCI.  After adding the LIEU field, it resolved the issue.  Something I would not have ever expected, but it worked.

We also removed the relationship as the intent is actually to have the LIEU info crossover to the work order, so we also updated the LOC2WO crossover domain.

I observed one other unrelated problem.

So, we out this one down as solved!

HELLO EVERYONE,
I thank you all for your contribution and particularly @GRAIG KOKAY who gave me his precious time to investigate the problem. WITH the log he set up we were able to identify the source of the problem. As weird as it may sound, we were looking in the wrong direction. Thank you all

01 juil. 2024 12:30:01:532 [WARN] BMXAA6694W - The mbovalueinfo for attribute LIEU for object MULTIASSETLOCCI could not be retrieved.