We have moved to a better location, across the street:
Our team has found the Providex database hard to build solutions with. Sage has built the UQE for use in Sage Intelligence to overcome limitations like multiple left joins but important features like sub-queries are still not supported.
Hit the image below for access to some documentation on Providex:
Consolidated Financial Reporting using Sage Intelligence. Also applies to non Financial Reporting….
Due to reasons like convention, technical limitations or just an embrace of statutory financial reporting doubling up as management reporting, profit and loss reports often report on activity for the current and previous years only.
I know that for a start-up or a company that experiences a high degree of change, assessing trends over multiple years is not necessarily helpful to managing the business. But there are many companies who would benefit from having a Profit and Loss Statement for many years to assess trends in incomes and expenses.
By creatively applying Business Intelligence, we encourage BI professionals to give customers that option and we encourage companies to insist on multi-year Profit and Loss solutions. Below is a basic example of such a solution, accompanied by a graphical representation of the trend.
Many of our manufacturing customers use Builds of Materials in their ERP to aid in the manufacturing process: configuring recipes, managing inputs, planning for requirement and managing projected profits.
Although these are very useful for a manufacturing environment, for a system to truly be useful to its owner, it must incorporate business information from Sales Orders, Purchase Orders, Component QOH and Unfinished Builds. And finally, what the business manager cares most about is the delivery of this information on an interactive reporting platform.
In this article I wish to share the concept of reporting on shared components between Builds….
One of our customers recently requested that we add the 2 fields below with the red borders to the ‘BOM Requirements Planning’ solution that we had built for them. I thought this was a great idea due to the following considerations…..
When planning requirements in a manufacturing environment, it often happens that component items are assessed and ordered in the context of a particular Assembly. As an example, if Assembly A and B each require 10 components of item Y and both A and B need to be built, then in the context of A and B alone, only 10 of item Y are required when the reality is that 20 of item Y are required.
Hence, the field below named ‘OrderQtyAll’ is one that discloses the total number of components required, including those that are required for builds other than the current build being reported on and analyzed. Consequently the field named ‘RequiredAll’ now reflects the true quantity required by considering QOH, All component items indirectly on order across all builds, Sales Orders and Purchase Orders.
The Working Capital Cashflow Model reveals relevant cash related information relating to Working Capital components. It answers the question that business managers ask with high frequency: ‘how much money will there be in the bank account during and after the current working capital cycle’.
It does this by asking the business manager ‘how many days would you like to forecast cashflows for?’
The model then reveals the Accounts Receivable and Accounts Payable due over the prediction period.
It also predicts other cash outflows incl. Payroll, based on cash outflow activity from the previous month for the same period.
By having this predictive cash information real-time and in one place, you can now take corrective actions by collecting debts with precision,
renegotiate vendor terms and identify other cash outflows that may not be required this month or may not be required at all.
It’s the working capital cashflow model that you dreamed about but have never had the luxury of possessing….until now.
Download this solution here > >
Microsoft® Excel® 2007+