ALLOW_NON_RANGE_ITEM Config Parameter Is Not Working For Customer Order Functionality
(Doc ID 2427125.1)
Last updated on MARCH 14, 2019
Applies to:Oracle Retail Store Inventory Management - Version 16.0.1 and later
Information in this document applies to any platform.
On : 16.0.1 version, Administration
ALLOW_NON_RANGE_ITEM config parameter is not working as expected for customer order functionality.
If the value for this parameter is 'true' and user is creating a transaction (inventory adjustment, RTW etc.) for an item which is not ranged to a store or warehouse, application is raising a warning message 'This item is not ranged for this store. Would you like to range it'.
When user press yes on pop up, system creates the transaction and creates an entry in STORE_ITEM table for the store and non ranged item with status 'Q'.
If user tries to perform same action as above when ALLOW_NON_RANGE_ITEM parameter value is 'false', system does not allow to perform the activity.
However, in case of customer order creation using Webservice application it is not working as expected.
Irrespective of the value of ALLOW_NON_RANGE_ITEM parameter, when webservice tries to create an order for an item which is not ranged to the store, order gets created and at the same time, new entry gets created in STORE_ITEM with status 'Q'.
Steps to recreate:
The issue can be reproduced at will with the following steps:
1. ALLOW_NON_RANGE_ITEM =FALSE
2. Create customer order for an item not ranged to a store.
3. Notice that item is autoranged with status 'Q'
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document