# How to add Slack alerts and approvals to Oracle E-Business Suite

> Source: https://netray.co/integrations/oracle-ebs-slack
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Integrations

## Short answer

Build a Slack app that posts EBS Workflow and Oracle Alert events into channels through an internal relay, offers slash commands for read-only lookups, and accepts interactive button clicks that respond to Workflow notifications. The relay, not EBS, talks to Slack, so no inbound access to the application tier is needed.

## System

Oracle E-Business Suite

## Capability

slack

## Intro

Slack tends to be the tool of engineering, supply chain planning and customer success teams, often at companies whose ERP is a long-running EBS install. People in Slack channels talk about shortages and escalations, but the data they need sits behind an Oracle Forms or OAF screen that few people have licences or patience for.

The goal is not to move EBS into Slack. It is to push the few events that need a human response into the right channel and let people ask simple questions without logging in, while the system of record keeps the transactions.

Below is a pragmatic design for 12.1.3 and 12.2.x, written for teams that do not want to depend on a marketplace connector for a legacy ERP.

## Use Cases

### Shortage war-room channel

**Description:** Planners post material shortages from MRP exceptions and discrete job component shortages to a channel with item, job, need date and on-hand, and mark owner and ETA by reaction or button.

### Slash command for stock

**Description:** A command such as /ebs onhand ITEM ORG returns on-hand by subinventory and supply and demand next week from a read-only query.

### Procurement escalations

**Description:** High-value POs approaching need date with no receipt create a thread in the buyer channel with a Nudge Supplier button that triggers an email or WhatsApp.

### Order hold release

**Description:** Credit and quality holds in Order Management generate a message to the right owner with a Request Release button that creates a task rather than releasing the hold directly.

### Job close-out reminders

**Description:** Completed discrete jobs not yet closed show up in a weekly list for cost accountants with variance amounts.

## System Surface

- Workflow Business Event System: event subscriptions with a custom PL/SQL rule function to enqueue Slack-bound messages, typically into a custom table or Advanced Queue.
- Oracle Alert: periodic and event alerts that select rows such as past due POs or shortages and can feed the staging table.
- Open API access through Integrated SOA Gateway or PL/SQL wrappers: lookups, and where supported, transactions such as responding to notifications.
- Reporting views over MTL_ONHAND_QUANTITIES_DETAIL, PO_LINE_LOCATIONS_ALL, WIP_DISCRETE_JOBS and OE_ORDER_HEADERS_ALL, noting that exact tables and multi-org access via MOAC views depend on your version and setup.
- WF_NOTIFICATIONS responses for approval actions, together with FND_USER for identity mapping to a Slack user via email address.
- Concurrent manager request status for batch jobs whose completion matters to a team.

## How It Works

### Create the Slack app

**Detail:** Define bot scopes for posting messages, slash commands and interactivity. Enable Socket Mode if you cannot receive public inbound calls, which lets the relay hold an outbound connection to Slack.

### Provision a relay inside the network

**Detail:** The relay reads EBS staging tables, calls Slack APIs and receives interactions. Socket Mode keeps all connections outbound, which suits locked-down EBS environments.

### Capture events from EBS

**Detail:** Use Alerts or a business event subscription to write outbound records. Include record type, key identifiers and the channel route derived from organisation, buyer or planner.

### Build lookup commands on a replica

**Detail:** Create a small set of parameterised queries for the slash commands and run them against a read-only account or a standby database, with row limits and timeouts.

### Add interactive actions

**Detail:** Use Block Kit buttons carrying a signed payload. On click, the relay checks the Slack user against the mapped FND user and performs only actions allowed for that role.

### Close the loop

**Detail:** Update the original message, record the outcome in a custom log table and expose a daily summary to the process owner.

## Example Flows

### Shortage triage

**Trigger:** Nightly planning run produces a critical component shortage for a job due within three days.

**Steps:**

- Alert query writes the shortage to the staging table.
- Relay posts to the planning channel with item, job and available supply.
- A planner clicks Taking It and the relay logs the owner.
- The planner replies with an ETA, which the relay stores as a note.

**Result:** The shortage list is owned in the open and ownership is visible to production.

### Quick stock check

**Trigger:** A supervisor types a slash command in the plant channel.

**Steps:**

- Slack sends the command to the relay.
- Relay validates the user and organisation permission.
- Read-only query returns on-hand by subinventory and open supply.
- Formatted reply appears in the channel, visible only to the requester.

**Result:** Common stock questions are answered in seconds without opening Forms.

## On Prem

Slack is a cloud service, so the only question is how much EBS data you let flow to it. Run the relay inside your network with Socket Mode so connections go outward only, keep payloads to identifiers and summary numbers, and avoid posting part descriptions or customer names for controlled programmes. If an AI model interprets free-text requests, host it on your own GPU server and have it produce a parameterised query that the relay validates, rather than letting it generate SQL against the production database. Where Slack itself is not permitted, the same relay design can post to an on-prem chat tool such as Mattermost.

## Security

- Verify Slack signatures on every inbound request and rotate the signing secret and bot token on a schedule.
- Run lookups on a read-only account scoped to the views you expose, not the APPS schema.
- Map Slack users to FND users by verified email and reject unmapped users.
- Do not post export-controlled technical data, pricing or customer identities into channels with guests.
- Record who clicked what and which EBS call resulted.

## Options

### Generic integration platform with a database trigger

**Fit:** Fits alert-only needs with minimal logic.

**Effort:** A few days per alert type.

### Custom Slack app and relay

**Fit:** Fits interactive approvals, slash commands and strict identity checks.

**Effort:** One to two months for a first set.

### Partner build with Netray

**Fit:** Fits teams adding a private AI assistant behind the Slack front end.

**Effort:** Pilot on one channel, then extend.

## Pitfalls

- Posting every alert to one channel trains people to mute it; route by owner and severity.
- MOAC and operating unit security mean a lookup might return rows the Slack user should not see unless you apply the same restrictions.
- Slack rate limits can throttle bursts such as a month-end alert storm; batch and queue messages.
- Releasing holds directly from a button skips business controls, so create a request instead.
- Custom packages can become invalid after 12.2 patching cycles, and a silent failure means missed alerts. Monitor the queue depth.

## Faq

### Is there an official Slack connector for Oracle EBS?

**Answer:** There is no widely used native one that handles EBS Workflow approvals end to end. Teams usually build a small app with a relay, or use an integration platform for alert-only cases. Check current marketplace listings for your version before deciding.

### Can Slack users approve EBS requisitions?

**Answer:** Yes, if the relay maps the Slack user to the Workflow recipient and calls the supported notification response routine. Keep value limits and fall back to the worklist for anything unusual.

### How do I avoid opening a firewall port to EBS?

**Answer:** Keep all traffic outbound from your network. The relay polls staging tables and uses Slack Socket Mode, so neither EBS nor the database receives an inbound connection from the internet.

### Will slash commands hit my production database?

**Answer:** They can, which is why they should use a read-only account on a replica or standby with row and time limits. Start with a small set of fixed queries and review the load before adding more.

### Can an AI model answer free-form questions in Slack?

**Answer:** Yes. A model hosted on your own server can map a question to an approved query template and format the answer. Avoid giving it raw SQL access to production tables.

## Search terms

oracle ebs slack integration, slack for oracle e-business suite, oracle ebs slack bot, oracle ebs slash command, oracle ebs slack alerts, oracle ebs workflow slack approvals, connect oracle ebs to slack, oracle erp slack notifications, oracle ebs shortage alerts slack, oracle ebs 12.2 slack app

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json