Re: Split a top level item.

Stephen

So you now have satisfactory solution for MRP management of this situation.
You may still have an issue with pricing.

I advise against changing list price, or special pricing to something other than you want for the future. In ORD500 you can change price of an individual shipment line to what is desired for that shipment, and not affect any future shipments with that price.

The simplest solution might be a note to accounting that after everything has been shipped to customer and billed normally with BIL500, to do a BIL600 Billing Adjustment, which can be negative or positive, to back out any $ that got over-billed. You might want to do a test of BIL600 to make sure you can do what is desired there.

We are also 405 CD.

Something we do that may be a helpful idea for you.
We have created a dummy non-MRP item called MISCELANEOUS which has an item class of 11 which is ordinarily used for special charges like expedite fees.

We then create an ORD500 line with quantity one of this item, price or no price, notes or no notes, to be picked by shipping at same time as completion of some complex customer order(s) so that a "whole story" ends up on final customer invoice. We do this separately because there may be a whole bunch of shipments involved in some complex situation, then when it is all completed, then and only then we want explanation on billing. Afterwards we inventory adjust to remove results of "shipping out" a non-existent item.

We have also used special lines, but have no control over when they get billed.
Key them into ORD500, then the next time we do billing, there they are.

By using dummy item MISCELANEOUS, we get the "special charge" data into our orders when we have all the facts, and we control which billing cycle they are to go onto, typically same one as the relevant items actually getting shipped to customer.

We also have a dummy item VOID which comes in useful during physical inventory, when some auditor not like us deleting physical inventory tags, instead we make them item VOID with quantity zero, so they all show up same place on some reports.

Al Macintyre

Al,

Thanks for your input.

We are thinking the cleanest way to get what we want is in line with
your third suggestion of creating a new top level part without the
subcomponent and having two orders that comprise the entire top level
part.

Stephen Wheeler


-----Original Message-----
From: macwheel99@xxxxxxxxxxx [mailto:macwheel99@xxxxxxxxxxx]
Sent: Tuesday, May 22, 2007 4:51 PM
To: SSA's BPCS ERP System
Cc: Al me home
Subject: Re: [BPCS-L] Split a top level item.

You can enter a credit quantity in customer orders by using
an RMA. You can also experiment with a negative number in
safety stock.

You can copy engineering of the top item with a slight
change, discontinuing the sub-component involved, where (if
you have room in item #) add a character at the end (we use R
for repair for this purpose), or a character at the beginning
(we use exclamation point to force certain items to the front
of our lists of items).

Al Macintyre

---- Original message ----
>Date: Tue, 22 May 2007 14:19:24 -0500
>From: "Stephen Wheeler" <stephenw@xxxxxxxxxxxxxxxx>
>Subject: [BPCS-L] Split a top level item.
>To: "SSA's BPCS ERP System" <bpcs-l@xxxxxxxxxxxx>
>
>Hello All,
>
>
>
>We have a situation where a customer has placed an order for
a top level
>item, but only wants a subcomponent shipped now for
fabrication
>purposes, and then wants the remainder in approximately two
months. For
>pricing reasons, the order cannot be separated into the
subcomponents.
>We need to be able to show demand in the system for the
component that
>will ship early, and be able to schedule the remaining parts
for later
>production. We need to be able to control MRP messages for
purchasing
>and production.
>
>
>
>One work around we have thought of is to place an order for
the
>subcomponent to create the initial demand, then place a
second order
>later for the top level item when it is needed, issuing a
credit for the
>first order. The problem is in the second order, trying to
tell the
>system we want the top level without the subcomponent. On
the Order
>Entry screen (ORD500), we tried to enter the top level item
and then
>enter a negative quantity for the subcomponent. We receive
an error
>that "Quantity ordered cannot be less than zero."
>
>
>
>We are running BPCS 4.05 CD
>
>
>
>Any input or ideas would be greatly appreciated,
>
>
>
>Stephen
>
>
>
>~~~~~~~~~~~~~~~~~~
>
>Stephen Wheeler
>IT Coordinator
>Ridewell Corporation
>
>stephenw@xxxxxxxxxxxxxxxx
>(417) 833-4565
>Fax: (417) 833-4560
>
>~~~~~~~~~~~~~~~~~~
>
>
>
>--
>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.
>
>Delivered-To: macwheel99@xxxxxxxxxxx
--
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.

Delivered-To: stephenw@xxxxxxxxxxxxxxxx



--
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.

Delivered-To: macwheel99@xxxxxxxxxxx