Last updated on AUGUST 17, 2016
Applies to:Oracle Retail Merchandising System - Version 13.2.5 to 13.2.8 [Release 13.2]
Oracle Retail Merchandising System - Version 13.1.5 to 13.1.9 [Release 13.1]
Information in this document applies to any platform.
In Oracle Retail Merchandising System (RMS) 13.1.x and 13.2.x, when an order is being created, the base batch is populating the header (WF_ORDER_HEAD) and detail records (WF_ORDER_DETAIL) by referring to the future cost table. Future cost will always have records for the item/supplier relationship (which includes primary and secondary suppliers). In this case, while populating the detail table, the base batch is considering all the records related to the item in future cost.
Expected behaviour: The expectation is that the base batch should consider the item-supplier record for primary supplier only while populating detail record in WF_ORDER_DETAIL table for the respective order.
Steps to Reproduce:
- Prepare the input file in the prescribed format and place the same in the proper directory ($MMHOME/data/in directory).
- Make sure the item selected in the input file has more than one supplier associated, and one is set as primary.
- Go to $MMHOME/oracle/proc/src.
- Run wfordupld.ksh script:
Usage : wfordupld.ksh
wfordupld.ksh $MMHOME/data/in $MMHOME/data/out 1
- Post execution of the same,
(a) query the WF_ORDER_HEAD for the respective customer order reference number to get the generated Wholesale Order No.
(b) query WF_ORDER_DETAIL for the new Wholesale Order No. generated.
- Note that you find multiple records for the same item.
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