In an effort to clarify what you may see when doing Kit transactions let me
try to explain one more circumstance that may happen.

If you have an order for 10 Kits and you have 4 of the Kit parents in stock,
BPCS will create the '=' transactions for 6 sets of components to bring the
total Kit parents available up to 10 then you will get the normal 'B'
transaction for the complete 10 Kits.
This often confuses the users because only 6 sets of the components are
being used to fulfill an order for 10 Kits.

You can contact me off line if you want more information.

Bob Kohlndorfer
Unbeaten Path International

-----Original Message-----
From: bpcs-l-bounces+bkohlndorfer=unpath.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+bkohlndorfer=unpath.com@xxxxxxxxxxxx] On Behalf Of
Bailey, Dick
Sent: Thursday, October 23, 2008 3:38 PM
To: BPCS ERP System
Subject: Re: [BPCS-L] A question about kit processing in BPCS

If all the preparing transactions are correct, you should see an =
transaction with a negative quantity, taking each component out of stock,
plus a plus = transaction putting the parent kit into inventory, plus a B
transaction taking the parent kit number out of inventory.

That happens pretty well if the parent is NOT in inventory, and
components are actually in inventory and available so you can allocate them
and ship them. When a parent is in inventory and available, it gets
allocated and shipped and the components are ignored. If the parent is NOT
in inventory and one component is not avaivable, the components cannot be
allocated, so you get only a shipment of the parent kit and it goes
negative.

I hope this is clear, if not you can contact me direct. We have been
using BPCS kits (in 8.0 now) for 7-8 years. It is critical that somebody
manages the inventory records carefully.

Dick Bailey
MCFA, Inc.

-----Original Message-----
From: bpcs-l-bounces+dick.bailey=mcfa.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+dick.bailey=mcfa.com@xxxxxxxxxxxx] On Behalf Of
Hermann, Robert G.
Sent: Tuesday, October 21, 2008 4:23 PM
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] A question about kit processing in BPCS

I work for a fairly large manufacturing company which is getting ready to
introduce a new item which we think can best be handled by the use of kits.
We are on BPCS 5.1 which we century dated ourselves using the Focus/2000
product.

We have no experience with kits and very little documentation to go on.
My question is: What inventory transactions should we expect to see
regarding both the parent (kit) and component children? Our kit parent is
composed of one drum of component child "A" and one drum of component child
"B". So, when we ship confirm a quantity of one kit parent, what inventory
transactions should I see in the ITH file?

The reason I am asking this question is that I have been running tests on
our development AS/400, and I have been getting conflicting results.
During my first test, I could have sworn that I saw a positive "="
transaction and a negative "B" transaction for the parent, and a negative
"=" for each component. On subsequent tests, I have been seeing only a
negative "B" transaction for the parent. I do note that we "placed" some
parent items in inventory for another reason; I searched the BPCS-L archive
for posts regarding kits, and reading these has me thinking that by placing
some parent items in inventory, we interfered with "normal" kit processing
and this is why no inventory transactions were made for the component
children.

Any information you provide on this topic will be greatly appreciated.
Thank you.

-- Bob Hermann

--
This is the 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.

Delivered-To: Dick.Bailey@xxxxxxxx

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.