QM table QAMV and QAMR have different record status

[danny_loo]

Hi all,

I've a situation here which i'm unable to understand why it's happening.

I have a inspection lot for a material which i did the inspection process as usual.

The inspection lot has about 25 chacteristics to be inspected, no dynamic modification rule.

When the results are recorded, i prepare to do the usage decision for the inspection lot but i notice a difference at 1 of the characteristic.

Not all the 23 characteristics are processed, therefore some of the characteristics are in status "5" (processing is completed) some are in status "0" (can be processed).

The problem characteristic is in status "0".

However when in the usage decision, the status becomes a "2" (processed).

I've checked the table QAMV and QAMR.

The status in QAMV is "0" whereas the status in QAMR is "2".

May i ask, how can the status of a characteristic be "processed" when no result is recorded for it?

Is it a bug which need to be fix?

Thank you very much for all your advise 

Best Regards,

Dan

[former_member42743]

Once an optional characteristic is "accessed" it will cause the status of the inspection lot to go from REL to INSP.  I.e. even if all characteristics are skipped or optional, once you attempt to record results for one of those characteristics, it now basically becomes required.  So if a user by accident records a value on a characteristic and saves it, but then comes back and deletes the result, the characteristic is still in a 2 state.

FF

[Former Member]

Its possible,

check the screen of RR ,user tired to do result recording on char which is optional one.( status has changed from 0 to 2)