Wrong Agreement End Date Due To "Commitment Period" And "Commit Period UOM" Not Being Cleanup For Prior Records In Relationship Domain (Doc ID 2805161.1)

Last updated on SEPTEMBER 13, 2021

Applies to:

Symptoms

It was reported that after executing 'Auto Asset' functionality for a promotion with 'Track as agreement' checked, the following was observed for the agreement created: the end date was correctly set (1 day ahead) on the
agreement header, on the promotion , on the service bundle. But for the Service Bundle Components the end date was set as one year ahead.


On further investigation it was found that the behavior was caused by some records from S_PROM_ITEM table having  COMMIT_PRD_UOM_CD = Years and COMMIT_PRD=1  and TYPE_CD = CPItems.
The following scenario was identified as being able to produce such records in standard application 21.5 version:


    1. Navigate to Sitemap > Administration - Product > Product Promotions
    2. Create a new bundle promotion BUG32925274-Promo1
    3. Under promotion select Product > Component and add component for product "BUG32925274-CP1".Set Min/Max/Def cardinalities to 1.
    4. Drill down on "BUG32925274-CP1" and under the relationship click on "Modify"
    5. Run this SQL query on the database:

  

    6. Confirm that both COMMIT_PRD and COMMIT_PRD_UOM_CD are null
    7. In the "Commitment" applet, set "Commitment Period" to 1 and "Commit Period UOM " to "Years"
    8. Run the same SQL as in step 5 and check that COMMIT_PRD is 1 and COMMIT_PRD_UOM_CD is "Years"
    9. On the UI, erase the value for "Commitment Period" and "Commit Period UOM" on the UI.
   10. Run the same SQL => both COMMIT_PRD and COMMIT_PRD_UOM_CD are null.
   11. On the UI, set "Commitment Period" to 1 and "Commit Period UOM " to "Years" in the "Commitment" applet again.
   12. In the "Relationship Domain" applet, add a new record, say "Bredband 2".
   13. Run the same SQL  => this time 2 records are retrieved which all have COMMIT_PRD is 1 and COMMIT_PRD_UOM_CD is "Years"
   14. On the UI, erase the value for "Commitment Period" and "Commit Period UOM"on the UI again.
   15. Run the same SQL  => this time we still have 2 records. But only one record has null value for COMMIT_PRD and COMMIT_PRD_UOM_CD. For the other one, COMMIT_PRD remains 1 and COMMIT_PRD_UOM_CD remains "Years".

Changes

Cause

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