MK Client 2 Validated Screen Reference

• Classification: OBSERVED-FACT
• Captured: read-only Client 2 screen baseline; see dated examples and limitations below
• Does not own: current Runtime fact, tenant access policy or user procedure

This reference is the canonical Client-2 screen workflow and screen-capture baseline. It does not replace the current tenant access model.

Scope and operating boundary

• Tenant: MK Metal Trading (CLIENT_ID = 2).
• Workflow: order-first commercial work, booking, inbound/outbound execution, conditional scale, and Trade Summary review.
• The example values below are demonstration records from a read-only walkthrough. They are not current production records and must not be copied into live work without review.
• The workflow does not authorize writes, deletion, allocation, scale submission, or invoice changes by itself.

Menu map

Area	Menu path	Primary use
Daily control	Daily Dashboard > Daily Dashboard	Inventory, purchase, and sales snapshot.
Commercial	Operations > Orders > Commercial Orders	Purchase and sales agreements.
Receiving	Operations > Orders > Inbound Orders	Brokerage or MK Yard inbound execution.
Customer delivery	Operations > Orders > Doortrade Orders	Customer-specific doortrade receiving.
Shipping	Operations > Orders > Outbound Orders	Booking/container-linked outbound execution.
Export	Operations > Orders > Export Brokerage	One-step document/order flow when yard scale is not required.
Booking	Operations > Orders > Booking List	Vessel, cutoff, container allowance, packing list, and invoice flags.
Schedule	Operations > Schedule & Allocation > Order Schedule	Weekly inbound/outbound work schedule.
Allocation	Operations > Schedule & Allocation > Allocation Workbench	Stage and apply inventory lots to outbound targets.
Scale	Operations > Scale Portal	Physical yard weigh-in and weigh-out only.
Reporting	Billing & Reports > Trade Summary	AP, AR, costs, claim, margin, and transaction detail.
Commodity reporting	Billing & Reports > Daily Commodity Report	Monthly purchase/sales commodity movement.
Rates	Billing & Reports > Rates > Commodity Rate / Freight Rate	Commodity and trucking rate maintenance.
Administration	Admin & Masters > Master Data	Company, commodity, fuel, and common master data.
Users and menus	Admin & Masters > Users & Menus	User roles, menu tree, and role landing pages.

End-to-end screen sequence

1. Confirm the signed-in workspace is MK Metal Trading before entering order data.
2. Create the purchase agreement in Commercial Orders. Confirm the supplier, reference, commodity, quantity, UOM, rate, and estimated amount before saving.
3. Create the sales agreement in Commercial Orders. Confirm the buyer, reference, commodity, quantity, UOM, and sales rate.
4. Create the export booking. Verify shipping line, vessel, booking type, container quantity, min/max weight, ERD, SI cutoff, cutoff, ETD, ETA, POL, POD, billing customer, shipper, and commodity.
5. Create the inbound receiving order. Enter gross and tare weights; Net Weight is calculated and should not be typed directly when the screen calculates it.
6. Create the outbound sales order. Link the booking and container, then verify size, seal, shipper, consignee, carrier, commodity, and open weight.
7. Use Scale Portal check-in and check-out only when the truck or material physically uses the local yard scale. Confirm axle totals before submission.
8. Use Allocation Workbench when received inventory must be connected to an outbound shipment. Stage lots, verify remaining quantity, then apply only after review.
9. Confirm AP, AR, costs, invoice numbers, and margin in Trade Summary. Search by container first when the broader transaction filter is ambiguous.

Demonstration values and field rules

The walkthrough used one linked record set: MANUAL-20260527104706-PO, MANUAL-20260527104706-SO, MANUAL-20260527104706-BK, MANUAL-20260527104706-IN, MANUAL-20260527104706-OUT, container MSDU1047060, seal SEAL104706, and commodity 5000/6000 AL Scrap.

• Purchase: 45,000 lb at $0.62/lb; estimated purchase amount $27,900.00.
• Sales shipment: 42,000 lb at $0.84/lb; AR amount $35,280.00.
• Outbound scale example: tare 25,000 lb, gross 67,000 lb, net 42,000 lb.
• Example Trade Summary result: AP trucking $450.00, AR $35,280.00, margin $34,830.00.
• Booking searches must include the booking cutoff date in the list To date. A saved booking can appear missing when the filter ends before its cutoff.
• A scale ticket remains on the active in-yard board after check-in and leaves the board after check-out; verify the completed result from the print view or linked order detail.

Process boundaries and recovery notes

• Brokerage and Export Brokerage are document/order flows. Do not create repeated yard and scale work unless the operation physically enters the yard workflow.
• Doortrade is customer/process-specific. Use only the fields and document requirements that apply to that customer; do not add scale-only inputs by default.
• Direct outbound order creation does not automatically allocate inventory. Use Allocation Workbench when an inventory lot must be linked.
• If PDF preview or automated extraction remains loading, review the source document and enter verified rows manually. Do not apply unreviewed extracted values.
• If a saved order or booking does not appear, confirm the menu, tenant, date range, keyword, status, and list refresh before creating another record.
• Before any Save, Apply, Submit, Delete, or Send action, reread the selected record and confirm that the intended tenant and workflow branch are visible.

Screen references

Source-mapped screen baseline

SOURCE_MAPPED records the route/control caller from repository source. RUNTIME_READ_ONLY records the 2026-07-19 Local admin2 GET/HEAD-only capture; it is not mutation, field-role, device, provider, or Production proof. The 2026-07-20 local functional report is separate evidence.

Screen	Entry / required reread	Boundary and capture
mk-commercial-orders	Commercial Orders; agreement type, counterparty, reference, commodity, quantity/UOM, rate, terms and every line after reopen	Agreement state is separate from inbound/outbound/booking/scale/allocation; soft-delete only a proven unexecuted agreement. SOURCE_MAPPED / RUNTIME_READ_ONLY. capture
mk-inbound-orders	Inbound Orders; purchase source, parties, ticket/load, commodity, quantity/UOM, weight and each item after reviewed source application	Header/item, scale/execution, transload and lot states are separate; Direct/Mixed is not persisted allocation. SOURCE_MAPPED / RUNTIME_READ_ONLY. capture
mk-doortrade-orders	Doortrade Orders; customer, reference, commodity, lines and linked source order	Alias shares the inbound editor; it creates no second storage authority. SOURCE_MAPPED / RUNTIME_READ_ONLY. capture
mk-outbound-orders	Outbound Orders; sales order, booking/container, size/seal, parties, commodity, open weight, date and allocation state	Creation does not allocate inventory. SOURCE_MAPPED / RUNTIME_READ_ONLY. capture
mk-order-schedule	Order Schedule; period, source order/reference, status and linked source order	Derived planning projection, not order/execution authority. One expected aborted telemetry/fetch console error occurred under the non-GET guard. SOURCE_MAPPED / RUNTIME_READ_ONLY. capture
mk-allocation-workbench	Allocation Workbench; target shipment, lot, balance, quantity/UOM and post-apply summary	Lot balance and allocation summary require separate rereads. SOURCE_MAPPED / RUNTIME_READ_ONLY. capture
mk-booking-list	Booking List; vessel, cutoff, container limits, ports, parties, commodity, equipment and linked order	Booking, equipment, packing document and invoice projections are separate. SOURCE_MAPPED / RUNTIME_READ_ONLY. capture
bookingConfirmation, mkPackingList, packingList, fbol	Existing Booking detail document/print surfaces; reread booking, parties, vessel/ports, equipment and cargo before print/effect	Rendered values do not prove source persistence, provider delivery, file/email save or rate write. Direct capture was UNKNOWN in the read-only packet; local functional evidence is separate. packing capture
scaleticket, scale-ticket-list	Scale Portal/ticket view; vehicle, parties, cargo, agreement, gross/tare/net and signatures	Printed ticket is a projection; physical scale caller and Trade projection are separate. Read-only direct capture UNKNOWN; functional evidence is separate. capture
mk-export-brokerage	Export Brokerage; source PDF, extracted fields, parties, booking/container, commodity/rate/UOM/quantity/weight and generated links	Source upload, analysis, generated orders and job state are separate; analysis is not job creation. SOURCE_MAPPED / RUNTIME_READ_ONLY. capture
mk-commodity-rate	Commodity Rate; company, commodity, rate/UOM, effective/expiration dates and overlap filter	Master rate is separate from consuming transaction amount. SOURCE_MAPPED / RUNTIME_READ_ONLY. capture
mk-freight-rate	Freight Rate; payer, carrier, origin/destination, condition, rate and effective dates	Master rate is separate from transaction amount and provider billing. SOURCE_MAPPED / RUNTIME_READ_ONLY. capture
mk-trade-summary, mk-deal-ledger	Trade Summary; filters, parties, commodity/status and linked PO/SO/inbound/outbound/booking/container	Summary is a projection, not a transaction authority. SOURCE_MAPPED / RUNTIME_READ_ONLY. capture
mk-daily-dashboard	Daily Dashboard; date/period, totals, open work, cutoff risk and owning detail page	Total is a navigation signal, not approval/mutation. SOURCE_MAPPED / RUNTIME_READ_ONLY. capture
mk-daily-commodity-report	Daily Commodity Report; period/company/commodity, purchase/sales totals and linked source records	Report projection must not overwrite operational records. SOURCE_MAPPED / RUNTIME_READ_ONLY. capture

The read-only packet opened all 13 Operations-menu routes with GET/HEAD-only routing, aborted all other requests, made zero business writes, and had zero page errors. It is source/navigation evidence only; it does not prove field-role behavior, concurrency, physical-device accuracy, Production, or durable print/file completion. See MK admin2 functional test report for the separately authorized Local functional run.

---

Source: docs/research/mk/2026-07-19/MK_CLIENT2_VALIDATED_SCREEN_REFERENCE.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.