Re: Level Loop Error

Hi Bill,

I think I might have had something like this a long time ago.

In our scenario we had product A that has a route that has components B 
and C

We made a batch of product A that was out of specifications, but instead 
of dumping the batch we decided to re-work the batch into future batches 
of the product, so our product setup became product A has a route that has 
components B and C and A

This drove MPR/MPS crazy!! Having a product with itself as an input did 
not compute.
I am fairly sure that we were getting the really helpful 'Level Loop 
Error' message on our reports.

I imagine that this type of scenario might also cause Costing to fail.

Bottom line check your routes to ensure you have not created an endless 
loop

Regards,
Gary Brown
IT Manager
Applied Australia Pty Ltd
_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list
To post a message email: SYSTEM21-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/system21
or email: SYSTEM21-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/system21.