Kevin Fons Sr Application Consultant

Add functionality to create a usage based forecast and publish to the Demand Forecast. Possibly via the Cortan AI tools or a developed worksheet possibly with options to increase or decrease a forecast by a percentage based on projected sales budgeting (i.e. 10% growth in sales for a particular item).

When using the move function to assign a machine center from the work center task list or when in the production order routing you change the type to Machine Center from work center and choose a machine center, the fields on the Machine Center Scheduling tab override the routing times always via the stock code. We need the option to not do this as in many cases this is not desirable and not wanted. For example if the setup time is 0 or blank then the routing setup time could carry forward. Or add a new Boolean field "Use Routing Times" which when it is true it would not change the times on the routing, just change the work center to the chosen machine center. We can figure out how to address this via an extension but it is code that should not be needed with some flexibility in the stock code (simple if statement could fix)

Taking away the product group code field has really limited customers and the Item Category The key on the item category could be the Code and the Parent Category not just the code. Since the product group code was removed we have customers that the item category is a major issue based on how it is setup. The customers were using the item category and product group as separate item categorizations and filters. Attributes do not work well as they are very limited in scope of where they exist and can be used as filters. The item category hierarchy also has major filtering issues (there is an existing ides for this one) For example this is a typical customer setup (when they had the product group) Top level Item (Parent) Categories of Steel Plastic Wood Then inside each of these the customer would like to have the same subcategories in each one (this was their product group code) Brackets Supports etc. This is not possible since you can only have the category Brackets once so when a database is upgraded the categories create as Brackets1, Brackets2, etc. The customer needs to be able to filter in various areas of the application like Filter all wood parts all brackets all wood brackets This is not possible with he way the table is setup and how the filtering functionality works in BC.

It would be great if we could have a service to create / update the postal code table from a remote source. For example a function to load / update postal codes and it would go get all known postal codes for a country or countries and populate and/or update the code, city, state, country.

Create a function for disassembly orders Production an Assembly types). This would allow the users to create the order , consume the same item as the source and then output / adjust in or un-consume the components they choose to return to stock. This could in theory be a worksheet / Journal that you would populate with the negative and positive adjustments. An actual production order with a routing would be nice as labor could be reported against it. This mod has been done or asked for by several customers in the past.

It would be valuable if the customer or partner could configure tables to be shared across companies for multi-company tennants. Tables like reason codes, Postal code, country code, and other generic setup tables could be shared and then easily kept in sync between companies. This does not include master record tables that are much more complicated to maintain due to the number of fields and variations from company to company for specific fields.

Add a function to pages like customer, vendor where there is address data and add a function to get the Longitude and Latitude and populate to the record.

It would be really nice to have a page or better yet notifications that a newer version of a third party application is available in the marketplace. Right now unless the ISV informs you (and sometimes they don;t know exactly when their app is updated in the marketplace) you have no idea there is a new version. Also, make it standard on the application to have a release notes and / or whats new link.

We are really lacking the ability to schedule production orders. The Due Date, start date and end date are all linked currently so you cannot move the start date and end date prior to the due date to schedule wen you want to run the order. Ideally a Scheduling time could be added to the manufacturing setup and possibly the item (mfg setup is global, item is specific). an example might eb scheduling time = 1W which would set the start date a week earlier so material would be planned to arrive by the start date. Then the user could manually or via the visual schedulers available move the start date to schedule it in a particular work center (as long as the end date does not move past the due date). The dates would initially be calculated as: Due date = due date End Date = Due date - scheduling time Start date = End Date - production time from the routing. The user would then be able to move the start date of the entire order or a routing operation and the end date would be adjusted but the due date not changed as long as the end date is still less than the due date. Moving the start date where the end date moved past the due date would result in a message telling the user the end date would be past the due date and they would have to select Yes to do it vs the No default. The scheduling time would only be used for the initial refresh of the production order, however there could be a function to Reschedule the Production Order (o the existing refresh function could be used). The refresh button could have a field for the scheduling time where the user could adjust the time for a particular order. It might also be nice to indicate via a field on the header and/or line that the order had been "scheduled" i.e. the start date / end dates changed.

When Bin Mandatory is set the item dimensions will not be populated to the Physical Inventory Journal resulting in the inability to post the journal without manually populating the dimension values on each line. When doing cycle counts or annual physical inventories this can be hundreds or thousands of lines. This is because when bins are being used the journal calculates from Bin quantity and not ILE quantity so the dimensions are not used. There needs to be a way to populate the dimensions when using bins, potentially from the default on the Item record. This is really a large hole in the functionality when using dimensions on items and bins.