7005d51af3
* feat: add field `Action on Purchase Order Submission` (cherry picked from commit628ea42b63) # Conflicts: # erpnext/buying/doctype/buying_settings/buying_settings.json * feat: auto create SCO on PO submission (cherry picked from commit9ec6f1e1d6) # Conflicts: # erpnext/buying/doctype/buying_settings/buying_settings.json * feat: add field `Action on Subcontracting Receipt Submission` (cherry picked from commit762906f240) # Conflicts: # erpnext/buying/doctype/buying_settings/buying_settings.json * chore: notify user on SCO creation (cherry picked from commit745e3bfb73) * feat: add field `Purchase Order Item` in SCO Service Item (cherry picked from commit45d5cff47d) * fix: hold PO item ref in SCO Service Item (cherry picked from commit7e4dd33ab0) * feat: add field `Purchase Order Item` in SCO Item (cherry picked from commita2ede7d6d5) * fix: maintain PO and PO Item ref in SCR Item (cherry picked from commite1cea25781) * feat: auto create PR on SCR submission (cherry picked from commit040cc8d22f) * feat: add `Purchase Order` link in SCR connections (cherry picked from commitca8a5b45ba) * feat: add `Subcontracting Receipt` link in PO connections (cherry picked from commit98cba5ed30) * fix: dont show `View` button on cancelled SCR (cherry picked from commitdd80d3b9b9) * fix: use checkbox instead of select field (cherry picked from commitd366a91d9e) # Conflicts: # erpnext/buying/doctype/buying_settings/buying_settings.json * feat: Subcontracting Receipt ref in Purchase Receipt (cherry picked from commitd891bd7fac) * feat: SCR Item ref in PR Item (cherry picked from commit37b3ac7952) * feat: provision to create PR from SCR (cherry picked from commit8052103197) * chore: PR ref in SCR connections (cherry picked from commit096a2c8cd0) * fix: map warehouses in return SCR (cherry picked from commit874766a82f) * fix(ux): hide `Create Purchase Receipt` button for Subcontract Return (cherry picked from commit7145b040f1) * chore: `linter` (cherry picked from commit857f2b5a01) * test: auto create SCO on PO submit (cherry picked from commit68585f6f2b) * test: auto create PR on SCR submit (cherry picked from commit7b0cd03f88) * fix(test): `test_auto_create_purchase_receipt` (cherry picked from commit3da0aa6a0b) * chore: `conflicts` --------- Co-authored-by: s-aga-r <sagarsharma.s312@gmail.com>
ERPNext as a monolith includes the following areas for managing businesses:
- Accounting
- Warehouse Management
- CRM
- Sales
- Purchase
- HRMS
- Project Management
- Support
- Asset Management
- Quality Management
- Manufacturing
- Website Management
- Customize ERPNext
- And More
ERPNext is built on the Frappe Framework, a full-stack web app framework built with Python & JavaScript.
Installation
Login for the PWD site: (username: Administrator, password: admin)
Containerized Installation
Use docker to deploy ERPNext in production or for development of Frappe apps. See https://github.com/frappe/frappe_docker for more details.
Manual Install
The Easy Way: our install script for bench will install all dependencies (e.g. MariaDB). See https://github.com/frappe/bench for more details.
New passwords will be created for the ERPNext "Administrator" user, the MariaDB root user, and the frappe user (the script displays the passwords and saves them to ~/frappe_passwords.txt).
Learning and community
- Frappe School - Learn Frappe Framework and ERPNext from the various courses by the maintainers or from the community.
- Official documentation - Extensive documentation for ERPNext.
- Discussion Forum - Engage with community of ERPNext users and service providers.
- Telegram Group - Get instant help from huge community of users.
Contributing
License
GNU/General Public License (see license.txt)
The ERPNext code is licensed as GNU General Public License (v3) and the Documentation is licensed as Creative Commons (CC-BY-SA-3.0) and the copyright is owned by Frappe Technologies Pvt Ltd (Frappe) and Contributors.
By contributing to ERPNext, you agree that your contributions will be licensed under its GNU General Public License (v3).
Logo and Trademark Policy
Please read our Logo and Trademark Policy.