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

Oracle E-Business Suite integration 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

1. 1

   Create the Slack app

   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.

2. 2

   Provision a relay inside the network

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

3. 3

   Capture events from EBS

   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.

4. 4

   Build lookup commands on a replica

   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.

5. 5

   Add interactive actions

   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.

6. 6

   Close the loop

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

Security checklist

• 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.