-
Purchase Agreement lines screen needed
Purchase agreements are really hard to work with in real life because so many things are missing. Here is one idea that is easy to execute and will make it a lot better: we need a screen that shows all Purchase agreement lines so I can find out which items are in an agreement. There is no way to find out otherwise. The screen is just like the screen Open Purchase lines but other fields are relevant like Max enforced yes/no and of course the agreement line price. -
Unit Sequence group id needs to be on the Create Released product screen
We really need the unit sequence group id to be on the Item creation screen! When I choose an advanced warehousing storage dim group, the "reservation hierarchy" appears on that create screen but no unit seq group! The unit seq group id should also appear. This should have been done years ago. It is painful as one tends to forget that field , then one starts the item in a transaction and one gets stopped. This is important to fix. -
Forecast consumption by transactions (configured products need this) not working when phantoms
The following is a serious gap in the solution: When we forecast configured product demand, we use allocation keys to get a forecast to be managed on an option level. This option is represented by a part number that I have given a percentage. When this part number is a phantom, the forecast consumption only works temporarily. When my top level prod order is planned, there is an exploded demand for the phantom item in the BOM that nicely reduces its forecast. When I firm my top level planned prod order, the phantom disappears from the BOM and the forecast consumption I had for the phantom is reversed after the next MRP. This is entirely logical from MRP's perspective ("I see no demand for the phantom so the forecast remains unconsumed). This will lead to double demand for the components below the phantom.It really does not work. The work around is to manually reduce all the forecasts for the items that are sitting in item allocation keys and are phantoms. And that should happen for each sale. That is a big work around. My idea is that MRP should be changed to NOT reverse the forecast consumption when the item that carries the forecast is a phantom. that would be sufficient. -
Purchase agreement improvements
1.We really need a screen that shows all Purchase agreement lines that exist. That way we can find out relatively quickly whether an item is in any Purchase agreement OR 2.Add a new menu to the released product action area Purchasing, just like we have for Trade Agreements, where I can look up whether an item is in a Purchase agreement OR 3.Make a new fact box tab on the Released prod grid that displays any Purchase agreement that exists for an item. Basic data as dates and agreement quantity and vendor should show. -
No more "Marked for Deletion" in WrkCtrCapRes
CURRENT FUNCTIONALITY: A prod order in status Released, where picking work has been created , will get “marked for deletion” for all capacity reservations” after I run scheduling while open picking work exists. The user thinks this is capacity reservation “on the way out” but the opposite is the case. This is a temporary hold status of the capacity reservation. After picking complete, it will come right back as normal capacity reservation. ….
The capacity overview in Master planning includes “marked for deletion” records which now I really am happy about. This means we can use that without filtering since the “ghost” capacity reservations for ended orders and RAF orders I hope have been removed. Yet the entire "marked for Deletion" behavior I consider unacceptable. Root cause is Advanced warehousing picking work causing these records that are a mystery for the average user.
PROPOSED FUNCTIONALITY: 1. Eliminate the status “marked for deletion” capacity reservations records. See item 3 for detail. 2.Remove the dependency of open picking work and prod order scheduling. This is functionality that is not needed. With regular warehousing you don’t get an error when you have an unposted picking list journal while you run scheduling. 3. When scheduling gets into an error like missing calendar or effective date of calendar not in current date range, do not do anything in the capacity reservations table until the user has fixed the error. 4.After RAF status, all capacity reservations of a prod order should be removed. (I guess the hot fix that is on the way will do this) -
Send warning when personalizing certain fields that should not be personalized
A user can personalize any field. yet there is trouble when the user takes fields that are controlled by Dimension display, for example. or when the user starts personalizing the Job card Terminal screen that has its own column display setup feature. As soon as the dimension display changes or the display column set up is changing, there are unpredictable effects in the screen display. Users should be stopped when making this mistake. A warning should come up "This field is controlled by Dimension display. Do not personalize". similar warning for the Job Card terminal fields. -
Regular warehousing and production really need this
When I create production order picklist journals (using reqular warehousing) a sore point is that the system does not care whether I have inventory or not. My picking list gets everything in the PROD BOM and only after evaluate I will find out which items can actually be picked. There is no way to put a select filter in the picklist line creation process, so it would only put those items on the list that can be fully physically reserved.! There is no way,. We had to make a customization for this. The standard system should work with regular warehousing Prod order picklists that can actually be used as picklists. With advanced WHS , we can "release to warehouse" the same prod order multiple times, as more materials come in. That works perfectly. We get new picking work for exactly those items that have a phys reservation and can be picked. With regular warehousing we need that option also. It would come down to starting the same order again, with a quantity of zero of course, and then get additional picklist created for items that arrived in inventory more recently. Etc. Until no more remaining qty in the Prod BOM. Let us know if this is feasible. We know it is because we just programmed it and it works perfectly. Design details of this idea can be debated but here you have the essential need and the sketched solution. -
Personalization moving fields
The personalization needs improvement. When trying to move a field the user always faces a lengthy process if you use drag and drop. I know the arrow keys work better. But the drag and drop is painful. You need many attempts to finally get the field in place. Users also need time to figure out you should not drag the field header which is intuitive but the field content. That I had to explain so many times. Nobody does that right. User friendliness of the dragging of fields to other positions is far below acceptable. -
Quality functionality needs roadmap
Quality management and control is functionality that has barely changed in 10 years. The Inventory status of adv warehousing was integrated with Quality orders, we lost the quarantine order but I can't remember much innovation . There are fundamental gaps in Quality and we have so far customized this. four key features would improve the situation drastically. We can't do these things with power apps. 1.Inspection frequency functionality. "Skip lot" called often. I want to inspect every 10th PO for a certain item/vendor combination. When I find quality problems I may switch to every 5th PO. When I have no problems I may relax to 1 in 20 PO or even no inspection at all. This is a key feature to have 2.AQL table with sample sizes. These are tables providing sample sizes for order quantities. Many customers use these. 3.Adv Warehouse- Quality order integration using locations so I can put away to different locations based on the outcome of the Quality order. 4.Automatic creation of Quality case after failure of inspection. (to make up for the loss of the quarantine order). -
Quality order sampling
THe new feature Quality order for whs processes is a great initiative but it contains one big mistake. Sample testing is misconceived seriously. When I test 10 EA of a total lot of 100 EA I decide what to do with the entire 100 EA. A sample symbolizes the total lot. With this feature, the quantity being tested via a quality order, those 10 EA, are the only ones going to a reject location if I have a failed test. THe other 90 EA , using the license plate, are going to the normal put away location. That is 100% wrong. So we can only use this new feature when we do a 100% sample or we use the license plate frequency counter. This is rather shocking. It has to be changed. Few customers use a 100% sampling.
You’re offline. This is a read only version of the page.
