The purpose of this lesson is to teach a successful go-live strategy called Audit Summaries.
Definition
An audit summary window is an iDempiere window that helps you quickly identify and resolve instances of all known issues.
Examples Issues
There are many many ways to create invalid or inaccurate data in an ERP system. There are times when you know a specific situation will lead to errors. the Audit Summary Window make is easy to catch all known issues in a single place. Here are some example of errors/issues:
Your company decides that a Vendor BP should only have one address that is flagged as isRemitTo. The Audit Summary Window will have a tab called "Vendor BP". The results in the tab will show all Vendor BP's with the above issue. Users can easily zoom to the offending BPs to remedy all issues.
Your company decides that the Product window->Price tab->Limit Price field should always be equal to the products costing record. The Audit Summary Window will have a tab called "Product Pricing". This will will have records of all Products that violate the above condition. Users can easily zoom to the offending products for manual intervention, or an ERP Admin and create a query to update all offending products accordingly.
As you create new tabs, set the TabLevel = 0. This means there is no parent child relationship between all the tabs.
Each new tab created will be backed by a view. The view should begin with "ChuBoe_Audit" and end with "_V". Feel free to replace "ChuBoe" with your company's call sign.
Each view must have the iDempiere required fields of AD_Client_ID, AD_Org_ID, Created, CreatedBY, Updated, UpdatedBy.
Set the tab's "Single Row Layout" field to false or un-checked. This helps make the data easier to read.
Set the tab's "Insert Record" field to false or un-checked. This ensure you do not get an error when you show a tab with no results.
Do not be afraid to union different issues in the same view. If you find 5 different issues that can happen for the BP record, update append your current view to include a different check with a different "AuditText" value describing the different issue.
You can include context in the Audit Text - as demonstrated in the sample tab.