Module catalog
Purpose
Section titled “Purpose”Map business modules to repository folders for navigation.
modules.txt entries
Section titled “modules.txt entries”From leekimerp/leekimerp/modules.txt:
- Lee Kim Alliance ERP —
lee_kim_alliance_erp/(core custom DocTypes, pages, reports) - Time Tracking Module —
time_tracking_module/ - Singpass —
singpass/ - Incorporate —
incorporate/ - Payroll Plus —
payroll_plus/
Cross-cutting packages
Section titled “Cross-cutting packages”| Folder | Role |
|---|---|
api/ | Whitelisted HTTP API |
override/ | DocType class overrides |
scripts/ | Payroll, company, sales invoice helpers |
scheduler_events/ | Cron entry points |
tasks.py | Task functions referenced by hooks or jobs |
hook_events/, hook_methods.py | Validation and automation |
fixtures/ | Data import definitions |
Module dependency (narrative)
Section titled “Module dependency (narrative)”flowchart TB M01[Users & Desk roles] M02[Partners / Applications] M03[Sales & Billing] M08[Payroll] M07[Accounts] M01 --> M02 M01 --> M03 M01 --> M08 M02 --> M03 M03 --> M07 M08 --> M07Entry points
Section titled “Entry points”- Desk: Module visibility is role-dependent.
- Code: Start from
hooks.pyand the module folder for the feature you need.
Dependencies
Section titled “Dependencies”ERPNext standard apps (e.g. erpnext, hrms) as installed on the site.
Known gaps
Section titled “Known gaps”Submodule boundaries are Frappe modules; some logic spans multiple folders (e.g. Xero in api/xero.py plus DocTypes under lee_kim_alliance_erp).