Phantoms and successful backflushing

Yahoo Archive
1
Try not to add any operations, subassemblies, but materials only
inside Phantom BOM. Backflush all operations except the last one in
its parent part's BOM. Report production quantity using Labor
Entry on that final operation, and you will see all child parts
inside the Phantom BOM get backflushed.


--- In vantage@yahoogroups.com, "g8makin" <jj.tarter@...> wrote:
>
> Hi all! I'm new to the group, but so thrilled to find you because
> looking through the posts answers to so many questions. Thank you!
>
> We're completely new to Vantage and preparing to implement v8.03.
The
> issue we have has been touched on a bit in here recently, but not
> exactly. In our BOMs we have structured many subassemblies as
> phantoms in order to be able to modify them easily and to report
> production on the final product without having to report
production
> at each subassembly level as they are true phantoms within the
> manufacturing process and we want everything to backflush upon
making
> the final product. We've set all the backflush tags on the
> materials, operations set correct, locations correct -- everything
> per textbook/instruction complete as far as we can tell. When we
> report quantity only (Kanban) on the final product, everything
> backflushes perfectly. Transaction history is correct and
inventory
> is perfect. Cost per production standards, etc. works fine.
However,
> if we create a quick job and report production using a Labor entry
on
> the final operation, it will only backflush what is related to
that
> operation (it looks like it tries to backflush on down when
viewing
> the transaction history/get details, however, actual inventory
does
> not change). What's stumping us whether this is a system bug or
> whether we are trying to get the system to do something it doesn't
> do? Do phantoms only backflush by reporting on quantity only
> (Kanban)? We've not been able to get precise answers from
customer
> support as of yet. I wondered if any of you have dealt with this
> issue or have had any problems?
>
2
Hi all! I'm new to the group, but so thrilled to find you because
looking through the posts answers to so many questions. Thank you!

We're completely new to Vantage and preparing to implement v8.03. The
issue we have has been touched on a bit in here recently, but not
exactly. In our BOMs we have structured many subassemblies as
phantoms in order to be able to modify them easily and to report
production on the final product without having to report production
at each subassembly level as they are true phantoms within the
manufacturing process and we want everything to backflush upon making
the final product. We've set all the backflush tags on the
materials, operations set correct, locations correct -- everything
per textbook/instruction complete as far as we can tell. When we
report quantity only (Kanban) on the final product, everything
backflushes perfectly. Transaction history is correct and inventory
is perfect. Cost per production standards, etc. works fine. However,
if we create a quick job and report production using a Labor entry on
the final operation, it will only backflush what is related to that
operation (it looks like it tries to backflush on down when viewing
the transaction history/get details, however, actual inventory does
not change). What's stumping us whether this is a system bug or
whether we are trying to get the system to do something it doesn't
do? Do phantoms only backflush by reporting on quantity only
(Kanban)? We've not been able to get precise answers from customer
support as of yet. I wondered if any of you have dealt with this
issue or have had any problems?
3
Our environment is very similar to yours (V8.03 and 55000 multilevel phantoms). And are contending with the same problem you have observed. Kanban reporting works great but blows up our planning process as the kanban jobs (and there requirements) don't persist to drive manufacture and procurement of long lead time items.

We found to utilize persistent jobs, we had to set the last operation in the job to qty reporting (a pain in the neck whenyou have 170 new jobs entered daily) and then have to both labor report the qty completed AND receive the qty completed to get all the labor and materials to backflush.

Epicor has made (too many) assumptions about how different types of orders should behave. We are 'disecting' the kan-ban process to see if we can point it at existing jobs to get the behavior we desire.

If you get anywhere on this, please post your solution (as will I)!

g8makin <jj.tarter@...> wrote:
Hi all! I'm new to the group, but so thrilled to find you because
looking through the posts answers to so many questions. Thank you!

We're completely new to Vantage and preparing to implement v8.03. The
issue we have has been touched on a bit in here recently, but not
exactly. In our BOMs we have structured many subassemblies as
phantoms in order to be able to modify them easily and to report
production on the final product without having to report production
at each subassembly level as they are true phantoms within the
manufacturing process and we want everything to backflush upon making
the final product. We've set all the backflush tags on the
materials, operations set correct, locations correct -- everything
per textbook/instruction complete as far as we can tell. When we
report quantity only (Kanban) on the final product, everything
backflushes perfectly. Transaction history is correct and inventory
is perfect. Cost per production standards, etc. works fine. However,
if we create a quick job and report production using a Labor entry on
the final operation, it will only backflush what is related to that
operation (it looks like it tries to backflush on down when viewing
the transaction history/get details, however, actual inventory does
not change). What's stumping us whether this is a system bug or
whether we are trying to get the system to do something it doesn't
do? Do phantoms only backflush by reporting on quantity only
(Kanban)? We've not been able to get precise answers from customer
support as of yet. I wondered if any of you have dealt with this
issue or have had any problems?






---------------------------------
Never miss an email again!
Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out.

[Non-text portions of this message have been removed]
4
We also use many phantoms. I believe the system only backflushes the
materials associated to the operation that the labor is being entered
at. It does not go back. Are you not reporting labor at the previous
operations? I believe at the job closing process it might correct your
issue.



________________________________

From: g8makin [mailto:jj.tarter@...]
Sent: Wednesday, March 14, 2007 10:31 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Phantoms and successful backflushing



Hi all! I'm new to the group, but so thrilled to find you because
looking through the posts answers to so many questions. Thank you!

We're completely new to Vantage and preparing to implement v8.03. The
issue we have has been touched on a bit in here recently, but not
exactly. In our BOMs we have structured many subassemblies as
phantoms in order to be able to modify them easily and to report
production on the final product without having to report production
at each subassembly level as they are true phantoms within the
manufacturing process and we want everything to backflush upon making
the final product. We've set all the backflush tags on the
materials, operations set correct, locations correct -- everything
per textbook/instruction complete as far as we can tell. When we
report quantity only (Kanban) on the final product, everything
backflushes perfectly. Transaction history is correct and inventory
is perfect. Cost per production standards, etc. works fine. However,
if we create a quick job and report production using a Labor entry on
the final operation, it will only backflush what is related to that
operation (it looks like it tries to backflush on down when viewing
the transaction history/get details, however, actual inventory does
not change). What's stumping us whether this is a system bug or
whether we are trying to get the system to do something it doesn't
do? Do phantoms only backflush by reporting on quantity only
(Kanban)? We've not been able to get precise answers from customer
support as of yet. I wondered if any of you have dealt with this
issue or have had any problems?





[Non-text portions of this message have been removed]
5
From what we understand to be true, phantoms are the only way that
Vantage can backflush all the way down between parent-child
subassemblies. All operations and materials are to be set to
backflush except for the final, final operation and it is supposed to
be the only quantity you have to report. Maybe at the job closing is
where we're dropping the ball. I'll test that and report back.

--- In vantage@yahoogroups.com, "Tom Morrison" <tmorrison@...> wrote:
>
> We also use many phantoms. I believe the system only backflushes the
> materials associated to the operation that the labor is being
entered
> at. It does not go back. Are you not reporting labor at the previous
> operations? I believe at the job closing process it might correct
your
> issue.
>
>
>
> ________________________________
>
> From: g8makin [mailto:jj.tarter@...]
> Sent: Wednesday, March 14, 2007 10:31 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Phantoms and successful backflushing
>
>
>
> Hi all! I'm new to the group, but so thrilled to find you because
> looking through the posts answers to so many questions. Thank you!
>
> We're completely new to Vantage and preparing to implement v8.03.
The
> issue we have has been touched on a bit in here recently, but not
> exactly. In our BOMs we have structured many subassemblies as
> phantoms in order to be able to modify them easily and to report
> production on the final product without having to report production
> at each subassembly level as they are true phantoms within the
> manufacturing process and we want everything to backflush upon
making
> the final product. We've set all the backflush tags on the
> materials, operations set correct, locations correct -- everything
> per textbook/instruction complete as far as we can tell. When we
> report quantity only (Kanban) on the final product, everything
> backflushes perfectly. Transaction history is correct and inventory
> is perfect. Cost per production standards, etc. works fine.
However,
> if we create a quick job and report production using a Labor entry
on
> the final operation, it will only backflush what is related to that
> operation (it looks like it tries to backflush on down when viewing
> the transaction history/get details, however, actual inventory does
> not change). What's stumping us whether this is a system bug or
> whether we are trying to get the system to do something it doesn't
> do? Do phantoms only backflush by reporting on quantity only
> (Kanban)? We've not been able to get precise answers from customer
> support as of yet. I wondered if any of you have dealt with this
> issue or have had any problems?
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
6
I have never successfully found a way to backflush through phantoms to the
next level.



_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
JJ
Sent: Thursday, March 15, 2007 4:03 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Phantoms and successful backflushing



From what we understand to be true, phantoms are the only way that
Vantage can backflush all the way down between parent-child
subassemblies. All operations and materials are to be set to
backflush except for the final, final operation and it is supposed to
be the only quantity you have to report. Maybe at the job closing is
where we're dropping the ball. I'll test that and report back.

--- In vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com, "Tom
Morrison" <tmorrison@...> wrote:
>
> We also use many phantoms. I believe the system only backflushes the
> materials associated to the operation that the labor is being
entered
> at. It does not go back. Are you not reporting labor at the previous
> operations? I believe at the job closing process it might correct
your
> issue.
>
>
>
> ________________________________
>
> From: g8makin [mailto:jj.tarter@...]
> Sent: Wednesday, March 14, 2007 10:31 AM
> To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
> Subject: [Vantage] Phantoms and successful backflushing
>
>
>
> Hi all! I'm new to the group, but so thrilled to find you because
> looking through the posts answers to so many questions. Thank you!
>
> We're completely new to Vantage and preparing to implement v8.03.
The
> issue we have has been touched on a bit in here recently, but not
> exactly. In our BOMs we have structured many subassemblies as
> phantoms in order to be able to modify them easily and to report
> production on the final product without having to report production
> at each subassembly level as they are true phantoms within the
> manufacturing process and we want everything to backflush upon
making
> the final product. We've set all the backflush tags on the
> materials, operations set correct, locations correct -- everything
> per textbook/instruction complete as far as we can tell. When we
> report quantity only (Kanban) on the final product, everything
> backflushes perfectly. Transaction history is correct and inventory
> is perfect. Cost per production standards, etc. works fine.
However,
> if we create a quick job and report production using a Labor entry
on
> the final operation, it will only backflush what is related to that
> operation (it looks like it tries to backflush on down when viewing
> the transaction history/get details, however, actual inventory does
> not change). What's stumping us whether this is a system bug or
> whether we are trying to get the system to do something it doesn't
> do? Do phantoms only backflush by reporting on quantity only
> (Kanban)? We've not been able to get precise answers from customer
> support as of yet. I wondered if any of you have dealt with this
> issue or have had any problems?
>
>
>
>
>
> [Non-text portions of this message have been removed]
>





[Non-text portions of this message have been removed]
7
Bingo! It was the issue of job closing. I tested this evening and
although entering the production qty as a Labor entry on the final
operation automatically checked "complete"...the job itself was not
complete per the Job Tracker. Upon closing the job, everything
backflushed all the way down through the phantom, etc. **big smile**

Now the other issue with the PartTran History being all messed up
sounds like it's related to that Timeout issue others have
discussed. It makes sense because on the previous jobs where we
didn't properly close, there would have been backflush inv
transactions pending. We'll have to check into that.

Thank you!


--- In vantage@yahoogroups.com, "Tom Morrison" <tmorrison@...> wrote:
>
> We also use many phantoms. I believe the system only backflushes the
> materials associated to the operation that the labor is being
entered
> at. It does not go back. Are you not reporting labor at the previous
> operations? I believe at the job closing process it might correct
your
> issue.
>
>
>
> ________________________________
>
> From: g8makin [mailto:jj.tarter@...]
> Sent: Wednesday, March 14, 2007 10:31 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Phantoms and successful backflushing
>
>
>
> Hi all! I'm new to the group, but so thrilled to find you because
> looking through the posts answers to so many questions. Thank you!
>
> We're completely new to Vantage and preparing to implement v8.03.
The
> issue we have has been touched on a bit in here recently, but not
> exactly. In our BOMs we have structured many subassemblies as
> phantoms in order to be able to modify them easily and to report
> production on the final product without having to report production
> at each subassembly level as they are true phantoms within the
> manufacturing process and we want everything to backflush upon
making
> the final product. We've set all the backflush tags on the
> materials, operations set correct, locations correct -- everything
> per textbook/instruction complete as far as we can tell. When we
> report quantity only (Kanban) on the final product, everything
> backflushes perfectly. Transaction history is correct and inventory
> is perfect. Cost per production standards, etc. works fine.
However,
> if we create a quick job and report production using a Labor entry
on
> the final operation, it will only backflush what is related to that
> operation (it looks like it tries to backflush on down when viewing
> the transaction history/get details, however, actual inventory does
> not change). What's stumping us whether this is a system bug or
> whether we are trying to get the system to do something it doesn't
> do? Do phantoms only backflush by reporting on quantity only
> (Kanban)? We've not been able to get precise answers from customer
> support as of yet. I wondered if any of you have dealt with this
> issue or have had any problems?
>
>
>
>
>
> [Non-text portions of this message have been removed]
>