How to add Microsoft Teams to SAP ECC 6.0
Short answer
Connect ECC to Teams with a bot or workflow service that receives SAP events (Business Workflow, NACE output, IDocs), posts adaptive cards, and calls BAPIs when someone clicks Approve. Entra ID identifies the person and maps them to an SAP user, so the action is posted with the right authorization.
ECC approvals normally live in the SAP Business Workplace inbox (SBWP) or in release transactions such as ME28 and ME29N. Approvers who are in Teams all day simply do not open SAP, so purchase orders and requisitions sit unreleased and plants wait.
Teams is a good fit for ECC because it reaches people where they work, supports structured cards with buttons, and can be tied to corporate identity. The work is on the plumbing between an old on-prem SAP system and a cloud collaboration tool.
What teams use it for
PO release cards
Push a card for each purchase order awaiting release strategy approval, with vendor, value, requester and a link, and release it from the card.
MRP exception channel
Post MD06 or MD04 exceptions for a planner group into a channel so shortages and reschedule messages are discussed in one place.
Quality notifications
Alert the quality team when a QM notification or inspection lot is rejected, with the material, batch and plant.
Invoice block resolution
Tell the buyer when an invoice is blocked for price or quantity variance and let them mark it for release or reject.
Ask-the-ERP bot
A bot that answers read-only questions such as stock by plant or open lines on a PO, using BAPIs behind the scenes.
SAP ECC 6.0 integration surface
- Business Workflow (SWDD, SWI1, SWI2_FREQ) emits work items and events; a Z task or event receiver can forward the work item key to middleware.
- Release strategies for POs and requisitions expose BAPI_PO_RELEASE and BAPI_REQUISITION_RELEASE; confirm availability and parameters in transaction BAPI.
- NACE output types and ALE IDocs give event-style triggers without touching standard programs.
- RFC access via SAP NCo, PyRFC or node-rfc, or OData through NetWeaver Gateway where installed.
- User mapping: ECC users (SU01) rarely match Entra ID directly, so keep an explicit mapping table by employee ID or email.
How it works
- 1
Register the bot or workflow app in Entra ID
Create an app registration, define tenant scope, and decide whether the bot is personal, channel-based or both.
- 2
Stand up the bridge service
A service that receives SAP events and calls Teams messaging APIs (Bot Framework or the current Teams SDK, and Microsoft Graph for channels). Hedge: the recommended SDK has changed over time, so check Microsoft's current guidance.
- 3
Emit events from ECC
Forward workflow items or output messages with only a document key. The bridge reads details through RFC.
- 4
Render adaptive cards
Cards carry the key facts and Approve, Reject and Open buttons; the button payload holds the document key and a signed token.
- 5
Authorize and post
On click, map the Entra identity to an SAP user, check the person is a valid releaser for that object, then call the release BAPI.
- 6
Update the card and audit
Replace the card with the outcome and log who did what, when and against which document.
Example flows
Plant manager approves a PO
Trigger: A PO above threshold reaches the plant manager's release code.
- Workflow event reaches the bridge.
- Bridge reads PO header and items.
- An adaptive card is sent to the manager in Teams.
- Manager taps Approve.
- Bridge calls the release BAPI as the mapped user.
Result: Release in minutes rather than waiting for an SAP login.
Planner shortage digest
Trigger: Nightly MRP run completes.
- Bridge pulls exception lines for the planner group.
- A summary card lists critical shortages.
- Planner clicks through to open the material in SAP via a link.
Result: A single prioritised morning list per planner.
Keeping data on-prem
ECC and the bridge can both sit inside your network; the bridge needs outbound access to Microsoft endpoints and a public or relayed endpoint for card button callbacks. For stricter sites, use a relay pattern where the bridge polls for actions instead of exposing an inbound port. Card content is stored by Microsoft, so keep payloads to summaries and keys. If you add a natural-language bot, host an open-weight model locally so questions about stock, vendors and prices are not sent to a public AI service.
Security checklist
- Map each Teams user to an SAP user and perform releases under that identity or with an explicit delegated check, never one shared super-user.
- Sign button payloads and expire them so a forwarded card cannot be replayed.
- Restrict channels that carry commercial data to appropriate groups, and review Teams retention policies.
- Limit the RFC service account to released BAPIs and the specific release objects.
Ways to get it done
Power Automate or a SAP connector with cards
Effort: Days to two weeks; licensing and gateway setup matter.
Light alerting with limited approvals.
Custom bot and bridge
Effort: Typically 4 to 8 weeks.
Controlled approvals with identity mapping and audit.
Partner such as Netray
Effort: Scoped pilot in weeks.
You also want an AI assistant in Teams that queries ECC read-only on local models.
Pitfalls
- !Workflow items released from Teams still need to complete in SAP; releasing a PO without completing the work item leaves stale inbox items.
- !Release code and release group checks are easy to bypass if you only check the user, not the strategy.
- !Entra IDs and SU01 users drift when people change roles; reconcile monthly.
- !Card-based approvals on mobile hide detail; include enough lines or a clear link.
Frequently asked questions
Can ECC send approvals to Teams without custom code?
Rarely. Standard workflow can email, but Teams cards need a bridge. The ECC side can still be configuration only, using NACE or workflow events, while a service handles Teams and BAPI calls.
Does this need SAP Gateway?
No. RFC and BAPIs work without it. OData through Gateway is a convenience for web-style clients if your ECC has Gateway installed.
How do we ensure only authorized people approve?
Resolve the Entra identity to an SAP user, then check the release strategy for that object before calling the BAPI. SAP's own authorization stays the source of truth.
Is Teams data stored outside our network?
Yes, message content sits in Microsoft's cloud, so send keys and summaries, not sensitive commercial or export-controlled detail.
Will this survive a move to S/4HANA?
The cards and the bot largely will. Only the SAP-facing adapter changes, which is why keeping business logic in the bridge pays off.
Want Microsoft Teams working on your SAP ECC 6.0?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment