A Salesforce rep promises a delivery date they cannot see. The price on the quote is not the price SAP will use. A credit hold in SAP is invisible in Salesforce until the customer calls. And when the deal is won, someone re-keys the order into SAP and a typo becomes a returned shipment.

The root cause is not the two systems, it is that each is right about something the other needs: Salesforce knows the customer conversation, SAP knows the price list, the stock, the credit position and the invoice. Integration is the work of letting each see the other's facts at the moment they matter.

What ECOSIRE builds

A custom integration between Salesforce and the SAP system you run: S/4HANA (cloud or on premise) or SAP Business One. The pattern depends on the system. On the SAP side we use its published APIs: OData services for S/4HANA, the Service Layer for Business One. On the Salesforce side we use Apex callouts with Named Credentials, and Platform Events or Change Data Capture to react to changes without polling. Where you already run an integration platform, we build on it instead of beside it.

Accounts and business partners, with one owner per field

Salesforce Accounts and SAP business partners are matched on a key we agree (never a name alone) and linked by a stored identifier on each side. Before anything syncs we decide which system owns which field: SAP usually owns payment terms, credit limit, tax data and the account number; Salesforce usually owns the relationship and the contacts. Conflicts follow that rule instead of last-writer-wins.

From opportunity to sales order

A closed-won opportunity, or a quote at the stage you choose, creates a sales order in SAP with the mapped customer, materials, quantities, plant or warehouse, requested date and your reference. The rep sees the SAP order number on the opportunity. Validation errors from SAP (a blocked material, an incomplete address, a credit block) return to the opportunity as readable messages, not as a silent failure.

Pricing and availability on the quote

Where the process needs it, a quote line requests the price, discount conditions and availability from SAP, so the number on the quote is the number SAP will invoice. Which calls happen on the quote and which wait for the order is a scoping decision, because each call adds latency to the rep's screen.

Delivery, invoice and payment status back to Salesforce

Order status, delivery and shipment details, invoice numbers, amounts and open balances flow back to the opportunity, the account or a custom object. Account owners see overdue balances and credit holds, and Salesforce flows can act on them: a task for the owner, a hold on a new quote.

Product and price master

Materials or items are synchronised into Salesforce Products with the price lists you choose, so reps quote from a catalogue that matches SAP.

Operations you can supervise

Every message in either direction is logged with status, payload reference and error detail in a custom object, with replay for failures and alerts to an administrator. Retries are idempotent, so a retry never creates a second sales order.

Who this is for

Companies that sell through Salesforce and fulfil and invoice from SAP, and want reps and account owners to see SAP's facts without a phone call to the back office. If your SAP system is Business One, our separate Salesforce CRM sync listing for SAP Business One covers that product's specifics.

How delivery works

1. Scoping workshop. We map your sales process, SAP system and release, master data ownership, pricing procedure and volumes. 2. Written quote. The scope, exclusions, assumptions, non-functional requirements and delivery date are agreed in writing first. 3. Build in non-production. We build against a Salesforce sandbox and an SAP test client or company database with copies of your real master data shapes. 4. Integration test and acceptance. End-to-end scenarios, including errors and replays, are run with your users and signed off. 5. Cutover and support window. Production is switched on in the sequence we agree, and we stay through your first month-end.

What this is not

This is not a pre-built package, and it does not replace SAP's or Salesforce's own integration products where you already run them. It is written for your Salesforce org and your SAP system after a scoping workshop, against a written quote that states scope, exclusions, assumptions and the delivery date. It does not modify standard SAP objects, and custom ABAP development or Salesforce customisation beyond the objects and flows named in the quote is out of scope unless the quote says so.