SAP ECC

SAP ECC (ERP Central Component) is SAP's on-premise ERP suite, and predates SAP's modern S/4HANA API surface. Most ECC environments don't expose anything MODLR can call directly, so this typically uses MODLR's Workaround integration method - combining other MODLR building blocks rather than a direct API, database or file connection:

TIP

Every SAP ECC environment is configured differently, and the right approach depends on what your Basis/functional team can make available. MODLR support is happy to investigate further alongside you - submit a request for SAP ECC integration advice.

• No REST API by default. Unless a customer has specifically implemented SAP Gateway/OData services on top of ECC (an optional add-on, not universal), there's no modern HTTP API to connect to as a Standard or Advanced Integration.
• Direct database access is discouraged. ECC's data model is deeply normalized across thousands of interlinked tables, and SAP's licensing terms generally prohibit unlicensed direct database access - so this isn't treated as a Datasource integration in the usual sense, even where DB credentials happen to be available.
• A scheduled file export is the common workaround. The typical approach is a custom ABAP report or standard transaction, run as a background job, that exports the required data (GL transactions, cost centres, etc.) to a CSV or Excel file. That file is then delivered to a location MODLR can reach - most often an SFTP server - and pulled in via Flat File Load (see TechOne for the same pattern applied to a different platform), or read with Reading Excel Files in MODLR if the export is a workbook rather than a CSV.

Because ECC configurations, module usage and export capabilities vary significantly between customers, the exact export mechanism needs to be confirmed against the specific SAP environment being integrated with, rather than assumed from this page alone.