Honor Restrict Attribute Check in Manufacturing Transaction API

In certain scenarios, users may want to ignore some of the inventory attribute matches even when the location has restrict attribute checks. For example, for perishable products, if a user is capturing Quarantine status codes in Attribute A and Destination Country in Attribute B, mixing inventories of a SKU with different Destination Country in one location might be permissible/ignored, but mixing different Quarantine status codes can cause actual damage to inventories.

To help with this, when posting a Manufacturing Transaction API request, if "Restrict Inventory Attribute" is enabled for the Location and has "Ignore attribute value for restrict attribute check" configured:

  • the system will ignore matching the attributes of a SKU that is listed in the "Ignore attribute value for restrict attribute check" field of the Location, and allow you to locate the inventories to the location, as long the other attribute values not listed in the "Ignore attribute value for restrict attribute check" matches.
  • The API will fail with error "Location prevents diff invn attr combination for a SKU.Cannot Proceed."  if there is a mismatch in attribute values other than those listed in the "Ignore attribute value for restrict attribute check" field. 

We've also updated existing manufacturing transaction API request behavior so that when the passed lpn_nbr gets CONSUMED, the system now writes IHT 2 instead of IHT4 when the passed lpn_nbr gets CONSUMED.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources