Batch History - archive.sap.com · 1 Batch History - Enhanced Manufacturing Functionality with SAP...

1

Batch History - Enhanced Manufacturing Functionality with SAP ERP 6.0 EHP 4

Navaneeth AN, Solution Management, Manufacturing, SAP Labs IndiaJürgen Wettengl, Solution Management, Manufacturing, SAP AG02. February 2009

2

© SAP 2009 / Batch History – Ehp4 release/

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.).

3


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 SystemCase B: Multiple ERP SystemsCase C: One ERP Systems / Multiple Non SAP Systems (Shop Floor Systems)Case D: Multiple ERP Systems / Multiple Non SAP Systems (Shop Floor Systems)

4


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).

5


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

6


1. Definition and Usage2. Batch Information Cockpit3. Architecture4. Batch History - Process Steps5. Implementing Batch History6. Enhancement Planned in Future Releases7. Potential Benefits and Summary

Agenda

7


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

Stephanie Hügel BASF IT ServicesArmin 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.”

8


Application Example:Selection Screen

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 stockPalletization, container numberUsage decision quality controlQuality characteristics, such as type-related / not type-relatedBatch specification suitable for customer / not suitable for customerBatch specification suitable for country / not suitable for countryWhich batches are provided by which suppliers?

9


Application Example:Results for batch selection and its stock






10


Application Example:Selection of follow up actions

Conversion of unrestricted batch stock to blocked stock :






11



Agenda

12


Architecture A – One SAP ERP system

BatchRelatedObjects(Create/Change)

Batch MasterGoods MovementProd OrderInspection LotInspection resultUsage DecisionQM NotificationQuantsSales OrderDelivery ……

SAP ERP System A

Batch Information Cockpit

Display Batch History

Batch HistoryIndex table

Read

Update via Pull Principle

13


Update

SAP MII

Service Call

Work OrderGoods Mvt.…

BatchRelatedObjects

Shopfloor System X

Non-SAP


BatchRelatedObjects

Shopfloor System Y


Batch MasterGoods MovementProd OrderInspection Lot……

SAP ERP System A



Batch HistoryIndexTable

Read

Architecture B – One SAP ERP system and multiple Non SAP systems


14


Update

SAP MII

Service Call


BatchRelatedObjects

Shopfloor System XNon-SAP


BatchRelatedObjects

Shopfloor System Y

Architecture C – Multiple SAP ERP system and multiple Non SAP systems



SAP ERP System A



Batch HistoryIndex Table

Read




SAP ERP System B



Batch HistoryIndex Table

Read



BatchRelatedObjects

Shopfloor System X1Non-SAP


BatchRelatedObjects

Shopfloor System Y1Update

SAP MII

Service Call

Read

15



Agenda

16


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.

17


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)

e.g. Material is entered for Batch History

searchExecute or F8

18


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

19


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

20


Process Steps – Follow Up Action

Right click on the batch object types will provide the follow up actions maintained for detailed analysis

21


Process Steps – Follow Up Action

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

22


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

23


Process Steps – Batch History details from different ERP systems

User would have to enter login credentials to another

ERP system if he has authorization

24


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

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

25


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 ArticleBatch History: How to Guide on getting Batch information from non SAP systems using SAP MIIhttps://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/208239ac-3161-2b10-f29a-abec6754942e

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

26


Requirement being batch information is obtained from different SAP and non SAP systems -> impacts performance delivery

Index TableDefining 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

Process Steps – Index Table (Pull Principle) : Performance Improvement

VBAK VBAP EKKO AFPO …….

RVBOBJTABUPDThis program will be run to query all object type related db tables

and then store the data in the index table

TOBJ_INDEX

27


Features – Display Batch History

Batch History header information

Minimize/Maximize Header/ALV Grid

28


Features – Display Batch History

Sort Ascending

Sort Descending

Filter Print

Export Options –e.g., spreadsheet

ALV Grid Features

29


Features – Batch History Print Option

Print

Print Report will contain Header information

andBatch History Details table

30


User Authorization

User-group specific selection screen viewUnique selection screen for user groups, containing specific Batch Related Object Types

Different ERP systemsFor Batch History details from different ERP systems, user should have necessary

authorizations

31


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

ReleaseInformation

Test Case

32



Agenda

33


Implementing Batch History

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

34



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.

35



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

36



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

37



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

38



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

39



Agenda

40


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)

41



Agenda

42


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

43


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 panelwith 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 supportCompliance to Legal requirement – GMP GuidelineDefect Tracing Product RecallRegression Analysis

44


Info/additional requirements regarding Batch History functionality

Contacts:

Stephan Haehre ([email protected])

Jürgen Wettengl ([email protected])

Navaneeth AN ([email protected])

45


Copyright 2008 SAP AGAll 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 Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können 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 erwähnte SAP-Produkte und Services sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten 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 können länderspezifische 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 enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.

SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.

Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinkszugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab.

Alle Rechte vorbehalten.

Batch History - archive.sap.com · 1 Batch History - Enhanced Manufacturing Functionality with SAP...

Documents

Transcript of Batch History - archive.sap.com · 1 Batch History - Enhanced Manufacturing Functionality with SAP...