Connect SAP ECC with Microsoft Dynamics 365 Customer Insights using appse ai to automate workflows, sync data, and eliminate manual tasks between both platforms.
160+
Integrations
135+
Clients
100%
Custom Integration
Explore triggers and actions available for both apps. Switch between apps to see what each one can do.
Showing triggers & actions for SAP ECC
| Modules | Action |
|---|---|
| Simulate Sales Order | Simulate a sales order using BAPI_SALESORDER_SIMULATE (SAP ECC / S/4HANA). Read-only — returns pricing, schedule lines and availability without creating a document (no commit). |
| Check Material Availability | Check ATP material availability using BAPI_MATERIAL_AVAILABILITY. Plant, Material and Unit are mandatory. |
| List Custom Objects (BAPI/RFC) | Search RFC-enabled function modules by name pattern using RFC_FUNCTION_SEARCH. Used as the option source for the Custom Object dropdown. |
| Create Sales Order | Create a sales order using BAPI_SALESORDER_CREATEFROMDAT2 (SAP ECC / S/4HANA). Commits automatically. |
| Get Sales Order Details | Read detailed data for one or more sales orders using BAPISDORDER_GETDETAILEDLIST. |
| Get IDoc Status by Source Reference | Find an inbound IDoc by the source order number and return its number and status. Reads EDIDC where ARCKEY matches the reference the IDoc post wrote into the control record. Use this after posting an IDoc asynchronously — the post confirms only that SAP accepted the call, so this is how the flow learns whether an IDoc exists and what happened to it. Status 53 = posted, 64 = created and waiting for processing, 51 = application error. |
| Advance Action | Call any custom BAPI / RFC-enabled function module. Pick the object; its parameters load dynamically from the SAP interface metadata. Choose the operation (create/update commit; query reads). |
| Get Customer Detail | Read customer master data using BAPI_CUSTOMER_GETDETAIL2 |
| Get Custom Object Schema (BAPI/RFC Metadata) | Return the parameter/field schema of an RFC-enabled function module or BAPI by reading its SAP interface metadata (no execution). Provide the exact function name (e.g. a Z*/Y* BAPI). |
| Create Sales Order (IDoc — ORDERS05) | Post an inbound ORDERS05 sales-order IDoc into SAP through the on-prem agent and return the assigned IDoc number. Segments are packed and posted via the inbound-IDoc RFC function; SAP processes the IDoc into a sales order per the partner profile (WE20). Success means the IDoc was created and committed (status 64), not that the sales order posted — verify processing in a following step. Not idempotent: re-posting creates a second IDoc, so filter source orders by datetime window rather than retrying blindly. |
| Get Customer List | List customers using BAPI_CUSTOMER_GETLIST. Optionally filter by a customer number range (select-options). |
Automate smarter with an AI-native platform designed for the way mid-market businesses really work.