One reason why the order is repriced is because the price book date has changed. We have the price book date at order header level and at order line level.
Then, my doubt is if you have the list price book properly maintained. When there is a repricing in an item, let's say the 1 January 2004, the list price book should be as follow:
OLD PRICE 1 January 2003-----------31 December 2003
NEW PRICE 1 January 20004-------99999999
This way, the old order lines shouldn't be repriced if their price book date at line level doesn't change, but the new entered lines will appear with the new price.

I hope this is useful
Enrique Calvin
Business Consultant

From: "Sue Underwood" <Suzanna.Underwood@xxxxxxxx>
Reply-To: "SSA's BPCS ERP System" <bpcs-l@xxxxxxxxxxxx>
To: <BPCS-L@xxxxxxxxxxxx>
Subject: BPCS6.04 Order Repricing
Date: Tue, 18 May 2004 14:42:08 -0500
MIME-Version: 1.0
Received: from mc7-f24.hotmail.com ([]) by mc7-s19.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Tue, 18 May 2004 12:53:01 -0700
Received: from mail.midrange.com ([]) by mc7-f24.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Tue, 18 May 2004 12:49:43 -0700
Received: from linux.midrange.com (localhost [])by mail.midrange.com (8.12.8/8.12.8) with ESMTP id i4IJgj6T019892;Tue, 18 May 2004 14:42:45 -0500
Received: from internavgw1.trin.net (nav.trin.net [])by mail.midrange.com (8.12.8/8.12.8) with SMTP id i4IJgSWA019874for <BPCS-L@xxxxxxxxxxxx>; Tue, 18 May 2004 14:42:42 -0500
Received: from corptrnexch3.enterprise.trin.net ([])by internavgw1.trin.net (SAVSMTP with SMTP idM2004051814305512973for <BPCS-L@xxxxxxxxxxxx>; Tue, 18 May 2004 14:30:55 -0500
Received: from CORPTRNEXCH.enterprise.trin.net ([]) bycorptrnexch3.enterprise.trin.net with MicrosoftSMTPSVC(5.0.2195.5329); Tue, 18 May 2004 14:42:08 -0500
X-Message-Info: NDMZeIBu+sqSClWHlypXnTk1GVMv6UZuR7W0606V/V8=
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
Message-ID: <FF529C23A8662B4DA8A968E11939602102AD62DE@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: Thread-Topic: BPCS6.04 Order Repricing
Thread-Index: AcQ9EBryqwguRqh8RyGNamP2dqbFtg==
X-OriginalArrivalTime: 18 May 2004 19:42:08.0775 (UTC)FILETIME=[34CBA970:01C43D10]
X-Virus-Scanned: clamd / ClamAV version 0.70, clamav-milter version 0.70j
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
X-BeenThere: bpcs-l@xxxxxxxxxxxx
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SSA's BPCS ERP System <bpcs-l.midrange.com>
List-Unsubscribe: <http://lists.midrange.com/mailman/listinfo/bpcs-l>,<mailto:bpcs-l-request@xxxxxxxxxxxx?subject=unsubscribe>
List-Archive: <http://archive.midrange.com/bpcs-l>
List-Post: <mailto:bpcs-l@xxxxxxxxxxxx>
List-Help: <mailto:bpcs-l-request@xxxxxxxxxxxx?subject=help>
List-Subscribe: <http://lists.midrange.com/mailman/listinfo/bpcs-l>,<mailto:bpcs-l-request@xxxxxxxxxxxx?subject=subscribe>
Errors-To: bpcs-l-bounces@xxxxxxxxxxxx
Return-Path: bpcs-l-bounces@xxxxxxxxxxxx

Hello all,

We have a division on BPCS 6.04MM, and they have users that just love
Client Server order entry.  Recently this division went through a price
increase.  When orders that were entered prior to the increase date are
maintained, (i.e. change in qty or shipping warehouse) the entire order
is re-priced.  Obviously, the potential is there to overcharge the
customer.  I've been poking around and I don't see a way to prevent

Have you encountered this and how did you work around it?  Is there a
system parm that I'm overlooking?

Thanks for your help.
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.

The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.