SAP runs the core.
Everything around it runs on Excel.
Clean core means your custom requirements have to live somewhere. Today that's Excel, Access and Z-tables. dForge is a governed application layer next to SAP — never a replacement: data model, roles, workflows, reports and audit from one definition, on PostgreSQL, in your own environment.
Show as presentation→The ring of spreadsheets around the core.
SAP handles the core processes well. It's everything around them — the approvals, requests and exceptions — that ends up in places nobody governs.
Next to SAP, not instead of it.
SAP keeps the core. dForge takes the side processes that never belonged there — and gives them the governance a spreadsheet never had.
Keep the core clean
Custom requirements move out of Z-tables and core modifications into a separate application layer. SAP stays standard, and your upgrades stop depending on custom code.
- Custom logic lives beside SAP, not inside it.
- Fewer Z-tables and modifications to carry through every upgrade.
- A clearer answer for the S/4HANA Z-code decision.
Replace the spreadsheet ring
The Excel and Access tools around SAP become governed applications: a real data model, roles, workflows, reports and an audit trail — all from one definition, not a pile of files.
- Data model, roles, workflows, reports and audit from one definition.
- Approvals and hand-offs replace files emailed between teams.
- A side application in weeks — not a quarter.
Your perimeter, your database
One PostgreSQL database per customer, row- and column-level security, a full audit trail, and self-hosting in your own environment. Your data doesn't leave the perimeter you control.
- One PostgreSQL database per customer.
- Row- and column-level security, full audit trail.
- Self-host in your own environment.
Core mods & Excel vs. a governed layer.
One side process first. Then the next.
No platform program and no change to the core. Pick the process that hurts most, run it beside SAP, and expand from there.
Inventory the ring
List the spreadsheets, Access tools and Z-tables around SAP — who uses them, what they feed, what breaks when they're wrong. Pick the one that hurts most.
Model it and connect it
We model the process as a dForge module. Your SAP integrator connects SAP to our JSON-RPC API and webhooks, using the standard SAP interfaces you already run.
Run beside SAP, then expand
The first process goes live next to SAP with roles and audit in place. Then the next one — on the same model, the same database, the same security.
The side processes teams build first.
Requests from stores and branches — fixtures, stock, maintenance — routed, approved and tracked.
Promotion proposals and price changes with approval steps before they reach SAP.
Customer returns and supplier claims with status, owners, documents and a full history.
Collect, check and approve supplier data internally before the vendor record is created in SAP.
Delays, damages and short deliveries logged, assigned and resolved — not lost in email.
Whatever lives in a spreadsheet next to SAP today — modeled as a governed application.
These are examples of what you build on dForge — not packaged modules. Each one is modeled around how your teams actually work.
Modules worth installing first for this.
Warehouse management: procurement requests, PO workflow, stock operations, inventory tracking. Vendor identity lives in the shared parties module; WMS-specific columns (supplier code, payment terms) are layered as an extension.
Product pricing, price lists, discount rules, and cost tracking (WAC)
Accounts receivable, accounts payable, invoicing, and payments
Sales CRM: contacts, leads, opportunities, quotes, activities, and product catalog. Customer identity lives in the shared parties module; CRM-specific columns (industry, credit limit, account manager) are layered on as an extension.
Opens these modules, and the integrations that connect them, on one review page in your dForge workspace. Remove what you don't need; nothing installs until you confirm.
Tell us what you need and we'll build the module — or book a call to map your systems together.
See who else builds on dForge.
Monday, Zoho or HubSpot stopped fitting
Aging Access, FoxPro or custom ERP
Founders & domain-specific micro-SaaS
CIOs under pressure to deliver more, faster
Simplify operations on one governed model
Run ops behind Shopify or WooCommerce
Small companies with no developer on staff
Department managers waiting on central IT
Consultancies & systems integrators
Analysts who design the model
SAP, S/4HANA, SAP BTP and ECC are trademarks or registered trademarks of SAP SE. dForge is not affiliated with, endorsed by or certified by SAP SE.