SAP S/4HANA, SuccessFactors, ECC and Datasphere
What SourceLace can do with SAP today: your own SAP S/4HANA system, reads and approved changes, with each person's own SAP user (see SAP S/4HANA); your own SAP ECC (see SAP ECC); your own SAP Datasphere tenant, read-only, with each person's own Datasphere login (see SAP Datasphere); and SAP's public demo sandboxes for S/4HANA Cloud and SuccessFactors, read-only. Per-person sign-in to your own SuccessFactors system is not available yet.
At a glance
| Connects through | Sign-in | Network | Status | First test question | |
|---|---|---|---|---|---|
| SAP S/4HANA, your own system | S/4HANA OData APIs (V2) | Personal sign-in | Cloud Public Edition: nothing to open. Private Cloud or on-premise: SourceLace Agent or SAP BTP | Pilot | "List 5 customers from s4hana:prod." You see your own customers, as far as your SAP user may see them. |
| SAP S/4HANA, SAP's demo sandbox | S/4HANA Cloud OData APIs on SAP's public sandbox | Shared account | Nothing to open | Verified, sandbox only | "List 5 customers from s4hana:sandbox." You see SAP's demo customers. |
| SAP SuccessFactors | SuccessFactors OData API on SAP's public sandbox | Shared account | Nothing to open | Verified, sandbox only | "Show 5 users from successfactors:sandbox." You see SAP's demo users. |
| SAP Datasphere | Datasphere consumption OData APIs | Personal sign-in | Nothing to open | Pilot | "Which views can I read in datasphere:prod?" You see the assets exposed for consumption in your spaces. |
| SAP ECC | SAP Gateway OData (V2) services | Personal sign-in | SourceLace Agent or SAP BTP | Pilot | See SAP ECC. |
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.
What is available today
- Your own SAP S/4HANA (Pilot): reads, and changes each person proposes and approves, as that person's own SAP user. SAP's own authorizations decide what each person sees and may change.
- SAP's public sandbox on the SAP Business Accelerator Hub, for S/4HANA Cloud and SuccessFactors: real SAP APIs with shared demo data, not your company's, signed in with one API key held by SourceLace. Read-only. Good for seeing SAP questions work before you connect your own system.
Per-person sign-in to your own SuccessFactors system is not available yet. If you want it, tell support@sourcelace.com which systems and how your people sign in to them today.
SAP S/4HANA
SourceLace reads your S/4HANA through SAP's standard OData APIs (such as Business Partner, Sales Order, Purchase Order and Product), and can create or update one record at a time when a person approves the change. It never deletes records. Each person signs in as their own SAP user, so S/4HANA applies that person's business roles and authorizations to every read and every change. SourceLace stores no SAP password.
How SourceLace reaches your system depends on your edition. Choose it under Connect through when you add the source:
| Your S/4HANA | Connect through | What your admin sets up |
|---|---|---|
S/4HANA Cloud Public Edition (run by SAP, address ending in s4hana.cloud.sap) |
Direct | A communication system and arrangements in S/4HANA Cloud: below |
| S/4HANA Cloud Private Edition (RISE with SAP) | SAP BTP and Cloud Connector, or the SourceLace Agent | The same as for SAP ECC: through SAP BTP or through the agent |
| S/4HANA on-premise | The SourceLace Agent, or SAP BTP and Cloud Connector | The same as for SAP ECC: through the agent or through SAP BTP |
| SAP's demo sandbox | Leave Connect through empty | Nothing |
Not sure which edition you have? Your SAP Basis team or SAP account manager knows. If your people open S/4HANA at an address ending in s4hana.cloud.sap, it is the Public Edition.
What your admin does in SAP S/4HANA Cloud Public Edition
Who: your S/4HANA Cloud administrator, a user with the business role for communication management (in SAP's standard roles, the Administrator role, SAP_BR_ADMINISTRATOR). About 30 minutes. SAP's own guide to communication management is in the SAP S/4HANA Cloud Public Edition documentation. Screen names can differ slightly between SAP releases; the steps stay the same.
You need SourceLace's redirect URL:
https://mcp.sourcelace.ai/connect/callback
- Create a communication system for SourceLace. Open the app Communication Systems and choose New. Enter a system ID and name, such as
SOURCELACE. As Host Name, enter SourceLace's host (the host in the redirect URL above). Under OAuth 2.0 Settings (or Users for Inbound Communication, depending on your release), add an inbound OAuth 2.0 client: SAP shows or lets you enter its client ID. Enter SourceLace's redirect URL above as the client's redirect URI, exactly. If SAP creates a client secret, copy it now. Save. - Create a communication arrangement for each API SourceLace may use. Open the app Communication Arrangements and choose New. Pick the communication scenario of the API, such as
SAP_COM_0109(Sales Order Integration) orSAP_COM_0008(Business Partner, Customer and Supplier Integration). SAP's Business Accelerator Hub shows each API's communication scenario on its page, under Overview or Configuration Details. Choose the communication system from step 1, and as the inbound authentication method choose OAuth 2.0. Save. Repeat for each scenario. Only the APIs of arrangements you create here can be used; everything else is refused by SAP. Before you save, read the arrangement's two checks:- Does the scenario offer OAuth 2.0? SourceLace signs people in with OAuth 2.0 only, so an API can be used only through an arrangement whose inbound authentication is OAuth 2.0. Not every communication scenario offers it: some offer only User Name and Password or SSL Client Certificate. On the arrangement, the Supported Authentication Methods link beside Inbound Communication shows what the scenario offers; a scenario that offers OAuth 2.0 also shows OAuth 2.0 Grant Type and Client Type (SourceLace needs Authorization Code + PKCE; a Public Client has no secret). If OAuth 2.0 is not offered, SourceLace cannot read that API directly (see When a scenario has no OAuth 2.0).
- Which of its services can SourceLace use? Under Inbound Services, read the Application Protocol column. A scenario often mixes OData V2, OData V4, SOAP, IDoc and RFC services. SourceLace uses the OData V2 rows and, on the direct sign-in, the OData V4 rows, to read (which interfaces). For each OData V2 row you want, copy the service name from the Service URL (the last part, such as
API_BUSINESS_PARTNER). For each OData V4 row, write the service asgroup/service/versionfrom its Service URL (how). Skip rows marked Deprecated; use the newer one, whose name may end in;v=0002or_2_SRV. Services SourceLace knows are ready; add any other underservices(Add the source), including your own custom ones (names startingYY1_).
- Check people's business roles. Each person who will use SourceLace needs a business user with business roles that allow the APIs and the actions (display, change) they should have. SAP checks these on every call. Nothing extra is needed for SourceLace.
- Note the system's API address (the host with
-api). This is the System address in SourceLace. It is not the address people open in a browser to log in. (SourceLace needs two addresses for one system: the API address for data and tokens, and, in step 5, the UI address for SAP's sign-in page. They differ by-api.) It is your system's address with-apiafter the first part, such ashttps://my123456-api.s4hana.cloud.sapforhttps://my123456.s4hana.cloud.sap. The communication arrangement in step 2 shows it as API-URL under Common Data, and as the host of each service URL under Inbound Services. - Check where SAP's sign-in page lives. In S/4HANA Cloud, the sign-in page (
/sap/bc/sec/oauth2/authorize) is on the UI address on some systems (https://my123456.s4hana.cloud.sap, with no-api), not the API address from step 4. Open it in a browser to check which address shows SAP's login page, and note that full address, such ashttps://my123456.s4hana.cloud.sap/sap/bc/sec/oauth2/authorize. - Send to your SourceLace admin: the API address (step 4), the sign-in address (step 5), the client ID and, if SAP created one, the client secret (step 1), and the scopes, if the arrangement lists any.
Check that it worked: ask the first test question from At a glance. You see your own customers. Signing in shows SAP's own login page for your system (never a grey browser box asking for a user name and password). If you see "SAP refused this ... (HTTP 403)", the sign-in works and the person's business roles do not allow that API (step 3).
If it did not work: look the message up under When something goes wrong.
Which SAP interfaces SourceLace can use
SAP offers the same business data through several kinds of interface. The Application Protocol column of an arrangement's Inbound Services names the kind. SourceLace's S/4HANA connection works with one.
| Application Protocol | Used by SourceLace? | What to know |
|---|---|---|
OData V2 (service URL contains /sap/opu/odata/sap/) |
Yes: reads, and changes people approve | Prefer rows that are not marked Deprecated. |
OData V4 (service URL contains /sap/opu/odata4/) |
Yes, reads only, on the direct sign-in | SAP's newer services. Name them as in Adding an OData V4 service. Changes to V4 data are not available yet, and V4 is not available through SAP BTP or the SourceLace Agent. |
| SOAP | No, in the S/4HANA connection | Often used to send data into S/4HANA (names like "Replicate" or "Confirmation"). |
| IDoc | No | A message SAP sends or receives, not something to ask questions of. |
RFC (names like BAPI_...) |
No | SAP's internal function calls. |
An arrangement can use only the rows of the kinds above that SourceLace supports; the others are simply not used, and the arrangement still works for the OData V2 and V4 rows. If a scenario has no OData V2 or V4 row you need, see When a scenario has no OAuth 2.0 for the other ways to get the same data.
Your own objects: custom business objects you published in S/4HANA Cloud (names starting YY1_, such as YY1_MYOBJECT_CDS) appear as OData V2 rows of a custom communication scenario. Add their service names under services; each person sees only what their own SAP roles allow.
Adding an OData V4 service
A V4 service address has several parts, so SourceLace asks for them as group/service/version. In the arrangement's Inbound Services, open the row's Service URL. After /sap/opu/odata4/sap/ it reads group/srvd_a2x/sap/service/version. Drop the fixed srvd_a2x/sap and keep the rest:
| The Service URL ends | Enter under services |
|---|---|
.../sap/opu/odata4/sap/api_product/srvd_a2x/sap/product/0001/ |
api_product/product/0001 |
- Add it to the source. In Connections, edit the S/4HANA source and add the name to Services, next to any V2 names. It is the same source and the same sign-in; nothing else changes.
- Find its tables. Ask for the service's objects (for example "describe the objects in
api_product/product/0001"). An object is the service and a table:api_product/product/0001/Product. - Read it. Questions work as for V2: for example
api_product/product/0001/Product?$filter=ProductType eq 'FERT'&$top=20. People see only what their own SAP roles allow.
Good to know: V4 services whose address does not contain srvd_a2x are not supported yet. $inlinecount is not used in V4, and $expand takes up to three plain names. A number, GUID, date or true/false key is written without quotes (UnitId=42), and a text key as is. If a V4 service does not show up when people search, its name or arrangement is wrong: ask to describe service/EntitySet (or read it) to see SAP's own message.
When a scenario has no OAuth 2.0
SourceLace does not fall back to a user name and password or a certificate, and it never keeps an SAP password, so it cannot use that API through this connection. What you can do:
- Look for another API for the same data. SAP often offers the same business objects through a second scenario or a newer API; the Business Accelerator Hub lists the scenario of each. If one offers OAuth 2.0, build its arrangement and add the API's service name under
services(Add the source). - Ask SAP, or your SAP partner, whether your release has an OAuth 2.0 variant of the scenario. SAP may add authentication methods to a scenario in a later release.
- Leave that API out. Everything else you arrange with OAuth 2.0 keeps working; only the missing API is unavailable.
- Tell SourceLace support which scenario and API you need.
Add the source (SourceLace admin)
Kind SAP S/4HANA (s4hana). Pick Connect through first; the form then shows only the fields that apply.
| Option | Type | Default | Example | What it is |
|---|---|---|---|---|
connect_via |
Choice | (empty: SAP's sandbox) | direct |
Connect through: direct (Cloud Public Edition), btp (your SAP BTP and Cloud Connector) or agent (the SourceLace Agent). Empty with auth = sandbox reads SAP's demo sandbox. |
url |
Address | (required for direct and BTP) | https://my123456-api.s4hana.cloud.sap |
Direct: your system's API host, the address with -api in it (step 4 above). It is where SourceLace fetches data and tokens, not the address people open to log in; if SAP's login page is on another address, use authorize_url. BTP: the BTP address that forwards to S/4HANA's Gateway, as for ECC. |
client_id |
Text | (required for direct and BTP) | SourceLaceClient |
The OAuth client ID (step 1 above, or the BTP service key). |
client_secret |
Secret | (none) | Its secret, if it has one. Stored encrypted and never shown again. Without a secret, the direct sign-in uses SAP's public client sign-in (PKCE). | |
scope |
List, separated by spaces | (none) | Scopes to ask for, if your arrangements list any. | |
services |
List of names | Direct: SAP's standard APIs SourceLace knows. BTP: (required) | API_CUSTOMER_MATERIAL_SRV |
More OData services people may use: a V2 service by the name in the arrangement's Service URL, such as API_CUSTOMER_MATERIAL_SRV (or API_OUTBOUND_DELIVERY_SRV;v=0002 when SAP shows a version); on the direct sign-in also a V4 service as group/service/version, such as api_product/product/0001 (how). Through BTP, the only V2 services SourceLace may reach. |
agent |
Text | (required for the agent) | agt_0123456789ab |
The SourceLace Agent's id, as for ECC. |
gateway_path |
Path | /sap/opu/odata/sap |
Where the OData services live. Rarely needs changing. | |
auth_url, sap_client |
Through BTP only, as for ECC. | |||
authorize_path, token_path |
Path | SAP's defaults | /sap/bc/sec/oauth2/authorize |
Direct only: change them only if your SAP administrator says your system signs in at other paths. |
authorize_url |
Address | (empty: url plus authorize_path) |
https://my123456.s4hana.cloud.sap/sap/bc/sec/oauth2/authorize |
Direct only: the full address of SAP's sign-in page, for a system whose sign-in page is on its UI address (no -api) while url is the API address. Use it instead of authorize_path, not with it. |
auth |
Text | (none) | sandbox |
sandbox for SAP's public demo sandbox. |
To let people propose changes, turn on Allow changes on the source and list the objects that may be changed, as SERVICE/EntitySet, such as API_SALES_ORDER_SRV/A_SalesOrder. Through the agent, the agent's own writes list must allow them too.
What people can do
- Objects are named
SERVICE/EntitySet, such asAPI_BUSINESS_PARTNER/A_CustomerorAPI_SALES_ORDER_SRV/A_SalesOrder. On the sandbox and through the direct sign-in,search_schemasearches a built-in list of common APIs (business partners, customers, suppliers, sales orders, billing documents, deliveries, purchase orders, products, stock, receivables) plus theservicesoption. Through BTP or the agent, it searches the services those allow. describe_objectreads the service's$metadata: fields, labels, keys and navigation properties.- OData V4 services (direct sign-in) work the same way, read only, with objects named
group/service/version/EntitySet, such asapi_product/product/0001/Product(Adding an OData V4 service). query(languageodata) takesSERVICE/EntitySetplus OData options:$filter,$select,$expand,$orderby,$top,$skipand$inlinecount. For exampleAPI_SALES_ORDER_SRV/A_SalesOrder?$filter=SoldToParty eq '17100001'&$select=SalesOrder,TotalNetAmount&$top=20.get_recordtakes a key such as17100001, or a composite key such asSalesOrder='1',SalesOrderItem='10', and navigation properties as related lists (up to 3).- Changes (your own system only):
propose_changecreates or updates one record of an object an admin made changeable, and shows the current values first. Nothing changes until the person approves. If someone else changed the record in SAP since the preview, the change is refused and the person proposes it again. Records are never deleted. Agents' changes wait for approval in the same way.
SAP SuccessFactors
What your admin does in SAP SuccessFactors
Nothing, today. As with S/4HANA, this source reads SAP's public SuccessFactors demo sandbox, with demo data and an API key SourceLace holds. Nobody registers anything in SuccessFactors. SAP's own API reference is on the SAP Business Accelerator Hub.
Check that it worked: ask the first test question from At a glance. You see SAP's demo users.
Add the source (SourceLace admin)
Kind SAP SuccessFactors (successfactors). As with S/4HANA, there is no sign-in page.
| Option | Type | Default | Example | What it is |
|---|---|---|---|---|
auth |
Text | (required) | sandbox |
Must be sandbox. In Connections this is Sign-in method, already set to the sandbox. |
entities |
List, separated by commas | (none) | cust_Vehicle, Background_Education |
More entity sets to offer in schema search, including custom cust_ objects. |
What people can do
- Objects are entity sets such as
User,PerPerson,EmpJob,EmpEmployment,FODepartmentorPosition. describe_objectreads that entity's$metadata.query(languageodata) takes the entity set plus$filter,$select,$expand,$orderby,$top,$skip,$inlinecount, and the effective-dating optionsasOfDate,fromDateandtoDate(dates such as2024-01-31). For exampleEmpJob?$filter=department eq 'SALES'&$select=userId,jobTitle,managerId&$top=20.get_recordtakes a key such asadmin, or an effective-dated key such asseqNumber=1L,startDate=datetime'2015-01-01T00:00:00',userId='admin'.
SAP ECC
SAP ECC systems in your own data centre (kind ecc) are read through your SAP Gateway OData services, either with a small SourceLace Agent inside your network or through your SAP BTP and Cloud Connector, as each person's own SAP user, with no SAP passwords stored. It is Pilot: see SAP ECC (on-premise).
SAP Datasphere
SourceLace reads the views and analytic models your SAP Datasphere tenant exposes for consumption, through Datasphere's consumption OData APIs. Each person signs in with their own Datasphere login, so Datasphere shows them only the spaces they are a member of, and applies its own roles and data access controls. Everything is read-only.
Status: Pilot. New or partial, offered to pilot customers. Built on SAP's documented Datasphere consumption APIs; not yet used with a customer's live tenant.
What your admin does in SAP Datasphere
It takes about 10 minutes, once per tenant.
Who: a Datasphere user with the DW Administrator role (or a role with the System Information privilege to update), who can open System → Administration → App Integration. For step 5, each space's DW Space Administrator.
- Note the Authorization URL. In Datasphere, open System → Administration → App Integration. Copy the Authorization URL at the top, such as
https://corvanta.authentication.eu10.hana.ondemand.com/oauth/authorize. This is the Authorization URL field in SourceLace. - Add an OAuth client. Under Configured Clients, click Add a New OAuth Client:
- Name:
SourceLace. - Purpose: Interactive Usage (each person signs in as themselves; not API Access, which is a technical user and cannot be used to sign people in).
- Redirect URI:
https://mcp.sourcelace.ai/connect/callback, exactly, with nothing after it. - Token lifetimes (if your tenant shows them): the refresh token lifetime is how long people stay connected before they sign in again, such as 30 days.
- Name:
- Copy the client's id and secret. Click Add. Copy the OAuth Client ID and the Secret into SourceLace's OAuth Client ID and Secret fields. Datasphere shows the secret only now: if it is lost, delete the client and add a new one.
- Copy the tenant address. It is the host of the address people open Datasphere at, such as
corvanta.eu10.hcs.cloud.sap, withouthttps://. This is the Tenant address field. - Let people read the data. Views need Expose for Consumption switched on and must be deployed; analytic models must be deployed. In Space Management, open each space people should read, and under Users (or Members) add them with a role that may read its data.
Check that it worked: after your SourceLace admin adds the source, one space member clicks Connect on My connections, signs in with their Datasphere login, and asks the first test question from At a glance. They see the views exposed in their spaces. If it fails, look the message up under When something goes wrong.
SAP's own guide: SAP Datasphere documentation (search for "Create OAuth2.0 Clients to Authenticate Against SAP Datasphere" and "Exposing Data for Consumption").
Add the source (SourceLace admin)
Kind: SAP Datasphere (datasphere). Type the secret on the web app's Connections page, not in a chat.
| Option | Type | Default | Example | What it is |
|---|---|---|---|---|
host |
Host name | (required) | corvanta.eu10.hcs.cloud.sap |
The tenant address. Must end in .cloud.sap. |
auth_url |
Address | (required) | https://corvanta.authentication.eu10.hana.ondemand.com/oauth/authorize |
The Authorization URL from step 1. |
client_id |
Text | (required) | sb-1a2b3c4d... |
The OAuth Client ID from step 3. |
client_secret |
Secret | (required) | The secret from step 3. Stored encrypted; shown only as (saved). |
|
spaces |
List, separated by commas | (every space the person can see) | SALES, FINANCE |
Only these spaces are offered and read. Datasphere's own permissions still apply inside them. |
What people can do
- Objects are named
SPACE/ASSET, such asSALES/SALES_ORDERS.search_schemasearches the assets exposed for consumption that the person can see. describe_objectreads the asset's$metadata: its columns, labels and, for analytic models, which columns are measures.query(languageodata) takesSPACE/ASSETplus$select,$filter,$orderby,$topand$skip, such asSALES/SALES_ORDERS?$select=Customer,NetAmount&$filter=NetAmount gt 1000&$orderby=NetAmount desc&$top=50. Analytic models also take$applyto aggregate, such asSALES/REVENUE?$apply=groupby((Region),aggregate(Revenue with sum as Revenue)).SPACE/ASSET/$count?$filter=...returns the number of rows.- SourceLace reads at most your organization's row limit, in pages, and stops waiting after its query time limit. Datasphere has no way to stop a query from outside, so it may finish on its own.
- There is no
get_record: usequerywith a$filteron the key columns. - Views with input parameters cannot be queried yet.
When something goes wrong
| What you see | What it means | What to do |
|---|---|---|
| "...: per-user SAP sign-in is not built yet. For now, this source needs "options": {"auth": "sandbox"} to use SAP's public sandbox." | A SuccessFactors source was saved without the sandbox sign-in method. | In Connections, set Sign-in method to SAP's public demo sandbox (the form chooses it for you). Your own SuccessFactors system cannot be connected yet. |
| "Choose how SourceLace reaches your S/4HANA system under 'Connect through'..." | An S/4HANA source has neither a way to connect nor the sandbox. | Choose Direct, SAP BTP or the SourceLace Agent (see the table under SAP S/4HANA), or set Sign-in method to the sandbox. |
| "The option 'url' must be your S/4HANA Cloud system's https:// API host..." | The address is not an S/4HANA Cloud API host (the one with -api), or it has a path. |
Enter only https:// and the API host, such as https://my123456-api.s4hana.cloud.sap, not the login address (step 4). |
| A grey browser login box appears at sign-in and SAP rejects it, or the sign-in page never shows SAP's login. | The sign-in request went to the API address, which can ask for a password in the browser instead of showing SAP's login page. | In the source, set Sign-in address (authorize_url) to the UI address's sign-in page, such as https://my123456.s4hana.cloud.sap/sap/bc/sec/oauth2/authorize (step 5), and leave Sign-in path empty. |
| "The option 'authorize_url' must be your S/4HANA Cloud sign-in address..." | The address is not https://, not on an S/4HANA Cloud domain, has a port or query, or has no path. | Enter the full sign-in address from step 5. |
| "Set either 'authorize_url' or 'authorize_path', not both." | Both sign-in options are filled in. | Keep Sign-in address and empty Sign-in path. |
| "SAP S/4HANA Cloud sign-in failed (invalid_client)..." or "... (unauthorized_client)..." | The client ID or secret is not the communication system's inbound OAuth client, or the client may not use this sign-in. | Copy the client ID (and secret) again from the communication system (step 1). |
| "SAP S/4HANA Cloud sign-in failed: invalid_grant ..." or "... redirect_uri ..." | The client's redirect URI is not exactly SourceLace's. | Set the redirect URI to SourceLace's redirect URL, exactly (step 1). |
| "SAP S/4HANA Cloud refused your new sign-in (HTTP 401), so connecting again will not help..." | SAP refused even a token it had just issued: the API has no communication arrangement with OAuth 2.0 for SourceLace's communication system. | Your S/4HANA Cloud administrator creates the arrangement for that API's scenario (step 2). |
| An API you need is refused, or the arrangement cannot be saved with OAuth 2.0. | Its communication scenario does not offer OAuth 2.0 as an inbound authentication method, so SourceLace cannot sign in to it. | See When a scenario has no OAuth 2.0: find another API for the same data, or leave it out. |
| A scenario's rows say SOAP, IDoc or RFC, and SourceLace cannot use them. | SourceLace reads OData V2 and V4 services only. | Use the scenario's OData rows, or see Which SAP interfaces SourceLace can use. |
| "'...' is not an OData service name, such as API_SALES_ORDER_SRV (V2) or api_product/product/0001 (V4...)." | A name in Services is neither a V2 name nor group/service/version. |
For V4, take the part of the Service URL after /sap/opu/odata4/sap/, drop srvd_a2x/sap, and write group/service/version (how). |
| "OData V4 services can be read through the direct sign-in to S/4HANA Cloud Public Edition only." | A V4 service was used on a source that connects through SAP BTP or the SourceLace Agent. | Use that system's OData V2 services, or connect it directly if it is Public Edition. |
| "SAP S/4HANA Cloud: nothing was found for the V4 service ... (HTTP 404)..." | The service has no communication arrangement for SourceLace's communication system, or the name does not match the arrangement's Service URL. | Check the arrangement (step 2) and write the name as in Adding an OData V4 service. |
| "SAP refused this for ... (HTTP 403)..." | The sign-in works, but the person's business roles do not allow this API or action. | Your SAP administrator checks the person's business roles (step 3). |
| "SAP S/4HANA: the record changed after the preview..." | Someone changed the record in SAP between the preview and the approval. | Propose the change again to see the current values. |
| "SourceLace never deletes records in SAP S/4HANA..." | A delete was asked for. | Delete the record in SAP itself. |
| "SAP's public sandbox is read-only..." | A change was proposed on the demo sandbox. | Connect your own S/4HANA system to make changes. |
| "SAP S/4HANA: nothing was found at ... (HTTP 404)..." | The service is not set up: no communication arrangement (direct), not published in BTP, or not activated in Gateway. | Direct: create its arrangement (step 2). BTP or agent: as for ECC. |
| "SAP S/4HANA: nothing was found at ... (HTTP 404): Resource not found for the segment 'X'" | The service is set up, but X is not a field or entity it has. In the chat this reads "SAP did not recognise the field or object 'X'", and the answer usually carries on with a later step. | Nothing, when the answer arrived. If the question ended in failure, ask which fields the object has, or check the spelling of X with your SAP administrator. |
| "The SAP sandbox is not set up on SourceLace yet..." (or "The SuccessFactors sandbox ...") | SourceLace's access to SAP's sandbox is not ready. | Contact support. |
| "SAP refused the request (HTTP 401)..." or "SuccessFactors refused the request (HTTP 403)..." | SAP's sandbox did not accept SourceLace's key. | Contact support. |
| "SAP returned HTTP 429." (or "SuccessFactors ...") | SAP's sandbox limits how many requests everyone sends it. | Try again in a minute. |
| "'...' is not an allowed OData option. Use ..." | Only the OData options listed above are accepted. | Use those options. |
| "SAP: ... has no entity set ..." or "SuccessFactors has no entity set ..." or "... is not an S/4HANA object" | The name is wrong, or not in the built-in list. | Check the name with search_schema, or add the service or entity with the source's options. |
| "S/4HANA queries are SERVICE/EntitySet..." or "SuccessFactors queries are EntitySet..." | The query does not start with an object name. | Start with the object, such as API_BUSINESS_PARTNER/A_Customer?$top=5. |
| "'...' in the services option of ... is not an OData service name." or "'...' in the entities option of ... is not an entity set name." | The option has something other than names. | Names only, separated by commas. |
| "Ask for at most 3 related lists at a time." | get_record asked for too many related lists. |
Ask for fewer. |
| "... must be a date such as 2024-01-31." | An effective-dating option (asOfDate, fromDate, toDate) is not a date. |
Use the form 2024-01-31. |
| "SAP Datasphere sign-in failed (unauthorized_client): this OAuth client cannot be used for personal sign-in..." | The OAuth client's purpose is not Interactive Usage. | Add a client with the purpose Interactive Usage (step 2) and enter its id and secret. |
| "SAP Datasphere sign-in failed (invalid_client): the client ID or secret is wrong..." | The id or secret on the source is not the client's. | Add a new client and copy both again (step 3). |
| "SAP Datasphere sign-in failed: invalid_grant ..." or "... redirect_uri ..." | The sign-in code was refused, usually because the client's Redirect URI is not exactly SourceLace's. | Set the Redirect URI to the one in step 2, exactly. |
| "SAP Datasphere did not accept your new sign-in (HTTP 401), so connecting again will not help..." | Datasphere refused even a token it had just issued: the person has no Datasphere user, or the client is not Interactive Usage. | Your Datasphere admin checks the person's user and the client's purpose. |
| "Your SAP Datasphere session has expired." | The sign-in ended. | SourceLace refreshes it itself. If it then asks, connect again. |
| "SAP Datasphere: you do not have access to this..." | Datasphere's own permissions refused it (HTTP 403). | Ask your Datasphere admin to add you to the space, or to give you a role or data access control that allows it. |
| "SAP Datasphere: SPACE/ASSET was not found, is not exposed for consumption, or you cannot see it..." | The name is wrong, the view is not exposed, or the person is not in its space. | Check the name with search_schema. Its modeler may need to turn on Expose for Consumption and deploy it. |
| "SAP Datasphere: SPACE/ASSET has no data set SourceLace can read. If it has input parameters, ..." | Views with input parameters cannot be queried yet. | Query a view without input parameters. |
| "SAP Datasphere could not run this query..." | Datasphere refused the query (HTTP 400 or 501). | Check column names with describe_object. $apply works on analytic models only. |
| "SAP Datasphere took too long to answer..." | The query ran past the time limit. | Narrow it: fewer columns, a $filter, a smaller $top, or aggregate with $apply. |
| "SAP Datasphere is busy (too many requests)..." or "SAP Datasphere had a problem (HTTP 503)..." | Datasphere is overloaded or under maintenance. | Try again in a few minutes. |
| "SAP Datasphere could not be reached..." | The tenant address is wrong, or Datasphere is down. | Check Tenant address, then try again. |
| "... needs the option 'auth_url' ..." or "The option 'auth_url' of ... must be the Authorization URL ..." | The Authorization URL is missing or wrong. | Copy it from Datasphere's App Integration page (step 1). |
| "The option 'host' of ... must be a host name ending in .cloud.sap..." | The tenant address is not a Datasphere address. | Copy only the host, such as corvanta.eu10.hcs.cloud.sap (step 4). |
| "SuccessFactors: no ... with key ..." | No record has that key in the demo sandbox. | Use a key from a query's results. |
| "... returned $metadata that could not be read." or "... sent a next-page link to a different address; stopping." | SAP's answer was not in the form SourceLace expects, or it pointed to another address, which SourceLace never follows. | Try again shortly. If it repeats, contact support. |
| "The option 'spaces' of ... lists more than 50 spaces." | The Datasphere source's list of spaces is longer than SourceLace reads. | An admin shortens the list in the source's Spaces (optional) field, or leaves it empty. |
| "SAP Datasphere answered with a web page instead of data (HTTP ...)." or "SAP Datasphere did not answer $count with a number." | Datasphere had a problem, or something between SourceLace and Datasphere answered instead. | Try again shortly. If it repeats, contact support. |
| "SourceLace refused to call an unexpected SAP Datasphere address." | A link in Datasphere's answer led outside your Datasphere host; SourceLace never follows those. | Try again. If it repeats, contact support. |