At my company and in terms of rejection, Quality Control has to specify a specific line item in the specification, code, etc. to reject something. So, in this case QC could not reject it as with the EOR's approval it is in compliance with D1.1. Quality Assurance, on the other hand, can reject on the basis on the final quality of the product e.g. we could simply say, "It's not good enough." In this case I could add that the material is not in *full* compliance with the ASTM-A106 Grade B specification, which is true, and require our sub-contractor to qualify by testing as an unlisted material in accordance with section 4.0 of AWS D1.1:2006.
...Assuming that I was of that opinion.
I like that "Quality Control has to specify a specific line item in the specification, code, etc. to reject something". I guess you do that on a report? If so, that's good practice, and can also be a learning tool. Much better than seeing some generic code on a QC report, then having to look at a legend to see what the code means, such as WSW (wrong size weld).
Heh, we try but, could still be better.
I assume this is all pretty standard ISO stuff but, QC fills out a Non-Compliance Report (NCR) which then goes to the Management Review Board (MRB) for disposition. They've got plenty of acronyms and codes to save time/space but, we all try to be very specific. Like you said, it's a good learning tool for everyone involved (keeps us current, honest, etc.) but, those code books sure wear out fast! I'd love a digital version with a search feature.