SAP ECC 6.00
May 2007
English
Electronic Batch Recording (EBR) (P13)
SAP AGDietmar-Hopp-Allee 1669190 Walldorf
Building Block Configuration Guide
Germany
SAP Best Practices Electronic Batch Recording (EBR): Configuration Guide
Copyright
© Copyright 2006 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.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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 are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
© SAP AG Page 3 of 14
SAP Best Practices Electronic Batch Recording (EBR): Configuration Guide
Icons
Icon Meaning
Caution
Example
Note or Tip
Recommendation
Syntax
Typographic Conventions
Type Style Description
Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.
Cross-references to other documentation.
Example text Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.
Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.
EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.
Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.
<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.
© SAP AG Page 4 of 14
SAP Best Practices Electronic Batch Recording (EBR): Configuration Guide
ContentsElectronic Batch Recording (EBR): Configuration Guide..........................................................5
1 Purpose............................................................................................................................. 5
2 Preparation........................................................................................................................ 5
2.1 Prerequisites............................................................................................................5
2.1.1 Building Blocks....................................................................................................5
3 Configuration.....................................................................................................................5
3.1 Defining Layout Profile.............................................................................................5
3.2 Defining Deviation Profile........................................................................................6
3.3 Maintaining Storage System SAP ArchiveLink........................................................7
3.4 Maintaining Number Range for SAP ArchiveLink....................................................8
3.5 Defining Logical File Name......................................................................................8
3.6 Changing Order-Type Dependent Parameters........................................................9
3.7 Defining Signature Method for Simple Signature...................................................10
3.8 Checking and Changing Global Document Types SAP ArchiveLink.....................10
3.9 Checking and Changing Links to Content Repository SAP ArchiveLink................11
3.10 Defining Overall Profile..........................................................................................12
4 Master Data..................................................................................................................... 13
4.1 Changing Material.................................................................................................13
© SAP AG Page 5 of 14
SAP Best Practices Electronic Batch Recording (EBR): Configuration Guide
Electronic Batch Recording (EBR): Configuration Guide
1 PurposeThis configuration guide provides the information you need to set up the configuration of this building block manually.
2 Preparation
2.1 Prerequisites
To archive an electronic batch record, the SAP R/3 system must be connected to a so-called "Optical Archive" (write-once-read-multiple principle)!
However, for demonstration purposes (ONLY!) it might be useful to archive in the database. In this case please refer to SAP Notes 595563 and 685521.
2.1.1 Building BlocksBefore you start installing this building block, you must install prerequisite building blocks. For more information, see the Building Block Prerequisites Matrix for Pharmaceuticals .
3 Configuration
3.1 Defining Layout Profile
UseThe purpose of this activity is to define a layout profile for the batch record.
Procedure1. Access the activity using one of the following navigation options:
IMG MenuProduction Planning for Process Industries Process Data Documentation Batch Record Contents and Layout Define Document Profiles
Transaction Code COCU1
2. On the Change View: “Document profile”: Details choose New entries.
3. Enter the following data:
Key field Entry
Document profile < your document profile > e.g. 1000001
Description < your description > e.g. Document profile for EBR (BP_PH)
© SAP AG Page 6 of 14
SAP Best Practices Electronic Batch Recording (EBR): Configuration Guide
4. In the area Document type selection set indicators for Table of contents, Version data, Process order, Material list, Inspection lot, PI sheet and Process messages.
5. Choose Output control.
6. Choose New entries.
7. In the Document type field enter Table of contents and choose Use standard settings and then Next entry (F8).
8. In the Document type field enter Version data and choose Use standard settings and then Next entry (F8).
9. In the Document type field enter Process order and choose Use standard settings and then Next entry (F8).
10. In the Document type field enter Material list and choose Use standard settings and then Next entry (F8).
11. In the Document type field enter Inspection lot and choose Use standard settings and then Next entry (F8).
12. In the Document type field enter PI sheet and choose Use standard settings and then Next entry (F8).
13. In the Document type field enter Process messages and choose Use standard settings.
14. Save your entries.
ResultA document profile was defined.
3.2 Defining Deviation Profile
UseThe purpose of this activity is to define a deviation profile for the batch record.
Procedure1. Access the activity using one of the following navigation options:
IMG MenuProduction Planning for Process Industries Process Data Documentation Batch Record Contents and Layout Define Deviation Profiles
Transaction Code COCU2
2. On the Change View “Deviation profile”: Overview screen choose New entries.
3. Enter the following data:
Key field Entry
Deviation profile < your deviation profile > e.g. YP-EBR
Description < your description > e.g. Deviation profile for EBR (BP_PH)
4. Choose Use standard settings.
5. In the area PI data scope set indicator for Deviations in PI sheet.
6. Choose QM data scope in the Dialog Structure.
7. Choose New entries.
© SAP AG Page 7 of 14
SAP Best Practices Electronic Batch Recording (EBR): Configuration Guide
8. In the Inspection type field enter 03 and following entries:
Scope of inspection lot data
Missing inspection lot for inspection type
Indicator set
Usage decision
Valuation other than “acceptance” Indicator set
Inspection results
Valuation other than “acceptance” Indicator set
Defects found
Inspection lot defect Indicator set
Operation/phase defects Indicator set
For inspection characteristics Indicator set
9. Save your entries.
ResultThe deviation profile for the batch record was defined.
3.3 Maintaining Storage System SAP ArchiveLink
Use
The purpose of this activity is to maintain the storage system for SAP ArchiveLink.
PrerequisitesAn optical archive is connected to your SAP R/3 system already.
Procedure
This is a cross-client configuration. Ensure that the target client has appropriate settings (transaction scc4).
1. Access the activity using one of the following navigation options:
IMG MenuSAP Web Application Server Basic Services Archive Link Basic Customizing Define Content Repositories
Transaction Code OAC0
2. On the Change Content Repositories: Overview choose Create, activate Full administration and make the following entries:
Key field Entry
Content repository < the “name” of your optical archive > e.g. A2
Description < a description of your choice > e.g. Optical archive
Storage type 04 - HTTP content server
© SAP AG Page 8 of 14
SAP Best Practices Electronic Batch Recording (EBR): Configuration Guide
Version no. 0046
HTTP srvr.port < your server port > e.g. hs2086.wdf.sap.corp
Port number < your port number > e.g. 1080
HTTP script archive
3. Save your entries.
ResultThe storage system for SAP ArchiveLink was checked and maintained.
3.4 Maintaining Number Range for SAP ArchiveLink
Use
The purpose of this activity is to define number range for SAP ArchiveLink.
Procedure
This is a cross-client configuration. Ensure that the target client has appropriate settings (transaction scc4).
1. Access the activity using one of the following navigation options:
IMG MenuSAP Web Application Server Basic Services Archive Link Print List Customizing Maintain number ranges
Transaction Code OANR
2. On the SAP ArchiveLink Number range screen choose Change intervals.
3. On the Maintain Number Range Intervals screen choose Insert intervals and make the following entries:
Key field Value
No 01
From number 0000000001
To number 9999999999
External number Indicator set
4. Choose Enter and save your entry.
ResultA number range for SAP ArchiveLink was defined.
3.5 Defining Logical File Name
Use
© SAP AG Page 9 of 14
SAP Best Practices Electronic Batch Recording (EBR): Configuration Guide
The purpose of this activity is to change the filename length.
Procedure
This is a cross-client configuration. Ensure that the target client has appropriate settings (transaction scc4).
1. Access the activity using one of the following navigation options:
IMG Menu
Cross-Application Components Documentation Management System Document Distribution General Settings Platform-Independent File Names Maintain file names and file paths across all clients
Transaction Code FILE
2. On the Change View “Syntax group definition”: Overview select Syntax group definition from Dialog Structure.
3. Enter 75 in the Lngth field for the Syntax grp Wndows NT.
4. Save your entry.
ResultThe length of filenames was changed.
3.6 Changing Order-Type Dependent Parameters
Use
The purpose of this activity is to change the process order type for the use for archiving.
PrerequisiteThe process order type must exist already!
Procedure1. Access the activity using one of the following navigation options:
IMG MenuProduction Planning for Process Industries Process Order Master Data Order Define Order Type-Dependent Parameters
Transaction Code COR4
2. On the Change View “Order Type-Dependent Parameters”: Overview screen select the appropriate process order type (e.g. YP01) in the required plant (e.g. BP01) and choose Details.
3. On the Master data tab set the flag Approval required in Recipe area.
4. On the Process data documentation area deselect Order record required flag and select Batch record required flag.
5. Save your entries.
Result
© SAP AG Page 10 of 14
SAP Best Practices Electronic Batch Recording (EBR): Configuration Guide
Process order type was changed for archiving.
3.7 Defining Signature Method for Simple Signature
Use
The purpose of this activity is to define a signature method for the simple signature.
Procedure1. Access the activity using one of the following navigation options:
IMG Menu
Production Planning for Process Industries Process Management Control Recipe / Pi sheets Digital Signatures Specify Signature Method for Approval Using Simple Signature
Transaction Code SPRO
2. On the Change View “Specify Signature Method for Simple Signature”: Overview screen select the Signature object Batch record. Approval (40) and assign the Signature Method System Signature with authorization by R/3 user ID/Password (R).
3. Save your entries.
ResultSignature method was assigned to batch record approval.
3.8 Checking and Changing Global Document Types SAP ArchiveLink
UseThe purpose of this activity is to check the entries for global document types.
Procedure1. Access the activity using one of the following navigation options:
IMG MenuSAP NetWeaver Application Server Basic Services Archive Link Basic Customizing Edit document types
Transaction Code OAC2
2. Check whether the required entries are available:
Document type Description Document class
PIEBRCONTE Batch record: Table of contents PDF
PIEBRDEVIA Batch record: Deviations PDF
PIEBRMATLI Batch record: Material list PDF
PIEBRMESSA Batch record: Process messages PDF
© SAP AG Page 11 of 14
SAP Best Practices Electronic Batch Recording (EBR): Configuration Guide
PIEBRORDER Batch record: Process order PDF
PIEBRPOC Batch record: Browser-based PI sheet HTM
PIEBRPRLOS Batch record: Inspection lot PDF
PIEBRSHEET Batch record: PI sheet PDF
PIEBRUSER Batch record: User-defined data PDF
PIEBRVERS Batch record: Version data PDF
3. If above settings are not available make required changes in the Document class field.
4. Save your entries.
ResultSettings for global document types were checked and were changed if necessary.
3.9 Checking and Changing Links to Content Repository SAP ArchiveLink
UseThe purpose of this activity is to check the links to content repository.
Procedure1. Access the activity using one of the following navigation options:
IMG MenuSAP NetWeaver Application Server Basic Services Archive Link Basic Customizing Edit links
Transaction Code OAC3
2. Check whether the required entries are available:
Object type Document type Status Cont. Rep. ID Link
BUS3051 EBR_DOC active < your optical archive > e.g. A2 TOA01
BUS3051 EBR_PDF active < your optical archive > e.g. A2 TOA01
BUS3051 EBR_RTF active < your optical archive > e.g. A2 TOA01
BUS3051 PIEBRCONTE active < your optical archive > e.g. A2 TOA01
BUS3051 PIEBRDEVIA active < your optical archive > e.g. A2 TOA01
BUS3051 PIEBRMATLI active < your optical archive > e.g. A2 TOA01
BUS3051 PIEBRMESSA active < your optical archive > e.g. A2 TOA01
BUS3051 PIEBRORDER active < your optical archive > e.g. A2 TOA01
BUS3051 PIEBRPRLOS active < your optical archive > e.g. A2 TOA01
BUS3051 PIEBRSHEET active < your optical archive > e.g. A2 TOA01
BUS3051 PIEBRUSER active < your optical archive > e.g. A2 TOA01
BUS3051 PIEBRVERS active < your optical archive > e.g. A2 TOA01
© SAP AG Page 12 of 14
SAP Best Practices Electronic Batch Recording (EBR): Configuration Guide
BUS3053001 EBR_DOC active < your optical archive > e.g. A2 TOA01
BUS3053001 EBR_PDF active < your optical archive > e.g. A2 TOA01
BUS3053001 EBR_RTF active < your optical archive > e.g. A2 TOA01
BUS3053001 PIEBRCONTE active < your optical archive > e.g. A2 TOA01
BUS3053001 PIEBRDEVIA active < your optical archive > e.g. A2 TOA01
BUS3053001 PIEBRMATLI active < your optical archive > e.g. A2 TOA01
BUS3053001 PIEBRMESSA active < your optical archive > e.g. A2 TOA01
BUS3053001 PIEBRORDER active < your optical archive > e.g. A2 TOA01
BUS3053001 PIEBRPOC active < your optical archive > e.g. A2 TOA01
BUS3053001 PIEBRPRLOS active < your optical archive > e.g. A2 TOA01
BUS3053001 PIEBRSHEET active < your optical archive > e.g. A2 TOA01
BUS3053001 PIEBRUSER active < your optical archive > e.g. A2 TOA01
BUS3053001 PIEBRVERS active < your optical archive > e.g. A2 TOA01
4. If above settings are not available make required changes in the Content Repository ID field.
5. Save your entries.
ResultSettings for the links to the content repository were checked and changed if necessary!
3.10 Defining Overall Profile
UseThe material-specific overall profile for your plant has to be defined.
PrerequisitesDocument and deviation profiles exist already.
Procedure1. Access the activity using one of the following navigation options:
IMG MenuProduction Planning for Process Industries Process Data Documentation Batch Record Define Material-Specific Overall Profile
Transaction Code COCS
2. On the New Entries: Details of added Entries screen make following entries:
Key field Entry
Material < your material > e.g. PH-2400
Plant < your plant > e.g. BP01
Document profile < your document profile > e.g. 10000001
Deviation profile < your deviation profile > e.g. YP-EBR
Signature strategy SAPPOCSS (R/3 user/password check for PI sheet)
© SAP AG Page 13 of 14
SAP Best Practices Electronic Batch Recording (EBR): Configuration Guide
3. Save your entries and repeat the step above for PH-2500, PH-2600, PH-6501, PH-6502, PH-6503 and PH-6504.
ResultThe material-specific overall profile was defined and assigned to your plant.
4 Master DataThe following activities describe the master data required for this Building Block. The steps do not describe the transactions in detail but list the relevant transaction and the corresponding master data file. For more details on using the individual transactions please refer to the Online Help in the system.
4.1 Changing Material
UseThe purpose of this activity is to change existing materials for batch recording.
Procedure1. Access the activity using one of the following navigation options:
SAP Menu Logistics Material Management Material Master Material Change Immediately
Transaction Code MM02
2. Refer to the following file for details of the master data required: SMB10_MM02_O001_P13.TXT.
ResultData were added in the material master.
© SAP AG Page 14 of 14