on 2012 May 03 3:19 PM
Hi All,
I have come across a strange requirement. I would appreciate if someone reconfirm me or suggest few more ideas.
Alternatives that came in to my mind are,
Many thanks,
Anand Rao
I clarify few more aspects here,
Basically there are following possibilities for the values in fields of lower limit and upper limit.
Is there any feasibility to accommodate above cases in specification in inspection plan
Anand
Message was edited by: Anand Rao
This haas always been a problem in SAP in the QM module. The value in the upper spec for instance is a valid value. SAP considers all values in upper or lower spec to actually be <= or >= values. You can definitely do as you already suggested and make the upper spec to be 1.89 as you suggested in QM.
That probably isn't the true problem. The true problem probably arises when you try to use that spec in a COA. You want the custoner to see the spec as < 1.90.
I see two options for this.
1. Create a second calcualted MIC's for these type of characteristics. Add them as a conditional MIC that is only done when the controlling MIC is accepted. The formual is simple, C00010.
In the second calculated MIC, the spec is set to 1.90. But this value is only filled when the controlling MIC passes, i.e the one set with an upper spec of 1.899. The second calculated MIC should always pass as a result. And in the COA you report the second MIC and spec.
2. In the COA you create a new FM for "insp. spec. origin.". In the function module you round the spec up once decimal place before returning the value to the COA program. By doing this, your inspection plan spec is set to 1.899 in the plan. The FM when reporting this spec, rounds it up one decimal place and this value would becoem 1.90 when published in the COA. You of course only select this insp. spec origin for characteristics that need it.
If your lower spec is 1.50 your spec value in the lot should be set to 1.501. When this is rounded, it becomes 1.50.
FF
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My apologies for replaying late!
You got it correctly FF. Not only customer but the user also wants to see the spec as < 1.90 (instead of ≤ 1.90) where all values below 1.90 are acceptable but not 1.90.
Your 2nd suggestion sounds good which takes care of printing specs by rounding it off.
At the time of RR even user confuses when he sees the spec as = < 1.90 but cannot conclude whether 1.90 is acceptable or not. I think the description of MIC can help user addressing this. Let me put following 2 hypothetical cases.
Sr | MIC Desc | Spec as it appears in QA32 RR screen |
1 | Carbon % | = < 0.08% |
2 | Carbon % (< 0.08%) | = < 0.08% |
If we cannot avoid appearing = < 0.08% in spec column, at least description can guide user that 0.08 is acceptable or not. And while printing specs on COA, perhaps there could be a way in ABAP to set printing logic similar to one you suggested.
Thank you Sujit for your valuable suggestion also.
Thanks again. Keep posting.
Regards,
Anand
Rather than using the description of the test, you might want think anout using one of the info 1, 2 or 3 fields for this. Some tests have long descriptions which if you have to add a spec to it, could exceed the characters allowed.
You can move the column right niext the results recording column so it is clearly visable to the user.
FF
User | Count |
---|---|
94 | |
9 | |
8 | |
8 | |
6 | |
5 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.