Batch History - Enhanced Manufacturing Functionality with SAP ERP 6.

0 EHP 4

Navaneeth AN, Solution Management, Manufacturing, SAP Labs India Jrgen Wettengl, Solution Management, Manufacturing, SAP AG 02. February 2009

Present Situation

Customers store the batch related information: in different SAP ERP systems, Example: In one SAP ERP system the batch was produced and delivered to another SAP ERP system in which the packaging takes place and the delivery to the customer. in SAP ERP systems and non SAP systems with different levels of granularity, Example: Higher data granularity in the ERP systems e.g. the batch characteristics relevant for the batch determination in the ERP processes and very detailed data granularity in LIMS or MES systems like the process parameters a batch was produced with (e.g. temperatures, etc.).

SAP 2009 / Batch History Ehp4 release/ Page 2

Problem Statement

To get the complete history data for a batch with all details it is necessary to go to different systems, different reports and transactions. There is a high fault probability to consider all relevant objects and transactions in the different systems manually. Even if there is only one SAP ERP system used.

Scenarios
Case A: One ERP System Case B: Multiple ERP Systems Case C: One ERP Systems / Multiple Non SAP Systems (Shop Floor Systems) Case D: Multiple ERP Systems / Multiple Non SAP Systems (Shop Floor Systems)

SAP 2009 / Batch History Ehp4 release/ Page 3

Legal Requirement EU GMP 9 Guideline

The companies must take legal requirements regarding "good manufacturing practice" into account. An example from the EC Guide to Good Manufacturing Practice for Pharmaceuticals (EU-GMP 9): The manufacturer shall have a system of documentation based upon specifications, manufacturing formulae and processing and packaging instructions, procedures and records covering the different manufacturing operations that they perform. Documents shall be clear, free from errors and kept up to-date. Pre-established procedures for general manufacturing operations and conditions shall be available, together with specific documents for the manufacture of each batch. This set of documents shall make it possible to trace the history of the manufacture of each batch. The batch documentation shall be retained for at least one year after the expiry date of the batches to which it relates, or at least five years after the certification referred to in Article 30 (2) of Directive 81/851/EEC, whichever is the longer. When electronic, photographic or other data processing systems are used instead of written documents, the manufacturer shall have validated the system by proving that the data will be appropriately stored during the anticipated period of storage. Data stored by these systems shall be made readily available in legible form. The electronically stored data shall be protected against loss or damage of data (e.g. by duplication or back-up and transfer onto another storage system).

SAP 2009 / Batch History Ehp4 release/ Page 4

Definition
Batch History

Functionality to display all the set of documents for a specific batch with holistic information to trace the history of a batch.
Usage
Compliance to Legal requirement GMP Guideline Defect Tracing Product Recall Regression Analysis

SAP 2009 / Batch History Ehp4 release/ Page 5

Agenda

1. 2. 3. 4. 5. 6. 7.

Definition and Usage Batch Information Cockpit Architecture Batch History - Process Steps Implementing Batch History Enhancement Planned in Future Releases Potential Benefits and Summary

SAP 2009 / Batch History Ehp4 release/ Page 6

BASF AG User Report on Implementing the Batch Information Cockpit (BIC)

Stephanie Hgel BASF IT Services Armin Eisenhauer BASF AG

The Batch Information Cockpit (BIC) is a central control panel with extensive, batch-specific analysis and control options that take the strain out of batch management. There are two different user groups, each with different selection criteria, for accessing the BIC. This ensures that the user is only presented with that data that is relevant for a particular decision.

SAP 2009 / Batch History Ehp4 release/ Page 7

Application Example: Selection Screen

SAP 2009 / Batch History Ehp4 release/ Page 8

As of SAP Enterprise, selection criteria for a user group can be stored using a selection variant. This means that it is no longer necessary to enter the selection criteria manually for each selection.

The Batch Information Cockpit provides the user with concrete support when dealing with the following issues: Analysis of slow-moving items / remaining shelf life in the warehouse Availability to promise (ATP) check, with a display of active ingredient quantities Analysis by different batch characteristics: Dutiable goods stock Palletization, container number Usage decision quality control Quality characteristics, such as type-related / not type-related Batch specification suitable for customer / not suitable for customer Batch specification suitable for country / not suitable for country Which batches are provided by which suppliers?
8

Application Example: Results for batch selection and its stock

SAP 2009 / Batch History Ehp4 release/ Page 9

As of SAP Enterprise, selection criteria for a user group can be stored using a selection variant. This means that it is no longer necessary to enter the selection criteria manually for each selection.

The Batch Information Cockpit provides the user with concrete support when dealing with the following issues: Analysis of slow-moving items / remaining shelf life in the warehouse Availability to promise (ATP) check, with a display of active ingredient quantities Analysis by different batch characteristics: Dutiable goods stock Palletization, container number Usage decision quality control Quality characteristics, such as type-related / not type-related Batch specification suitable for customer / not suitable for customer Batch specification suitable for country / not suitable for country Which batches are provided by which suppliers?
9

Application Example: Selection of follow up actions

Conversion of unrestricted batch stock to blocked stock :

SAP 2009 / Batch History Ehp4 release/ Page 10

As of SAP Enterprise, selection criteria for a user group can be stored using a selection variant. This means that it is no longer necessary to enter the selection criteria manually for each selection.

The Batch Information Cockpit provides the user with concrete support when dealing with the following issues: Analysis of slow-moving items / remaining shelf life in the warehouse Availability to promise (ATP) check, with a display of active ingredient quantities Analysis by different batch characteristics: Dutiable goods stock Palletization, container number Usage decision quality control Quality characteristics, such as type-related / not type-related Batch specification suitable for customer / not suitable for customer Batch specification suitable for country / not suitable for country Which batches are provided by which suppliers?
10

Agenda

1. 2. 3. 4. 5. 6. 7.

Definition and Usage Batch Information Cockpit Architecture Batch History - Process Steps Implementing Batch History Enhancement Planned in Future Releases Potential Benefits and Summary

SAP 2009 / Batch History Ehp4 release/ Page 11

11

Architecture A One SAP ERP system

SAP ERP System A

Batch Related Objects (Create/ Change)
Batch Master Goods Movement Prod Order Inspection Lot Inspection result Usage Decision QM Notification Quants Sales Order Delivery

Update via Pull Principle

Batch History Index table

Read

Batch Information Cockpit Display Batch History

SAP 2009 / Batch History Ehp4 release/ Page 12

12

Architecture B One SAP ERP system and multiple Non SAP systems

SAP ERP System A

Non-SAP
Shopfloor System X

Batch Related Objects (Create/ Change)

Batch Master Goods Movement Prod Order Inspection Lot

Update via Pull Principle

Batch History Index Table

Read

SAP MII
Update

Batch Related Objects

Work Order Goods Mvt.

Service Call
Shopfloor System Y
Batch Related Objects Work Order Goods Mvt.

Batch Information Cockpit Display Batch History

SAP 2009 / Batch History Ehp4 release/ Page 13

13

Architecture C Multiple SAP ERP system and multiple Non SAP systems
SAP ERP System A
Batch Related Objects (Create/ Change)
Batch Master Goods Movement Prod Order Inspection Lot

Non-SAP
Shopfloor System X
Batch History Index Table
Batch Related Objects Work Order Goods Mvt.

Update via Pull Principle

SAP MII
Update

Read Batch Information Cockpit Display Batch History

Service Call

Shopfloor System Y
Batch Related Objects Work Order Goods Mvt.

Read SAP ERP System B

Batch Related Objects (Create/ Change)
Batch Master Goods Movement Prod Order Inspection Lot

Non-SAP
Shopfloor System X1
Batch Related Objects Work Order Goods Mvt.

Update via Pull Principle

Batch History Index Table

SAP MII
Update

Read Batch Information Cockpit Display Batch History

Service Call

Shopfloor System Y1
Batch Related Objects Work Order Goods Mvt.

SAP 2009 / Batch History Ehp4 release/ Page 14

14

Agenda

1. 2. 3. 4. 5. 6. 7.

Definition and Usage Batch Information Cockpit Architecture Batch History - Process Steps Implementing Batch History Enhancement Planned in Future Releases Potential Benefits and Summary

SAP 2009 / Batch History Ehp4 release/ Page 15

15

Main Features

The main functions of the batch history application are as follows: Activate the batch-related object types (SAP/non-SAP systems) to update the index table. Assign Batch History selection tab and selection of the relevant batch-related object types based to a user group. Restart Batch Information Cockpit for required user group. Display the complete batch history data with options to sort by create/change date. Follow-up actions based on the displayed batch-related object types. Print the batch history.

SAP 2009 / Batch History Ehp4 release/ Page 16

16

Process Steps Display Batch History

Batch Information Cockpit (Transaction : BMBC) Restart BMBC with user group where in Batch History functionality is enabled Flexible selection of batches on the basis of material-, batch-, stock-, SLED- as well as classification-data (e.g. characteristics like viscosity or density, status of classification)

Execute or F8

e.g. Material is entered for Batch History search

SAP 2009 / Batch History Ehp4 release/ Page 17

17

Process Steps Batch History Selection Screen

Batch History Tab Page in Batch Information Cockpit
Batch Related Object Types (SAP/nonSAP) display dependent on the customizing settings for object types/user group combination Evaluation Period for which the history details of a batch have to be considered Valid Plants selection for having same BRO types search across all plants for displaying batch history Cross Systems checkbox if flagged, the history details of a batch are tracked from more than one SAP systems Movement Type filter used when Material Document object type is flagged

SAP 2009 / Batch History Ehp4 release/ Page 18

18

Process Steps Display Batch History

List of Batches is displayed on the left pane for the Material Search Right Click on the Batch and you will find Batch History functionality entry Batch History Details screen has header information and the batch object types details

SAP 2009 / Batch History Ehp4 release/ Page 19

19

Process Steps Follow Up Action

Right click on the batch object types will provide the follow up actions maintained for detailed analysis
SAP 2009 / Batch History Ehp4 release/ Page 20

20

Process Steps Follow Up Action

New Window showing the follow up (e.g., sales order) information

SAP 2009 / Batch History Ehp4 release/ Page 21

21

Process Steps Batch History details from different ERP systems

Cross System check box to be checked if same batch information is maintained in different ERP system as well

SAP 2009 / Batch History Ehp4 release/ Page 22

22

Process Steps Batch History details from different ERP systems

User would have to enter login credentials to another ERP system if he has authorization

SAP 2009 / Batch History Ehp4 release/ Page 23

23

Process Steps - Batch History details from Non SAP Batch Related Object Types

Customer defined object type check box to be checked if batch information is maintained in non SAP system as well

Information from non SAP system

SAP 2009 / Batch History Ehp4 release/ Page 24

24

Process Steps - Batch History details from Non SAP Batch Related Object Types

Note: Batch History information from non SAP system is delivered as a working example using SAP MII in SDN (not part of Ehp4 release) SDN Article Batch History: How to Guide on getting Batch information from non SAP systems using SAP MII
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/208239ac-3161-2b10-f29a-abec6754942e
SAP 2009 / Batch History Ehp4 release/ Page 25

25

Process Steps Index Table (Pull Principle) : Performance Improvement

Requirement being batch information is obtained from different SAP and non SAP systems -> impacts performance delivery
VBAK VBAP EKKO AFPO .

Index Table
Defining Batch Related Object types (definition of the key, description, defining the attributes etc) Activate/Deactivate the batch related object types Pull Principle - To populate the index table, that is the report program will pull data from the various BRO type tables (SAP/nonSAP) Batch History functionality will retrieve information from the index table Batch History analysis will not retrieve information from the individual batch related object record table

RVBOBJTABUPD
This program will be run to query all object type related db tables and then store the data in the index table

TOBJ_INDEX

SAP 2009 / Batch History Ehp4 release/ Page 26

26

Features Display Batch History

Batch History header information Minimize/Maximize Header/ALV Grid

SAP 2009 / Batch History Ehp4 release/ Page 27

27

Features Display Batch History

ALV Grid Features

Sort Ascending

Filter

Print

Sort Descending
SAP 2009 / Batch History Ehp4 release/ Page 28

Export Options e.g., spreadsheet

28

Features Batch History Print Option

Print

Print Report will contain Header information and Batch History Details table

SAP 2009 / Batch History Ehp4 release/ Page 29

29

User Authorization
User-group specific selection screen view
Unique selection screen for user groups, containing specific Batch Related Object Types

Different ERP systems

For Batch History details from different ERP systems, user should have necessary authorizations
SAP 2009 / Batch History Ehp4 release/ Page 30

30

Activate Batch History Business Function

Stable Core Basis SAP ECC 6.0 (ERP 2005), Enhancement Pack 4 Activate customizing for Batch History per business function

Active (bulb glows) Business Function

Documentation Release Information

Test Case

SAP 2009 / Batch History Ehp4 release/ Page 31

31

Agenda

1. 2. 3. 4. 5. 6. 7.

Definition and Usage Batch Information Cockpit Architecture Batch History - Process Steps Implementing Batch History Enhancement Planned in Future Releases Potential Benefits and Summary

SAP 2009 / Batch History Ehp4 release/ Page 32

32

Implementing Batch History

1.

In Customizing Logistics General -> Batch Management -> Batch Information Cockpit -> Define user-group-specific selection -> Maintain a user group

SAP 2009 / Batch History Ehp4 release/ Page 33

33

Implementing Batch History

2.

Choose a user group and navigate to selection tab title where you assign the selection tab Batch history to the user group, check the active flag and save the same.

SAP 2009 / Batch History Ehp4 release/ Page 34

34

Implementing Batch History

3.

In Customizing Logistics General -> Batch Management -> Batch Information Cockpit > Batch History -> Define BRO types and Parameters (check the active flag and define SAP Table and key fields)

Note: For non SAP BRO type, External Box need to be flagged as well
SAP 2009 / Batch History Ehp4 release/ Page 35

35

Implementing Batch History

4.

Select the BRO type (BAHMAS) and navigate to the user groups and assign a user group..similarly for all BRO types

SAP 2009 / Batch History Ehp4 release/ Page 36

36

Implementing Batch History

5.

For the same BRO type (Batch Master) navigate to the events and define the events for the same .

SAP 2009 / Batch History Ehp4 release/ Page 37

37

Implementing Batch History

6.

For the BRO type/ event combination, define the attributes.

SAP 2009 / Batch History Ehp4 release/ Page 38

38

Agenda

1. 2. 3. 4. 5. 6. 7.

Definition and Usage Batch Information Cockpit Architecture Batch History - Process Steps Implementing Batch History Enhancement Planned in Future Releases Potential Benefits and Summary

SAP 2009 / Batch History Ehp4 release/ Page 39

39

Planned enhancements in next (Ehp5) release

Implementing Batch History functionality with Push Method approach Archiving Batch History Index Table Batch History details display from Archived Table Invoking Batch History functionality from Batch Where Used List Defining additional Batch Related Object Types (e.g., Shift Notes, WIP Batch, Handling Unit)

SAP 2009 / Batch History Ehp4 release/ Page 40

40

Agenda

1. 2. 3. 4. 5. 6. 7.

Definition and Usage Batch Information Cockpit Architecture Batch History - Process Steps Implementing Batch History Enhancement Planned in Future Releases Potential Benefits and Summary

SAP 2009 / Batch History Ehp4 release/ Page 41

41

Potential Benefits

The functionality provides one transaction and flexible environment for selection of relevant batch related object types for batch history search from SAP and non SAP systems It provides better end user satisfaction by removing high fault probability in obtaining batch information from various systems The functionality is in Compliance with Good Manufacturing Practice guideline requirement for tracing the history of manufacture of each batch

SAP 2009 / Batch History Ehp4 release/ Page 42

42

Summary

Batch History Functionality is to display all the set of documents for a specific batch with holistic information to trace the history of a batch. Functionality resides in Batch Information Cockpit (BIC), central control panel with extensive, batch-specific analysis and control options that take the strain out of batch management. Functionality is widely applicable across all manufacturing industries (process and discrete) Functionality is widely used to support
Compliance to Legal requirement GMP Guideline Defect Tracing Product Recall Regression Analysis

SAP 2009 / Batch History Ehp4 release/ Page 43

43

Info/additional requirements regarding Batch History functionality

Contacts: Stephan Haehre (stephan.haehre@sap.com) Jrgen Wettengl (juergen.wettengl@sap.com) Navaneeth AN (navaneeth.an@sap.com)

SAP 2009 / Batch History Ehp4 release/ Page 44

44

Copyright 2008 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned and associated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrckliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen knnen ohne vorherige Ankndigung gendert werden. Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte knnen Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwhnte SAP-Produkte und Services sowie die dazugehrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Lndern weltweit. Alle anderen in diesem Dokument erwhnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte knnen lnderspezifische Unterschiede aufweisen. Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthlt nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP-Produkts und ist fr SAP nicht bindend, einen bestimmten Geschftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP bernimmt keine Verantwortung fr Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollstndigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewhr, weder ausdrcklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschlielich, hinsichtlich der Gewhrleistung der Marktgngigkeit und der Eignung fr einen bestimmten Zweck sowie fr die Gewhrleistung der Nichtverletzung geltenden Rechts. SAP bernimmt keine Haftung fr Schden jeglicher Art, einschlielich und ohne Einschrnkung fr direkte, spezielle, indirekte oder Folgeschden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschrnkung gilt nicht bei Vorsatz oder grober Fahrlssigkeit. Die gesetzliche Haftung bei Personenschden oder die Produkthaftung bleibt unberhrt. Die Informationen, auf die Sie mglicherweise ber die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP untersttzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewhrleistungen oder Zusagen ber Internetseiten Dritter ab. Alle Rechte vorbehalten.
SAP 2009 / Batch History Ehp4 release/ Page 45

45