APPS.QA_MQA_PLAN_ELEMENTS dependencies on QA_SPECS

Line 34: -- qa_spec_chars, qa_specs and the user entered spec value. It gave

30: -- When user doesnt enter any spec, a -1 is passed in..........not a null.
31:
32: -- rkaza bugs 2753703, 2767550. 01/27/2003. Refer to bug texts for more
33: -- info. Previously the where clause used to have 3 outer joins qa_chars,
34: -- qa_spec_chars, qa_specs and the user entered spec value. It gave
35: -- incorrect results. For Eg: 1) Either the char is removed if no spec matches. 2) More
36: -- than one row results for the same char if the char is present in some
37: -- other spec other than the one specified by user. 3) The char is retained
38: -- if no spec matches but some spec limits found in qa_spec_chars are also

Line 40: -- behavior the qa_spec_chars and qa_specs need to combined into one without

36: -- than one row results for the same char if the char is present in some
37: -- other spec other than the one specified by user. 3) The char is retained
38: -- if no spec matches but some spec limits found in qa_spec_chars are also
39: -- retained when they have to be made null. In order to correct this
40: -- behavior the qa_spec_chars and qa_specs need to combined into one without
41: -- an outer join between them based on common_spec. Since we didnt want to
42: -- create a new view for a bug fix, we have combined them in the from clause
43: -- itself. Also we put the filtering condition for the user entered spec
44: -- value in the same.

Line 185: qa_specs qs

181: qsc.LOWER_USER_DEFINED_LIMIT,
182: qsc.UOM_CODE
183: FROM
184: qa_spec_chars qsc,
185: qa_specs qs
186: WHERE
187: qsc.spec_id = qs.common_spec_id AND
188: qs.spec_id = x_spec_id) QscQs
189: WHERE