(Doc ID 2374207.1)

Last updated on APRIL 16, 2018

Applies to:

Oracle Warehouse Management Enterprise Edition Cloud Service - Version 8.0.0 and later
Information in this document applies to any platform.


Question 1: The company parameter ORD_DTL_BLANK_INVN_ATTR_B_IS_WILDCARD_OBSOLETE is set to 'no', which means when the Order Detail's "Attribute B" field is empty, the system will only allocate from inventory that don't have Attribute B's.

There's an order a order with no value in order detail inventory attribute B. However, why the system allocated IBLPN for it through a wave run? This IBLPN has a lock code 'LOT', which is configured to be treated as Attribute b.
Question 2: So what's the current parameter to use? User have been this parameter and it has been part of their flow as a result of product team set-up. When did it get the 'obsolete' part appended and as a result become actually obsolete?
Question 3: Explain a bit more? If Users select Attribute B from the 'Ignore order detail attribute' list, does it mean ORD_DTL_BLANK_INVN_ATTR_B_IS_WILDCARD = 'no' or 'yes'?
In this way Users cannot select Attribute B from the "Ignore order detail attribute list". Then should they configure ORD_DTL_BLANK_INVN_ATTR_IS_WILDCARD as 'no' and select the other attributes from the "Ignore order detail attribute list"? Who will be overriding the other?
Question 4: Regarding the company parameter ORD_DTL_BLANK_INVN_ATTR_IS_WILDCARD. Should Users configure it as 'no'? Is it overriding the 'Ignored order detail attribute list' or being overridden by the 'Ignored order detail attribute list'?

To confirm configuration:

Configuration should be:
Select Attribute C, D, E, F, G from 'Ignored order detail attribute list'


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