Name: Exploring Electronic Batch Record (EBR) in SAP Digital Manufacturing – PET 2026
Uploaded: 2026-5-11
Duration: 1401 s

Share feedback

<p>We are aware of intermittent issues in accessing the learning content</p>

We are aware of intermittent issues in accessing the learning content

Personalize your learning.

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

This browser is not supported

Please try again later

Sorry, we encountered an error

Try again or reset results to continue browsing

We didn’t find what you’re looking for

To continue, please log in

Your session has timed out

Validate your skills and learning by completing the certification exam and gain a highly recognised accreditation.

Book your certification exam

Complete the assessment to validate your SAP PartnerEdge competency qualifications.

Ready to take your assessment?

Learn about the key features and essentials in the latest release to help you prepare for the Stay Certified assessment.

Prepare for assessment

Learn new skills you need at your own pace with our bite-sized lessons.

Prepare for certification

In your My Learning account you can view your certification and learn how to take your Stay Certified assessment.

Ready to take your Stay Certified assessment?

Explore {title} at SAP Learning. Find out more!

Assessment

Course Completion

Knowledge Badge

Overview

Support Resource

Certification Exam

Theoretical Exam

Schedule

External Course

Practical Exercise

Practical Test

External Hands-On

External Resource

Learning Journey

Learning Journey Assessment

Lesson

Live Session

Practice System

Quiz

Scenario Based Assessment

Course Assessment

Course

Stay Certified

Subscription

System Based Assessment

Test Out

Unit

Video

Video Playlist

Week

Want to remove this from your Learning List?

Your exclusive access to the SAP Learning Hub, event edition is ready. <link>Start learning now.</link>

Access activated

You can now register for free Live Sessions.

<div><div><div><div><div><div><div><div><div><div>SAP Business Suite Product Expert Training (PET) H1 2026 / Plan to fulfill / SAP Business Technology Platform / Supply Chain Management / SAP Digital Manufacturing / Electronic Batch Record (EBR) /  eDHR (Electronic Device History Record)<br><br>In this video, you will explore the latest Electronic Batch Record (EBR) and eDHR (Electronic Device History Record) capabilities introduced in release 2605, designed to enhance traceability, streamline digital record execution, and strengthen regulatory compliance and confidence.<br><br>Ask your questions in our <a target="_blank" rel="nofollow noopener noreferrer" href="https://community.sap.com/t5/enterprise-resource-planning-q-a/qa-p/erp-questions">community</a> using the  PET_Enablement tag under “Question User Tags.” <br><br>Here you can find the <a target="_blank" rel="nofollow noopener noreferrer" href="https://d.dam.sap.com/a/hioikRh/PET-H1-2026_EBR.pdf?rc=10&inline=true&doi=SAP1311391">slide deck</a>. <br><br>Please note that captions have not been edited.</div></div></div></div></div></div></div></div></div></div>

Exploring Electronic Batch Record (EBR) in SAP Digital Manufacturing – PET 2026

Welcome to this product expert training within SAP, where today within Digital Manufacturing we will focus on the electronic batch record. Following the regular disclaimer, my name is Antoine Gerritsen and I'm a product expert within SAP Digital Manufacturing. We will focus in on the plan to fulfill end-to-end process and the manufacturing parts, zooming it into the electronic batch record where we will look at the electronic batch record context the electronic batch records design within sap that you're manufacturing followed by a demonstration of the 2605 solution and a look ahead to what's to come within sap on the electronic device history record challenges related to electronic batch records in the market are often around meeting quality and compliance needs often a paper and manual process that is risk and error prone and we see in the market a higher number of batches and long release cycles with heavy documentation effort the electronic batch record is intended to simplify this process and reuse the time and build a digital audit trail and record of the production process where it is intended to capture all the execution evidence, manage the data and documents that I have contributed to this record, and provide a document-based solution to you that is GMP compliant, where we execute a Weaver and a release workflow supported by e-signatures, and that way build an audit trail where we also provide a summary reward if we desire to conclude the electronic batch record release. looking at the context of the electronic batch record within SAP we have a operational scope a technical scope and a functional scope where today we will zoom in on the functional scope that comprises several aspects but today we will mainly look at the electronic batch record the electronic batch record within SAP is based on a lot of legal background for example based on FDA 21 CFR part 11 and EU GMP that has been investigated thoroughly to build a solution that is intended to support your regular compliance the electronic batch records fits in a larger process where initially there is a definition of a master batch records that defines the execution process based on S/4HANA data and amended with additional information like work instructions and relevant data collections and process set points that need to be collected that could be recorded in a master batch record then in operations the process gets executed data gets collected work instructions are used and all kinds of records are collected and electronic signatures are gathered in the process Quality is being managed from that point onwards, of course, with the review processes involved. And overall, like I said, e-signatures are really important to capture the audit trail. In the execution process, you might have seen some non -conformances and deviations where the review by exception process uses e-signatures to guide you through that review process and build an audit trail for each non-conformance. Alerts can happen and can be monitored and managed to manage your production and provide visibly and support cop-up processes for your organization. And subsequently, the electronic batch record, or for discrete device history, the electronic device history record in future can be used to create complete EBRs that capture all the evidence from the execution in a document -based fashion and is supported by a review and release process that has a basis in e-signatures. So with that, an electronic batch record is a digital version of a paper batch record and is a record that captures and tracks all the data and documents related to a production process to support compliance in regulated industries. So let's dive deeper into the electronic batch record. As mentioned, it is intended to be a flexible document -driven record solution to support GMP compliance and a review and approval process that is built in part to the dough. EPRs are then created and can be managed within SAP Digital Manufacturing, taking into account the scope of the execution process the there is a review and approval workflow that can build a extensive audit trail documents are the basis for this electronic batch record to have a non -changeable format in which they are stored and the benefit is also it is built within pod to the dough so any extensibility can possibly be used to enhance it for your use, where there's still also a ton of future plans to, for example, auto-generate documents or other items that are to come. Now, putting it into the bigger picture, the electronic batch record is intended to capture the documents during execution so in that respect in the production definition an mbr gets created for example that describes how the process is going to be executed and subsequently in the execution data are collected and work instructions are followed and a review by exception process can be used to look at all the non-conformances and what happens with those and sign up on those with e-signatures all these documents can be loaded into the electronic batch record where within the electronic batch record pod that is available there is a workflow where a electronic batch record will be created under a draft can be completed put under review from there be approved or rejected and if approved goes to a potential to release and if fully released we have completed the full cycle supported by e -signatures there is a option to reject an electronic batch record in the under review or approved stage if it doesn't meet the needs at which point a new version will be created that can be sent through the approval process and workflow again of course there's also a option to cancel an electronic batch record if not needed anymore and that will come also within 2.8605. Furthermore there is a potential future capability where there might be an option to integrate the electronic batch record outcome also towards the batch release hub. So in that respect the review by exception process captures and manages all the non-conformances related to a production process the electronic batch record captures all the relevant documents including the non -conformances related to the execution and production of a material the batch release hub in the whole picture captures the electronic batch record and any other relevant documents to support the batch release broader When we look at the electronic batch record, we will see that there is a summary overview page that is built within Part 2.0 as a template that you can use. In that overview page, you'll see batches with their individual statuses from an EBR perspective, and they will follow the workflow from draft to under review to approved and released as mentioned before to support the for ice principle the roles to execute these stages are set within BTP where in based on those roles one can either execute tasks in draft or under review or under approved and not in the others depending on how those roles are set of course. All this is supported with the e-signature that is available within Digital Manufacturing Pod 2.0. In order to set up the electronic batch record there is a create public EBR that is available where that you can find online. There will also within 26.5 be a production process service that you can select and activate to create the EBR and as mentioned there is a pot to the dough templates available that you can use as a basis for your EBR and hopefully meets all your needs the electronic bet record then itself aside from that overview page digging into an electronic record itself. We'll have some general information about your order, material, and dates next to your batch number and the state of the EBR, has a list of the SSCs, and we'll have a overview of all the documents in the electronic batch record that can be previewed and can be added or removed in a only draft state, where at the end to the right there is a full audit trail that this displays all the e-signatures that have been captured for each state transition in the end a summary report can be created if configured to have a overall summary of all the documents and SFCs and general information as well as the auditory activity log that has been captured during the process now let's look at the electronic batch record in more detail and look at a demonstration before we dig into the demonstration we will that is for the 2605 release make sure to also check out our blog post following the qr code as there is more additional information available there as well as there has been a on 24 what's new webinar that you might be interested to watch as well. So without further ado, let's dig into the electronic batch records and the demonstration available for you as we have released this in 2605. Today, we will look at the electronic batch records. We'll start from the managed pod to do application where we can create an EBR pod from the EBR electronic batch record template. Or we can give it a name and a description and use later the functionalities of the pod 2.0 to also possibly extend it where it required. We will see in the pod designer that there are two pages that make up the EBR that are based on the electronic batch record plugins that are available within pod2.0. We will look at the table widget here where we have a configuration to turn on the or off the automatic generation of the electronic batch record summary report that can be generated upon release if desired and configured. Let's look at the creation of an EBR where we will start from the supervisor role, where we will start with a draft EBR, since it's loaded in a computer pod environment. And as a supervisor we will see a draft EBR for the batch that has general information, order details, material details and dates, as well as the details for the SFCs included in the batch, and an activity log to show the progress and an audit trail with that. The creator can add documents to the EBR as we can see here where we can load files from our laptop or other environment onto the electronic batch record and give them a relevant description we are able to upload pdfs as well as picture formats as can be shown also in this dialog where in this case we'll look at uploading a picture of for example machine settings we can edit the names of the documents or where needed also delete them by selecting them and pressing the remove button if desired however in this case the electronic badge record looks okay for by the creator and he will say it is ready for a review and use e-signature dialogue to place it in the next stage of the review process we will see that the EBR is after the e-signature ready for review which also shows that the supervisor role the creator does not have any other rights with this EBR currently so we'll have to switch to the QA officer roles as assigned in B2B and once we start from the QA officer we have a EBR that is under review that can be reviewed by the QA officer they go through the review process looking at all the details and general information can preview all the documents to make sure that everything is in order. Once all the documents are in order, it could be moving to the next state. However, the QA officer feels that there is a non-conformance document, for example, missing, so can reject the EBR using the e-signature where a comment is required at this point to send it back to the creator, the supervisor, to make the required adjustments and the state change to reject it, upon which the quality officer has no further actions that they can do, at which point we'll see that it is rejected in the overview and action is required. The supervisor role now sees has opened the EBR. They could potentially cancel it, but in this case we're gonna create a new viewer version because there is a document missing. We can always, once created a new version is created, go back and look at the previous versions and find the audit trail and the state of all the documents in that version upon rejection. But in this case, in the current version, we are now still able to, or again, able to add documents to the electronic batch record. So the supervisor can add the missing documents with this additional document add it it looks to be complete so he can send it off for a second trial attempt for the review process towards the QA officer using the e-signature dialogue again the state has changed supervisor can do no other thing other than look at the current and or previous version so we switched to the quality officer environment where we will have this EBR under a version 2 now under review the quality officer can go in look at previous versions and in this case also seeing that all the documents are there they can approve the electronic batch record and send it forwards towards the next stage of review towards release using the e-signature they sign off and again the quality officer can now do not any further actions on this ebr as it is in a status approved and we can switch to the quality manager view to find this ebr that is now under the status approved where the quality manager can open it version 2 approved status can review all the general information and sfcs and documents this time we'll specifically also look at the preview of the picture seeing that it's all okay they could reject or release it in this case we are looking good so the quality manager will release the electronic patch record upon after release of the electronic batch record the quality manager will again not be able to edit anything in the ebr anymore no buttons can be pressed it's in the status released and it's now overall for everybody in a view only state now in this example the configuration initially was turned off to create an ebr summary report if it were turned on the system upon creation of the release ebr would also create this ebr summary report and abstract anything from the ebr template pod template ui and we can see everything also including the audit trail as it's in there being a document that can be shared to other parties interested so far the demo for the electronic batch record Thank you for watching the demonstration of electronic batch record. Now, electronic batch records will be applicable for both this process and discrete industry. However, for discrete industry, there often is also a need for a electronic device history record for each individual device that is produced there. The solution there is solving several similar needs to look at the having a digital record for that specifically vice so you have an audit drill that is document based as well and follows a similar workflow that could be needed so this will be a future capability within sap digital manufacturing that is currently being worked on but wanted to at least present you the overview here to give you look ahead of what that looks like and see what that will turn into later this year. The electronic device history record, similar to an EBR, is a digital version of a paper device history record that captures and manages and tracks all the data related to the manufacturing process of an individual SFC within SAP digital manufacturing and hence supports regulated industries. Similarly to the EBR, it will be a document-driven flexible solution built within POD2 .0 based on a POD2.0 template to create EDHR's review and approve them with a comprehensive audit trail using e-signatures will be document-based and, as mentioned, within POD2.0 to support you there. here you can see some quick screenshots and lab previews of the electronic device history record where in basis we intend to use the similar setup and principles as with the electronic batch record of course in this case focused on the device history record and hence having a focus that it's based on the SFC instead of the batch. So with this preview into the electronic device history record, we are at the end of this session and we would like to thank you for watching this episode. There is a lot more material available to you that you can explore. So feel free to check out these links as displayed on this slide to enable your learning allow you to engage with the community and support the implementation of the SAP solutions. There are several more ways to stay up to date as well if you want to share your feedback with us as well please see the links here or go to the various platforms displayed in the enablement wheel and also check out our community and if you have any feedback or questions please make sure to contact our experts at the displayed email or use the tag PET enablement to ask your questions in the community again thank you for your time and looking forward to present next updates to you in near future