MCR is Getting Raised When MRP Based Product is Received at a Different Maximum Retail Price (MRP), but SHIPSKU Table Not Updated (Doc ID 2007865.1)

Last updated on AUGUST 17, 2016

Applies to:

Oracle Retail Merchandising System - Version 12.0.5IN to 12.0.7 [Release 12.0]
Information in this document applies to any platform.

Symptoms

In Oracle Retail Merchandising System (RMS) India Localized Version 12.0.5IN, an MRP Change Request (MCR) is getting raised when a Maximum Retail Price (MRP) based product is received at a different MRP.  The ORDLOC table is updated with the new MRP, but SHIPSKU contains the original value.


Steps to Reproduce:

  1. Create an order for MRP based items and take backups of ORDHEAD and ORDLOC tables.
  2. Perform receiving of the order with a different MRP than the MRP at which the order was raised.
  3. Take backups of ORDLOC and SHIPSKU after receiving.
  4. Take backups of RCV_MRP and RCV_MRP_HEAD tables.
  5. Notice the MRP behavior on ORDLOC and SHIPSKU after receiving.  The new MRP is updated in ORDLOC, but SHIPSKU contains the old MRP.

 

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