The only thought is whether a component in a BOM is also a sub component n a sub assembly. This can be prevented with an option on the profile preventing duplicate items on a BOM. Does the error list the product?

It would be so much easier if I could see the system.

Good luck


Message Received: Jan 08 2008, 06:20 PM
From: Bill.Geissinger@xxxxxxxxxxxxxxxxx
To: system21@xxxxxxxxxxxx
Subject: [SYSTEM21] SECOND REQUEST - Level Loop Error

One of our plants is trying to do an Item Master file Re-Cost (1/MDC).
Upon running the option, they're getting a Level Code Error Report, with a
'Level Loop Error On Item xxx' error. Does anyone know what causes this
and how to correct it? TIA

The information contained in this email, including attachments, is confidential and may be legally privileged and protected from disclosure by the Electronic Communication Act, 18 U.S.C. 2510-2521. It is intended solely for the addressee(s), and if the reader is not the intended recipient, you are hereby notified that any access, use, reproduction, disclosure or dissemination of this communication by anyone is strictly prohibited. Any action taken or omitted to be taken in reliance on this email is prohibited and may be unlawful. Neither Hutchinson Sealing Systems Inc., Paulstra CRC, the Hutchinson Group nor any of its subsidiaries shall assume legal liability or responsibility for any incorrect, misleading or altered information contained herein. If you have received this message in error, please notify the sender immediately by replying to the email and deleting it from your computer.
This is the System 21 Users (SYSTEM21) mailing list
To post a message email: SYSTEM21@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: SYSTEM21-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

This thread ...


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

This mailing list archive is Copyright 1997-2020 by 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].