Blanket Sales Agreement Price Break Modifiers Are Getting The End Dates Updated On The Price Break Details Automatically (Doc ID 2627962.1)

Last updated on JANUARY 15, 2020

Applies to:

Symptoms

ACTUAL BEHAVIOR
Sales Agreement Modifier price break header lines are automatically updated with an end date = BSA header expiration date,
whenever the existing modifier is Updated.

* An additional issue is that this process is updating the Price Break detail lines with an end date as well.
This seems to corrupt the record, so we can not update the record after this update is done.

EXPECTED BEHAVIOR
Expects the end date of the modifier line not to be automatically updated when it is manually set.

STEPS
The issue can be reproduced at will with the following steps:
1. Responsibility: Order Management Super User, Vision Operations
    Go to Sales Agreements-> Sales Agreements
2. Input valid Customer Number, set Activation Date = (past date),
    Expiration Date = (future date, say 16-OCT-2019).
3. Go to Pricing Tab.
    Set New Modifier List
4. In line block , go to Pricing tab.
    Set Item up as a price break header, break line type: Discount, Break type: Point
       start date: 01-OCT-2019
       end date: Null
    Ranges
        0-5                Percent 10
        5-10             Percent 20
     10-9999999  Percent 30
5. Save the BSA.
6. Query modifier from Pricing->Modifier->Modifier Setup.
7. Update the modifier, say update the DFF value, then save.
8. Now the modifier's end date = 16-OCT-2019, same as BSA header expiration date.


Other scenario where issue is replicated:

1. Created BSA
     start date: 01-OCT-2019
     expiration date: 30-OCT-2019
2. Created modifier for Price Break based on item
    start date: 01-OCT-2019
    end date: <null>

3. Enabled debug
4. Updated expiration date of BSA
      start date: 01-OCT-2019
      expiration date: 30-NOV-2019
5. Turned off Debug
6. Reviewed modifier Price Break line details
    It now shows:
      start date: 01-OCT-2019
      end date: 30-NOV-2019


Expectation:
Since the end date was manually changed on the PBH line, does not expect that a change to the BSA header
would automatically trigger that the same date is populated on the PBH line.

Cause

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