Data Insight User Guides
Object Refresh – End-to-End Step-by-Step User Guide
This locked guide explains how to create a DDR Object Refresh template from start to finish, including source and target connection selection, business object selection, custom table inclusion, advanced filtering, table exclusion, data scrambling, template locking, and preparation for execution. Object Refresh uses the same controlled DDR wizard approach as Data Refresh, but without the Date Selection step.
Purpose of Object Refresh
DDR Object Refresh allows SAP teams to copy a selected business object or process object from a source SAP system to a target SAP system without performing a full system copy. This is useful when a test team needs a controlled set of master data, transactional object data, custom table data, or dependency data for a specific business scenario.
The key difference between Object Refresh and Data Refresh is simple: Object Refresh does not ask for From Date or To Date. The data scope is instead controlled by the selected business object and the filters applied during configuration.
Important: Use Object Refresh when the refresh requirement is object-driven rather than time-driven. Use Data Refresh when the refresh must be restricted by a date range.
Access Object Refresh from the DDR Central Console
From the DDR Central Console, select Object Refresh from the left-hand menu. This opens the object-based refresh wizard. The Object Refresh button is highlighted using a zoom callout so users can clearly identify the correct menu option and avoid selecting Data Refresh by mistake.
Use the left-hand navigation and select Object Refresh. This opens the Object Refresh wizard where a controlled object-based refresh template can be created.
Select the Template Type
DDR provides multiple template options. For a new object refresh, select Custom Template and then choose Blank Template when you want to create the configuration from the beginning.
Use where a predefined object refresh pattern already exists.
Use where the user needs to control objects, filters, tables, and exclusions.
Use where an existing template is close to the required configuration.
Select the required template type. For a controlled object refresh, choose a Custom Template and then use a Blank Template or copy an existing template when required.
Enter Template Name, Transfer Type, and Connection
Enter a clear template name that explains the purpose of the object refresh. Then select the correct transfer type and configured connection. For RFC-based refreshes, the selected connection must point to the correct source and target SAP clients.
- Template Name: Use a meaningful name, such as FI Object Refresh, Material Master Refresh, or Customer Test Data Refresh.
- Transfer Type: Choose the required mode, such as RFC based, file based, or webservice based.
- Connection: Select the approved source-to-target connection.
Enter a meaningful template name, select the correct transfer type, and choose the configured connection between the source and target SAP systems.
Select Business Object Group – Master Data
Open the Business Object Group section and select Master Data when the object refresh needs to copy reusable business records. This may include material, customer, vendor, accounting, or other master data objects depending on your DDR configuration.
Master Data selection is useful when the target system requires specific object records but does not need a full transactional dataset.
Select Master Data when the refresh requirement is focused on master records such as accounting document master objects, materials, customers, vendors, or other reusable business objects.
Select Business Object Group – Process
Select Process when the refresh needs to follow a process-oriented object grouping. DDR then displays process-related objects available for selection. This helps users build refresh templates around functional scenarios and process flows.
Select Process when the refresh requirement is process or object-flow driven. This allows DDR to display process-related business objects for selection.
Select Transactional Business Object and Include
Select the required transactional business object from the list and click Include. Once included, the object appears in the selected business objects table. This confirms that the object is part of the refresh scope.
The selected business object controls the main data set DDR will copy. Any related tables, dependencies, filters, and exclusions are then applied against this selected object.
Choose the required transactional business object and click Include. The selected object moves into the selected business objects area and becomes part of the refresh template.
Add Additional Tables and Relationship Mapping
Use Additional Tables when the object refresh must include customer-specific tables, enhancement tables, Z tables, Y tables, or other related tables that are not part of the standard object definition.
Additional tables can be added directly by table name or through a relationship mapping. Relationship mapping allows DDR to understand how the included table connects to the parent object, helping to keep the copied data consistent.
Use Additional Tables to include customer-specific tables, Z tables, Y tables, or relationship-based tables that are not automatically included in the standard object definition.
Open the Object Filter Section
Open Object Filter when the object refresh needs to be restricted by field-level values. Filters are used to control exactly which records are copied to the target system.
Common filters include document number, company code, fiscal year, plant, material, customer, vendor, document type, or other fields available for the selected object.
Open the Object Filter section when the selected object needs field-level restriction. This is where users can control the exact records that should be copied.
Select Filtering Fields and Create Filter
Click Add Filters and select the required filtering fields. The screenshot shows key fields such as document number, company code, and fiscal year. Select the fields required for the object refresh, click Include, and then click Create Filter.
Creating the filter prepares the selected fields for value entry. This is where the user defines what should be included or excluded from the object refresh.
Select key fields or other available fields such as document number, company code, and fiscal year. Click Include and then Create Filter to build the filter structure.
Use Advanced Multiple Selection to Add More Filter Line Items
The advanced multiple selection option allows the user to add more line items against the same field. This is useful when several values or ranges must be entered for a single object refresh filter.
Users can add, remove, and maintain multiple selection rows before confirming the filter values. This gives the template owner more granular control over the refresh scope.
Use the advanced multiple selection screen to add extra line items. This allows several values, ranges, or conditions to be maintained against the same filter field.
Select Values to Include in Data Replication
Use the Select tab to define the values that must be included as part of the object refresh. These values are included in the replication selection and copied to the target system where they match the configured object and table rules.
- Single Value: Include one exact value.
- Greater Than or Equal To: Include values from a starting point.
- Less Than or Equal To: Include values up to an ending point.
- Interval: Include a range between two values.
Use the Select tab to define values that must be included in the object refresh. These values become part of the replication selection logic.
Exclude Values Not Required for Replication
Use the Exclude from Selection tab to define values that must not be copied. This is useful where certain records should be avoided because they are not needed for the test scenario, are too sensitive, or must not overwrite existing target data.
Exclusion rules help reduce unnecessary data movement and protect target-side records from being overwritten by unwanted source records.
Use the Exclude from Selection tab to define values that must not be copied. This helps avoid overwriting unwanted records or moving unnecessary data.
Maintain the Table Exclusion List
Open Exclude Table to prevent specific tables from being copied as part of the object refresh. This can be used for technical tables, large tables, sensitive tables, or tables that are not required in the target environment.
If a table exclusion file is used, upload it and preview the exclusion list before finalising the template. Review the list carefully because excluded tables will not be copied even if they are part of the selected object or additional table configuration.
Use the Table Exclusion section to exclude technical, large, sensitive, or unwanted tables from the object refresh scope.
Data Scrambling
After completing the table exclusion step, click Next to proceed to Data Scrambling. Data Scrambling protects personal, confidential, commercial, and regulated information before it is made available in a non-production system.
14.1 Select Scrambling Mode
DDR allows the user to choose how scrambling should be applied. The available options include None, Scramble at Source, and Scramble at Target.
No scrambling is applied during the refresh.
Sensitive data is scrambled before it leaves the source system.
Data is scrambled on the target system before or during target-side replication processing.
Select whether scrambling should be skipped, applied at source, or applied at target.
14.2 Include Scrambling Policy
After selecting the scrambling mode, choose the required scrambling policy. Policies can be selected from the available pattern list and then included in the selected pattern list. In the example shown, fixed text scrambling policies are selected and shown in the preview panel.
Scrambling policies can be designed for common sensitive fields such as names, addresses, bank details, email addresses, telephone numbers, employee details, customer data, vendor data, or other sensitive business fields.
Choose the required scrambling policy from available patterns and include it in the selected patterns list.
14.3 Security Guidance
Scrambling should be used whenever sensitive data is copied into non-production systems. This helps reduce exposure of personal, confidential, commercial, and regulated data during testing, training, support, and project activities.
Reference: For detailed scrambling configuration, refer to the Data Scrambling User Guide.
Data Replicator Button and Template Lock
Once the Object Refresh template has been reviewed, click the Data Replicator button to finalise and release the template for replication.
DDR displays a confirmation message before release. Select Yes only when the configuration has been fully checked. Released templates are locked and cannot be modified, which protects the approved refresh design from accidental change.
Confirm and release the object refresh template. Once released, the template is locked and cannot be modified.
Review and Lock the Object Refresh Template
Before releasing the template, review the full configuration. Confirm the template name, transfer type, connection, selected business object group, selected business object, additional tables, object filters, include values, exclude values, table exclusions, scrambling mode, selected scrambling policy, and template lock confirmation.
Once the configuration is correct, proceed to the Data Replicator release step. Released templates should be treated as locked so the approved configuration cannot be changed accidentally before execution.
Object Refresh Summary
DDR Object Refresh provides a controlled way to copy selected SAP business object data from source to target without using a date selection. The refresh is driven by object selection, additional table handling, filter fields, include and exclude logic, table exclusions, and release control.
Reminder: Object Refresh is object-driven. Do not add a Date Selection step to this guide.