Results Recording Blocked for a QM Characteristic
The message means the inspection lot, the specific characteristic, or its master setting is in a state that does not allow a value or skip code to be entered right now. The usual causes are a lot not yet released, a characteristic whose recording indicator is switched off, a characteristic already closed, or a specification validity gap. It is rarely a program error.
Covers why a quality inspector cannot enter a result against a characteristic in an inspection lot, ranging from lot release status to control indicators on the master characteristic and the inspection plan, to specification validity windows. Gives the check sequence across QA03, QS23 and QP03, the branch-by-cause resolution, and why forcing a value or recreating the lot makes things worse.
Published 16 Sept 2026· 1,157 words
The business symptom
Quality inspector opens the inspection lot to record a measurement or a defect count and the characteristic line is greyed out, or the system throws a message saying results recording is not possible for this characteristic. The complaint usually arrives as 'I can't type into the result field' or 'QE51N shows the characteristic but the value column is blocked'. Sometimes it is reported as 'the sample size shows zero so I can't enter anything', or 'the characteristic disappeared from the list I was working on yesterday'. Production is waiting on the usage decision and the quality department is under pressure to close the lot, so what looks like a screen glitch gets treated as urgent before anyone checks the inspection lot status or the control settings behind the characteristic.
The configuration behind it
- Inspection lot is not in released status - the lot was created but automatic release failed, or the inspection type requires manual release and nobody released it before results recording was attempted.
- Characteristic recording indicator switched off in the master characteristic or overridden at inspection plan level - the characteristic is carried into the lot for information or classification only, so no input field is generated.
- Characteristic already closed - a value or a skip code was already recorded and the status was set to closed, locking the field against a second entry.
- Sample size resolved to zero through the sampling procedure - a fixed or dynamic-modification rule assigned zero samples for this lot, which is a valid outcome but reads to the inspector as a system fault rather than a nothing-to-record instruction.
- Characteristic belongs to a partial lot that has not been triggered - in lots split into partial lots, the characteristic instance sits on a partial lot not yet created or released, so the parent lot's list does not offer it for recording.
- Specification validity gap - a batch-specific or material specification characteristic has a valid-from/valid-to period that does not cover the lot's inspection date, so no valid version of the characteristic can be found to record against.
- Work center or inspector authorization restricts recording - the operation carrying the characteristic is assigned to a work center or QM authorization group the logged-on user does not hold, so the field displays but stays uneditable.
- Characteristic is configured for catalog-only or long-text entry rather than free numeric input, and the inspector is trying to type a value directly into a field that expects a code selection.
What to check
- QA03 - display the lot header, confirm status is REL and that TECO or CLSD is not already set.
- QA02 or QE51N - open the characteristic overview for the lot, check the status icon and any skip or lock reason against the specific characteristic in question.
- QS23 - display the master inspection characteristic, confirm the recording indicator and catalog assignment are switched on.
- QP03 - display the inspection plan operation the lot's inspection type draws from, confirm the control indicator was not overridden at task-list level relative to the master characteristic.
- QA32 or QA07 - check the results-recording worklist to see whether the characteristic appears at all, which separates a genuine recording block from an authorization restriction.
- Sampling procedure behind the inspection type - confirm whether the sample size and dynamic modification rule produced a valid non-zero sample for this specific lot.
- Specification validity - from the characteristic origin display inside QA03, confirm the valid-from/valid-to period of the batch or material specification covers the lot's inspection date.
How to prove it in the data
Pull QA03 for the lot and open the characteristic overview screen: the status column shows whether the characteristic is open, skipped, or closed, and the detail screen for that characteristic shows the recording indicator it inherited from the plan. Cross-check the same characteristic number in QS23 for the master-level setting and in QP03 to see whether the task list overrode it. If several lots for the same material and inspection type show the identical block, the cause is configuration, not one bad lot.
Resolution path
If the lot itself is not released, release it in QA02 - a data fix with no transport, though it is worth confirming why automatic release failed, since a permanent correction to the inspection type's release setting does need a transport. If the characteristic's recording indicator is switched off in the master characteristic or the inspection plan, decide first whether recording was suppressed on purpose; if not, correct the indicator in QS24 or QP02 and release a new plan version - this is a configuration change carried through the normal task-list release cycle and does not retroactively touch lots already created against the earlier version. If the characteristic is already closed with a value or skip code recorded, use the reset function for results recording rather than editing anything directly - a data correction, not config. If the block is a genuine zero sample size, the lot needs no fix; only the sampling procedure or dynamic modification rule needs review if a non-zero result is expected on future lots. If the cause is a specification validity gap, extend or correct the valid-from/valid-to dates on the specification - a master data fix, not a transport.
The fix people try first (and why it fails)
The usual first move is to have someone with debug or direct table-maintenance access force a value into the result field, or to cancel and recreate the inspection lot from scratch. Forcing a value bypasses whatever control indicator blocked it in the first place, so the result carries no sampling or specification linkage and will not reconcile cleanly against the usage decision or the batch record later. Recreating the lot loses the sample already drawn, resets characteristics already recorded correctly, and can duplicate a goods receipt posting if the lot was tied to one, turning a short configuration check into a stock-reconciliation problem.
Whose problem this is
This sits with the QM configuration owner for inspection planning if the block traces to the master characteristic or task list; it sits with the quality inspector's line supervisor if it is a one-off lot release or status issue. The handover note should state the lot number, characteristic number, the exact status found in QA03, QS23 and QP03, and whether the fix is data at the lot level or configuration at the plan or master level requiring a release and transport.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-functional-issues/results-recording-not-possible-for-the-characteristicERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.