Currently using BPCS Version 8.2.01 on iSeries V5R2.

We are having an issue with Shipping Patterns and Lead-time.  A release is 
received from our customer (EDI) and when the release is pulled into the RMS 
contract in BPCS the shipping pattern will be used.  When the release is 
converted to the order, the lead time is picked up and new dates are calculated 
but the dates are not correct.  The shipping pattern and lead time do not seem 
to be working as they should.

If the item in the release is a firm requirement, the new calculated date 
(still off) will be pulled through for scheduling and MPR.  

If the line in the release is a forecast item only, the shipping lead time is 
not brought through to Scheduling and MPR.  The customer request date is used 
when MPS and MRP are calculated.  We may have a shipping lead time of 31 days 
but the system does not consider this and we would not order our components in 
time to make this build.  

It is a good thing that our Materials Department is aware of these issues and 
ensures that all Customer Orders are covered and production has components when 
time to build.  NOTE:  Our Scheduler will not rely on BPCS and has a 
spreadsheet in which he maintains using information given to him from Customer 
Service.

The first time this issue was reported to SSA, we were told that BPCS was 
operating as it should but SSA did create an enhancement BMR.  We were 
persistent and now this BMR has been escalated.

Is there any other companies that are also experiencing this problem and how 
are you dealing with this issue?

Sincerely,
___________________________________________
Sylvia L. Dufour
Business Analyst
Schukra of North America Ltd.
 



 
The information contained in this e-mail message is intended only for the 
personal and confidential use of the recipient(s) named above. If the reader of 
this message is not the intended recipient or an agent responsible for 
delivering it to the intended recipient, you are hereby notified that you have 
received this message and any attachments in error and that any review, 
dissemination, distribution, copying or alteration of this message and/or its 
attachments is strictly prohibited. If you have received this message in error, 
please notify the sender immediately by electronic mail, and delete the 
original message.  Sender employs reasonable precautions to ensure against 
transmission of viruses and other destructive e-mail attachments; however, it 
makes no warranties that this message or any attachment thereto is free from 
viruses.  Recipient is responsible for the protection of its own system; under 
no circumstances shall Sender be liable or any actual or consequential damages 
that may result from any inadvertent transmission of a virus or other 
destructive e-mail attachment.   Recipient is cautioned not to open any file or 
attachment about which there is any uncertainty.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.