QM Module issue with zero as result Need help from ABAPER TOOO

[Former Member]

Hi,

One of my client at time of results recording for some MIC's results could be Zero as value & few times he wont record for that particular MIC by taking reference of inspection point .Now when i am displaying in Z report as Datatype for that Result is considered as Numeric system is behaving blank entities as zero value as well as zero (Actual  result) also zero ,this is making a huge problem when Average result of that particular MIC is concerned.

Eg: Inspection lot  1000061 Material-XXX

Inspection pt event 1 :results MIC1 - 3   , MIC2 - 0(Actual reading value is Zero what he got from measuring equipment)

Inspection pt event 2 :results MIC1 - 3.3, MIC2 -  (few times he wont take result to few MIC)

Inspection pt event 3 :results MIC1 - 3.2, MIC2 - 1.2

In Zreport

Material XXX----Average as it should display as

MIC1     (3+3.3+3.2)/3=3.166                                  

MIC2    (0+1.2)/2=0.6 (this should happen since for event2  MIC2 he has left it blank)

Currently happening scenario

Material XXX----Average as it is displaying as of now

MIC1     (3+3.3+3.2)/3=3.166                                        

MIC2     (0+0+1.2)/3=0.4(this is happening in report Where it is Considering blank as zer as well as actual zero result as zero )

& we have also tested by replacing zero with blank but result was different

MIC1     (3+3.3+3.2)/3=3.166                                   

MIC2     (0+1.2)/2=0.6(this should happen since for event2  MIC2 he has left it blank)

Currently happening scenario

Material XXX----Average as it is displaying as of now

MIC1      (3+3.3+3.2)/3=3.166                                       

MIC2      (1.2)/1= 1.2 (this is happening in report Where it is removing all zeros)

Please provide a solution which can meet client requirement

[nitin_jinagal · Accepted solution]

Hi Krishna,

I m not exactly sure but since you use Z report, I think your ABAPer can achieve this.

What I have understand that whenever a value is entered in the MIC, it should be taken into account for calculation to average out the results, it may be ZERO or some other numeric value. But when it is left out, system should not consider them for any calculation. Correct !!

I think you can use Result record status to achieve this. Initial status is ( 0 or 1, depending upon the MIC if it is optional or required), lets say it 1 in your case, then following would occur,

• When you enter a value like 1.2, 2.12, 3.05, this status would get changed to 2, 3 or 5 from 1 (inspection point 3)
• Now if you enter 0 as input value, this status would also get changed to 2,3 or 5 (inspection point 1)
• But when no value is entered, result record status would remain as 1 (inspection point 2)

See the feasibility of mapping the result calculation based on this status. Your program should consider it always for status 2,3 or 5 but ignore it when the status is 1.

I just suggested it after thinking a bit. I'm not a technical consultant but I think this might work

Regards,

ntn

[Former Member · Accepted solution]

Thanks for quick reply...wat ever you have said is absolutly correct,but we have changed the logic by considering the MIC's in report to datatype CHAR by which we can get exact picture of values wat ever it is (Zero or Null) .Only problem will be standard sum & Mean wont be possible .For which we have provided direct radio button in selection screen with Material Specific such that Summation & Mean can be achieved by program considering all values.

[nitin_jinagal · Accepted solution]

Oh great !! So I could somehow suggested you the right way, and you found another one also. Anyway, we have two options now

I guess your query is resolved now. if so, kindly close this thread

Regards,

ntn

[former_member42743 · Accepted solution]

In the results tables look for the following fields.

MAXWERTNI     QNINITIAL     CHAR     000001          Not initial

MEDIANNI     QNINITIAL     CHAR     000001          Not initial

MINWERTNI     QNINITIAL     CHAR     000001          Not initial

MITTELWNI     QNINITIAL     CHAR     000001          Not initial

VARIANZNI     QNINITIAL     CHAR     000001          Not initial

MOMENT3NI     QNINITIAL     CHAR     000001          Not initial

MOMENT4NI     QNINITIAL     CHAR     000001          Not initial

ANTEILONI     QNINITIAL     CHAR     000001          Not initial

ANTEILUNI     QNINITIAL     CHAR     000001          Not initial

These fields are a one character indicator that tell you if the matching database field is be considered as null or zero.  If there is an "X" in the field, and the filed value is 0.00000000000 thn it means zero.  Otherwise it means null.

I.e  MAXWERTNI Is for field MAXWERT.

MEDIANNI is for field MEDIANNI

etc, etc

CS