Table of contents
At a glance
How do you validate SAP Business One for GxP use?
Demonstrate that your SAP Business One installation meets the requirements of its regulated use. Include the version, configuration, database, add-ons, roles and interfaces. The consequences of a failure determine test depth. Pay particular attention to effective material controls, complete data transfers and traceable changes. Supplier documentation and partner testing can help, but neither replaces your assessment of the process.
- The batch status and technical suitability must be consistent for each relevant document.
- SAP Business One will be evaluated independently; functions from ByDesign or S/4HANA will not be transferred.
- Change Log, approval and electronic signature serve different functions.
- Add-ons, technical users and exceptions are included in the scope of the exam.
1. Define the regulated use in decision-making
Start with a process list rather than navigating through all ERP menu options. Which data drive material usage, manufacturing, labeling, or traceability? Who relies on these data? An incorrect bank connection and a wrong quality status have different implications. Shared master data can impact multiple workflows. Therefore, document which functions are relevant and explain why others fall outside the scope of the current evaluation.
For GMP activities involving human medicinal products, EU Annex 11 addresses computerised systems and a risk-based approach. As of October 6, 2026, the EU Directory implemented the January 2011 revision. Part 11 is classified based on relevant FDA record-keeping requirements and actual use of electronic records. The product name alone does not determine the applicability.
2. Describe system status and operational responsibility
The technical examples refer to SAP Business One 10.0. The sources include the SAP Business One 10.0 application guide, the SQL Administration Guide SP 2605, and the Web client help on authorization settings, version FP 2608. These documentation versions do not represent the version currently installed. SAP Business One is neither SAP Business ByDesign nor SAP S/4HANA.
Document the complete system architecture including the database platform and actually used client. For a hosting partner, clarify who manages users, performs backups, and notifies of changes. A successful installation does not guarantee that your technical requirements have been correctly implemented.
| Component | Required information | Why it counts |
|---|---|---|
| Installation | Version, Feature-/Support-Package, Database, Localization | Define functions and supported combinations |
| User access | Desktop client, web client, mobile, or technical access methods | Identify alternative booking paths |
| Extensions | Add-on Version, Custom Fields, Queries and Reports | Make additional logic visible |
| Operation | System Owner, Hosting Agreement, Backup and Recovery | Assign responsibility to the relevant parties. |
3. Check batching and traceability throughout
SAP distinguishes batch assignment at each booking and only during release. Article-specific settings may override the general default. The review begins at master data level: Is the intended batch management method established for all relevant articles and controlled against inappropriate changes?
For an internal traceability audit, use, for example, two batches from the same material supplied by different vendors. Record inbound receipt, partial withdrawals, transfers, and returns. Then, have a qualified user reconstruct the origin and usage of a selected subset of material. Verify quantities, units, internal and external batch numbers, and the linkage between postings. A filled batch field alone does not adequately address these questions.
Sources: [2]
4. "Locked" does not imply a complete process lock
The SAP help documentation still lists potential inventory documents for "Locked" status, such as transfers and product withdrawals. "Access not possible" restricts certain sales documents but allows, for example, inventory transfers. The English term "Locked" must therefore not be unverifiedly interpreted as a complete quarantine function.
First, define the technical rule: A material may be relocated approximately, but not withdrawn for manufacturing purposes. Then, assign an authorized action to each relevant documentation type. If a discrepancy exists between standard behavior and process requirements, evaluate appropriate additional controls. This may require an alternative process approach or a reviewed process extension. The key factor is the documented overall outcome, not the name of a status field.
Sources: [1]
5. Example: Test of material status including exception route
The following example considers a facility with a separate quality decision function. Raw material R-01 is available as Batch C-01. No withdrawal for the defined manufacturing process may occur prior to release; documented transfer to the testing area is permitted. Does your solution comply with this rule? The test result determines compliance and is not a guaranteed standard function.
Perform cases using a standard warehouse user. Document initial inventory, configuration, role, transaction type, and expected behavior prior to execution. Repeat critical cases using actual scanners or interfaces employed in practice. A test successful only in the desktop client does not automatically validate an alternative booking pathway.
| Situation | Verification | Acceptance criterion of the example |
|---|---|---|
| Batch without quality release | Withdrawal for manufacturing initiation | Unauthorized use is prevented by the implemented overall solution. |
| Permitted quarantine transfer | Shift batch within defined test range | Batch, quantity, and business status remain correctly assigned. |
| Exception user | Change status and subsequently withdraw | Only the duly authorized pathway is possible; the decision must remain traceable. |
| Outdated Quality Notification | Retransmit an earlier release status | Current decision will not be overlooked or overridden |
| Withdrawal of a subset | Partially reverse the withdrawal | Quantity, origin, and additional usability conform to the specified rules. |
6. Testing Roles at the Actual Workpath
SAP defines Superusers with full privileges that are not restricted like those of regular users. Therefore, such accounts should not be used as evidence that a specific role has been appropriately scoped. Ensure documentation also includes user groups, representations, and technical accounts. When multiple user and group assignments exist, SAP identifies the highest applicable privilege level as effective. A restricted individual assignment does not automatically negate any broader group privileges.
A meaningful role validation considers, for example, the creation of a batch, the modification of its status, and the removal of a batch separately. Test both authorized and rejected actions. Include a role transition and user exit scenario. For partner solutions, verify their own rights management. Additionally, document who controls authorized administrative changes and how urgent support requests can be traced and justified.
Sources: [3]
7. Change Log, Link storage and professional history together
The ChangeLogsService service describes modifications to various Business-One objects and displays differences. This does not constitute a complete coverage of every technically relevant event. Select specific, relevant changes—for example, a master data value or a permission setting—and verify the actually available information.
Additionally, SAP documents a cleanup function for change logs. A technical deletion capability does not constitute professional authorization to remove information subject to retention requirements. Therefore, establish appropriate safeguards, access rights, and retention periods in line with the record. Verify that the responsible party can later clearly reconstruct a process. If reasons or contextual links are missing, the supplementary control must actually address this gap.
8. Compare client and interface authorizations
In the documented Webclient settings, a separate option activates the approval process for the DI data interface. Other options concern changes to pending or approved drafts and generated documents. These settings belong in the documented configuration if the corresponding process is relevant.
In particular, assess a professional change following approval: what decision shall then be made, and what information does the approver receive? Also evaluate rejection and delegation scenarios. An approval function does not constitute an electronic signature under Part 11. If such a signature is required, additionally evaluate the relevant requirements regarding identity, significance, and permanent association with the record.
9. Purposefully include add-ons, reports, and data transfers
A sector-specific package can significantly alter the relevant process. Demonstrate which function is achieved through SAP standard, a configured partner product, or custom development. A generic GAMP category solely due to the designation "add-on" is insufficient for this differentiation. Evaluate the actual component and its actual usage.
For each significant transfer, document the leading system, identifiers, units, and error handling. A sample test re-sends the same goods receipt twice following a connection failure. The agreed expectation is: no undetected duplicate booking and a traceable error resolution process. Each individual release report is verified against known data, including edge cases. Evaluate partner evidence for consistency with your version, configuration, and used integrations.
10. Migration, Changes, and Project Launch Preparation
During a migration, compare not only dataset volumes. Review selected historical batch chains, open documents, quantities, and required attachments. Define which history must be available in the target system and which must remain readable in the legacy system. Specify how errors are corrected and how re-imports are controlled.
The SAP Administration Guide covers databases and components during upgrades, as well as backup and recovery procedures. Derive a separate review scope from planned changes. A restart test should include a technical workflow, not merely the server startup. At project initiation, the following action points should be jointly defined with the functional department, IT, partner, and QA:
- Process owners designated and regulated decisions defined.
- Installation status, database, client access, and add-ons documented.
- Relevant batch, master data, and role rules agreed.
- All interfaces, reports, and exception pathways fully documented.
- Appropriate test environment available, along with representative and targeted erroneous test data.
- Partner evidence verified; open gaps and responsible parties identified.
- Migration, storage, restoration, and operational changes planned.
Sources: [7]
Project experience and collaboration
Check batch and quality data in SAP Business One
We assess Business One, its industry add-on and connected applications as one workflow. Your process team might show us how a batch is created, assessed and used. With IT and the partner, we identify applicable documentation and evidence gaps. A limited extension may need only a targeted check. If the operational process changes, we redefine requirements and testing with your team.
Frequently asked questions about SAP Business One
Must the entire SAP Business One be validated?
The scope follows your regulated use. First, identify the processes, records, and shared data that impact product quality or relevant decisions. From this, derive the affected functions and dependencies. A blanket review of all menus is no more justified than excluding the ERP solely due to its financial functions.
Sources: [8]
Is SAP Business One suitable for pharmaceutical use?
Not automated. Whether SAP Business One adequately supports your pharmaceutical process is demonstrated by the evaluation of the overall solution against your requirements. Consider standard features, partner package, and your specific organizational structure together. Identify critical workflows, including error and exception cases.
Does a blocked batch status prevent every goods movement?
No. SAP still describes inventory documents that can be created. Check the actual document type and workflow. If the requirement is to prevent a production issue, test that specific action in the configured system. Define which stock transfers remain permitted. The status name alone is insufficient evidence.
Sources: [1]
Does a Change Log constitute a complete GxP audit trail?
An existing Change Log is not yet a proof of a complete GxP audit trail. The ChangeLogsService describes changes to different business-one objects; you must check the coverage of all events you need. Include your own fields, partner solutions and technical approaches. Evaluate comprehensibility, protection, storage and possible gaps.
Sources: [4]
Are approvals in SAP Business One processed using electronic signatures?
An approval status alone does not establish the applicable signature requirements. First, clarify which decision is to be confirmed and whether an electronic signature is required. Then evaluate the full implementation, including but not limited to user assignment, the significance of confirmation, and its alignment with the correct version of the record.
Sources: [10]
Does the same validation evidence apply to the Desktop client, Web client, and interface?
Only to the extent that the proven functionality and its prerequisites actually align. Capture all utilized access points and verify discrepancies. Documented, separate activation of the approval process for DI demonstrates why a single surface test does not cover all pathways. Critical transfers require appropriately selected individual cases.
Sources: [6]
Can we take over the partner's validation package?
Appropriate documentation may be used upon evaluation. Compare versions, configurations, requirements, and executed test cases against your actual implementation. Remain transparent regarding process variants, interfaces, or risks that are not covered. A volume of documentation or a successful standard test does not replace the justified decision to retain additional internal evidence.
What must be ready prior to startup?
Collect process overview, installation status, add-on and interface list, roles, and available partner certifications. Identify critical decisions and known edge cases. An accessible test environment and appropriate data enable subsequent concrete testing. If these fundamentals are missing, plan initial clarification first; otherwise, a supposed test phase may devolve into an unplanned inventory review.
Who must work on a small company?
Minimum requirements include individuals who are competent to assess the process technically, provide technical oversight of the system, and authorize quality requirements. The implementation partner shall provide details on configuration and enhancements. A single individual may assume multiple responsibilities, provided that authorities, necessary competencies, and appropriate controls have been established. Special attention should be given to allocating time for technical evaluations and review of findings.
What factors determine effort and duration?
Key drivers include the number of critical process variations, internal enhancements, interfaces, data quality, and the current state of existing documentation. Additionally, available test environments, queries to partners, and turnaround times for test results play a role. A clear standard process can be designed differently than a migration involving numerous exception pathways. Reliable timelines arise from these factors, not from the product name.
Sources and review date
The product specifications are based on the referenced SAP documents and their respective version statuses. Check matrices and project questions are standalone recommendations; the behavior of the specific installation must be verified.
- SAP Business One 10.0: Window Batch Details
- SAP Business One 10.0: General Settings for Batch Numbers
- SAP Business One SDK 10.0: ChangeLogsService
- SAP: How to Manage the Protection of Personal Data in SAP Business One
- SAP Business One Webclient: Approval Process Settings
- SAP Business One Administrator’s Guide
- European Commission: EU GMP Annex 11
- European Commission: EudraLex Volume 4
- eCFR: 21 CFR Part 11
- FDA: Part 11 – Scope and Application
Sources checked: .
Define the scope prior to the testing phase
We support you in delineating SAP Business One processes, evaluating existing partner certifications, and planning pending audits. As a starting point, system overview, expansion list, and your key regulated workflows are sufficient.
- 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.

