Real Opportunity data in SAP. Honest about what's still missing.
fieldbrain writes to SAP Business ByDesign / S/4HANA, using a stable system code instead of a guessed sales phase.
The technical precision
fieldbrain uses LifeCycleStatusCode for status: a small, fixed system code, not a customer-relabeled picklist. An earlier version wrote fieldbrain's internal stage name directly into a field never meant for it; that was removed, not patched over silently.
What actually syncs
What stays unchanged: fieldbrain only ever writes the fields from the table above. Other objects, your own automations, layouts, or reports in your CRM stay untouched. Nothing gets deleted, renamed, or restructured, only added to.
A day with SAP
After a customer visit, a rep records the key points. fieldbrain updates the matching opportunity in SAP Business ByDesign or S/4HANA with the correct LifeCycleStatusCode and adds context as a note. For a team using SAP as its forecast source of truth, the status stays current, even while the Business Partner link is still handled manually today.
Does fieldbrain automatically link the opportunity to our business partner?
Not yet, that's an openly documented gap. This relationship can't be safely replicated in ByDesign without a live sandbox, better honestly open than a faulty write.
What happens if SAP has a brief outage?
fieldbrain automatically retries the write with increasing wait time. A temporary error on SAP's side doesn't result in a lost update.
Security & Permissions
Your connection belongs exclusively to your account. No other user, not even on the same team, can access it.
Sync is part of the Professional plan and above. Without an active plan it stays inactive, nothing runs in the background.
Disconnect it and sync stops immediately. Data already transferred stays where it is, nothing is retroactively deleted.