How to add WhatsApp to Oracle E-Business Suite
Short answer
Add WhatsApp to Oracle EBS by listening to Workflow business events or Oracle Alerts, passing them through a small middleware service, and sending approved template messages through the WhatsApp Business Platform. Replies come back through a webhook and are written to EBS via Integrated SOA Gateway services or open interface tables, never by direct updates to base tables.
Most Oracle EBS sites in manufacturing have a decade of customisations, a locked-down DMZ and a supplier base that already lives on WhatsApp. Buyers chase confirmations by phone, planners forward screenshots of shortage reports, and approvers ignore Workflow email because the mailer lands in a folder nobody reads.
WhatsApp is attractive because suppliers, drivers and plant managers already answer it within minutes. The challenge is that EBS has no native WhatsApp channel. You are building a bridge between the EBS notification and event layer on one side and the WhatsApp Business Platform on the other, with an opt-in register and a clear rule for what is allowed to write back.
This page walks through that bridge for EBS 12.1.3 and 12.2.x, including what to do when the application tier cannot reach the internet directly.
What teams use it for
PO acknowledgement from suppliers
When a purchase order is approved and communicated, send the supplier a template message with the PO number, lines and promise dates, and accept a reply with YES or a new date that updates the promised date through a controlled interface.
Late shipment and ASN nudges
A nightly query over open PO shipments past need-by date triggers a message to the supplier contact asking for a ship date, then logs the answer against the PO shipment as a note for the buyer.
Requisition approvals on the move
Approvers get a short summary of a requisition awaiting approval from the Workflow notification, with Approve and Reject quick-reply buttons that complete the Workflow notification response.
Customer order status
Customer service contacts get dispatch and delivery confirmation messages driven by shipment confirmation in Order Management and Shipping, with a reply option for questions routed back to a CSR queue.
Maintenance and quality alerts
Quality holds, failed inspections and urgent work orders raise a message to the supervisor on duty, with the record number and a link to the OAF page behind your VPN.
Oracle E-Business Suite integration surface
- Workflow Business Event System: subscriptions on events such as oracle.apps.po.event style business events (exact event names vary by module and version) can call a custom PL/SQL rule function that queues a message for middleware.
- Oracle Integrated SOA Gateway (ISG): exposes interfaces from the Integration Repository as REST or SOAP services in 12.2 (REST is available in later 12.2 releases and patch levels), useful for read lookups and for calling supported public APIs on the way back.
- Open Interface tables and public PL/SQL APIs: for example PO_HEADERS_INTERFACE for PO changes and the PO change request APIs, each followed by the matching concurrent import program rather than a direct table update.
- Oracle Alert and concurrent programs: periodic alerts or a custom concurrent request can select the rows that deserve a message and insert them into a custom outbound staging table.
- Workflow notification mailer and WF_NOTIFICATIONS: the notification ID and response options are what a WhatsApp reply must map back onto, using WF_NOTIFICATION.Respond or the supported worklist APIs.
- FND_USER and HR contact data: mobile numbers for suppliers sit in PO_VENDOR_CONTACTS or TCA (HZ_CONTACT_POINTS), and often need cleaning to E.164 format before use.
How it works
- 1
Register a WhatsApp Business account
Create a Meta business account, verify it, and choose either the WhatsApp Cloud API or a business solution provider. Reserve a dedicated number that is not used on a personal handset.
- 2
Build the opt-in register
Add a custom table keyed by supplier site or contact with number, consent date, source and language. Do not send a business-initiated message until a consent record exists.
- 3
Capture EBS events into a staging table
Use a Business Event subscription or a scheduled concurrent program to insert outbound requests into a custom staging table with document type, document ID, template name and parameters. Keep this logic out of the transaction path so a messaging failure never blocks a PO approval.
- 4
Run a small middleware service
A service in the DMZ or an internal subnet with an allowed egress rule polls the staging table or receives a call from a database job, then calls the WhatsApp send endpoint with a pre-approved template and parameters.
- 5
Handle inbound webhooks
Meta calls your public HTTPS endpoint with delivery receipts and replies. The middleware validates the signature, matches the sender to an opt-in record and open document, and parses the reply.
- 6
Write back through supported paths
Valid replies call an ISG service, a public API wrapped in a PL/SQL procedure, or insert into an open interface table. Anything ambiguous goes to a human queue instead of being guessed.
- 7
Monitor and reconcile
Log every message ID against the EBS document, track failures such as invalid numbers and unapproved templates, and report daily to the buyer group.
Example flows
Supplier confirms a PO date
Trigger: PO approved and communicated for a vendor flagged for WhatsApp.
- Business event subscription writes a row to the outbound staging table.
- Middleware sends the po_confirmation template with PO number and first promise date.
- Supplier replies with a new date as free text.
- A parser proposes a date and the buyer sees it in a review queue for high value lines.
- Approved change is submitted through the PO change request path and the buyer is notified.
Result: Promised dates in EBS stay current without a buyer phoning each supplier.
Requisition approval by reply
Trigger: A Workflow notification lands in an approver's worklist for a requisition under a set value.
- Subscription captures the notification ID and requisition summary.
- Template message goes to the approver with Approve and Reject buttons.
- Button payload carries a signed token containing the notification ID.
- Middleware verifies the token and responds to the Workflow notification as that user.
Result: The Workflow completes under the correct approver with an audit trail in WF_NOTIFICATIONS.
Keeping data on-prem
On-prem EBS usually means the database and application tier cannot talk to the internet, and that is fine. Keep the staging table and the logic inside the network, run the middleware on a host in the DMZ, and allow only outbound HTTPS to the WhatsApp endpoints and inbound HTTPS from Meta to the webhook through a reverse proxy. Message content is sent to Meta by design, so for regulated sites keep template parameters to identifiers and dates rather than part descriptions, drawing numbers or customer names. If you want free-text replies understood, the parsing model can run on your own GPU server so reply text from suppliers never goes to a third-party AI service.
Security checklist
- Never expose EBS, ISG or the database to the internet for this; only the thin webhook receiver is public.
- Use a dedicated integration user with a narrow responsibility and ISG security grants limited to the services needed.
- Sign button payloads and reject replies from numbers that do not match the opt-in record.
- Avoid controlled technical data, pricing and customer identities in message bodies; send a reference and use a portal link for detail.
- Retain message logs and consent records according to your records policy and local messaging rules.
Ways to get it done
Off-the-shelf BSP with an Oracle connector
Effort: Weeks, plus template approval time; limited two-way logic.
Fits sites that only need simple notifications and are comfortable with a vendor hosting the message flow.
Build in-house middleware
Effort: Roughly one to three months for a first flow including opt-in and monitoring.
Fits teams with PL/SQL and integration skills who want full control of the write-back rules.
Work with a partner such as Netray
Effort: A scoped pilot on one or two flows first, then extend.
Fits sites that need reply understanding, approvals and on-prem constraints handled together.
Pitfalls
- !Sending business-initiated messages outside an approved template fails once the 24 hour customer service window has closed.
- !Supplier contact phone numbers in EBS are often free text, so normalise and validate them before launch.
- !Direct updates to PO base tables break upgrade and patching assumptions; use supported APIs and interfaces.
- !Approvals by chat need a hard rule on value limits, otherwise you bypass the controls AME was configured to enforce.
- !Online patching cycles in 12.2 can invalidate custom packages, so test the integration after each patch set.
Frequently asked questions
Does Oracle EBS support WhatsApp natively?
No. There is no built-in WhatsApp channel. You connect through Workflow business events or a staging table, a middleware service and the WhatsApp Business Platform, then return replies through ISG services or open interfaces.
Which EBS versions can do this?
Both 12.1.3 and 12.2.x can. The difference is mostly the REST support in ISG on newer 12.2 patch levels and edition-based online patching constraints. On 12.1.3 you will lean more on SOAP services, PL/SQL wrappers and interface tables.
Can the approver reply directly to approve a requisition?
Yes, if you map the reply to the Workflow notification response. Use a signed token and value limits so the approval remains valid under your AME rules, and keep the notification history for audit.
Is customer data sent to Meta?
The message content and phone number are processed by the WhatsApp platform. Keep message parameters to references and dates, and put sensitive detail behind an authenticated link inside your network.
Can replies be understood if suppliers write freely?
A language model can extract a date or a yes or no from short replies. Run it on your own server if you do not want supplier text leaving the network, and route low confidence results to a buyer instead of writing them to EBS.
Want WhatsApp working on your Oracle E-Business Suite?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment