SAP S/4HANA, SuccessFactors and ECC

What SourceLace can do with SAP today: SAP's public demo sandboxes for S/4HANA Cloud and SuccessFactors, read-only. Per-person sign-in to your own SAP systems is not built yet.

What is available today

SourceLace's SAP connectors read SAP's public sandbox on the SAP Business Accelerator Hub: real S/4HANA Cloud and SuccessFactors APIs with shared demo data, not your company's. The sandbox signs in with one API key held by SourceLace, not with each person's own SAP login, so it shows SAP questions working end to end but does not test per-person permissions. Everything is read-only.

Per-person sign-in to your own S/4HANA or SuccessFactors system is not built yet. If you want it, tell support@sourcelace.com which systems and how your people sign in to them today.

SAP S/4HANA

Add the source: kind SAP S/4HANA (s4hana). There is no sign-in page: connecting goes straight back to SourceLace.

Option	Type	Default	Example	What it is
`auth`	Text	(required)	`sandbox`	Must be `sandbox`: SAP's public demo sandbox.
`services`	List, separated by commas	(none)	`API_CUSTOMER_MATERIAL_SRV`	More OData services to offer in schema search, besides the built-in list.

What people can do:

Objects are named SERVICE/EntitySet, such as API_BUSINESS_PARTNER/A_Customer or API_SALES_ORDER_SRV/A_SalesOrder. search_schema searches a built-in list of common APIs (business partners, customers, suppliers, sales orders, billing documents, deliveries, purchase orders, products, stock, receivables) plus the services option.
describe_object reads the service's $metadata: fields, labels, keys and navigation properties.
query (language odata) takes SERVICE/EntitySet plus OData options: $filter, $select, $expand, $orderby, $top, $skip and $inlinecount. For example API_SALES_ORDER_SRV/A_SalesOrder?$filter=SoldToParty eq '17100001'&$select=SalesOrder,TotalNetAmount&$top=20.
get_record takes a key such as 17100001, or a composite key such as SalesOrder='1',SalesOrderItem='10', and navigation properties as related lists (up to 3).

SAP SuccessFactors

Add the source: 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`.
`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, FODepartment or Position.
describe_object reads that entity's $metadata.
query (language odata) takes the entity set plus $filter, $select, $expand, $orderby, $top, $skip, $inlinecount, and the effective-dating options asOfDate, fromDate and toDate (dates such as 2024-01-31). For example EmpJob?$filter=department eq 'SALES'&$select=userId,jobTitle,managerId&$top=20.
get_record takes a key such as admin, or an effective-dated key such as seqNumber=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 and a small SourceLace Agent inside your network, as each person's own SAP user, with no SAP passwords stored. It is in testing: see SAP ECC (on-premise).

When something goes wrong

What you see	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."	Set the `auth` option to `sandbox`. Your own SAP system cannot be connected yet.
"The SAP sandbox needs an API key..." (or "The SuccessFactors sandbox ...")	SourceLace's sandbox key is not set up on this server. Contact support.
"'...' is not an allowed OData option. Use ..."	Only the options listed above are accepted.
"SAP: ... has no entity set ..." or "SuccessFactors has no entity set ..."	Check the name with `search_schema`, or add the service or entity with the source's options.
"Ask for at most 3 related lists at a time."	Ask for fewer related lists in one `get_record`.
"'...' in the entities option of ... is not an entity set name."	Fix the `entities` option: names only, separated by commas.