0% found this document useful (0 votes)
96 views8 pages

Erpnext Documentation

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
96 views8 pages

Erpnext Documentation

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

Introduction

Today, small and medium-sized businesses (SMEs) also face some of the problems that large enterprises
do. One of them being planning and managing their resources. SMEs face similar complexities but have
limited resources to deal with them.

Businesses and government agencies have to:

 Do accounts to track their sales/purchases.


 Do their taxes.
 Pay their employees.
 Manage deliveries within promised timelines.
 Deliver quality goods and services.
 Communicate with customers, answer their queries.

Large enterprises invest millions of dollars in highly sophisticated systems like SAP. SAP and similar
systems are able to handle requirements from these large enterprises to bring their multi-country, multi-
company, multi-currency, global businesses into a single platform. This has helped them achieve
consolidation of data/records in the fundamental processes such as accounting, taxation, payroll,
reporting, and supply chain to name a few.

So even today, we continue to struggle to keep things organized. They often use a mix of applications and
tools such as spreadsheets, accounting software, web-based CRMs to manage their day-to-day record
keeping. As a consequence, they have to access different systems to understand customers' master data,
sales, cash flows, or profitability. The information exists in different silos. It becomes hard to combine the
data in order to get useful insights or alerts. This leads to SMEs being reactive instead of being proactive
in their day-to-day operations. With such a constrained way of working, there's limited scope for growth.

Open-Source ERP systems bring cost savings compared to proprietary ERP systems and this makes them
to me more popular and increasingly solicited.

Major proprietary ERP vendors include: SAP, Oracle Applications, Microsoft Dynamics, the SAGE group,
PeopleSoft, J.D.Edwards, Baan, SSA Global Technologies. Infor Global Solutions.
In the Open-Source ERP software market, we find the following major players: Adempiere, Compiere,
ERP5, GNU Enterprise, OpenERP, Openbravo, Opentaps, ERPnext, WebERP and BlueERP.

Open Source refers to any software or program whose source code is made available to other developers
for use, modification and enhancement. Open Source doesn’t mean only access to the source code, the
distribution terms of Open-Source Software must comply with several criteria related to distribution,
derived works, integrity of the author’s source code, distribution of license, and license terms among
others. The Open-Source business model relies on shifting the revenue stream from the product itself to
the product auxiliaries such as support, training, documentation, etc.

Open-Source Software adoption in large companies is considered to be a relatively recent movement.


Open-Source Software is gaining terrain in large organizations, some see it as just another development
alternative; others see in it a strategic competitive advantage.

The use of Open Source has proved itself in companies of the developed world. A study carried out by
Forrester research in September 2008 revealed that Open Source is used on average by 1 in every 5
companies in Europe and North America, and 22% of those companies have chosen a 100% Open-Source
model. The study revealed also that, in general, companies start by introducing Open Source through the
use of Apache web server or an Open-Source operating system such as GNU/Linux. Then, development
tools and programming languages such as Eclipse, PHP and Perl usually follow. The third phase is usually
adopting Open-Source solutions for database management, such as MySQL and Postgresql.

Open-source ERP system addresses some fundamental problems SMEs struggle with when managing
their resources:

 Affordability: It is a Free and Open-Source Software, freely available to download and install.
 Completeness: All necessary modules are available.
 Customization: It is easy to add fields, or add more features.
 Efficiency: Computing requirements are relatively low (cheaper to host and manage).
 Wholesomeness: A single system and database that allows multiple users to record transactions
or extract data simultaneously.
Why ERP Systems Are Important
Many growing businesses and government agencies are ignoring the importance of investing in business
technology that includes both hardware and software. Most businesses hang on to their basic
accounting solution or pieced-together solution or legacy ERP software until a change is urgently
required.

ERP Systems will help you to:

 Track all invoices and payments.


 Know what quantity of which product is available in stock.
 Identify and track your key performance indicators (KPIs).
 Identify open customer queries.
 Manage employee payroll.
 Assign tasks and follow up on them.
 Maintain a database of all your customers, suppliers, and contacts.
 Prepare quotations.
 Track your budgets and spending.
 Determine effective selling price based on the actual raw material, machinery and effort cost.
 Get reminders on maintenance schedules. And a ton more.
Disaster recovery plan
The objective of a disaster recovery plan is to ensure that you can respond to a disaster or other
emergency that affects information systems and minimize the effect on the operation of the business.
When you have prepared the information described in this topic collection, store your document in a
safe, accessible location off site.

Major goals of a disaster recovery plan:


 Minimizing Downtime: ERP systems are the backbone of many businesses, and any disruption
can result in significant downtime, leading to financial losses and operational setbacks. A well-
structured disaster recovery plan ensures that critical systems are restored promptly, minimizing
the impact on productivity and customer service.
 Protecting Data: ERP systems contain vast amounts of sensitive business data, including financial
records, customer information, and operational data. A disaster recovery plan incorporates data
backup strategies, ensuring that data is regularly backed up and can be restored quickly and
accurately in case of a disaster or system failure.
 Ensuring Compliance: Many industries are subject to regulatory requirements regarding data
protection, privacy, and business continuity. By implementing an ERP disaster recovery plan,
organizations can demonstrate their commitment to compliance and safeguard themselves
against potential legal and financial consequences.
 Preserving Reputation: Downtime and data loss can significantly damage a company’s
reputation. Customers and partners rely on organizations to deliver uninterrupted services and
protect their information. A robust disaster recovery plan ensures that businesses can recover
swiftly from disruptive events, preserving their reputation and maintaining the trust of
stakeholders.

Key Components of an ERP Disaster Recovery Plan


 Risk Assessment: Identify potential risks and vulnerabilities that could disrupt ERP operations.
Conduct a thorough analysis of the organization’s infrastructure, data centers, and IT processes
to understand potential points of failure.
 Business Impact Analysis (BIA): Assess the potential impact of ERP system disruptions on
various business functions, financials, and customer satisfaction. Prioritize critical processes and
data to determine the recovery time objectives (RTO) and recovery point objectives (RPO) for
each.
 Data Backup and Recovery: Implement a robust data backup strategy, ensuring that ERP data is
regularly backed up and stored in secure, off-site locations. Test data restoration procedures
periodically to verify their effectiveness and integrity.
 Redundant Infrastructure: Establish redundant hardware and software infrastructure to ensure
failover mechanisms are in place. This includes redundant servers, storage systems, network
components, and power supply, which can minimize downtime and enable rapid system
recovery.
 Communication and Notification: Develop a clear communication plan to inform employees,
customers, and stakeholders about the recovery process, expected downtime, and alternative
arrangements. Establish a chain of command and designated spokespersons to coordinate
communication during an ERP system disruption.
 Testing and Training: Regularly test the disaster recovery plan to identify potential weaknesses
and ensure that all components function as intended. Conduct training sessions for key
personnel involved in the recovery process to familiarize them with their roles and
responsibilities.
 Planning for the worst-case scenario is crucial when it comes to safeguarding the integrity and
availability of ERP systems. By investing time and resources in developing a comprehensive
disaster recovery plan, organizations can effectively minimize the impact of disruptions and
ensure business continuity. Remember, ERP disaster recovery is an ongoing process that requires
regular updates, testing, and adaptation to evolving risks and technologies. By staying proactive
and prepared, businesses can confidently navigate through any ERP system disruption and
emerge stronger on the other side.

Software prerequisites to install erpnext:


 Maxscale
o MaxScale is an advanced proxy, router, and load balancer:
 Mariadb
o MariaDB provides enterprise open-source database and cloud managed database
services to support scalability, mission-critical deployments, and more.
 Mariadb vs Mysql = MySQL is slightly slower than MariaDB in replication and
querying. MariaDB is slightly faster than MySQL in replication and querying.
MySQL supports super read-only function, dynamic columns, and data masking.
MariaDB supports invisible columns and temporary table space.
 Virtual machine
o Virtual machines run on a physical machine and access computing resources from
software called a hypervisor. (Microsoft hyper-v, virtual box, proxmox)
Process flow of government procurement of goods through shopping and small value procurement
(SVP)

FLOWCHART DESCRIPTION PERSON RESPONSIBLE

START

Preparation of End user (supply officer)


purchase Request / prepares PR based on approved
material request PPMP/APP

Checks and certifies that the


Certification that procurement is included in the
procurement is end-users approved PPMP
included in the
approved PPMP/APP

Provides budget clearance


indicating the approved budget
Budget Clearance for the contract (ABC) and
funding source

Approval of PR

Transmittal of PR for
the conduct of
procurement in
accordance w. ra9184
https://www.microchannel.asia/why-erp-systems-are-important/

https://docs.erpnext.com/docs/user/manual/en/global-defaults

https://frappe.io/

https://discuss.frappe.io/t/separation-of-hr-payroll-modules-into-an-app/92270

installing erpnext in Debian os https://www.buff0k.co.za/node/217

install maxscale in Debian os https://severalnines.com/blog/how-install-and-configure-maxscale-


mariadb/#:~:text=Go%20to%20ClusterControl%20%2D%3E%20Select%20the,also%20import%20an
%20existing%20one.

Similar to erpnext https://alternativeto.net/software/erpnext/?p=2

Install extra app https://www.cloudclusters.io/docs/erpnext/How%20to%20Install%20Extra%20APP


%20in%20ERPNext141667874379.html

You might also like