BusinessFlows

Layman's summary

Imagine this process like a field work chain: Project requests goods/services, Admin checks, Logistics/Procurement carries out the purchase, then Accounting pays until completed. This document helps you see the big flow without having to read the code.

Visual Summary (Main Flow)

Flow	Goals	Core actors	Final output
Projects	Open project work	Admin, PM, SPV	Active project + attached team
SPB	Request for materials from the field	Project/SPV, Head Admin	SPB approved/revised/rejected
PO	Purchases from suppliers	Logistics/Admin, Head Admin, SPV	PO approved then goods received/complaint
SPK	Employment/service contracts	Role SPK, Head Admin, Accounting	SPK approved then SPK payment runs
Payment	PO/SPK Repayment	Accounting, Head Admin	Payment verified / split paid

---

🏗️ 1) Flow Project

Flow chart

Sequences

Note

Team detail columns across pivot tables (e.g. PM/SPV/logistics) are still scattered. The complete relationship structure is on the Database Design Full page.

---

📦 2) Flow SPB (Request for Goods)

Flow chart

Sequences

---

🧾 3) Flow PO (Pre Order)

Flow chart

Sequences

---

🛠️ 4) Flow SPK

Flow chart

Sequences

---

💳 5) Flow Payment (PO + Split)

Flow chart

Sequences

---

Important Controls

• Role access determines who can make/approve/revise.
• Some status updates trigger PDF regeneration.
• Notification integration (FCM) exists for certain events.
• Soft delete affects historical data in reports.

Verification Notes

• Status: Partial
• Scope: SLA between stages and detailed auto-transition rules per role are not yet explicitly visible in one source.
• Action: Synchronize with operational SOP + verify Livewire screen per status (reference VM-005 in Verification Matrix).