Mick Andrus
13th January 2004, 18:00
We're on Baan 5c0 and we're getting the message in the subject line when we try to create a production order for a certain item. I've been trying to interpret Baan's code on this - we have some code picked up in solutions - but it's rather cryptic.
Does anyone understand exactly what this message means? I'm assuming there's a maximum allowable operation number for any given routing but how is that number calculated?
I can produce a production order for this item in our test environment but not in our production environment.
Mick Andrus
15th January 2004, 18:26
We figured it out. It was a parameter setting. No worries.
hendra
16th January 2004, 13:08
Hi Mick,
Care to share what parameter setting you have worked out?
Thanks a lot,
hendra
Mick Andrus
16th January 2004, 15:03
The parameter in SFC, Initial Value for Renumbering Operations is the one. We have six logistics companies, 100 through 600. In Companies 200 - 600 it was set at 100. In Company 100 it was set at 999 - this was an oversight during the company setup.
I discovered the parameter problem before Baan Support could start investigating but they did supply me an explanation. According to Baan Support, when SFC is creating a production order and it comes across a phantom in a PBOM and the phantom itself does not have a routing, it uses this value to create a pseudo-routing for the phantom. The value in the parameter is used as a starting number and this operation numbers are incremented by the value in Step Size for Renumbering Operations. In our case that is 10.
The maximum allowable value for these routing operations is 999. Since this parameter was set at 999, the system was immediately overrunning its maximum allowed value.
The irony is that only Company 100 is using phantoms in their true sense so if we'd had this parameter misset in another company it probably wouldn't have been a problem. We were puzzled at first that we had this problem with some items and not others: even items with extensive and long routings would go through just fine and items with short routings would get the error.
Oh, well. Live and learn.