IT systems · Practical guide

Validating abas ERP: testing customisations and material flows

In abas ERP a custom rule may work on a screen yet fail to control the warehouse or interface transaction that matters. Include standard functions, tailored workflows and material flows when scoping GMP use. The examples are planning cases, not findings of a known product defect or results from an executed abas test.

Table of contents

At a glance

How do you validate abas ERP for GMP use?

Demonstrate that your abas environment is fit for its intended regulated processes. Assess the standard functions in use, customisations, permissions, master data and interfaces. The potential impact on the process and its records determines what to test. A configurable ERP, a quality management module or a supplier test report does not replace this assessment.

  • The list of own adjustments serves as a central basis for the inspection requirements.
  • Batch assignment and storage journal currently do not establish a comprehensive GMP release logic.
  • A technical review should be performed on all booking pathways used for the process.
  • Manufacturers, partners, and users require clearly defined and separated responsibilities within the change management process.

1. Define product scope, operating mode, and regulated process boundaries

Abas represents the product for the industrial medium-sized enterprise. The current overview page emphasizes Cloud ERP; however, the evaluated function pages do not call a binding build or a complete assignment of all functions to each contract model. Therefore, document the actual version, additional components, own adjustments and operational responsibility. Do not derive the properties of an existing installation solely from the current marketing.

The application case under consideration here is a GMP-relevant material or manufacturing process for medicinal products for human use. Whether abas should be used for this is based on your business requirements and the proven suitability. The manufacturer focus on industrial medium-sized companies is neither an exclusion reason nor a pharmaceutical proof of suitability.

Annex 11 applies to computerised systems used in GMP-controlled activities. For FDA-related electronic records, additional assessment of the Part 11 applicability scope is required. A ERP for procurement and invoicing is not inherently GxP-related solely due to its name; however, the use of a material status or a quality-relevant data transfer within the system may render it GxP-related.

Sources: [1] [6] [8] [9]

Further reading:

2. Document modifications such that their impact is observable

The manufacturer's individualization portal includes no-code/low-code tools, flexible user interface programming (FOP), Abas Java Objects (AJO), Report Designer, and a graphical workflow designer. For validation planning, the ease with which a change is created is not decisive. What is decisive is the substantive impact of the change and the processes it affects.

Capture each relevant change with purpose, responsible party, version status, and affected data. An additional display field requires different justification compared to a standalone calculation of material quantity. A review or analysis may also be decision-critical if QA relies on it during a batch release. The matrix below is an independent work aid for prioritization and does not constitute a GAMP classification.

Own decision matrix for ABAS adjustments
Adjustment typeQuestion on process impactAppropriate testing method
Additional mask field Information or significant quality statement? Data origin, authorized personnel, and usage tracking
FOP or AJO logic Does she modify the booking, quantity, or decision? Check specific rules with normal, boundary, and error cases
Workflow Who is authorized to proceed with a process? Investigate roll-offs, returns, substitutions, and repetitions
Report Which decision depends on selection and calculation? Compare release with intentionally curated source data
Abas-Connect Configuration What significance does a transferred value have? Assign, transform, and handle errors review

Sources: [2] [6] [7]

3. Demonstrate jointly the manufacturer's standard and own logic

Abas describes an architecture that separates core functionality and adaptations and thus facilitates upgrades. This is useful for your planning, but does not mean that the technical effects of an update are excluded. A received adaptation object can interact with other input data or a changed follow-up process, for example, after a change.

Request a clear description for critical changes, including: trigger, data used, rule, and behavior in case of missing information. This enables process owners to verify the intended outcome without needing to review source code. Technical documentation and coding expertise shall remain with the responsible developer or partner, as required for evaluation of implementation.

Assign existing standard tests to the actually utilized functions. A partner protocol is helpful when version, configuration, and acceptance criteria are clearly visible. Where your installation diverges from this, plan additional supporting evidence. A generic category for the entire ERP system cannot be inferred either from "standard software" or from the presence of FOP.

Sources: [2] [6]

4. Track batch, storage location, and booking correction together

The storage site mentions storage groups and storage places, inventory information as well as a warehouse journal. This should make material movements and the connection of batch or serial number with a customer order comprehensible. For mobile operations, the manufacturer describes the browser-based scanner solution Warehouse.

Distinguish in your requirements the identity of a batch, its storage location, its quantity, and its technical usability. Correctly stored batch numbers do not automatically prevent unauthorized withdrawal. The public product specification does not establish a universal GMP blocking mechanism for all booking pathways; this must be specifically defined for the intended process.

Trace a partial quantity through receipt, transfer, issue and a permitted reversal. Reconcile stock with the movement history and corresponding order. For scanning, add a misread code and an interruption. Decide in advance how a user should recognise a transaction that failed to reach the target.

Sources: [3] [6]

5. Incoming material inspection distinguishes from material selection decision

In the procurement function, Abas describes a simplified quality management system for incoming goods inspections, complaints, and returns. Individual inspection plans, product-specific inspection criteria, as well as sampling or full inspections, are outlined. The local alignment with DIN EN ISO 9001:2015 does not constitute evidence of a complete GMP laboratory or release function.

Therefore, clarify where test results arise, who evaluates them and which decision is returned to the ERP. If detailed laboratory records remain in another system, their relationship to the ERP batch should be recognizable. Also, define the behavior in case of missing testing, incomplete results and a later corrected evaluation.

As a testing approach, two warehouse receipts for the same article with different inspection results are suitable. This clearly demonstrates whether the decision is based on the specific delivery or batch, or inadvertently affects other stocks. A checkmark and permissible material usage are only equivalent if the authorized process rule explicitly specifies this and its implementation is supported by validation evidence.

Sources: [4] [6]

6. Separate storage journal, proof of change and permissions

A warehouse journal addresses questions regarding material movements. However, it does not provide clear traceability for all required changes to master data, test characteristics, or internal quality fields. The analyzed public abas system pages do not offer sufficient evidence of a comprehensive GMP audit trail for your installation.

Prepare a targeted list of relevant data: What may be modified, who is authorized to make modifications, and what documentation is required for subsequent evaluation? Request a demonstration at the actual operational site. When assessing, also consider privileged access and technical accounts. A technical change must not remain invisible simply because it is executed through an alternative access pathway.

For the review, the history must be clearly linked to the relevant activity. Define responsibilities and appropriate review triggers. If electronic signatures are envisaged, evaluate them separately. A workflow approval, a username in the journal, or a document archive claimed to be version-controlled does not constitute signature compliance.

Sources: [3] [5] [6] [8]

7. Verify Connect, REST API, and data export functions according to their intended use

Abas offers Abas Connect for configured integrations and the Abas REST API for read and write access leveraging core logic and customizations. This describes an integration approach, but it does not replace a review of your specific functional rules. Document the actual controls enforced at each respective data transfer pathway.

The connectivity module also includes PDM integration, DMS linkage, and MS SQL Connector. The latter is described for data export and incremental reconciliation. A report generated from this process may therefore reflect a different data state than the current ERP process. For decision-critical analyses, clearly identify the source data and the respective data acquisition timestamp.

At a selected interface, verify not only successful transport but also send an unknown article reference, a missing mandatory value, or the same message repeatedly. Agree on how errors are detected and handled. A technically valid message must not be implicitly considered a fully complete and compliant process.

Sources: [5] [6]

Further reading:

8. Example: a standalone material rule across multiple pathways

The example does not require any specific abas-standard function. A company has established its own quality attribute to control material usage. The rule states: no material withdrawal may occur for the considered order without a documented release decision. In practice, the ERP screen, Warehouse module, and a linked application are being used.

Use the same starting data to test the rule through these three paths. Establish whether your implementation applies the agreed control everywhere. Record any deviations, causes, affected transactions and the decision about continued use.

Own test matrix for a customer-specific release rule
ScenarioExpectation in the defined exampleSubstantiated evidence
Release is missing, standard ERP interface The sample withdrawal does not occur. Quality attribute, role and booking result
Same data, Warehouse The same professional limitation applies to the mobile process. Scanned object and resulting transaction
Same data, linked application Technical access does not bypass the rule. Request, Response, and Actually Implemented ERP Data
Query for connection termination retry A previously booked entry is detected; no undetected duplication. Process identification and quantity reconciliation
Approved release, reattempt The authorized process may continue. Decision basis and successful assignment

Sources: [2] [3] [5] [6]

9. Plan changes and operational transitions in conjunction with the associated adjustments

Assess prior to an update which standard functions, custom rules, and interfaces may be affected. A different evaluation may be sufficient for a change in display only compared to changes in booking logic. Document the decision, including any reused evidence. Technical upgrade capability does not address this technical question.

In the case of migrations, you should examine not only quantities and article numbers but also relationships: Which batch belongs to which movement, which test result for delivery, which release for intended use? A selected dataset with correction history is often more informative than just a comparison of sums. However, it remains a sample whose selection has to be justified.

Specify in the operating agreement who is responsible for handling safeguards, restoration, technical modifications, and failure reporting. Plan for a restart scenario that ensures relevant adjustments, interfaces, and archived records remain accessible. The operation of a server or the availability of a login interface does not confirm the restoration of your material process.

Sources: [2] [6] [7]

Further reading:

10. Organize and participate in KMU binding organizational arrangements

Key information is rarely held by a single individual. The process owner defines allowable material usage; QA evaluates the quality perspective. IT and system owners understand operational workflows and access rights. Developers and partners describe their own logic and interfaces. Procurement and warehouse demonstrate which pathways are actually used under time pressure.

In addition, please specify who has the authority to resolve open questions. Without clear material specifications, a technically executed test yields only observations. A small joint run using known test data promptly reveals such gaps. Use the following checklist as a practical preparation and adapt the documentation to your quality management system.

  • Describe the intended regulated process and relevant records.
  • Maintain product status, operating mode, additional components, and responsible parties.
  • Inventory the in-house FOP-/AJO-logic, workflows, reports, and integrations.
  • Specify material status, inspection decision, and correction procedures in clear and understandable language.
  • Record booking routes including warehouse and technical access points.
  • Verify manufacturer and partner certifications regarding version, prerequisites, and scope.
  • Provide representative test data, required functional areas, and an appropriate test access.
  • Define how deviations will be assessed, who will decide on production use and who will own subsequent changes.

Sources: [6] [7]

Project experience and collaboration

Distinguish standard abas functions, customisations and process steps

Using a material or manufacturing transaction, we identify how standard abas functions, customisations and your own work steps fit together. We match existing descriptions and evidence to the version in use. A known customisation may allow a focused assessment. A newly configured quality-relevant process first needs clear requirements and owners. This distinction determines the tests we prepare with the process owners and IT.

Frequently asked questions about abas ERP

Can ABAS ERP be used in a GMP-related process?

A GMP-compliant use is possible if the specific solution, including its modifications, demonstrably meets the established requirements. Identify the required functions and controls and compare them to your environment. A focus on industrial product output alone does not establish GMP suitability, nor does it preclude such a use.

Sources: [1] [6]

For which ABAS states and operating modes do the statements apply?

The current manufacturer pages were read on October 6, 2026. They describe functional areas and emphasize in the product overview Cloud ERP, but do not show a uniform binding build. For your installation, version, scope and operating model therefore remain separate. Do not transfer public statements unchecked to an existing contract or an older environment.

Sources: [1] [2]

Is ABAS automatically assigned to a specific GAMP category by FOP or AJO?

No. The mentioned tools demonstrate that individual adaptations are possible. For the demonstration, you must evaluate their actual content, development approach, and process impact. An additional display differs from own decision-relevant calculation logic. Therefore, clearly justify the components and their respective validation requirements.

Sources: [2] [6]

Does the storage log suffice for audit trail requirements?

The storage log can provide evidence of material movements. This does not yet establish that it captures all required changes to master data or configuration. Demonstrate the necessary change types at the specific site. Also evaluate protection, clarity, and future subject-matter review.

Sources: [3] [6]

Is the described quality management system a complete pharmaceutical QMS?

This is not supported by the product page content reviewed. The Procurement area describes a basic quality management system, including receipt inspection, complaints, and return deliveries. Additional quality processes and documentation requirements are determined by your specific needs. Please specifically review the interfaces to Laboratory, deviation handling, and material approval, rather than treating functional names as comprehensive coverage.

Sources: [4] [6]

Do we need to apply the same rule to mask, warehouse, and interface?

When using these pathways for the relevant process, their coverage must be justified. It is not necessary for every input to be repeated arbitrarily. What is critical is whether different technical approaches may enable distinct errors or workarounds. The example in this article demonstrates a concise approach to comparing a critical rule with the same input data across multiple actually used pathways.

Sources: [3] [5] [6]

Which manufacturer and partner documentation supports validation?

Version-specific functional descriptions, configuration documentation, traceable tests, and information on changes and known limitations are valuable. For in-house logic, you additionally require your technical rules and designated point of contact. Review each individual requirement to determine which is addressed by these elements. A general quality certificate or the designation "upgradable" does not replace this specific reference.

Sources: [2] [6]

What must our SME provide prior to project start?

Name a decision-making process owner, QA, IT, and the responsible partner or developer. Prepare a system and configuration overview, existing validation evidence, and appropriate test data. Clear rules for material usage and corrections are particularly important. Missing documentation must not be concealed; it should be identified and treated as specific preparatory action items.

Sources: [6] [7]

What drives the effort and duration of abas validation?

Above all, the scope and clarity of own adaptations, the number of different booking pathways, integrations, and the quality of inventory data influence operations. Additionally, existing documentation, testing capabilities, and the availability of functional departments play a role. A brief joint walkthrough of a critical process chain provides a more robust planning basis than a one-size-fits-all duration based on user count. A fixed time or price commitment cannot be inferred from the product name alone.

Sources: [2] [7] [6]

Must every upgrade be revalidated?

Not at all. Evaluate the change, its effects and the validity of the existing evidence. From this you derive targeted tests, for example for affected adaptations, material bookings or interfaces. Also document why non-affected evidence can be used further. The fact that individual adjustments are technically retained does not replace this technical change decision.

Sources: [2] [6]

Sources and review date

The basis is the officially published abas product pages and primary regulatory sources opened on 6 October 2026. Public descriptions do not replace version-specific help or agreements regarding the scope of delivery. A comprehensive GMP audit trail and a universal material release logic are therefore not substantiated. Tables and test cases are proposed suggestions for your specific configuration.

  1. Abas: ERP system for the industrial mid-market segment
  2. Abas: Personalization
  3. Abas: Warehouse management
  4. Abas: Procurement and Quality Management at the Goods Receiving Point
  5. Abas: Connectivity and IoT
  6. European Commission: EU GMP Annex 11, January 2011 revision
  7. EMA: GMP/GDP Questions and Answers – Annex 11
  8. FDA: Part 11 – Scope and Application
  9. European Commission: EudraLex Volume 4

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Clarify the relevant abas adjustments and gaps in validation evidence

Daniel Herrmann Consulting assists you in translating individual ERP logic, material processes, and existing documentation into a justified inspection need.

  • 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 →