Incorrect Date Data When Creating a "Price List" By API OE_BLANKET_PUB.PROCESS_BLANKET
(Doc ID 2456122.1)
Last updated on OCTOBER 25, 2020
Applies to:
Oracle Advanced Pricing - Version 12.2 and laterOracle Order Management - Version 12.2 and later
Information in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
When we run the core API oe_blanket_pub.process_blanket to create a Price List related to an Agreement,
the "Effective Date" on header of the list and the "Start date - End Date" of the 1st line of the price list, are created with the SYSDATE,
disregarding the dates of the lines of the Agreement. This only happens with the 1st lines of the List.
From the 2nd line, the creation of the lines respects the dates of the lines of the Agreement.
EXPECTED BEHAVIOR
Expects the effective date of the header and the "Start date - End Date" of the 1st line of the price list,
to be created with the value provided to the API
STEPS
The issue can be reproduced at will with the following steps:
1. Run custom wrapper code to call the API
2. Oracle Pricing Manager Responsibility
3. Navigate To: Price List > Price List Setup
4. Query the price list and review the data
shows Sales agreement # 1751 created
Activation Date: 01-MAR-2019
Expiration Date: 01-JAN-2020
Under Main(tab) is one line
item: 202
UOM: T
Activation Date: 02-MAR-2019
Expiration Date 01-JAN-2020
Shows price list
Header effective dates: 29-AUG-2018 through <Null>
List Line has:
item: 202
start date: 29-AUG-2018 --<<<
Qualifier
Sales Agreement Id = 1751
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 |
Cause |
Solution |
References |