inoerp Goto Github PK

inoERP is an OneApp (Go back-end & Flutter front-end) based enterprise management system. The ERP systems contain all the required modules for running small to midsize businesses. The features are similar to Oracle R12/ Cloud Application and SAP ECC/Hana S/4.

The application uses MySQL database and OneApp JavaScript APIs to create business logic. All the database and javascript codes are available on GitHub.

The client is available for Andriod, iOS, macOS, Windows, and Web.

The server is available for Windows, macOS, and Linux.

Documentation: http://docs.inoerp.com

REST APIs http://api.inoerp.com

Web Demo:

• https https://demo.inoerp.com:8090/

• http http://demo.inoerp.com:8085/

Contact : [email protected], [email protected]

The web client is experimental and doesn't have all functionalities of native clients (Windows/macOS/Andriod/iOS). The performance of the web is also not at the same level as a native client. So, try the application with a native client and use the above URL in your native client.

1. Install MySQL Ver 8.0.+
2. Change MySQL settings on the config.json file

{
      "dbConnName": "Inoerp",
      "dbType": "MySQL",
      "host": "localhost",
      "portNumber": 3306,
      "dbName": "inoerp",
      "userName": "YourDbUserName",
      "password": "YourDbPassword",
      "connPoll": 5,
      "maxConnPoll": 10,
      "defaultRowLimit": 5
    }

3. Import the database

mysql -u root -p < /home/files/inoerp.sql

database file is available @ assets\db\mysql folder

The import process will create the required inoerp schema.

CREATE DATABASE  IF NOT EXISTS `inoerp` /*!40100 DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci */ /*!80016 DEFAULT ENCRYPTION='N' */;
USE `inoerp`;
SET GLOBAL log_bin_trust_function_creators = 1;

Ensure SET GLOBAL log_bin_trust_function_creators = 1;

1. Enter server hostname and port on the config.json file

  "application": {
    "protocol": "http://",
    "hostName": "localhost",
    "portNumber": 8085,
    "certFile": "",
    "keyFile": ""
  },

2. Change any other settings on the config.json file as per business requirement

You can start the server like any other application. You can stop the server using OneApp Desktop/Mobile client. You can also send a REST request to Your host/stop to stop the application. To send a stop request, you must have admin authority.

 ./oneapp_win.exe
 

or in Linux

nohup ./oneapp_linux &
 

Access the application using any client of your choice. The clients are available for

• Andriod
• Windows
• macOS
• iOS
• Web

Download Client

The console will show you a message stating the host and port when the server starts. Server start should not take more than 10-15 seconds.

Starting server @ localhost:8085
 

Open the application in a browser and test that you can login with the default username and password (admin/admin)

Click on the sign-in button, and the system will redirect you to the dashboard.

:::caution

The web client is experimental and doesn't have all functionalities of native clients (Windows/macOS/Andriod/iOS). The performance of the web is also not at the same level as a native client. So, try the application with a native client and use the above URL in your native client.

:::

Read how to configure and use any client @ OneApp

Below are the fully functional ERP Modules available in inoERP

Chart of Accounts inoERP allows a multi-segment accounting structure that you can use to represent all segments of a business transaction. Ex : 001-100-1020202-0100-100 Where 001 – Represents a specific company/business unit /legal entity 100 – Represents a cost center 1020202 – a Natural account such as Asset, Liability, Expense, Income, or Owners Equity

2. Calendars Define as many different financial calendars as required Ex: One calendar INO_CORP for Corporate and INO_USA, INO_UK for specific countries
3. Account Combinations
4. Currency & Conversions
5. Ledger: A set of a calendar, currency, and chart of accounts
6. Banks
7. Journal

1. Suppliers
2. AP Transactions

• 2.1 Invoices
• 2.2 Debit Memo
• 2.3 Credit Memo

3. PO/Transaction Matching
4. Multi select matching
5. AP Payments

• 5.1 Single Invoice Payment
• 5.2 Multi select Payment

6. Transfer Journals to GL

1. Customer
2. AR Transactions

• 2.1 Invoices
• 2.2 Debit Memo
• 2.3 Credit Memo
• 2.4 Deposit
• 2.5 Guarantee
• 2.6 Charge Back

3. AR Payments

• 3.1 Single Invoice Payment
• 3.2 Multi select Payment

4. Transfer Journals to GL

1. Asset
2. Depreciation
3. Transactions
4. Configuration

1. Enterprise Org
2. Legal Org
3. Business Org
4. Inventory Org 5 Address

1. Item Master
2. Unit of Measure
3. Sub inventory
4. Locator
5. Inventory Transactions
6. Material Receipts
   • PO Receipt
   • IR Receipt
   • RMA Receipt
7. Onhand Value
8. Cycle Count
   • Cycle Count Adjustment
   • Cycle Count Approval
9. ABC Analysis

1. Purchase Order

   • Standard
   • Blanket Agreement
   • Planned PO

2. Requisitions

   • External
   • Internal

3. RFQ / Quote

4. Approval for PO, Requisition

1. Sales Order - Creation & Auto Booking
2. Sales Picking
3. Delivery & Shipment
4. Auto AR Invoice

1. Departments
2. Resources
3. Routing
4. BOM
5. Super BOM

1. Material Element
2. Material OH
3. Overhead
4. Resources
5. Standard Cost
6. Cost Roll Up
7. Cost Update

1. Work Order
2. WIP Move Transactions
3. WIP Resource Transactions
4. WIP Material Transaction
5. WO Completion/Return

1. Forecast
2. MDS
3. MRP
4. Min-Max Planning
   • Multi Bin Min Max

1. Employee
   • Education
   • Experience
   • Planned PO
2. Job
3. Position
4. Compensation & Payroll
5. Leave System
6. Approval Hierarchy

1. Options
2. Value Groups
3. Transaction Types
4. Custom Reporting
5. Search
6. Multi Select
7. Mass Upload

1. User
2. Roles and Role Base Access Control
3. Notification
4. Document Approval

1. Project System
2. Asset Maintenance
3. HelpDesk

The idea behind inoERP is to provide a dynamic pull-based system where the demand /supply changes frequently and traditional planning systems (such as MRP or Kanban) are incompetent to provide a good inventory turn.

A dynamic pull system is an advanced version of a pull system that encompasses the best feature of the traditional pull system & MRP. The major disadvantage of the conventional Kanban system is the fixed Kanban size and requirement of at least two bins for the entire operation. In a sudden demand decrease, the Kanban system can result in extra inventory, and the value of unused inventory can go up to 2 bin size. Similarly, In case of unexpected demand increases can result in a line down, and the issue will be severe if the lead times are not short.

The dynamic pull system overcomes this issue by recalculating the bucket size (Kanban size/lot size) before creating any supply (requisitions/purchase order/work order). Each time a new supply is created, the system automatically decides the best supply size per the actual demand.

The old PHP version of inoERP is available @ https://github.com/php-inoerp/inoERP