
Accenture says Combe put finance and supply chain on Fusion
The announcement came from Accenture rather than Oracle, and it carries no go-live date and no numbers. The customer profile is the part to read.
Topic coverage
Source-linked reporting and practical patterns organized around a shared enterprise applications question.

The announcement came from Accenture rather than Oracle, and it carries no go-live date and no numbers. The customer profile is the part to read.

An Oracle press release pairs undated patient intake with prescriber credentialing that ships now. The reusable credential model is the part worth copying.

An ODP security check has landed in SAP EarlyWatch Alert, putting a June note about unchecked RFC callers in front of people who never read the patch queue.

Workday says early adopters cut benefit provider onboarding time by 75 percent. The trade is that the list of providers you can connect to is now Workday's.

Oracle says the Manchester arena has connected Simphony to NetSuite. The release skips every number a finance architect would need to judge it.

A vendor press release states an intention to connect reimbursement workflows to Fusion financials. Nothing named in it is generally available yet.

Tottenham Hotspur consolidated about 35 fan-facing systems onto Salesforce. The harder work is the one Rob Pickering names in passing: identity across touch points.

SAP says Colombina migrated all 16 countries it operates in to S/4HANA Cloud Private Edition at once, skipping the phased waves most programmes plan for.

Microsoft says Server Logic in Power Pages can now invoke Power Automate cloud flows, which puts an externally facing form in front of 1,400 connectors.

Dynamics 365 Activate profiles a company's whole Salesforce data set before migration starts, already at billions of records. That access needs scrutiny.

ServiceNow's MCP servers keep ACL and role enforcement in place, so what an agent can do is decided by the role model your instance already has.

SAP put drones and humanoids on Joule at its first Embodied AI Jam. Our read: every use case rests on an equipment or routing record a person keeps accurate.

SAP's Embodied AI Jam sent teams home with use cases and architectural proposals. Here is the five-part test that separates a robot demo from a process.

SAP's Embodied AI Jam listed warehouse automation without naming a system. Here is the task data, write-back, and exception path a floor team needs first.

Salesforce in Claude ships 37 prebuilt sales skills. Each one encodes a definition of deal health and pipeline review that your org may not share.

Salesforce says an admin connects Salesforce in Claude once and permissions are managed centrally. Whose identity each action runs under is the question to ask.

Salesforce in Claude reads CRM and Slack data through one admin connection. Governing the writes, where business rules and side effects live, is the hard part.

Salesforce says Claudeforce routes actions through its rules. Here is what the trust boundary must still carry when a seller never opens Salesforce.

Salesforce says Claudeforce moves from select pilots to open beta in September 2026. What a Salesforce team should settle before sellers connect Claude to CRM.

SAP integration moves business documents, not rows. Which patterns hold up over years, which quietly become somebody's problem, and what to check first.

An integration belongs to neither system team, so it goes unowned. What the owner role really involves, and why it is a stronger career position than it looks.

The choice between a configured integration and a script gets settled by who is free that week, and your entitlement decides more of it than anyone admits.

Effective dating separates the Workday integrations that still hold up in year five from the ones that went quietly wrong and told nobody.

Employee Central owns the person and S/4HANA owns the identity you post against. The replication between them is where the money quietly leaks.

Extend earns its place when the app sits on Workday objects and inherits tenant security. Orchestrating outside systems is a different job.

The two products share most of their design. The real choice is who owns the thing in two years, which budget pays, and who gets paged at 2am.

Most integrations handle success and failure and nothing between them. The partial load, the business rejection and the empty run are the ones that hurt.

Integration accounts miss every joiner and leaver process. Give each one a named owner, a readable name, narrow scopes and a rehearsed rotation.

The same validation in the form, the flow and the ERP is a tradeoff nobody wrote down. Pick the layer by who must never be able to break the rule.

A connector gets a record from one system to another. An integration owns what happens when the record gets rejected, and most sync projects fail without that part.

Before a Power Platform or SAP roadmap gets sequenced, list every flow it touches with a source of record, a consumer, and the person who fixes exceptions.

Sales and service can keep their own screens. They have to share the customer identifier, the lifecycle states, the conflict rule, and the correction path.

A queue between Power Automate and Oracle Fusion guarantees delivery. Someone still has to decide what a duplicate, stale request, or rejected record means.

The parallel runs, per-element tolerances, and sign-offs that decide whether a Workday or Oracle HCM payroll go-live is safe, and who should own each one.

A Power Automate flow can report success on a Workday employee event while the team that gets the ticket cannot see what arrived or how to correct it.

Decide what moves before you touch a mapping rule, read the merge output yourself, and verify against totals the business already argues about.

Integration Center handles a scheduled extract well. The entity you pick, the as of date and the failure email decide whether anyone can trust the file.

Most mock loads are built to pass. A rehearsal proves something only at full volume, on the real cutover clock, with the awkward records left in.

SAP BTP is one name over four different things: extension runtimes, integration, data services and AI. Knowing which one you mean is most of the answer.

A reorg breaks employee feeds that were built against last year's org chart. Pick keys and reconciliation that outlive the chart.

Name the business event, send only fields the receiver acts on, version when meaning changes, and write down what happens to duplicates.

Match on the number the business already reads out, enforce it as a unique field on both sides, and test the missing, repeated, and near-twin key first.