Hi ,

We are getting this message while sessioon timrp1210m00 is running.

We have checked all BOMs but couldn't find reason of this problem.

message : tibom1411a
( Loop found in multi-level BoM , caused by manufactured Item )


Do you have idea about this.

Thanks in advance

Nuray

It appears that you have an item within itself in the bill. Run the session Update Low Level Codes and Detect Loops (tibom1213m000). This should show you the problem.

Thank you very much.

Problem has been solved .

Best Regards.

Nuray

Hello,

I have the same problem but, I ran the session mentioned here and does not correct the problem. It does give me a report with three parts with loop but doesn't correct them.

I checked the Multi-Level BOM for the three items and does not have loop under them.

On the Item master stands "Loop" on Net Change LLCD. The Item in the BOM is Low Level 3(three other items above it) but in the Item masters reads Low Level Code 0.

What can I do?

Thanks in advance,

Session tibom1213m000 gives you the results, which are received by you. Now to correct the issues, you may please run the session Print where used item in multi level BOM for all these 3 items and you would come to know where they are getting used. It need not be that these items are just one level below another, it could be possible that they would be say 3 or 4 or may be 10 level below. Print where used item would let you know the anomalies (again this would be the report).

Hello again,

I removed the loop by removing the item that was causing the loop. However; the user expired it with the effectivity dates. So the item it doesn't supposed to be called and the loop should not be there since the item was expired.

What I see this session tibom1213m000 (we have tibom1213m10b A&D) does not check for effectivity dates and tags the items with loop regadless of effecitivy. I entered a loop with an item effective and expired the same date in the past (March 10, 2015 both dates) and the session gives me a loop.

I just want to make sure that people here instead of expire items in a situation like this, better they create a new item.

Thanks in advance,

Hello
It is better to physically remove those conflicting child items from the BOM. The reason being MRP logic would not look at the effective dates! The logic for this is, you may receive an order for a particular revision number which had this conflicting item as a child and then there would be again an issue while generating MRP orders for this revision number.