645ee2d822
* refactor: misc pick list refactors - make tracking fields read only and no-copy 🤦 - collapse print settings section, most users configure it once and forget about it, not need to show this. - call pick list grouping function directly - use get_descendants_of instead of obscure db function (cherry picked from commit5c3f9019cc) * test: bundles in picklist (cherry picked from commit7d5682020a) # Conflicts: # erpnext/stock/doctype/pick_list/test_pick_list.py * feat: Pick list from SO with Product Bundle (cherry picked from commit36c5e8a14f) * refactor: sales order status update - rename badly named variables - support updated packed items (cherry picked from commite64cc66df7) # Conflicts: # erpnext/stock/doctype/pick_list/pick_list.py * perf: single update per Sales Order. For each SO item the sales order picking status was being updated, this isn't required and wasteful. (cherry picked from commitc3fc0a4f55) * feat: back-update min picked qty for a bundle (cherry picked from commit60bc26fdbe) * refactor: simplify needlessly complicated code (cherry picked from commit3ddad6891a) * refactor: groupby using keys instead of int index (cherry picked from commit277b51b404) * refactor: simpler check for non-SO items (cherry picked from commitf574121741) * feat: create DN from pick list with bundle items (cherry picked from commit23cb0d684d) * refactor: remove unnecssary vars also remove misleading docstring (cherry picked from commit25485edfd9) * fix: round off bundle qty This is to accomodate bundles that might allow floating point qty. (cherry picked from commit41aa4b3524) * feat: transfer picklist stock info to packing list (cherry picked from commit1ac275ce61) * test: product bundle fixture (cherry picked from commitee54ece8fd) * test: test bundle - picklist behaviour (cherry picked from commit9e60acdf56) # Conflicts: # erpnext/stock/doctype/pick_list/test_pick_list.py * fix: compare against stock qty while validating Other changes: - only allow whole number of bundles to get picked (cherry picked from commit8207697e43) * fix: dont map picked qty and consider pick qty for new PL Co-Authored-By: marination <maricadsouza221197@gmail.com> (cherry picked from commit47e1a0104c) * fix(UX): only show pick list when picking is pending [skip ci] (cherry picked from commit9a8e3ef235) * chore: make picked qty read only (cherry picked from commitebd5f0b1bb) * chore: conflicts and py3.7 compatibilty Co-authored-by: Ankush Menat <ankush@frappe.io>
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 requires MariaDB.
ERPNext is built on the Frappe Framework, a full-stack web app framework built with Python & JavaScript.
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.
Full 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).
Virtual Image
You can download a virtual image to run ERPNext in a virtual machine on your local system.
System and user credentials are listed on the download page.
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.
Contributing
- Issue Guidelines
- Report Security Vulnerabilities
- Pull Request Requirements
- Translations
- Chart of Accounts
Logo and Trademark
The brand name ERPNext and the logo are trademarks of Frappe Technologies Pvt. Ltd.
Introduction
Frappe Technologies Pvt. Ltd. (Frappe) owns and oversees the trademarks for the ERPNext name and logos. We have developed this trademark usage policy with the following goals in mind:
- We’d like to make it easy for anyone to use the ERPNext name or logo for community-oriented efforts that help spread and improve ERPNext.
- We’d like to make it clear how ERPNext-related businesses and projects can (and cannot) use the ERPNext name and logo.
- We’d like to make it hard for anyone to use the ERPNext name and logo to unfairly profit from, trick or confuse people who are looking for official ERPNext resources.
Frappe Trademark Usage Policy
Permission from Frappe is required to use the ERPNext name or logo as part of any project, product, service, domain or company name.
We will grant permission to use the ERPNext name and logo for projects that meet the following criteria:
- The primary purpose of your project is to promote the spread and improvement of the ERPNext software.
- Your project is non-commercial in nature (it can make money to cover its costs or contribute to non-profit entities, but it cannot be run as a for-profit project or business). Your project neither promotes nor is associated with entities that currently fail to comply with the GPL license under which ERPNext is distributed.
- If your project meets these criteria, you will be permitted to use the ERPNext name and logo to promote your project in any way you see fit with one exception: Please do not use ERPNext as part of a domain name.
Use of the ERPNext name and logo is additionally allowed in the following situations:
All other ERPNext-related businesses or projects can use the ERPNext name and logo to refer to and explain their services, but they cannot use them as part of a product, project, service, domain, or company name and they cannot use them in any way that suggests an affiliation with or endorsement by ERPNext or Frappe Technologies or the ERPNext open source project. For example, a consulting company can describe its business as “123 Web Services, offering ERPNext consulting for small businesses,” but cannot call its business “The ERPNext Consulting Company.”
Similarly, it’s OK to use the ERPNext logo as part of a page that describes your products or services, but it is not OK to use it as part of your company or product logo or branding itself. Under no circumstances is it permitted to use ERPNext as part of a top-level domain name.
We do not allow the use of the trademark in advertising, including AdSense/AdWords.
Please note that it is not the goal of this policy to limit commercial activity around ERPNext. We encourage ERPNext-based businesses, and we would love to see hundreds of them.
When in doubt about your use of the ERPNext name or logo, please contact Frappe Technologies for clarification.
(inspired by WordPress)