E1: 45: Base Price Batch Update (R41830) Does Not Expire Old Price
(Doc ID 1929106.1)
Last updated on NOVEMBER 29, 2021
Applies to:JD Edwards EnterpriseOne Advanced Pricing - Sales - Version 9.0 and later
Information in this document applies to any platform.
When the Base Price Batch Update (R41830) is run to create a new base price, it does create the new base price, but it leaves the original base price with the original expiration date and does not expire the original base price record.
The test below illustrates the issue:
- Go into Work with Base Prices (P4106) in the QBE Line
- Enter Eff Date From > “01/01/2020”
- Enter Eff Date Thru > “12/02/2021
- There are 224 records returned
- Setup a Version of Base Price Batch Update (R41830)
- Set Update Tab Option #1 (Update Base Price File) to 1 (Performs Update)
- Set Adjustments Tab Option #1 (Price Adjustment Type) to % (Adjust price by percentage)
- Set Adjustments Tab Option #2 to 5 (5%)
- Set Effective From Date to 11/24/2021 (Today’s Date)
- Set Effective Thru Date to 12/31/2030
- Run Base Price Batch Update (R41830) with data selection as follows:
- Eff Date From > “01/01/2020”
- Eff Date Thru > “12/02/2021
- Report PDF shows prices were increased 5% and Expiration Dates set on new prices to 12/31/2030
- For example Item 2112 increased from 1,000.00 to 1,050.00.
- Go into Work with Base Prices (P4106) and find Item 2112. There are two prices now:
- Original Price has the Effective Date Thru Date set as 12/31/2025 which was not changed
- Effective Date Thru for the original price should have been set to Today’s Date (Expired)
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