SourceLace Docs
FAQOpen the app

SAP ECC (on-premise)

How to connect an SAP ECC system in your own data centre: SourceLace reads (and, if you allow it, creates or updates) data through your SAP Gateway OData services, as each person's own SAP user, through a small SourceLace Agent that runs inside your network, or, if your network allows no new outbound connection, through your own SAP BTP and Cloud Connector (Connect through SAP BTP). No SAP passwords are stored anywhere and no inbound firewall rule is needed.

Status: Pilot. New or partial, offered to pilot customers. Built on SAP's documented behaviour for SAP Gateway OData (version 2), client certificates and certificate-to-user mapping. Tell support@sourcelace.com before you start, so we can help with the first connection.

At a glance

Connects through Sign-in Network Status First test question
SAP ECC through the SourceLace Agent SAP Gateway OData (V2) services Personal sign-in (each person's own SAP user, no sign-in page) The agent connects out to SourceLace on port 443; no inbound rule Pilot Your IT department runs sourcelace-agent check --config <configuration file> --user <email>. Then: "Which entity sets does ecc:prod offer?"
SAP ECC through SAP BTP SAP Gateway OData (V2) services, published in your SAP BTP subaccount Personal sign-in (each person's own BTP login) Your existing SAP BTP and Cloud Connector; nothing new in your network Pilot "Which entity sets does ecc:prod offer?"

Add each source with the usual steps. The network answers are explained in What your network needs. If the first test question fails, the error message tells you what to fix: look it up under When something goes wrong below.

How it works

  1. Your IT department runs the SourceLace Agent, a small program (or Docker container), on a machine inside your network that can reach SAP over HTTPS.
  2. The agent opens one outbound connection to SourceLace over HTTPS (port 443) and keeps it open. SourceLace sends requests over it; nothing connects in to your network.
  3. For each request, the agent maps the asking person to an SAP user (by a rule you choose) and calls SAP Gateway with a client certificate for that user that it signs itself and that lasts a few minutes. Your SAP system trusts the agent's certificate authority and maps each certificate to its SAP user, so SAP applies that person's own authorizations. This is the same pattern as SAP Cloud Connector's principal propagation.
  4. The agent checks every request against its own allowlist first: only the Gateway services you list can be read, and only the entity sets you list under writes can be changed. Deletes, $batch and anything outside your Gateway paths are refused, whatever SourceLace asks.

SourceLace reaches ECC only through SAP Gateway OData services, never through RFC or BAPI calls. If you want SourceLace to use a BAPI's logic, expose it as a Gateway service (for example with transaction SEGW) and add that service to the agent.

The steps for your IT department and SAP Basis administrators are below, in What your admin does in SAP.

What your admin does in SAP (through the agent)

Your IT department and your SAP Basis administrators do this once per SAP system. Plan half a day, and tell support@sourcelace.com before you start: support sends the agent (a Docker image, or a Python package) and helps with the first connection.

Who:

  • IT department: someone who can run a program on a Linux machine or container host inside your network.
  • SAP Basis: an administrator who may use transactions STRUST, SMICM, RZ10, /IWFND/MAINT_SERVICE, SICF and CERTRULE (or SM30 for EXTID_DN), usually with the SAP_BC_BASIS_ADMIN role or your company's equivalent.
  • Security administrator: someone who may change roles in PFCG, to give people authorization for the Gateway services.
  • SourceLace admin: for the agent's token and the source.

Before you start, check:

  • SAP ECC 6.0 with SAP Gateway (SAP_GWFND, or IW_FND and GW_CORE on older releases), embedded or on a separate Gateway hub, and the OData services you want SourceLace to use.
  • An HTTPS port on SAP's ICM that the agent's machine can reach.
  • The agent's machine can make outbound HTTPS connections to SourceLace (directly or through a proxy that allows WebSocket connections). It needs little: 1 virtual CPU and 512 MB of memory are plenty.
  • Each person who will use SourceLace has their own SAP dialog user, unlocked, in the SAP client you will use.

Steps:

  1. Create the agent's token (SourceLace admin). See Create the agent's token below. Hand the token to the IT department through your password manager, never by email or chat. Note the agent's id (agt_...).

  2. Install the agent (IT department). Install it as support describes (Docker, or Python 3.11 or later with the systemd unit it comes with). Put the token in /etc/sourcelace-agent/token, readable only by the agent's user (chmod 600). If outbound traffic goes through a proxy, set HTTPS_PROXY for the agent.

  3. Make the agent's certificate authority (IT department). Run sourcelace-agent make-ca --out /etc/sourcelace-agent --name "SourceLace Agent CA Corvanta". It writes ca.key, the private key, which never leaves this machine (back it up encrypted; anyone with it could sign in to SAP as any mapped user), and ca.crt, the certificate, valid 5 years. Give ca.crt to your SAP Basis administrators, with the SHA-256 fingerprint the command prints.

  4. Write the agent's configuration (IT department, with SAP Basis). In the agent's configuration file (support sends an example), set SAP's HTTPS address and client (such as https://ecc.corvanta.com:44300 and 100), the Gateway path (/sap/opu/odata/sap), the services SourceLace may read, any entity sets it may change (writes), the certificate subject (such as O=Corvanta, C=US), and who is which SAP user (see Who is which SAP user). If SAP's own HTTPS certificate is from an internal certificate authority, export that CA from STRUST as a PEM file and set server_ca.

  5. Trust the agent's certificate authority in SAP (SAP Basis). Run STRUST, switch to change mode, open SSL server Standard (repeat for each application server's PSE if there are several), click Import certificate, choose ca.crt, then Add to Certificate List, and Save. Restart the ICM: SMICM → Administration → ICM → Exit Soft → Global. Check: CN=SourceLace Agent CA Corvanta is in the certificate list and the fingerprint matches.

  6. Let the ICM ask for client certificates (SAP Basis). In RZ10, check that icm/server_port_<n> has an HTTPS port (PROT=HTTPS,PORT=44300), that icm/HTTPS/verify_client is 1 (the default: not 0, and not 2, which would ask every browser for a certificate), and, if you use CERTRULE in step 8, that login/certificate_mapping_rulebased is 1. To see a parameter's current value, use RZ11. If an SAP Web Dispatcher or load balancer sits in front of SAP, either let the agent connect straight to the application server, or have the Web Dispatcher forward the agent's certificate:

    • on the Web Dispatcher, set icm/HTTPS/forward_client_certificate = TRUE;
    • on the application server, set icm/HTTPS/trust_client_with_issuer and icm/HTTPS/trust_client_with_subject to the issuer and subject of the Web Dispatcher's own client certificate, so SAP accepts the certificate it forwards.

    SAP's guide is "Using SSL with SAP Web Dispatcher". The ICM restart in step 5 can also be a system restart in a quiet period.

  7. Activate the Gateway services and give people access (SAP Basis and security). In /IWFND/MAINT_SERVICE, click Add Service, choose the system alias (usually LOCAL), find the service (such as ZSALES_ORDER_SRV) and Add Selected Services. Check its ICF node is active (green), or activate /sap/opu/odata/sap/<SERVICE> in SICF. Test it in /IWFND/GW_CLIENT with /sap/opu/odata/sap/<SERVICE>/$metadata. In PFCG, add the service to a role's menu (which proposes authorization object S_SERVICE), plus the usual data authorizations, and give the role to the people. On a separate Gateway hub, the hub must reach ECC through a trusted RFC connection (SM59, "Current User").

  8. Map certificates to SAP users (SAP Basis). On the agent's machine, the IT department makes a sample: sourcelace-agent sample-cert --config <configuration file> --user ana.lopez@corvanta.com --out sample.crt (it holds no key). Then either:

    • CERTRULE (recommended, one rule for everyone): run CERTRULE, switch to change mode, Upload Certificate sample.crt, click Rule, and set Certificate Attr. = Subject, Login As = ID, Certificate Entry = CN. Leave the other parts of the subject (O and C) and the issuer as they are in the rule, so only certificates from the agent's certificate authority with your O and C are mapped. Save. The status shows the sample maps to its SAP user (such as ALOPEZ). CERTRULE only exists on systems with a recent SAP_BASIS support package; if your system does not have the transaction, use EXTID_DN instead.
    • EXTID_DN (one row per person): in SM30, view VUSREXTID, External ID type DN, add CN=ALOPEZ, O=Corvanta, C=US with user ALOPEZ, Activated. For many people at once, use transaction EXTID_DN.

    Either way, a locked SAP user is refused.

  9. Check and start the agent (IT department). Run sourcelace-agent check --config <configuration file> --user ana.lopez@corvanta.com. It checks the configuration, SAP's HTTPS port and certificate, each service's $metadata as that person, and the connection to SourceLace. Then start it (systemctl enable --now sourcelace-agent, or the Docker container with --restart unless-stopped). Check: the agent logs Connected to SourceLace as agent Frankfurt DC., and On-premise agents in SourceLace shows it Online with its services.

  10. Add the source (SourceLace admin). See Add the source below.

When check fails: HTTP 401 means steps 5, 6 or 8 are unfinished (SAP does not trust the agent's CA, or cannot map the certificate to a user); HTTP 403 means the SAP user lacks an authorization such as S_SERVICE (step 7); HTTP 404 means the service is not activated (step 7); "could not reach SAP" means the address, port or SAP's certificate in step 4.

Check that it worked: one person whose SAP user is mapped clicks Connect on My connections: SourceLace shows their SAP user. Then they ask "Which entity sets does ecc:prd offer?".

SAP's own guides: SAP Help Portal (search for "SAP Gateway Foundation", "Rule-Based Certificate Mapping" and "Trust Manager").

Create the agent's token (SourceLace admin)

  1. On Connections, under On-premise agents, click Add an agent and give it a name, such as Frankfurt DC.
  2. SourceLace shows the agent's token (it starts with sla_) once. Copy it into the agent's token file, or give it to whoever installs the agent through your password manager. SourceLace keeps only a hash of it.
  3. Once the agent runs, the list shows it Online, with the time it was last seen and the services it offers. Revoke stops a token at once and disconnects the agent; make a new one to replace it.

Each organization can have up to 20 agents, for example one per SAP system.

Add the source (SourceLace admin)

On Connections → Add a source, choose SAP ECC (on-premise) (ecc).

Option Type Default Example What it is
agent Text (required) agt_0123456789ab The id of the on-premise agent, shown under On-premise agents.
connect_via Choice the agent Connect through: the SourceLace Agent, or your SAP BTP (below).
gateway_path Text /sap/opu/odata/sap /sap/opu/odata/sap Where your Gateway services live. The agent must list the same path.

Changes are off unless you turn them on. Name objects as SERVICE/EntitySet, such as ZSALES_ORDER_SRV/SalesOrderSet. A change is only possible when it is allowed in both places: here, and in the agent's own writes list. Records are created or updated one at a time; SourceLace never deletes records in SAP ECC.

Who is which SAP user

Each person reaches SAP as their own SAP user. The agent decides which one from the email they sign in to SourceLace with:

  1. SourceLace passes the person's email to the agent. SAP never sees the email.
  2. The agent's [users] settings turn the email into an SAP user name. With the rule email_local_part and your domain listed, ana.lopez@corvanta.com becomes ANA.LOPEZ. Entries in [users.table] handle exceptions, such as "ana.lopez@corvanta.com" = "ALOPEZ", and with the rule table only the people listed there are mapped.
  3. The agent calls SAP with a short-lived certificate for that SAP user, and SAP applies that user's own authorizations.

So the SAP user must already exist and be unlocked in the configured client, with authorization S_SERVICE for the Gateway services and the usual data authorizations. SourceLace needs no SAP password and no shared technical user. Your SAP Basis administrators map the agent's certificates to users once, with one CERTRULE rule for everyone, or one EXTID_DN row per person.

SAP user names are at most 12 characters. With the rule email_local_part, anyone whose email address before the @ is longer than that (or has other characters) must be listed in [users.table].

Never list a public mail domain such as gmail.com in the agent's domains. People who sign in with an address outside your domains go in [users.table] instead.

To test one person before everyone connects, your IT department runs sourcelace-agent check --config <configuration file> --user <their email> on the agent's machine. It shows the SAP user the email maps to and whether SAP accepts it.

Connect (each person)

Each person clicks Connect on My connections (or asks their AI app to connect). There is no sign-in page: SourceLace asks the agent which SAP user the person is, and shows it. People the agent cannot map are refused with "You have no SAP user in the SourceLace Agent's configuration".

Connect through SAP BTP instead of the agent

If your network allows no new outbound connection but you already run SAP BTP with SAP Cloud Connector, SourceLace can reach ECC through your BTP instead of the agent. Nothing new runs in your network: SourceLace calls an HTTPS address in your BTP subaccount with each person's own BTP sign-in, and BTP and Cloud Connector pass that person on to ECC (principal propagation), so ECC still applies their own SAP authorizations. Status: Pilot.

Your BTP administrators publish the Gateway services on an HTTPS address in BTP (SAP API Management, or an approuter) backed by a destination with principal propagation, and register SourceLace as an OAuth client with the redirect URL:

https://mcp.sourcelace.ai/connect/callback

What your admin does in SAP BTP

Your BTP administrators and SAP Basis administrators do this once. Tell support@sourcelace.com before you start.

Who:

  • Cloud Connector administrator: someone who can sign in to your Cloud Connector's administration page.
  • BTP administrators: a Subaccount Administrator of the subaccount (to add destinations, create the sign-in client and, for SAP API Management, an API proxy, with that service's own admin role).
  • SAP Basis: STRUST, RZ10 and CERTRULE in ECC, as in the agent steps.

Steps:

  1. Expose ECC's Gateway in Cloud Connector (Cloud Connector administrator). For the subaccount, open Cloud To On-Premise → Access Control → Add: back-end type ABAP System, protocol HTTPS, ECC's internal host and HTTPS port, a virtual host (such as ecc-virtual:443), principal type X.509 Certificate. Add a resource: URL path /sap/opu/odata/sap/ with Path and all sub-paths. Set up principal propagation (SAP's guide "Configure Principal Propagation"): trust the subaccount (Configuration → On Premise → Trust), create the CA certificate for principal propagation, and choose the subject pattern (such as CN=${name}). Check: the access control line shows Reachable.

  2. Let ECC trust Cloud Connector (SAP Basis). In STRUST (SSL server Standard), import Cloud Connector's system certificate and its principal propagation CA; in RZ10, let the ICM accept Cloud Connector as a trusted reverse proxy (icm/trusted_reverse_proxy_<n> naming Cloud Connector's certificate); and map the short-lived certificates to SAP users with CERTRULE (or EXTID_DN), as in step 8 of the agent steps.

  3. Add a destination (BTP administrators). In the subaccount, Connectivity → Destinations → New Destination: type HTTP, URL http://ecc-virtual:443 (the virtual host from step 1), proxy type OnPremise, authentication PrincipalPropagation, your Cloud Connector's Location ID if you use one, and the additional property sap-client with your SAP client (or set SAP client on the source instead). Save, then click Check Connection.

  4. Publish the services on an HTTPS address (BTP administrators). Use what you already run: an SAP API Management API proxy whose target is the destination, with a policy that checks the person's OAuth token; or a small approuter with a route to the destination that forwards the person's token. Note the address up to just before /sap/opu/odata/sap, such as https://corvanta.prod.apimanagement.eu10.hana.ondemand.com/ecc. It must be on *.ondemand.com or *.cloud.sap. If the address already ends at the Gateway root, SourceLace's Gateway path is /. Check: a GET of <address>/sap/opu/odata/sap/<SERVICE>/$metadata with a person's token returns the service's metadata, and SAP's trace (ST01) shows that person's SAP user, not a technical one.

  5. Register SourceLace as a sign-in client (BTP administrators). The client must allow the authorization code and refresh token grants, with the redirect URL above.

    • XSUAA: in the subaccount, Instances and Subscriptions → Create, service Authorization and Trust Management Service (xsuaa), plan application, with the parameters {"oauth2-configuration": {"redirect-uris": ["<the redirect URL above>"], "grant-types": ["authorization_code", "refresh_token"]}}. Then create a service key and open it: clientid is SourceLace's Client ID, clientsecret its Client secret, and url its BTP login service.
    • SAP Cloud Identity Services: add an application with OpenID Connect, add the redirect URL, and create a client secret. The BTP login service is your tenant, such as https://corvanta.accounts.ondemand.com.

    The API proxy or approuter from step 4 must accept tokens issued to this client.

Check that it worked: after your SourceLace admin adds the source with the fields below, one person clicks Connect, signs in with their company's BTP login, and asks "Which entity sets does ecc:prd offer?". If SAP refuses with HTTP 401, principal propagation (steps 1 and 2) is unfinished; 403, the SAP user lacks an authorization such as S_SERVICE; 404, the service is not published (step 4) or not activated in /IWFND/MAINT_SERVICE.

SAP's own guides: SAP BTP documentation (search for "Cloud Connector", "Principal Propagation" and "Create Destinations") and SAP Help Portal.

Add the source through BTP (SourceLace admin)

In Connections, set Connect through to Your SAP BTP and Cloud Connector, and fill in these fields instead of the agent id:

Option Example What it is
connect_via btp Connect through BTP (Connect through in Connections).
gateway_path /sap/opu/odata/sap Optional: the path after url. / when url already ends at the Gateway root.
url https://corvanta.prod.apimanagement.eu10.hana.ondemand.com/ecc The HTTPS address in BTP, up to just before the Gateway path. Must be on *.ondemand.com or *.cloud.sap.
auth_url https://corvanta.authentication.eu10.hana.ondemand.com Your BTP login service: the subaccount's XSUAA, or SAP Cloud Identity Services such as https://corvanta.accounts.ondemand.com.
client_id, client_secret sb-sourcelace!t12345 The OAuth client your BTP administrators registered for SourceLace. The secret is stored encrypted.
services ZSALES_ORDER_SRV, ZCUSTOMER_SRV The only Gateway services SourceLace may reach.
sap_client 100 Optional: the SAP client, if the destination does not set it.

Each person then clicks Connect and signs in once with their company's BTP login.

What people can do

  • search_schema lists the entity sets of the Gateway services the agent offers, read from each service's $metadata as the person.
  • describe_object on SERVICE/EntitySet lists fields, labels, keys and navigation properties.
  • query (language odata) takes SERVICE/EntitySet plus OData options: $filter, $select, $expand, $orderby, $top, $skip, $inlinecount and sap-language. For example ZSALES_ORDER_SRV/SalesOrderSet?$filter=SoldTo eq '1000'&$select=SalesOrder,NetValue&$top=20. Only entity sets can be queried, never function imports.
  • get_record takes a key such as 4711, or a composite key such as SalesOrder='4711',Item='10', and navigation properties as related lists (up to 3).
  • propose_change and apply_change create or update one record, where allowed. SAP Gateway's CSRF token is handled by the agent. When the service sends ETags, SourceLace refuses to apply a change if the record changed after the preview; when it does not, the preview says so.

Message queues through the agent

The same agent can let SourceLace agents start from messages on IBM MQ inside your network, through its one outbound connection. Your IT team lists the queue manager and the queues SourceLace may read in the agent's configuration file ([[brokers]]); nothing else can be read. A SourceLace admin then adds a message queue connection of type Through the on-site SourceLace Agent, with the agent's id, and agents choose a queue from the agent's list.

  • A message is removed from the queue only after SourceLace has started the agents' runs for it. Until then it stays under the queue manager's unit of work, and it is delivered again if anything fails on the way.
  • Messages that are not JSON start no run. They go to the backout queue your IT team names, or are removed if none is named.
  • The MQ user's password stays on the agent's machine, and is sent to the queue manager only over TLS.

See Start agents from your message queues.

Security

  • No SAP passwords exist in SourceLace or in the agent. Each certificate names one SAP user and expires within minutes.
  • The certificate authority's private key stays on the agent's machine. SourceLace never has it, so SourceLace alone cannot sign in to SAP as anyone.
  • The agent decides what can be reached, from its own configuration file: SAP's address and client, the Gateway services, the writable entity sets and who is which SAP user. SourceLace cannot change any of it.
  • The agent logs request ids, methods, service names, HTTP status and timings, never row data, query options, tokens or keys.
  • Change the agent's token whenever someone who saw it leaves: create a new agent under On-premise agents, put its token in the agent's token file, restart the agent, then Revoke the old agent.
  • Renew the certificate authority before it expires (it is valid 5 years): your IT department makes a new one with sourcelace-agent make-ca into another folder; your SAP Basis administrators import it in STRUST next to the old one and adjust CERTRULE if needed; the IT department switches the agent to the new one; then the old one is removed from STRUST.
  • To stop SourceLace reaching SAP at once, do any one of these: stop the agent, Revoke its token under On-premise agents, or remove the agent's certificate authority from STRUST.
  • The agent's log is safe to share with support: it holds request ids, methods, service names, HTTP status and timings only.
  • Rows from SAP are held briefly like any other source's and are never copied into a database, except inside a saved chat that shows them (How long things are kept). Every answer is read live from your systems, unless your organization has chosen Saved answers, an optional add-on your admin turns on system by system.

When something goes wrong

What you see What it means What to do
"Set the option 'agent': the id of your on-premise agent..." No agent id on a source that connects through the agent. Enter the id from On-premise agents, or set Connect through to SAP BTP.
"You filled in the BTP fields but 'Connect through' is empty..." The BTP fields are filled in, but the source still connects through the agent. Set Connect through to Your SAP BTP and Cloud Connector.
"There is no on-premise agent ... in your organization." The agent id does not exist or was revoked. Use an id from On-premise agents.
"Your organization's SourceLace Agent is offline, so SAP cannot be reached right now..." The agent is not running, or cannot reach SourceLace over outbound HTTPS. A SourceLace admin sees its state under On-premise agents; your IT department checks the agent's log and the proxy.
"The SourceLace Agent (...) did not answer within 60 seconds." SAP or the agent was too slow. Try again with fewer rows ($top) or fields ($select).
"...: SAP did not answer the agent in time. Ask your IT department to check the agent's connection to SAP." (or "could not reach SAP") The agent cannot reach SAP's HTTPS port. Your IT department checks SAP's address, port and certificate in the agent's configuration file (step 4), and runs sourcelace-agent check.
"You have no SAP user in the SourceLace Agent's configuration: ..." The agent cannot map this person's email to an SAP user. Your IT department adds your email domain to the agent's users.domains, or your email to [users.table]. If the message says the email "does not make a valid SAP user name", the part before the @ is longer than 12 characters or has other characters: add the person to [users.table].
"The SourceLace Agent for ... refused this request: The Gateway service ... is not in the agent's sap.services list." The agent's allowlist does not include that service. Your IT department adds it to services (after step 7).
"SAP did not accept the certificate login for ... (HTTP 401)." SAP does not trust the agent's certificate authority, or cannot map the certificate to a user. Your SAP Basis administrators check STRUST (step 5), the ICM (step 6) and CERTRULE or EXTID_DN (step 8).
"SAP refused this for ... (HTTP 403)..." SAP's own authorization check refused it. Ask your security administrators for S_SERVICE on the service and the data authorizations (step 7).
"SAP ECC: ..." or "SAP ECC returned HTTP 404." (through the agent) SAP Gateway's own message, often a service that is not activated (such as "No service found for namespace"). Activate the service in /IWFND/MAINT_SERVICE (step 7).
"SAP BTP sign-in failed: ..." (such as invalid_client or redirect_uri) BTP refused the sign-in: the client id or secret, or the redirect URL in the client. Check the client against its service key, and its redirect URL (BTP step 5).
"SAP refused your new BTP sign-in (HTTP 401), so connecting again will not help..." SAP refused even a token BTP had just issued: principal propagation is not set up for this person. Your BTP and Basis administrators check the destination's PrincipalPropagation, Cloud Connector's trust, and STRUST and CERTRULE in ECC (BTP steps 1 to 3).
"Your SAP BTP session has expired." The BTP sign-in ended. SourceLace refreshes it itself. If it then asks, connect again.
"SAP ECC: nothing was found at ... through SAP BTP (HTTP 404)..." The BTP address published no such service, or already includes the Gateway path. If the BTP address ends at the Gateway root, set Gateway path to /. Otherwise check the service is published (BTP step 4) and activated in /IWFND/MAINT_SERVICE.
"The Gateway service ... is not in this source's services list..." The source lists only some services. Your SourceLace admin adds it to Gateway services.
"SAP BTP could not be reached..." The BTP address is wrong, or BTP is down. Check BTP address.
"The option 'gateway_path' can be / only when connecting through SAP BTP..." / was set for a source that uses the agent. Use the path the agent lists, such as /sap/opu/odata/sap.
"The option 'url' ... must be an https:// address in SAP BTP..." or "... must be your BTP login service..." The BTP address or login service is not on SAP's BTP domains. Copy the address from BTP step 4, and the login service from the service key's url (step 5).
"SAP ECC: the service ... has no entity set ..." The name is wrong, or it is a function import. Check the name with search_schema. Function imports cannot be queried.
"SAP ECC: the record changed after the preview." Someone changed the record in SAP meanwhile. Propose the change again to see the current values.
"The SourceLace Agent sent an answer SourceLace could not read." or "SAP sent an answer that is not JSON." The agent or SAP answered in a form SourceLace does not understand, often because the Gateway service returned an error page. Try again. If it repeats, ask your SAP Basis team to check the service in the Gateway and the agent's log.
"SourceLace could not tell the agent who is asking. Try again." The request reached the agent without the person's SourceLace identity. Try again. If it repeats, contact support.