I’m looking for advice on connecting our SAP ECC system to a cloud-based BOM management tool without breaking the bank. Our company has under 100 employees and we need to sync material data and bill of materials between systems.
The main functions we need are:
Push BOM and material info to SAP with change tracking
Pull material costs and vendor data from SAP
Handle complex multi-level BOMs with thousands of components
Right now we manage this through spreadsheets which becomes unmanageable with large BOMs containing tons of metadata. We’re also planning to move from ECC to S/4HANA on-premise soon, so any solution needs to work with both versions.
I’ve looked into integration platforms but the SAP connector pricing seems excessive for our size. Direct RFC development might be cheaper but requires more technical resources, especially for handling nested BOM structures.
What approaches would you recommend for a small company budget? Looking for something that balances cost, implementation time, and ongoing maintenance without getting locked into expensive subscription models.
Any specific guidance on SAP APIs or methods for BOM read/write operations would be really helpful since I’m coming at this from the business user side rather than deep SAP technical knowledge.
We dealt with something similar two years back - had to connect SAP ECC with our cloud inventory system. Ended up using SAP Cloud Platform Integration and it was cheaper than we thought. The trick was negotiating based on transaction volume instead of user count since we only had automated flows running. For BOMs specifically, CS_BOM_EXPL_MAT_V2 worked great for reading multi-level structures, and BAPI_MATERIAL_SAVEDATA handled material master updates without issues. RFC works but gets messy fast when you’re dealing with BOM explosions and version control. About your S/4HANA migration - wait until after you transition before setting up any integration. We made that mistake on another project and had to rework huge chunks of our integration logic because the API behaviors changed enough between ECC and S/4HANA. S/4HANA’s REST APIs are way easier to work with than the old RFC methods anyway.
skip the fancy integration platforms for a small biz. we built a simple middleware service with python + pyrfc lib that handles all our SAP connectivity. way cheaper than commercial solutions and works great for BOM ops. you’ll need someone who can code, but sounds like you’re already considering that. ours has been runnin 3 years without major issues.
Check if you’ve got SAP’s PI/PO system already included in your license package. Lots of smaller companies skip this thinking it’s too complicated, but it’s actually perfect for basic BOM sync and you won’t pay extra connector fees. We did this at a 90-person manufacturing company and completely avoided third-party platform costs. The real win is the built-in error handling and monitoring. When you’re dealing with thousands of components, you need solid retry logic and transaction rollbacks - stuff that custom RFC solutions usually screw up. PI/PO handles this automatically. For what you’re doing, use IDOC processing instead of direct RFC calls. MATMAS and BOMMAT IDOCs work great for material and BOM data flows, and the format doesn’t change between ECC and S/4HANA. Way less migration pain down the road. No PI/PO? Try SAP’s Integration Suite. They’ve got startup-friendly pricing that scales with transactions, not users. Much better deal for companies your size than the usual enterprise licensing nightmare.
Had the same issue at my old company before we hit 150 employees. Skip the expensive SAP connectors - we used SAP’s web services with a basic message queue instead. Here’s the trick: use SAP’s standard web services for material stuff rather than jumping into RFC hell. SOAP services like MaterialByElements and BillOfMaterialByMaterial cover most cases without custom dev work. We built a small service that grabbed data from these web services, flattened the BOM hierarchy, then pushed everything to our cloud system. Your S/4HANA migration worry? This approach saved us because the web service interfaces stayed the same. We just updated auth methods and endpoint URLs. Took six weeks with one part-time developer. Maintenance is practically zero since we’re using SAP’s supported interfaces instead of custom RFC calls that break every update. Cost was about 8k for development vs 40k yearly for enterprise integration platforms.
Been through this exact scenario with multiple companies. SAP connector licensing from traditional platforms is brutal for smaller teams.
What worked best: building direct RFC connections through an integration platform that doesn’t charge premium SAP fees. You handle all those BOM functions without the enterprise markup.
For your specific needs:
BAPI_MATBOM_CREATE_MULTIPLE for pushing complex BOMs
CS_BOM_EXPL_MAT_V2 like Nova mentioned for reading structures
BAPI_MATERIAL_GET_ALL for pulling cost data
Nested BOM handling is tricky but totally doable with the right platform processing RFC calls. You avoid the spreadsheet nightmare and get real change tracking.
On S/4HANA migration timing - I disagree with waiting. Build it now with RFC calls that work on both systems. The transition becomes smoother when your integration already handles the data flows.
Companies your size need enterprise SAP connectivity without enterprise pricing. The platform handles RFC complexity while you focus on business logic.
This cuts implementation time to weeks instead of months and keeps costs reasonable. Plus you own the integration logic for when you migrate to S/4HANA.
I’ve done this with three different companies - here’s what actually works without burning cash.
Build a lightweight middleware layer between your systems. Node.js with SAP connector libraries works great and costs way less than those enterprise platforms charging per transaction.
For BOM operations, focus on these RFCs:
RFC_READ_TABLE for material master data pulls
CSAP_MAT_BOM_READ for reading existing BOMs
CSAP_MAT_BOM_MAINTAIN for BOM updates
With multi-level BOMs, handle recursion properly. Cache material relationships and build your hierarchy in memory instead of making multiple SAP calls. Saves time and reduces load on ECC.
For S/4HANA migration - build with OData services in mind. ECC supports them through Gateway, S/4HANA has them natively. Smoother transition than pure RFC calls.
Nobody mentioned handling metadata complexity. Create a mapping layer that transforms your BOM structure into something your cloud tool understands. Don’t cram SAP-specific data into systems that weren’t designed for it.
We built something similar for an 80-person manufacturing company - total dev cost under 15k. Compare that to enterprise platform licensing and you’re looking at major savings over two years.
