Data Insight User Guides
Dynamic Data Replicator – Complete Functionality Overview
Dynamic Data Replicator (DDR) is an enterprise SAP data management platform for controlled SAP refresh, shell build, system build, client build, selective replication, object refresh, full system copy, scrambling, backup recovery, monitoring, utilities, and operational governance. DDR helps customers reduce dependency on repeated full copies by allowing technical and functional teams to define exactly what should be copied, how it should be filtered, where it should be loaded, how sensitive data should be protected, and how runtime execution should be controlled from the Central Console.
Process Applications
DDR process applications provide the operating model for connection management, replication design, build execution, refresh execution, monitoring, and operational control.
DDR Connection Application
The DDR Connection Application registers and manages Source and Target SAP systems from the DDR Central Console. It provides the technical foundation for all replication, export, import, simulation, monitoring, shell build, and refresh activities.
Administrators create meaningful connection names so users can identify the SAP systems and clients involved in replication activity. This reduces confusion in multi-system landscapes and supports governed execution.
Technical Capability
- Defines central to source and central to target relationships.
- Supports RFC based communication and logical system mapping.
- Supports reusable connection naming for functional and technical users.
- Provides the connection foundation for templates, monitoring, simulation, export, import, and runtime processing.
Centralised connection management improves governance, reduces operational mistakes, and allows multiple SAP landscapes to be controlled from one DDR Central Console.
DDR Template Application
The DDR Template Application is the design layer for replication. A template defines the business, technical, security, and runtime scope of the refresh before data is exported or imported.
Templates include Source system, Target system, business objects, filter conditions, scrambling options, runtime settings, and import or export controls. Templates are reusable and can also be exported and imported.
| Template Component | Purpose |
|---|---|
| Source and Target | Defines where data is read from and where it is loaded. |
| Business Objects | Defines the SAP master data, transaction data, or custom object scope. |
| Filter Conditions | Supports dates, object keys, company code, plant, customer, vendor, material, and custom logic. |
| Scrambling Options | Defines how sensitive data is secured during or after replication. |
| Reusable Execution | Allows repeatable, auditable and governed execution. |
Templates reduce manual configuration, improve consistency, and give customers a repeatable and auditable replication model.
DDR Shell Build
DDR Shell Build creates lightweight SAP shell environments by exporting repository objects, system table data, and configuration related information without copying Production master or transactional application data.
This is useful where customers need a clean SAP system structure that mirrors Production configuration but does not require business application data. It can support sandbox creation, training environments, project systems, proof of concept systems, or target preparation before selective data loading.
Technical Overview
DDR Shell Build supports SAP system build activities by generating export content that can assist system creation using SAP Software Provisioning Manager processes. The target shell contains the required repository and system configuration information while excluding application data volume.
Repository and Configuration Focus
Transfers system structure, repository objects and technical configuration rather than full business transactional data.
Smaller System Footprint
Reduces storage, infrastructure cost, and provisioning time by excluding master and transactional application data.
Faster Provisioning
Supports faster preparation of non-production shells compared with full Production copies.
Controlled Build Process
Provides a governed DDR driven process for shell system export and preparation.
DDR System Build
DDR System Build helps SAP customers build new Test, Training, Sandbox or Project systems with Production aligned configuration and controlled system data.
This application reduces effort when preparing lower SAP environments and can be combined with shell build, client build, selective data refresh, object refresh, and scrambling strategies.
Technical and Operational Value
- Supports creation of lower SAP systems using Production aligned configuration.
- Helps establish project, training, support, and testing environments.
- Reduces unnecessary full Production data volume where a lighter system is sufficient.
- Provides a structured build path before selective master or transaction data loading.
Enables SAP teams to create useful non-production environments with better control, lower storage impact, and stronger alignment to project requirements.
DDR Client Build
DDR Client Build helps customers create a new SAP client in a Test or lower environment. It is designed for scenarios where customers need a new client that is similar to Production from a configuration and user master perspective.
The application can use standard SAP profile SAP_UCSV for building the client with Customising and User Master records. This provides a controlled baseline before selective data refresh or additional replication activities are executed.
Use Cases
- Create a new client for testing, training, or project validation.
- Prepare a lower client before loading selected master or transaction data.
- Support phased SAP refresh activities where configuration is required before application data load.
Provides structured client creation that can be combined with selective refresh, object refresh, data scrambling, and monitoring.
Data Deletion Based on Time, Object and Technical Criteria
DDR Data Deletion allows administrators to delete selected SAP data from lower environments using time-based, object-based, or technical criteria. This supports housekeeping after refresh cycles, test data cleanup, failed load recovery, repeated data preparation, or non-production storage reduction.
Data deletion must be controlled because SAP records are connected through business object relationships and technical dependencies. DDR provides a governed method to identify deletion scope and reduce inconsistent cleanup.
Technical Description
- Time-based deletion where records are removed according to date ranges.
- Object-based deletion for selected business objects or transaction groups.
- Technical cleanup where specific tables or generated datasets need to be removed.
- Removal of previous test data before a new refresh or replication run.
- Reduction of non-production database growth.
Deletion activities should be planned and validated before execution. Use clear scope, correct filters and appropriate approval because deleted data may not be recoverable unless backup or restore points exist.
Utility and Technical Control Applications
DDR utilities support post-refresh correction, number range handling, housekeeping, exclusions, custom relationships, and operational maintenance.
DDR Utility Application
The Utility section contains supporting tools required during or after SAP data refresh activities. These tools help administrators manage post-refresh correction, operational controls, runtime maintenance, and technical system adjustments.
At present, DDR includes number range buffer utility capability which helps extend or adjust number ranges in the target system once refresh activity is completed.
Reduces post-refresh manual effort and supports controlled correction of technical SAP settings after data movement.
Business Object Builder for Custom Table Relationships
DDR Business Object Builder allows technical teams to define custom business objects and custom table relationship models for customer-specific SAP developments.
Many SAP customers use Z tables, industry add-ons, custom modules, third-party namespaces, and bespoke process tables. DDR Business Object Builder allows these structures to be included in governed refresh processing by defining parent-child relationships and key dependencies.
Technical Capability
- Define custom parent and child table relationships.
- Map custom keys and dependency fields.
- Build reusable custom business objects for replication.
- Support bespoke modules and non-standard SAP processes.
- Improve consistency when copying custom SAP data footprints.
Allows DDR to support customer-specific SAP extensions instead of only standard SAP objects, making the refresh process more complete and business relevant.
Technical Table Exclusion
Technical Table Exclusion allows administrators to exclude specific SAP tables from export, import, refresh, deletion, or replication processing.
This is important where certain tables must remain target specific or where customers do not want logs, temporary tables, audit records, generated files, interface queues, or environment-specific settings to be overwritten.
Technical Use Cases
- Exclude environment-specific configuration tables.
- Exclude technical logs or temporary processing tables.
- Exclude custom tables that should not be copied from Production.
- Protect target-specific entries from being overwritten.
- Reduce export and import volume by excluding unnecessary tables.
Protects system-specific target data, reduces unwanted data movement, and improves refresh safety.
Number Range Management
DDR Number Range Management helps customers manage and extend number ranges in the target system after refresh or replication activity is completed.
This is important because refreshed data can create number range conflicts if the lower environment continues to create new documents after receiving copied Production data.
Technical Description
- Helps align number range buffers after replication.
- Reduces duplicate document number risks.
- Supports post-refresh operational readiness.
- Helps lower environments continue testing without number range conflicts.
Reduces post-refresh failures caused by exhausted, duplicated, or misaligned SAP number ranges.
DDR House Keeping
DDR House Keeping supports cleanup and maintenance of operational artefacts, logs, temporary data, generated files, historical processing records, and runtime outputs.
Refresh and replication activities can generate logs, exports, backup files, monitoring records, and operational metadata. House Keeping helps manage this growth and keeps the DDR environment cleaner and easier to support.
Operational Benefits
- Reduces unnecessary storage growth.
- Removes outdated runtime artefacts.
- Supports controlled retention of DDR logs.
- Helps technical teams maintain a stable DDR environment.
Data Security and Compliance Applications
DDR security functions help protect sensitive SAP data when Production data is moved into non-production systems.
DDR Data Scrambling
DDR Data Scrambling protects sensitive SAP data during refresh and replication. It helps reduce the risk of exposing Production-sensitive data in test, training, sandbox, project, or support systems.
Scrambling rules can be configured based on customer compliance requirements, internal policies, and data protection standards.
Scramble at Source
The most secure option. Sensitive data is scrambled during export before it leaves the Source system.
Scramble at Target
Sensitive data is scrambled after import into the target non-production environment.
Technical Capability
- Configurable field-level scrambling rules.
- Can be applied to master data, transaction data, and custom tables.
- Supports repeatable scrambling logic for consistent testing.
- Helps preserve data usability while masking sensitive values.
- Supports GDPR and internal data security requirements.
Enables realistic testing with protected data and reduces compliance risk in non-production environments.
Refresh and Replication Applications
DDR refresh applications replicate full systems, selected time windows, specific business objects, or file-based datasets based on project and testing needs.
Data Refresh – Time-Based Application
The Time-Based Application allows SAP administrators to replicate data for a specified date or time range. Users can define date filters and extract only relevant Production data into non-production environments.
For a selected time range, required business objects can be filtered and selected, reducing total data volume and improving runtime.
Technical Benefits
- Reduces export and import volume.
- Improves runtime by limiting replication to a selected time window.
- Supports projects and tests requiring recent business transactions.
- Reduces non-production database growth.
Instead of copying years of Production data, customers can refresh only the time period required for testing or validation.
Object-Based Application
DDR Object-Based Application allows business users and administrators to replicate specific transaction data or master data into lower environments from Production.
This is useful when a Production issue needs to be reproduced in a lower system without refreshing the entire client or system.
Use Cases
- Replicate a specific customer, vendor, material, sales order, purchase order, invoice, or business object.
- Reproduce Production defects in test systems.
- Support functional testing with realistic object data.
- Reduce effort compared with full system refreshes.
Provides targeted replication for functional teams and avoids unnecessary full-system data movement.
System Refresh – Full System Copy
DDR Full System Copy Application is used by administrators to copy or replicate an entire Production environment into a non-production environment.
This functionality is suitable where a complete Production-like dataset is required for testing, performance validation, training, project simulation, or operational readiness.
Operational Value
- Supports full environment replication where selective copy is not sufficient.
- Provides Production-like data volume for complete test scenarios.
- Can be combined with scrambling to protect sensitive data.
- Supports full refresh governance through monitoring and runtime controls.
DDR Data Replication / Export Application
DDR Data Replication and Export Application executes replication activities defined by administrators and functional users in templates.
This is the operational runtime application used to trigger data export, replication, pause and resume, file export, file import, simulation, and monitoring driven processes.
Technical Runtime Control
- Triggers data export and replication jobs.
- Supports pause and resume of replication activity.
- Works with runtime parameters such as package size, batch size, and workprocess allocation.
- Integrates with monitoring, notification, simulation, and error log functions.
- Supports controlled execution of template-defined replication logic.
Provides the controlled execution engine for DDR, allowing customers to run governed SAP data refreshes with operational visibility and runtime flexibility.
Monitoring and Operational Control
DDR monitoring functions provide runtime visibility, execution tracking, source and target status, and operational logs for support and governance.
DDR Monitoring Application
DDR Monitoring helps users track the replication process and provides detailed logs of replication activity. Source system and Target system activities are shown separately to make issue identification easier.
Users can view runtime information, status indicators, percentage completion, table progress, and runtime messages.
Monitoring Benefits
- Provides source and target progress visibility.
- Helps identify where a replication process is delayed or failed.
- Supports technical runtime logs for support teams.
- Improves governance of long-running refresh activities.
- Provides visibility into percentage completed and execution status.
Helps users monitor DDR execution from a single screen and quickly identify whether issues are occurring on the Source system, Target system, or within replication processing.