1. What version of the software are you running? 12.0.2.10 2. What is the problem? A designer is supposed to think about the dispositions. Today the fields are always pre-filled with "Keep Order", "Use Existing" and "Use Existing". Often these values are simply taken over - whether they are correct or not. Now, of course, the fields could not be pre-filled and provided empty. However, there is then the risk that no value is entered here if the designer does not touch this field. So to summarise the problem: Either we have no values or wrong values in the disposition fields. It would therefore be a great advantage if we provide the disposition fields empty, but make them mandatory fields that have to be filled in. This way, a designer has to think about which values are correct here. 3. Are you using a workaround? If yes, please describe it. At the moment we cannot find a suitable workaround for this. 4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation. The disposition fields should be filled correctly with every change. This setting has an influence on work preparation, purchasing and production itself. With this idea we can force a designer to think about which values are correct here. 5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.) The work preparation department is the last instance to check the ECN and all included articles before they are released. If incorrect values have been entered here, or the values have not been changed, then: Parts are still in use that should have been scrapped. Parts that should have been reworked are still in use. Our products work with people and around people. In the event of a serious error, this can result in personal injury. Our products are not mass-produced (about 1500 devices per year), but the individual assemblies/parts are usually very large and very expensive. If these are produced incorrectly, immense costs arise. A central part of our products can cost over 30,000€, a whole device is several times more expensive. Communication should take place via these existing fields. If this does not happen, there is an effort in communication (queries, explanations, etc.). The data quality in the system suffers from the wrong values. Later evaluations to avoid problems become almost impossible. ...
... View more