Don,
Blank should cause the program logic to use the "S" value, so I would expect
that you would see the manufacturing demand and the customer order demand
for the service part. So, I am still unclear about exactly what your users
are seeing (or not seeing) and why they are not able to understand where the
demand is coming from. To me, based on what you have described, BPCS should
be providing you will the information that you need in order to manage this
Item and its demand.
I would be happy to talk with you further about this situation.
Thanks.
Les Mittman
847-858-5235
BPCS Consultant with over 25 years experience
-----Original Message-----
From: bpcs-l-bounces+lmittman=sbcglobal.net@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+lmittman=sbcglobal.net@xxxxxxxxxxxx] On Behalf Of Don
Cavaiani
Sent: Friday, April 23, 2010 9:11 AM
To: BPCS ERP System
Subject: Re: [BPCS-L] FW: Anyone care to comment of this topic ourupcoming
meeting next week?
Les,
That field ICMPSD on all records in CIC is BLANK - looks like that
defaults the program logic into the equivalent of an "S" code value?
Don
-----Original Message-----
From: bpcs-l-bounces+dcavaiani=amerequip.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+dcavaiani=amerequip.com@xxxxxxxxxxxx] On Behalf
Of Les Mittman - SBC
Sent: Friday, April 23, 2010 8:24 AM
To: 'BPCS ERP System'
Subject: Re: [BPCS-L] FW: Anyone care to comment of this topic
ourupcoming meeting next week?
Don:
Demand for a part comes two (2) sources. Dependent demand is from
manufacturing. That is, Component is used on a S.O. or it is a
Component on a BOM that has a Planned Order. Independent demand comes
from external sources such as Customer Orders and Forecasts.
Regardless, both types of demand must be planned for. MRP should be
providing you with this aggregate demand so that Planned Orders for
purchasing are suggested.
So, is the problem that your company is not using the MRP information?
Or, is it that MRP did not see the service demand? If so, then the
problem may be that the MRP Facility Planning Data (CIC) for the Item is
not set to include both independent and dependent demand. The value
should be set to 'S' for "sum" of these demands.
You mentioned that you are viewing an exception report. Is it the BPCS
MRP Exception Report?
The exception report will identify Planned Orders that have messages.
MRP Inquiry (MRP300) is the tool that will easily identify were the
requirements are coming from for an Item Number. So, you would be able
to see there exactly where the demand was coming from.
Does this problem occur frequently? What information, reports, or
inquiries are people looking at who are involved in these situations?
It sounds like you have a procedural or process issue here that needs to
be addressed.
I hope that my comments will be helpful to you.
I would be happy to further discuss this problem with you offline, if
you would like.
Thanks.
Les Mittman
847-858-5235
BPCS Consultant with over 25 years of experience
-----Original Message-----
From: bpcs-l-bounces+lmittman=sbcglobal.net@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+lmittman=sbcglobal.net@xxxxxxxxxxxx] On Behalf Of
Don Cavaiani
Sent: Thursday, April 22, 2010 5:22 PM
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] FW: Anyone care to comment of this topic our upcoming
meeting next week?
We are on 405cd:
Problem Statement: We are losing our on margin because we cannot tell
when viewing the exception report if the demand is a service repair
order.
Example: When we bought part number MT3007 recently we bought a lower
quantity amount because demand was low for production. Not realizing
when we made the buy decision that there was service demand we went
ahead and paid 38% more for the part when we could have passed it on to
the customer.
Don F. Cavaiani
IT Manager
Amerequip Corp.
920-894-7063
"It's amazing what you can accomplish if you don't care who gets the
credit." Harry S. Truman
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
