Sales order
Quantity, price and delivery date are entered; demand flows to planning.
SAL · CMP · TRG
Manufacturing · Logistics · Finance · TROIA
CANIAS ERPConsulting and Development
Integrated enterprise process management from manufacturing to finance.
CANIAS ERP is an enterprise ERP platform with deep manufacturing, logistics and finance coverage, shipping with its own database (iasDB) and its own object-oriented development environment (TROIA). Its distinguishing feature is that processes the standard does not cover can be solved inside the product’s own development environment while preserving the integrity of the standard source.
- Manufacturing & MRP
- TROIA
- caniasIQ
- iasDB
- e-Transformation
- 70 modules
Order to production in CANIAS
From order to production. One data flow.
When the order changes, planning, stock and cost move together. Hover a step to see which CANIAS modules run.
MRP
Material needs and lead times are calculated from BOM, stock and open orders.
MRP · DMF · BOMPurchasing
Requests and orders for missing material; import process for foreign purchases.
PUR · IMPRaw material
Goods receipt, lot and bin; the purchase invoice is verified.
INV · WMS · VERWork order
The production order opens against routing and capacity and is loaded to work centres.
PRD · ROU · CAPProduction
Actual consumption and time from the floor; production intelligence and automation.
PRD · PRI · AUTQuality
Inspection plans, checks and non-conformance records.
QLTFinished goods
Finished goods enter stock; actual production cost is calculated.
INV · PRC · INCShipping
Packing, shipping and export documents.
PAC · SHM · EXPInvoice
Sales invoice; e-invoice, e-archive and e-waybill.
SAL · EIN · EAM · EDNFinance
Ledger entry, standard vs actual cost variance and financial reporting.
FIN · CAL · COS · FRM
70 official modules · 9 business areas
CANIAS ERP module map
The headings in the vendor’s official module list, with their own group codes. Not all of them are deployed on a project; scope is set by fit-gap.
9 modules
Manufacturing
Master data, BOM, routing, production orders, costing and automation in one model.
Module group details →- BASBase Data ManagementCMN
- BOMBill of Materials ManagementCMN
- ROURouting ManagementCMN
- PRDProduction ManagementPRM
- PRCProduction Cost ManagementPRM
- PRIProduction IntelligencePRM
- AUTAutomationPRM
- ACTActivity ManagementPRM
- PRJProject ManagementPRM
6 modules
Planning
Demand forecasting, MRP and capacity with budget, scorecard and risk.
Module group details →- MRPMaterial Requirements PlanningMAP
- DMFDemand ForecastingMAP
- CAPCapacity ManagementPRM
- BUDBudget ManagementSTP
- BSCBalanced Scorecard ManagementSTP
- ERMEnterprise Risk ManagementSTP
10 modules
Logistics
Stock, warehouse, transfers, purchasing, invoice verification, import and shipping on one document chain.
Module group details →- INVInventory ManagementINM
- WMSWarehouse ManagementINM
- TROTransfer ManagementINM
- INCInventory Cost ManagementINM
- PURPurchase ManagementPUM
- VERInvoice VerificationPUM
- SHMShipment ManagementPUM
- IMPImport ManagementPUM
- PACPackaging ManagementSAM
- ESMEnterprise Sustainability ManagementPUM
10 modules
Sales & CRM
Sales, export, campaigns, commissions and targets; customer relations, opportunities, requests and surveys.
Module group details →- SALSales ManagementSAM
- EXPExport ManagementSAM
- CMPCampaign ManagementSAM
- CMMCommission ManagementSAM
- TRGSales TargetsSAM
- RTMRetail ManagementSAM
- CRMCustomer Relationship ManagementCUM
- OPMOpportunity ManagementCUM
- ISMIssue ManagementCUM
- SVMSurvey ManagementCUM
14 modules
Finance
General ledger, finance, consolidation, fixed assets, costing and e-transformation.
Module group details →- FINFinancial AccountingFIM
- FMTFinancial ManagementFIM
- FRMFinancial Report ManagementFIM
- FCMFinancial Consolidation ManagementFIM
- ASTAsset ManagementFIM
- LRMLegal Reporting ManagementFIM
- CALStandard Cost ManagementCSM
- COSCost Center AccountingCSM
- EINE-InvoiceETR
- EAME-ArchiveETR
- EDNE-Delivery NoteETR
- EBMElectronic Book ManagementETR
- EARElectronic Account ReconciliationETR
- EPRE-Producer ReceiptETR
- HCMPersonnel ManagementHRM
- CRRCareer ManagementHRM
- TRNTraining ManagementHRM
- TRVTravel ManagementHRM
- SSMSelf Service ManagementHRM
3 modules
Quality & Maintenance
Quality, service and maintenance on the same records as production and logistics.
Module group details →- QLTQuality ManagementLOG
- SRVService ManagementLOG
- MNTMaintenance ManagementPRM
1 modules
BI
caniasIQ: sales summary by industry, city, vendor and product; operational data becomes management indicators.
Module group details →12 modules
Platform
TROIA development tools, workflows, web services, EDI, documents and system management.
Module group details →- DEVDevelopment ToolsENV
- BPMBusiness Process ManagementENV
- WSRWeb ServicesENV
- EDIElectronic Data InterchangeENV
- DOCDocument ManagementENV
- KMSKnowledge ManagementENV
- MAMMail Application ManagementENV
- SMSSMS ManagementENV
- CLBCollaboratorENV
- SYSSystem AdministrationENV
- MMSMessage Management SystemETR
- GDPGeneral Data ProtectionETR
The module names and codes in this section are taken from the vendor’s official module list. Licence scope, version policy and product roadmap are the vendor’s responsibility; we recommend verifying current scope in the vendor’s documentation.
01 OBJECT: SALES ORDER · BEFORE SAVE
02 CHECK CREDIT LIMIT
03 IF LIMIT IS EXCEEDED
04 START APPROVAL FLOW (REGION → FINANCE)
05 HOLD THE RECORD
06 ELSE
07 VALIDATE DELIVERY DATE WITH MRP
08 COMPLETE RECORD · WRITE AUDIT TRAIL✓ Compiled in the customer layer · standard class untouched
TROIA
What do we develop on CANIAS?
TROIA is CANIAS’s own object-oriented development environment, with its own IDE, compiler and interpreter. The code we write lives inside the application; we do not build a side system that bypasses the ERP.
- Screens
- Fields
- Validation
- Business rules
- Workflow
- Reports
- Web service
- API
- Automation
- Integration
- 01
Custom screen development
Screens and forms in the ERP’s own interface layer for processes with no standard equivalent.
- 02
Business rules and validation
Consistency, limit and mandatory-field rules that run when a record is opened and saved.
- 03
Approval flows
Multi-level approval and hold mechanisms tied to amount, line item or risk threshold.
- 04
Custom reports
Breakdowns the standard report does not cover; outputs exposed to a data warehouse or BI layer.
- 05
Web services and APIs
Secure, traceable connection of external systems to the ERP and the definition of service contracts.
- 06
Batch operations and automation
Scheduled jobs, bulk record generation, data correction and file-driven processing flows.
- 07
Existing customisation analysis
An inventory of developments accumulated over the years: which are still in use, which are dead code?
- 08
Performance improvement
Slow screens, reports and batch jobs addressed at the query and data-access layer.
- 09
Version compatibility work
Assessing before an upgrade whether each customisation conflicts with changed standard behaviour.
Writing customisations without breaking the upgrade
In CANIAS a customisation can be written without modifying the standard object directly: a customer-owned class takes the place of the standard class. The discipline is this — when standard behaviour needs to change, it is handled in the customer layer rather than by editing the standard source. There is a price for this and we say it upfront: every customisation is customisation debt, and that debt is paid at upgrade time. So we do not turn every request into development; where the standard offers an acceptable route, we recommend that first.
Sustainable investment
Version upgrades and performance
- 01
Customisation inventory
Before an upgrade we establish which developments are still used and which are dead code. Customisations that will not be carried forward make the upgrade cheaper.
- 02
Conflict assessment
Code in the customer layer is not deleted outright by an upgrade, but it can conflict with changed standard behaviour. Every item is assessed individually.
- 03
Test coverage
Which flows enter regression testing after an upgrade is derived from the customisation inventory.
- 04
Performance
Slow screens and reports are addressed through data access, indexing and batch design; adding hardware is not the first answer.
FAB Technology
CANIAS is a deep product. FAB fits it to your business.
Let’s establish your current version, the modules genuinely in use and the customisations that have accumulated — then decide on upgrade or improvement.
Current-state analysis
Version, the modules genuinely in use and the existing customisation inventory.
Fit-gap
Listing separately where processes fit the standard and where they do not.
Module implementation
Deployment, master data design, opening balances and authorisation.
TROIA development
Screens, reports, business rules, approval flows and automation.
Integration
Connections to banking, e-documents, POS, e-commerce, B2B, WMS and production systems.
Data migration
Separate migration and verification plans for master data, open transactions and history.
Version upgrades
Customisation inventory, conflict assessment and regression test coverage.
Maintenance and support
Regular support, performance monitoring and keeping the customisation inventory current.
Where we step into CANIAS projects
Our work runs on your installation: we solve the processes the standard does not cover using the platform's own methods, and we do it without breaking version upgrades. Licensing, release policy and the product roadmap remain the vendor's responsibility.
The module map and the TROIA development scope are set out above. For the layer architecture, database structure and comparative evaluation criteria, see what is CANIAS ERP.
What we take on in your CANIAS installation
Module implementation and go-live
We map your processes onto what the standard covers and list what it does not in a fit-gap register. Module go-live, master data design, opening balances and data migration are planned from that register. Which process is solved by configuration and which by development is stated separately in the scope document.
Development and customisation with TROIA
TROIA is CANIAS's own development platform, with its own IDE, compiler and interpreter. We write screen, report, workflow and process customisations on that platform. The code lives inside the application; we do not stand up a side system that bypasses the ERP.
Integration
We build the links to banks, e-invoicing, POS, e-commerce, B2B, WMS, production systems and third-party services. Our baseline is that a retried request must not create a duplicate record and that every flow must be observable; the detail is on the API and system integration page.
Version upgrades and maintenance
Upgrading an existing installation, reviewing accumulated customisations and ongoing support. Before an upgrade we establish which customisations are still in use and which are dead code; a customisation that does not have to be carried forward makes the upgrade cheaper.
Writing customisation without breaking the upgrade
CANIAS provides a structure that lets a customisation be written without editing the standard object directly: a customer-owned class takes the place of the standard class. The discipline is this — when standard behaviour must change, it is handled in the customer layer rather than by editing the standard source.
There is a price, and we say it up front: every customisation is customisation debt. The upgrade is where that debt is settled. So we do not turn every request into development; if the standard offers an acceptable route, we propose that first.
How a CANIAS project runs
- Current-state analysis. Which release the installation is on, which modules are genuinely used, and an inventory of existing customisations.
- Fit-gap. The processes the standard covers and those it does not are listed separately.
- Scope and method. For each gap — configuration, TROIA development or integration — decided in writing.
- Development and testing. Customisations are written in a test environment; the acceptance criteria are the items in the scope document.
- Go-live. Data migration, parallel running and a user training plan.
- Maintenance. An upgrade calendar and keeping the customisation inventory current.
What this page does not claim
We publish no unmeasured success rate, average project duration or customer count. CANIAS module coverage and licence rights depend on your own contract; nothing on this page replaces the vendor's licence terms. We recommend verifying the product's current capabilities in the vendor's own documentation.
Frequently asked questions
Are you a CANIAS partner?
No. We hold no formal partnership on the CANIAS side; we provide independent consulting. Your counterpart for licensing and product support is the vendor.
We already run CANIAS — can you work without starting over?
Yes; a substantial part of our work is on installations that are already live. We start by taking an inventory of the existing customisations.
Who owns the TROIA development?
The code we write stays in your installation and its source is yours. The scope document records the rationale for each customisation and the standard object it affects; if you continue with another team, the handover runs through that document.
Will our customisations be lost in a version upgrade?
If a customisation was written in the customer layer, an upgrade does not delete it outright — but it can conflict with changed standard behaviour. That is why a customisation inventory is produced before the upgrade and each item is assessed individually.
Let’s review your CANIAS installation together
Let’s establish your current version, the modules genuinely in use and the customisations that have accumulated — then decide on upgrade or improvement.