MES utilization reasons and UCOs

It is important to understand the relationship of MES utilization reasons and your UCO configurations that use them.

When configuring a raw reason code in a UCO template or instance, the default utilization reason and allowable utilization reasons that you assign to it come directly from the global set of utilization reasons defined in the MES database. Therefore, the best practice is to first define utilization reason groups and reasons within the MES database before configuring raw reason codes in the UCOs.

If this global set of utilization reasons are added, deleted, or changed in any way, your UCO configurations that use them might be affected.

The Entity Model Builder will only write the utilization reasons configured for a UCO's raw reason codes that exist in the global set to the MES entity that is being created or modified.

Also, each UCO must have a default raw reason code that the Entity Model Builder will pass into the MES database, whose assigned default utilization reason will become the default unknown utilization reason for the entity. If the default utilization reason mapped to the default raw reason code of the UCO does not exist in the global set of possible utilization reasons, an error is logged and the UCO is marked as invalid.