Upon Approving the Promotion, the Approval Date and Approval ID Are Null (Doc ID 2129277.1)

Last updated on APRIL 24, 2016

Applies to:

Oracle Retail Price Management - Version 14.1 and later
Information in this document applies to any platform.

Symptoms

In Oracle Retail Price Management (RPM), for a particular promo_dtl_id for which conflict checking is successful and is approved, the approval_date and approval_id are both null.  It is expected that these value should be populated in the RPM_PROMO_DTL table.


 

Steps to Reproduce

Scenario 1:

  1. Create a promotion in RPM UI application.
  2. Approve the promotion.
  3. The promotion is approved and the state is "3".  Approval ID/Date are null in RPM_PROMO_DTL table.


Scenario 2:

  1. Create a promotion in RPM UI application.
  2. Approve the promotion.
  3. The promotion is approved and the state is "3".  Approval ID/Date are populated in RPM_PROMO_DTL table.
  4. Change the promotion back to worksheet status.
  5. Modify the promotion - update the end date, add items, add locs.
  6. Approve the promotion.
  7. Promotion is approved and the state is changed to "3".  Approval ID/Date are null in RPM_PROMO_DTL table.

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms