Corporate Backbone

This guide shows how to use the Corporate Backbone window in a defence-grade, multi-warehouse manufacturing setup with real UI screens.

Before you start

1. Sign in with the right company and user

   A repeated username on a second device now gets a separate session, but approval workflows still require the correct authority level and company selection.

2. Read the active policy gates

   APQP, subcontract package, plant transfer wall and four-eyes enforcement can be toggled from the user screen; check them before starting critical records.

3. Use the optional fields intentionally

   Carrier, warehouse, security class, serial range, certificate, file ID and note fields later appear in audit and reporting packages.

0. Tab map and role gates — "why do I only see 8 tabs?"

The Corporate Backbone window defines ten tabs, but not everyone sees all ten. The tab strip is filtered by role: someone in a production role sees eight, a system administrator sees ten. This is by design, not a fault — the server endpoint behind a tab you cannot see is closed to you as well. The table below states which authority opens which tab, and where it is documented on this page.

1. Genealogy

This tab consolidates root-cause tracing for lots, serials and work orders. FAI, SPC, NCR, subcontract, clean-room and enterprise nodes appear in the same trace tree.

📷 Actual screen

Actual screen: lot and serial search on the left, node and relationship authoring on the right.

2. Production File

As-planned and as-built data are stored in the same object. Recipe, components, operations, confirmations and quality status are tied to the same file sequence.

📷 Actual screen

Actual screen: capture, listing, freeze and recipe comparison in one tab.

• A frozen file keeps the as-planned and as-built difference inside the same record; if the recipe, operation, or quality outcome changes, capture a new snapshot and keep the old frozen file as evidence.
• Recipe comparison shows what was planned first, while confirmations and quality links show what actually happened on the floor. Defence and subcontract audits read both together.

3. E-signature / Revision

The same user cannot sign twice. Approval rules are tied to source type, source number and the declaration text. Revision records store project, configuration, effectivity dates and serial range together.

📷 Actual screen

Actual screen: approvals and signatures on the left, effectivity and applicability checks on the right.

Usage rule

• Finish the two-user approval before posting budget or FX records.
• Do not leave project or serial range blank when saving a revision; applicability checks rely on them.
• Effectivity date, configuration, and serial range make sense together. If one stays blank, the same revision may affect the wrong product variants.

4. APQP / NCR

The APQP backbone keeps PSW, MSA, PFMEA, process flow, capability history and control-plan versions under one root. NCR records cannot close until the physical stock action is completed.

📷 Actual screen

Actual screen: APQP document linking, deviation handling and NCR action management are kept together.

A deviation or waiver should be opened only within a lot, serial, or order boundary. Instead of leaving a generic exception in APQP, state clearly which serial range is released and until which date.

5. Subcontract Flow

The subcontract dispatch and return wizard keeps ASN, supplier approval, CoC, CoA, PPAP, certificates, lot and serial lists inside one package record.

📷 Actual screen

Actual screen: operation selection, package fields and dispatch or acceptance status live together.

• Do not create a package without selecting the supplier account.
• If CoC, CoA or certificates are missing on return, do not mark acceptance as complete.
• Do not keep ASN, lot, serial, and return-acceptance packages in separate places. The Backbone package exists to keep the dispatch, external process, and return chain inside one record.

6. Plant / Warehouse

This tab combines plant setup, warehouse security policies and live pre-save stock validation. Quarantine walls and security classes are enforced here during transfers.

📷 Actual screen

Actual screen: plant definitions on the left, warehouse policies and pre-checks on the right.

7. Project / Evidence

Projects, WBS, contract budget, FX impact and area-based evidence policies are managed here. Approved budget and FX entries cannot be posted without the four-eyes chain.

📷 Actual screen

Actual screen: project tree, WBS, budget, FX and evidence policies in one view.

8. Tasks / Tools

This tab creates tasks from HR findings, allows manual task entry, stores user filters and performs safe cleanup of test data.

📷 Actual screen

Actual screen: task list, saved filters, example wizards and safe test cleanup together.

Round-2 operating notes

This section pulls the daily operating rules that changed after Round 2 into one place: least-privilege `ik_muduru` usage, concurrent portal-update conflicts, complete shipment optional fields, and the cross-tab evidence chain.

📷 Actual screen

The same Tasks / Tools screen anchors the Round-2 notes: task creation, portal follow-up, and safe test cleanup still live together.

📷 Actual screen

Shipment notes and file identities feed the same audit chain that Project / Evidence uses for budget, FX, and area-based evidence policy.

Metal Operations: nine-step daily workflow

Open Metal Operations in the Corporate Backbone window. Although the cards look separate, they join through the same stock code, warehouse, heat/lot and source numbers. Starred fields are mandatory; complete optional fields whenever possible for search and audit.

Metal Operations Center and Handheld Terminal

Open Metal Operations Center in Corporate Backbone. On a phone or handheld scanner open Metal Handheld Terminal from the main menu. Follow this order to keep daily work correct and auditable.

1. Handheld: choose QR, barcode, RFID or manual. Keep focus in the large code box for keyboard-emulating scanners. The recommended label is STOK=...|LOT=...|PAKET=...|DEPO=...|LOKASYON=.... Validate Scan resolves stock, heat, lot, pack, warehouse and bin together.
2. Stock Extra: enter stock and optionally warehouse. Read on-hand, sales/central reservation, open purchase, in-transit, planned product, component demand, available stock, ATP date and risks in one result.
3. Quote matrix: save the customer's factor, discount, lead days, currency and alternate grade. Generate rows from active variant IDs, then send them to the real Quote Entry form and review before saving.
4. Cutting schedule: enter plan, machine, start/end and capacity. Overlaps or capacity overruns are rejected. Drag cards to reorder and watch yield and remaining length.
5. ASN and delivery: complete gate/appointment, loading, carrier reference, plate and driver. Upload the delivery proof. The server rejects Delivered without an active POD and receiver.
6. Certificate OCR: enter a context and upload MTC PDF/PNG/JPEG. OCR suggests heat, lot, grade, standard, size and certificate number. Review it; OCR never publishes a certificate by itself.
7. Smart replenishment: score the approved supplier, then calculate for stock, branch/warehouse and usage period. The result gives transfer/purchase, quantity, velocity class and evidence; approve it separately.
8. Webhook/EDI: send channel, event, external reference, payload and unique idempotency key. Retrying the same key creates no duplicate. The processor updates status and response.
9. Exception cockpit: review negative ATP, uncertified lot, off-tolerance weight, late order and open in-transit daily. Users without finance permission do not see cheque or FX lists.
10. Audit package: enter order/invoice, heat/lot and ASN. Validate the manifest hash, then download PDF or ZIP. ZIP contains the UTF-8 manifest, evidence and SHA256SUMS.txt. This seal proves integrity; it is not a qualified electronic signature.

Practical details: local server OCR reads PNG/JPEG and scanned PDFs, up to 20 MB and 20 PDF pages. Quote transfer preserves customer, currency, discount and due date; enter the actual FX rate separately. Dragging a cutting card swaps real times atomically. PDFs contain a CMS signature; ZIPs also include SHA256SUMS.p7s and the public certificate. The installed application test certificate is not a qualified signature or trusted timestamp. Live bank/carrier connections and physical RFID/weighbridge acceptance require provider accounts and devices.

Common situations

E-signature › "Approval authorities (second signer)" and the four-eyes matrix

In corporate approvals (budget, deviation, metal variant, exchange rate…) a rule carries an authority code, and that code decides who may add the second signature. In a company with a single manager, rules coded "yonetici" could never complete: there was no second manager to sign. The Approval authorities card solves this — the manager designates an employee as second signer for a specific subject family.

1. Corporate › E-signature tab › the "Approval authorities (second signer)" card (only a system administrator edits).
2. Type the user name, choose the subject family: finans (budget, fx, hedge, contract, project, payment, credit), kalite (revision, deviation, APQP, PPAP, NCR, FAI, ECN, CAPA, clean room), operasyon (reservation, RMA, rate, weighbridge, variant, cutting, shipment, transfer, replenishment, certificate…) or * (all). Optional note; Add authority.
3. Writing the same user + family a second time updates the record (no duplicate). Remove on the row drops the authority; pending approvals are untouched.

Messages: "invalid family" (422) — only four values are valid; "user not found" (404); "you cannot make yourself an authority" (422); an unauthorised employee attempting to sign gets DORT_GOZ_YONETICI (403). Every signature records its class (manager / authority / department head / employee); opening an approval shows the "second signers" list defined for that family.

What the approval list shows to whom: subject families

The approval screen used to open only with the Quality module right; a production user could not start a metal-variant approval, a banker could not see a rate approval. The gate now narrows by subject: the finance family is visible and startable with Management/Bank/Invoice rights, the quality family with Quality, the operations family with Warehouses/Production/Purchasing/Orders; "metal-kur" is both operations and finance. The list is filtered to the subjects you may see (the response carries a "filtered by subject" flag) — an empty list is scope, not a fault. A manager sees everything.

Partially updating a subcontract package (adding the document later)

A subcontract package opened without documents used to be stuck: CoC, CoA, PPAP, certificate, serials, lot or ASN could not be added later. The package can now be partially updated: only the fields you send are written, the rest stays. Rule: once the package has left draft, document/lot/serial/ASN cannot be blanked (the "ready" gate must not regress); document ids must be an active or frozen file in Attachments (otherwise FASON_BELGE). Status fields (supplier approval, shipment/acceptance status, order no, account) cannot be changed this way — if present in the body, FASON_PAKET_KORUMA (422); those move via the "status" endpoint.

If two people edit the same package: every record carries a version. If the "expected version" you send differs from the stored one you get KAYIT_DEGISTI (409) — no data is lost; reread the package, see the latest changes, then save. The response always returns the "missing" list and a "can be ready" flag; the package-write response lists the missing items too.

Automatic lots on raw-material purchases and per-card lot tracking

Until now "lot-tracked card" meant "a card that had a lot before"; purchase invoices opened no lots while sales consumed by FEFO. Three pieces were added:

1. Card flag: "lot tracking yes/no" can be written explicitly per stock card (Warehouses › lot tracking; API PUT /api/depolar/lot-takip/<code>; a manager or any warehouse keeper). Without a flag the old rule applies (a card with lot history is tracked); "no" switches tracking off despite history.
2. Automatic lot on purchase: when a purchase invoice (kinds that receive stock) is written, a lot is opened for every tracked line. If you gave a lot number and expiry on the line, it is used; otherwise the number is generated from the pattern in the depo.otomatik_lot_kalibi gate (default "{belgeNo}-{sira}"; placeholders {belgeNo} {sira} {kod} {tarih} {depo}, at most 60 characters, {belgeNo} mandatory). Untracked cards are skipped silently; the "lotlar" list in the response says which lot came from which source, a body lot that could not be written is reported via "lotUyari". Calling the same document again gives "zatenVar".
3. Rollback when the invoice is deleted: lot receipts opened by that document are reversed (a row that reaches zero is removed), sales consumptions tied to the document are returned with the same lot and expiry; the response carries "lotGeriAl". A second delete call does nothing. A rollback error does not break the delete; it appears as "lotGeriAl.hata".

Single-call IQC goods acceptance and the CoC lot requirement

Accepting an incoming batch used to be five separate operations: certificate check, IQC acceptance record, decision, lot and release from quarantine. The new endpoint POST /api/kalite/iqc-kabul runs them in order in a single call; the body requires the invoice number (or a line: code+quantity), the decision (accept/reject), the target warehouse (non-quarantine) and a reason; lot/expiry and certificate are optional. Permission: the quality write gate (manager or quarantine-warehouse keeper).

Reading partial success: this endpoint is not all-or-nothing — it is five separate operations. If a step fails, the response returns that step's error code (403/404/409/422), says "completed: no" and lists the steps already written (e.g. record and decision written, release failed with "quantity exceeds on-hand"). Finish the rest by hand, or fix the quantity and redo only the failed step.

CoC lot requirement (gate kalite.coc_lot_zorunlu): a CoC check without a lot number on a card where a certificate is mandatory passes while the gate is off but carries the warning "general check — not lot-based"; with the gate on it stops with LOT_GEREKLI. With a lot only the "no certificate" gate is asked. When you upload a second file to the same object in Attachments (e.g. the same heat number), the aktifSayac in the response tells how many active files that key holds — the quickest way to notice a duplicate certificate upload.

Supplier 90-day summary, single-signature setting and automatic period lock

Supplier summary (GET /api/kurumsal/tedarikci-ozet?carikod=…&gun=90; department, production, invoice, quality or warehouses right): purchase and return count/amount in the last N days, IQC accept-reject-pending and rejection ratio, NCR count and open NCRs, quality rejections, account rating and metal supplier score. Because NCR and quarantine rejections carry no account, they are matched by the rule "supplier of the last purchase delivery before the record date" — the same rule as the scorecard.

Single-signature setting (depo.dort_goz_tek_imza): if the company has a single system administrator and the gate is on, that administrator may approve his own transfer instruction; the trace lands in the notes as "TEK_IMZA" and a separate Audit-trail row is opened. If another administrator exists the setting is not applied. Automatic period lock (mali.donem_kilidi_otomatik = day of month, 0 off): on day N the previous month is locked (lock date = the 1st), an announcement goes to managers, an audit record is written; a lock moved forward by hand is not pulled back. Both live on the Management › Security gates screen; see the table in the Security guide.

Supplier accreditation (Nadcap) and the subcontract shipping gate

Special processes such as heat treating, coating and NDT cannot be given to an unaccredited supplier. The accreditation (programme, certificate number, issuer, EXPIRY) is recorded per supplier; the routing operation records which programme is required. The gate runs when a subcontract package moves to shipped and stops the shipment on an expired accreditation. If the operation carries no special process the gate never runs. Detail: Defence Traceability → Special processes.

Setup asks about backup maintenance, second-user approval, amount limits and the Financial Operations period lock. All default to off. Administrators can change them under Settings → Corporate controls. The 15-minute maintenance lease is a safety timeout, not a waiting period. Scheduled MAIN/EK1 backup requires this option. Administrators can always back up manually; the write lease is temporary and does not enable the saved option. Existing period locks in other document modules remain separate.

Financial operations, planning and backups

Open Corporate → Financial Operations. Define your accounts first; a customer control account must use the customer type. Reconciliation shows source transactions, explicit settlements and the difference between the customer subledger and posted entries. Existing documents are not posted automatically.

Select a source transaction and prepare an entry. Debit and credit totals must balance; customer control amounts must match the source. When second-user approval is enabled, another authorized user approves the draft. A posted source document cannot be edited or deleted until its entry is reversed with a reason. Reversal preserves the original and creates opposite journal lines on the current open date.

For settlement, select debit and credit transaction numbers for the same account and the amount to apply. Partial payments, advances and returns can use their existing source records. Remaining balances are checked again on approval. Customer analyses apply confirmed links first and use FIFO only for unmatched balances.

Planning and Operations → Additional cost flow follows a recorded purchase cost through inventory movements and production outputs. Select Prepare accounting entry, then choose the expense invoice, supplier and accounts. Add a tax line if needed. The cost allocation total is protected and the entry requires a second approver only when that option is enabled. Negative stock or untraceable returns/cancellations prevent an unsupported allocation.

Material and capacity planning combines the recipe, available inventory, procurement lead times, machine queues and dated working-minute overrides. Shared components consume stock once. Dates are conservative daily estimates, not reserved delivery promises. Missing lead times, inactive machines or incomplete routings leave the date blank. Existing genealogy remains available from the Traceability tab.

Daily backups require an existing server folder, a schedule, a backup password and administrator credentials for unattended execution. Credentials are stored encrypted. During the native snapshot, MAIN and EK1 writes pause under an expiring lease. Package verification checks both encrypted files. Actual restore runs from the setup wizard into a new company; new PostgreSQL and Firebird backups also compare table row-count fingerprints before the restored company is registered.