QS61 automatically catch MIC with Class Characteristic

[former_member636397]

Good afternoon!

Today I was about to create a Material Specification using QS61. But when I opened QS61, there were already some MIC and their Class Characteristic.

We have the general characteristic assigned in the batch class and the material assigned to that batch class. And MIC is linked to that class characteristic.

Why in Material Specification there are a few MICs, if they were not assigned ?

[former_member42743 · Accepted solution]

By default when you create the material spec, or even change the material spec, SAP automatically reads in the batch characteristics and their linked MIC's.

Craig

[former_member636397 · Accepted solution]

fire.fighter, thank you for the answer.
But why SAP automatically reads in the batch characteristics and their linked MIC's ?
Does SAP provide any detailed information about it?

Ksenia

[former_member42743 · Accepted solution]

No. They really don't provide much info.

The spec I believe originally served as the means to link QM to classification. Without it you could never pass inspection lot data to the batch record. Around version 4.0 they added the configuration tick box in the plant config to allow batch classification without a material spec. So its not necessarily required anymore by a lot of systems.

I don't particularly care for it. I've seen errors at times when people modify the spec in QS61. For instance, if you delete the reference in QS61 to the MIC, it will not show up in the inspection lot. Some places have a need to do this.

In that case, if at a later date you open the spec again with QS61, it restores the reference automatically and you have to delete them again. i think that's because this transaction uses the "1" transaction code (QS61) as both create and change. The QS62 transaction is for display. This kind of violates the SAP standard of 1=create, 2=change and 3 = display. I know there are a few other transactions that violate this too so I guess its just more a guideline. 🙂 MP01 and MP02 is another example where they violated that.

Craig