Contents

1. What is the Quality window for, and who needs it?2. Getting to know the screen: seven tabs 3. Permissions: who can write, who can approve?4. FAI — first article inspection Query the order's state Prepare the evidence Write the decision 5. Certificate (CoC) — attaching a document to a lot 6. ECN — engineering change and the version lock 7. PPAP — the customer's file approval 8. NCR / CAPA — nonconformance report and corrective action 9. Sample — who took how much, from which lot?10. Tracing — the recall trail (lot no → document → customer)11. The link to quarantine: where does the accept/REJECT flow run?12. When the system stops you 13. Daily routine by role 14. Frequently asked questions 15. Glossary 17. PPAP: pick the level and the expected documents appear by themselves 18. Lot block: the clean-room decision, manual block/release and where it stops things 19. Single-call IQC acceptance, the CoC lot requirement and the quarantine warehouse type 16. Linking quality evidence to the correct record

Help › Quality Window

The Quality Window — A Guide from Scratch

This guide is written for someone who has never used quality software. You already know quality work: you measure, you decide, you keep a record. What you will learn here is which gate that decision opens or closes inside the program. The Quality window has one single idea: releasing anything depends on an APPROVAL, and without the approval the program will not let it through. All seven tabs are different faces of that one idea. Read them in order.

⏱ How long does it take?

Sections 1–3 (logic + screen + permissions): 12 minutes of reading. Sections 4–10 (the seven tabs): five minutes each — read the one you need. After that, writing an FAI decision takes a minute and tracing a lot for a recall takes ten seconds.

1. What is the Quality window for, and who needs it?

Consider this question: who said "this batch is sound", and on what evidence? On paper there is a signature; but when the auditor arrives, the signature is not what is asked about — they ask where the measurement is, where the certificate is, which recipe version it was built from, whether the customer had approved it. The Quality window records the answers at the moment the decision is made; it is not a pile of paper collected afterwards.

Figure 1 — The seven tabs of the Quality window; the bottom-right box is their shared outcome.

💡 The window in one sentence

It records whether goods may be released, together with the evidence — and when the evidence is missing, the program itself refuses.

🧭 Who needs this window?

The quality officer — this is their whole day. The quarantine keeper — raises the NCR for rejected goods here. The production supervisor — the answer to "why can't I confirm output" lives here (FAI/PPAP/ECN). The buyer — sees here why goods without a certificate were not accepted. The administrator — only they hold the approve/reject buttons. Everyone may read.

2. Getting to know the screen: seven tabs

To open the window, click the Production / Quality tile in the dock and pick Quality (the same tile also holds Production and the Corporate Backbone — all three answer "how was it made, is it conforming, where is the evidence"). Stock, Warehouses and the Metal Handheld live in a separate tile: Stock / Warehouse. Once open you see seven tabs along the top. At the top right, if you have no write permission, it says "read only"; the ? button next to it brings you to this guide.

Tab	The question it answers	What does it lock?
FAI	Was the first article measured and approved?	Serial production confirmation
Sertifika (CoC)	Is a certificate attached to the material's lot?	IQC acceptance (incoming quality)
ECN	Which recipe version is in force?	Raising a work order
PPAP	Has the customer approved serial production of this part?	Serial confirmation (checked before FAI)
NCR / DÖF	What happened to the nonconforming goods, what is the root cause, who fixes it and by when?	Closing the record (an undecided NCR cannot close)
Sample	Who took how much sample from which lot, and what was the result?	Nothing — it is only a record (no stock movement!)
Tracing	Where did this lot come from, where did it go, which customer received it?	Nothing — it is a read-only report

3. Permissions: who can write, who can approve?

There are three levels and they must not be confused. (1) Reading — anyone with a session may read every tab; hiding quality data helps nobody. (2) Writing — creating records (attaching a certificate, opening an ECN, a PPAP record, NCR fields, samples) requires being a system administrator OR an assigned user of the QUARANTINE warehouse. The administrator makes that assignment under Warehouses → QUARANTINE → Staff. (3) Approve/Reject — the ECN decision, the PPAP decision and the certificate-mandatory flag belong to the system administrator alone; a quality officer does not even see those buttons.

⚠ "This action needs an administrator or a QUARANTINE keeper"

If you see this message nothing is broken: you hit a permission gate. All you need to do is ask an administrator to add you to Warehouses → QUARANTINE → Staff. Buttons being invisible has the same cause — but the real gate is on the server; forcing a button changes nothing.

4. FAI — first article inspection

FAI is a simple idea: before you make a part a thousand times, measure the first one. The program enforces it like this: if the work order's routing contains an operation flagged fai='evet', and no approved FAI exists for that part yet, the order sits at "bekliyor" (waiting) and no serial production confirmation can be written. Only a "first sample" confirmation up to the sample quantity is allowed — because you must produce the piece you are going to measure.

🚫 No approval without measurement

If you pick Onaylı (approved) and save with no evidence, the program answers: "FAI approval requires MEASUREMENT EVIDENCE: either attach a measurement report (report file no) or enter measured values on the operation. An approval given without measuring is void at audit." Evidence comes two ways: (a) you type the file number of a measurement report uploaded to Files into the Rapor dosya no field, or (b) at least one measurement row has been entered on the operation in the Production window. For Red (reject) a reason is mandatory.

Query the order's state

Type the work order number into the Emir no box at the top right and press [Emir durumu sorgula] (query order state). One of four answers comes back: gerekmez (not required — no FAI operation in the routing, or this part already has an approved FAI), bekliyor (waiting), onaylı (approved), red (rejected). The reason is shown beside it — e.g. "there is no first-article operation in the routing".
Prepare the evidence

If you have a measurement report, upload it in the Files window and note its file number. If you entered the measurements on the operation, the evidence already exists and no report number is needed.
Write the decision

Fill the FAI kararı yaz (write FAI decision) box: order no, result (Onaylı / Red), revision, sample count, report file no and reason. Press [Kararı yaz]. Once written, the order's fai_durum field is updated and the lock opens (or, on a reject, closes). The decision row appears in the list showing who decided and when.

ℹ Who may give the FAI decision?

If the FAI_ONAY competence is defined in HR, the decider must hold that competence in valid form ("first article approval requires qualification"). If no such competence has ever been defined the rule is simpler: the administrator decides. This gate is identical to the confirmation gate in the Production window — two screens never produce two rules.

5. Certificate (CoC) — attaching a document to a lot

Some materials may not be accepted without a document: steel, pharmaceutical raw material, food additive, aircraft parts… The program splits this in two. (1) The mandatory flag — an administrator marks a stock code as "certificate required". (2) The certificate record — a certificate is attached to a particular lot of that code. Before writing an acceptance, incoming quality (IQC) asks the program: "is there a certificate for this lot of this code?" If not, the answer is blunt: SERTIFIKA_YOK … it cannot be accepted without a certificate.

💡 Where does the document itself live?

The PDF/scan is uploaded in the Files window. The CoC tab here holds the link: which stock code, which lot, which document number, who issued it, on what date. There are two types: Sertifika (CoC) and Analiz raporu (CoA).

Field	What to enter
Stok kodu	Mandatory. Typed lowercase is converted to uppercase.
Lot no	May be left blank, but do not: without a lot the certificate binds to the code, and every lot of that code counts as covered.
Tip	Certificate (CoC) or analysis report (CoA).
Belge no / Veren / Tarih	The document's own number, the issuing supplier or laboratory, and its date.

⚠ The mandatory flag belongs to the administrator

The [Zorunluluk işareti] button is visible only to an administrator. It asks two questions: the stock code and "Required? (evet/hayir)". The flag is stored as an incoming quality criterion — once set, that code can no longer be accepted without a certificate. Unflagged codes flow exactly as before; installing the module does not stop your existing goods receipt.

6. ECN — engineering change and the version lock

Changing a recipe looks innocent; yet the most expensive production mistakes start there: if you cannot answer "which recipe did we build it with?" you cannot defend a returned batch. The ECN rule is: a recipe never takes effect by itself. A change becomes a draft first, an administrator approves it, and on approval the old versions drop to archive while the new one becomes in force. A work order can only be raised from the version in force.

Figure 2 — The ECN flow: draft → decision → archive. On approval the old ones are archived first, then the new version is put in force.

Opening an ECN: enter the product code, the recipe number and a reason (mandatory — "an undocumented change cannot be defended at audit"). Optionally describe the consequence in Etki (impact). On save an ECN-YEAR-NO number is generated automatically, the target recipe version is moved to taslak (draft) and the state becomes onay-bekliyor (awaiting approval). Decision: on the list row an administrator presses Onayla (approve) or Reddet (reject); a rejection asks for a reason. An ECN is decided once; a second attempt answers "this ECN has already been decided".

ℹ Old installations are not locked

If a recipe's state was never filled in (the ECN flow was never used for it) the program raises no obstacle: the highest active version counts as in force. Installing the module does not lock your existing recipes.

7. PPAP — the customer's file approval

PPAP is the file in which the customer tells you "you may produce this part in series". In automotive (IATF) it has levels 1–5; in the program the level is only information and does not set the lock. What sets the lock is the state: draft → submitted → approved | rejected.

💡 The small-business principle

If a part has no PPAP record at all there is no obstacle — it is produced freely. The lock only bites once you have opened a PPAP record for that part. Installing the module in a workshop that does not use PPAP stops nothing; the rule engages the moment you start using it.

Opening a record: the part code and the revision are mandatory — a PPAP is granted to one particular revision of a part. Customer code, level and state (draft / submitted) are chosen. You cannot write "approved" from this form; approval is a separate decision, otherwise the lock would mean nothing. The document list: click the row, then use + Belge satırı (document line) to add the required documents — control plan, FMEA, measurement report — and press [Tamamlandı işaretle] (mark complete) as each is finished. The row header shows how many required documents are still missing in an amber badge. Decision: the administrator presses Onayla/Reddet.

🚫 No approval with missing documents

When the administrator presses Onayla the program counts the required documents. If even one is not "tamam" (complete) it answers: "PPAP_BELGE_EKSIK: approval cannot be given before the required documents are complete — [names of the missing ones]". This is what auditors ask about most; an approved PPAP file with a missing control plan is worse than no approval at all.

⚠ Three PPAP warnings you will meet in production

PPAP_ONAYSIZ — a record exists but is draft/submitted: no serial confirmation before the customer approves. PPAP_RED — the file was rejected: no confirmation until it is corrected and re-approved. PPAP_SURESI_GECTI — approval exists but its validity has expired: in the customer's eyes there is no approval, so it must be renewed. All three stop serial production confirmation, and they are checked before FAI.

8. NCR / CAPA — nonconformance report and corrective action

An NCR separates two questions. First: what happens to these goods? The answer is the MRB decision — rework, scrap, or şartlı (use-as-is under concession). Second: what will we do so it does not happen again? The answer is the CAPA — root cause, corrective action, owner and due date. You cannot close the second before answering the first; the program does not allow it.

Field	Mandatory?	What it is for
Stok kodu · Miktar · Neden	Yes (all three)	The identity of the nonconformance: what, how much, why.
Depo	No, but strongly advised	Where the goods physically sit — usually QUARANTINE.
Lot no	No, but strongly advised	If a recall is needed, this is the number you will search in the Tracing tab. Without it, "which batch?" has no answer.
Kök neden · Aksiyon · Sorumlu · Termin	No (may be filled in later)	The CAPA itself. Analysis matures later; leave blank when opening and fill in afterwards with DÖF kaydet.

The MRB decision: click the row and, in the panel that opens, press rework, scrap or şartlı; add a note if you wish. The decision is taken once — trying to decide an NCR that is not awaiting MRB answers "no NCR awaiting MRB found". After the decision the same panel shows Kapat (DÖF) (close); the closing note is mandatory, and a closed record can never be edited again (traceability).

🚫 The MRB decision creates NO stock movement

This is the most misunderstood rule. Saying "scrap" does not remove the goods from stock. The record states "these goods are scrap", nothing more. The physical write-off is a separate action, done through Warehouses → QUARANTINE → Disposal with a witness and a report. So that you do not forget, the program itself appends this sentence to the decision note: "the decision creates no stock movement — use Warehouses → QUARANTINE → Disposal for the scrap write-off". The same holds for rework: the repair runs as a work order on the production side.

ℹ The same record on two screens

NCR records also appear in the Departments window and the MRB decision can be written there too — both call the very same operation. What the Quality window adds is the CAPA fields (warehouse/lot/root cause/ action/owner/due date) and the closing flow. Two screens never produce two rules.

9. Sample — who took how much, from which lot?

The Sample tab is a very simple ledger: who took how much sample, of which code, from which lot and which warehouse. Later you write the result as Uygun (conforming) or Red (reject). A rejection requires a note. The result is written once — if you got it wrong you cannot amend it; the correct move is to open a new sample record ("a result has already been written — take a new sample to correct it"). This is deliberate: a quality record that can be edited afterwards is worth nothing.

🚫 Taking a sample does NOT reduce stock

The banner at the top of the tab says: "Taking a sample does NOT reduce stock — it is only a record. If consumed samples must be reflected in stock, use Warehouses → Count (or Disposal)." The notification on save repeats it: "the sample was only recorded — the stock reduction is done separately (count or disposal flow)." Why? Because most samples come back (they are measured and returned to the shelf); the ones that do not are closed out in one go at period end by a count or a disposal. Turning every sample into its own stock movement only bloats the ledger.

10. Tracing — the recall trail (lot no → document → customer)

This tab answers one question, and it is the most frightening question in quality work: "who did we sell the bad batch to?" Type the lot number into the box and press [İzle] (trace) or hit Enter. The program lists every movement of that lot number: receipt, issue, transfer, quarantine release, disposal, count difference, production consumption, subcontract out-and-back. Rows that left on a sales document are additionally matched to the invoice and the customer — you see them summarised in the "documents/customers this lot went to" strip above the table.

Source	What it means	What is the ref no?
`belge`	Issue on a sales invoice (deducted by FEFO)	Invoice number — the customer and title show on this row too
`elle`	Manually entered lot (a lot typed at goods receipt shows like this too)	The lot record's own row number
`transfer`	Inter-warehouse dispatch/receipt (two rows: out + in)	Transfer order number
`serbest`	Release from quarantine (accept or REJECT)	Release report number
`imha`	Witnessed disposal	Disposal report number
`sayim`	Negative count difference (drained from lots by FEFO)	Count slip number
`fire`	In-transit loss or damage	Transfer order number
`teyit`	Component consumption on a production confirmation	Confirmation number
`fason`	Out to and back from the subcontractor	Subcontract record number
`top-ac` · `kesim` · `top-bol` · `top-artik`	Roll/length operations: opening a roll, cutting, splitting, writing off the remnant	The row number of the roll record

⚠ "The lot movement log has not been created yet"

This is not an error: it means the company has not had a single lot movement yet. The log is created by itself on the first one. Also know: only rows sourced from belge resolve to a customer. If goods left the warehouse by hand, "who received them" has no answer there — which is why selling through documents is the precondition of traceability. The trail is sorted newest first and shows at most 500 rows.

11. The link to quarantine: where does the accept/REJECT flow run?

The Quality window is the decision ledger; the place that physically moves goods is the Warehouses window. Do not confuse the two. Nonconforming goods wait in the QUARANTINE warehouse; they leave it through Warehouses → QUARANTINE → Release. That flow asks four questions: quantity, decision (accept / reject), target warehouse and a reason (all mandatory). Two warehouse slips are cut, a report row is written, and the lot information (lot no + expiry) is carried across to the target — so the trace never breaks.

⚠ Know these two warnings

(1) "Target warehouse warning" — if you send rejected goods to a warehouse of type normal (i.e. sellable), the program warns: "rejected goods are going to the SELLABLE (normal) warehouse … — a scrap/reject type warehouse is advised". It does not block, because a small business may not have a separate scrap store; but the right move is to create one via Warehouses → Info → Warehouse type: Hurda / Red. Scrap-type warehouses never appear in the sales document warehouse picker — that is the real protection. (2) "Missing quality decision" — if you dispatch goods straight out of QUARANTINE with a transfer order, a warning lists the codes with no release report: "…the correct route is Warehouses → QUARANTINE → Release; the dispatch remains valid with administrator approval." Your dispatch is not cancelled, but the trail is incomplete.

The full account of that flow is in the Warehouse guide: the quarantine accept/REJECT steps, the disposal report, the lot ledger, expiry warnings and the lot-versus-stock reconciliation are all explained there. The Quality window holds the reasons and the trail of those decisions; Warehouses moves the goods.

12. When the system stops you

None of the messages below is a fault; each is a deliberate gate, and each has exactly one fix.

Message	Meaning and fix
This action needs an administrator or a QUARANTINE keeper	The write gate. Ask an administrator to add you under Warehouses → QUARANTINE → Staff.
FAI approval requires MEASUREMENT EVIDENCE	Upload the measurement report in Files and type its number, or enter measurements on the operation in Production.
FAI_YETKI: … first article approval requires qualification	You lack the FAI_ONAY competence in HR, or it has expired. Have it renewed under HR → Competences.
SERTIFIKA_YOK: … cannot be accepted without a certificate	The code is flagged "certificate required". Get the document from the supplier and attach it to its lot on the CoC tab.
ecn.ac: a reason is mandatory	An undocumented recipe change cannot be defended at audit. Write one sentence — but write it.
ecn.karar: this ECN has already been decided	An ECN is decided once. If a further change is needed, open a new ECN.
RECETE_YURURLUKTE_DEGIL: … an order can only be raised from the version in force	The recipe is draft or archived. Get the open ECN approved, or raise the order from the version in force.
PPAP_BELGE_EKSIK: approval cannot be given before the required documents are complete	The message ends with the names of the missing documents. Mark each "complete", then approve.
kalite.ppap.yaz: approval is NOT given by this operation	The record form cannot set "approved" — approval is a separate decision; have the administrator press Approve.
ncr.kapat.yaz: the MRB decision must be written first	A record cannot close while the fate of the goods is undecided. Choose rework/scrap/şartlı first.
ncr.duzelt.yaz: the NCR is closed — a closed record cannot be changed	Traceability requires it. If new information appeared, open a new NCR and refer to the old one.
kalite.numune.sonuc: a result has already been written	The result is written once. Open a new sample record to correct it.
First article approval (FAI) is WAITING — no serial production confirmation	Appears in the Production window. Produce and measure the sample, then write the FAI decision here.

13. Daily routine by role

Role	Every day	Weekly
Quality officer	NCR → the "awaiting MRB" filter: anything still undecided? Sample → "awaiting result": anything measured? Orders waiting on FAI.	CAPAs whose due date is near (the ⏱ at the end of the row). CAPAs ready to close. PPAP missing-document badges.
Quarantine keeper	Open an NCR for every batch landing in quarantine (do not forget warehouse + lot no). Take samples and write results.	Goods waiting in quarantine: anything decided but still sitting there? Run the release/disposal flow.
Administrator	ECN → the "awaiting approval" filter. PPAP files awaiting a decision.	Is the certificate-required list still right? Who holds quality write permission (QUARANTINE staff) — has anyone left?
Production supervisor	When an order refuses a confirmation, query its FAI state first; the cause is usually FAI, PPAP or the recipe version.	Do new parts need a PPAP record? Open ECNs for your recipe change requests.

14. Frequently asked questions

Will installing this module stop our production?

No — this was designed deliberately. FAI only bites on orders whose routing has a flagged FAI operation, CoC only on codes flagged "certificate required", PPAP only if you opened a PPAP record for that part, ECN only if the recipe's state has been filled in. Unflagged data flows exactly as before. The gates work as you switch them on.

I chose "scrap" but stock did not change — is something broken?

Nothing is broken; that is the rule. The MRB decision creates no stock movement; the program appends that very sentence to your decision note. The physical write-off happens in Warehouses → QUARANTINE → Disposal with a witness and a report. The two are separated because the decision belongs to quality and the stock movement to the warehouse.

Can I skip the lot number?

The program will not stop you — but on the day of a recall you will have no number to type into the Tracing tab. The lot number is the only key to "which batch"; make a habit of entering it when opening an NCR, taking a sample and receiving goods. One minute of typing saves a day of searching.

May I attach the certificate to the code instead of the lot?

Technically yes, but do not. With the lot left empty, the acceptance check treats every lot of that code as documented — so future batches slip through without a certificate. A certificate belongs to the batch it came with.

Does the PPAP level change the lock?

No. The level (1–5) is information only, kept because IATF practice expects it. The only things that set the lock are the state and the validity date.

15. Glossary

Term	Meaning
FAI	First Article Inspection — measuring and approving the first piece before serial production.
CoC / CoA	Certificate of Conformity / of Analysis — the supplier's or laboratory's document.
IQC	Incoming Quality Control — the acceptance inspection of arriving goods.
ECN	Engineering Change Notice — the approval path for a recipe or drawing change.
PPAP	Production Part Approval Process — the file in which the customer grants serial production.
NCR	Non-Conformance Report — the record saying "these goods do not meet spec".
MRB	Material Review Board — the body deciding the fate of nonconforming goods: rework / scrap / use-as-is.
DÖF / CAPA	Corrective And Preventive Action. Root cause + action + owner + due date; closes only with a closing note.
rework / scrap / şartlı	Repair / write off as scrap / use as is under concession. All three are MRB decisions and none moves stock.
Lot / parti	A group of goods made under the same conditions or arriving in the same shipment. The unit of traceability.
SKT	Expiry date. Held on the lot record; the basis of the FEFO order and of the warning strip.
Geri çağırma (recall)	Collecting back a batch already in the market. The Tracing tab is its first step: who received the batch?

17. PPAP: pick the level and the expected documents appear by themselves

When opening the PPAP record of section 7 you had to list the required documents by hand; when the customer said "level 3" you typed 18 rows from memory. Now, once the level (AIAG 1–5) is chosen on the PPAP form, the expected document list appears immediately (mandatory ones as blue chips), and if the "Open document rows automatically when the record is created" box is ticked, the document rows are written by themselves when the record opens. The success message says how many rows were opened.

Level	Template (AIAG PPAP 4th edition, Table 4.2)
1	PSW only (part submission warrant).
2	PSW + sample + dimensional results + material/performance + appearance approval (5 documents).
3 · 5	Full set: 18 documents, all mandatory.
4	PSW mandatory; the other 17 rows open as "customer-defined" (not mandatory) — you agree with the customer which ones are wanted and mark them.

Approval gate: to set a PPAP to "approved", every mandatory document row of the template must be "done"; otherwise it stops with PPAP_BELGE_EKSIK and counts the missing ones. If you change the level on an existing record, rows are not added by themselves — you ask for it with the "complete missing" option; if you want no template at all, untick the box when creating (visible escape). The template is idempotent: an existing row is not opened twice.

18. Lot block: the clean-room decision, manual block/release and where it stops things

Blocking a lot does not move it physically; it stops it on the consumption and shipment paths: the FEFO suggestion in sales skips the lot and lists it as "blocked" in the response, manual lot selection on a production confirmation is refused with LOT_BLOKE (a red gate in Check), and a selected lot on a transfer instruction or shipment is refused. The lot list shows the block status, reason and reference. Every lock and release is written to the lot movement log (direction: block / release).

Clean-room decision: if you see a violation on a measurement and decide lot_karantina, the production lots tied to the measurement's order and opened after the measurement time are locked (reference "temizoda:<measurement no>"). If no lot is found the decision is not written, with LOT_BULUNAMADI; either choose via the "lotlar" list or tick the "no production at that time" escape. If you later correct the decision to accept or measurement error, only the locks placed by this measurement are released. Details: Production guide.
Manual block and release (quality write gate: manager or quarantine-type warehouse keeper): GET /api/kalite/lot-bloke lists blocked lots; POST /api/kalite/lot-bloke locks by lot sequence or code+lot no — a reason is mandatory; POST /api/kalite/lot-serbest releases. If you give a reference on release, only locks placed with that reference are opened; another decision's lock is untouched. The Quality window has no separate screen for these endpoints this round; the clean-room tab shows the lock result as a message.

19. Single-call IQC acceptance, the CoC lot requirement and the quarantine warehouse type

Single-call IQC acceptance (POST /api/kalite/iqc-kabul): the five steps of accepting an incoming batch — certificate check, IQC acceptance record, decision, lot, release from quarantine — run in order in one request. Invoice number (or code+quantity), decision, target warehouse and reason are mandatory; lot/expiry and certificate optional. This endpoint is not all-or-nothing: if a step fails, the response returns that step's error code, says "completed: no" and lists the steps already written — finish the rest by hand. Body and sample response: Corporate guide. The FAI of section 4 and the accept/REJECT flow of section 11 are unchanged; this endpoint is their shortcut.

CoC lot requirement (gate kalite.coc_lot_zorunlu, off by default): if you run the certificate check of section 5 without a lot number, the response passes while the gate is off but carries the warning "general check — not lot-based" (lotBazli: no); with the gate on it stops with LOT_GEREKLI and the certificate question is not asked at all. With a lot only the SERTIFIKA_YOK gate exists. When uploading a second certificate to the same heat/lot key, the aktifSayac in the Attachments response (active files under that key) reveals the duplicate.

Quarantine is a warehouse type: the "manager or KARANTINA keeper" rule of section 3 is now "manager or keeper of a quarantine-type warehouse"; second quarantine warehouses such as CN-KRNT are covered too. The Quality window's context gives the "my quality warehouses" list; the release form selects the source warehouse, and the target cannot be quarantine-type. If you get 403 the message names the warehouse type and the assignment. Details: Warehouse guide.

🔗 Related guides

For the quarantine accept/REJECT flow and the lot ledger see the Warehouse guide; for work orders and confirmations the Production guide; for incoming quality (IQC) and the department side of NCR the Departments guide.

16. Linking quality evidence to the correct record

Attach the FAI/measurement report and used drawing to FAI; CoC/CoA/certificate to CoC; new drawing, control plan, PFMEA, process flow, and specification to ECN; approval pack to PPAP/APQP; and inspection/measurement/test report plus photos to NCR and samples. In IQC receipt and lot tracing, match supplier certificates and delivery note to the same physical lot.

Do not delete an approved quality result or old revision. Cancel a wrong attachment with a reason and upload the correct report as a new attachment. Verify lot/serial/order, report number, validity, and security class. Field guide: Practical User Handbook.