Category Archives: ERPNext

ERPNext articles, info, comparison, experience

2024

How ERPNext become Next ERP for MH Notebook Factory (Thailand) when compared with Odoo

https://ecosoft.co.th/menghua-case-study

Interesting story how old Odoo customer (v.7 CE – Community edition with many customizations) finally decided not to upgrade to v.16 of Odoo, but to go for ERPNext.

Quotes:

Upgrade only available on Odoo Enterprise Edition which can cause a hefty cost on licensing

ERPNext pros:

  • Easier upgrade even with custom modules
  • Easier long term maintenance with built-in low code tools
  • Reasonable pricing for Fully managed Frappe Cloud

2023

Comparison of Odoo and ERPNext

https://ecosoft-odoo.blogspot.com/2023/05/how-erpnext-superior-than-odoo-odooer.html?m=1

Quotes:

Many good open source software start out with a 100% openness and attracted a lof of diehard developers. Once successful, it lets their community down. Therefore, being open source is a key crireria for me here.

Odoo itself was also 100% open source when started, until Version 9, the license was changed from AGPL (100% Open) to LGPL (Open Core). Subsequently, serveral key modules have been removed from the community version.

Another comparison Odoo vs ERPNext:
https://frappe.io/erpnext/comparisons/erpnext-vs-odoo

ERPNext vs SAP Business One B1

https://frappe.io/erpnext/comparisons/erpnext-vs-sapb1

Interesting video with comparisons from a SAP B1 partner who also started offering ERPNext:
ERPNext over SAP B1 – Sailesh Khawani | ERPNext Conference 2022

1 Lac (Lach) – A lakh (/læk, lɑːk/; abbreviated L; sometimes written lac[1]) is a unit in the Indian numbering system equal to one hundred thousand (100,000; scientific notation: 105).[1][2] In the Indian 2, 2, 3 convention of digit grouping, it is written as 1,00,000.[3] For example, in India, 150,000 rupees becomes 1.5 lakh rupees, written as ₹1,50,000 or INR 1,50,000. https://en.wikipedia.org/wiki/Lakh

And another video for transportation service company FR8, who migrated from SAP B1 to ERPNext:
Proprietary to Open Source Journey from SAP B1 to ERPNext | Jay

ERPNext – common party accounting (customer vendor invoice offsetting)

GitHub code for common party accounting:
https://github.com/frappe/erpnext/blob/develop/erpnext/accounts/doctype/party_link/party_link.py

Documentation: https://docs.frappe.io/erpnext/user/manual/en/common_party_accounting

More documentation and examples with video: https://fosserp.com/blog/shorts/using-common-party-accounting-in-erpnext

Short docu on setting up common party accounting in ERPNext

In practice happens that a regular vendor might purchase your services or goods (so it is becoming a customer). And vice versa – usual customer can provide goods or services to your company. In order to offset (net, netting) the invoices and track financial balances between companies you can activate and use in ERPNext the “Common Party Accounting” functionality.

  1. In ERPNext navigate to app/erpnext-settings -> “Accounts Settings” and enable “Common Party Accounting” in the ‘Invoicing Features’ section.
  2. Two scenarios to link the customer or supplier. Depending on what is the primary role – If the party is already created as a supplier and is usually a supplier, then create it as a customer too. Go to the “Supplier”, click on “Link with Customer” from the “Actions” option to link.
    Respectively if the party is already created as a customer and this is its usual role, then create a supplier. Go to the “Customer”, and click on “Link with Supplier” from the “Actions” option to link.
  3. Now, create a sales invoice against the customer (who usually is supplier) who was assigned as the secondary party in the previous step.
  4. Upon submission of the sales invoice, an automatic journal entry will be made against the linked supplier, creating an advance balance. Also the invoice is marked as paid.
  5. You can now reconcile this journal entry advance against a Purchase Invoice.

This process allows you to adjust your purchases with the sales transactions.

MariaDB table which stores the links: tabParty Link

+-----------------+--------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+-----------------+--------------+------+-----+---------+-------+
| name | varchar(140) | NO | PRI | NULL | |
| creation | datetime(6) | YES | | NULL | |
| modified | datetime(6) | YES | MUL | NULL | |
| modified_by | varchar(140) | YES | | NULL | |
| owner | varchar(140) | YES | | NULL | |
| docstatus | int(1) | NO | | 0 | |
| idx | int(8) | NO | | 0 | |
| primary_role | varchar(140) | YES | | NULL | |
| secondary_role | varchar(140) | YES | | NULL | |
| primary_party | varchar(140) | YES | | NULL | |
| secondary_party | varchar(140) | YES | | NULL | |
| _user_tags | text | YES | | NULL | |
| _comments | text | YES | | NULL | |
| _assign | text | YES | | NULL | |
| _liked_by | text | YES | | NULL | |
+-----------------+--------------+------+-----+---------+-------+

In order to get easily from within ERPNext a list of current settings, you can create a new Query report (Report List -> Add report) with the following SQL query:

select name, primary_role, secondary_role, primary_party, secondary_party, creation, docstatus, idx
  FROM
    `tabParty Link` AS party
    

Or use "Party Link" in search field and choose "Party Link List" to get list of already existing links between Vendors and Customers.
e.g.: erpnext.yoursite.com/app/party-link