BATCH INFORMATION COCKPIT - batch history

Batch History

Jürgen Wettengl, Solution Management, Manufacturing, SAP AGNavaneeth AN, Solution Management, Manufacturing, SAP Labs India15 September 2008

SESSION CODE: MFG_902

© SAP 2008 / Batch History / ASUG 2008 – Juergen Wettengl, Navaneeth AN/

Objective and Learning Points

What you will learn from this session:

1. Understand the latest enhancement in Batch Information Cockpit in form of BatchHistory

2. Learn the benefits of using Batch History functionality – and how YOU can findout what's is in for your company !

3. Examples on how the functionality can be used

4. Outlook on new enhancements planned in Batch History functionality in futurereleases


Agenda

Enhancements planned in future releases4

Definition and Usage

Batch Information Cockpit2

New Functionality “Batch History” &Process Steps

3

AGENDA

1

Potential Benefits and Summary5


Definition

Batch History

Functionality to display all the set of documents for aspecific batch with holistic information to trace thehistory of a batch.Usage

Compliance to Legal requirement – GMP Guideline

Defect Tracing

Product Recall

Regression Analysis


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 toanother SAP ERP system in which the packaging takes place and the deliveryto the customer.

in SAP ERP systems and non SAP systems with different levelsof granularity,

Example: Higher data granularity in the ERP systems e.g. the batchcharacteristics relevant for the batch determination in the ERP processes andvery detailed data granularity in LIMS or MES systems like the processparameters a batch was produced with (e.g. temperatures, etc.).


Problem Statement

To get the complete history data for a batch with all details it is necessary to go todifferent systems, different reports and transactions.

There is a high fault probability to consider all relevant objects and transactions inthe 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)


Legal Requirement – EU GMP § 9 Guideline

The companies must take legal requirements regarding "good manufacturing practice" intoaccount. 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 recordscovering the different manufacturing operations that they perform. Documents shall be clear,free from errors and kept up to-date. Pre-established procedures for general manufacturingoperations and conditions shall be available, together with specific documents for themanufacture of each batch. This set of documents shall make it possible to trace thehistory of the manufacture of each batch. The batch documentation shall be retained for atleast one year after the expiry date of the batches to which it relates, or at least five years afterthe 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 writtendocuments, the manufacturer shall have validated the system by proving that the data will beappropriately stored during the anticipated period of storage. Data stored by these systemsshall be made readily available in legible form. The electronically stored data shall beprotected against loss or damage of data (e.g. by duplication or back-up and transfer ontoanother storage system).


Agenda





3

AGENDA

1



BASF AG User Report on Implementing theBatch 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 batchmanagement.”

“There are two different user groups, each with different selection criteria, foraccessing the BIC. This ensures that the user is only presented with that datathat is relevant for a particular decision.”

“About 6,300 employees from areas such as production, sales anddistribution, supply chain, warehouse, and quality management currently usethe Batch Information Cockpit on a regular basis.”


Application Example:Selection Screen


Application Example:Results for batch selection and its stock


Application Example:Selection of follow up actions

Conversion of unrestricted batch stock to blocked stock :


Agenda





3

AGENDA

1



PPMMSDCRM…

BatchRelatedObjects

SAP System A

PPMMSDCRM…

BatchRelatedObjects

SAP System B

PPMMSDCRM…

BatchRelatedObjects

SAP System C

BIC

Work OrderGoods Mvt.…

BatchRelatedObjects

Shopfloor System A

Non-SAP

Insptn LotsQuality Rslt.…

BatchRelatedObjects

Shopfloor System B

Architecture


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 asclassification-data (e.g. characteristics like viscosity or density, status of classification)

e.g. Materialis entered forBatch History

searchExecute or F8


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


Features – Display Batch History

Batch History header information

Minimize/Maximize Header/ALV Grid


Features – Display Batch History

Sort Ascending

Sort Descending

Filter Print

Export Options –e.g., spreadsheet

ALV Grid Features


Process Steps – Follow Up Action

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


Process Steps – Follow Up Action

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


Process Steps – Batch History SelectionScreen

Batch History Tab Page in BatchInformation Cockpit

Batch Related Object Types(SAP/nonSAP) display dependent on thecustomizing settings for object types/usergroup combination

Evaluation Period for which the historydetails of a batch have to be considered

Valid Plants selection for having sameBRO types search across all plants fordisplaying batch history

Cross Systems checkbox if flagged, thehistory details of a batch are tracked frommore than one SAP systems

Movement Type filter used whenMaterial Document object type is flagged


Process Steps – Batch History details fromdifferent ERP systems

Cross System check boxto be checked if samebatch information is

maintained in differentERP system as well


Process Steps – Batch History details fromdifferent ERP systems

User would have to enterlogin credentials to another

ERP system if he hasauthorization


Customer defined objecttype check box to be

checked if batchinformation is maintained in

non SAP system as wellInformation

fromnon SAP system

Process Steps - Batch History details fromNon SAP Batch Related Object Types


Right Click onCustomer Defined

Object type

Note: Batch History information from non SAP system is deliveredas a working example using SAP MII. The approach will be deliveredin SDN and is not part of standard EhP4 offering

Process Steps - Batch History details fromNon SAP Batch Related Object Types


Requirement being batch information isobtained from different SAP and nonSAP systems -> impacts performancedelivery

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 isthe report program will pull data from the variousBRO type tables (SAP/nonSAP)

Batch History functionality will retrieve informationfrom the index table

Batch History analysis will not retrieve informationfrom 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


Process Steps – Batch History Print Option

Print

Print Report will contain Headerinformation

andBatch History Details table


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


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)

BusinessFunction

Documentation

ReleaseInformation

Test Case


Implementing Batch History

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



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



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



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



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



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


Agenda





3

AGENDA

1



Planned enhancements in future releases

Implementing Batch History functionality with Push Method approach

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


Agenda





3

AGENDA

1



Potential Benefits

The functionality provides one transaction and flexible environment for selection ofrelevant batch related object types for batch history search from SAP and non SAPsystems

It provides better end user satisfaction by removing high fault probability inobtaining batch information from various systems

The functionality is in Compliance with Good Manufacturing Practice guidelinerequirement for tracing the history of manufacture of each batch


Summary

Batch History Functionality is to display all the set of documents for a specificbatch with holistic information to trace the history of a batch.

Functionality resides in Batch Information Cockpit (BIC), central control panel withextensive, batch-specific analysis and control options that take the strain out ofbatch management.”

Functionality is widely applicable across all manufacturing industries (processand discrete)

Functionality is widely used to supportCompliance to Legal requirement – GMP GuidelineDefect TracingProduct RecallRegression Analysis


Info/additional requirements regarding BatchHistory functionality

Contacts:

Jürgen Wettengl ([email protected])

Navaneeth AN ([email protected])

mailto:rgenWettengl([email protected])

mailto:[email protected]


Thank You for Participating !

[SESSION CODE: MFG 902

Please remember to complete and return yourevaluation form following this session.

For ongoing education on this area of focus, visit the Year-RoundCommunity page at www.asug.com/yrc

http://www.asug.com/yrc


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 changedwithout 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 aretrademarks 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 displayedare 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 documentcontains 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, orother 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 ofmerchantability, 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 limitationshall 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 thesematerials 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 durchSAP 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 diedazugehö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 Namenvon Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. 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 anderenVereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmtenGeschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht dieRichtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, wederausdrü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 Zwecksowie 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 Verwendungdieser 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 überInternetseiten Dritter ab.

Alle Rechte vorbehalten.


Implementing Batch History : Non SAP BatchRelated Object Types

BADI Interface to allow users to define and update External BRO Types

Customer has an MES (Manufacturing Execution System), where he maintains the Batch related objectdetails. He will then define this object type in the customizing and use the BADI exit to retrieve the data fromthe MES system (recommended using SAP MII (Manufacturing Intelligence and Integration).

In order to store the external BRO types and their relevant data in SAP system, would have to do thefollowing.

Create the BRO type in customizing and flag it as external BRO type.

Define a structure of how this external BRO type data would look.<INCLUDE>

MATERIAL MATNR CHAR 18 0 Material Number

PLANT WERKS_D CHAR 4 0 Plant

BATCH CHARG_D CHAR 10 0 Batch Number

EVENT_DATE DATE DATS 8 0 Event date

EVENT_TIME TIME TIMS 6 0 Event time

AUTHOR AUTHOR CHAR 20 0 Author

<INCLUDE>

ORDER_NO AUFNR CHAR 12 0 Order Number

QUANTITY QUANT_13 CHAR 13 0 Quantity

QUAN_UNIT UNIT UNIT 3 0 Unit

PRICE AMOUNT_ALV DEC 15 0 Amount [KB]

CURRENCY WAERS CUKY 5 0 Currency Key

MFG_DATE DATE DATS 8 0 Starting Date of Change of Deduction

MFG_TIME TIME TIMS 6 0 Time


Create a table type for the mentioned structure

The data has to be pulled from the external system into the BADI and update the table in thedefined format and pass the internal table to the exporting parameter (using SAP MII)

The data in the internal table along with the object type will be interpreted, processed andstored into the Index table

Implementing Batch History : Non SAP BatchRelated Object Types

BATCH INFORMATION COCKPIT - batch history

Documents

Transcript of BATCH INFORMATION COCKPIT - batch history