1d5935a10f
* refactor(Supplier): custom buttons call make methods (backport #49840) (#49841) Co-authored-by: Raffael Meyer <14891507+barredterra@users.noreply.github.com> * fix(Common Code): fetch canonical URI from Code List (backport #49882) (#49883) Co-authored-by: Raffael Meyer <14891507+barredterra@users.noreply.github.com> fix(Common Code): fetch canonical URI from Code List (#49882) * fix: Set paid amount automatically only if return entry validated and has negative grand total (#49829) (cherry picked from commitdcbcc596f2) # Conflicts: # erpnext/public/js/controllers/taxes_and_totals.js * fix: resolved conflict * fix: linter; dont change doc after DB update (backport #49907) (#49909) Co-authored-by: Raffael Meyer <14891507+barredterra@users.noreply.github.com> Co-authored-by: ruthra kumar <ruthra@erpnext.com> fix: linter; dont change doc after DB update (#49907) * fix: do not fetch disabled item tax template (cherry picked from commitb10cf4a928) # Conflicts: # erpnext/public/js/controllers/transaction.js # erpnext/stock/get_item_details.py * chore: fix conflicts * chore: fix conflicts * chore: fix linters issue * feat: dynamic due date in payment terms when fetched from order (backport #48864) (#49937) * feat: dynamic due date in payment terms when fetched from order (#48864) * fix: dynamic due date when payment terms are fetched from order * fix(test): use change_settings decorator for settings enable and disable * fix(test): compare schedule for due_date dynamically * fix: save conditions for due date at invoice level * fix: make fields read only and on change of date unset the date condition fields * fix: remove fetch_form * fix: correct field assingment * fix: revert unwanted changes * refactor: streamline payment term field assignments and enhance discount date handling * refactor: remove payment_term from fields_to_copy and optimize currency handling in transaction callback * refactor: ensure default values for payment schedule and discount validity fields (cherry picked from commit3c70cbbaf8) # Conflicts: # erpnext/accounts/doctype/payment_schedule/payment_schedule.json # erpnext/accounts/doctype/payment_schedule/payment_schedule.py # erpnext/public/js/controllers/transaction.js # erpnext/selling/doctype/sales_order/test_sales_order.py # erpnext/stock/doctype/purchase_receipt/test_purchase_receipt.py * chore: resolve conflicts --------- Co-authored-by: Lakshit Jain <ljain112@gmail.com> --------- Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> Co-authored-by: Raffael Meyer <14891507+barredterra@users.noreply.github.com> Co-authored-by: Nabin Hait <nabinhait@gmail.com> Co-authored-by: ruthra kumar <ruthra@erpnext.com> Co-authored-by: ljain112 <ljain112@gmail.com> Co-authored-by: rohitwaghchaure <rohitw1991@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.