Erpnext for agriculture

Frappe Framework App Development
35

@woakes070048 Thanks for creating the proper repo on Github.

I appreciate that the repo has the basic “blueprint” for the agricultural setup and erpnext.

My implementation of ERPNext so far has yielded some ideas… I will share them here and then we can add accordingly.

  1. I am using BOM and Production Order to transfer materials from several warehouses to one warehouse and continue moving from that warehouse to another warehouse.
  2. ERPNext and its BOM currently manage only 1. Materials 2. Operations. but not 3. Fixed Assets (those that remain with the item produced for a time, such as a pot, planting tray, etc.)
    For illustration purposes, suppose I have BOM called: Planting. For that, I need:
    a. Materials: soil, seeds, water
    b. Operations: Measuring soil, filling the pot, making a hole, planting the seed, irrigating
    c. Fixed assets: Xcm diameter plastic draining pots

The BOM will produce a final product called “Potted plant”. After some days, the next production order is to transplant these to the field, at a different location, for example. When you do, you not only produce a plant in the soil, but the plastic draining pot, not only gets moved, but is now “freed up” as an asset that can be “washed” and reused. The production order in ERPNext, should have a field per fixed asset item as a “destination warehouse” so that when the production is validated, the items transfer to the “washing” warehouse, where another production order “pot washing” is generated, with a final destination warehouse “pot storage” setup there. (This is a feature request for ERPNext alone)

  1. Clearly, the functionality is already in ERPNext for a “proper hierarchy” to attach warehouses to parent warehouses, and of course the same goes for the accounts in assets. My proposal would be to create a new DocType called “Geographical” or similar. This would be similar to Accounts, Warehouses in the following manner:

  • Each unit and subsequent subunits can be nested and shown similar to “Chart of Accounts”. You can see the tree hierarchy for “geographical locations”.

  • Similar to a warehouse that has a corresponding “Account”, each “geographical unit” needs to be linked to: “Account”, “Warehouse”. This way, any action taken upon a “geographical unit” that involves transferring stock, or adding “cost of operations” through a BOM, can be registered there.

*This should replicate the proposed model for consolidation, which is already being built in to ERPNext, here: