The purpose of this post is to test the accuracy of iDempiere’s Last PO costing method. Tests will be performed when costing level is at (a) Client, (b) Organization, and (c) Lot/Batch. Tests performed for products with and without Attribute Set values.
The LastPO Costing Method behaved as expected. There were a few issues when I set Costing Level to Lot/Batch that were independent of the LastPO Costing Method. See Questions and Comments section below for more details.
Installation: pulled for last build
Login: GardenWorld Admin
- Changed Costing Method to Last PO.
- Set System Configuration accounting to post on a schedule (not immediate).
- Restarted application server.
- Stopped GardenWorld Accounting service. This allows me to perform a “Run Now” when I want.
Product: Created new product specifically for Client Level, Last PO testing.
Last PO Costing Notes
- Matched PO posting process creates and updates the costing record.
- Material Receipt will not post unless MR matched to a PO via a Matched PO record.
- Material Receipt always posts Matched PO value regardless of LastPO costing record.
- Invoice posts at Invoice value
- Matched Invoice posts IPV for the delta between MR and Inv.
- Shipments posts at Last PO Costing Record.
- The above comments held true for all Costing Levels (Client, Organization and Lot/Batch).
- Set the Costing Level and reboot the application server
- For each Costing Level, create a new product.
- Create two POs per costing record. Receive product for first order. Post and observe results. Receive second product. Post and observe results.
- For Costing Levels of Organization and Lot/Batch, perform the above step across two organizations or Lot/Batches. Verify that the second attempt did not contaminate the costing record of first Org/Lot/Batch.
- Sale products in high quantities so that the sale qty covers multiple receipts. Confirm the Shipment COGs posting is using the product’s costing record.
- I did not test across multiple Accounting Schemas.
Questions and Observations
- When Costing Level set to Organization, why do summary organizations get a costing record?
- When Lot Costing Level, MProduct.beforeSave should ensure M_AttributeSet is not null. Otherwise, PO prepareIt() will throw a null pointer exception when trying to access the M_AttributeSet.
What is the best way to Learn iDempiere and ADempiere?
I teach an on-line class that covers how to learn, configure and audit open source ERP. It uses iDempiere as the reference ERP. Here are more details. I have learned much over the last ten years, and I have much to share. I look forward to seeing you there!!
Why consider Open Source ERP
Open source ERP gives you every opportunity to prove or disprove its ability to support your company’s ERP needs on a timeline that satisfies your organizational needs. With open source ERP, you do not face the same financial constraints nor do you face the same conflicts of interest as with commercial ERP. Instead, you invest in the appropriate skills and knowledge for your people and processes. Best of all – if open source ERP cannot solve your company’s needs, you can safely justify spending the additional $2K to $5K per person per year for life of your commercial ERP to help drive your organization’s success.
ADempiere vs iDempiere vs Openbravo vs Compiere
The ADempiere, iDempiere, Openbravo and Compiere environments are amazingly similar. iDempiere came from ADempiere. ADempiere and Openbravo came from Compiere. Compiere came from Jorg Janke. Jorg came from Oracle. As a result, iDempiere and ADempiere have much in common with Oracle’s ERP in terms of the financial feature set.
This is both good and bad. Good because iDempiere and ADempiere are quite capable to help a company grow beyond $500M USD. Bad because they tend to be more complex in that they account for multiple languages, accounting schemas, currencies, calendars, costing types, costing methods, etc…. If you are a growing organization, and you need a system that will grow with you, and you have the right internal talent/resources, iDempiere or ADempiere will be a big asset for you.
The biggest difference between these products is that ADempiere and iDempiere are pure open source. ADempiere and iDempiere make all feature available for free. Compiere and Openbravo hold back features behind a commercial or paid license.
iDempiere and ADempiere vs OpenERP
iDempiere/ADempiere (iD/AD) and OpenERP approach ERP from two very different directions. OpenERP comes out of the box with very simple options. If you are coming from QuickBooks, and you need a simple ERP system help you manage your business, OpenERP will look and feel comfortable.
iD/AD comes out of the box with every feature installed and configured to run a $200M+ USD business. If your business is growing rapidly, and you are willing to invest the time to learn an enterprise accounting system, then iD/AD will give you confidence.
Which one is best for you depends on your internal talent, growth and business complexity. Here is a post to help you learn more.
About Chuck Boecking: I am an ERP educator. I believe that open source ERP have achieved mainstream capabilities, and as a result, more companies can create greater efficiency across their organization. I started using the iDempiere code base in 2003. Back then, it was called Compiere. In 2006, I started my first multi-million dollar installation. Since then, ADempiere has helped me create great success with distribution and manufacturing companies all over the world. My vision of success is to find companies that can best use open source ERP to help them achieve a single, global instance that drives a discontinuous increase in profitability. I believe that organizations win when they own their technology.
If you have questions, comments or concerns, let me know. I definitely want your feedback.
You can contact me by phone using 512.850.6068.
My email is firstname.lastname@example.org.
You can complete the form on this page.
Thank you for taking the time. I look forward to speaking with you.