"Consolidate New Order Releases" Flag - Explanation + warning for DCM DCS Integration

Resolving The Problem

Response from Engg:
This flag is NOT for shipment consolidation flag. It does what document says. For example, have this flag checked, then create an order with two lines, make sure one line gets backordered and second line gets released. Then create inventory for the backordered line and run the schedule and release. It will schedule the backordered line and will add that to the same release (i.e. release# 1). When flag is not checked, then it will create release#2 for the backordered line.

By default, if an order is created from console, the DO_NOT_CONSOLIDATE flag in YFS_ORDER_HEADER would be set to N.
When the order has the DoNotConsolidate flag set to "N", the following attributes will be used for matching if they are set up as buyer/seller constraints and routing based constraints.
Attribute in OrderLine
CustomerPONo
MarkForKey
OrderType
DepartmentCode
ItemClassification of the Item on OrderLine

CAUTION: If you are integrating with Yantra DCS make sure you do NOT check this flag.
This is an alert to all who are doing a DCM 5.0/WMS 6.2 implementation. In the Configurator, go to Platform>Business Process>Process Modeling and right click on Order Fulfillment, and click on the related entities tab. There is a check box for 'Consolidate New Order Releases'. What this means is for example, if an order has a release, and you add another line to that order, the release agent will add it to the existing release. Another example is if you have an order that downloaded into WMS and backordered back to DCM, and it releases again, it will release under the same release number.

The big problem here is when DCM sends that same release number down to WMS, it will fail because the order number already exists. Support does have a script for it if you do happen to hit this problem. And this could be a problem with any WMS system let alone ours.

The workaround for now is leave this parameter unchecked.