Dynamic Modification with the Usage Decision If you set the indicator
Dynamic modification at usage decision
in the
dynamic modification rule
, the system updates the quality level for the current inspection lot when the usage decision is made.
When the usage decision is made for the current inspection lot, the system updates the quality level based on the dynamic modification rule.
Updating the Quality Level (Dynamic Modification with the Usage Decision)
When an inspection lot is created , two scenarios are possible:
Quality level does not yet exist |
Quality level already exists |
The system creates a quality level. The system maintains the quality level on the basis of the criteria defined at the header or characteristic level of the inspection plan or for the inspection lot origin (if dynamic modification without a plan is specified). The quality level is maintained on the basis of the:
|
The system:
|
The system copies the initial inspection stage from the dynamic modification rule as the current inspection stage in the new quality level. If a reference dynamic modification level is active for the predefined dynamic modification level in Customizing and a quality level exists for this level, the system copies the current inspection stage in the quality level of the reference dynamic modification level into the quality level and uses it as the initial inspection stage. |
When the usage decision is made, the system updates the quality level based on the dynamic modification level:
At the lot level, or at the inspection type level with a task list |
At the characteristic level |
At the inspection type level without a task list |
The system stores the number of the current inspection lot in the field for the inspection lot number. |
||
The system stores the valuation of the inspection lot (acceptance or rejection) in the field for the usage decision for the inspection lot. |
||
It reduces the counter for inspection lots without a usage decision by one. |
||
The system determines the dynamic modification valuation automatically. It does this according to the worst-case principle: If at least one characteristic was rejected, the system rejects the inspection lot because of dynamic modification (it updates the quality level).
The worst-case principle is defined in a function module in Customizing . You can replace the default values at client level using a customer-specific function module. |
The system automatically changes the dynamic modification valuation for the characteristic to "rejected" in the following cases:
The system updates the field for the valuation of the characteristic. |
The system determines the dynamic modification valuation automatically. It does this on the basis of the usage decision code. |
The system increases the counter for the number of inspections that were rejected since the inspection stage change by one. |
||
The system increases the counter for the number of inspections that were accepted since the inspection stage change by one. |
||
The system initiates a stage change if the conditions for a stage change have been fulfilled. |
||
The system updates the
|
||