Academy
Data Sources

ERP Step

The ERP step connects the data preparation flow directly to your ERP and pulls ready-to-use reports — trial balances, receivables, master data — through the system’s official APIs, without manually exporting files. Use it when the data you need is available in the native connector’s reports. ERP is in the Data Source category of the toolbar and is available in Turbo AI processes.

You select the ERP, provide a credential, choose the report, and fill in the business filters — the platform takes care of the rest: authentication, API calls, pagination, and technical parameters are managed automatically. Each time the process runs, the data is fetched again from the ERP, with the date filters filled in based on the reference date.

The available ERPs are: SAP S/4HANA, SAP Business One, Microsoft Dynamics 365 Finance & Operations, Microsoft Dynamics 365 Business Central, Oracle NetSuite, Oracle E-Business Suite, and Sankhya. Other connectors appear in the list with the label Coming soon and cannot yet be configured.

Before you start: access and security on the ERP side

This preparation usually involves the team that manages the ERP and your company’s information security team. First, it’s worth understanding the integration’s security model:

  • One-way, outbound from the platform: Dattos is the one calling the ERP API — the ERP does not need to initiate any connection or install anything.

  • Read-only: the step only queries the selected reports. No data is written to or changed in the ERP.

  • Always over HTTPS: all communication is encrypted in transit.

  • Protected credentials: sensitive fields (passwords, secrets, tokens) are encrypted in storage and masked in the interface; privacy profiles control who can use each credential; and access can be revoked at any time — by deactivating the credential in the platform or disabling the integration user in the ERP itself.

What the ERP team needs to grant:

  • Dedicated integration user/application: an exclusive account for the integration (not a person’s account), with a read-only profile, limited to the report entities that will be consumed.

  • ERP API enabled: the API service used by the integration must be active — for example, the OData services in SAP S/4HANA and the Service Layer in SAP Business One.

  • Network access to the API: the platform must be able to reach the API endpoint. Cloud systems (Dynamics 365, NetSuite, Sankhya W) are already accessible over the internet; internal-network systems (SAP on-premise, Oracle EBS middleware) require firewall or VPN/VPC access — contact Dattos Support to set up the appropriate option.

  • Credentials generated and delivered securely: the keys and passwords for the integration user are what you enter in the platform.

What to prepare in each ERP (each connector article details the step-by-step process and all fields):

  • SAP S/4HANA: integration user authorized on the objects of the OData APIs used (e.g., /IWFND/ and /IWBEP/). Authentication via SAP basic login or OAuth 2.0.

  • SAP Business One: dedicated integration user with permission on the queried entities, via Service Layer (user and password).

  • Dynamics 365 Finance & Operations: application registered in Azure AD with the permission Dynamics ERP - Runtime Service, authorized as the integration user in the environment.

  • Dynamics 365 Business Central: application registered in Azure AD with the permission API.ReadWrite.All, authorized under Settings > Business Central API Permissions. The scope name is the Microsoft default — the integration performs read-only operations.

  • Oracle NetSuite: integration with Token-Based Authentication (TBA) enabled and an access token generated for the integration user.

  • Oracle E-Business Suite: integration middleware layer (e.g., Oracle Integration Cloud) exposing EBS data via REST, with the integration server’s user and password.

  • Sankhya: application created in the Sankhya W portal (Settings > Integrations > Applications), with permission on the queried entities.

ERP without internet access: if the system runs only on the company’s internal network, the connection can be made through a site-to-site VPN/VPC — a private tunnel between Dattos’ environment and yours. Contact Dattos Support to evaluate this setup.

How to configure

The configuration opens in full screen, in two steps.

Step 1 — Connection

  • Select the ERP: choose the connector from the list of available ERPs.

  • Credential: select an already registered credential or click + Add ERP credential to register a new one with the data prepared on the ERP side. The fields vary by ERP.

  • Next Step: when you proceed, the platform validates authentication with the ERP. If something is wrong, you will see the message "Authentication failed. Check the credential and try again."

Reusable credentials: once registered, the same credential can be used in multiple steps and processes. Inactive credentials must be reactivated before use.

Step 2 — Configuration

  • Report: select the report from the list, organized by business module (Accounting, Accounts Payable, Sales, among others).

  • Parameters: fill in the report filters (company, period, status). Only business parameters appear here — the API’s technical parameters are managed automatically.

  • Sample Records: number of records brought into the data sample during flow building.

  • Finish: saves the step. Then connect its output to the next steps in the flow, just like any other data source.

Date parameters marked as automatically filled use the execution’s reference date — for example, fiscal year and month, first and last day of the month. This makes the process recurring without manual adjustment: with each closing, the execution retrieves the correct period. You can override the values whenever you need a specific period.

Attention: changing the ERP resets the selected credential and configuration; changing the report resets the parameters. The platform asks for confirmation before doing so.

Usage example

An accounting team needs the SAP S/4HANA trial balance every month. In the ERP step, they select SAP S/4HANA and the integration credential, choose the report Trial Balance in the Accounting module, and keep the period parameters filled in automatically by the reference date. With each monthly run of the process, the trial balance for the reporting month reaches the flow with no manual export — ready to feed a reconciliation or an analysis.

Best practices

  • Data volume: native integrations are encapsulated API calls — performance and supported volume depend on each ERP’s API limits. For very large extractions, prefer the Database step or file exchange.

  • Report unavailable in the connector: the REST API and Database steps obtain data from any system that provides API or SQL access.

  • Authorization error in the report: check with the ERP team whether the integration user has permission on the entities for that specific report.

  • Introduction to integrations

  • ERP integration: SAP S/4HANA · SAP Business One · Dynamics 365 Finance & Operations · Dynamics 365 Business Central · Oracle NetSuite · Oracle E-Business Suite · Sankhya

  • API Rest Step

  • Database Step

Was this helpful?
Was this helpful?