Data Refresh Operator
Implementation and operations: in weeks, not months
DRO is designed to be implemented quickly and run by your own team. Setup takes place centrally – not in each system separately.
How the implementation works
Demo
We show you DRO using your own use cases and discuss how you can get to know DRO in your landscape.
Basic setup
Source and target systems are registered in the control system. Provided the relevant contacts are available, this is technically in place within a day.
Integrate your own objects
Customer-specific tables and dependencies are added to the business object model – in the system or via JSON import.
Onboarding & first runs
The people involved are given an introduction, followed by the first test runs.
In-house operation
You carry out client copies yourself. Our support is on hand, and if you wish, we take over operations.
How long the implementation takes overall depends mainly on how quickly internal contacts are available and how many customer-specific tables are included. We expect a few weeks rather than months.
Set up centrally, controlled centrally
Setup is carried out via the DRO control system. From there, the connected SAP systems are registered and, later on, all client copies are controlled. There is no need to configure each system extensively or to assign numerous authorisations there.
Global settings apply to all systems; where necessary, system-specific settings override them. You maintain export templates, exception lists, verification clients and distribution groups for notifications on start, completion and errors in one place.
Integrating customer-specific tables
DRO can include Z tables and enhancements at any time. You define your own business objects or extend existing ones with additional tables and dependencies – and specify exactly when which data is copied along with them.
An example: if a Z table depends functionally on a standard table, you store this relationship in the model. The data is then only copied if the associated data of the parent object is copied as well.
Maintenance takes place directly in the system or via a documented JSON import. This means that even larger enhancements can be prepared quickly – based on the documented structure, also with the help of AI tools.
Open model. Business objects, tables and dependencies are fully visible in DRO and are not a trade secret. You can see at any time why a table is copied, which object it belongs to and which dependencies lie behind it.
Operations and support
- In-house operation
- After handover and onboarding, your team carries out and manages client copies independently.
- Support
- As standard, with a response time of up to eight hours. We agree stricter SLAs individually.
- Operation by Velvet Mind
- If you wish, we take over operations or individual operational tasks – as part of our managed services.
Working with existing tools
Tools for system copies remain as they are. For client copies, DRO is intended as a replacement: DRO handles control and execution itself.
After a migration to S/4HANA (from release 2023) – whichever tool was used – nothing stands in the way of DRO. Wherever an SAP client copy is technically and functionally possible, DRO can also be used.
Get to know DRO.
In a free demo, we show you DRO live using your own use cases – remotely and with no obligation. We discuss where the benefits lie for memory, refresh time and operating costs, and how you can try DRO in your own landscape.
- Benefits specific to your use cases
- A live look at time slice, dependency resolution, export and import
- Answers directly from the team behind DRO