Data Insight User Guides
DDR Run Parameters – Runtime Execution & Performance Control Guide
DDR Run Parameters is one of the most important operational functionalities within Dynamic Data Replicator.
The Run Parameters functionality provides full runtime control over package sizing, batch processing,
and workprocess allocation for both source and target SAP systems before and during replication execution.
This functionality allows SAP administrators and operational teams to optimise runtime performance,
control workload allocation, improve execution scalability, and manage replication throughput for large SAP datasets.
Run Parameters must be configured before every replication execution. Users are required to select
the required export template and assign the appropriate runtime execution parameters before triggering the refresh.
Purpose of DDR Run Parameters
DDR Run Parameters are designed to provide operational runtime control during SAP replication activities. The functionality allows administrators to optimise replication execution based on infrastructure capacity, database performance, runtime workload, and operational execution requirements.
- Package size management
- Batch processing control
- Source workprocess allocation
- Target workprocess allocation
- Runtime workload optimisation
- Execution scalability management
- Runtime performance tuning
This functionality is especially important for large enterprise SAP landscapes where execution performance, database throughput, and runtime optimisation are critical to successful replication execution.
Select Export Template from Dashboard
From the DDR Central Console, select Dashboard from the left navigation panel. Users must first select the required export template by clicking the radio button before the template name.
Once the export template is selected, click the Run Parameters button from the top execution toolbar.
Configure Runtime Execution Parameters
After selecting Run Parameters, DDR opens the runtime configuration popup where administrators can assign runtime execution parameters before replication begins.
The runtime configuration allows full control over package sizing, batch processing, and workprocess allocation across both source and target systems.
| Field | Description |
|---|---|
| New Package Size | Defines the number of records processed within each execution package during runtime processing. |
| New Batch Size | Defines the batch processing size used during replication execution activities. |
| Source Workprocess | Defines the number of source SAP workprocesses allocated for runtime extraction activities. |
| Target Workprocess | Defines the number of target SAP workprocesses allocated for runtime loading activities. |
| Transfer | Saves and applies the configured runtime execution parameters. |
Runtime Monitoring & Performance Visibility
Once the runtime parameters are configured and execution begins, DDR provides visibility into runtime workload, estimated completion time, package sizing, workprocess allocation, database sizing, table counts, and execution status directly from the Dashboard.
This enables operational teams to monitor execution behaviour and validate runtime optimisation during replication processing.
Key Benefits of DDR Run Parameters
DDR Run Parameters provide complete runtime execution control and operational flexibility across SAP replication activities.
DDR Runtime Configuration Best Practices
To achieve stable runtime execution, optimal replication performance, and controlled workload distribution, Enterprise Data Insight recommends following the below runtime parameter best practices during SAP replication execution activities.
| Configuration Area | Recommended Best Practice |
|---|---|
| Source Workprocess Allocation | A minimum of 1 source workprocess is required during replication execution. Additional source workprocesses can be allocated depending on infrastructure capacity and workload requirements. |
| Target Workprocess Allocation | A minimum of 4 target workprocesses is recommended to support stable runtime loading and improve replication throughput. Additional workprocesses may be allocated depending on target system performance and infrastructure sizing. |
| Recommended Package Size | Enterprise Data Insight recommends starting with a 20,000 package size for most replication activities. This provides strong runtime performance and balanced workload distribution for large SAP datasets. |
| Memory Management Considerations | Package sizing should be adjusted based on available SAP memory allocation and runtime workload behaviour. In environments where memory pressure or runtime dumps occur, it is recommended to gradually reduce the package size from 20,000 to 15,000 or lower. Runtime optimisation may require controlled trial-and-error tuning depending on the SAP landscape and dataset size. |
| Recommended Batch Size | Enterprise Data Insight recommends a default 10,000 batch size for most enterprise replication activities. |
| Batch Size Performance Optimisation | In environments where runtime bottlenecks or memory pressure are identified, reducing the batch size to 5,000 has shown strong performance improvements and improved runtime stability across large enterprise refreshes. |
Runtime parameter optimisation should always be aligned with SAP infrastructure sizing, database performance, available memory allocation, workload distribution, and operational execution requirements.
DDR provides the flexibility to adjust runtime behaviour dynamically, allowing organisations to optimise replication performance based on real-time operational conditions.