Can an LoV on quantity be available when a batch balance is at a ‘unreleased’ state with a tree structure node at a ‘proposal created’ stage?>> We have a situation where a customer is creating batch balances but in an ‘unreleased’ state and a tree structure at ‘proposal created’ stage, an LoV is triggered on the Qty.>> The customer claims that this was the norm when they were on App 10 UPD 3 and now that they have upgraded to UPD 10, they expect the same behaviour.>> When tested in our core environments (latest, UPD 10 and UPD 3 versions), I could not create a batch balance to with an LoV made available for the Qty. That field has only been editable so far, as per expected behaviour.>> Could there be any functional scenario within the application where the Qty field is triggering an LoV at an unreleased stage of a Batch balance? Thanks!Heshani
We have a situation where the customer is running in to a system crash for ALL users due to a middleware server data outage when running certain query parameters in the manufacturing visualizer from time to time.>> How was visualizer designed for and what technical limitations are related to the design>> What is the best practice and what action could be taken to mitigate a risk of such a system outage by using a query parameters that visualizer was not defined for? A simple typo could cause such an incident.
When running capability check, are non-consumed components considered if qty per assembly>0, lead time>0?
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.