Practical User Handbook

This page is for an employee using the program for the first time and needing to complete daily work safely. Read the common rules here first, then open the guide for your job's module. If you do not know a term, do not guess: type the word shown on screen into Help search.

Four checks before you start

Check the name and company at the top right to confirm that you signed in as the correct user and company.
Do not create a record before choosing the work date, plant/warehouse, and purchase/sale direction.
If Save or Approve is missing, check your permission with your supervisor. Never use another person's account.
If the list looks stale, press Refresh first. If two people edit the same record, do not write again before reviewing the newest version.

1. The same working order on every record form

Decide the purpose. Are you creating, correcting, or approving a status? Correct information entered in the wrong window is still a bad record.
Complete mandatory fields. Starred fields cannot be blank. Code, account, stock, warehouse, date, quantity, and status drive the reports.
Complete optional but operationally important fields. Owner, description, recipient, vehicle, plate, driver, loading note, lot, serial, project, and cost centre complete the audit story.
Save the main record first. “Save the main record first” in the attachment panel is not an error; the record identity needed for linking does not exist yet.
Verify the result. A success message is not enough. Find the record in the list and recheck its number, quantity, status, and attachments.

1.1 Mandatory versus optional

Type	What should you do?
Mandatory	It has a star or gives a clear warning when saving. Never enter a temporary or invented value instead of finding the real one.
Optional	The record can technically be created, but complete it when the information exists. A blank may create a gap later in reporting, search, shipping, or audit.

2. Versioned file and evidence attachment standard

The File attachments panel works the same way in production, quality, warehouse, subcontract, commercial, CRM, banking, HR, and project forms. Uploading a file alone is not enough; you also record what it is and which work it belongs to.

2.1 How to complete the fields

Field	Rule and example
Document type	Choose the file's business meaning: technical drawing, specification, work instruction, control plan, certificate, CoC/CoA, measurement/FAI/SPC/test/inspection report, delivery document, delivery note, ASN, warehouse receipt, contract, bank slip, photograph, or PPAP pack.
Document / report no.	Mandatory for certificates and report types. Enter the number printed on the document, not the file name; for example COC-2026-184.
Revision	Mandatory for technical drawings, specifications, work instructions, control plans, PFMEA, and process flows. Example: A or 03. Never overwrite the old file; upload the new revision as a new attachment.
Validity	Start and end dates show when the document may be used. Do not leave the end date blank for certificates, calibrations, or time-limited approvals.
Lot / Serial / Order	If evidence belongs to a specific production run, enter its identity. Do not attach a random lot or serial to a general procedure. Do not alter an order number supplied by the form.
Security class	Choose Public, Internal, Official use only, or Confidential. Apply company policy to customer drawings and defence/project documents; never lower the class for convenience.
Customer property	Tick this when the customer owns the file's intellectual or physical content. The flag does not permit free sharing; it requires stricter protection.

2.2 Attach a file step by step

Save and reopen the main record; make sure the correct record number is visible.
Choose the document type in File attachments. Complete the document/report number or revision when a star appears.
Enter validity, lot, serial, security, and customer-property data from the actual document.
Select or drag the file. Keep the window open until upload completes. The limit is 20 MiB per file.
Check the listed file name, type, number, revision, links, and status.
Press the file name to preview text, images, or PDF; use the separate Download button to save it locally. For Office/CAD formats the browser cannot display, the system clearly tells you to download the file.

A file is not deleted; it is cancelled with a reason. If you chose the wrong file, press Cancel and state a clear reason. An attachment in a frozen production file cannot be changed silently. Upload the correct file as a new revision; the old version remains in the audit trail.

2.3 Which document belongs to which record?

Document	Related forms	Key link
Technical drawing	Stock card; recipe; production request, order, machine, and tool; FAI, ECN, project; quote, sales order, and CRM opportunity.	Revision, validity, and customer property.
Certificate / CoC / CoA	Stock card and lot; IQC receipt; CoC and lot tracing; measuring device; subcontract pack and return; personnel competence or PPE.	Document number, validity, lot/serial, and supplier.
Measurement / FAI / SPC / test / inspection report	Production order and SPC characteristic; cleanroom measurement; FAI, NCR, sample, IQC receipt; maintenance/machine/tool.	Report number, order, lot/serial, measurement date, and device.
Delivery document / delivery note / ASN / warehouse receipt	Warehouse count, lot, pallet, and transfer; subcontract dispatch/return; sales order and invoice; PPE handover and entry-exit checklist.	Document number, sender/recipient, date, vehicle/plate, lot/serial.

3. Shifts and patterns: setup required before attendance

A shift defines a workday's start and finish. A pattern is the day-by-day sequence of shift codes; X is a rest day. If shifts and patterns are not set before attendance, plan rows may be missing and night/overtime calculations may be wrong.

The HR manager opens Personnel → Time → Shifts and records code, name, start, finish, night/day-overrun, and active status. If a night shift finishes the next day, verify the day-overrun setting.
In Patterns, enter a unique code and clear name. Use defined shift codes for workdays and only X for rest days. Example: S,S,A,A,N,N,X,X.
Apply the pattern to personnel with a start date. The start date is day one of the pattern; a wrong date shifts the entire rotation.
Check the weekly plan and the employee portal's shift view. “—” hours mean the shift card lacks start/finish; no shift name means the pattern/plan was not applied.
Open the attendance period only after verification. If a shift changes, do not silently overwrite the old plan; create a new plan with an effective date.

Example: G,G,G,G,G,X,X for office work; S,S,A,A,N,N,X,X for three-shift production. Apply it to one test employee first, check the eight-day calendar, then apply in bulk.

4. Module and daily task card by job

The card below tells you which guide to open first. Detailed field names and screenshots are on the linked module page.

Job / guide	Correct daily flow	Cancel / error / example
Document chain · Document entry	Sales/accounting permission; correct account, direction, date, warehouse, and stock. Use quote → order → delivery note → invoice → collection conversion; do not retype.	Do not delete a stock/financial document; cancel or reverse it. Example: convert a sales delivery note to its invoice and attach proof of delivery.
Account card · Stock card · Lists	Card-create permission; unique code, name/title, unit, tax, and group data. Attach drawings/specifications/certificates to stock and contracts/contact evidence to accounts.	A card with movements is usually not deleted; make it inactive. On “code already used,” find the existing card rather than inventing another code.
Warehouse	Warehouse-scope permission; source/destination, stock, quantity, lot/serial, pallet, and recipient. Follow order → dispatch → receipt and attach the warehouse receipt.	A received transfer is not deleted; use correction/reversal. Example: dispatch 40 parts on two pallets with vehicle, plate, and recipient.
Production · Cutting/installation	Production permission; approved recipe/revision, order, warehouse, machine, shift, and quantity. Follow recipe → request → plan → order → confirmation → quality gate; attach the correct drawing/instruction revision.	A confirmed order is not deleted; cancellation/reversal leaves a trail. Do not force past “invalid revision” or “insufficient stock.” Example: attach drawing B, work instruction 03, and the measurement report to order 125.
Quality · PPAP/SPC · Environment/cleanroom	Quality permission; order/lot/serial, characteristic, device, measurement, and decision. Attach FAI, IQC, SPC, NCR/MRB, CoC/CoA, APQP/PPAP, and calibration evidence to its record and physical lot.	An approved result is not deleted; open a new revision or NCR decision. Never hide an out-of-tolerance result when correcting it. Example: quarantine lot L-204 with measurement report MR-18.
Purchasing / IQC / maintenance / support · Corporate / subcontract / project	Department permission; supplier, request, quote, approval, due date, lot, and project. Follow purchase request → bid comparison → order → receipt → IQC; for subcontracting follow dispatch → external process → return → acceptance.	A received order or subcontract pack is not deleted; create a return/NCR. Example: attach the supplier's CoC, ASN, and return inspection report to the same subcontract pack.
Finance · Reconciliation · Profit	Finance permission; correct cash/bank account, counterparty, currency, date, amount, and cost centre. Attach the bank slip to its receipt and the contract to its project/account. Explain reconciliation differences with evidence.	Collections/payments are not deleted; use a reversing receipt. “Bank data stale” is only for users authorised for banking. Example: attach transfer slip DK-902 to the bank receipt.
CRM · Message templates · Field/B2B	Sales/field permission; account/lead, owner, stage, expected date, and amount. Record every contact as an activity; attach drawing/specification to the opportunity and contract to the order/project.	Do not delete a won/lost opportunity; update status and reason. Example: attach customer drawing A and its specification to the “New rotor quote” opportunity.
Human Resources	HR or supervisor permission; employee number, employment period, shift/pattern, legislation, and privacy. Create person, then period, pattern, plan, and attendance. Attach contract/certificate/health/PPE/exit evidence to its form.	Past employment periods are not deleted; create a new period for rehire. Keep health/identity evidence in the correct security class. Example: test the night-team pattern, then apply it in bulk.
Cockpit · Reports · Archive	View/approve permission; correct date, company, plant, warehouse, and currency filter. Check scope first, trace the number to its source list, and verify historical versions in Archive.	A report row is not deleted; correct the source record. Example: for a revenue difference, check date and sales direction, then drill down to the invoice.
Print forms · Communication · Tools · Agent	Template/publish or view permission. Check document type and purchase/sale direction in print, recipient and attachment in communication, and working folder in Tools. The Agent is decision support only; open and verify the source.	A wrongly sent document may not be recallable; preview before sending. Example: preview the sales invoice with the sales default template, then send it to the correct account.
Settings · Security/audit · Migration glossary	Ordinary users do not change administrator settings. Change your own password from your own account and never share it. Record permission, evidence-policy, and log changes with date and reason.	Instead of deleting a permission record, change its scope and active status in a controlled way. Example: a warehouse user without banking permission does not see bank-staleness alerts.

5. How to resolve an error message

Read the message before closing it; note the record number, field name, and error code.
400/422: a mandatory field or business rule is missing. Correct the named field with real information.
401/403: session or permission problem. Sign in again; if permission is missing, contact your supervisor and do not use another account.
409 / KAYIT_DEGISTI: another user saved first. Refresh, review the difference, and re-enter only the needed change.
File rejected: check type/size and starred document number or revision. Never disguise a file by changing its extension.

Do not press the same button repeatedly. Even if the screen appears to wait, the write may be queued on the server. Wait for a result or error, then refresh. If it continues, report the screen, company, record number, time, and message; never include your password.

6. End-of-day check

If you left a draft or pending record, did you record its owner and next step?
Do today's shipment, production, quality, finance, and HR records show the correct status?
Are mandatory evidence files linked to the correct record with type, number, revision, and security class?
Did you create a task/support record instead of leaving an error as a verbal remark?