The loadInventoryMismatch service

The LoadInventoryMismatch service goes through several different steps.

From file IO to text translator

The LoadInventoryMismatch service first looks at a particular directory where the node uploads the inventory information in an XML file of the following format:


<?xml version="1.0" encoding="UTF-8" ?>
<Inventory YantraMessageGroupID=”OPTIONAL” ShipNode="REQUIRED" ApplyDifferences=""
 CompleteInventoryFlag="" ReasonCode="" ReasonText="">
    <Items>
        <Item InventoryOrganizationCode="REQUIRED" ItemID="REQUIRED" ProductClass=""
 UnitOfMeasure="" >
            <Supplies>
                <Supply ETA="" Quantity="" Segment="" SegmentType="" ShipByDate=""
 SupplyType="" SupplyReference="" SupplyReferenceType="" SupplyLineReference=""
 AvailabilityType="">
                    <Tag BatchNo="" LotNumber=”” LotAttribute1="" LotAttribute2=""
 LotAttribute3="" LotKeyReference="" ManufacturingDate="" RevisionNo="" />
                </Supply>
            </Supplies>
        </Item>
        <Item ...>
            ...
        </Item>
    </Items>
    <Items>
        <Item ...>
            ...
        </Item>
    </Items>
</Inventory>

That XML is then passed on to the Text Translator.

Note: There are as many messages sent to the JMS queues as there are <Items> nodes. In order to control the number of those messages, make use of the number of <Item> nodes within each <Items> node appropriately. IBM® recommends including 100 <Item> nodes within each <Items> node.