How to add Slack to SAP ECC 6.0
Short answer
Build a small Slack app that sits next to ECC: slash commands call read-only BAPIs, alerts come from NACE output or IDocs, and interactive buttons call release BAPIs. Socket Mode lets the app run inside your network with outbound connections only, which suits on-prem ECC.
Some ECC manufacturers, often with software or engineering-led teams on the same site, use Slack for operations. Questions like "is this material in stock at plant 1000" or "where is PO 4500012345" turn into someone opening MMBE or ME23N and pasting a screenshot.
A Slack app turns those into one line and keeps the answer, and the person who gave it, in the channel. The same app can post MRP shortages, quality holds and blocked deliveries to the right channel.
What teams use it for
Slash command stock lookup
Type a command with a material number and plant to see unrestricted stock, quality stock and open reservations from the material stock tables.
Order and delivery status
Look up a sales order or delivery and show its status, schedule lines and goods issue state in the thread.
Shortage and expedite channel
Post critical MRP exceptions or late POs to a channel with a button to claim the item for follow-up.
Quality hold alerts
Notify engineers and planners when a batch is blocked or an inspection lot fails usage decision.
Maintenance breakdown ping
Post new PM notifications for critical equipment so on-call technicians see them immediately.
SAP ECC 6.0 integration surface
- Read BAPIs such as BAPI_MATERIAL_AVAILABILITY, BAPI_PO_GETDETAIL and BAPI_SALESORDER_GETSTATUS cover most lookups; exact availability varies by support package.
- For ad hoc reads, RFC_READ_TABLE is tempting but restricted and truncates wide rows; prefer purpose-built function modules.
- NACE output types and IDocs trigger alerts; PM and QM notifications can use their own workflow or user exits.
- RFC clients: SAP NCo, PyRFC or node-rfc; OData if NetWeaver Gateway is installed.
- Authorization: lookups run under a read-only service user, with a user mapping if you need per-person results.
How it works
- 1
Create the Slack app
Define slash commands, bot scopes and interactivity. Use Bolt for a quick start.
- 2
Choose Socket Mode or HTTP
Socket Mode opens an outbound WebSocket so no inbound firewall hole is needed; HTTP mode needs a reachable endpoint.
- 3
Connect to ECC
Run the RFC client in the same service with a service account, connection pooling and timeouts.
- 4
Implement read commands first
Return concise Block Kit messages with source document keys and timestamps, and show what was queried.
- 5
Add alert producers
Subscribe to ECC events via NACE or IDocs and post to channels by plant or planner group.
- 6
Add guarded write actions
Buttons for release or claim-and-comment go through a role check and a confirmation step before any BAPI is called.
Example flows
Stock check in channel
Trigger: A planner types a stock command with a material and plant.
- The app validates the material format.
- It calls the availability BAPI.
- It returns on-hand, quality and reserved quantities with a time stamp.
Result: An answer in seconds with no SAP login.
Late PO alert with claim
Trigger: A nightly job finds PO lines past due.
- The app posts a message per buyer group.
- A buyer clicks Claim.
- The message updates with the owner and a link to ME23N.
Result: Clear ownership of each late line.
Keeping data on-prem
Run the Slack app inside the plant network and use Socket Mode so ECC is never exposed. Slack stores message content, so keep alerts to keys, quantities and statuses. For questions in plain language, put a locally hosted open-weight model in the app so material descriptions and supplier names are not forwarded to a third-party AI.
Security checklist
- Verify Slack request signatures and restrict commands to specific workspace channels.
- Use a read-only RFC role for lookups; separate role for any write actions.
- Do not post prices, costs or restricted technical data to shared channels.
- Rate-limit commands to protect ECC dialog resources.
Ways to get it done
Generic workflow tools with an SAP connector
Effort: Days; limited interaction.
Basic notifications.
Custom Slack app with Bolt
Effort: Typically 3 to 6 weeks.
Internal engineering teams who want control.
Partner such as Netray
Effort: Pilot in weeks.
You want plain-language questions and agentic follow-up on local models.
Pitfalls
- !Slack commands must respond within seconds; ECC calls can be slow, so acknowledge first and post results after.
- !Calling RFC_READ_TABLE for convenience can leak data your authorization model did not intend.
- !Alert noise kills adoption; start with a few high-value alerts.
- !Unit conversion and plant-specific batch handling produce wrong stock answers if ignored.
Frequently asked questions
Can I query SAP ECC from Slack?
Yes. A Slack app can call BAPIs or function modules through RFC under a read-only service user and return the answer in the channel. Start with stock, PO and order status.
Do I need to open ECC to the internet?
No. With Socket Mode the Slack app connects outbound, and the app talks to ECC on the internal network.
Can people approve things in Slack?
They can, with interactive buttons that call release BAPIs, but add identity mapping and a role check. Many sites start with read-only commands and alerts.
Is there an official SAP Slack connector for ECC?
Not for ECC specifically as far as I know. Third-party integration platforms offer connectors, but check how they handle RFC, on-prem agents and write-back.
How is this different from a Teams integration?
The ECC side is the same. Differences are Slack's Block Kit and Socket Mode versus Teams adaptive cards and Entra ID, plus where your users actually are.
Want Slack 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