IT systems · Practical guide

GxP SAP system copies and client refreshes

An SAP system copy starts successfully, but a background connection may still point at a production target. Before using the copy for tests, verify that the data, identities and active functions suit the intended target environment.

Table of contents

At a glance

What should you check after a GxP SAP system copy or client refresh?

Verify the planned data and configuration version and relevant target references, including system identity, connections, jobs, users, outputs and interfaces. Assess protection and permissible use of copied data separately. Perform technical and business acceptance checks and document the permitted use. A system copy and a client refresh have different scopes. No universal post-copy list fits every landscape.

Define the copying procedure and intended use unambiguously

During a system copy, a system duplicate is created with a different host and system identity. A system refresh updates an existing target with source data and, in the SAP-described procedure using ABAP Post-Copy Automation (PCA), retains the previously backed-up target configuration. In a client copy, the selected profile or table selection determines which data from a source client is transferred to the target client. Source and target may reside in the same or different systems. In the refresh plan, clearly specify the exact procedure, product version, data and configurations transferred, as well as intentionally excluded components.

Define the purpose: development, training, regression, migration trial, or failure analysis. This determines distinct requirements for data availability and functionality. A training-optimized environment is not automatically a representative validation system. If tests in such an environment are intended to serve as release documentation, relevant differences from intended production must be evaluated. The copy date alone does not establish full equivalence or technical suitability.

Sources: [1] [4] [2]

Before copying: document dependencies and data risks

Prepare an inventory of relevant interfaces, background jobs, output destinations, identity services, and external archives. Assess which connections are carried over during copying and which remain separate. A stored target name within the system may continue to point to production after a refresh. Also, printers, email recipients, and file destinations can trigger real-world effects outside the test environment.

Evaluate confidential and personal data prior to acceptance. The data protection legality shall be separately determined. Data masking and target authorizations must align with the intended test. Consider local copies and exports to external project stakeholders. An identical data set may facilitate certain tests, but does not automatically justify any access. Define which security and configuration measures must be completed prior to the first user access.

Sources: [2]

System identity and compounds verified during post-processing

SAP describes post-copy automation for technical follow-up activities. The extent and manner of its implementation depend on the specific process and available resources. Automation serves as a support tool, not a blanket acceptance. Verify the actual system requirements, connections, and target mappings. Document which settings are copied, modified, or deliberately restored.

The separation for productive processing is particularly important. Test the intended interfaces with controlled remote sites or suitable replacement procedures. A connection that works technically can be dangerously wrong precisely because it reaches the wrong system. Document target address, authorization and effect on the process. The proof should confirm that the planned path is actively and unauthorized real processing is prevented, not only show a successful network response.

Sources: [1]

Example: Refresh of a validation system

In the example, an SAP test system is supplied with a current data level. The source contains a nocturnal shipping job, a laboratory connection and an output to a real printer. Only controlled test counterparts are to be used in the target. The technical copy run ends successfully. Before the release, the team checks whether jobs, connections and outputs correspond to the target concept and do not trigger productive action.

The reference package also includes a known item, a batch, and an open process. These objects are professionally reviewed upon refresh. A correctly launched system with incorrectly imported customizing would be unsuitable for the intended validation demonstration. The matrix below serves as an independent work aid. It is adapted to the actual copy procedure and does not claim to provide identical replication efforts for each SAP product or each cloud edition.

Own work aid – Example: Refresh of a validation system
AreaAcceptance questionRelevant evidence
System integration Is the intended target being activated? Unique identity and labeling
Interface Which endpoint is reached? Controlled test with objective evidence of intent
Background job Can he run towards the target? Verified active job list
Output Where does pressure or message go? Defined test channel
Data version Is the required inventory available? Reference objects and comparisons
Use Which tests are approved? Documented Suitability and Limits

Sources: [2]

Check data, configuration, and executability separately

A quantity check can confirm that relevant data sets have been successfully transferred. Include domain-specific reference objects and their relationships. Verify key master data, statuses, numbering linkages, and required historical records. An identical number of data records does not automatically confirm correct assignment. If data have been masked or transformed, these rules are reviewed and documented to distinguish them from the original dataset.

The configuration may differ from data transfer and software version. Verify which customer-specific settings and enhancements are relevant to the test. Following this, assess the feasibility of a known process scenario. Each of the three levels provides distinct insights. "Data available" does not imply "process representative"; "process is running" does not imply "all required data are complete". The acceptance criteria integrate the evidence necessary for the intended use.

Sources: [2] [3]

Evaluate users and permissions following the refresh

Transferred accounts may have inappropriate rights or historical access levels in the target. Check intended roles, technical users, external stakeholders and blocked accounts. A project administrator should not automatically get access to all productive confidential data. Permission follows the target purpose. Connections to the identity service are also checked for the correct context.

Evaluate relevant authorized and denied actions. Assess whether existing test identities should be retained or new ones established. Historical user assignments and current access rights are distinct considerations. Masking of display names must not inadvertently disrupt necessary test relationships. At the same time, historical references must not serve as justification for granting access to former employees. The specific implementation will be clearly documented in the target concept.

Sources: [2]

Demonstrate representativeness for validation tests

When used as a GxP validation objective, document relevant differences from the intended production. This may include interface replacements, data volumes, software components, printers, and permissions. Not every deviation renders a test inappropriate; however, each must be evaluated in relation to the specific test assertion. A simulated lab value may validate a mapping rule, but cannot automatically demonstrate actual end-to-end transmission.

Define additional evidence for aspects the environment cannot represent. Identify checks to be performed later in a suitable environment. Keep the tested version stable or assess changes before execution. A refresh during a test cycle can invalidate input data and evidence already obtained. Trace each result to its actual baseline.

Sources: [2]

Release, Repeatability and Next Change

The completion combines copy scope, technical rework, data reconciliation, permissions, reference cases and known limits. Name the permitted use. An environment can be ready for development while still missing conditions for a formal process proof. These differences should be visible and not remain solely in the knowledge of an administrator. Open critical target connections are clarified before the relevant use.

For recurring refreshes, a well-kept procedure with controlled inputs and acceptance criteria is suitable. Automated controls can detect typical misconfigurations. However, check their effectiveness and changes. A list, which is only signed again at each run, does not prove actual testing. Good post-copy work provides a comprehensible target condition and makes the next test cycle reliably planable.

Sources: [2] [1]

Project experience and collaboration

Verify the refreshed test system before use

Before a refresh, we agree with SAP Basis and process owners which configuration to preserve and which data version to copy. Using known objects, we trace the data references, jobs and endpoints actually reached. Planned automation may support the follow-up work. Different system landscapes need their own controls. We pay particular attention to outputs or connections that could inadvertently reach production. The resulting target state and supporting evidence determine permitted test use.

Frequently asked questions about Validating an SAP system copy

Are system copies and customer refreshes the same?

No. Upon a system copy in SAP, a duplicate is created with a different host name and its own system ID. A system refresh overwrites the existing target with current source data; the target configuration is previously backed up according to the post-copy automation procedure described by SAP and is then re-applied. In contrast, a client copy transfers a selected scope of a source client to a target client, either within the same or a different system. The specific approach used for a "client refresh" must be clearly defined within the project. This leads to the required follow-up activities.

Sources: [1] [4]

Does a successful SAP startup following a copy suffice?

No. It only confirms a technical partial state. Check relevant data, configurations, connections, jobs, and permissions. For validation tests, the environment's suitability for the specific test objective must be demonstrably justified. An ongoing system may continue to use incorrect productive objectives.

Must all interfaces within the test system be disabled?

Not at all. Required tests can require controlled connections. The decisive factor is which remote points and effects are explicitly allowed. Productive actions must not be triggered unintentionally. Check target addresses, identities and processing based on the released target concept.

Can a production copy be used unchanged for testing?

This requires evaluation of purpose, access, protection, and legal compliance with data protection regulations. For certain tests, masked or synthetic data may be more appropriate. Additionally, review active job roles and communication channels. The term "test system" alone does not justify any data access or any outgoing data processing.

Can Post-Copy Automation replace acceptance?

No. It can perform and document defined follow-up tasks. The acceptance review verifies whether the required target state has actually been achieved. The scope and boundaries of automation must be clearly defined. Appropriate technical and professional controls should be implemented instead of relying solely on a successful automation status.

Sources: [1]

What happens to already executed tests after a refresh?

Assess whether your established status and statements remain appropriate for the intended release. A refresh may alter data, configurations, or dependencies. Previous results remain historical evidence and must not be unreviewedly attributed to the new state. Required recertifications will be justified and formally defined.

Sources and review date

Source date: 14 October 2026; supplemental SAP help for customer copy reviewed on 18 October 2026 in the version 2025 FPS02. Regulatory classification and manufacturer functions are separately documented. Examples, test matrices, and templates are standalone work aids; they are customized for the actual intended use.

  1. SAP: ABAP Post-Copy Automation Configuration GuideTechnical follow-up activities on system copies. No universal command sequence applicable to each SAP environment. Reviewed on 14.10.2026.
  2. European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 14.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
  3. PIC/S: PI 041-1, Good Practices for Data Management and Integrity (2021)Inspection Guidance on Data Integrity; in particular electronic data, transmission, access, and review.
  4. SAP ABAP Platform 2025 FPS02: Remote Copy of Customer Data Between SystemsVersion 2025 FPS02, visible as of October 18, 2026. Customer copy with predefined source/destination customers and scope defined via copy profile or table selection. For the specific release, the associated tools and limitations must be taken into account.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

How we can support you

Daniel Herrmann Consulting combines professional assessment with hands-on work on the specific system. During the first meeting, we clarify your intended use, existing documentation, and the next most appropriate action step.

  • SAP S/4HANA validation →

    Support an SAP go-live with evidence your team can defend at audit while keeping validation on schedule. We take a risk-based approach from the template to the interface for greenfield or brownfield projects and existing ECC systems.

Send a project enquiry Customer testimonials →