Follow

April 4, 2018 Release Notes

We have moved to a once every two weeks release cycle. Here are the latest changes scheduled for release on Wednesday, April 4, 2018.

New Transfer Order Logic

The standard design for accommodating in-transit transfer orders from one source location to a destination location is by placing the transit order in an in-transit location. However, this approach was not suitable for companies that do not have in-transit location in their ERP. As a result, a new in-transit order logic has been introduced.

A new status has been created in DemandCaster with a designation of "U" for unfulfilled. If transfer orders are unfulfilled (not yet issued from the source location) the status "U" will be assigned to the transfer order. This status will then explode from the destination as an unfulfilled requirement against the source location thereby netting the available inventory at the source. If the transfer order is fulfilled, it will be assigned a status of "O" or as a secondary option "P" and will not explode against the source since the inventory has already been issued at the source.

Image 1: Transfer Orders at Destination

Image 2: Transfer Orders passed from Destination to Source

A more detailed explanation is provided in the Vendor Orders section of the data tables documentation.

This new feature will provide an easier way to accomodate transfer order logic in a manner that does not require an additional location for in-transit orders. The benefit, your SKU count will be lower and your requirement plan will be faster.

If you would like to change your transfer order logic to accomodate this feature, please contact support by either creating a ticket in support or emailing support@demandcaster.com.  Please note that there could be a nominal charge to make the change to your existing integration.

Capacity Planning Improvements for NetSuite

New scripts have been deployed to extract work center, routing, and job progress data necessary for capacity planning for NetSuite users.

Auto Refresh Resources

In the past, when changes were released to production, at times certain javascript/css updates were not automatically refreshed causing some users to not see updates. The process has been updated to ensure those resources are always updated when changes are deployed.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk