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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.