One moment please...
 
 
E-WMS   
 

How-to: use E-WMS web services for guided processes

This document describes how to use E-WMS web services for guided processes.

The E-WMS web service offers the possibility to exchange E-WMS transaction types, using the Exact Entity (Action) Service.

The web service adds extra WMS functions to the Action Service of the Exact Entity Services.

Guided processes are processes where you send something to the scanner first and return the realizations, for example the standard order picking process.

Supported transaction types

The following E-WMS guided transaction types (EES 'Actions') are available:

  • WMS_ExportGuidedReceipts
  • WMS_ImportGuidedReceipts
  • WMS_ImportGuidedSalesOrders
  • WMS_ExportGuidedSalesOrders

All transactions support SKU numbers.

Basic workings

The WMS web service gets the advice from the WMS RF tables and creates transactions in the WMS RF tables, as a scanner would do.

These transactions can be read back and processed by using the WMS Control Center, or by using the WMS RF Service.

The EES WMS actions offer only very minimal validation of the offered transactions, since the imported transactions will be read back and validated by a WMS control center or WMS RF service, which already offers all required validations.

The web service itself will only return functional error messages for mandatory data which was not provided, such as a missing order number or item code. In that case the transaction will not be imported.

Recommended process

For all guided processes via services the recommended process is:

  1. When you want to use the services independent from existing physical scanners set up a separate scanner in Exact Globe Next via menu System ? WMS ? Scanners ? Scanners.
  2. When you want to use auto queue to automatically send the advice to this ‘service’ scanner create a new group and link only the scanner created to this group and use the settings in System ? WMS ? Service schedules ? Scanner group filters to define when to give the advice to this scanner.
  3. Retrieve the advice for the scanner ID defined in step 1 via the guided export services. The lines for this scanner ID are retrieved line by line. The field DateTimeExported is updated in table CSPickITRFSubLine to indicate the line has been exported and next line based on sequence number will be exported in next call. All fields defined in the metadata file in the XMD folder of your Exact Globe Next installation (for example XMD\Exact.Metadata.Action.WMS.ExportguidedSalesOrders for guided fulfillments) are exported
  4. Use the guided import service to post the realization to the RF tables. You can use the following properties:

    Property

    Description

    TransactionID

    Mandatory, use the transactionID from the exported line. This is part of the key to link the realization to the advice. A validation is done if it exists in the RF tables.

    HeaderID

    Mandatory, use the HeaderID from the exported line. This is part of the key to link the realization to the advice. A validation is done if it exists in the RF tables.

    SublineID

    Mandatory, use the SublineID from the exported line. This is part of the key to link the realization to the advice. A validation is done if it exists in the RF tables.

    SalesOrderNumber

    Only used for fulfillment. Mandatory, use the SalesOrderNumber from the exported line. This is part of the key to link the realization to the advice. A validation is done if it exists in the RF tables.

    PurchaseOrderNumber

    Only used for receipts. Mandatory, use the PurchaseOrderNumber from the exported line. This is part of the key to link the realization to the advice. A validation is done if it exists in the RF tables.

    HandTerminalID

    Mandatory it is advisable to use the same handterminal ID as the exported line

    IsLastLine

    The property IsLastLine is used for finishing the current order. When IsLastLine is true, the IsReady field in cspickitrftransaction will be updated to true. And this is the trigger for the wms control center functionality to determine if an order is ready for read-back/import.

     

    If not set to "true", the transaction will be created in the RF tables but will never be read back.

    If you want to offer multiple sub lines for one transaction header (order): you can set IsLastLine=false to add more sub lines to the transaction ID returned by the web service for the first created transaction line. Then only set IsLastLine=true for the last sub line. 

    You can also offer each sub line as a single transaction by always setting IsLastLine=true, then each sub line will have it's own header and will be read back and processed as independent transaction.

    If you offer multiple sub lines with SKU numbers for one transaction, it can be beneficial to set IsLastLine=false for all sub lines, except for the last line where IsLastLine=true.  Then these multiple SKU lines will be read back as one transaction, and processed in Exact Globe Next as one total transaction (SKU numbers are only available in WMS tables). When offering this same transaction where in each sub line IsLastLine is set to 'true', then this will create separate transactions in Exact Globe Next (more records = larger tables).

     

    ItemCode

    Mandatory, validation if it is an existing item, whether item is divisible and whether item is SKU item when SKU data is filled. The itemcode needs to match the itemcode in the exported transaction. When entering another itemcode the transaction will still be done on the item with corresponding transaction, header, subline and orsrg id.

    Warehouse

    Mandatory, free to choose

    Location

    Use location  when setting warehouse locations is on in Globe, free to choose

    SerialBatchNumber

    Optional, free to choose

    Quantity

    Mandatory, free to choose

    DateStart

    Only used when receiving S/B items. Optional, free to choose

    DateEnd

    Only used when receiving S/B items. Optional, free to choose

    SkuItemID

    Only used when receiving new SKU

    IsOuterSkuItem

    Only used for receiving. Needs to be 1 when receiving an outerSKU,

    IsInnerSkuItem

    Only used for receiving. Needs to be 1 when receiving innerSKU, 

    OuterSKU

    Optional, free to choose

    InnerSKU

    Optional, free to choose

    ScanUnit

    Optional, free to choose

    OrsrgID

    Mandatory, use the SublineID from the exported line. This is part of the key to link the realization to the advice. A validation is done if this value exists in the RF tables.

    RecipeID

    Mandatory when the item is an explosion item. When left empty it will be imported as 0 (meaning not an explosion item). When you have explosion items in your database, take the RecipeID from the export.

    SSCCNumber1

    Not mandatory, free to choose

    SSCCNumber2

    Not mandatory, free to choose

Other properties in the XMD are not imported.

Database tables

For more information about the WMS SQL tables, see E-WMS database information: tables used for Control Center and ASP advice/picked lines.

The transaction services are only using the “picking tables”:

  • CSPickITRFSubLine (also contains SKU data)
  • CSPickITRFHeaderLine
  • CSPickITRFTransaction

When receiving a new SKU via the WMS_ImportGuidedReceipts service this SKU will be registered in the SKU master table CSPickITSKUMaster.

For more information about SKU, see E-WMS SKU Management: an introduction.

Related Documents

     
 Main Category: Attachments & notes  Document Type: Support - On-line help
 Category:  Security  level: All - 0
 Sub category:  Document ID: 28.636.139
 Assortment: E-WMS  Date: 18-04-2025
 Release: 417  Attachment:
 Disclaimer