My Oracle Support Banner

E1: 42: Sales Order Batch Cost Update (R42950) Incorrectly Updates Price Even Though the Version Has Been Set To Update Cost Only. (Doc ID 2972824.1)

Last updated on FEBRUARY 26, 2024

Applies to:

JD Edwards EnterpriseOne Sales Order Management - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

Sales Order Batch Cost/Price Update (R42950) is updating the Price on the Sales Order even though the version has been set to update Cost only. This occurs if the Sales Price Based On Date in the System Constants (P4101) is set to 5 (System Date) but the order was created in the past, which is before the date the job is run.

If Price Update Processing Option is BLANK, Sales Order Batch Cost/Price Update (R42950) SHOULD NOT update the Price

Steps to Reproduce:

  1. In System Constants (P41001) Sales Price Based On Date is set to 5 (System Date) – Today’s date is 9/6/2023
  2. Sales Order was created for 2 units at a Price of 50.00 on 8/29/2023
  3. The Base Price on the Item Today (9/6/2023) is 70.00
  4. The Sales Order Batch Cost/Price Update (R42950) Version is set to Update Cost but DON’T update price.
  5. Run the Sales Order Batch Cost/Price Update (R42950) Version against the Sales Order today (System Date 9/6/2023) which is several days AFTER the order date and requested date of 8/29/2023.
  6. The price was updated from 50.00 to 70.00, even though the Sales Order Batch Cost/Price Update (R42950) Version processing options were set to only update cost.

Sales Price Based on Date = System Date

Don't Update Price

Price Updated Anyway

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.