Tim Schofield schrieb:
Im not sure, if that is how it's supposed to work, but it's the way it works ;-) Besides, it worked
that way in SP3 too and, I hate that behaviour.
This effect is caused by the way route information is saved. Most of the information (workcenter,
time settings...) are not kept directly on the route but on a different table (RouteOpr) which is
linked to the route by the operation name, itemCode and routeCode (where item- and routeCodes can be
defined to be specific or general).
So if you use the same operation name twice on the same route, you link to the same data record
(RouteOpr) for both operations and therefore all changes are reflected on both operations.
As I said above I hate this. If you want to use general operation names like e.g drilling, the
probability, that this will occur several times in a route is high. And then you have to use
drilling_1, drilling_2, because not every drilling operation will take the same time, but it will
make no sense to define an operation name for every possible drilling operation.
Mike
|