Oracle keeps Premier Support for E-Business Suite through at least 2037, so there is no forced date; the pull is the move to Fusion, where customer data sits in CX, product data in SCM and hierarchies in Enterprise Data Management, each priced by its own metric.
| Oracle hubs | Lima master data |
|---|---|
| TCA party and account | customer and business-contact domains |
| PIM item and catalog | material and product-classification domains |
| DRM hierarchy version | versioned hierarchy with validity; DRM validations as rules |
| Open interface | write-back through public APIs and interfaces; read through JDBC |
| Responsibility | the twelve security layers |
| DRM transaction history | the audit trail |
An industrial group with EBS and DRM for cost-centre and account hierarchies moved DRM first: 14 hierarchies with 3 years of versions loaded as versioned hierarchies; the validations became rules; the EBS GL and a planning tool received the golden hierarchies through the write path. The Fusion project later read the same golden hierarchies into Enterprise Data Management's subscribers.
They move behind a router one at a time: SOAP consumers get a generated WSDL, SQL readers get views with the same names, API consumers get REST with the same shapes.
Yes, read-only, for as long as your retention policy needs; its history is already searchable in Lima.
The inventory: the count of domains, sources, rules, hierarchies and consumers, written before the work starts.
Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.
