We successfully implemented automated BOM synchronization between SolidWorks and our SAP ERP system using Aras 14.0. Previously, engineers manually exported BOM data from CAD assemblies and our ERP team re-entered it into SAP, causing frequent errors and 3-5 day delays.
Our solution leverages the CAD Connector with custom field mapping to automatically push BOM changes to Aras, then a scheduled job validates and synchronizes to SAP via REST API. The field mapping handles part numbers, quantities, materials, and procurement data. Validation rules check for duplicate entries, missing required fields, and material code mismatches before sync.
Since deployment, we’ve eliminated 95% of manual BOM entries and reduced our change cycle from 5 days to under 8 hours. The automated validation catches data issues before they reach ERP, preventing downstream production delays.
Excellent implementation that addresses all three critical aspects of CAD-ERP BOM synchronization. Let me break down the key success factors:
Field Mapping Architecture: The CAD_ERP_Material_Map custom ItemType provides a maintainable translation layer that decouples CAD properties from ERP master data. This approach allows material mappings to evolve without code changes. The UI for engineers to request new mappings is crucial - it keeps the system current while maintaining data governance. Consider adding approval workflow for new material mappings to ensure procurement team validation.
Automated Sync Job Design: The state-based sync eligibility (Released/In Production only) combined with hash-based change detection is the right pattern. Running every 2 hours during business hours balances timeliness with system load. The version comparison prevents unnecessary ERP updates, which is important for audit trails. One enhancement to consider: implement a priority queue where critical BOMs (expedited orders) can trigger immediate sync rather than waiting for the next scheduled job.
Validation Framework: Your multi-layer validation (format, existence, relationships) prevents the most common data quality issues. The sync history table for rollback capability demonstrates mature operational thinking. The daily reconciliation report is essential - it provides the safety net that catches edge cases your validation rules might miss.
Performance metrics are impressive: 95% reduction in manual entries and 5 days to 8 hours cycle time represents significant ROI. For organizations implementing similar solutions, I’d add these recommendations:
- Incremental Rollout: Start with a single product line or BOM type, validate the mapping and validation rules, then expand
- Error Classification: Categorize validation failures (critical vs warning) to avoid blocking legitimate changes for minor issues
- Analytics Dashboard: Track sync success rates, validation failure patterns, and processing times to identify optimization opportunities
- Change Impact Analysis: Before syncing BOM changes, calculate downstream impact (affected orders, inventory requirements) and include in approval workflow
The combination of CAD Connector, custom mapping tables, scheduled validation jobs, and REST API integration to SAP provides a robust, maintainable solution. The key architectural decision - making sync eligibility dependent on lifecycle state - ensures data integrity while maintaining engineering flexibility. This pattern is applicable to other CAD-ERP integration scenarios beyond BOM synchronization.
The material mapping was our biggest challenge. We created a custom ItemType called CAD_ERP_Material_Map that stores the translation table. Each record maps CAD material properties to SAP material codes with validation rules. Our sync job queries this mapping table before pushing to ERP, and flags unmapped materials for manual review. We also built a simple UI for engineers to request new material mappings when they use materials not yet in the system.
We run sync jobs every 2 hours during business hours and hourly overnight. The job checks the BOM’s lifecycle state before syncing - only Released or In Production BOMs are eligible. If a BOM is in Edit mode, it’s skipped until the next cycle. We don’t lock BOMs during sync; instead, we use version comparison. The job stores a hash of the last synced BOM state, and only pushes changes if the hash differs. This prevents redundant updates and handles the case where ERP data might be manually corrected. Conflicts are rare because Released BOMs require change orders to modify, which temporarily moves them out of sync scope.
What validation rules did you implement? We’re concerned about data quality issues propagating from CAD to ERP. Also, do you have rollback capabilities if bad data makes it through?