Maximo Open Forum

Assuming the message has the STATUS attribute set correctly, you would not need to invoke the change status manually. Any statusable object (WORKORDER, PO, PR, INVUSE, etc.) in Maximo should have an inbound processing class of psdi.iface.mic.StatefulMicSetIn at a minimum. This class helps the integration handle the change status properly. 

For all objects in Maximo (statusable or not) you want to identify if we have existing object structures and processing classes. In this case, the MXINVUSE object structure and the psdi.iface.app.invusage.MaxInvUseProcess processing class. This processing class extends from the StatefulMicSetIn so it has those capabilities plus some additional logic that is specific to Inventory usage.

The reason you should duplicate existing object structures (or at least re-use the classes) is because we will often provide the necessary logic for handling a lot of the interactions that might be required to support this object properly. For example, on an Asset you need to be able to move the asset (change the parent or location) and there's special logic required to do that properly that we had to write in the processing class. On inventory usage, status progression is important but there's also some special logic for handling shipments and inventory split (when a sufficient balance doesn't exist to cover the required items). Without these processing classes, these operations may not be handled properly. 

Assuming the message has the STATUS attribute set correctly, you would not need to invoke the change status manually. Any statusable object (WORKORDER, PO, PR, INVUSE, etc.) in Maximo should have an inbound processing class of psdi.iface.mic.StatefulMicSetIn at a minimum. This class helps the integration handle the change status properly. 

For all objects in Maximo (statusable or not) you want to identify if we have existing object structures and processing classes. In this case, the MXINVUSE object structure and the psdi.iface.app.invusage.MaxInvUseProcess processing class. This processing class extends from the StatefulMicSetIn so it has those capabilities plus some additional logic that is specific to Inventory usage.

The reason you should duplicate existing object structures (or at least re-use the classes) is because we will often provide the necessary logic for handling a lot of the interactions that might be required to support this object properly. For example, on an Asset you need to be able to move the asset (change the parent or location) and there's special logic required to do that properly that we had to write in the processing class. On inventory usage, status progression is important but there's also some special logic for handling shipments and inventory split (when a sufficient balance doesn't exist to cover the required items). Without these processing classes, these operations may not be handled properly. 

Assuming the message has the STATUS attribute set correctly, you would not need to invoke the change status manually. Any statusable object (WORKORDER, PO, PR, INVUSE, etc.) in Maximo should have an inbound processing class of psdi.iface.mic.StatefulMicSetIn at a minimum. This class helps the integration handle the change status properly. 

For all objects in Maximo (statusable or not) you want to identify if we have existing object structures and processing classes. In this case, the MXINVUSE object structure and the psdi.iface.app.invusage.MaxInvUseProcess processing class. This processing class extends from the StatefulMicSetIn so it has those capabilities plus some additional logic that is specific to Inventory usage.

The reason you should duplicate existing object structures (or at least re-use the classes) is because we will often provide the necessary logic for handling a lot of the interactions that might be required to support this object properly. For example, on an Asset you need to be able to move the asset (change the parent or location) and there's special logic required to do that properly that we had to write in the processing class. On inventory usage, status progression is important but there's also some special logic for handling shipments and inventory split (when a sufficient balance doesn't exist to cover the required items). Without these processing classes, these operations may not be handled properly. 

Hello Sahoo,

Regarding #1, Dont restrict Status field, it seems that the checkbox for it is read-only. Hence it is automatically restricted. Any way to bypass that so I can unrestrict it?

Assuming the message has the STATUS attribute set correctly, you would not need to invoke the change status manually. Any statusable object (WORKORDER, PO, PR, INVUSE, etc.) in Maximo should have an inbound processing class of psdi.iface.mic.StatefulMicSetIn at a minimum. This class helps the integration handle the change status properly. 

For all objects in Maximo (statusable or not) you want to identify if we have existing object structures and processing classes. In this case, the MXINVUSE object structure and the psdi.iface.app.invusage.MaxInvUseProcess processing class. This processing class extends from the StatefulMicSetIn so it has those capabilities plus some additional logic that is specific to Inventory usage.

The reason you should duplicate existing object structures (or at least re-use the classes) is because we will often provide the necessary logic for handling a lot of the interactions that might be required to support this object properly. For example, on an Asset you need to be able to move the asset (change the parent or location) and there's special logic required to do that properly that we had to write in the processing class. On inventory usage, status progression is important but there's also some special logic for handling shipments and inventory split (when a sufficient balance doesn't exist to cover the required items). Without these processing classes, these operations may not be handled properly. 

Status fields should always be restricted. This occurs due to the RESTRICTED field on MAXATTRIBUTE saying this should be restricted. Customers could check the override box and disable this for a specific object structure but this exists on the out of the box attributes for a reason. 

If you don't restrict the field, the value you provide via MIF will get set directly on the record and not go through the proper change status process. 

Hello Sahoo,

Regarding #1, Dont restrict Status field, it seems that the checkbox for it is read-only. Hence it is automatically restricted. Any way to bypass that so I can unrestrict it?

Assuming the message has the STATUS attribute set correctly, you would not need to invoke the change status manually. Any statusable object (WORKORDER, PO, PR, INVUSE, etc.) in Maximo should have an inbound processing class of psdi.iface.mic.StatefulMicSetIn at a minimum. This class helps the integration handle the change status properly. 

For all objects in Maximo (statusable or not) you want to identify if we have existing object structures and processing classes. In this case, the MXINVUSE object structure and the psdi.iface.app.invusage.MaxInvUseProcess processing class. This processing class extends from the StatefulMicSetIn so it has those capabilities plus some additional logic that is specific to Inventory usage.

The reason you should duplicate existing object structures (or at least re-use the classes) is because we will often provide the necessary logic for handling a lot of the interactions that might be required to support this object properly. For example, on an Asset you need to be able to move the asset (change the parent or location) and there's special logic required to do that properly that we had to write in the processing class. On inventory usage, status progression is important but there's also some special logic for handling shipments and inventory split (when a sufficient balance doesn't exist to cover the required items). Without these processing classes, these operations may not be handled properly.