As a senior developer I often have to throw together reports and forms for inquiry and analysis of data.  Some of the reports and form require data from multiple tables (more than 2). In this case I like to use views because the speed of retrieval is faster than joining a bunch of table using code whether using complex query or select statements. The view is not stored data but rather dynamically created only when the view is accessed.  I can pick what fields I want use on the view which makes the view useful because now I am working with only the data relevant to my need. I can create aggregate fields which will compute sums, counts, max and min values. Furthermore, I can use my view like I would use a table to retrieve data using queries via X++ or on a report for form.  If you find …

MRP action messages can be a very good way to manage the supply chain but too many messages can make it unuseable. What I have found is to start with Advance and Postpone the only two action messages used.  Also I recommend using Postpone margin and Advance margin. Typically I use 10 days for Postpone and 5 days for Advance. The margin days depends on how tight your planning is. Using action messages in this way matches the real world and planners then begin to use the action messages to manage purchase orders, production orders and transfer orders. Using action messages from a daily rum MRP can significanlty improve your inventory availability and inventory levels.  

Here is a simple way of taking a string and adding leading zeros to it. This will take “123A” and return “00123A” ItemZeroFill = strrep(’0′, 6 – strlen(strlrtrim(’123A’))) + strlrtrim(’123A’);