All Posts

In the iScala ecosystem, Crystal Reports remain a critical part of daily operations. They drive invoices, delivery notes, financial documents, production paperwork, and countless customer‑facing outputs. Yet anyone who has ever attempted to modify one of these reports—especially adding new fields—knows the process is anything but straightforward. What seems like a simple request (“Can you add this field to the report?”) often turns into a technical obstacle course. And for ma

Upgrading Epicor iScala is far more complex than applying a patch. Modern versions introduce new Java, Tomcat, SQL Server, and security requirements that often clash with older, heavily customized Australian installations. One wrong version choice can break the Application Server, integrations, or financial reporting. Most iScala environments also carry years of custom scripts, bespoke reports, and legacy data structures. These rarely migrate cleanly and must be rebuilt, reva

Key Challenges 1. Structural Mismatch Each ERP has unique tables, naming conventions, and mandatory fields. Without expert mapping, imports fail or produce inconsistent data. Lonze Com ensures schema alignment and clean validation. 2. Master‑Data Inconsistency Different systems often hold duplicate or conflicting customer, supplier, and item records. We standardize and cleanse master data before migration. 3. Transactional Alignment Fiscal calendars, posting rules, and curren