Practical guides · Practical guide

Testing batches, status changes and traceability in SAP Business ByDesign

Which stock can staff actually use, and how can its origin and onward movement be traced? In SAP Business ByDesign, check identified stock, lifecycle status, the Restricted indicator and posting documents together. The examples are based on the Business ByDesign Library 2608 dated 21 August 2026. Verify the behaviour of your own configuration.

Table of contents

At a glance

How do you test batches and stock blocks in ByDesign?

Trace identified test stock from goods receipt through restricted use, a justified status change and delivery. Include unauthorised use, expired stock and corrections, then trace the actual postings forward and backward. Distinguish the lifecycle status of the identified stock from the Restricted indicator on individual stock quantities. Which transactions remain permitted depends on the documented process and configuration.

  • Identified stock is product-specific; a number is not automatically unique across the entire system.
  • Blocked, Obsolete, Expiry Date, and Restricted must not be considered as equivalent mechanisms.
  • Verify the intended restriction effect at the specific withdrawal or distribution pathway.
  • Traceability depends on transaction records and their links. Current stock alone is insufficient.

Record the actual batch identity and product boundary

ByDesign treats batches and lots as forms of Identified Stock. The Library describes a stock that belongs to exactly one product. Depending on configuration, its identifier is unique only to that product; global uniqueness must be explicitly configured and is not pre-defined. Therefore, always link product and stock identifier when describing test data and traceability chains.

Record the Identified Stock type in the product master, how numbers are assigned and the relevant attributes. The documented Batch and Lot types differ from Optional Specified Stock and Mandatory Specified Stock. Check that any example fits the actual type and handling of the product specification.

This article expands on inventory and traceability audits. General ByDesign validation and evaluation of cloud updates are covered in separate knowledge articles. Functionality evidence from S/4HANA or Business One is not transferred here. A similar German field designation does not constitute evidence of identical functionality.

Sources: [1]

Lifecycle status and Restricted separately explain

The library distinguishes the lifecycle states Preparation, Active, Blocked, and Obsolete. In addition, there is the Restricted flag applied to inventory items. In particular, a specific inventory item in the Blocked state may be associated with both restricted and unrestricted inventory. Therefore, a single status field does not capture all possible usage scenarios.

Prepare a concise status overview for your process: What constitutes a professional quarantine, what is a technical usage restriction, and who is authorized to initiate a transition? Define the combination of controls that implements your intended control. The following workflow guide outlines what you should distinguish; it is not a complete SAP transition status matrix.

Also check existing tasks and reservations. Correctly updated master data display alone does not address how an already initiated process continues. Document the exact time of status change and the actual response of the affected process.

Own inspection aid: Different status and inventory information
InformationWhat you should consider separatelyAppropriate test decision
Identified Stock and Product Unique identity of the affected material With which combination is goods securely assigned?
In Preparation or Active Usability of the master data set Is the dataset usable at the correct stage?
Blocked or Obsolete Process-dependent limitation of the identified inventory level Which specific intended use should be prevented?
Restricted Limitation of the respective inventory balance What quantity and which inventory level are affected?
Expiry date Time-dependent usability Does the control function operate even in the absence of a visible status change?
Logistics Department and Reservation Location and availability for the requested procedure Is the product actually usable at the intended location?

Sources: [1]

Verify the traceability of goods receipt and identity takeover

An identified inventory balance may, according to the supplier, originate initially as a master data record, during migration, or upon receipt confirmation. Upon entry in the verification process, activation occurs automatically at the end of the entry. No professional quality release may be inferred from this: technical activation and your quality decision address distinct questions.

Prepare deliberately similar test datasets. Verify the assignment of product, internal identifier, supplier identifier, and relevant date information. Then track the appearance of the goods in the relevant logistics area and with associated inventory information. A subsequently corrected designation is not a substitute for correct documentation linkage at receipt.

Select the variants based on your actual workflow: full receipt, partial receipt, mismatched identification, and rejection of a defective confirmation. Define the expected outcome and responsible handler for each scenario. If a review plan or quality inspection is involved, explicitly incorporate its impact, rather than assuming the same status progression for all receipts.

Sources: [1] [2]

Demonstrate the restriction on the intended use

Blocking is not a universal movement restriction. The ByDesign documentation permits certain activities for locked, obsolete, or expired identified stocks, including internal movements, scrapping, and stock adjustments. Therefore, the ability to move a product into a quarantine area does not automatically indicate a system failure.

Define the required condition at the technically decisive point: An unverified batch may not be dispatched to a customer via the intended distribution route. A controlled transfer within the warehouse may concurrently be permissible. Test both scenarios separately using the actually employed process and the intended user permissions.

The source and target verification in logistics considers several factors. SAP explicitly limits the verification described there for an unblocked, identified inventory to standard outbound processes. Therefore, separately evaluate alternative paths, manual selections, cancellations, and integrated applications. A successfully blocked standard case does not automatically cover such variants.

Sources: [1] [2]

Status change for decision and authorization binding

The regulatory examples relate to human medicinal product GMP. Annex 11 is the GMP guideline for computerised systems; the extent of controls is justified based on usage and risk assessment. FDA Part 11 must be evaluated additionally when electronic use and record retention requirements are applicable. Other industries and legal domains require separate assessment.

Determine which evidence justifies a status change and which role is authorized to perform it. Assess a legitimate modification and a trial conducted without the intended authorization. Also evaluate future traceability: which inventory balance was affected, what decision underpinned the action, and where is the relevant record retained? You must review the technical history within your system.

Active is not a blanket verification of a legally regulated batch certificate. For finished pharmaceutical products, Annex 16 distinguishes between quality testing, certification by a qualified person, and transfer to sellable stock. If your process includes such steps, you must provide specific validation evidence for their implementation. The activation of an identified stock data record does not automatically assume this responsibility.

Sources: [2] [3] [4] [5] [1]

Treat expired goods and corrections as separate variants.

SAP describes the expired identified inventory functionally as blocked, without automatically updating the visible lifecycle status to blocked. Therefore, a test that solely checks for this status would not adequately evaluate the time-dependent mechanism. Verify the actual process using an appropriately selected date.

Pre-determine which date is relevant and how borderline cases are treated in the operational process. Use controlled test data before and after this time. Determine the environment, date setting and expected processing. This will identify whether you have tested a date rule or just a random selection decision.

Withdrawals, customer returns and internal movements may follow different rules from a new standard delivery. Trace a correction relevant to your business from the document to the restored stock. SAP also identifies limits on automatic stock category changes for externally managed warehouses. A ByDesign display alone cannot confirm that a logistics provider has applied the same status.

Sources: [1] [2]

Verify origin and transfer based on actual events.

The Library describes the navigation from the Identified Stock Overview to confirmations and production batches. Through this navigation, the usage of consumed in-process materials can be traced. For your review, the actually confirmed usage is relevant. A planned batch list shows the intended composition but does not indicate which material was actually used in the investigated process.

Build a manageable test data set with distinct incoming stocks, a processing step, and multiple possible downstream pathways. Define the expected mapping independently of the subsequent screen display. Then trace backward from the final product to its origin, and forward from an incoming stock to known downstream records.

Evaluate the scope of the statement: Are only current quantities visible, or are also previously expired goods included? Should cancelled or corrected transactions be included in the analysis? Which relationships are preserved during a system transition? A complete hit list for your pre-defined data constitutes concrete validation evidence. However, this does not imply a general guarantee of complete traceability for any historical event.

Sources: [1] [2]

Review the Confirmation Journal and interfaces technically and professionally.

The Confirmation Journal documents verified movements and quantity changes. Its presentation depends on the selected attributes: for example, removing the confirmation number allows multiple transactions to be consolidated into a single line. Therefore, a condensed list may indicate a different level of aggregation and does not necessarily imply missing bookings.

Ensure that your test filter, time period, used attributes, and required documentation navigation are defined. Compare confirmations, reversal entries, and remaining balances. Pay attention to units and meaning when dealing with quantities: a confirmed quantity and its balance impact are not necessarily equivalent across all displays. The current inventory overview does not replace the review of movement history.

When integrated with a scanner, a warehouse service provider, or another system, an additional handover step is introduced. As targeted failure scenarios, test a foreign product identifier, a duplicate confirmation, and a missing confirmation. Crucially, determine whether the affected dataset is correctly assigned and whether a discrepancy remains resolvable. These suggestions do not constitute a guaranteed error handling mechanism for a specific ByDesign interface.

Sources: [1] [2]

Example: From receipt to delivery

The following example does not describe completed product testing. A product receives two distinct incoming batches, A and B. Batch A has been technically evaluated and approved for the intended process flow, while for batch B, the required decision remains pending. A subset of batch A will be further processed, and the resulting finished product will be released.

Define for B first the desired lock mechanism of your configuration. Verify both an unauthorized release attempt and an authorized internal transfer. Only change the status after the planned test validation and with the correct role. Then perform a controlled positive workflow. This ensures visibility into whether identity, decision, and actual usage are aligned.

Finally, document the origin of the supplied starting material and the known uses of A. B must not inadvertently appear as a used material. Deviations shall be recorded with "Required," "Actual," "Evidence," and affected function, and shall be professionally assessed. A technical notification may indicate an expected negative test result; it is not automatically considered a product defect or a formal CAPA.

Example: internal test matrix for stocks A and B
Test stepExpected result set in advanceSuitable evidence
Goods receipt and assignment A and B unequivocally belong to the correct product. Goods receipt document, identifiers and stock display
Unauthorized use of B The defined distribution pathway prevents unexplained goods. The role used for the test, the process step and the observed response
Permitted internal reallocation Controlled movement does not inadvertently alter the release significance. Source and target documents, status and stock indicator
Rationale for status change Only the intended role affects the relevant inventory. Decision rationale and observed change
Positive Use and Distribution The reconciled stock is linked to the correct subsequent document Approval, subsequent product and delivery document
Forward and backward verification Expected relationships are complete; B is not incorrectly assigned. Journal view, filter, and traceable audit trail

Sources: [1] [2]

Test scope, participation, and practical closure planning

To initiate the process, you require a documented material route, the production configuration, and appropriate test data. Inventory, production or shipping, QA, and ByDesign responsibility holders should be able to jointly explain the significance of the used states. A implementation partner can assist with technical limitations; the desired process restriction is determined by your process owner.

Effort arises primarily due to different logistics models, external warehousing, historical data, and unclear stockholding relationships. Initially plan the variants with relevant failure consequences. Enhance the final decision with remaining restrictions and responsibility for future changes. A new numbering sequence, a modified role, or a changed integration can also have impacts on this review, even in the absence of a new product attribute.

  • Record the SAP Business ByDesign release, test environment and relevant configuration.
  • Product, identified stock type, and uniqueness rule of the identifier defined.
  • Lifecycle status, Restricted and professional release significance explained separately.
  • Goods receipt, authorized internal movement and prohibited use selected.
  • Authorized and unauthorized test roles prepared.
  • Expiry date, corrections, and external transfers considered on a risk-based basis.
  • Expected traceability relationships independent of the report description.
  • Journalfilter, document markers, quantities and units clearly traceable and securely verified.
  • Deviation evaluation, final decision, and responsible party for changes designated.

Sources: [2] [1]

Project experience and collaboration

Verify batch status and traceability against the underlying records

With your process owners, we choose a ByDesign process that connects batch identity, quality status and actual use. We test traceability and the effects of status changes through the relevant handovers. Where master data and responsibilities are clear, focused tests may suffice. Otherwise we resolve those points before testing. For each case, we record source evidence, the expected change in status and quantity, and the records needed to demonstrate it.

Frequently asked questions about Batch management in ByDesign

Are Batch and Lot functions in ByDesign equivalent to those in S/4HANA or Business One?

This assumption should not be adopted. The evaluated ByDesign Library 2608 defines Batch and Lot as Identified Stock types with distinct rules. For the inspection scope, the product lineage, selected type, and specific process apply. Similar terms in other SAP products do not indicate identical status transitions, nor do they confirm equivalent interfaces or traceability pathways.

Sources: [1]

Does the identified stock ID serve as a unique batch identifier?

Product-wide, only if system-wide uniqueness is established. By default, the identifier within a product is unique. Include product and inventory identifier in your inspection documentation. Specifically review exports and external transfers that omit product reference, as this could lead to incorrect consolidation of different inventory batches.

Sources: [1]

Does Blocked mean that no movement at all is possible with the batch?

No. The documentation allows certain internal movements, scrapping, and inventory changes even under restricted lifecycle states. Therefore, separately evaluate the professionally prohibited usage, such as your distribution route, distinct from authorized inventory transactions. A successful transfer into a controlled area is not automatically considered a block error. What is decisive is the pre-established required state of your specific process flow.

Sources: [1]

Is Restricted equivalent to the lifecycle status Blocked?

No. One describes inventory information, the other describes the status of the identified inventory. SAP clarifies that "Blocked" may be associated with either restricted or unrestricted inventory. Document the combination intended for your quarantine procedure and verify its impact in the target process. A single indicator should not be used to derive a complete release or block decision.

Sources: [1]

Will expired inventory be automatically flagged as "Blocked"?

The evaluated documentation describes a treatment scenario similar to "Blocked" status, without correspondingly updating the visible lifecycle status. Therefore, verify actual usage with appropriate test data and date settings. A comparison of displayed status alone cannot serve as valid control evidence. The allowable processes must be assessed separately for each process based on the expiry date.

Sources: [1]

Is the activation of an identified stock already equivalent to pharmaceutical batch release?

The activation initially makes the master record dataset accessible within the described technical context. This does not constitute a legally mandated certification of a finished pharmaceutical product. Annex 16 outlines specific responsibilities and procedural steps for such certification. When ByDesign is implemented within your release process, verify the specific linkage to decision-making, role assignment, and documentation. An active status alone does not establish these requirements.

Sources: [1] [5] [2]

Does the Stock Overview provide sufficient evidence for traceability?

The current stock record alone does not demonstrate the complete historical material pathway. Utilize relevant certifications, production and delivery records, as well as the Confirmation Journal. Review the origin and onward transfer of previously known test data. Document filters and display parameters to ensure a subsequent reviewer understands the actual processes included in the evaluation.

Sources: [1]

Why does the Confirmation Journal display fewer rows after a layout change?

The journal can summarize records based on the selected attributes. When the confirmation number is hidden, multiple activities may appear in the same row. Therefore, fewer rows do not necessarily indicate data loss. Verify the filters, grouping settings, and required documentation attributes, and compare the underlying activities. For your review, the necessary level of detail must be retained.

Sources: [1]

What data and stakeholders do we need prior to test start?

Prepare distinct products or stock items, appropriate status and date variants, as well as anticipated downstream relationships. QA, storage, production, or shipping personnel, along with the ByDesign responsible parties, should jointly define the desired workflow. For external storage or scanning operations, relevant partner stakeholders should be included. An appropriate test environment and a documented configuration state ensure that unexplained discrepancies do not render the test unworkable.

Sources: [2] [1]

How do we determine resource requirements and manage deviations?

The key drivers include process variations, external inputs, data quality, and required historical linkages. Start with a defined material pathway and expand based on relevant risks. Document the required, actual, and relevant supporting evidence. Assess deviations based on their impact to the intended use; not every expected error message constitutes a defect, and not every technical deviation necessitates automatic escalation.

Sources: [2]

Sources and review date

The technical statements refer to the SAP Business ByDesign Library 2608 dated 21 August 2026, retrieved on 6 October 2026. Configuration, process variants, and external warehouses are to be assessed separately. Examples and tables are provided as internal audit aids; a specific installation was not tested.

  1. SAP Business ByDesign Library 2608: Identified Stock and Stock Verification
  2. EU GMP Annex 11: Computerised Systems
  3. European Commission: EudraLex Volume 4
  4. FDA: Part 11 — Scope and Application
  5. EU GMP Annex 16: Certification by a Qualified Person and Batch Release

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Prepare the specific inventory and traceability test in detail

Daniel Herrmann Consulting supports you in integrating professional blocking rules, ByDesign configuration, and the required traceability chains into a verifiable inspection scope.

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