SAP S/4HANA Cloud Access for Data Foundation
Data Foundation brings data from every ERP system and instance you connect into one Common Finance Model, and SAP S/4HANA Cloud is one of the ERPs it reads directly. The connection reads the tenant’s released OData services with OAuth 2.0 client credentials; no agent is involved. This page is for the S/4HANA Cloud administrator who sets that up, and for the PlaidCloud user who asks them to.
PlaidCloud only reads data. Nobody sends a password or a client secret by email.
Send the Access Request
Section titled “Send the Access Request”On the project’s Foundation tab, choose Create a new connection under SAP S/4HANA Cloud connection. The form shows the full request. Click Copy request to paste it into your own message, or Email request to open it in your mail program with the subject “Read-only SAP S/4HANA Cloud access for PlaidCloud (OAuth 2.0 client credentials).”
What the S/4HANA Cloud Administrator Sets Up
Section titled “What the S/4HANA Cloud Administrator Sets Up”-
Create a communication user for PlaidCloud, in the app Maintain Communication Users. Its authentication method is OAuth 2.0 or user name and password, as your landscape requires.
-
Create a communication system for PlaidCloud, in the app Communication Systems, with that user for inbound communication and OAuth 2.0 client credentials.
-
Create a communication arrangement for each scenario below, in the app Communication Arrangements, all for the system from step 2. Together they expose the OData services PlaidCloud reads:
Scenario Service Company Code API_COMPANYCODE_SRVG/L Account in Chart of Accounts API_GLACCOUNTINCHARTOFACCOUNTS_SRVCost Center API_COSTCENTER_SRVBusiness Partner and Customer API_BUSINESS_PARTNERProduct API_PRODUCT_SRVFiscal Year Variant Periods API_FISCALYEARPERIODFORVARIANT_SRVExchange Rates API_EXCHANGERATE_SRVJournal Entry Item API_JOURNALENTRYITEMBASIC_SRV(the journal and the balance carried forward)Billing Document API_BILLING_DOCUMENT_SRV(optional: it adds invoiced sales, documents and items)Give the communication user access to every company code you report on.
What to Send Back
Section titled “What to Send Back”| The administrator sends | Entered in PlaidCloud as |
|---|---|
The host of the tenant’s API, for example my300000-api.s4hana.cloud.sap |
Host |
| The client ID | Client ID |
| The client secret, through the secure connection form | Client secret, which your team pastes in itself |
The token URL, only if your landscape uses an XSUAA authorization server instead of the tenant’s own (/sap/bc/sec/oauth2/token) |
Token URL (optional) |
| The scope, only with an XSUAA authorization server | Scope (optional) |
| Whether Carry Forward Balances has run for each fiscal year you load | Nothing to enter. The opening balances are read from it. |
Check the Access
Section titled “Check the Access”Back in PlaidCloud, enter the values and click Test connection. Each dataset shows as Readable, Missing permission or Error:
| Dataset | Service it needs |
|---|---|
| Entities | API_COMPANYCODE_SRV |
| Chart of accounts | API_GLACCOUNTINCHARTOFACCOUNTS_SRV |
| Departments | API_COSTCENTER_SRV |
| Customers | API_BUSINESS_PARTNER |
| Products | API_PRODUCT_SRV |
| Currency rates | API_EXCHANGERATE_SRV |
| Fiscal calendar | API_FISCALYEARPERIODFORVARIANT_SRV |
| General ledger | API_JOURNALENTRYITEMBASIC_SRV |
| Trial balance | API_JOURNALENTRYITEMBASIC_SRV |
| Sales lines | API_BILLING_DOCUMENT_SRV (optional) |
When a dataset shows Missing permission, ask the administrator to add the communication arrangement for its service and test again. Sales lines, budget and inventory balances are optional: a tenant that doesn’t hold one still loads everything else.