Reporting Tool
StrategicERP’s Reporting Tool is part of its integrated ERP system used to build dashboards and generate real-time business reports across modules like finance, projects, sales, HR etc. Users can filter records, configure parameters, and export results in standard formats for analysis
Custom Report creation with Reporting Tool
Dashboard creation with ReportingTool
Pivot Reports
Pivot reports provide an interactive, Excel-style multi-dimensional table view.
Users can dynamically pivot columns and rows, group data, and perform aggregation (sum, average) on numeric fields.
Ideal for ad hoc data analysis and uncovering insights with flexible data reshaping.
Accessible via the Reporting Tool with options to toggle on/off from default HTML reports.
MRT Reports
MRT reports are designed for composite reporting where multiple related sub-reports or charts are combined into one view.
They often provide real-time dashboards by aggregating core business metrics or transactions from various modules.
Useful for overview reports or management summaries requiring consolidated data from diverse sources.
MRT offers enhanced filtering and drill-down capabilities across linked reports.
Docx Reports
Docx reports generate formatted Word documents based on pre-designed Docx templates.
These are typically used for official reporting, invoices, contracts, or formatted statements requiring customized branding and static data presentation.
Users create and upload Docx templates with placeholders, which get populated dynamically during generation.
Perfect for customer-facing or legally binding documents where visual and layout control is essential.
Common report creation errors in StrategicERP typically stem from configuration mistakes, SQL mismatches, or file handling issues. These errors can occur when using the Reporting Tool, Report Development Form, or Docx-based report templates, and most have straightforward fixes documented in the ERP knowledge base and field guidance.
Frequent Reporting Errors and Fixes
1. Field Mapping or Table Alias Errors
Error: Incorrect table alias (T1, T2, etc.) or unmapped fields in the Report Development Form cause blank outputs or SQL exceptions.
Fix: Ensure proper alias-to-column matching for each selected table; verify that all columns belong to the same module or are mapped correctly using the “Add Column” and “Alias” fields in the report form.
2. Missing or Incorrect Form IDs
Error: “Form ID not found” or inaccessible report fields. This occurs when linked modules are incorrectly chosen.
Fix: Select the correct module and form ID before adding fields. Each report must have a unique sequence and form mapping for ERP to retrieve table relationships.
3. Filename or Download Path Issues
Error: Downloaded reports have generic or wrong filenames when shared via mail or exports.
Fix: Open the report using the System Utility (SU) module and rename files using the configuration path under the Filename property field as per documentation.
4. SQL Report Not Working on Custom State
Error: “SQL report not working” message appears for custom or Pivot reports when queries include deprecated syntax or missing filters.
Fix: Review SQL statements via the development form, removing redundant subqueries; revalidate with available ERP table fields before refreshing the report.
5. Save Button Not Responding
Error: Occurs during report saving under “Custom Report Creation Using Reporting Tool” due to expired sessions.
Fix: Regenerate OTP and ensure all mandatory fields (module, title, share options) are filled before saving.
6. HTML/Docx Report Misalignment
Error: Generated Docx or HTML reports misformat fields or ignore data.
Fix: Verify column IDs correspond to form field names and upload a properly linked Docx template. Use only expected field keys (case-sensitive) as cited in the “Docx Report Management Form”.
Steps to resolve report permission errors
Report permission errors in StrategicERP usually occur when users lack the required module-level, form-level, or report-level access rights configured through the ERP’s Permission Management module. These errors prevent users from viewing, executing, or exporting reports and can be resolved through administrative access configuration.
Typical Error Messages
When permission settings are misconfigured, users may encounter messages like:
“Access Denied for Report”
“User does not have permission to execute this report”
“Record visibility restricted due to role settings”.
Steps to Resolve Report Permission Errors
Step 1. Verify Role and Module Permissions
Log in with an Admin or ERP SuperUser account.
Navigate to ERP Admin → Permission Management.
Select the Module Name and Form Name associated with the report.
Confirm that the user’s assigned role (e.g., “Project Manager” or “Account User”) has Read/Write/Execute permission enabled for that module.
If missing, enable necessary permissions by toggling corresponding checkboxes and saving changes.
Step 2. Review User Group Inheritance
Go to User Group Settings under Permission Management.
Verify whether the user inherits access from another group; if not, assign an appropriate Group Role Template.
Use the “Copy Permissions” feature to replicate access rights from existing functional users who can run reports successfully.
Step 3. Check Report Form Access
Open Reporting Tool → Report List.
Identify the report ID, and check whether the “Visible For” or “Role Access” field lists the user’s role.
If not available, edit the report’s setup and add the necessary roles or departments for visibility.
Step 4. Audit Change History
To identify recent modifications that may have revoked permissions:
Go to ERP Admin → Permission Management → Change History.
View timestamped updates to module access or removed privileges; restore required settings if changes were accidental.
Step 5. Reset Permissions (If Corrupted)
If roles or permissions have become inconsistent:
Use the “Reset to basic” option under Permission Management.
Then reapply organization-wide permissions using predefined templates, ensuring reports are re-linked to module-access tables.
