valdiating
This commit is contained in:
@@ -27,9 +27,10 @@ Several occasions during the configuration of the **Manufacturing** module, it b
|
|||||||
A product can be created in either of these modules **Manufacturing** module or in the **Stock Management** module or even on **Sales** module. On each of these modules there are some additional info related to the product and the module in use. The image below show the message when a product was being created in the **Stock Management** module and the module is not configured.
|
A product can be created in either of these modules **Manufacturing** module or in the **Stock Management** module or even on **Sales** module. On each of these modules there are some additional info related to the product and the module in use. The image below show the message when a product was being created in the **Stock Management** module and the module is not configured.
|
||||||
|
|
||||||

|

|
||||||
<img src="assigments/img/03-moduleOverlap.png" align="right" width="400px"/>
|
|
||||||
|
|
||||||
There is no way we can achieve a minimalist implementation of an ERP system with a single module. When dealing with customers, a **Sales** module is mandatory, but in a situation the company has an stablished sales team. Adding a **CRM** module will benefit the data in the system and the sales team work. For these two separate modules the common information is the *Customers*, on each module there is some specific data, but the common information is shared between both modules. *Product* is another information item of an ERP that is used cross several modules. In the **Sales** module the most information is the cost price, yet on **Stock Management** the inventory and location is a key information.
|
There is no way we can achieve a minimalist implementation of an ERP system with a single module. When dealing with customers, a **Sales** module is mandatory, but in a situation the company has an stablished sales team.
|
||||||
|
<img src="assigments/img/03-moduleOverlap.png" align="right" width="400px"/>
|
||||||
|
Adding a **CRM** module will benefit the data in the system and the sales team work. For these two separate modules the common information is the *Customers*, on each module there is some specific data, but the common information is shared between both modules. *Product* is another information item of an ERP that is used cross several modules. In the **Sales** module the most information is the cost price, yet on **Stock Management** the inventory and location is a key information.
|
||||||
|
|
||||||
## Selection
|
## Selection
|
||||||
<img src="assigments/img/03-ModuleSelection.png" align="left" width="400px"/>
|
<img src="assigments/img/03-ModuleSelection.png" align="left" width="400px"/>
|
||||||
|
|||||||
@@ -9,6 +9,9 @@
|
|||||||
id="svg5"
|
id="svg5"
|
||||||
inkscape:version="1.2.1 (9c6d41e410, 2022-07-14, custom)"
|
inkscape:version="1.2.1 (9c6d41e410, 2022-07-14, custom)"
|
||||||
sodipodi:docname="03-moduleOverlap.svg"
|
sodipodi:docname="03-moduleOverlap.svg"
|
||||||
|
inkscape:export-filename="03-moduleOverlap.png"
|
||||||
|
inkscape:export-xdpi="150"
|
||||||
|
inkscape:export-ydpi="150"
|
||||||
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
|
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
|
||||||
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
|
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
|
||||||
xmlns="http://www.w3.org/2000/svg"
|
xmlns="http://www.w3.org/2000/svg"
|
||||||
|
|||||||
|
Before Width: | Height: | Size: 12 KiB After Width: | Height: | Size: 12 KiB |
Reference in New Issue
Block a user