When the operators create a new MRB the status goes to Created.
However, on a least 3 cases the MRB went into status Planned. We can’t figure out what is making the status be Planned vs Created.
Planned doesn’t even seem to be a valid status (doesn’t show in the search options).
Can anyone shed some light on why MRBs sometimes create in status Created and sometimes Planned?
Page 1 / 1
Hi,
Some questions!
Are the MRBs all the same type (e.g. Purchase Order MRB) and created in exactly the same way each time?
Does the same user get a ‘Planned’ and ‘Created’ MRB or does it vary by user?
Could you share a couple of examples with screen shots?
Many thanks!
So this is turning out to be really weird. It also seems to be some kind of timing issue.
If we create an MRB in our Test environment, it creates the MRB in status Planned. If you look at the underlying table MRB_HEAD, Objstate=Planned, State=Planned.
If we create an MRB in our Production environment or DEV, it creates the MRB in Status Created. The underlying table MRB_HEAD shows Objstate=’Planned’, State=’Created’
All three databases have all of the same patches applied, the only difference is DEV was refreshed from production about a month ago and TEST was refreshed about 3 months ago. As far as I can tell nothing changed in the code in that time frame.
This may be moot point now, but I am very concerned that the system behavior seems to have changed without any deliveries being applied.
Has there been a custom event added in the intervening period?