Layout: Sales Order

Added POs to Sales Order layout.  When an item is added to a Sales Order and there are no available quantities, then that item is on backorder.  A purchase order is created with this item added as a line.  Previously, there was no way to navigate to this purchase order from the Sales Order layout.  Users can now go to More…/POs from the Sales Order layout.

Consolidated these two scripts:

1.     get last order reference number (orderType)
2.     next order reference number

Both scripts get the last reference number of a particular order type.  Since orders are based on a universal data model (i.e. all orders are built on one table) then the Serial Number in the data setup cannot be used.*  The two scripts were created a month apart and each had a slightly different method and handled different use cases.  One handled a UI process (i.e. the user created a new order record) and the other handled scripted processes (order records were created as part of a script).

*This is not entirely true. The presumption of Trayse Inventory is that your company would like to have a readable order number that is prepended with the order type abbreviation AND that these order numbers should be sequential.  That is, purchase orders would have PO10001, PO10002, PO10003, etc. and Sales Orders would have SO10001, SO10002, SO10003, etc.

There is another option, which is to use the serial number feature of the field definition. This would remove sequencing within a given order type.  Instead, order number might be PO10001, EO10002, SO10003, PO10006, EO10004, SO10005, PO10006, etc., or more simply 10001, 10002, 10003, 10004, etc. but among all order types.

Layout: Item | Purchase Order

The On Order quantity was not updating when:

1. a new item was created
2.  a PO was created from the Item layout

(This is using the Create PO button on the bottom right of the Item layout.)

Two scripts were altered: 

1.     select warehouse ID based on warehouse name
2.     set the balance quantity fields (parameters)

Modifications to select warehouse ID… was necessary to fix the bug.  Modifications to set the balance… is precautionary.

See log at bottom of those scripts for details.

Layout: Sales Order | Button: More.../Pick History

Button pointed to “display receipt history for order” instead of “display pick history for order”. 

Script: “display pick history for order” pointed to the Receipt History layout instead of the Pick History layout.  Likewise, the single search criteria was

Set Field [ RECEIPT::orderID ; $orderID ]

Instead of 

Set Field [ PICK::orderID ; $orderID ]

Custom dialog at the end of the script was also updated.

Layout: Menu

Added written instructions for adding a new menu item.  Instructions are to the right of the visible layout, in Layout Mode.

Layout: Sales Order

Changed the Release to Picking… button to Release Sales Order.  Picking is now by order.  Batch picking has been removed.  This is in preparation for creating an Assembly Order (a.k.a. Build Order, Production Order, Manufacturing Order, Work Order, etc.).

Layout: Purchase Order | Field: Vendor

Script trigger passes a JSON object with a misspelled key (“Compnay Type” should be “Company Type”).

JSONSetElement ( 
  "" ; 
  ["Compnay Type" ; "Vendor" ; JSONString] ;
  ["Window Top" ; 160 ; JSONNumber]
)

Should be

JSONSetElement ( 
  "" ; 
  ["Company Type" ; "Vendor" ; JSONString] ;
  ["Window Top" ; 160 ; JSONNumber]
)

Note: Thanks to Humberto Becerra for finding this.

Added WAREHOUSE_global table occurrence.

Layout: Putaway

Created a card window for users to add a location via the Putaway layout.  Previously, a user could add any alpha numeric string in the Actual Location field.  If the string did not correlate to an existing location, it was added to the Location table.  However, only LOCATION::location was updated and not the fields zone, aisle, section, row, or bin.  Now, if a user enters a location that does not exist, a card window appears and offers the user a list of locations for that warehouse or the option of creating a new location.

Layout: Location

The field LOCATION::location was not visible on the Location layout as it was a calculation field and can be seen in the sub-header section (a.k.a. light blue section).  Added the location to the layout, below description and above zone.

Changed LOCATION::location to an auto-enter calculation, creating a string from zone, aisle, section, row, bin.

NOTE: Location should be modified to best suite your warehouse organization.  Zone, aisle, section, row, and bin are commonly used, but may not be required in your situation.  Customize as needed.