Run the ExpectedInventorySynchronize command

To run this command, we must be able to log on to WebSphere Commerce Accelerator as a Logistics Manager or Product Manager role.


Procedure

  1. Use the following URL as an example, paste the following code into a web browser:

        http://myhostname/webapp/wcs/stores/servlet/ExpectedInventorySynchronize?
        <?xml version="1.0" encoding="UTF-8"?><XML>
        <delimiter>|</delimiter> 
        <counter>counter_number</counter>
        <synchronizeraitem>
        <vendor>Store_201_Vendor</vendor> 
        <createtime>2004-01-01-00:00:00.0</createtime>
        <externalid>VPN1234 567 G</externalid> 
        <orderdate>2004-01-01-00:00:00.0</orderdate>
        <openindicator>Y</openindicator> 
        <dateclosed></dateclosed>
        <expecteddate>2004-02-12-00:00:00.0</expecteddate> 
        <originalexpecteddate>2004-01-29-00:00:00.0</originalexpecteddate>
        
        <ffmcenter>ff_cen_ID</ffmcenter>
        <partnumber>part_no</partnumber> 
        <qtyordered>qty_ord</qtyordered>
        <qtyreceived>qty_recd</qtyreceived> 
        <qtyremaining>qty_remain</qtyremaining>
        <deleteflag>0</deleteflag> 
        <radetailComment>Comment for item 4</radetailComment>
        </synchronizeraitem> 
        <synchronizeraitem>
        <radetailid>RA_Detail_ID</radetailid> 
        <dateclosed>2004-01-01-00:00:00.0</dateclosed>
        <qtyremaining>qty_remain_2</qtyremaining>
        </synchronizeraitem> </XML> 

    where:

        counter_number
        Required: Specifies the number of records that are passed to StoredProcedure. The maximum value is 10000. This parameter is required if we are passing XML records.

        Store_201_Vendor
        Specifies the vendor name that is supplying the inventory.

        2004-01-01-00:00:00.0
        Specifies the date and time that the record was created.

        VPN1234 567 G
        Specifies an external identifier, typically supplied by the vendor.

        2004-01-01-00:00:00.0
        Specifies the date that the order was created with the vendor.

        Y
        Specifies if expected inventory may still be received and allocated to back orders (value = Y), or if no further inventory will be received and expected inventory may not be allocated to back orders (value = N).

        2004-02-12-00:00:00.0
        Specifies the date the inventory being adjusted is now expected to arrive. This parameter is required if inserting records.

        2004-01-29-00:00:00.0
        Used to locate an existing RADETAIL when you update an existing record.

        ff_cen_ID
        Specifies the fulfillment center ID. This parameter is required if specifying an RA ID and multiple fulfillment centers exist for that one ID.

        part_no
        Specifies the part number of the inventory record; used with memberid to locate an itemspc_id.

        qty_ordered
        Specifies the quantity that is ordered from vendor in this expected inventory record. If this parameter is not specified when creating a new record, it defaults to 0.

        qty_recd
        Specifies the quantity received to date from the vendor for this expected inventory record. If this parameter is not specified when creating a new record, it defaults to 0.

        qty_remain
        Specifies the quantity still expected from vendor for this expected inventory record. Typically, this quantity equals the quantity ordered minus the quantity received, but could be different if the vendor is unable to ship the total quantity. If this parameter is not specified when creating a new record, it defaults to 0.

        0
        Specifies whether to delete the corresponding RA. A value of 0 indicates that the matching RA and RADETAIL entries should not be deleted.

        Comment for item 4
        Specifies a comment.

        RA_Detail_ID
        Specifies the ID of an RADETAIL to locate an existing record for update.

        2004-01-01-00:00:00.0
        Specifies the date this record was closed.

        qty_remain_2
        Specifies the quantity still expected from vendor for this expected inventory record. Typically, this quantity equals the quantity ordered minus the quantity received, but could be different if the vendor is unable to ship the total quantity. If this parameter is not specified when creating a new record, it defaults to 0.

  2. Use the following output parameters to determine whether the command ran successfully or if any errors occurred.

        ExpRecsRejected
        The number of records from the input that were rejected.

        ExpRecsProcessed
        The number of records from the input that were processed.

        ExpRecsInserted
        Of the number of records that are processed, the number of records that were inserted.

        ExpRecsUpdated
        Of the number of records that are processed, the number of records that were updated.

        ExpRecsReturnCodes
        A return code for each record that was included the input. A value of less than 0 indicates that the error was found before sending it for update or add. Other values are possible; for a list of the other return codes that can result from an update or add, see Stored Procedure error codes.

        ExpRecsWarnMsgs
        Error message information.

        getRejectedRecords()
        The number of records that are rejected because of missing store IDs, expected date, vendor, part number, missing vendors in VENDOR table, and part numbers without item specification.

        getProcessedRecords()
        The number of successfully processed records.

        getExpectedRecordInserted()
        The number of records that are inserted into the RADETAIL table.

        getExpectedRecordUpdated()
        The number of records that are updated in the RADETAIL table.

        getCommandStatus()
        Specifies whether the command was successful or if it failed.

        getWarningMessages()
        Lists warning messages for all the records that are rejected in Vector.

  3. Confirm that the command ran successfully by running a database query to view that the tables were synchronized.


Related tasks
Scheduling ATP-inventory jobs