That all works really well. The issue we are having is the assemblies under the phantom boms. For example a weldment that is part of a phantom bom, but not a phantom bom itself. The parts that go into that weldment (usually laser brake, or some combination of fab activities) are the ones that aren't related correctly to the welding operation. The odd thing is, it's only the assemblies, not the materials that are having this issue.
That all works really well. The issue we are having is the assemblies under the phantom boms. For example a weldment that is part of a phantom bom, but not a phantom bom itself. The parts that go into that weldment (usually laser brake, or some combination of fab activities) are the ones that aren't related correctly to the welding operation. The odd thing is, it's only the assemblies, not the materials that are having this issue.
Does anyone else see this behavior in your system? We are on E10.0.700.4
Thanks,
Brandon
Method tracker
Asm 1 top level (op 10 for asm 2)
Asm 2 phantom bom (op 10 for asm 2)
Asm 3 regular bom (related to op 10 for asm 2)
Asm 4 (related to op 10 for asm 3)
Asm 5 (related to op 10 for asm 3)
Asm 6 (related to op 10 for asm 3)
Asm 7 phantom bom
Asm 8 not phantom bom (related to op 10 for asm 7)
Asm 9 (related to op 10 for asm 8)
Asm 10 (related to op 10 for asm 8)
Asm 11 (related to op 10 for asm 8)
After get details on the job
Asm 1 (related to op 10 for asm 1)
Asm 3 (related to op 20 from asm 2)
Asm 4 – Here is where the problem is,
this should be related to op 10 for asm 3,
however it will show up as related to op 20, which doesn’t exist
Asm 5- Here is where the problem is,
this should be related to op 10 for asm 3,
however it will show up as related to op 20, which doesn’t exist
Asm6 - Here is where the problem is,
this should be related to op 10 for asm 3,
however it will show up as related to op 20, which doesn’t exist
Asm 8 (related to op 30 from asm 7)
Asm 9 - Here is where the problem is,
this should be related to op 10 for asm 3,
however it will show up as related to op 30, which doesn’t exist
Asm 10 - Here is where the problem is,
this should be related to op 10 for asm 3,
however it will show up as related to op 30, which doesn’t exist
Asm 11 - Here is where the problem is, this should be related to op 10 for asm 3,
however it will show up as related to op 30, which doesn’t exist
Operations
Op 10 for asm 1
Op 20 (was op 10) from asm 2
Op 30 (was op 10 ) from asm 7
Are using Alt Methods?
Don Kollmann
ACH Foam Technologies
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Monday, August 1, 2016 1:28 PM
To: vantage@yahoogroups.com
Subject: [Vantage] anyone else having problems with related OPS on parts under phantom BOM's?
So I've been going back and forth with service for a while trying to get them to be able to recreate a problem we are having with assemblies being related to their proper operations after their parents have been pushed up a level.
The agent that I am working with hasn't been able to recreate the problem. I've tried in base mode, and even with the training database to show that it isn't our system, and I can recreate the problem every time. Below is a text example of a tree that would
cause the problem. Hopefully the word wrap doesn't clutter up what I am trying to show to badly.
Does anyone else see this behavior in your system? We are on E10.0.700.4
Thanks,
Brandon
Method tracker
Asm 1 top level (op 10 for asm 2)
Asm 2 phantom bom (op 10 for asm 2)
Asm 3 regular bom (related to op 10 for asm 2)
Asm 4 (related to op 10 for asm 3)
Asm 5 (related to op 10 for asm 3)
Asm 6 (related to op 10 for asm 3)
Asm 7 phantom bom
Asm 8 not phantom bom (related to op 10 for asm 7)
Asm 9 (related to op 10 for asm 8)
Asm 10 (related to op 10 for asm 8)
Asm 11 (related to op 10 for asm 8)
After get details on the job
Asm 1 (related to op 10 for asm 1)
Asm 3 (related to op 20 from asm 2)
Asm 4 – Here is where the problem is, this should be related to op 10 for asm 3,
however it will show up as related to op 20, which doesn’t exist
Asm 5- Here is where the problem is, this should be related to op 10 for asm 3,
however it will show up as related to op 20, which doesn’t exist
Asm6 - Here is where the problem is, this should be related to op 10 for asm 3,
however it will show up as related to op 20, which doesn’t exist
Asm 8 (related to op 30 from asm 7)
Asm 9 - Here is where the problem is, this should be related to op 10 for asm 3,
however it will show up as related to op 30, which doesn’t exist
Asm 10 - Here is where the problem is, this should be related to op 10 for asm 3,
however it will show up as related to op 30, which doesn’t exist
Asm 11 - Here is where the problem is, this should be related to op 10 for asm 3,
however it will show up as related to op 30, which doesn’t exist
Operations
Op 10 for asm 1
Op 20 (was op 10) from asm 2
Op 30 (was op 10 ) from asm 7
Don Kollmann
ACH Foam Technologies
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Monday, August 1, 2016 2:48 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] anyone else having problems with related OPS on parts under phantom BOM's?
I am not. Not on purpose anyways.
Don Kollmann
ACH Foam Technologies
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Monday, August 1, 2016 4:38 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: anyone else having problems with related OPS on parts under phantom BOM's?
We just have one method for each part. So that's not our problem. Did you end up fixing your issue? Or do you have a work around?
[Non-text portions of this message have been removed]