We are on an earlier version of BPCS where we use different pricing methods for different customer items, that can sometimes lead to an item being shipped for zero price in error. Once the data is on a customer invoice, it is very difficult to detect, let alone get the customer to pay.

What we now do is run a query/400
(a) listing all customer orders lines shipped today with price zero
(b) listing all customer order lines due to ship with price zero.

We use the customer type to track the personnel in charge of customer service, marketing, quality, engineering etc. associated with each customer, so when I see new activity on one of the customer problem reports, I know who to notify.

When billing, I can bypass selected customer orders, or entire customers, when there are some problems that customer service ought to clarify first.

I run the billing at end day, after the shipping has completed. This is one of several reports I run, looking for possible errors in the data of what was shipped today, due to ship soon. At this time of year there is high risk that orders that should be due early in 2009 will be keyed as due early in 2008, and early in 2009, risk that some orders due in 2009 keyed as due in 2008. Plus same kind of error elsewhere in BPCS.

It is easier for us to spot that kind of error nowadays because one of the reports I distribute with daily billing is a PAST DUE report ... list & total all customer order lines with a due date to ship prior to today. It shows minimum due date by customer & whole report.

New problems I notified people about yesterday:
* now that we know the dates of physical inventory, what about all these customer orders due to ship during those dates?
* here is a list of items with no usage (shipped to customer or used in production) in 2008 ... in some cases our safety stock is correct for prior year's customer requirements, but is now driving excess unwanted inventory

New problem I did figure out what to do about it
* Field in shipping, how many shipped, can key in (by accident) negative # ... various programs down stream ASSUME positive # there, do not show the sign ... the invoice becomes a credit memo

New problem I not yet figured out what to do about it:
* We key in delivery ticket manually (it would be nice if it was automatically generated like orders etc.) ... someone did a shipment without specifying the ticket #. Some reports won't run on shipments with none. But it got billed.

Al Macintyre

Dan Sweeney :wrote:

Christopher,

Currently there isn't any configuration setting nor system parameter in
ERPlx that will tell the system that a zero priced order line is in
"error".

A modification to the order processing program that prices the order
line will need to be enhanced in order to satisfy your companies
management.

-----Original Message-----
From: ChristopherWynn@xxxxxxxxxx
Sent: Friday, December 05, 2008 10:12 AM
To: BPCS ERP System
Subject: [BPCS-L] ORD700 - Add edit for zero price

Currently all customer orders are priced using special pricing. The
nature of our business requires that each customer/ product combination
have its own price and effectivity dates. When a price expires ORD700
will issue a warning message(UME6055) stating the price is zero but will

allow the order line to be accepted. This has resulted in zero priced
lines being shipped on a few occasions. Our management would like the
system the prevent zero priced order lines from being entered. We
would
like to make the zero price edit an error instead of a warning. Is
there
a way to configure the system to do this? Or is a modification
required?
We are using ERP LX version 8.3.1. We are new to BPCS having migrated

from PRMS recently.

Christopher Wynn
AB Mauri Foods, Inc./Ohly Americas
Information Systems
314-392-0876



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.