cancel
Showing results for 
Search instead for 
Did you mean: 

Removal of Manual Valuation in QE51N

faisal_khan
Participant
0 Kudos

Hi,

We have a requirement to remove the Manual Valuation popup while doing result recording in QE51N.

I referred to below link

https://answers.sap.com/questions/5368548/remove-manual-valuation-pop-up.html

I tried the above in tcode QDV2 but a warning pops up as foolows:

"If you change the valuation mode, data for the sample will be deleted

Message no. QD218

System Response

Example:

Sampling type: Fixed sample

Valuation mode: Attributive inspection according to nonconforming units
Sample data: Sample size and acceptance number

If the valuation mode is changed, the data for the sample size and the acceptance number is deleted.
This prevents incorrect data from being written to the data base."

I need to know the consequences of above change as can't comprehend the above reasoning.

Regards

Faisal

Accepted Solutions (0)

Answers (1)

Answers (1)

AlbertSAP
Advisor
Advisor
0 Kudos

Hi Faisal,

thank you for the details provided.

Message no. QD218 occurs in include MQDSVF10. After the warning message following fields are cleared in form init_felder_zur_stichprobe ("...data for the sample will be deleted..."😞

...
*----------------------------------------------------------------------
*       FORM INIT_FELDER_ZUR_STICHPROBE
*----------------------------------------------------------------------
*       Felder zur Stichprobe initialisieren.
*----------------------------------------------------------------------
FORM init_felder_zur_stichprobe.
  CLEAR qdsv-stprumf.
  CLEAR qdsv-annahmez.
  CLEAR qdsv-kfaktor.
  CLEAR qdsv-kfaktorni.
  CLEAR qdsv-stprplan.
  CLEAR qdpkt-kurztext.
  CLEAR qdsv-prschaerfe.
  CLEAR qdsv-aqlwert.
  CLEAR qdsv-prozumf.
  CLEAR qdsv-prozumfni.
  CLEAR qdsv-prozazl.
  CLEAR qdsv-prozazlni.
  CLEAR qdsv-qrkart.
  CLEAR qdsv-kzumfs.
  CLEAR qdsv-fbkeymfs.
  CLEAR qdfmt-kurztext.
  CLEAR qdsv-stpranz.
  CLEAR qdsv-raster.
ENDFORM.
...<br>

Have a nice day,

Albert

***

Read and follow the 'SAP Community Rules of Engagement' at

https://www.sap.com/community/about/rules-of-engagement.html

faisal_khan
Participant
0 Kudos

Hi Albert,

Thanks for the info.

Will it effect the created Inspection Plans and Inspection Lots?

Regards

Faisal

AlbertSAP
Advisor
Advisor
0 Kudos

Hi Faisal,

inspection plans and inspection lots are 2 different stories.

Inspection plans will be affected by the changes in the sampling procedure. Therefore, it is highly recommended to check the consistency of the inspection plan in transaction QP02 after a sampling procedure change. (An example: if the inspection point relevancy of a sampling procedure is changed and the task list header inspection point config contradicts the sampling procedure, that is an inconsistency and will cause troubles.)

Inspection lots. We need to distinguish two stages of the lot, if we are talking about sampling procedure change.

1.) If the lot has no sample calculated yet, then you can change the plan (including the sampling procedure), it will have no effect on the existing lot. The plan and sampling is read for the lot, when the plan assignment and sample calculation takes place. It means the adjusted/changed plan and sampling procedure will be used for the lot.

2.) If the lot has already task list assigned and sample calculation took place, it means the sample size is determined with the characteristic data for the lot specifically (important tables: QAMV, QASV). Therefore, a change in the sampling procedure would not affect this lot. However, if you reset the sample calculation for the lot (if available), you could re-calculate the sample according to the adjusted/changed sampling procedure.

This is some general information in the topic, testing of the specific business process is required, whether there are any other effects of a change in the sampling procedure.

Have a nice day,

Albert

***

Read and follow the 'SAP Community Rules of Engagement' at

https://www.sap.com/community/about/rules-of-engagement.html