A Sales Order for a finished good or work in progress would check to see if any were available. If none or only some were available then it would automatically create an Assembly Order.

Now, the process checks not only what is available (i.e. what is on the shelf), but also if any existing Assembly Orders are making that SKU and of those quantity being made, how many are available (in other words, how many are not on backorder).

This reduces unnecessary Assembly Orders and an unintended build up of stock.

As part of the Document module update, the image button in the Item layout (More.../Image) has been changed to Documents.  This allows users to easily store multiple images of an item.

Trayse Inventory now has a Document module.  Documents are added in the context of other records.  For example, Purchase Orders, Sales Orders, Assembly Orders, Companies, Items,  etc.

Documents are easily added via Drag and Drop.  These are stored externally.

• Removed table occurrence “RECEIPT_processLog”

• Moved unconnected base tables to the top left of the graph.  Previously, they were intermixed with table occurrences that have relationships (TOGs) in order to maintain alphabetical order from top to bottom.  Alphabetical order is still preserved, but divided among two distinct groups: those without relationships are at the top and those with relationships are below.

• Increased white space between TOGs for better readability.

Layout: Item

Card window: Item Location

When adding a new record, the script goes to the warehouse global field, awaiting user input.  The field is a popup and behaves slightly differently on Windows than on Mac.  On Windows, it appeared to populate the field, but it didn’t.  Then, when moving to the next field, the warehouse global field appeared to clear.  To rectify this appearance issue, the warehouse global field is no longer selected when adding a new location for an item.

Layout: Item

Card window: Vendor

When adding a Vendor for an item, all the fields are required, but the UI didn't indicate that.

Updated custom menus for various layouts.

Layout: Sales Order

Changed the message for releasing a sales order.  Message now includes the other records that were created, including (when appropriate) Assembly Orders, Purchase Orders, and Pick.  Multiple Assembly Orders and Purchase Orders can be created on a single release.  The message displays up to 3 of each order type.  When there are more than 3, a 4th line includes the difference and a note to tell the user where to find them.  For example, if 12 Assembly Orders were created, the message is:

ASSEMBLY ORDERS

AO10010

AO10011

AO10011

+9 more.  See More…/Assembly Orders.

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.