DDR – Client Build Export

This guide explains how to use the Client Build functionality within the Dynamic Data Replicator (DDR) Shell Build application. It covers the process of creating new SAP clients using client export, local client copy, and remote client copy methods. The guide also provides a detailed overview of SAP client copy profiles and how they control the scope of data transferred, helping users create production-like environments for testing, training, and development.

DDR Shell Build Guide

Client Build Application

The Dynamic Data Replicator (DDR) Client Build application helps SAP customers create new clients within test or lower environments that closely resemble the production client. Using the Client Build functionality, administrators can create a new client through supported SAP client copy methods, including client export, local client copy, and remote client copy.

For client export scenarios, DDR supports transport-based export from the source system and import into the target system. This allows system teams to create production-like clients while controlling the scope of copied data through standard SAP client copy profiles such as SAP_UCSV, SAP_CUST, SAP_USER, and other supported profiles.

Step 1: Access the Shell Build Application

DDR Shell Build screen with New button highlighted

Navigate to the Central Admin Console, select Shell, then click New to start a new Shell Build activity.

Step 2: Choose Client Build

DDR Shell Build popup showing Client Build System Build and Data Deletion options

From the Shell Build popup, select Client Build and click Create.

Client Build Options in DDR

DDR Client Build supports three client build methods:

1. Client Export

Creates a transport-based client export from the source system. The generated transport is then imported into the target system.

2. Local Client Copy

Copies client data within the same SAP system from one client to another, based on the selected SAP profile.

3. Remote Client Copy

Copies client data from a remote SAP system using RFC communication and the selected client copy profile.

Step 3: Select Client Export

DDR Client Build screen showing Client Build Type dropdown

Select the required Connection, then choose Client Export as the Client Build Type.

Step 4: Select Target Client and System Profile

Enter the Target System ID and select the correct System Profile based on the required client build scope.

Client Export Configuration Fields

Connection

Select the DDR connection that defines the source and target system route for the client build.

Client Build Type

Select Client Export when the build should be generated as a transport export from the source system.

Target System ID

Enter the target client number that will receive the exported client data after import.

System Profile

Select the SAP client copy profile that controls which data is exported and copied.

SAP Client Copy Profiles Explained

Profile	Meaning	What it copies	Typical use
SAP_ALL	All client-specific data without change documents	Customising, user master, application data, master data, and transactional data, excluding change documents.	Full client copy where most client data is required.
SAP_APPL	Customising and application data without change documents	Customising plus business application data, excluding change documents.	Functional test clients where application data is needed but change history is not required.
SAP_APPX	SAP_APPL without authorisation profiles and roles	Customising and application data, excluding authorisation profiles and roles.	Application copy where target authorisations must remain controlled separately.
SAP_CUST	Customising	Client-dependent configuration and customising settings only.	Shell build or configuration-only clients without application data.
SAP_CUSV	Customising and user variants	Customising settings and user variants.	Configuration client where user variants are also required.
SAP_CUSX	Customising without authorisation profiles and roles	Customising only, excluding authorisation profiles and roles.	Configuration refresh where target authorisation design must be preserved.
SAP_PROF	Only authorisation profiles and roles	Roles, profiles, and authorisation-related objects.	Security or role alignment between clients.
SAP_UCSV	Customising, user master records, and user variants	Customising settings, user master data, and user variants.	Production-like lower environment clients without full application transaction data.
SAP_UCUS	Customising and user master records	Customising and user master records, excluding user variants.	Client setup where users are required but variants are not needed.
SAP_UONL	User without authorisation profiles and roles	User master records without associated authorisation profiles and roles.	User copy where roles and profiles should be maintained separately in the target.

Important Guidance

For a lightweight shell or production-like lower environment, avoid selecting profiles that copy full application, master, or transactional data unless this is specifically required. For Shell Build style use cases, profiles such as SAP_CUST, SAP_UCUS, or SAP_UCSV are normally more appropriate depending on whether user master data and variants are required.