RE: pseudo

One thing you may investigate is incorporating the Psuedo's operation into
the Parent Routing. For example: if you run an Operation 10 and 20 and the
pseudo parts are added at a point in between you could add an operation step
# 15 for example, and make it non-reportable so that it is considered
complete when #20 is reported. This would allow the cost generation to Load
Standards or 'roll-up' the costs. You should see this operation on your
paperwork as well. 

Another approach would be to add the machine or labor to an existing routing
step where you already add this Psuedo to the product.


Test this out and determine whether it helps.

Good Luck,

McK King

BWAY    


-----Original Message-----
From: Chick Doe [mailto:Cdoe@xxxxxxxxxxxxxxxxxxxxx]
Sent: Wednesday, January 21, 2004 5:14 PM
To: bpcs-l@xxxxxxxxxxxx
Subject: pseudo


version 6.1

suppose i have a small sub-assembly part that is made up of a couple of
components. this sub-assembly part has a b/m and it has a routing that
describes how to assemble it and has the time standards.

now suppose i want to stop making the sub-assembly as a stand alone
item and that we want to issue the components to the higher level
assembly that is the parent of the sub-assembly. i think i can do this
by changing the coding of the sub-assembly part number to a pseudo. but
what do i do about the routing operation to assemble the sub-assy? it
won't show on the routing for the parent item. it will still get rolled
up via the cost generation, but how do i include this on the shop
package that goes to the floor for the parent?

chick doe
prime measurement products
_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.