Send leads to SAP
A chat lead becomes a business partner, in S/4HANA or in Business One.
SAP is one connection covering two products that share a name and almost nothing else. Pick which one you run and the rest of the form changes with the answer.
Both run on your own server. There is no SAP host to default to, which is why the address is a field, and why what is on your network decides whether the call arrives at all.
What you need
- The server address, over https. A credential is not sent over plain http, and the connect form refuses one that is.
- A user that may create business partners, and its password.
- For Business One, the company database -- the same one you pick when signing into the client.
For S/4HANA, the API_BUSINESS_PARTNER service has to be exposed on your gateway. If it is not, the connection fails at the first call rather than at the first lead, which is the better place for it to fail.
Connect and route
- In Destinations, connect SAP and choose the product.
- Paste the address and the user. We verify by doing the handshake that product needs: for S/4HANA a CSRF fetch, for Business One a login. Either one proves the address, the user and the authorisation at once.
- Create a route -- which leads it takes.
- Map the fields. Name, email, phone and the address parts.
Where an email actually goes
In S/4HANA an email address is not a field on a business partner. An address hangs under the partner, and the email hangs under the address. A create that carries one is a deep insert three levels down.
You map Email. The nesting is assembled for you, because asking somebody to map to_BusinessPartnerAddress/to_EmailAddress/EmailAddress is asking them to know our problem. The same goes for the phone number, the city and the postcode: flat fields in the mapper, nested correctly on the way out.
Business One keeps an email on the partner itself, so there is nothing to assemble.
Person or organisation
S/4HANA's business partner is one object with a category: 1 is a person, 2 an organisation. A lead that gave a company name and no surname is created as an organisation; anything else is a person. The roles a partner plays -- customer, supplier -- are yours to set in SAP.
In Business One a chat lead is created as a lead, which is what cLid means there, rather than as a customer. Converting it is a decision somebody in your team makes, not one a chat makes.
What gets sent
A curated set of fields rather than everything the service exposes: API_BUSINESS_PARTNER has hundreds of them, and a mapper is not a schema browser.
A partner needs a last name (or an organisation name). One is filled in from what the lead carries when the mapping leaves it out.
Common errors
A 403 on the first call usually means the user may reach the service but is not authorised for business partners. The credential verified; the authorisation is a separate question and SAP answers it separately.
CSRF token validation failed means the token and the session it was issued with did not travel together. The connector fetches both and sends both, so this one points at something between us and your gateway rewriting or dropping cookies.
What it does not do
It creates. It does not update an existing partner and it does not check for one. It does not create sales orders, quotations or anything else -- a business partner is what a lead is.
This has not been measured against a live system. Both products run on customer hardware, so there was no host to test against. It is written against SAP's own documentation of the two APIs, and the first connection is the first measurement. If something does not match what your system does, tell us and we will fix it against yours.