Provides information about CRM contacts, combining information from tables such as contact history, accounts, contact and acct managers.
Provides information about CRM opportunities, combining information from tables such as opportunities, accounts, campaigns, products, leads and acct managers.
Provides information about CRM tickets/tech support, combining information from tables such as ticket/tech support, accounts, contracts, urgency, ticket problem, solution, contact and acct managers.
Source Data: Transactions from open Payable transaction tables, with aging as of today’s date.
Common Uses: Designed to analyze the outstanding payables by vendor, vendor groupings, due date, discount date and aging.
Source Data: Transactions from open Receivable transaction tables, with aging as of today’s date.
Common Uses: Designed to analyze the outstanding receivables by customer, acct manager, salesperson, territory, other customer groupings, due date, discount date and aging.
Source Data: The GL History Files that supply the ERP’s financial reporting, along with the GL Budget and the resulting variance calculations. Accounts are grouped using the ERP’s account group (or type) files, and DataSelf Desktop users can create their own groups. The user is able to report the balances as of the end of each month, quarter, or year, as well as the net change per selected time period.
Period-ending balances and net change values are available
- “as-posted” (debits are positive, credits are negative)
- “reversed” (credits are positive, debits are negative – used for reproducing simple Income Statements, so that the expenses appear as negative numbers)
- “normalized” (both debit and credit postings and balances are positive, so that, for example, Liability and Equity accounts become a positive number – used for replicating Balance Sheets and ratios)
Common Uses: replication of the Balance Sheet and Income Statement, from which users can drill down from higher-level statement groupings to individual accounts. Includes the ability to filter or slice any report by sub-account segments. Analysis of balance sheet and income statement trends and ratios. In a dashboard with other reporting packages such as GL Transactions and SA Sales to allow a drilldown from the month-end balances to underlying details.
Source Data: GL Transaction History Files, which contain GL journal entries and the journal postings from other modules such as Accounts Payable and Accounts Receivable. The level of detail available through GL reporting varies by ERP package and setup options selected. I.E. Some systems post individual AR invoice information (such as customer number/invoice number) to the General Ledger, but most systems summarize posting batches. The Out-of-the-box reporting includes the level of detail as contained in the GL postings.
Common Uses: designed to analyze posting details, such as source journals posting to different accounts or account groups, account segments, dates, posting comments, financial ratios, etc. Posting amounts are available both as-posted (i.e. credits are negative) and “normalized” (for natural credit accounts, such as Sales, the signs are reversed, so that, for example, Sales become a positive number).
Common Customizations: journal entries may be linked back to source data, Option Fields (User Defined Fields), or comments expanded to include such information as Customer, for a Customer-based Profit and Loss.
This reporting package consists of two parts: GL Income Statement and GL Balance Sheet.
Source Data: GL financial statement balances files, which provide the total debits, credits, and ending balances for each GL account per fiscal month. The Income Statement includes two budgets, either from the ERP or from an optional outside budget source (such as an Excel file), to provide Budget versus Actual comparative analysis.
Data Format: SSAS Cube technology supports the more sophisticated data structure found in financial statements. Financial statements require that the accounts be grouped into a varying number of subheading levels, that credit accounts be shown as positive numbers, and various subgroupings be added or subtracted from one another. (The cube’s “Parent-Child” dimensions provide this functionality.)
Formal Financial Statements: Because of its flexibility and ease of formatting, MS Excel is the preferred front end for formal financial statement presentation (which are usually printed to pdf or otherwise published). The cube structures in combination with Excel allow users a great deal of flexibility to easily customize financial reports (rearranging account groupings, adding calculations or additional lines such as a Gross Margin Percent line, and fine-tuning the formatting).
Financial Statement Ad Hoc Analysis: Both DataSelf Analytics and Excel provide non-formal financial statement presentations that are easy to use and interact with, including the ability to drill down from a one or two line report displaying just the major groups (Assets, Liabilities and Equity, or Income Statement) through the grouping levels to the individual accounts’ monthly totals.
Other Financial Analysis: Both Excel and DataSelf Analytics can provide financial analysis and graphics, such as graphing the trend of the relationship between open Accounts Receivable against Net Income.
Source Data Inventory On Hand, On Purchase Order, On Sales Order by item by warehouse/location table.
Common Uses For current On Hand values and Qty Available (On Hand + PO – SO) by item (or other item groupings) and warehouse/location. This table is also often used in DataSelf Analytics as a “blend” table with another Reporting Package. For example, used with SA Sales or IN Transaction History, to compare current On Hand with historical sales or usage trends.
Common Customization: Item costing can be modified to also present cost on hand at standard cost.
Source Data: Inventory transaction history table. In most ERP systems, these tables contain inventory moves such as sales, receipts, adjustments and inventory transfers among locations/warehouses.
Common Uses: Designed to analyze inventory sales and moves over time, cost and quantity.
Common Customization: Item costing can be modified to present historical transactions at today’s standard or average cost, for better trend analysis.
Common Uses For historical On Hand trending reporting by item (or other item groupings) and warehouse/location.
Source Data: Purchase Order header and detail tables. For most ERP systems, these tables will not contain historical PO records.
Common Uses: Designed to analyze the outstanding purchase orders by vendor, product, warehouse/location, PO date and expected date.
Source Data: Invoice header and detail tables.
Common Uses: Designed to analyze historical sales, quantity sold and gross profit by customer, acct manager, product and product groupings, territory, customer address, ship to, and location/warehouse.
Source Data: Sales Order history header and detail tables. Includes Sales Order measures for amounts and quantities Booked, Sold and Lost.
Common Uses: This is a favorite with salespeople who want to track their booked orders by order date. Also analyzes the open sales orders by salesperson, customer, acct manager, product or other product groupings, territory, customer address, ship to, and location/warehouse.
The actual reporting package for each ERP/CRM may be slightly different. Subject to change without notice.