IT systems · Practical guide

Validating Sage X3 for GxP use

Sage X3 can link purchasing, warehousing and production. Whether a rejected material status actually blocks an issue depends on configuration, permissions and data flows. Use the Sage X3 V12 documentation to plan checks of traceability, exceptions, change records and ongoing operation.

Table of contents

At a glance

What matters when validating Sage X3?

Validate the intended process in its actual Sage X3 configuration. Record the version, deployment model, sites, enabled functions and customisations. Test the effect of quality statuses and management rules, elevated permissions, complete batch links and configured logging. The supplier’s features are a starting point. Your requirements, risk rationale and documented results demonstrate how the configuration performs.

  • Technical basis is the online help for Sage X3 V12. Compare the information with your installed version, your configuration, and your customizations.
  • Q and R are status indicators; their effect depends on rules and authorizations.
  • The table audit requires deliberate configuration and does not capture all data indiscriminately.
  • Cross-location processes, modifications, and operational responsibility fall within the same validation scope.

1. Define version, operating mode, and system boundaries

The technical examples refer to the publicly available online help for Sage X3 V12. However, a V12 help topic does not specify which patch level is installed or which functions are included in your contract. Therefore, capture the application version, technical components, activated features, customizations, and integrated systems prior to comparing requirements against vendor documentation.

Sage currently describes SaaS, Private Cloud, and On-Premises as deployment models. The specific assignment of responsibilities follows your offering and operating concept. Clarify update lead time, administrative access, testing opportunities, and data access in the event of exit. A general statement regarding the deployment model does not replace these agreements.

This article addresses Sage X3 independently. Functions from German Sage 100 or any other Sage solution are not transferred. Additionally, a technical command to validate a table in the development environment does not constitute evidence of a GxP-computerized system validation.

Sources: [1] [6] [8]

2. The relevant decisions and records determine

Begin with the intended material flow: Who determines usage, where is the critical documentation located, and what information is passed to the next process? The same inventory can be interpreted differently for dispatch, production, and quality decisions. Document the significance of each used status and the actual data that supports a professional release.

The focus here is on GMP processes for human medicinal products. Annex 11 requires a risk-based approach. For Part 11, specific electronic records and underlying FDA requirements are decisive. The software brand or the presence of a quality module does not determine this application area.

A suitable starting point is a workflow from warehouse receipt through to delivery, supplemented by corrections and exceptions. Assign responsibility, data source, and expected validation evidence to each critical transition point. This enables justification for the necessity of a specific test, while other functions remain outside the defined scope.

Sources: [8] [9] [10]

3. Verify quality status and its actual blocking effect

The X3-V12-Help defines A as accepted, Q as in quality control, and R as rejected. The product category's administrative rules are decisive: Depending on configuration, either a Q- or R-status may be assigned and issued. A mandatory analysis requirement for Q also arises from the setting. The letter alone therefore does not constitute a reliable blocking effect.

First, establish the technical requirement: For example, material shall neither be shipped to a customer nor consumed in a specific manufacturing step prior to quality release decision. Translate this requirement into the relevant booking types and control rules. The following internally developed review recommendations are based on such a prerequisite and do not constitute assertions regarding your current configuration.

Example: Review of a proposed lockout concept
Starting pointIntentional simulated procedureTo be determined in advance
Material is pending quality release decision Normal warehouse account attempts a release Unauthorised use will be prevented in the affected area.
The material was technically rejected. Order attempts assignment and subsequent delivery Both steps comply with the approved lock-down concept.
Analysis is incomplete User attempts to assign an accepted follow-up status A required decision cannot be circumvented
Only a portion of the quantity is accepted. Order exceeds available quantity Unreleased quantity is excluded from efficacy.
Exception permission is present An authorized person carries out a scheduled special procedure. Authorization, justification, and evidence align with the exception process

Sources: [2] [8]

4. Demonstrate traceability across locations and process boundaries

The Traceability function describes forward and backward traceability of a batch, including cross-site tracking. The assistance also sets a limit: components from assembly or disassembly processes are not displayed through this function. If such processes occur, a separately assessed traceability pathway is required; a general statement regarding batch backward traceability is therefore insufficient.

Pilot example: Allocate an incoming raw material batch to two manufacturing orders. Ship a portion of the result to a second location and subsequently record a return shipment. Identify the affected downstream batches originating from the incoming batch and trace a delivery back to its source. Verify that quantities, document references, and display limits align with your independent target inventory?

Also verify the evaluation itself: A stored restriction to a specific site or document type must not be misinterpreted as a complete recall list. Document the selection criteria used by the department and how outsourced process stages are considered. Explicitly identify steps that are intentionally not covered in the validation evidence.

Sources: [4] [8]

5. Evaluate rights per function, location, and exception

The X3 Help describes functional authorizations with restrictions by location or location group, along with additional options. Derive a technical role model from this: data entry, review, status update, correction, and administration represent distinct responsibilities. A user must be able to perform the required action at the correct location; unauthorized access at that location must also be reviewed.

Particular attention should be given to STOADMIN. According to the manufacturer, an authorized stock administrator may bypass assignment and administrative rules, for example, issuing R-stock. Whether this capability is required must be determined by your operational needs. If required, define its strictly limited purpose, the issuance procedure, and subsequent professional verification.

Example: Repeat the same locked release action using a standard warehouse account, quality role, and intended administrator account. Document differences and authorized exceptions. Then verify role revocation and location change. The result must align with the approved task delegation, not merely with the technical expectations of an administrator.

Sources: [5] [3] [8]

Further reading:

6. Specifically configure and evaluate the Table Audit

X3 V12 can log selected table operations via database triggers and store configured field values before or after a change. The help documentation explicitly states that the standard does not include an audit configuration. Additionally, audit tables themselves, as well as CLOB, BLOB, and AXX fields, are excluded from this mechanism.

The technical question is therefore: Which relevant changes must you be able to understand later? Assign these requirements to the actually affected tables and fields. A technical protocol entry is insufficient if the auditor cannot identify the business context. Changes to the audit configuration itself and administrative interventions also require a reviewed control.

The following assignment constitutes a proposed approach for review. Assess it jointly with your X3 partner and quality assurance. The implementation of a table-based audit does not, by itself, guarantee complete change justifications or compliant electronic signatures.

From Technical Audit Inquiry to Verifiable Evidence
Process questionTo be verified in the systemAcceptance based on your intended use
What was changed? Relevant fields and conditions for documentation Major changes remain clearly reconstructible.
To which procedure does the change belong? Identity and permanent traceability of the record Auditors can clearly identify the relevant business incident.
How are corrections justified? Justification for a required change amendment The reason and correction remain traceable and linked.
What contents are missing from the mechanism? Affected data types and additional supporting evidence Boundaries are assessed and required gaps are addressed.
Who controls conspicuous changes? Access, Selection, Review, and Follow-up Process The responsible party recognizes, evaluates, and tracks relevant anomalies.

Sources: [6] [8]

7. Quality decision and electronic signature to be evaluated separately

Define what constitutes a release in your process: Does it confirm a test result, authorize material usage, or substitute a legally relevant signature? These decisions may be interrelated but are not equivalent. A changed status does not automatically document all components of a required signature.

When electronically signing, the identity of the person, the timestamp, and a permanent link to the relevant record must be verifiable and consistent with applicable requirements. Evaluate individually the case of a subsequent amendment to released content: Which decision remains valid, what requires re-evaluation, and how does a later reader identify the difference? Assert this effect only when the specific workflow is substantiated.

Sources: [8] [10]

8. Verify configuration, in-house developments, and interfaces together

Sage distinguishes in the V12 documentation between settings and specific developments. Settings can be complex and may generate code; developments require separate measures to manage changes and patches. This technical distinction is helpful for inventory management but does not automatically assign a GAMP category or a blanket scope of validation evidence.

Therefore, identify which change materially affects the process: a calculated quantity, a status transition, a report, or an interface. Clarify the intended behavior, responsible parties, and change history. ERP supplier documentation does not replace a customer-specific extension description.

Example of a interface test: An attached laboratory system transmits a result twice, followed by a corrected version. Verify identity, sequence, associated material quantity, and the allowed follow-up action. Repeat the scenario with a connection drop. Define in advance which system holds decision authority and how incomplete or inconsistent transmission can be detected.

Sources: [7] [8]

Further reading:

9. Ensure professional and technical safeguards for migration, releases, and restoration

Plan a migration involving more than a single dataset comparison. For representative batches, the required quantities, units, statuses, references, and historical records must remain accessible in the intended target system. Define which legacy data is transferred and which is retained in a separate preservation solution. A reviewer conducting a subsequent investigation must be able to understand this boundary.

For a batch release, assess the impact on approved processes, permissions, audit settings, and configuration changes. Accordingly, perform targeted regression testing and document any remaining deviations. Neither the term "standard update" nor the technical commitment to maintain a setting addresses the question of professional suitability.

During a recovery exercise, the department should be able to trace a representative business scenario following technical restoration. Verify associated data repositories and required historical records. Establish acceptable alternate procedures and controlled restart protocols during an outage; a hosting agreement alone often does not adequately describe these workflow steps.

Sources: [8] [7] [1]

10. Prepare the project launch for key issues of concern

In a small or medium-sized company, establish who defines the expected process outcomes and who can explain the technical implementation. Identify the warehouse or production owner, QA, the internal system operator and the X3 and hosting partners as applicable. Management should resolve open responsibilities and staff availability before a tentative target date becomes a de facto release date.

The effort depends among other factors on locations, different material rules, in-house developments, interfaces, and existing documentation. Unclear exceptions and hard-to-explain inventory data are particularly time-consuming. Therefore, a brief inventory review together with a complete example process provides a more robust planning basis than the number of users alone.

  • Document version, patch level, operating mode, locations, and enhancements.
  • Identify key quality decisions and records for each process.
  • Understand product categories, status rules, and existing exceptions.
  • STOADMIN and other elevated authorizations with their intended business purpose are documented.
  • Traceability for partial quantities, location changes, and returns with required stock levels prepared.
  • Define audit configuration, technical limits, and subject matter review.
  • Provide a representative test environment, roles, and failure scenarios.
  • Agree on migration, release assessment, restoration, and release responsibility.

Sources: [8]

Project experience and collaboration

Trace quality status through to material use

In Sage X3, we work backwards from a particular use of material. What status applied, which decision had been made and which rule permitted the posting? The business team, IT and any relevant partner bring together the configuration and existing evidence. A targeted test may resolve a single uncertain transition. For a new site, we also examine local rules, permissions and handovers between sites. These differences determine the cases to test at each site.

Frequently asked questions about Sage X3

Is Sage X3 automatically suitable for GMP processes?

A functional scope alone does not establish suitability for use. You must define relevant processes, data, and requirements and evaluate the configured implementation in a traceable and justifiable manner. This applies equally to roles, expansions, and operations. Manufacturer documentation serves as a key foundation; however, your justification must demonstrate why the specific workflow reliably fulfills the intended functions.

Sources: [8]

Which version and operating mode do the examples refer to?

The functional details are derived from the Sage-X3 V12 Online Help. The article does not reference a purported latest patch level. Verify the information against your specific installation and licensing configuration. Sage currently describes several operating models, including SaaS, Private Cloud, and On-Premises; the specific features, update procedures, and responsibilities must be confirmed in accordance with your individual contract and operational concept.

Sources: [1] [2] [6]

Should Q and R be automatically blocked for every material release?

No. The V12 Help states that assignment and distribution for this status also depend on administrative rules. Therefore, review the current combination of product category, booking path, and authorization. Your professional blocking rule must be justified for each relevant usage pathway. A visible status indicator must not be unverifiedly interpreted as a comprehensive usage restriction.

Sources: [2]

Why must STOADMIN be given special consideration?

The stock administrator may, according to Sage rules, bypass standard user restrictions during inventory processing. This capability may be necessary for defined exceptional cases, but must align with the approved process. Assess authorization assignment, permitted circumstances, and subsequent controls. Explicitly evaluate the difference between a standard account and an exception authorization, rather than verifying only the successful standard workflow.

Sources: [3] [8]

Does the table audit capture all relevant changes?

Not automated. Tables, operations, fields, and conditions are configured; the help section also lists excluded data types and does not provide a standard audit setting. Compare the actual coverage against your requirements. Also assess the business relevance and the protection of evidence. Technical gaps requiring specialist solutions must be addressed, not merely by extending the log file.

Sources: [6] [8]

Does the traceability report support every type of trace?

The documented functionality supports forward and backward traceability as well as cross-site references. However, it has limitations, particularly in cases involving components from assembly and disassembly. Review your actual process steps, selection filters, and required references in conjunction with an independent required inventory. Additional traceability pathways shall be defined where the applied analysis does not fully reflect the technical process flow.

Sources: [4]

Must an X3 adjustment always be classified equally?

No. The technical distinction between recruitment and development does not result in a flat-rate GAMP category. Evaluate what will be changed, what influence this has on relevant data or decisions and what appropriate evidence is available. A small formula may be technically significant, while a mere change of presentation justifies a different scope.

Sources: [7] [8]

What should we prepare prior to startup?

Useful are version overview, process and site lists, relevant material rules, roles, extensions, and known interfaces. Include a representative batch production flow and access to an appropriate test environment. Identify, above all, the personnel responsible for defining intended values and evaluating results. Incomplete documentation can be systematically supplemented when open items are clearly visible and assigned to responsible parties.

Sources: [8]

Who must collaborate and what causes effort and duration?

Process owners, Quality Assurance, IT or system administrators, and the relevant X3 partners must be able to jointly decide. Key drivers for effort include differing site-specific rules, exceptions, data quality, customizations, interfaces, and lack of supporting documentation. The availability of functional departments also impacts planning. Only after a thorough assessment can a robust workload estimate be established; the product name alone does not determine a fixed duration or price.

Sources: [8]

How much must be re-verified after a batch release?

First assess which released requirements and dependencies may be impacted by the release. From this, derive validation evidence and regression testing. Pay particular attention to material rules, authorizations, logging, and customizations. Document results, deviations, and release decisions. Unknown impacts must not be implicitly considered unchanged; they must be investigated or appropriately addressed within the test scope.

Sources: [8] [7]

Sources and review date

Source date: 6 October 2026. Technical statements relate to the specified Sage-X3-V12-Helper topics. The online help does not replace a review against the installed patch level, activated features, contract, and customizations. Information on deployment models is derived from the current German product description. The regulatory focus is on GMP processes for human medicinal products; the test cases are internal proposals.

  1. Sage Germany: Sage X3, current product and distribution description
  2. Sage X3 V12 Online Help: Quality Control (GESSTQ)
  3. Sage X3 V12 Online Help: Stock Administrator (STOADMIN)
  4. Sage X3 V12 Online Help: Traceability (CONSSTK)
  5. Sage X3 V12 Online Help: Functional Profile (GESAFP)
  6. Sage X3 V12 Online Help: Tables, Audit tab (GESATB)
  7. Sage X3 V12 Online Help: Setup and specific development
  8. European Commission: EU GMP Annex 11, Computerised Systems
  9. European Commission: EudraLex Volume 4, current GMP guidelines
  10. FDA: Part 11, Electronic Records; Electronic Signatures – Scope and Application

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Define the scope of evidence for your X3 process

We support you in structuring material selections, exception pathways, and justifications in collaboration with Quality Assurance, the Technical Department, and X3 partners. The starting point is the intended use.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →