I submitted an incident with Infor Concierge. They told me that, "Often the error message is indicative of a Sequence out of Sync and after several attempts they will get back in Sync.". Sure enough, after several save attempts if started working normally. I was told there is no way for the end user to re-sync this operation other than multiple save attempts.
Was this happening in production environment or a training environment? This does sometimes happen when you refresh your training with production because of the database itself. Glad this issue has been resolved for you.
Basically, what they are saying is there are several sequences(work order number, transaction number, purchase order number, ect) in the back end of the data base that pulls a number when it is trying create a new record. When the sequences get messed up basically it is trying to pull a duplicate number to one that already exists in the database and each time you save it is trying to pull it again. That is why they said that if you keep saving it will fix itself.
We kept having this issue over and over. So we started moving all of our PMs to the new Maintenance Patterns. Since there is nothing to sync, we don't have this issue anymore. We love Maintenance Patterns. (in version 11.4).
I submitted an incident with Infor Concierge. They told me that, "Often the error message is indicative of a Sequence out of Sync and after several attempts they will get back in Sync.". Sure enough, after several save attempts if started working normally. I was told there is no way for the end user to re-sync this operation other than multiple save attempts.
Was this happening in production environment or a training environment? This does sometimes happen when you refresh your training with production because of the database itself. Glad this issue has been resolved for you.
Basically, what they are saying is there are several sequences(work order number, transaction number, purchase order number, ect) in the back end of the data base that pulls a number when it is trying create a new record. When the sequences get messed up basically it is trying to pull a duplicate number to one that already exists in the database and each time you save it is trying to pull it again. That is why they said that if you keep saving it will fix itself.
This was happening in the production environment. Thank you for the explanation. I was wondering.
We kept having this issue over and over. So we started moving all of our PMs to the new Maintenance Patterns. Since there is nothing to sync, we don't have this issue anymore. We love Maintenance Patterns. (in version 11.4).
Tracie, Is this when you are trying to create the actual record view PM schedule record on the record view or save equipment on the equipment tab?