Data Insight User Guides
Execute Refresh On Demand – Step-by-Step User Guide
Execute On Demand allows authorised users to start a DDR replication process immediately from the Dashboard without waiting for a scheduled job window. It is used when a refresh, object copy, or selected replication needs to be triggered straight away for testing, validation, support, or urgent non-production data readiness.
Purpose of Execute On Demand
The Execute On Demand function is designed for situations where a replication run must be started manually and immediately. Instead of waiting for a scheduled export time, the user selects the required Template ID from the DDR Dashboard and clicks Execute to start the process.
This is useful for urgent test data refreshes, validating newly created templates, repeating a controlled data copy, supporting defects that require refreshed data, or running a replication after changes have been made to source selection criteria, dependencies, run parameters, or target preparation.
Key point: Execute On Demand does not replace scheduled automation. It gives the operations or project team a controlled manual execution option when the replication must run immediately.
Open Dynamic Data Replicator
Log in to the DDR Central Console and confirm that the required menu options are available. The Dashboard menu is used to monitor and execute replication activities across the SAP source and target systems.
Go to the DDR Dashboard
From the main menu, select Dashboard. The Dashboard shows the available replication entries and their operational details, including template name, export ID, run ID, source logical system, target logical system, execution status, creation details, and messages.
The Dashboard also displays source and target progress panels, table category counts, database size, workprocess usage, package size, estimated completion values, and run status indicators.
Select the Required Template ID
Locate the required Template ID in the Dashboard list and select it by clicking the radio button on the left-hand side of the row. The selected row determines which replication definition will be executed.
Before clicking Execute, confirm that the selected row is correct. Check the Template Name, Export ID, Run ID, source logical system, target logical system, mode of execution, and any displayed message field.
Important: Always confirm that the selected template points to the correct source and target system. Execute On Demand starts a live replication run based on the selected Dashboard record.
Click Execute to Start the Run
After selecting the correct Template ID, click the Execute button from the Dashboard toolbar. DDR starts the selected replication process on demand using the configured template, connection, package size, workprocess settings, and run parameters.
Monitor Source and Target Execution Status
Once the run starts, monitor the progress directly from the Dashboard. DDR displays source and target progress bars, completed and remaining work, table category information, record counts, database size values, selected workprocesses, package size, and workprocess status.
This gives the user immediate visibility of whether the replication is progressing correctly and whether the source and target processing is balanced.
Technical Behaviour
| Area | Technical Detail |
|---|---|
| Template selection | The selected Dashboard row controls the Template ID, Export ID, Run ID, source logical system, target logical system, and execution context. |
| Manual trigger | The Execute button triggers the replication immediately rather than relying on a future schedule. |
| Runtime control | Execution uses the configured DDR run parameters, including package size, workprocess allocation, and template-level selection rules. |
| Operational visibility | Progress can be reviewed through source and target status panels, table counts, DB size, estimated completion information, and workprocess status. |
| Support traceability | The run can be reviewed through Dashboard status, reports, error logs, and execution messages. |
Advantages and Business Benefits
Teams can refresh selected data immediately when testing or support activity requires it.
Users do not need to wait for the next scheduled run when an urgent replication is required.
The run is still governed by the selected DDR template, connection, system mapping, and run parameters.
Support teams can repeat or trigger a controlled run when investigating a defect, missing data issue, or failed test cycle.
Execution remains visible in DDR for reporting, monitoring, audit review, and operational control.
Project teams can combine scheduled runs for routine activity with on demand runs for exceptional or urgent scenarios.
Recommended Checks Before Execution
- Confirm the correct Template ID has been selected.
- Confirm the source and target logical systems are correct.
- Review the Export ID and Run ID before triggering the run.
- Check that the target system is ready to receive the replicated data.
- Review the package size and workprocess allocation where performance management is required.
- Use the Dashboard, Report, and Error Log options after execution to confirm the outcome.