mirror of
https://github.com/frappe/erpnext.git
synced 2026-05-03 05:28:27 +00:00
[js-libs] upgraded to latest bootstrap and font-awesome
This commit is contained in:
@@ -1,12 +1,11 @@
|
||||
---
|
||||
{
|
||||
"_label": "Introduction"
|
||||
"_label": "Introduction",
|
||||
"_title_image": "img/why-erpnext.png"
|
||||
}
|
||||
---
|
||||
## What is an ERP and why should I care?
|
||||
|
||||

|
||||
|
||||
Small business are not so different from large ones. They contain most of the complexities of a large business but with many more constraints. Small businesses have to communicate with customers, do accounts, pay taxes, do payroll, manage timelines, deliver quality, answer questions and keep everyone happy just like large businesses.
|
||||
|
||||
And to it *efficiently*.
|
||||
|
||||
@@ -1,14 +1,13 @@
|
||||
---
|
||||
{
|
||||
"_label": "Accounting Setup"
|
||||
"_label": "Accounting Setup",
|
||||
"_title_image": "img/setup-accounting.png"
|
||||
}
|
||||
---
|
||||
## Chart of Accounts
|
||||
|
||||
The Chart of Accounts forms the blueprint of your organization. The overall structure of your Chart of Accounts is based on a system of double entry accounting that has become a standard all over the world to quantify how a company is doing financially.
|
||||
|
||||

|
||||
|
||||
The Chart of Accounts helps you answer:
|
||||
|
||||
- What is your organization worth?
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
{
|
||||
"_label": "Before We Start"
|
||||
"_label": "Before We Start",
|
||||
"_title_image": "img/before-we-start.png"
|
||||
}
|
||||
---
|
||||
## Before We Start
|
||||
@@ -13,8 +14,6 @@ ERPs are not required.
|
||||
|
||||
Like exercise.
|
||||
|
||||

|
||||
|
||||
Human body does not require to be exercised today or maybe tomorrow, but in the long run, if you wish to maintain your body and its health, you should get on the treadmill.
|
||||
|
||||
In the same way, ERPs improve the health of your organization over a long run by keep it fit and efficient. The more you delay putting things in order, the more time you lose and the closer you get to a major disaster.
|
||||
|
||||
64
docs/docs.user.setup.codification.md
Normal file
64
docs/docs.user.setup.codification.md
Normal file
@@ -0,0 +1,64 @@
|
||||
---
|
||||
{
|
||||
"_label": "Item Codification"
|
||||
}
|
||||
---
|
||||
|
||||
> To Codify or Not To Codify, is the question.
|
||||
|
||||
If you already have a running business with a number of physical items, you would have probably coded your items. If you have not, you have a choice. We recommend you should codify, but its your call.
|
||||
|
||||
Item codification is always a sensitive topic and wars have been fought on this (not joking). In our experience, when you have items that cross a certain size, life without codification is a nightmare.
|
||||
|
||||
### Benefits
|
||||
|
||||
- Standard way of naming things.
|
||||
- Less likely to have duplicates.
|
||||
- Explicit definition.
|
||||
- Help you quickly find if a similar item exists.
|
||||
- Item names get longer and longer as more types get introduced. Codes are shorter.
|
||||
|
||||
### Pain
|
||||
|
||||
- You have to remember the codes!
|
||||
- Harder for new team members to pick up.
|
||||
- You have to create new codes all the time.
|
||||
|
||||
### Example
|
||||
|
||||
You should have a simple manual / cheat-sheet to codify your items instead of just numbering them sequentially. Each letter should mean something. Here is an example:
|
||||
|
||||
If your business involves wooden furniture, then you may codify as follows:
|
||||
|
||||
Item Codification Summary Sheet
|
||||
(SAMPLE)
|
||||
|
||||
First letter: "Material" Third letter: "Size"
|
||||
|
||||
- W - Wood - 0 - less than 1mm
|
||||
- H - Hardware - 1 - 1mm - 5mm
|
||||
- G - Glass - 2 - 5mm - 10mm
|
||||
- U - Upholstery - 3 - 10mm - 10cm
|
||||
- P - Plastic
|
||||
|
||||
Second Letter: "Type"
|
||||
|
||||
For Wood: For Hardware:
|
||||
|
||||
- S - Sheet - S - Screw
|
||||
- B - Bar - N - Nut
|
||||
- L - L-section - W - Washer
|
||||
- M - Molded - B - Bracket
|
||||
- R - Round
|
||||
|
||||
The last few letters could be sequential. So by looking at code **WM304** - you know its a wooden molding less than 10cm in size
|
||||
|
||||
### Standardization
|
||||
|
||||
If you have more than one person naming items, the style of naming items will change for everyone. Sometimes, even for one person, he or she may forget how did they name the item and may create a duplicate name _"Wooden Sheet 3mm" or "3mm Sheet of Wood"?_
|
||||
|
||||
### Rationalizing
|
||||
|
||||
It is a good practice to have minimum varieties of items so that you keep minimum stock, housekeeping is simpler etc. When you are planning a new product and you want to know if you are already purchasing a part in some other product, the item codes will help you quickly determine if you are using a similar raw material in another product.
|
||||
|
||||
We believe if you do this small investment, it will help you rationalize things as your business grows, though its okay not to codify if you have less items.
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
{
|
||||
"_label": "Foundation: Customer"
|
||||
"_label": "Foundation: Customer",
|
||||
"_title_image": "img/customers.png"
|
||||
}
|
||||
---
|
||||
You can either directly create your Customers via
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
{
|
||||
"_label": "Foundation: Item"
|
||||
"_label": "Foundation: Item",
|
||||
"_title_image": "img/items.png"
|
||||
}
|
||||
---
|
||||
Items, Customers and Suppliers form the foundation of any ERP system.
|
||||
|
||||
Reference in New Issue
Block a user