Game in the Brain

 What makes ERPNext or any ERP hard to learn is the dizzying prerequisites. Because ERPs need to link data there will always be prerequisites to coordinate. Making a Material Request may sound simple until you realize all the CONTEXT that you need: Who is requesting, What department (linking to a User and Department data relationship), What for (linking to a Project and Client), what is it specifically part of (the Bill of Materials this is part of), the Supplier, what Accounts is this going to part of (Charter of Accounts). 

So any ERP system will have a Dizzying set of Requirements because everyone who uses it wants checks – they want to know if the request or action was done for the RIGHT reasons, by the right people, and with the right method. 

You know something is incorrect when any of these can be Logically and Simply discovered as WRONG by the preset criteria we make in the labyrinth of Prerequisites. We know its wrong when it’s not Part of a Clients Request, if it Exceeds our Budget for that Project, that There are more Pending (Billable) projects that should be prioritized… 

So it is only natural that As we Have more Checks and Criteria to know if an Action is Correct, then we BUILD a lot of constraints and prerequisites. 

Because there is so much Complexity or Prerequisites, we create a map and checklist of the CORE prerequisites in any system. Then we learn how to update these and which of these can be “updated on the fly” or will require a Massive Spreadsheet Update. 

You can imagine these Core Prerequisites as the Landmarks, the most frequently referenced and whose silhouettes are prominent in the distance. Paths have more specific details and these are the individual paths for each process: for material requests, purchase orders, payment vouchers, taxes etc…