Does Peachtree CA v8 do multiple level assemblies?
For instance, let’s say I have the following finished good assembly item:
1 TABLE PKG=
* 1 Table
* 4 Chairs
And, I also have this "sub"-assembly:
1 CHAIR=
* 4 Legs
* 1 Seat
* 1 Back
If I build one "TABLE PKG" in PT, does it accurately flush 16 legs, 4 seats
and 4 backs out of inventory?
Thanks in advance…
Ted –
PT v8 does not build assemblies on demand . . . for multiple assemblies to
work, you need to "build" 4 chairs prior to building a table pkg . . . If
you have 16 legs, 4 seats & 4 backs in stock, and simply build the table pkg
without building the chairs, you will have ending quantities of :
Table Pkg 1
Chair - 4
Leg 16
Seat 4
Back 4
HTH
Chad
Thanks for the reply. So what you’re saying is that PT does not cascade
down through sub-assemblies. That seems confusing to me. How do you get to
the negative number for the chair?
"Chad A Gross" <b1s…@NOSPAMhotmail.com> wrote in message
news:aqta9.27388$Hu2.3148@news1.central.cox.net…
- Hide quoted text — Show quoted text -
> Ted –
> PT v8 does not build assemblies on demand . . . for multiple assemblies to
> work, you need to "build" 4 chairs prior to building a table pkg . . . If
> you have 16 legs, 4 seats & 4 backs in stock, and simply build the table
pkg
> without building the chairs, you will have ending quantities of :
> Table Pkg 1
> Chair - 4
> Leg 16
> Seat 4
> Back 4
> HTH
> Chad
Ted –
Let’s say you start off with inventory counts as follows:
back 4
chair 0
leg 16
seat 4
table pkg 0
table 1
Scenario 1:
You have enough stock to build 4 chairs and 1 table pkg. If you go to
Tasks -> Assemblies and build 1 table pkg, Peachtree is going to adjust your
inventory quantities according to the Bill of Materials listed for the table
pkg. Since you indicated that the table pkg consists of 1 table and 4
chairs, Peachtree increases the quantity of table pkg by 1, decreases the
quantity of tables by 1 and decreases the quantity of chairs by 4, giving
you quantities of:
back 4
chair – 4
leg 16
seat 4
table pkg 1
table 0
Scenario 2:
Using our starting quantities at the top, you go to Tasks -> Assemblies and
build 4 chairs. This gives you quantities of:
back 0
chair 4
leg 0
seat 0
table pkg 0
table 1
You now go to Tasks -> Assemblies and build 1 table pkg. This gives you
quantities of:
back 0
chair 0
leg 0
seat 0
table pkg 1
table 0
Scenario 3:
Using our starting quantities at the top – you sell a table pkg before
building the pkg or chairs in Peachtree. Once the invoice is posted, you
have quantites of:
back 4
chair 0
leg 16
seat 4
table pkg - 1
table 1
You would have to now go to Tasks -> Assemblies, build four chairs AND 1
table pkg to get the correct ending quantites of:
back 0
chair 0
leg 0
seat 0
table pkg 0
table 0
I’m assuming you see what I mean by "Peachtree doesn’t build assemblies on
demand." If you sell an assembly that currently shows 0 on hand, it will
simply decrease the qty on hand by the number sold – it will not decrease
all of the individual components used to build that assembly.
How big of a deal this becomes depends on how complicated your assemblies
are, and how many you sell. I have about 100 different assemblies set up,
but in a given month I sell about 30 – 35. Since all of my assemblies
consist of items that are also sold by themselves, I simply invoice the
assemblies and let Peachtree show the negative qty throughout the month.
Then as part of my month-end procedures I build the necessary number of
assemblies to get their qty on hand back to zero, then check the counts on
my individual components & adjust those quantites as necessary . . .
HTH
Chad
Okay, thanks again, Chad.
I understand that I have to do builds in order to get a finished good into
inventory and also understand that it relieves inventory throughout the BOM.
I guess the main point I’m trying to make is whether or not it is in my best
interest to create "relational", or sub-assembly, BOMs. In looking at the
data structure of the inventory table, it looks rather linear. I gave a
very simple example in my original posting, but maybe it’s best to go into
further detail. I have 48 finished goods that share a similar basic
structure of 5 sub-components (the rest of the components create the
uniqueness of the item). To save myself a ton of data entry, I was wanting
to create a sub-assembly for that common component instead of having to go
through all the rigamarole AND was hoping that PT was "intelligent" enough
to relieve the inventory in my main BOM as well as the sub-BOM.
"Chad A Gross" <b1s…@NOSPAMhotmail.com> wrote in message
news:LIua9.28136$Hu2.16937@news1.central.cox.net…
- Hide quoted text — Show quoted text -
> Ted –
> Let’s say you start off with inventory counts as follows:
> back 4
> chair 0
> leg 16
> seat 4
> table pkg 0
> table 1
> Scenario 1:
> You have enough stock to build 4 chairs and 1 table pkg. If you go to
> Tasks -> Assemblies and build 1 table pkg, Peachtree is going to adjust
your
> inventory quantities according to the Bill of Materials listed for the
table
> pkg. Since you indicated that the table pkg consists of 1 table and 4
> chairs, Peachtree increases the quantity of table pkg by 1, decreases the
> quantity of tables by 1 and decreases the quantity of chairs by 4, giving
> you quantities of:
> back 4
> chair – 4
> leg 16
> seat 4
> table pkg 1
> table 0
> Scenario 2:
> Using our starting quantities at the top, you go to Tasks -> Assemblies
and
> build 4 chairs. This gives you quantities of:
> back 0
> chair 4
> leg 0
> seat 0
> table pkg 0
> table 1
> You now go to Tasks -> Assemblies and build 1 table pkg. This gives you
> quantities of:
> back 0
> chair 0
> leg 0
> seat 0
> table pkg 1
> table 0
> Scenario 3:
> Using our starting quantities at the top – you sell a table pkg before
> building the pkg or chairs in Peachtree. Once the invoice is posted, you
> have quantites of:
> back 4
> chair 0
> leg 16
> seat 4
> table pkg - 1
> table 1
> You would have to now go to Tasks -> Assemblies, build four chairs AND 1
> table pkg to get the correct ending quantites of:
> back 0
> chair 0
> leg 0
> seat 0
> table pkg 0
> table 0
> I’m assuming you see what I mean by "Peachtree doesn’t build assemblies on
> demand." If you sell an assembly that currently shows 0 on hand, it will
> simply decrease the qty on hand by the number sold – it will not decrease
> all of the individual components used to build that assembly.
> How big of a deal this becomes depends on how complicated your assemblies
> are, and how many you sell. I have about 100 different assemblies set up,
> but in a given month I sell about 30 – 35. Since all of my assemblies
> consist of items that are also sold by themselves, I simply invoice the
> assemblies and let Peachtree show the negative qty throughout the month.
> Then as part of my month-end procedures I build the necessary number of
> assemblies to get their qty on hand back to zero, then check the counts
on
> my individual components & adjust those quantites as necessary . . .
> HTH
> Chad
PT will not build an assembly (or sub assembly) if there are not enough
individual items on hand to build it. An error message appears.
–
Diane Koers
Co-author Peachtree 8 for Dummies
"MeTed" <me…@meted.com> wrote in message
news:N3va9.3910$mb.1609@nwrddc01.gnilink.net…
- Hide quoted text — Show quoted text -
> Okay, thanks again, Chad.
> I understand that I have to do builds in order to get a finished good into
> inventory and also understand that it relieves inventory throughout the
BOM.
> I guess the main point I’m trying to make is whether or not it is in my
best
> interest to create "relational", or sub-assembly, BOMs. In looking at the
> data structure of the inventory table, it looks rather linear. I gave a
> very simple example in my original posting, but maybe it’s best to go into
> further detail. I have 48 finished goods that share a similar basic
> structure of 5 sub-components (the rest of the components create the
> uniqueness of the item). To save myself a ton of data entry, I was
wanting
> to create a sub-assembly for that common component instead of having to go
> through all the rigamarole AND was hoping that PT was "intelligent" enough
> to relieve the inventory in my main BOM as well as the sub-BOM.
> "Chad A Gross" <b1s…@NOSPAMhotmail.com> wrote in message
> news:LIua9.28136$Hu2.16937@news1.central.cox.net…
> > Ted –
> > Let’s say you start off with inventory counts as follows:
> > back 4
> > chair 0
> > leg 16
> > seat 4
> > table pkg 0
> > table 1
> > Scenario 1:
> > You have enough stock to build 4 chairs and 1 table pkg. If you go to
> > Tasks -> Assemblies and build 1 table pkg, Peachtree is going to adjust
> your
> > inventory quantities according to the Bill of Materials listed for the
> table
> > pkg. Since you indicated that the table pkg consists of 1 table and 4
> > chairs, Peachtree increases the quantity of table pkg by 1, decreases
the
> > quantity of tables by 1 and decreases the quantity of chairs by 4,
giving
> > you quantities of:
> > back 4
> > chair – 4
> > leg 16
> > seat 4
> > table pkg 1
> > table 0
> > Scenario 2:
> > Using our starting quantities at the top, you go to Tasks -> Assemblies
> and
> > build 4 chairs. This gives you quantities of:
> > back 0
> > chair 4
> > leg 0
> > seat 0
> > table pkg 0
> > table 1
> > You now go to Tasks -> Assemblies and build 1 table pkg. This gives you
> > quantities of:
> > back 0
> > chair 0
> > leg 0
> > seat 0
> > table pkg 1
> > table 0
> > Scenario 3:
> > Using our starting quantities at the top – you sell a table pkg before
> > building the pkg or chairs in Peachtree. Once the invoice is posted,
you
> > have quantites of:
> > back 4
> > chair 0
> > leg 16
> > seat 4
> > table pkg - 1
> > table 1
> > You would have to now go to Tasks -> Assemblies, build four chairs AND 1
> > table pkg to get the correct ending quantites of:
> > back 0
> > chair 0
> > leg 0
> > seat 0
> > table pkg 0
> > table 0
> > I’m assuming you see what I mean by "Peachtree doesn’t build assemblies
on
> > demand." If you sell an assembly that currently shows 0 on hand, it
will
> > simply decrease the qty on hand by the number sold – it will not
decrease
> > all of the individual components used to build that assembly.
> > How big of a deal this becomes depends on how complicated your
assemblies
> > are, and how many you sell. I have about 100 different assemblies set
up,
> > but in a given month I sell about 30 – 35. Since all of my assemblies
> > consist of items that are also sold by themselves, I simply invoice the
> > assemblies and let Peachtree show the negative qty throughout the month.
> > Then as part of my month-end procedures I build the necessary number of
> > assemblies to get their qty on hand back to zero, then check the counts
> on
> > my individual components & adjust those quantites as necessary . . .
> > HTH
> > Chad
I thought I went into gory detail about my issue in my last post, so let’s
say, for the sake of argument, I have ten million of everything in
inventory. Here is my question; can PT handle sub-assemblies or do I have
to create one linear assembly item? Quantities in stock are not part of my
scenario. Since PT is not a very robust inventory management system, I
merely need to know if PT (in theory) properly flushes inventory through
sub-assemblies when invoiced.
Thanks for the replies.
"Diane Koers" <dkoers_nosp…@comcast.net> wrote in message
news:3Uva9.99451$Aw4.4254424@bin2.nnrp.aus1.giganews.com…
- Hide quoted text — Show quoted text -
> PT will not build an assembly (or sub assembly) if there are not enough
> individual items on hand to build it. An error message appears.
> —
> Diane Koers
> Co-author Peachtree 8 for Dummies
> "MeTed" <me…@meted.com> wrote in message
> news:N3va9.3910$mb.1609@nwrddc01.gnilink.net…
> > Okay, thanks again, Chad.
> > I understand that I have to do builds in order to get a finished good
into
> > inventory and also understand that it relieves inventory throughout the
> BOM.
> > I guess the main point I’m trying to make is whether or not it is in my
> best
> > interest to create "relational", or sub-assembly, BOMs. In looking at
the
> > data structure of the inventory table, it looks rather linear. I gave a
> > very simple example in my original posting, but maybe it’s best to go
into
> > further detail. I have 48 finished goods that share a similar basic
> > structure of 5 sub-components (the rest of the components create the
> > uniqueness of the item). To save myself a ton of data entry, I was
> wanting
> > to create a sub-assembly for that common component instead of having to
go
> > through all the rigamarole AND was hoping that PT was "intelligent"
enough
> > to relieve the inventory in my main BOM as well as the sub-BOM.
> > "Chad A Gross" <b1s…@NOSPAMhotmail.com> wrote in message
> > news:LIua9.28136$Hu2.16937@news1.central.cox.net…
> > > Ted –
> > > Let’s say you start off with inventory counts as follows:
> > > back 4
> > > chair 0
> > > leg 16
> > > seat 4
> > > table pkg 0
> > > table 1
> > > Scenario 1:
> > > You have enough stock to build 4 chairs and 1 table pkg. If you go to
> > > Tasks -> Assemblies and build 1 table pkg, Peachtree is going to
adjust
> > your
> > > inventory quantities according to the Bill of Materials listed for the
> > table
> > > pkg. Since you indicated that the table pkg consists of 1 table and 4
> > > chairs, Peachtree increases the quantity of table pkg by 1, decreases
> the
> > > quantity of tables by 1 and decreases the quantity of chairs by 4,
> giving
> > > you quantities of:
> > > back 4
> > > chair – 4
> > > leg 16
> > > seat 4
> > > table pkg 1
> > > table 0
> > > Scenario 2:
> > > Using our starting quantities at the top, you go to Tasks ->
Assemblies
> > and
> > > build 4 chairs. This gives you quantities of:
> > > back 0
> > > chair 4
> > > leg 0
> > > seat 0
> > > table pkg 0
> > > table 1
> > > You now go to Tasks -> Assemblies and build 1 table pkg. This gives
you
> > > quantities of:
> > > back 0
> > > chair 0
> > > leg 0
> > > seat 0
> > > table pkg 1
> > > table 0
> > > Scenario 3:
> > > Using our starting quantities at the top – you sell a table pkg before
> > > building the pkg or chairs in Peachtree. Once the invoice is posted,
> you
> > > have quantites of:
> > > back 4
> > > chair 0
> > > leg 16
> > > seat 4
> > > table pkg - 1
> > > table 1
> > > You would have to now go to Tasks -> Assemblies, build four chairs AND
1
> > > table pkg to get the correct ending quantites of:
> > > back 0
> > > chair 0
> > > leg 0
> > > seat 0
> > > table pkg 0
> > > table 0
> > > I’m assuming you see what I mean by "Peachtree doesn’t build
assemblies
> on
> > > demand." If you sell an assembly that currently shows 0 on hand, it
> will
> > > simply decrease the qty on hand by the number sold – it will not
> decrease
> > > all of the individual components used to build that assembly.
> > > How big of a deal this becomes depends on how complicated your
> assemblies
> > > are, and how many you sell. I have about 100 different assemblies set
> up,
> > > but in a given month I sell about 30 – 35. Since all of my assemblies
> > > consist of items that are also sold by themselves, I simply invoice
the
> > > assemblies and let Peachtree show the negative qty throughout the
month.
> > > Then as part of my month-end procedures I build the necessary number
of
> > > assemblies to get their qty on hand back to zero, then check the
counts
> > on
> > > my individual components & adjust those quantites as necessary . . .
> > > HTH
> > > Chad
Short Answer – No.
If you have 10 million of each item that makes up the sub-assembly, but your
sub-assembly qty on hand is 0 (you haven’t explicitly built any for stock),
then PT will not let you build the master assembly, because it says you
don’t have enough stock on hand to build the master assembly. In which case
you would be better off setting up one linear assembly item – which would
save you the steps of having to build both the sub-assemblies & master
assemblies . . .
Chad
Sounds good. This is my first experience w/ PT and didn’t want to assume
that the functionality I’m looking for is inherent to PT.
"Chad A Gross" <b1s…@NOSPAMhotmail.com> wrote in message
news:_swa9.28595$Hu2.4546@news1.central.cox.net…
- Hide quoted text — Show quoted text -
> Short Answer – No.
> If you have 10 million of each item that makes up the sub-assembly, but
your
> sub-assembly qty on hand is 0 (you haven’t explicitly built any for
stock),
> then PT will not let you build the master assembly, because it says you
> don’t have enough stock on hand to build the master assembly. In which
case
> you would be better off setting up one linear assembly item – which would
> save you the steps of having to build both the sub-assemblies & master
> assemblies . . .
> Chad
Peachtree is going to treat the sub-assemblies as just another inventory item.
You either have them on hand or not. If you have 1000 of the components you
need for the subs but have built 0 subs when you try to build the main
assembly Peachtree will tell you, you do not have enough stock on hand.
On the other hand I could have an assembly made up of assemblies that are all
made up of other assemblies.
Peachtree files are basically flat non-relational files. The betrieve engine
is used to translate the data.
One other very important point. Once an assembly has been built and used. For
instance one item of that assembly was created and then deleted, you can not
edit the assembly though you can copy it and rename it.
2003 has some real improvements in the inventory area though assembly handling
isn’t one of them.
Bill Couture