How icannai/erpnext-ai-research works
This repository is a small research log, not an ERP product or agent implementation. Its documented focus is comparing ERP architectures and tracing hardware procurement, with notes on where an AI agent might use ERPNext’s API. The procurement stages below are documented workflow concepts, not code components. The README also mentions forecasting and framework internals, but their referenced files are absent from the supplied tree, so they are not represented as repository nodes.
Main entry points: README.md Research overview · procurement-flow.md Request for Quotation · erpnext-vs-sap-mm.md ERP comparison
Components 12
Other components
- Research overview
README.md - ERP comparison
architecture/erpnext-vs-sap-mm.md - Procurement notes
domain/procurement-flow.md - AI agent
- ERPNext API
- Material Request
domain/procurement-flow.md - Request for Quotation
domain/procurement-flow.md - Supplier Quotation
domain/procurement-flow.md - Purchase Order
domain/procurement-flow.md - Purchase Receipt
domain/procurement-flow.md - Purchase Invoice
domain/procurement-flow.md - Payment Entry
domain/procurement-flow.md
Connections 9
- Research overview → ERP comparison: describes
README.md - Research overview → Procurement notes: describes
README.md - AI agent → ERPNext API: uses
README.md - Material Request → Request for Quotation: leads to
README.md - Request for Quotation → Supplier Quotation: leads to
README.md - Supplier Quotation → Purchase Order: leads to
README.md - Purchase Order → Purchase Receipt: leads to
README.md - Purchase Receipt → Purchase Invoice: leads to
README.md - Purchase Invoice → Payment Entry: leads to
README.md