_images/swm000.png

Administration

The following section describes the administration features and configuration setup within SuiteWM.

Administration Options

SuiteWM provides a comprehensive set of administration features to:

  • View Order Status Summary
  • Reprint documents
  • Reprint labels
  • Regenerate documents
  • Regenerate labels
  • Regenerate EDI
  • Reset orders
  • Reset Entire Batch
  • Cancel orders
  • Edit addresses
  • Edit other key order attributes
  • Set Order to Unreleased Status
  • Request VICS Bill of Lading (BOL)
  • Request Commercial Invoice (CI)
  • Confirm All Remaining Picks
  • Confirm Individual Picks Manually
  • Request Freight Quote
  • Request Freight Quote Status
  • Assign Task(s) to Employee
  • Request Global-e Manifest
  • Request BorderLinx Manifest
  • Request Passport Manifest
  • Check Security Protocol
  • Display Negative Inventory
  • Change Your Password
  • Manage User Credentials
  • Manage Workstations

Operations & Usage

SuiteWM delivers all administration options using a very simple approach that prompts an operator to enter either a fulfillment (order), batch pick ID, container ID, purchase order, or item (for item history), and then presents an array of options/action that can be taken on that order based on its current status. This is highly dynamic process that takes a potentially complex process and makes it very simple for the operator.

Tip

This feature is a very effective “one-stop-shop” for all information (and history) relating to an order, and should be the first place to begin any customer service research relating to an order.

For example, an operator enters a container ID in the Administration page shown below:

_images/swm780.png

SuiteWM locates that order based on the container, order , or batch ID scanned and presents all of the information that is known about that order.

_images/swm790.png

If the order is shipped, the operator can simply select the shipped container and SuiteWM will present a detailed view of all attributes related to that specific container.

_images/swm796.png

Specific picks for this container can be easily reviewed by clicking Picking Details on this page

_images/swm795.png

Numerous Administrative options can be invoked by selecting from the Drop Down and clicking Take Selected Action. The option shown vary with the state of the order. In this example below, the options are shown for an order that has already been shipped.

_images/swm797.png

The Batch details for any order can also be reviewed by clicking the Batch link

_images/swm798.png

A comprehensive Order Status Summary page is also available in SuiteWM under the Administration Page. This option displays a summary of orders in different statues, from release-not-picked, picked-not-packed, packed-not-shipped, and shipped-today. An example of this page is shown below. Any order can be easily accessed with single click, which delivers the operator to the Order Summary page shown above.

_images/swm799.png

Reprinting Documents

This Action will reprint any documents previously created. It does NOT regenerate the document; rather it retrieves the previously created PDF and directs that specific file to the printer. This is useful if a hardware-based printing problem is encountered.

Reprinting Labels

This Action is the same as reprinting documents, except that it is specific to labels such as ship labels. This will retrieve any previously created ZPL-based labels and direct them to the printer. Like reprinting documents, this is useful if a hardware-based printing problem is encountered.

Regenerating Documents & Labels

If a document or label needs to be regenerated because a condition or data has been changed since the original document was printed, this is the Action that should be selected by the operator. This action will initiate the necessary SuiteWM processes to regenerate the requested document or label. If a shipping label is to be regenerated, it will create a new tracking ID for the package.

Resetting Orders

This Action can only be performed if picking has not yet begun. Resetting an order will remove the order from any wave and batch. It will also deallocate any inventory and places the order in the initial state it was received in from the ERP.

Canceling Orders

Order cancellation is always a challenge in the warehouse, especially if picking has begun on the order. This Action, however, keeps the process very simple to manage, even after picking has begun. In fact, unless you have shipped the order, SuiteWM will allow you to cancel a fulfillment order, and manage the re-slotting of any picked inventory without the need to perform any inventory adjustments or re-receipt of the inventory.

To begin, the authorized operator would access the Administration Menu and enter the order number or scan one of the containers on the order. The page is shown below. Based on the status of the order, SuiteWM will list a variety of valid actions to take for this order. In this case, the order has begun picking, so an option to cancel is order is shown.

_images/swm587.png

Of course, if picking has not yet begun, the operator can also cancel the order as shown on the page below.

_images/swm588.png

Once the “Action to Take” is selected, the operator will be sequenced through a series of validation steps (to confirm the action requested). Once confirmed, the order will be canceled in SuiteWM. The inventory and containers will be automatically moved to a specifically designated bin or staging area for “return to stock” (or RTS) inventory, as is shown below.

_images/swm589.png

This “return to stock” bin may be defined as an allocatable bin, or not. If allocatable, then inventory in this bin is considered available for allocation and pickers could be directed to that bin if the allocation strategy dictates this. If not allocatable, then no picks will ever be allocated to that RTS bin, and you will need to move the inventory out of the bin to an allocatable bin.

To move inventory from the RTS bin, the operator will use the standard Move features to identify the Bin, Item, Quantity to Move. The operator may also simply scan the Container ID on the inventory to initiate a move. The operator can then select the standard “Suggest Bin” option and SuiteWM will direct the operator to the proper bin based on the standard putaway rules setup for this item (see Putaway).

Editing Order Addresses/Attributes

At times, data received from the ERP on the order must be changed at the last minute in the warehouse. This Action permits that, allowing authorized operators to edit order attributes at any time, but before the order is shipped.

Configuration Setup

List of Values (LOV)

SuiteWM business processes are driven by rules and settings defined by the user. While much of this data is standard to NetSuite, rules and setting specific to SuiteWM are defined in a simple custom table named SuiteWM List of Values. The sections below define the usage of this tables and typical values for each business process type.

Attention

Please note that caution should be taken when adding, updating or deleting any of the values noted below since they are all acted upon in real time by SuiteWM. Please conduct appropriate testing of each value set in a Sandbox environment before migrating any new or revised settings to a Production environment.

Rules

Usage:

LOV Type Lov Description LOV Code LOV Attribute 1 LOV Attribute 2
RULE Description of the rule Specific Code not to be changed Value for this rule Secondary Value

Examples:

Type LOV Description LOV Code LOV Attribute 1
RULE Verification of Items During Packing (boolean) packverifyitems TRUE
RULE Allow Full Case Picks pickallowfullcase TRUE
RULE Always Ship Using Less Options (boolean) alwaysshipusinglessoptions FALSE
RULE Always Ship Using More Options (boolean) alwaysshipusingmoreoptions FALSE
RULE API URL for SuiteWM (string) apiurl www.suitewm.com
RULE Auto create Container ID at Move (boolean) autocreatecontaineridatmove TRUE
RULE Auto create Container ID at Receiving (boolean) autocreatecontaineridatreceiving FALSE
RULE Auto Create Lot Exp Date Months (integer) autocreatelotexpdatemonths 0
RULE Bill Duties and Taxes to Separate Accoun (json) billdutiesseparately FALSE
RULE Bypass Pick Profile Page (boolean) bypasspickprofilepage FALSE
RULE Capture Container Type at Pack (Add Only) (boolean) capturecontainertypeatpack TRUE
RULE Capture Container Type at Shipping capturecontainertypeatship FALSE
RULE Capture Container Weight at Packing (boolean) captureweightatpack FALSE
RULE Capture Tracking at Receipt (boolean) capturetrackingatreceipt FALSE
RULE Carrier Suffix Required in NetSuite (boolean) carriersuffixrequired FALSE
RULE Confirm Receipt To PO Location (boolean) confirmreceipttopolocation TRUE
RULE Confirm Receipt Using Transfer (json/boolean) confirmreceiptusingtransfer  
RULE ConnectShip API Active (boolean) connectshipapiactive FALSE
RULE Count (Manual) Verify Item Only (boolean) countverifyitemonly FALSE
RULE Create a Return Ship Label with Shipment (boolean) createreturnshiplabel FALSE
RULE Create an SSCC18 id for shipping containers (boolean) packcreatesscc18 TRUE
RULE Create Item Labels for Return Authorization (boolean) createreturnlabelsforra FALSE
RULE Cycle Count Window (integer) cyclecountwindow 60
RULE Days After Shipment to Archive Data archivedays 90
RULE Decimal Inventory Management Settings (json) decimalinventorymanagement {“”active””: false...
RULE Default Cycle Count Plan Parameters (json) defaultcyclecountplanparameters {“”A””:33,”“B””:20,
RULE Default Receiving Status (string) defaultreceivingstatus GOOD
RULE Default Ship Label Logo (url) defaultshiplabellogo  
RULE Disable Putaway Dropdown List (boolean) disableputawaydropdownlist FALSE
RULE Display Item Alias with Item Name (boolean) displayitemalias FALSE
RULE Do Not Allocate Days After Ship Date (integer) donotallocatedaysaftershipdate  
RULE Do Not Set ERP Ship Cost (boolean) donotseterpshipcost FALSE
RULE Enable Accept All Cycle Counts (boolean) enableacceptallcyclecounts FALSE
RULE Enable Alert Page (boolean) enablealertpage TRUE
RULE Enable Ascending Order Putaway Sequence (boolean) enableascnedingputawayseq FALSE
RULE Enable Auto Pack Remaining to Current Container (boolean) enableautopackremaining TRUE
RULE Enable Batch Shipping (boolean) enablebatchshipping FALSE
RULE Enable Borderlinx API (boolean) enableborderlinx TRUE
RULE Enable Capture of Daily Effective Rate (boolean) enablecaptureofdailyeffectiverate TRUE
RULE Enable Capture Photo at Receipt (boolean) enablecapturephotoatreceipt FALSE
RULE Enable Code Date Entry (boolean) enablecodedateentry FALSE
RULE Enable Container Pick Operations (boolean) enablecontainerpickoperations FALSE
RULE Enable Cube Based Putaway (boolean) enablecubebasedputaway FALSE
RULE Enable Direct Multi Tracking Entry (boolean) enabledirectmultitrackingentry FALSE
RULE Enable EasyPost Rate Shopping (boolean) enableeasypostrateshopping FALSE
RULE Enable Electronic Commercial Invoice (boolean) enablecommercialinvoice FALSE
RULE Enable Freighquote API (boolean) enablefreightquote FALSE
RULE Enable Global-E API (boolean) enableglobale TRUE
RULE Enable Local Scale Driver (boolean) enableLocalScaleDriver FALSE
RULE Enable Manual Freight Charge Entry (boolean) enablemanualfreightchargeentry TRUE
RULE Enable Order Line Edting (boolean) enableorderlineediting TRUE
RULE Enable Order Type For Pack Rule (boolean) enableordertypeforpackrule FALSE
RULE Enable Pack Add (boolean) enablepackadd FALSE
RULE Enable Paper Pick Operations (boolean) enablepaperpickoperations FALSE
RULE Enable Passport API (boolean) enablepassport FALSE
RULE Enable Putaway Logic for Last Known Bin (boolean) enablelastknownbin TRUE
RULE Enable Putaway To Assigned Bin (boolean) enableputawaytoassignedbin FALSE
RULE Enable Receiving Message Display (boolean) enablereceivingmessagedisplay FALSE
RULE Enable Returnly API (boolean) enablereturnly FALSE
RULE Enable RocketShipIt V2 (boolean) enablerocketshipitv2 TRUE
RULE Enable Ship Label Logo (boolean) enableshiplabellogo TRUE
RULE Enable Shipment Consolidation (boolean) enableshipmentconsolidation FALSE
RULE Enable Shipping Acount Override by Shipping Service (boolean) enableaccountoverridebyservice FALSE
RULE Enable SPS V2 (boolean) enablespsv2 TRUE
RULE Enable Unlimited Item Alias (boolean) enableunlimiteditemalias FALSE
RULE Enable Wave Picking (boolean) enablewavepicking FALSE
RULE Enable Zone Order Picking (boolean) enablezoneorderpicking FALSE
RULE FedEx SmartPost Hub ID (string) smartposthubid 5802
RULE Final Shipping Container Used in Picking (boolean) pickintoshipping FALSE
RULE Inactive APIs (string) inactiveapis  
RULE Integrated Packing/Shipping Process (boolean) packandship FALSE
RULE Integrated Pick/Pack Process (boolean) pickandpack FALSE
RULE Manual Weight Required for Containers (boolean) manualweightrequiredforcontainers FALSE
RULE Maximum Batches Created in a Single Wave (integer) maximumbatchtasks 100000
RULE Maximum Cluster Created in a Single Wave (integer) maximumclustertasks 100000
RULE Maximum Numeric Quantity Allowed (integer) maximumnumericquantityallowed 10000
RULE Maximum Super Batches Created in a Single Wave (integer) maximumsuperbatchtasks 100000
RULE Maximum Totes in a Cluster (integer) pickmaximumtotes 4
RULE Maximum Totes in a Super Batch (integer) pickmaximumsbtotes 6
RULE Only Ship Single Containers (boolean) onlyshipsinglecontainers FALSE
RULE Pack Edit Do Not Create SSCC18 (boolean) packeditdonotcreatesscc18 FALSE
RULE Pack Verify Prohibited Task Types (String) packverifyprohibitedtasktypes NONE
RULE Pack With Order as Alias Container ID (boolean) packwithaliascontainerid FALSE
RULE Pre-Assigned Container IDs Defined During Picking (boolean) pickpreassignedcontainers  
RULE Print an SSCC18 id at packing for shipping containers (boolean) packprintsscc18 FALSE
RULE Print Case Labels At Receiving (json/boolean) printcaselabelsatreceiving {“”print_label ...
RULE Print Copies of Commercial Invoice (int) commercialinvoicecopies 1
RULE Print Ship Labels At Packing (json/boolean) printlabelsatpacking  
RULE Print Unit Labels At Receiving (json/boolean) printlabelsatreceiving {“”print_label ...
RULE Priorty pack destination suffix (string) priortypackdestinationsuffix .P
RULE Prompt Operator for Count Attribute (string) capturecountattribute  
RULE Receipt Documents Managed by Location (boolean) receiptdocumentsmanagedbylocation FALSE
RULE Receipt of Multi-Item Container Allowed (boolean) receiptmultiitemcontainer TRUE
RULE Receipt Percent Overage Allowed (20 = 20% Overage) (integer) receiptpercentoverageallowed 20
RULE Return Service Codes for Carriers (json/boolean) returnservicecode {“”UPS””: “”03””,...
RULE Ship Confirm: Do Not Alter ERP Line Items (boolean) donotaltererplineitems FALSE
RULE Skip Container Type Capture at Packing (boolean) skipcontainertypecaptureatpacking FALSE
RULE Skip Item Verification at Picking (boolean) skipitemverificationatpicking FALSE
RULE Skip Pack Complete Alert (boolean) skippackcompletealert FALSE
RULE Skip Pack Directive (boolean) skippackdirective FALSE
RULE SSCC18 GS1 (string) sscc18gs1 8889120
RULE SuiteWM Version 1 is Active (boolean) version1isactive FALSE
RULE Suppress BOL (boolean) suppressbol FALSE
RULE Suppress Confirming Adjustments to ERP (boolean) suppressconfirmingadjustmentstoerp FALSE
RULE Suppress Receiving Memo (boolean) suppressreceivingmemo FALSE
RULE Suppress Using Container ID (boolean) suppressusingcontainerid FALSE
RULE Threshold Maximum Quantity for Batch/Super Batch/Wave Units (integer) pickbatchmaximumunits 10000
RULE Threshold Quantity for Batch/Super Batch (integer) pickbatchthreshold 30
RULE Use Standard ASN Object (boolean) usestandardasnobject TRUE
RULE Verification of Items During Packing (boolean) packverifyitems TRUE

JSON for Decimal Inventory Management Rule:

{
    "active": true,
    "step": "0.25",
    "format": "#.##"
}

JSON for Print Labels at Receiving Rule:

{
    "print_label_default" : "YES",
    "print_label_default_qty" : 1
}

Roles

Usage:

LOV Type Lov Description LOV Code LOV Attribute 1 LOV Attribute 2
ROLE Description of the role Specific Code that will match value in Role Table Sorting order ERP Internal ID for this Role

Examples:

LOV Type Lov Description LOV Code LOV Attribute 1 LOV Attribute 2
ROLE Administrator ADMINISTRATOR 1 3
ROLE Manager MANAGER 2 4
ROLE Operator OPERATOR 3 5

The LOV Table relates to the ROLE table in SuiteWM which is defined as follows:

Role Name Role Definition
The LOV Code being used for this role A JSON Object which describes this role

Examples:

Role Name Role Definition (see sample bject below)
ADMINISTRATOR {“UnAuthorizedForms”: [“none”],”UnAuthorizedOptions”: [“none”]}

Tip

It is very useful to use a JSON Editor to compose/validate this data, and then post into this table. It is intended that this data is established once at the beginning of a project sine it is rarely changed.

Below is a sample Role Definition:

{
   "UnAuthorizedForms": [
       "Pack",
       "Count",
       "Search"
     ],
   "UnAuthorizedOptions": [
       "ReviewResults",
       "ResolveCounts",
       "SearchforPOASN"
   ]
 }

Note

Any option, button, or form can be de-authorized for any role.

Location

Usage:

LOV Type Lov Description LOV Code LOV Attribute 1
LOCATION Description of Physical Warehouse Location ERP Internal ID for this Physical Location Sorting order

Examples:

LOV Type Lov Description LOV Code LOV Attribute 1
LOCATION East Coast Warehouse 1 1
LOCATION West Coast Warehouse 2 2

Note

Locations should only be defined for PHYSICAL sites, and not virtual stores for isolating inventory. The Internal IDs should relate to the “top level” physical sites defined within the ERP.

Division

Usage:

LOV Type Lov Description LOV Code LOV Attribute 1 LOV Attribute 2 LOV Attribute 3 LOV Attribute 4
DIVISION Description of the Division ERP Internal ID for this Division Sorting order Prefix used in packlist processing Return Address JSON BOL Material Class

Examples:

LOV Type Lov Description LOV Code LOV Attribute 1 LOV Attribute 2 LOV Attribute 3 LOV Attribute 4
DIVISION Retail 2 1 RT PO Box 325, Highland MD, USA Electronics
DIVISION Wholesale 5 2 WS PO Box 543, Highland MD, USA Electronics

Note

Division may frequently be associated with ERP’s or NetSuite’s “Class” attribute, but it need not be. Distinct Divisions should only be defined if the operations are to be maintained distinctly within the warehouse.

Classification

Usage:

LOV Type Lov Description LOV Code LOV Attribute 1
CLASS Description of the Class ERP Internal ID for this Class Sorting order

Examples:

LOV Type Lov Description LOV Code LOV Attribute 1
CLASS EQUIPMENT 8 1
CLASS APPAREL 5 2

Ownership of Inventory

Usage:

LOV Type Lov Description LOV Code LOV Attribute 1 LOV Attribute 2
OWNER Description of Ownership for Location ERP Internal ID for this Owner Location Label Displayed During Receipt Putaway Strategy Rule Set

Examples:

LOV Type Lov Description LOV Code LOV Attribute 1 LOV Attribute 2
OWNER Consignment for East Warehouse 445 Consignment PUT-CONSIGN-EAST
OWNER Consignment for East Warehouse 446 Consignment PUT-CONSIGN-WEST

Note

This feature must be used with the rule setting “Confirm Receipt To PO Location (boolean)”. All items that are received against a matching PO Location will inherit the Putaway Strategy defined for that class of inventory ownership

Workstation

Usage:

LOV Type | Lov Description LOV Code LOV Attribute 1 LOV Attribute 2
WORKSTATION | Description of Workstation location and usage Internal Code Sorting Order A JSON Object which describes this Workstation

Examples:

LOV Type Lov Description LOV Code LOV Attribute 1 LOV Attribute 2
WORKSTATION Pack Station 1 1 1 {“printer_pdf”:”2356”, “printer_raw”:”654”, “scale_id”:”433”}
WORKSTATION Pack Station 2 2 2 {“printer_pdf”:”7366”, “printer_raw”:”399”, “scale_id”:”433”}
WORKSTATION Pack Station 3 3 3 {“printer_pdf”:”3777”, “printer_raw”:”632”, “scale_id”:”367”}
WORKSTATION Receving Dock 1 4 4 {“printer_pdf”:”3232”, “printer_raw”:”777”, “scale_id”:”232”}
WORKSTATION Receving Dock 2 5 5 {“printer_pdf”:”6464”, “printer_raw”:”777”, “scale_id”:”232”}
WORKSTATION Receving Dock 3 6 6 {“printer_pdf”:”4644”, “printer_raw”:”777”, “scale_id”:”232”}
WORKSTATION Testing Station 7 7 {“printer_pdf”:”screen”, “printer_raw”:”232”, “scale_id”:”0”}

Below is a sample Workstation Definition for LOV Attribute 2:

{
"printer_pdf": "49600",
"printer_raw": "49604",
"scale_id": "5637",
"scale_name": "toledo",
"start_bin_id":"DOCK.2",
"work_zone":"ZONE-A"
}

Note

The values in LOV Attribute 2 relate to PrintNode IDs associated with each printer or scale used in the operation. If multiple scales are attached to the same workstation, a Scale Name must also be set to identify the specific scale that SuiteWM should be reading. Please refer to section on PrintNode for more details on setup and usage.

Status

Usage:

LOV Type Lov Description LOV Code LOV Attribute 1
STATUS Inventory Status ERP Internal ID for the Virtual Location associated with this Status Internal ID for Operator Site

Examples:

LOV Type Lov Description LOV Code LOV Attribute 1
STATUS GOOD 1 1
STATUS HOLD 9 1
STATUS DAMAGED 12 1

Note

See Rules for attribute “availablestatus” (defaults as “GOOD”) which defines the single status considered as available to allocate inventory. All other statuses defined against inventory will be considered unavailable for standard allocation against orders.

Carrier Service

Usage:

LOV Type Lov Description LOV Code LOV Attribute 1 LOV Attribute 2 LOV Attribute 3 LOV Attribute 4
SERVICE Description of the Carrier Service SuiteWM ID and Sorting Order Carrier’s Internal Code for this Service Carrier ID Carrier SCAC Days in Transit

Examples:

LOV Type Lov Description LOV Code LOV Attribute 1 LOV Attribute 2 LOV Attribute 3 LOV Attribute 4
SERVICE UPS Ground 1 03 UPS UPSN 5
SERVICE UPS Second Day Air 2 02 UPS UPSN 2
SERVICE UPS Next Day Air 3 01 UPS UPSN 1
SERVICE UPS SurePost 4 93 UPS UPSN 5
SERVICE FedEx Ground 5 FEDEX_GROUND FEDEX FDEG 5
SERVICE FedEx Pri Overnight 6 FIRST_OVERNIGHT FEDEX FDEG 1
SERVICE FedEx Std Overnight 7 STANDARD_OVERNIGHT FEDEX FDEG 1
SERVICE FedEx 2 Day 8 FEDEX_2_DAY FEDEX FDEN 2
SERVICE USPS Priority 9 Priority USPS USPS 2
SERVICE USPS Parcel Select 10 ParcelSelect USPS USPS 5
SERVICE USPS Express 11 Express USPS USPS 5
SERVICE Asendia PMA 12 PMA ASENDIA USPS 5
SERVICE Asendia ISAL 13 ISAL ASENDIA USPS 5
SERVICE Asendia IPA 14 IPA ASENDIA USPS 5

Note

As many or few carrier/services may be defined. If the service is received from the ERP as “Standard” and Carrier is specified, SuiteWM will rate shop the best service for the shipment using that Carrier. If the Carrier is NOT specified, SuiteWM will rate shop the best service for the shipment across all authorized Carriers.

Container

Usage:

LOV Type Lov Description LOV Code LOV Attribute 1 LOV Attribute 2
CONTAINER Description of the Container Customer defined ID for the Code Sorting Order A JSON Object which describes this container

Examples:

LOV Type Lov Description LOV Code LOV Attribute 1 LOV Attribute 2
CONTAINER A1 BOX A1 1 {“length”: 8, “width”: 5, “height”: 4,”tare”: 0.45, “id”: “5265”}
CONTAINER A2 BOX A2 2 {“length”: 12, “width”: 5, “height”: 4,”tare”: 0.45, “id”: “4637”}}
CONTAINER B1 BOX B1 3 {“length”: 16, “width”: 8, “height”: 6,”tare”: 0.45, “id”: “4276”}}
CONTAINER M1 MEDIA PACK M1 4 {“length”: 6, “width”: 8, “height”: .5,”tare”: 0.45, “id”: “5462”}}
CONTAINER M2 MEDIA PACK M2 5 {“length”: 8, “width”: 10, “height”: 1,”tare”: 0.45, “id”: “6443”}}

Below is a sample Container Definition for LOV Attribute 2:

{
 "length": 16,
 "width": 12,
 "height": 1,
 "tare": 0.65,
 "id": "52654"
}

Length, width, and height are the external dimensions of the container type. Tare is the empty weight of the container (used any time a weight check is used. The “ID” is optionally used to identify the container type’s internal id assigned in the ERP.

Adjustment Types

Usage:

LOV Type Lov Description LOV Code LOV Attribute 1 LOV Attribute 2 LOV Attribute 3 LOV Attribute 4
ADJUST Description of the Adjustment Type Sorting Order ERP Internal ID for this Adjustment Type ERP Internal ID for the Expense Account to be used Default ERP Class Internal ID Default Department ERP Internal ID

Examples:

LOV Type Lov Description LOV Code LOV Attribute 1 LOV Attribute 2 LOV Attribute 3 LOV Attribute 4
ADJUST LOST LOST 10 2345 3 4
ADJUST FOUND FOUND 11 2345 3 4
ADJUST QUALITY ASSURANCE QA 8 2567 3 4
ADJUST DAMAGED DAMAGED 2 2345 3 4
ADJUST MARKETING MARKETING 3 2789 4 5
ADJUST OTHER OTHER 7 2345 4 5

Item Master Setup

SuiteWM’s Item Master setup is completely driven by the setup in the NetSuite Item Master. SuiteWM will automatically synchronizes it’s data with NetSuite’s data, ensuring that the two are never out of sync if updates are made in NetSuite. Custom forms are provided in NetSuite (as part of the SuiteWM NetSuite “bundle”) to define certain data elements or objects are that unique to SuiteWM (such as “putaway” or “bin allocation” rules that SuiteWM uses). This methodology is used so that ALL Item Master setup is completed in NetSuite. In fact, there is not even an option to edit or change Item Master data in SuiteWM; this eliminates the possibility of local changes being made that are not synchronized across the enterprise, a problem characteristic to most WMSs.

Any data element that is accessible using a NetSuite “Saved Search” can be synchronized with the SuiteWM Item Master, even if the elements are custom-defined for your NetSuite configuration.

Note

Design Reference:

SuiteWM relies on NetSuite (or ERP) Item Master setup data (using standard NetSuite forms). SuiteWM synchronizes to this data on a frequent basis, retrieving each item ID, various aliases such as UPC and/or vendor item code, descriptions, categories, and all other item attributes required to run the operation. Some of the content synchronized with NetSuite (or ERP) is reorganized within SuiteWM to align the content more effectively to warehouse operations. A perfect example of this is the pack hierarchy (optionally) defined for the item. This hierarchy is represented as a JSON object in SuiteWM as defined (in the example) below.

{
   "item_pack_attribute": {
       "logical_each": {
           "name": "unit",
           "qty": 1
       },
       "logical_case": {
           "name": "case",
           "qty": 6
       },
       "logical_pallet": {
           "name": "pallet",
           "qty": 144,
           "ti_hi": {
               "case_per_layer": 6,
               "layers_per_pallet": 4
           }
       },
      "default_container_type":"A10"
   }
}

Hence the “case pack” for an item, if defined, is referenced in the code as:

<?php
   $casePackLabel =  $item['item_pack_attribute']['logical_case']['name'];
   $casePackQty =  $item['item_pack_attribute']['logical_case']['qty'];
?>

Other Properties

SuiteWM also depends on system-level properties to perform it’s integration with NetSuite. Token Based Authentication keys, URLs, Account IDs, as well and system behaviors such a logging level, ftp activation, email alert activation, and more are stored in this startup file. This file resides in the same directory that SuiteWM is invoked from (regardless of the operating system). Different property files and configuration directories may be established for a single installation to create varying behaviors/configurations of SuiteWM. This file is named swm.properties and a sample is shown below:

# Site settings
swm.site=SuiteWM Production at Acuity Global LLC
swm.logrestresponse=false
swm.setexternalid=true

# Token Based Authentication settings
swm.tbaActive=true
swm.consumerKey=#
swm.consumerSecret=#
swm.tokenId=#
swm.tokenSecret=#

#  Processor class settings
swm.processinterface=com.acuity.swmrest.processors.ProcessInterface#

# REST settings
swm.content=application/json
swm.accept=*/*
swm.url=https://rest.na1.netsuite.com/app/site/hosting/restlet.nl?script=#&deploy=#
swm.webservices=true

# FTP settings
swm.ftpactive=false
swm.ftpconnect=ftp.acuityglobal.com
swm.ftpgetdirectory=edi
swm.ftpputdirectory=edi
swm.ftpprocessedprefix=IN_NS_

# API settings (saved searches being used)
swm.search.EMPLOYEE=customsearch_swm_employee
swm.search.ITEM=customsearch_swm_888_item
swm.search.KIT=customsearch_swm_888_kit
swm.search.BIN=customsearch_swm_888_bin
swm.search.LOV=customsearch_swm_888_lov
swm.search.SIF=customsearch_swm_940_sif
swm.search.TIF=customsearch_swm_940_tif
swm.search.PO=customsearch_swm_850_po
swm.search.TO=customsearch_swm_850_to
swm.search.RA=customsearch_swm_850_ra
swm.search.IS=customsearch_swm_850_is
swm.search.RAIR=customsearch_swm_850_ir
swm.search.TMS=customsearch_tms_mapping
swm.search.CUST=customsearch_swm_359_cust
swm.search.INV=customsearch_swm_888_inv
swm.search.SIFSYNC=customsearch_swm_940_sif_sync
swm.search.ITEMINV=customsearch_swm_888_item_inventory
swm.search.ITEMRECENT=customsearch_swm_888_item_recent

# Alert settings
swm.alert=john.doe@email.com
swm.report=john.doe@email.com

# SuiteWM database settings

Release and Configuration Management

SuiteWM releases and changes are managed using a best practice model, employing the latest and most modern approach and technology for configuration management. All source code, documents, and releases are formally managed using modern Integrated Development Environments (IDE) integrated with private GitHub repositories. Changes are formally designed, developed, tested, documented, tagged, and committed to a cloud-based private GitHub repository using the Standard Operating Procedure (SOP) summarized below, before any code is deployed to the customer.

_images/swm992.png

Operations & Usage

List of Values (LOV) are defined in the ERP (NetSuite) using a custom table/form and are synchronized to SuiteWM automatically. For a new value to be active in SuiteWM, this synchonization must take place, and the operator must log out and back into SuiteWM.