Yogini,
I'll take a look at using target value...or even one of the info fields mentioned above. We tried to use the "1st lower spec" to hold the MDL value, but when using SAP's COA Profile Spec Origin FM's for multiple specs...it always wants to overwrite the regular lower spec limit with the "1st lower spec limit" when something is in it. Does anyone know why the SAP help on the "1st lower spec limit" field says it is not used by the system, when it really is? I don't understand why SAP would ever want to overwrite the original lower spec limit with this...period.
For example: QC02MS_INSP_CHAR_SPECS right after inspection_char_read, assuming you find something, it calls PERFORM msobj_change_specs. In this subroutine, in every instance of me having a value in the 1st lower spec limit (p_qamkr_line-grenzeun1 or l_qamvrms-grenzeun1) , it replaces my original lower spec limit value (p_qamkr_line-toleranzun). I am puzzled by the fact that SAP puts so much emphasis on this field...especially since the search help description says it is an extra field not used in the system. Any idea why it is so important? I thought maybe SAP was doing the math on on the regular lower spec limit + or - a period of validity increment and holding in the 1st lower spec limit for population on the QAMVRMS table, but haven't been able to verify this.