You are on page 1of 81

Project Unity Functional Specification - Audit Trail

P ROJECT U NITY

F UNCTIONAL S PECIFICATION - AUDIT T RAIL

VERSION: 00 REVISION: 00

Document Approval and Release


ROLE NAME (AND TITLE) DATE AND SIGNATURE

AUTHOR

ACCENTURE VITTORIA CASALINI

REVIEW

CSV – VALIDATION CARLO CANDOTTI


CONSULTANT

BUSINESS – LOCAL TEAM LEAD DAVE MARKOVICH

BUSINESS - CORPORATE TEAM DAVIDE COHA


LEAD

420750868.doc Page 1 of 81
Project Unity Functional Specification - Audit Trail

Document Approval and Release


ROLE NAME (AND TITLE) DATE AND SIGNATURE

IT – LOCAL TEAM LEAD MASSIMO DE LUCA

APPROVAL

IT – CORPORATE MARCO MAIOLI

BUSINESS – NORTH AMERICA LUC RAYMOND


TEAM LEAD

GQ – VALIDATION SANDRO TACCANI


COORDINATOR

420750868.doc Page 2 of 81
Project Unity Functional Specification - Audit Trail

Document History

Version- Change date Responsible person Change summary


Revision

V00R00 09-DEC-2011 Vittoria Casalini Initial Version

Last version revision information

Paragraph # Change

420750868.doc Page 3 of 81
Project Unity Functional Specification - Audit Trail

Table of Contents

1. Introduction........................................................................................................................ 5
1.1 Reference Documents............................................................................................. 5
1.2 Definitions & Acronyms...........................................................................................5
2. Document Purpose.......................................................................................................... 6
3. Short Functional Description.......................................................................................... 6
3.1 GxP Criticality Analysis........................................................................................... 6
3.2 System GAP Analysis..............................................................................................7
4. Business Process Flow Chart........................................................................................ 7
5. Solution............................................................................................................................ 8
5.1 Inventory and Warehouse Management (INV).......................................................8
5.2 Manufacturing (MFG).............................................................................................11
5.2.1 Master Data.......................................................................................................... 11
5.2.2 Production Execution......................................................................................... 22
5.3 Quality Management (QUA)...................................................................................25
5.4 Plant Maintenance (PM)......................................................................................... 38
5.5 Purchasing (PUR)................................................................................................... 45
5.5.1 Master Data......................................................................................................... 45
5.5.2 Purchasing Process........................................................................................... 46
5.6 Standard SAP default configuration.....................................................................48
6. Overview Of SAP Transactions....................................................................................60
6.1 SAP Transactions................................................................................................... 60
6.2 Customizing Activities........................................................................................... 64
7. Overview of Additional Developments.........................................................................81
7.1 Reports, Forms....................................................................................................... 81
7.2 Interfaces................................................................................................................ 81
7.3 Conversions........................................................................................................... 81
7.4 Enhancements.......................................................................................................... 81

420750868.doc Page 4 of 81
Project Unity Functional Specification - Audit Trail

1. INTRODUCTION

1.1 REFERENCE DOCUMENTS

Reference Document

[1] UNITY-MFG-URS – Manufacturing User Requirements Specification

1.2 DEFINITIONS & ACRONYMS

Term/Acro Definition/Explanation
nyms

SAP Systems, Applications & Products in data processing

BoM Bill of Material; it is a complete, formally structured list of the components that make up a
product or assembly. The list contains the material number of each component, together with the
quantity and unit of measure.

QA Quality Assurance

PV Production Version; a production version determines which alternative BOM is used together with
which task list/master recipe to produce a material or create a master production schedule.

S/N Serial Number

INV Inventory and Warehouse

QUA Quality Management

MFG Manufacturing

PMO Plant Maintenance

PUR Purchasing

GxP Goods Manufacturing Practices

GAP GAP is the difference between the available functionalities against functionalities required. A
comparison of the information gathered in the Requirements gathering phase of a project may
identify gaps in the functionalities required compared to the functionalities available. The
Functional Specification Document describes the solution to cover the User Requirements/Gaps
referenced

SOP Standard Operating Procedure

MAN Manual

FS Functional Specification

GDL Guideline

GUI Graphical User Interface

420750868.doc Page 5 of 81
Project Unity Functional Specification - Audit Trail

2. DOCUMENT PURPOSE
Scope of the document is to provide details about the activation of audit trail functionality on
the system for specific GxP objects and related information. The GxP fields and the
corresponding audit trail reporting are grouped in different areas for the main business areas
impacted by GxP critical data management:

 Inventory and Warehouse Management (INV);

 Manufacturing (MFG);

 Quality Management (QUA);

 Plant Maintenance (PM);

 Purchasing (PUR).

For each area, for all GxP critical fields, the transaction requested for reporting all changes is
described.

3. SHORT FUNCTIONAL DESCRIPTION

3.1 GXP CRITICALITY ANALYSIS


In order to determine the scope of audit trail activation on top of the standard configuration
the following approach has been used:

 Determine the list of GxP critical transactions:

all the functional specification in scope of Plant Execution work-stream have been
analyzed; for each line the transaction mentioned has been primary classified as GxP
critical when the URS requirement is GxP critical.

After this first screening, a list of all GxP critical transactions has been identified. Within
this list only transaction that could create, change or delete (flag for deletion) objects
have been considered. ‘Display’ transactions, even when classified as GxP critical because
linked with GxP critical requirements, have not been considered as relevant for audit trail
purpose because no changes can be made on the data.

 Analyze the field managed in each GxP transaction:

all transactions classified as GxP critical and relevant for audit trail, have been than
analyzed in details: all fields that are somehow requested to be changed during a process
described in a functional specification, where judged as GxP critical or not. In a second
step, fields that are Gxp critical have been analyzed: only if they are modifiable by

420750868.doc Page 6 of 81
Project Unity Functional Specification - Audit Trail

custom or standard transaction, they have been included in standard audit trail
functionality. Final result of this analysis is the list of all the fields that need to be audit
trailed.

The basic goal reached with this analysis is to guarantee that the access to GxP critical fields
is only allowed to user with GxP critical roles and to guarantee that all changes on GxP critical
fields are logged properly.

NOTE

For goods movement transactions, in this analysis an assumption is made. Goods movement
transactions create material documents in Unity, and once a goods movement is created only
few fields are then modifiable (at header level only ‘Document header text’, at item level only
‘Uploading point’ and ‘Text’). The assumption is that the material document that corresponds
to the goods movement that was processed would provide the documentation required for
audit traceability of the goods movement transactions. Subsequent changes on the material
document are traced with the proper transaction for changing material document.

3.2 SYSTEM GAP ANALYSIS


In the system analysis for all the fields subjected to audit trail, it was checked whether the
system is already supporting the audit trail:

 for fields with audit trail activated, the completeness of the current functionality is
checked (for details about all SAP default audit trail activated fields refers to chapter
5.6);

 for fields without audit trail an implementation activity is performed and audit trail is
activated (for details about those SAP not default audit trail activated fields refers to
chapters 5.1, 5.2, 5.3, 5.4, 5.5).

4. BUSINESS PROCESS FLOW CHART


N/A

420750868.doc Page 7 of 81
Project Unity Functional Specification - Audit Trail

5. SOLUTION

5.1 INVENTORY AND WAREHOUSE MANAGEMENT (INV)

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist US

Acist EU

Ezem
BDI
UNITY-FSP- Batch Search Records for Inventory movement AUT10 001 N/A MFG07-01_0060
MFG-06-0010
The conditions are maintained by transaction MBC1 (Create batch search strategy) MBC1
and MBC2 (Change batch search strategy).
MBC2
Changes on Batch search strategy can be viewed by Pharma Pack tool by
transaction AUT10:
Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

 Start date (mandatory)


 Start time (mandatory) X X X
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)
 Transaction code (MBC1, MBC2)

By pressing execute the system provides the Output of table logs. For each table log
(by row selecting) it is possible to have the details for the inserted records (each
time a condition has been changed a new record is generated in KONDH table – SAP
table containing all changes performed on a specific table under audit trail table log).

UNITY-FSP- Posting change AUT10 002 N/A MFG07-01_0090 X X X


MFG-06-0020
The posting change can be changed with transaction LU02. LU01
Changes on Posting Change can be viewed by Pharma Pack tool by transaction
LU02
AUT10:
Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

 Start date (mandatory)


 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)
 Transaction code (LU01, LU02)

420750868.doc Page 8 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist US

Acist EU

Ezem
BDI
By pressing execute the system provides the Output of table logs. For each table log
(by row selecting) it is possible to have the details for the following fields:

 LUBU-QPLOS Inspection Lot Number


 LUBU-LGOR1 Storage location
 LUBU-LGOR2 Storage location
 LUBU-STATU Status of posting change

The following information is logged:

 Date
 Time
 Changed by
 Transaction Code
 Name of transaction
 Table and field changed
 Old value
 New value

UNITY-FSP- WM Control Cycle AUT10 003 N/A MFG07-01_0100 X X


MFG-06-0030
The “Control Cycle” can be changed with transaction LPK2 (Change Control Cycle LPK1
WM).
LPK2
Changes on WM Control Cycle can be viewed by Pharma Pack tool by transaction
AUT10:
Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

 Start date (mandatory)


 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)
 Transaction code (LPK1, LPK2)

By pressing execute the system provides the Output of table logs. For each table log
(by row selecting) it is possible to have the details for the following fields:

 PKHD-LGNUM Warehouse Number / Warehouse Complex


 PKHD-LGTYP Storage Type

420750868.doc Page 9 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist US

Acist EU

Ezem
BDI
 PKHD-LGPLA Storage bin
 PKHD-NKDYN Indicator: dynamic destination bin
 PKHD-BERKZ Material staging indicator for production supply

The following information is logged:

 Date
 Time
 Changed by
 Transaction Code
 Name of transaction
 Table and field changed
 Old value
 New value

420750868.doc Page 10 of 81
Project Unity Functional Specification - Audit Trail

5.2 MANUFACTURING (MFG)


MASTER DATA

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist EU
Acist US

Ezem
BDI
UNITY-FSP- Material Master MM01 004 N/A MFG07-01_0010 X X X X
MFG-06-0040 The material master is maintained by transaction MM01 (Material Master Create) and MM02
MM01, MM03, MM02 (Material Master Change)
Changes on Material Master can be viewed by: AUT10
A. By change document in Transaction MM01, MM02, MM03:

Material number
Select the view
Go in menu to -> Environment -> Display changes
All change documents are listed and double clicking on the change document it is
possible to see list of the fields that have been changed.

B. By Pharma Pack Tool by transaction AUT10:

Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

 Start date (mandatory)


 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)
 Transaction code (MM01, MM02, MM03)

C. By pressing execute the system provides the Output of table logs. For each table
log (by row selecting) it is possible to have the details for the following fields:

 MARC-XCHAR Batch management indicator (internal)


 MARC-MMSTA Plant-Specific Material Status
 MARC-AUSME Unit of issue
 MARC-INSMK Post to Inspection Stock
 MARC-KZDKZ Documentation required indicator

420750868.doc Page 11 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist US

Acist EU

Ezem
BDI
 MARC-VERKZ Version indicator
 MARC-FRTME Production unit
 MARC-QMATV Inspection Setup Exists for Material/Plant
 MARC-QMATA Material Authorization Group for Activities in QM
 MARC-KZECH Determination of batch entry in the production/process order
 MARA-MEINS Base unit of measure
 MARA-RAUBE Storage conditions
 MARA-TEMPB Temperature conditions indicator
 MARA-TRAGR Transportation group
 MARA-MHDHB Total shelf life
 MARA-MHDLP Storage percentage
 MARA-IPRKZ Period indicator for shelf life expiration date
 MARA-RDMHD Rounding rule for calculation of SLED
 MARM-MEINH Alternative unit of measure for stock keeping

The following information is logged:

 Date
 Time
 Changed by
 Transaction Code
 Name of transaction
 Table and field changed
 Old value
 New value

The audit trails are recorded under the change document object “MATERIAL” (SAP
object containing detailed changes to material master).

UNITY-FSP- Bill of Material (BoM) AUT10 005 N/A MFG07-01_0020 X X


MFG-06-0050
The material BOM is maintained by transaction CS01 (Material BOM creation) and CS01
CS02 (Material BOM change). Changes on Material BOM can be viewed by:
CS02
A. By change document in Transaction CS03 :

Select material, plant, usage and alternative


View general Item Overview

420750868.doc Page 12 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist US

Acist EU

Ezem
BDI
Go in menu to -> Environment -> Changes Document

B. By Pharma Pack Tool by transaction AUT10:


Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

 Start date (mandatory)


 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)
 Transaction code (CS01, CS02)

By pressing execute the system provides the Output of table logs. For each table log
(by row selecting) it is possible to have the details for the following fields:

 MAST-MATNR: Material Number


 MAST-STLAL: Alternative BOM
 MAST-STLAN:BOM usage
 MAST-WERKS: Plant
 MAST- LOSVN: From lot size
 MAST- LOSBS: To lot size
 STKO-AENNR: Change Number
 STKO-BMENG: Base Quantity
 STKO-DATUV: Valid from date
 STKO-STLST:BOM status
 STPO-AUSCH: Component scrap %
 STPO-FMENG: Fixed Quantity
 STPO-IDNRK: Component
 STPO-MEINS: Unit of measure
 STPO-MENGE: Requirement Quantity
 STPO-POSNR:BOM item number
 STPO-POSTP: Item Category
 STPO-REKRS: Recursiveness allowed
 STPO-SORTF: Sort string
 MAST-STLNR: Bill of material

The following information is logged:

 Date

420750868.doc Page 13 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist US

Acist EU

Ezem
BDI
 Time
 Changed by
 Transaction Code
 Name of transaction
 Table and field changed
 Old value
 New value

UNITY-FSP- Master Recipe AUT10 006 N/A MFG07-01_0030 X X


MFG-06-0060
The Master Recipe is maintained by transaction C201 (Material BOM creation) and C201
CS02 (Material BOM change). The Production Version is maintained by transaction
C202
C201, C202 and C223 (Production Version: Mass Processing).
C223
Changes on Master Recipe can be viewed by Pharma Pack tool by transaction
AUT10:

Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

 Start date (mandatory)


 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)
 Transaction code (C201, C202)

By pressing execute the system provides the Output of table logs. For each table log
(by row selecting) it is possible to have the details for the following fields:

 PLKO-PLNAL: Recipe counter


 PLKO-PLNNR: Recipe group
 MAPL-PLNAL: Recipe counter
 MAPL-WERKS: Plant
 MAPL-MATNR: Material number
 PLKO-PROFIDNETZ: Profile
 AUSP-ATWRT: Characteristic value (Multiple permitted values for
characteristic ‘Resource’)
 CABN-ATNAM: Characteristic name
 CRHD-ARBPL: Resource

420750868.doc Page 14 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist US

Acist EU

Ezem
BDI
 CRHD-STEUS: Control key
 PLKO-AENNR: Change number
 PLKO-BMSCH: Base quantity
 PLKO-KTEXT: Master recipe description
 PLKO-LOSBS: Charge quantity (to)
 PLKO-LOSVN: Charge quantity (from)
 PLKO-MEINH: Unit of measure of base quantity
 PLKO-PLNME: Unit of measure of charge quantity
 PLKO-STATU: Status
 PLKO-UMREN: Conversion factor (operation quantity)
 PLKO-UMREZ: Conversion factor (charge quantity)
 PLKO-VERWE: Usage
 PLMZ- LGORT: Storage location storage resource
 PLPO- EHOFFB: Unit for offset to start
 PLPO- EHOFFE: Unit for offset to finish
 PLPO- OFFSTE: Offset to sub operation finish
 PLPO-ARBID: Resource
 PLPO-BMSCH: Base quantity
 PLPOD-UVORN: Secondary resource allocation number
 PLPO-LTXA1: Operation description
 PLPO-LTXA1: Description
 PLPO-MEINH: Unit of measure for operation
 PLPO-MEINH: Unit of measure for operation
 PLPO-PHFLG: Phase indicator
 PLPO-PHSEQ: Control recipe destination
 PLPO-STEUS: Control key
 PLPO-UMREN: Conversion factor (Operation quantity)
 PLPO-UMREZ: Conversion factor (Charge quantity)
 PLPO-VORNR: Operation / phase number
 PLPO-VORNR: Phase number
 PLPO-WERKS: Plant
 RC271- STTAG: Key date (Valid from date)
 STPO-IDNRK: BOM component
 STPO-IDNRK: Component
 STPO-MENGE: Requirement Quantity
 STPO-POSNR:BOM component number
 STPO-POSTP: Item category
 STPO-REKRS: Recursiveness allowed
 PLPO-ISTKN BOM Item node Number
 PLPO-RUZUS Key rounding and additional values

420750868.doc Page 15 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist US

Acist EU

Ezem
BDI
Changes on Production Version can be viewed by Pharma Pack tool by transaction
AUT10:
Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

 Start date (mandatory)


 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)
 Transaction code (CS01, CS02, C223)

Following fields are considered as critical and changes are logged as explained
below:

 MKAL-ADATU: Valid from date


 MKAL-BDATU: Valid to date
 MKAL-BSTMA: To lot size
 MKAL-BSTMI: From lot size
 MKAL-STLAL: Alternative BOM number
 MKAL-STLAN: Alternative BOM usage
 MKAL-TEXT1: Short text for production version
 MKAL-VERID: Production version number
 MKAL- MKSP: Production version locked

The following information is logged:

 Date
 Time
 Changed by
 Transaction Code
 Name of transaction
 Table and field changed
 Old value
 New value

The following fields do not need an audit trail because the history of changes can be
retrieved by getting the respective ECM
PLKO-FLG_CHKED Recipe consistency flag

420750868.doc Page 16 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist US

Acist EU

Ezem
BDI
Process instructions and inspection characteristic changes via C202 can be retrieved
with transaction C261. For more detail, AUT10 can be used for looking at the
changes

Additional information for process instructions retrieval:


 User ID/date/time/used transaction/change number : C261 (the fields
‘Process instruction’ and ‘Process inst.char.’ have to be flagged)
 to view which data are created/changed/deleted :
CC33/environment/reporting/task list changes
 User ID/date/time/used transaction can be retrieved in AUT10 (transaction
C2021/C202)

UNITY-FSP- Resource AUT10 008 N/A MFG07-01_0040 X X


MFG-06-0070
The Resource is maintained by transaction CRC1 (Resource creation) and CRC2 CRC1
(Resource change).
CRC2
Changes on Resource can be viewed by Pharma Pack tool by transaction AUT10:
Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

 Start date (mandatory)


 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)
 Transaction code (CRAH for resource creation and CRAV for resource
changing)

By pressing execute the system provides the Output of table logs. For each table log
(by row selecting) it is possible to have the details for the following fields:

 CRHD-ARBPL Resource
 AUSP-ATWRT Characteristic value
 P3000-LGORT_RES Storage location storage resource
 CRHD-MIXMAT Indicator: mixing of material allowed
 CRHD-PLANV Usage
 CRHD-PRVBE Supply area
 CRHD-RGEKZ Indicator: Back-flushing
 CRHD-VERAN Person responsible
 CRHD-VGWTS Standard value key

420750868.doc Page 17 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist US

Acist EU

Ezem
BDI
 CRHD-WERKS Plant
 CRHD-PAR01: First Work Center Parameter (for formulas)
 CRHD-PAR02: Second Work Center Parameter (for formulas)
 CRHD-PAR03: Third Work Center Parameter (for formulas)
 CRHD-PAR04: Fourth Work Center Parameter (for formulas)
 CRHD-PAR05: Fifth Work Center Parameter (for formulas)
 CRHD-PAR06: Sixth Work Center Parameter (for formulas)

Changes of the description and other change for the resources can be checked via
transaction CR10.
All changes to resource classification values can be checked (AUSP-ATWRT).

UNITY-FSP- Batch Search Records for Process Order AUT10 009 N/A MFG07-01_0050 X X
MFG-06-0080
The Resource is maintained by transaction COB1 (Creation of batch search record) COB1
and COB2 (Change of batch search record).
COB2
Changes on Resource can be viewed by Pharma Pack tool by transaction AUT10:
Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

 Start date (mandatory)


 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)
 Transaction code (COB1, COB2)

By pressing execute the system provides the Output of table logs. For each table log
(by row selecting) it is possible to have the details for the following fields:

 KOTH030-AUART Order type


 KOTH031-AUART Order type
 KOTH031- PMATN Material number for order
 KOTH030-KAPPL Application
 KOTH031-KAPPL Application
 KOTH030-KNUMH Condition record number
 KOTH031-KNUMH Condition record number
 KOTH030-DATAB Validity start date of the condition record
 KOTH031-DATAB Validity start date of the condition record

420750868.doc Page 18 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist US

Acist EU

Ezem
BDI
 KOTH030-DATBI Validity end date of the condition record
 KOTH031-DATBI Validity end date of the condition record
 KOTH030-KSCHL Batches: Search strategy type
 KOTH031-KSCHL Batches: Search strategy type
 KOTH030-MATNR Material number
 KOTH031-MATNR Material number
 KOTH030-WERKS Plant
 KOTH031-WERKS Plant
 KONDH-KNUMH Condition record number
 KONDH-CHSPL Number of batch splits can be changed
 KONDH-CHANZ Batches: Maximum number of batches to be read
 KONDH-CHASP Batches: No. of batch splits allowed
 KONDH-CHMDG Batches: Dialog batch determination
 KONDH-CHMVS Batches: Exit to quantity proposal
 KONDH-CHMAN Manual batch determination
 KONDH-KZAME ID for display of UoM in batch determination
 KONDH-CHDYN Number of the following screen
 KONDH-CHCUA GUI status
 KONDH-CUOBJ_CH Internal object number of the batch classification
 KONDH-CLINT Internal Class Number
 KONDH-LOEVM_KO Deletion indicator for condition item
 KONDH-CHVSK Selection type at start of batch determination
 KONDH-CHVLL Over-delivery allowed in batch determination

UNITY-FSP- Object classification AUT10 010 N/A MFG07-01_0070 X X X X


MFG-06-0090
The class can be changed only by system administrator user, with transaction CL01 CL01
(Class Create) and CL02 (Class Change).
CL02
Changes on Class can be viewed by Pharma Pack tool by transaction AUT10:
Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

 Start date (mandatory)


 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)
 Transaction code (CL01, CL02)

420750868.doc Page 19 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist US

Acist EU

Ezem
BDI
By pressing execute the system provides the Output of table logs. For each table log
(by row selecting) it is possible to have the details for the following fields:

 KLAH-SICHT Organizational Area


 KLAH-STATU Class status
 KLAH-VONDT Valid-from date
 KLAH-BISDT Valid-to date
 KSML-OMERK Object-Dependent Characteristic
 KSML-IMERK Internal characteristic
 KSML-ABTEI Organizational Area

The following information is logged:

 Date
 Time
 Changed by
 Transaction Code
 Name of transaction
 Table and field changed
 Old value
 New value

The audit trails are recorded under the change document object “KLASSE”.

Other changes can be seen in the change overview screen in CL02/CL03

Class characteristics settings are only maintained in transaction CT04, when a


change of a characteristic is wanted, a new one is created.

UNITY-FSP- Object Characteristic AUT10 011 N/A MFG07-01_0080 X X X X


MFG-06-0100
The characteristic can be changed only by system administrator user, with CT04
transaction CT04 (Maintain characteristic).
Changes on Characteristic can be viewed by Pharma Pack tool by transaction
AUT10:
Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

 Start date (mandatory)


 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)

420750868.doc Page 20 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist US

Acist EU

Ezem
BDI
 Changed by (optional)
 Transaction code (CT04)

By pressing execute the system provides the Output of table logs. For each table log
(by row selecting) it is possible to have the details for the following fields:

 CAWN-ATINN Internal characteristic


 CAWN-ATWRT Characteristic value
 CAWN-ATFLV Internal floating point from
 CAWN-ATFLB Internal floating point value to
 CAWN-ATCOD Code for value dependency
 CAWN-ATSTD Default value
 CAWN-ATIDN Object identification
 CAWN-SPRAS Language key
 CAWN-TXTNR Number of Related Text
 CAWN-LKENZ Deletion indicator
 CAWN-ATTLV Tolerance from
 CAWN-ATTLB Tolerance to
 CAWN-ATPRZ Indicator: Tolerance Shown as a Percentage

The following information is logged:

 Date
 Time
 Changed by
 Transaction Code
 Name of transaction
 Table and field changed
 Old value
 New value

The audit trails are recorded under the change document object “FEATURE”.

420750868.doc Page 21 of 81
Project Unity Functional Specification - Audit Trail

PRODUCTION EXECUTION

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist US

Acist EU

Ezem
BDI
UNITY-FSP- Process order AUT10 012 N/A MFG07-01_0110 X X
MFG-06-0110
The Process order is created by transaction COR1, CORO, COR8 and it is COR1
maintained by transaction COR2 (Process order change).
COR2
Changes in the process order are obtained by the transaction for confirmation
(COR6, COR7, CORM). CORO
Changes on Process Order can be viewed by Pharma Pack tool by transaction
AUT10: COR6
Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter: COR7
 Start date (mandatory) COR8
 Start time (mandatory)
 End date (mandatory) CORM
 End time (mandatory) CO44
 Changed by (optional)
CORR
Transaction code (COR1, COR2, CORO, COR6, COR7, COR8, CORM, CO44); for
CORS
massive changes the transaction CO44 must be used as selection parameter.
CORT
By pressing execute the system provides the Output of Change documents and
table logs.
Table log has been deactivated (where possible) for following table:

 RESB
 AFFL
 AFPO
 AUFK
 RSADD

For these tables an enhancement has been implemented, driven by the OSS note
390635 that creates change documents for the changes performed in a process
order. This enhancement has been created for the following reason:

 Facilitate the changes analysis with transaction AUT10.


 Improve the performance of the transaction (less time for elaborating
the data)
 Have a change log for each changes performed on the order

420750868.doc Page 22 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist US

Acist EU

Ezem
BDI
Enhancement defines additional logic to decide whether change documents are
created.

For each change document (by row selecting) it is possible to have the details for
the following fields

Table-Field Description
AFKO-AENNR Change number
AFKO-AENNR Change number
AFKO-AENNR Change number
AFVC-AENNR Change number
AFFL-AENNR Change number
AUFK-AUART Order type
AUFK-IDAT2 Technical completion date
AFPO-XLOEK Deletion flag
AFKO-BMENGE Base quantity
AFVV-BMSCH Base quantity
AFKO-AUFLD Date of BOM explosion/routing transfer
AFKO-SFCPF Production scheduling profile
AFPO-PSMNG Order item quantity
AFKO-GAMNG Total order quantity
AFKO-GASMG Total scrap quantity in the order
AFVV-GMNGA Confirmed yield in order unit of measure
AFVC-SPLIM Maximum number of splits
AFVC-SPANZ Actual number of splits
AFVC-SPMUS Required splitting
AFKO-STLAL Alternative BOM
AFKO-STLAN BOM usage
AFVC-ISTKN BOM item node number
AFKO-STLST BOM status
AFKO-STLTY BOM category
AFVC-ISTTY BOM category
AFKO-STLNR Bill of material
AFVC-ISTNR Bill of material
AFPO-UNTTO Under-delivery tolerance limit

420750868.doc Page 23 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist US

Acist EU

Ezem
BDI
AFPO-VERID Production version
AFKO-ARSPS Order Item Number
AUFK-PHAS0 Phase “Order created”
AUFK-PHAS1 Phase “Order released”
AUFK-PHAS2 Phase “Order completed”
AUFK-PHAS3 Phase “Order Closed”

Standard change documents are available for following fields:

Order status Change document provided by the enhancement of this field is


not available because system status cannot be monitored.
Anyway a standard display of all the status changes is available
directly in the process order
Deletion flag

Change document provided by the enhancement of this field is


not available because system status cannot be monitored.
Anyway a standard display of all the status changes is available
directly in the process order

Process Order Confirmation

The confirmation of process order is done by transaction COR6 (Single Process


Order Confirmation), CORR (Collective entry: time ticket), CORS (Cancel process
order confirmation) and CORT (Display process order confirmation).

The order confirmation doesn’t involved any GMP critical field so the Audit trail is
not required.

420750868.doc Page 24 of 81
Project Unity Functional Specification - Audit Trail

5.3 QUALITY MANAGEMENT (QUA)

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist EU
Acist US

Ezem
BDI
UNITY-FSP- Batch Master – Basic Data AUT10 013 N/A MFG07-01_0120 X X X X X
MFG-06-0120
The batch master is maintained by transaction MSC1N (Batch Master Create) and MSC2N 014
MSC2N (Batch Master Change). The batch master can be created or changed by
different other transactions (MSC2N, MIGO, MB11, MB1B, MB1C, MB31, MIGO
MIGO_GO, QA11, QA12, SE38)
MB11
Changes on Batch Master Basic Data can be viewed by: MB1B
A. By change document in Transaction MSC2N or MSC3N:
 Material number MB1C
 Plant MB31
 Batch ID
Go to tab “Change” QA11
All change documents are listed and double clicking on the change document it is
possible to see list of the fields that have been changed. QA12
SE38
B. By Pharma Pack Tool by transaction AUT10:
Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

 Start date (mandatory)


 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)

Transaction code (MSC2N, MIGO, MB11, MB1B, MB1C, MB31, MIGO_GO, QA11,
QA12, SE38)

By pressing execute the system is provide the Output of table logs. For each table
log (by row selecting) it is possible to have the details for the following fields:

 MCHA-CHARG Batch number


 MCHA-LVORM Deletion Flag for All Data on a Batch at a Plant
 MCHA-ERSDA Creation date
 MCHA-LAEDA Date of last change
 MCHA-VERAB Availability date

420750868.doc Page 25 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist EU
Acist US

Ezem
BDI
 MCHA-VFDAT Shelf Life Expiration Date
 MCHA-ZUSTD Batch in restricted-use stock
 MCHA-ZAEDT Date of last status change
 MCHA-LIFNR Vendor's account number
 MCHA-LICHA Vendor batch number
 MCHA-VLCHA Original batch number (deactivated)
 MCHA-BWTAR Valuation type
 MCHA-CHAME Unit of issue for batch (deactivated)
 MCHA-LWEDT Date of last goods receipt
 MCHA-FVDT1 Date for unrestricted use
 MCHA-FVDT2 Date for unrestricted use
 MCHA-FVDT3 Date for unrestricted use
 MCHA-FVDT4 Date for unrestricted use
 MCHA-FVDT5 Date for unrestricted use
 MCHA-FVDT6 Date for unrestricted use
 MCHA-HERKL Country of origin of the material
 MCHA-HERKR Region of origin of material (non-preferential origin)
 MCHA-MTVER Export/import material group
 MCHA-QNDAT Next Inspection Date
 MCHA-HSDAT Date of production of the batch
 MCHA-CUOBJ_BM Internal object no.: Batch classification
 MCHA-ZUSCH: Batch Status Key

The following information is logged:

 Date
 Time
 Changed by
 Transaction Code
 Name of transaction
 Table and field changed
 Old value
 New value

The audit trails are recorded under the change document object “CHARGE”.

Batch Master long text audit trail can be displayed by Pharma Pack Tool by
transaction AUT10:

Start transaction AUT10 ‘Evaluation of audit trail: advanced mode’ (click on the

420750868.doc Page 26 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist EU
Acist US

Ezem
BDI
icon ‘Standard – advanced’) and enter:

 Choose “long text” option


 Start date (mandatory)
 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)

Transaction code (MSC2N, MIGO, MB11, MB1B, MB1C, MB31, MIGO_GO, QA11,
QA12, SE38)

Text object (optional), for this long text insert “CHARGE”


Text ID (optional), for this long text insert “VERM”

By pressing execute the system provides the Output of table logs.

UNITY-FSP- Batch Master – Classification AUT10 015 N/A MFG07-01_0130 X X X X X


MFG-06-0130
The batch master is maintained by transaction MSC1N (Batch Master Create) and MSC2N
MSC2N (Batch Master Change). The batch master can be created or changed by
different other transactions (MSC2N, MIGO, MB11, MB1B, MB1C, MB31, MIGO
MIGO_GO, QA11, QA12, SE38).
MB11
Changes on Batch Master Classification can be viewed by: MB1B
A. By change document in Transaction MSC2N or MSC3N:
 Material number MB1C
 Plant MB31
 Batch ID
Go to tab “Classification” QA11
Click on the Icon “Display Change Documents”
All changes are listed and double clicking on the change document it is possible to QA12
see list of the fields that have been changed. SE38

B. By Pharma Pack Tool by transaction AUT10:


Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

 Start date (mandatory)


 Start time (mandatory)
 End date (mandatory)

420750868.doc Page 27 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist EU
Acist US

Ezem
BDI
 End time (mandatory)
 Changed by (optional)
 Transaction code (MSC2N, MIGO, MB11, MB1B, MB1C, MB31,
MIGO_GO, QA11, QA12, SE38)

By pressing execute the system provides the Output of table logs. For each table
log (by row selecting) it is possible to have the details for the following fields:

 AUSP-ATWRT Characteristic value

The following information is logged:

 Date
 Time
 Changed by
 Transaction Code
 Name of transaction
 Table and field changed
 Old value
 New value

The audit trails are recorded under the change document object “CLASSIFY”.

UNITY-FSP- Quality Inspection – Inspection Lot AUT10 016 N/A MFG07-01_0140 X X X


MFG-06-0140
The Inspection lot is maintained by transaction QA02 (Inspection lot change) and QA01 017
QAC2 (Inspection lot quantity change).
QA02
Changes on the Inspection lot can be displayed with Pharma Pack Tool by
transaction AUT10: QAC2
Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter: QA11

 Start date (mandatory) QA12


 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)
 Transaction code (QA02, QAC2, QA11, QA12)

420750868.doc Page 28 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist EU
Acist US

Ezem
BDI
By pressing execute the system provides the Output of table logs. For each table
log (by row selecting) it is possible to have the details for the following fields:

 QALS-LMENGEIST Actual Lot Quantity


 QALS-PASTRTERM Inspection Start Date
 QALS-PAENDTERM End Date of the Inspection
 QALS-KTEXTLOS Short Text
 QALS-LAGORTCHRG Storage location
 QALS-LTEXTKZBB Log Exists for Usage Decision
 QALS-WAPOS Maintenance Item

The following information is logged:

 Date
 Time
 Changed by
 Transaction Code
 Name of transaction
 Table and field changed
 Old value
 New value

The audit trails are recorded under the change document object “QPRUEFLOS”.

Inspection lot long text audit trail can be displayed by Pharma Pack Tool by
transaction AUT10:
Start transaction AUT10 ‘Evaluation of audit trail: advanced mode’ (click on the
icon ‘Standard – advanced’) and enter:

 Choose “long text” option


 Start date (mandatory)
 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)
 Transaction code (QA02, QA11, QA12)

Text object (optional), for this long text insert “QPRUEFLOS” (long text code)
Text ID (optional), for this long text insert “QALS” (long text code)

420750868.doc Page 29 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist EU
Acist US

Ezem
BDI
By pressing execute the system provides the Output of table logs.

UNITY-FSP- Quality Inspection – Usage Decision AUT10 018 N/A MFG07-01_0150 X X X


MFG-06-0150
The usage decision can be inserted or updated by transactions QA11, QA12. QA11 019
Changes on the Inspection lot can be displayed with Pharma Pack Tool by
QA12
transaction AUT10:
Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

 Start date (mandatory)


 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)
 Transaction code (QA11, QA12)

By pressing execute the system provides the Output of table logs. For each table
log (by row selecting) it is possible to have the details for the following fields:

 QALS-STAT34 Stock Postings Completed


 QALS-STAT35 Usage Decision Has Been Made
 QALS-LMENGE01 Quantity Posted to Unrestricted-Use Stock
 QALS-LMENGE02 Quantity Posted to Scrap
 QALS-LMENGE03 Quantity Posted to Sample
 QALS-LMENGE04 Quantity Posted to Blocked Stock
 QALS-LMENGE05 Quantity Posted to Reserves
 QALS-LMENGE06 Quantity Posted to Another Material
 QALS-MATNRNEU Material Number to Which the Quantity is Posted
 QALS-CHARGNEU Batch to Which Goods Are Transferred
 QALS-LMENGE07 Quantity Returned to Vendor
 QALS-LMENGE08 Other Quantity Posted from Inspection Lot Stock
 QALS-LMENGE09 Other Quantity (2) Posted from Inspection Lot Stock
 QALS-LMENGEZUB Quantity That Must Be Posted
 QAVE-VAUSWAHLMG Selected Set of the Usage Decision
 QAVE-VCODEGRP Code Group of the Usage Decision
 QAVE-VCODE Usage Decision Code
 QAVE-VBEWERTUNG Code Valuation
 QAVE-VFOLGEAKTI Follow-Up Action

420750868.doc Page 30 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist EU
Acist US

Ezem
BDI
 QAVE-QKENNZAHL Quality Score
 QAVE-LTEXTKZ LONG TEXT FOR USAGE DECISION
 QAVE-KZART INSPECTION LOT, PARTIAL LOT, SINGLE UNIT,
INTERVAL
 QAVE-ZAEHLER COUNTER FOR USAGE DECISION

The following information is logged:

 Date
 Time
 Changed by
 Transaction Code
 Name of transaction
 Table and field changed
 Old value
 New value

The audit trails are recorded under the change document object “QPRUEFLOS”.

Usage Decision long text audit trail can be displayed by Pharma Pack Tool by
transaction AUT10:
Start transaction AUT10 ‘Evaluation of audit trail: advanced mode’ (click on the
icon ‘Standard – advanced’) and enter:

 Choose “long text” option


 Start date (mandatory)
 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)
 Text object (optional), for this long text insert “QPRUEFLOS”
 Text ID (optional), for this long text insert “QAVE”
 Transaction code (QA11, QA12)

By pressing execute the system provides the Output of table logs.

UNITY-FSP- Quality Inspection – Sample Drawing Procedure QPV2 020 N/A MFG07-01_0160 X X X
MFG-06-0160
AUT10
The sample drawing procedure can be created and modified with transaction
QPV2 (which is calling transaction SM34 in the background).

420750868.doc Page 31 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist EU
Acist US

Ezem
BDI
Changes on the Sample Drawing Procedure can be displayed with Pharma Pack
Tool by transaction AUT10:
Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

 Start date (mandatory)


 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)
 Transaction code (SM34)

By pressing execute the system provides the Output of change documents logs
(object QPRV). For each record (by row selecting) it is possible to have the details
for the following fields:

 QPRVK-GUELTIGAB Valid-from date


 QPRVK-SORTFELD Search Field
 QPRVK-QMASTAUTH Authorization Group QM Basic Data
 QPRVK-GEBANZ Physical-Sample Drawing Based on No. of Containers
 QPRVK-KZQUIT Confirmation Required for Physical-Sample Drawing
 QPRVK-ERSTELLER Name of User Who Created the Data Record
 QPRVK-AENDERER Name of User who Most Recently Changed the Data
Record
 QPRVK-DATUMERST Date on Which the Data Record Was Created
 QPRVK-ZEITERST Time Data Record Was Created
 QPRVK-DATUMAEND Date on Which Data Record Was Changed
 QPRVK-ZEITAEND Time of Last Data Record Change
 QPRVK-KZNVPRZV Sample-drawing Procedure Cannot Be Used
 QPRVK-KZVPRZVPL Sample-Drawing Procedure Is Used in Task List
 QPRVP-LOSGEBEH Lot Container
 QPRVP-PROBNRPL Highest Partial Sample No. Valid for Instruction
 QPRVP-GEBINDE1 Physical-Sample Container for Drawing Primary
Sample
 QPRVP-STPRPLAN1 Sampling Scheme for Primary Sample Stage of
Sample Drawing
 QPRVP-PRSCHAERF1 Insp. Severity in Samp.-Draw. Proc. At Primary
Sample Stage
 QPRVP-AQLWERT1 AQL Value in Primary Sample Stage
 QPRVP-PRANZ1 Fixed No. of Physical Samples for Primary Sample

420750868.doc Page 32 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist EU
Acist US

Ezem
BDI
Stage
 QPRVP-FAKTORPR1 Factor for Determining the Sample Size of a
Primary Sample
 QPRVP-FORMEL1 Formula Field for the Number of Samples
 QPRVP-GEBINDER Physical-Sample Container for Reserve Sample
 QPRVP-ANZRUECKL Number of Reserve Samples
 QPRVP-UMFRUECKL Size of Reserve Sample
 QPRVP-MERUECKL Unit of Measure for Reserve Sample
 QPRVP-GEBINDE2 Physical-Sample Container for Drawing Pooled
Sample
 QPRVP-STPRPLAN2 Sampling Scheme for Pooled Sample Stage of
Sample Drawing
 QPRVP-PRSCHAERF2 Insp. Severity of Sampling Procedure. At Pooled
Sample Stage
 QPRVP-AQLWERT2 AQL Value in Pooled Sample Stage
 QPRVP-PRANZ2 Fixed No. of Physical Samples for Pooled Sample Stage
 QPRVP-FAKTORPR2 Factor for Determining the Sample Size of a Pooled
Sample
 QPRVP-FORMEL2 Formula Field for the Number of Samples
 QPRVP-ERSTELLER Name of User Who Created the Data Record
 QPRVP-AENDERER Name of User who Most Recently Changed the Data
Record
 QPRVP-DATUMERST Date on Which the Data Record Was Created
 QPRVP-ZEITERST Time Data Record Was Created
 QPRVP-DATUMAEND Date on Which Data Record Was Changed
 QPRVP-ZEITAEND Time of Last Data Record Change

The following information is logged:

 Date
 Time
 Changed by
 Transaction Code
 Name of transaction
 Table and field changed
 Old value
 New value

The audit trails are recorded under the change document object “QPRV”.

420750868.doc Page 33 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist EU
Acist US

Ezem
BDI
UNITY-FSP- Quality Inspection – Inspection Method QS31 020 N/A MFG07-01_0170
MFG-06-0170
The inspection method can be created and modified with transaction QS31 AUT10
Changes on the inspection method can be displayed with Pharma Pack Tool by
transaction AUT10:
Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

 Start date (mandatory)


 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)
 Transaction code (SM34)
X X X
By pressing execute the system provides the Output of change documents logs
(object QS31). For each record (by row selecting) it is possible to have the details
for the following fields:

 QPMZ-WERKPM Plant for Inspection Method


 QPMZ-KATAB1 Catalog Entry is a Selected Set
 QPMZ-KATAB2 Catalog Entry is a Selected Set
 QPMZ-KATAB3 Catalog Entry is a Selected Set
 QPMZ-KATAB4 Catalog Entry is a Selected Set
 QPMZ-KATAB5 Catalog Entry is a Selected Set
 QMTB-GUELTIGAB Valid from Date
 QMTB-LOEKZ Status of Master Record

UNITY-FSP- Selected sets for Master Inspection Characteristics AUT10 021 N/A MFG07-01_0200 X X X
MFG-06-0180 The Selected sets is maintained by transaction QS51 (Edit selected set)
QS51
Changes on Sampling Procedure can be viewed by Pharma Pack Tool by
transaction AUT10:
Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

 Start date (mandatory)


 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)

420750868.doc Page 34 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist EU
Acist US

Ezem
BDI
 Changed by (optional)
 Transaction code QS51

By pressing execute the system provides the Output of table logs. For each table
log (by row selecting) it is possible to have the details for the following fields:

 QPAM-KTX01(short description)
 QPAC-CODEGRUPPE (code group)
 QPAC-CODE (code)
 QPAC-BEWERTUNG (valuation)
 QPAC-FEHLKLASSE (defect class)

The following information is logged:

 Date
 Time
 Changed by
 Transaction Code
 Name of transaction
 Table and field changed
 Old value
 New value

UNITY-FSP- Quality Inspection – Master Inspection Characteristics QS31 N/A N/A MFG07-01_0190
MFG-06-0190
The Master Inspection Characteristics are maintained by transaction QS31 (Create QS32
Master Inspection Characteristic) and QS32, QS33, (Change Master Inspection
Characteristic). X X X

Changes on Master Inspection Characteristics are shown by SAP using the Field
history button in QS32/QS33.

UNITY-FSP- Quality Inspection - Inspection Plan AUT10 022 N/A MFG07-01_0180 X X X X X


MFG-06-0200
The Inspection Plan is maintained by transaction QP01 (Create Inspection Plan) QP01
and QP02 (Change Inspection Plan).
QP02
Changes on Inspection Plan can be viewed by Pharma Pack Tool by transaction
AUT10:
Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

420750868.doc Page 35 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist EU
Acist US

Ezem
BDI
 Start date (mandatory)
 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)

Transaction code (QP01 for inspection plan creation and QP02 for inspection plan
changing)
By pressing execute the system provides the Output of table logs. For each table
log (by row selecting) it is possible to have the details for the following fields:

 PLKO-VERWE Task list usage


 PLKO-STATU Status
 PLKO-KTEXT Task list description
 PLKO-DELKZ Indicator: Delete completely in reorganization run
 PLPO-STEUS Control key
 PLPO-LTXA1 Short text
 PLMK-QMTB_WERKS Plant for Inspection Method
 PLMK-PMETHODE Inspection Method
 PLMK-VERWMERKM Master Inspection Characteristics
 PLMK-PROBENR Partial Sample No. for Inspection Charac. in Task List
 PLMK-KURZTEXT Short Text for Inspection Characteristic
 PLMK-STICHPRVER Sampling Procedure in Inspection Characteristic
 PLMK-AUSWMENGE1 Assigned Code Group or Selected Set
 PLMK-PRUEFQUALI: Inspector Qualification
 PLKO-QDYNHEAD: Level at which Dynamic Modification Parameters are
defined
 PLKO-QPRZIEHVER: Sampl Drawing Procedure
 PLMKB-FAKPLANME: Factor for Converting MatUnit of Measure to
SampUnit of Measure
 PLMKB-FAKPROBME: Factor for Converting SampUnitof Measure to
MatUnitof Measure
 RMQSD-REFWERK: Plant
 RMQSD-QUANTITAET: Quantitative characteristic
 RMQSD-QUALITEAT: Qualitative characteristic
 RMQSD-MSEHI: Unit of Measure
 RMQSD-ATNAM: Name of Class Characteristic

The following information is logged:

420750868.doc Page 36 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist EU
Acist US

Ezem
BDI
 Date
 Time
 Changed by
 Transaction Code
 Name of transaction
 Table and field changed
 Old value
 New value

Medium data volume for changes on Inspection Plan.


This information are available in the change object document “PLAN”.
Changes to the material assignment and other changes to the inspection plan can
be checked via transaction QP60/QP61

420750868.doc Page 37 of 81
Project Unity Functional Specification - Audit Trail

5.4 PLANT MAINTENANCE (PM)

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist EU
Acist US

Ezem
BDI
UNITY-FSP- Maintenance Plan AUT10 023 N/A MFG07-01_0220 X
MFG-06-0210
The Maintenance Plan is maintained by transaction IP01 and IP02. IP01
Changes on Maintenance can be viewed by Pharma Pack Tool by transaction
IP02
AUT10:
Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

 Start date (mandatory)


 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)

Transaction code (IP01 or IP02)

By pressing execute the system provides the Output of table logs. For each table
log (by row selecting) it is possible to have the details for the following fields

 MPLA-WARPL: Maintenance Plan


 MPLA-WPTXT: Maintenance Plan Text
 MMPT-ZYKL1: Maintenance cycle
 MMPT-ZEIEH: Unit for the performance of maintenance tasks
 MMPT-PAK_TEXT: Text for maintenance package/cycle
(time/performance)
 MMPT-OFFSET: Maintenance package offset
 MPLA-VSPOS: Shift Factor for Late Completion
 MPLA-TOPOS: Tolerance for Late Completion (%)
 MPLA-VSNEG: Shift Factor for Early Completion
 MPLA-TONEG: Tolerance for Early Completion (%)
 MPLA-SFAKT: Cycle modification factor
 MPLA-HORIZ: Call horizon for maintenance plan calls
 MPLA-ABRHO: Scheduling Period
 MPLA-HUNIT: Unit in scheduling interval

420750868.doc Page 38 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist EU
Acist US

Ezem
BDI
 MPLA-CALL_CONFIRM: Only Create New Call Object After Completing
Predecessor
 MPLA-STRAT: Maintenance Plan Strategy
 MPLA-PLAN_SORT: Sort field for maintenance plans
 MPLA-BEGRU: Technical object authorization group
 MPLA-TPLNR: Functional Location
 MPLA-EQUNR: Equipment Number
 MPOS-PLNTY: Task List Type
 MPOS-PLNNR: Key for Task List Group
 MPOS-PLNAL: Group Counter
 MPLA-START_DATE: Start Date for Scheduling
 MPLA-START_TIME: Start Time for Scheduling
 ITOBATTR-SERUNI: Serial Number

The following information is logged:

 Date
 Time
 Changed by
 Transaction Code
 Name of transaction
 Table and field changed
 Old value
 New value

UNITY-FSP- General Task List AUT10 024 N/A MFG07-01_0230 X


MFG-06-0220
The General Task list is created and maintained by transaction IA05 and IA06. IA05
Changes on Maintenance can be viewed by Pharma Pack Tool by transaction
IA06
AUT10:
Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:
 Start date (mandatory)
 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)

Transaction code (IA05 or IA06)

420750868.doc Page 39 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist EU
Acist US

Ezem
BDI
By pressing execute the system is provided the Output of table logs. For each
table log (by row selecting) it is possible to have the details for the following
fields:

 PLKO-PLNNR: Key for Task List Group


 PLKO-PLNAL: Group Counter
 PLKO-KTEXT: Task List Description
 PLKO-WERKS: Plant
 PLKO-STATU: Status
 PLPO-PLNNR: Key for Task List Group
 PLPO-VORNR: Operation/Activity Number
 PLPO-LTXA1: Operation short text
 PLPO-WERKS: Plant

The following information is logged:

 Date
 Time
 Changed by
 Transaction Code
 Name of transaction
 Table and field changed
 Old value
 New value

UNITY-FSP- Maintenance Order AUT10 025 N/A MFG07-01_0240 X


MFG-06-0230
Maintenance order is created and maintained by transaction IW31, IW32 and IW31
IW33.
IW32
Changes on Maintenance can be viewed by Pharma Pack Tool by transaction
AUT10: IW33
Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

 Start date (mandatory)


 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)
 Transaction code (IW31, IW32)

420750868.doc Page 40 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist EU
Acist US

Ezem
BDI
By pressing execute the system is provided the Output of table logs. For each
table log (by row selecting) it is possible to have the details for the following
fields:

 AUFK- AUFNR : Order Number


 AUFK- WERKS : Plant
 AUFK- ERDAT : Created on
 AUFK- IDAT2 : Technical Completion date
 AUFK- IDAT3 : Close Date
 AUFK- AUART : Order Type
 AFIH -EQUNR : Equipment Number
 AFIH -WARPL : Maintenance Plan
 AFIH -ABNUM : Maintenance Plan Call Number
 AFIH -WAPOS : Maintenance item
 AFIH-ADDAT : PM Order: Reference Date

The following information is logged:

 Date
 Time
 Changed by
 Transaction Code
 Name of transaction
 Table and field changed
 Old value
 New value

UNITY-FSP- Schedule Maintenance Plan AUT10 026 N/A MFG07-01_0250 X


MFG-06-0240
Maintenance Plan scheduling is created by transaction IP10. IP10
Changes on Maintenance can be viewed by Pharma Pack Tool by transaction
IP30
AUT10:
Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

 Start date (mandatory)


 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)

420750868.doc Page 41 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist EU
Acist US

Ezem
BDI
 Changed by (optional)
Transaction code (IP10)

By pressing execute the system provides the Output of table logs. For each table
log (by row selecting) it is possible to have the details for the following fields:

 AUFK- AUFNR : Order Number


 AUFK- WERKS : Plant
 AUFK- ERDAT : Created on
 AUFK- IDAT2 : Technical Completion date
 AUFK- IDAT3 : Close Date
 AUFK- AUART : Order Type
 AFIH -EQUNR : Equipment Number
 AFIH -WARPL : Maintenance Plan
 AFIH -ABNUM : Maintenance Plan Call Number
 AFIH -WAPOS : Maintenance item
 AFIH-ADDAT : PM Order: Reference Date

The following information is logged:

 Date
 Time
 Changed by
 Transaction Code
 Name of transaction
 Table and field changed
 Old value
 New value

Maintenance Plan scheduling is created by transaction IP30.


Changes on Maintenance can be viewed by Pharma Pack Tool by transaction
AUT10:
Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

 Start date (mandatory)


 Start time (mandatory)
 End date (mandatory)
 End time (mandatory)
 Changed by (optional)

420750868.doc Page 42 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist EU
Acist US

Ezem
BDI
Transaction code (IP30)

By pressing execute the system provides the Output of table logs. For each table
log (by row selecting) it is possible to have the details for the following fields:

 AUFK- AUFNR : Order Number


 AUFK- WERKS : Plant
 AUFK- ERDAT : Created on
 AUFK- IDAT2 : Technical Completion date
 AUFK- IDAT3 : Close Date
 AUFK- AUART : Order Type
 AFIH -EQUNR : Equipment Number
 AFIH -WARPL : Maintenance Plan
 AFIH -ABNUM : Maintenance Plan Call Number
 AFIH -WAPOS : Maintenance item
 AFIH-ADDAT : PM Order: Reference Date

The following information is logged:

 Date
 Time
 Changed by
 Transaction Code
 Name of transaction
 Table and field changed
 Old value
 New value

UNITY-FSP- Equipment AUT10 027 N/A MFG07-01_0210 X X X


MFG-06-0250
The Equipment is maintained by transaction IE01 (Create equipments) and IE02 IE01
(Change equipments).
IE02
Changes on Equipment can be viewed by Pharma Pack Tool by transaction
AUT10:
Start transaction AUT10 ‘Evaluation of audit trail: standard mode’ and enter:

 Start date (mandatory)


 Start time (mandatory)
 End date (mandatory)

420750868.doc Page 43 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist EU
Acist US

Ezem
BDI
 End time (mandatory)
 Changed by (optional)
 Transaction code (IE01 for equipment creation and IE02 for
equipment changing)

By pressing execute the system provides the Output of table logs. For each table
log (by row selecting) it is possible to have the details for the following fields:

 EQUI-EQART Type of Technical Object


 EQKT-EQKTX Description of technical object
 AUSP-ATFLV Internal floating point from
 AUSP-ATAWE Unit of Measurement
 AUSP-ATAW1 Unit of Measurement
 KSSK-STATU Classification status
 JSTO-STSMA Status profile
 JEST-STAT Object status

The following information is logged:

 Date
 Time
 Changed by
 Transaction Code
 Name of transaction
 Table and field changed
 Old value
 New value

Small data volume for changes on equipment.

420750868.doc Page 44 of 81
Project Unity Functional Specification - Audit Trail

5.5 PURCHASING (PUR)


MASTER DATA

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist US

Acist EU

Ezem
BDI
UNITY-FSP- Vendor Master AUT10 N/A N/A MFG07-01_0260 X X X X
MFG-06-0260
The vendor master is together with material master, one of the master data MK03
needed in purchasing area.
SE16
Changes on Vendor master can be viewed by:
Transaction MK03 (select all the views for General and Purchasing organization
data)
Go to menu to -> Environment -> Field changes
All changes are displayed for General and Purchasing organization data
SE16 Table CDHDR:
Change doc. object = KRED, KRED_N
Object value = 10 character vendor number (leading zero’s required!)
(Document number)
SE16 Table CDPOS:
Change doc. object = KRED, KRED_N
Object value = 10 character vendor number (leading zero’s required!)
(Document number)

Following field cannot be modified (key fields)


LFA1-LIFNR: Vendor Account Nr.

The following fields are used for the determination of the vendor as unique and
the changes to these fields are logged as explained below:

Name and Address Data:


LFA1-NAME1: Vendor Name
LFA1-STRAS: Street/House number
LFA1-PSTLZ: Postal Code
LFA1-ORT01: City
LFA1-LAND1: Country

Purchasing data:

420750868.doc Page 45 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist US

Acist EU

Ezem
BDI
LFM1-SPERM: Purchasing block at purchasing organization level
LFM1-LOEVM: Delete flag for vendor at purchasing level

Partner Data:
WYT3-DEFPA: vendor partner functions

The following information is logged:


Date
Time
Changed by
Which field was changed
Old and new values

PURCHASING PROCESS

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist US

Acist EU

Ezem
BDI
UNITY-FSP- Purchase Order AUT10 N/A N/A MFG07-01_0270 X X X X
MFG-06-0270
Changes on Purchase Order can be viewed by: ME23N
Transaction ME23N:
SE16
Select the PO document number
SE16 Table CDHDR:
Object Class= EINKBELEG
Object id= PO Document number
Changer = 10 digit change number
SE16 Table CDPOS:
Object Class= EINKBELEG
Object id= PO Document number

420750868.doc Page 46 of 81
Project Unity Functional Specification - Audit Trail

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist US

Acist EU

Ezem
BDI
Changenr = 10 digit change number

Following fields cannot be modified


EKKO-LIFNR: Vendor,
EKPO-WERKS: Plant,
EKPO-MATKL: Aggregate code (fixed at material level)
EKKO-LIFN2: Source
Following fields changes are logged as explained below:
EKPO-EMATN: Material code,
EKET-CHARG: Batch-id
EKET-WEMNG: Quantity of Goods Received

The following information is logged:


Changed by (Username)
Date
Time
Which field was changed (Old and new values).

420750868.doc Page 47 of 81
Project Unity Functional Specification - Audit Trail

5.6 STANDARD SAP DEFAULT CONFIGURATION

Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference

Acist Asia
Acist US

Acist EU

Ezem
BDI
UNITY-FSP- Change Objects for Audit Trail are already defaulted for other GxP critical fields in N/A N/A N/A MFG07-01_0010
MFG-06-0280 SAP and don’t need any further customization in the system. MFG07-01_0020
In the table below the objects are listed. MFG07-01_0030
MFG07-01_0040
MFG07-01_0050
MFG07-01_0060
MFG07-01_0070
MFG07-01_0080
MFG07-01_0090
MFG07-01_0100
MFG07-01_0110
MFG07-01_0120
MFG07-01_0130
MFG07-01_0140 X X X X X
MFG07-01_0150
MFG07-01_0160
MFG07-01_0170
MFG07-01_0180
MFG07-01_0190
MFG07-01_0200
MFG07-01_0210
MFG07-01_0220
MFG07-01_0230
MFG07-01_0240
MFG07-01_0250
MFG07-01_0260
MFG07-01_0270

Business object

420750868.doc Page 48 of 81
Project Unity Functional Specification - Audit Trail

Technical field/tables Description Transactions

VEPO-POSNR Delivery item VL32N/HU02/HUMO

VEPO-QPLOS Inspection Lot Number VL32N/HU02/HUMO

AFKO-BMENGE Base quantity COR1/COR2/COR5/COR7/CORM/COR8

AFKO- SFCPF Production scheduling profile COR1/COR2/COR5/COR7/CORM/COR8

AFKO-STLST BOM status COR1/COR2/COR5/COR7/CORM/COR8

AFPO-DAUAT Order type COR1/COR2/COR5/COR7/CORM/COR8

AFPO-XLOEK Deletion flag COR1/COR2/COR5/COR7/CORM/COR8

AFPO-CHARG Batch number COR1/COR2/COR5/COR7/CORM/COR8

AFPO-SERNR BOM explosion number COR1/COR2/COR5/COR7/CORM/COR8

AFPO-UNTTO Under delivery tolerance limit COR1/COR2/COR5/COR7/CORM/COR8

AFVV-BMSCH Base quantity COR1/COR2/COR5/COR7/CORM/COR8

AFVV-BMSCH Base quantity COR6/CORR/CORS

AFVV-MGVRG Operation quantity COR6/CORR/CORS

AUFK-AUART Order type COR1/COR2/COR5/COR7/CORM/COR8

AUFK-ASTNR Order status COR1/COR2/COR5/COR7/CORM/COR8

AUSP-ATWRT Characteristic value MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38

AUSP-ATWRT Characteristic value (Multiple C201/C202


permitted values for
AUSP-ATWRT Characteristic value CRC1/CRC2

CABN-ATNAM Characteristic name C201/C202

CAWN-ATCOD Code for value dependency CT04

CAWN-ATFLB Internal floating point value CT04


to

420750868.doc Page 49 of 81
Project Unity Functional Specification - Audit Trail

CAWN-ATFLV Internal floating point from CT04

CAWN-ATIDN Object identification CT04

CAWN-ATINN Internal characteristic CT04

CAWN-ATPRZ Indicator: Tolerance Shown CT04


as a Percentage
CAWN-ATSTD Default value CT04

CAWN-ATTLB Tolerance to CT04

CAWN-ATTLV Tolerance from CT04

CAWN-ATWRT Characteristic value CT04

CAWN-LKENZ Deletion indicator CT04

CAWN-SPRAS Language key CT04

CAWN-TXTNR Number of Related Text CT04

CRHD-ARBPL Resource C201/C202

CRHD-ARBPL Resource CRC1/CRC2

CRHD-RGEKZ Indicator: Backflushing CRC1/CRC2

CRHD-STEUS Control key C201/C202

CRHD-VGWTS Standard value key CRC1/CRC2

CRTX-KTEXT Short description CRC1/CRC2

KLAH-BISDT Valid-to date CL01/CL02

KLAH-STATU Class status CL01/CL02

KLAH-VONDT Valid-from date CL01/CL02

KOTH030-AUART Order type COB1/COB2

KOTH030-KAPPL Application COB1/COB2

420750868.doc Page 50 of 81
Project Unity Functional Specification - Audit Trail

KOTH030-KNUMH Condition record number COB1/COB2

KOTH030-DATAB Validity start date of the COB1/COB2


condition record
KOTH030-DATBI Validity end date of the COB1/COB2
condition record
KOTH030-KSCHL Batches: Search strategy COB1/COB2
type
KOTH031-AUART Order type COB1/COB2

KOTH031-KAPPL Application COB1/COB2

KOTH031-KNUMH Condition record number COB1/COB2

KOTH031-DATAB Validity start date of the COB1/COB2


condition record
KOTH031-DATBI Validity end date of the COB1/COB2
condition record
KOTH031-KSCHL Batches: Search strategy COB1/COB2
type
KSML-IMERK Internal characteristic CL01/CL02

KSML-OMERK Object-Dependent CL01/CL02


Characteristic
Long text batch master MSC1N/MSC2N

QAVE - LTEXTKZ Long text Usage decision QA11/QA12

LUBU-LGOR1 Storage location LU02

LUBU-LGOR2 Storage location LU02

LUBU-QPLOS Inspection Lot Number LU02

MARA-IPRKZ Period indicator for shelf life MM01/MM02


expiration date
MARA-MEINS Base unit of measure MM01/MM02

MARA-MHDHB Total shelf life MM01/MM02

MARA-MHDLP Storage percentage MM01/MM02

MARA-RAUBE Storage conditions MM01/MM02

420750868.doc Page 51 of 81
Project Unity Functional Specification - Audit Trail

MARA-RDMHD Rounding rule for calculation MM01/MM02


of SLED
MARA-TEMPB Temperature conditions MM01/MM02
indicator
MARA-TRAGR Transportation group MM01/MM02

MARC-AUSME Unit of issue MM01/MM02

MARC-FRTME Production unit MM01/MM02

MARC-INSMK Post to Inspection Stock MM01/MM02

MARC-KZDKZ Documentation required MM01/MM02


indicator
MARC-KZECH Determination of batch entry MM01/MM02
in the production/process
MARC-MMSTA Plant-Specific Material Status MM01/MM02

MARC-QMATA Material Authorization Group MM01/MM02


for Activities in QM
MARC-QMATV Inspection Setup Exists for MM01/MM02
Material/Plant
MARC-VERKZ Version indicator MM01/MM02

MARC-XCHAR Batch management indicator MM01/MM02


(internal)
MCHA-BWTAR Valuation type MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38

MCHA-CHAME Unit of issue for batch MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38


(deactivated)
MCHA-CHARG Batch number MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12/SE38

MCHA-CUOBJ_BM Internal object no.: Batch MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38


classification
MCHA-ERSDA Creation date MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38

MCHA-FVDT1 Date for unrestricted use MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38

MCHA-FVDT2 Date for unrestricted use MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38

MCHA-FVDT3 Date for unrestricted use MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12/SE38

MCHA-FVDT4 Date for unrestricted use MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38

420750868.doc Page 52 of 81
Project Unity Functional Specification - Audit Trail

MCHA-FVDT5 Date for unrestricted use MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38

MCHA-FVDT6 Date for unrestricted use MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38

MCHA-HERKL Country of origin of the MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38


material
MCHA-HERKR Region of origin of material MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38
(non-preferential origin)
MCHA-HSDAT Date of production of the MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38
batch
MCHA-LAEDA Date of last change MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38

MCHA-LICHA Vendor batch number MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38

MCHA-LIFNR Vendor's account number MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38

MCHA-LVORM Deletion Flag for All Data on MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38


a Batch at a Plant
MCHA-LWEDT Date of last goods receipt MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38

MCHA-MTVER Export/import material group MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38

MCHA-QNDAT Next Inspection Date MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12/SE38

MCHA-VERAB Availability date MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12/SE38

MCHA-VFDAT Shelf Life Expiration Date MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38

MCHA-VLCHA Original batch number MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38


(deactivated)
MCHA-ZAEDT Date of last status change MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38

MCHA-ZUSTD Batch in restricted-use stock MSC2N/MIGO/MB11/MB1B/MB1C/MB31/MIGO_GO/QA11/QA12 /SE38

MKAL-ADATU Valid from date C201/C202/C223

MKAL-BDATU Valid to date C201/C202/C223

MKAL-BSTMA To lot size C201/C202/C223

MKAL-BSTMI From lot size C201/C202/C223

MKAL-TEXT1 Short text for production C201/C202/C223


version

420750868.doc Page 53 of 81
Project Unity Functional Specification - Audit Trail

P3000-LGORT_RES Storage location storage CRC1/CRC2


resource
PKHD-LGNUM Warehouse Number / LPK2
Warehouse Complex
PKHD-LGPLA Storage bin LPK2

PKHD-LGTYP Storage Type LPK2

PLKO-BMSCH Base quantity C201/C202

PLKO-KTEXT Master recipe description C201/C202

PLKO-MEINH Unit of measure of base C201/C202


quantity
PLKO-PLNME Unit of measure of charge C201/C202
quantity
PLKO-STATU Status C201/C202

PLKO-UMREN Conversion factor (operation C201/C202


quantity)
PLKO-UMREZ Conversion factor (charge C201/C202
quantity)
PLKO-VERWE Usage C201/C202

PLMKB-AUSWMENGE1 Assigned Code Group or QP01/QP02/C201/C202


Selected Set
PLMKB-DUMMY10 Text Line for Additional QP01/QP02/C201/C202
Information
PLMKB-DUMMY20 Text Line for Additional QP01/QP02/C201/C202
Information
PLMKB-DUMMY40 Text Line for Additional QP01/QP02/C201/C202
Information
PLMKB-KURZTEXT Short Text for Inspection QP01/QP02/C201/C202
Characteristic
PLMKB-MKVERSION Version Number of the QP01/QP02/C201/C202
Master Inspection
PLMKB-PMETHODE Inspection Method QP01/QP02/C201/C202

PLMKB-PMTVERSION Version Number of the QP01/QP02/C201/C202


Inspection Method
PLMKB-PROBEMGEH Sample Unit of Measure QP01/QP02/C201/C202

PLMKB-PROBENR Partial Sample No. for QP01/QP02/C201/C202


Inspection Charac. in Task

420750868.doc Page 54 of 81
Project Unity Functional Specification - Audit Trail

PLMKB-PRUEFEINH Sample Quantity Factor for QP01/QP02/C201/C202


Sample
PLMKB-QMTB_WERKS Plant for Inspection Method QP01/QP02/C201/C202

PLMKB-QPMK_WERKS Plant QP01/QP02/C201/C202

PLMKB-STICHPRVER Sampling Procedure in QP01/QP02/C201/C202


Inspection Characteristic
PLMKB-VERWMERKM Master Inspection QP01/QP02/C201/C202
Characteristics
PLMKB-VSTEUERKZ Key Containing Preset QP01/QP02/C201/C202
Characteristic Control
PLMZ- LGORT Storage location storage C201/C202
resource
PLPO- USR04 Minimum Yield CS01/CS02

PLPO-ARBID Resource C201/C202

PLPO-BMSCH Base quantity C201/C202

PLPOD-AUFAK Scrap factor QP01/QP02

PLPOD-BMSCH Base quantity QP01/QP02

PLPOD-KTSCH Standard text key QP01/QP02

PLPOD-LTXA1 Short text QP01/QP02

PLPOD-MEINH Unit of measure QP01/QP02

PLPOD-STEUS Control key QP01/QP02

PLPOD-VORNR Operation Number QP01/QP02

PLPO-MEINH Unit of measure for operation C201/C202

PLPO-SLWID Key User field CS01/CS02

PLPO-STEUS Control key C201/C202

PLPO-UMREN Conversion factor (Operation C201/C202


quantity)
PLPO-UMREZ Conversion factor (Charge C201/C202
quantity)

420750868.doc Page 55 of 81
Project Unity Functional Specification - Audit Trail

PLPO-USR05 Maximum Yield CS01/CS02

PLPO-VORNR Operation / phase number C201/C202

PLPO-VORNR Phase number C201/C202

QALS-LAGORTCHRG Storage location QAC2

QAVE-LTEXTKZ LONG TEXT FOR USAGE QA11/QA12


DECISION
QAVE-QKENNZAHL Quality Score QA11/QA12

QAVE-VAUSWAHLMG Selected Set of the Usage QA11/QA12


Decision
QAVE-VBEWERTUNG Code Valuation QA11/QA12

QAVE-VCODE Usage Decision Code QA11/QA12

QAVE-VCODEGRP Code Group of the Usage QA11/QA12


Decision
QAVE-VFOLGEAKTI Follow-Up Action QA11/QA12

QCPR-CERTNO Certificate QC52

QCPR-CHARG Batch number QC52

QCPR-EBELN Purchasing Document QC52


Number
QCPR-EBELP Item Number of Purchasing QC52
Document
QCPR-HERSTELLER Number of Manufacturer QC52

QCPR-LFSNR Number of external delivery QC52


note
QCPR-LICHN Vendor batch number QC52

QCPR-LIFNR Vendor's account number QC52

QCPR-MATNR Material number QC52

QCPR-MBLNR Number of material QC52


document
QCPR-STATUS Certifcate Status QC52

420750868.doc Page 56 of 81
Project Unity Functional Specification - Audit Trail

QCPR-WERKS Plant QC52

QCPR-ZGTYP Certificate Type QC52

QDDRT-KURZTEXT Short Text QDR1/QDR2

QDPA-STPRUMF Number of Sampling Units in QDP1/QDP2


a Sample
QDPK-KZNVWPK Indicator: Sampling Scheme QDP1/QDP2
Cannot Be Used
QDSV-BEWERTMOD Valuation Mode QDV1/QDV2

QDSV-KZNVWSV Sampling Procedure Cannot QDV1/QDV2


Be Used
QDSV-KZOHI No Inspection Stage Change QDV1/QDV2

QDSV-QRKART Control Chart Type QDV1/QDV2

QDSV-STICHPRART Sampling Type QDV1/QDV2

QDSV-KZRAST Indicator: Sampling QDV1/QDV2


Procedure for Inspection
QDSV-STPRUMF Number of Sampling Units in QDV1/QDV2
a Sample
QDSV-ANNAHMEZ Acceptance Number QDV1/QDV2

QDSV-RASTER Frequency QDV1/QDV2

QDWV-KZPKTOH Without Inspection Points QDV1/QDV2

QDWV-KZPKTPM Inspection Points for Plant QDV1/QDV2


Maintenance
QDWV-KZPKTPP Freely-Defined Inspection QDV1/QDV2
Points
QDWV-KZPKTPV Inspection Points for Sample QDV1/QDV2
Management
QFLTP-LOSUMF Lot Size QDP1/QDP2

QFLTP-SOLLWERT Target Value for a QP01/QP02


Quantitative Characteristic
QFLTP-TOLERANZOB Upper Specification Limit QP01/QP02

QPRS-ABDAT storage until QPR1/QPR2

420750868.doc Page 57 of 81
Project Unity Functional Specification - Audit Trail

QPRS-ABDAU Storage Duration of the QPR1/QPR2


Physical Sample in Days
QPRS-ABINF storage information on the QPR1/QPR2
physical sample
QPRS-ABORT sample location QPR1/QPR2

QPRS-CHARG batch QPR1/QPR2

QPRS-GBTYP Physical-Sample Container QPR1/QPR2

QPRS-KTEXT Short Text for Physical QPR1/QPR2


Sample
QPRS-MATNR material QPR1/QPR2

QPRS-MEINH Unit of Measure for Physical QPR1/QPR2


Sample Size
QPRS-MENGE Size of the Physical Sample QPR1/QPR2

QPRS-PRTYP Physical-Sample Category QPR1/QPR2

QPRVK Sample-drawing procedure QPV2/SM34

QPRVP Sample-drawing items QPV2/SM34

RESB-CHARG Batch number COR1/COR2/COR5/COR7/CORM/COR8

RESB-FMENG Quantity is fixed COR1/COR2/COR5/COR7/CORM/COR8

RESB-KZECH Determination of batch entry COR1/COR2/COR5/COR7/CORM/COR8


in the production/process
RESB-RGEKZ Indicator: Backflush COR1/COR2/COR5/COR7/CORM/COR8

RESB-SERNR BOM explosion number COR1/COR2/COR5/COR7/CORM/COR8

RQPAS-QUALITAT Qualitative Characteristic QP01/QP02

RQPAS-QUANTITAT Quantitative Characteristic QP01/QP02

STKO-BMENG Base Quantity CS01/CS02

STKO-STLST BOM status CS01/CS02

STPO-IDNRK BOM component C201/C202

420750868.doc Page 58 of 81
Project Unity Functional Specification - Audit Trail

STPO-IDNRK Component C201/C202

STPO-IDNRK Component CS01/CS02

STPO-MENGE Requirement Quantity C201/C202

STPO-MENGE Requirement Quantity CS01/CS02

STPO-POSNR BOM component number C201/C202

STPO-POSNR BOM item number CS01/CS02

STPO-POSTP Item category C201/C202

STPO-POSTP Item Category CS01/CS02

VEPO-BESTQ Stock category in the VL32N/HU02/HUMO


Warehouse Management
VEPO-CHARG Batch number VL32N/HU02/HUMO

VEPO-HU_LGORT Content is Located at an HU- VL32N/HU02/HUMO


managed Storage Location
VEPO-VBELN Delivery VL32N/HU02/HUMO

420750868.doc Page 59 of 81
Project Unity Functional Specification - Audit Trail

6. OVERVIEW OF SAP TRANSACTIONS


6.1 SAP TRANSACTIONS

Transaction Code Transaction Title

AUT10 Evaluation of Audit Trail: Standard Mode

CS01 Create Material BOM : Initial screen

CS02 Change Material BOM: Initial screen

CS03 Display Material BOM : Initial screen

C201 Create Master Recipe : Initial screen

C202 Change Master Recipe: Initial screen

C203 Display Master Recipe: Initial screen

C223 Production Version: Mass Processing

CRC1 Create Resource: Initial screen

CRC2 Change Resource: Initial screen

CRC3 Display Resource: Initial screen

COB1 Create batch search strategy: Initial screen

COB2 Change batch search strategy: Initial screen

MBC1 Create batch search strategy: Initial screen

MBC2 Change batch search strategy: Initial screen

CL01 Create Class

CL02 Change Class

CT04 Characteristics

LB02 Change transfer requirement: Initial screen

LU01 Create Posting Notice

LU02 Change Posting Notice

LS02N Change Storage Bin

LS02 Change Storage Bin

420750868.doc Page 60 of 81
Project Unity Functional Specification - Audit Trail

Transaction Code Transaction Title

LS06 Block/Unblock Several Bins Simoultaneously

COR1 Create Process Order: Initial screen

COR2 Change Process Order: Initial screen

COR3 Display Process Order: Initial screen

CORO Create Process Order w/o Material: Initial screen

COR6 Enter Process Order Confirmation: Initial screen

COR7 Convert Planned Order to Proc. Order

COR8 Collective Conversion of Planned Orders: : Initial screen

CORM Mass Processing for orders

CO44 Mass processing for orders

CORR Collective Entry: Time Ticket

CORS Cancel Process Order Confirmation: Initial screen

CORT Display Process Order Confirmation: Initial screen

CR10 Display Resource Changes: Initial screen

IE01 Create Equipment: Initial screen

IE02 Change Equipment: Initial screen

IE03 Display Equipment: Initial screen

IA05 Create general task list: Initial screen

IA06 Change General Maintenance Task List: Initial screen

IP01 Create Maintenance Plan: Initial screen

IP02 Change Maintenance Plan: Initial screen

IP10 Schedule Maintenance Plan: Initial screen

IP30 Deadline Monitoring for Maintenance Plans (Batch Input IP10)

IW31 Create Maintenance Order: Initial screen

IW32 Change Maintenance Order: Initial screen

IW33 Display Maintenance Order: Initial screen

MB11 Enter Goods Movement: Initial screen

420750868.doc Page 61 of 81
Project Unity Functional Specification - Audit Trail

Transaction Code Transaction Title

MB31 Goods Receipt for Order: Initial screen

MIGO Goods Movement

MB1B Enter Transfer Posting: Initial screen

MB1C Enter Other Goods Receipts: Initial screen

MM01 Create material master: Initial screen

MM02 Change material master: Initial screen

MM03 Display material master: Initial screen

MSC2N Change batch

MSC3N Display batch

QA01 Create Inspection Lot Manually: Initial screen

QA02 Change Inspection Lot: Initial screen

QA03 Display Inspection Lot: Initial screen

QAC2 Transfer Insp. Lot Quant. (Plnt To Plnt, StorLoc to StorLoc)

QA11 Record usage decision: Initial screen

QA12 Change usage decision: Initial screen

QA13 Display usage decision: Initial screen

QDV1 Create sampling procedure: Initial screen

QDV2 Change sampling procedure: Initial screen

QDV3 Display sampling procedure: Initial screen

QP01 Create Inspection Plan: Initial screen

QP02 Change Inspection Plan: Initial screen

QP03 Display Inspection Plan: Initial screen

QS21 Create master insp. Characteristic: Initial screen

QS22 Change master insp. Version: Initial screen

QS23 Change master insp. Version: Initial screen

QS31 Create inspection method: Initial screen

QS32 Change inspection method: Initial screen

420750868.doc Page 62 of 81
Project Unity Functional Specification - Audit Trail

Transaction Code Transaction Title

QS33 Display inspection method: Initial screen

SE38 ABAP Editor

SM30 Call View Maintenance

420750868.doc Page 63 of 81
Project Unity Functional Specification - Audit Trail

6.2 CUSTOMIZING ACTIVITIES

Cust. No Customizing Description with Values T. Code or Path

001 Customizing setting for Batch Search strategy for inventory movement Audit Trail AUT01
In transaction AUT01 the logging flag will be activated for the table KONDH AUT02
In transaction AUT02 the following links between transaction and tables will be defined:

Trans. Table
MBC1 KONDH
MBC2 KONDH

002 Customizing setting for Posting Change Audit Trail AUT01


In transaction AUT01 the logging flag will be activated for the following fields: AUT02
o LUBU-STATU Status of posting change

Activate table logging for the following table:


- LUBU

In transaction AUT02 the following links between transaction and tables will be defined:

Trans. Table
LU02 LUBU

420750868.doc Page 64 of 81
Project Unity Functional Specification - Audit Trail

Cust. No Customizing Description with Values T. Code or Path

003 Customizing setting for WM Control Cycle Audit Trail AUT01


In transaction AUT01 the logging flag will be activated for the following fields: AUT02
o PKHD-NKDYN Indicator: dynamic destination bin
o PKHD-BERKZ Material staging indicator for production supply

Activate table logging for the following table:


- PHKD

In transaction AUT02 the following links between transaction and tables will be defined:

Trans. Table
LPK2 PKHD

004 Customizing setting for Material Master Audit Trail AUT01


In transaction AUT01 the logging flag will be activated for the following fields: AUT02
o MARC-XCHAR Batch management indicator (internal)
o MARC-MMSTA Plant-Specific Material Status
o MARC-AUSME Unit of issue
o MARC-INSMK Post to Inspection Stock
o MARC-KZDKZ Documentation required indicator
o MARC-VERKZ Version indicator
o MARC-FRTME Production unit
o MARC-QMATV Inspection Setup Exists for Material/Plant
o MARC-QMATA Material Authorization Group for Activities in QM
o MARC-KZECH Determination of batch entry in the production/process order
o MARA-MEINS Base unit of measure
o MARA-RAUBE Storage conditions
o MARA-TEMPB Temperature conditions indicator
o MARA-TRAGR Transportation group
o MARA-MHDHB Total shelf life
o MARA-MHDLP Storage percentage
o MARA-IPRKZ Period indicator for shelf life expiration date
o MARA-RDMHD Rounding rule for calculation of SLED
o MARM-MEINH Alternative unit of measure for stock keeping

In transaction AUT02 the following links between transaction and tables will be defined:

420750868.doc Page 65 of 81
Project Unity Functional Specification - Audit Trail

Cust. No Customizing Description with Values T. Code or Path

Trans. Table
MM01 MARA
MM02 MARA
MM03 MARA
MM01 MARC
MM02 MARC
MM03 MARC
005 Customizing setting for Material Bom Audit Trail AUT01
In transaction AUT01 the logging flag will be activated for the following fields: AUT02
o STKO-AENNR Change Number
o STPO-AUSCH Component scrap %
o STKO-DATUV Valid from date
o STPO-FMENG Fixed Quantity
o MAST-MATNR Material Number
o STPO-MEINS Unit of measure
o STPO-REKRS Recursiveness allowed
o MAST-STLAL Alternative BOM
o MAST-STLAN BOM usage
o MAST-WERKS Plant
o MAST_STLNR Bill of Material

In transaction AUT02 the following links between transaction and tables will be defined:

Trans. Table
CS01 MAST
CS01 STKO
CS01 STOP
CS02 MAST
CS02 STKO
CS02 STOP

006 Customizing setting for Recipe and Production Version Audit Trail AUT01
In transaction AUT01 the logging flag will be activated for the following fields: AUT02
o PLKO-AENNR Change number

420750868.doc Page 66 of 81
Project Unity Functional Specification - Audit Trail

Cust. No Customizing Description with Values T. Code or Path


o PLKO-LOSBS Charge quantity (to)
o PLKO-LOSVN Charge quantity (from)
o MAPL-MATNR Material number
o PLPO-PHFLG Phase indicator
o PLPO-PHSEQ Control recipe destination
o MAPL-PLNAL Recipe counter
o PLKO-PLNAL Recipe counter
o PLKO-PLNNR Recipe group
o PLKO-PROFIDNETZ Profile
o STPO-REKRS Recursiveness allowed
o MKAL-STLAL Alternative BOM number
o MKAL-STLAN Alternative BOM usage
o MKAL-VERID Production version number
o MAPL-WERKS Plant
o PLPO-WERKS Plant

In transaction AUT02 the following links between transaction and tables will be defined:

Trans. Table
C201 PLKO
C201 PLPO
C201 STPO
C201 MKAL
C202 PLKO
C202 PLPO
C202 STPO
C202 MKAL
C223 MKAL

008 Customizing setting for Resource Audit Trail AUT01


In transaction AUT01 the logging flag will be activated for the following fields: AUT02
o CRHD-MIXMAT Indicator: mixing of material allowed
o CRHD-PLANV Usage
o CRHD-PRVBE Supply area

420750868.doc Page 67 of 81
Project Unity Functional Specification - Audit Trail

Cust. No Customizing Description with Values T. Code or Path


o CRHD-VERAN Person responsible
o CRHD-WERKS Plant
o CHRD-PAR01 First Work Center Parameter (for formulas)
o CHRD-PAR02 Second Work Center Parameter (for formulas)
o CHRD-PAR03 Third Work Center Parameter (for formulas)
o CHRD-PAR04 Fourth Work Center Parameter (for formulas)
o CHRD-PAR05 Fifth Work Center Parameter (for formulas)
o CHRD-PAR06 Sixth Work Center Parameter (for formulas)

009 Customizing setting for Batch Search strategy for process order Audit Trail AUT01
In transaction AUT01 the logging flag will be activated for the following fields: AUT02
o KOTH031-CO_MATNR Material number for order
o KOTH031-MANDT Client
o KOTH030-MATNR Material number
o KOTH031-MATNR Material number
o KOTH030-WERKS_D Plant
o KOTH031-WERKS_D Plant
o KONDH-CHSPL Number of batch splits can be changed
o KONDH-CHMDG Batches: Dialog batch determination
o KONDH-CHMVS Batches: Exit to quantity proposal
o KONDH-CHMAN Manual batch determination
o KONDH-CHVLL Overdelivery allowed in batch determination

In transaction AUT02 the following links between transaction and tables will be defined:

Trans. Table
COB1 KOTH031
COB1 KOTH030
COB2 KOTH031
COB2 KOTH030
COB1 KONDH
COB2 KONDH

420750868.doc Page 68 of 81
Project Unity Functional Specification - Audit Trail

Cust. No Customizing Description with Values T. Code or Path

010 Customizing setting for Classification Audit Trail AUT01


In transaction AUT01 the logging flag will be activated for the following fields: AUT02
o KLAH-SICHT Organizational Area (domain ABTEILUNG)
In transaction AUT02 the following links between transaction and tables will be defined:

Trans. Object
CL01 KLASSE
CL02 KLASSE

011 Customizing setting for Object Characteristic Audit Trail AUT01


In transaction AUT01 the logging flag will be activated for the following fields: AUT02
o CAWN-ATINN Internal characteristic
o CAWN-ATWRT Characteristic value
o CAWN-ATFLV Internal floating point from
o CAWN-ATFLB Internal floating point value to
o CAWN-ATCOD Code for value dependency
o CAWN-ATSTD Default value
o CAWN-ATIDN Object identification
o CAWN-SPRAS Language key
o CAWN-TXTNR Number of Related Text
o CAWN-LKENZ Deletion indicator
o CAWN-ATTLV Tolerance from
o CAWN-ATTLB Tolerance to
o CAWN-ATPRZ Indicator: Tolerance Shown as a Percentage

In transaction AUT02 the following links between transaction and tables will be defined:

Trans. Table
CT04 CAWN
012 Customizing setting for Process Order Audit Trail AUT01
In transaction AUT01 the logging flag will be activated for the following fields: AUT02
o AFFL-AENNR Change number
o AFKO-AENNR Change number
o AFKO-AENNR Change number
o AFKO-AENNR Change number

420750868.doc Page 69 of 81
Project Unity Functional Specification - Audit Trail

Cust. No Customizing Description with Values T. Code or Path


o AFVC-AENNR Change number
o RESB-AENNR Change number
o AUFK-AUFIDAT2 Technical completion date
o AFVC-AUFLOEKZ Deletion flag
o RESB-CHSPLIT Batch key
o AFKO-CO_AUFLD Date of BOM explosion/routing transfer
o AFPO-CO_AUFME Unit of measure for in-house production
o AFPO-CO_PSAMG Scrap quantity in item
o AFPO-CO_PSMNG Order item quantity
o AFKO-GAMNG Total order quantity
o AFKO-GASMG Total scrap quantity in the order
o AFVV-GMNGA Confirmed yield in order unit of measure
o AFPO-LAGME Base unit of measure
o RESB-MATNR Material number
o RESB-NOMNG Required quantity
o AFVC-SPLITTANZ Maximum number of splits
o AFVC-SPLITTERM Actual number of splits
o AFVC-SPLITTUNG Required splitting
o AFKO-STALT Alternative BOM
o RESB-STALT Alternative BOM
o AFKO-STLAN BOM usage
o AFVC-STLKN BOM item node number
o RESB-STLKN BOM item node number
o AFKO-STLTY BOM category
o AFVC-STLTY BOM category
o RESB-STLTY BOM category
o AFKO-STNUM Bill of material
o AFVC-STNUM Bill of material
o RESB-STNUM Bill of material
o RSADD-STNUM Bill of material
o RESB-STVKN Inherited node number of BOM item
o AFPO-VERID Production version
o RESB-XLOEK Item is deleted
o AFRU-AUSBU Clear open reservations
o AFVV-ASVRG Operation scrap
o AFVV-GMNGA Confirmed yield in order unit of measure
o AFVV-LMNGA Total Yield Confirmed
o AFKO-ARSPS Order Item Number
o AUFK-PHAS0 Order Created
o AUFK-PHAS1 Order Released
o AUFK-PHAS2 Order Completed

420750868.doc Page 70 of 81
Project Unity Functional Specification - Audit Trail

Cust. No Customizing Description with Values T. Code or Path


o AUFK-PHAS3 Order Closed
In transaction AUT02 the following links between transaction and tables will be defined:

Trans. Table
COR1 AFVC
CORO AFVC
COR8 AFVC
COR6 AFVC
COR7 AFVC
CORM AFVC

013 Customizing setting for Batch Master Basic Data Audit Trail AUT02
In transaction AUT02 the following links between transaction and tables will be defined:

Trans. Object
MSC2N CHARGE
MIGO CHARGE
MB11 CHARGE
MB1B CHARGE
MB1C CHARGE
MB31 CHARGE
MIGO_GO CHARGE
QA11 CHARGE
QA12 CHARGE

014 Customizing setting for Batch Master long text Audit Trail AUT04
In transaction AUT04 the following entry should be deactivated:

Text
object Text ID

420750868.doc Page 71 of 81
Project Unity Functional Specification - Audit Trail

Cust. No Customizing Description with Values T. Code or Path

CHARGE VERM

A job is schedule that deletes all the long texts flagged in table TTXID. Current job scheduled run program AUT_DEL.

015 Customizing setting for Batch Master Classification Audit Trail AUT02
In transaction AUT02 the following links between transaction and tables will be defined:

Trans. Object
MSC2N CLASSIFY
MIGO CLASSIFY
MB11 CLASSIFY
MB1B CLASSIFY
MB1C CLASSIFY
MB31 CLASSIFY
MIGO_GO CLASSIFY
QA11 CLASSIFY
QA12 CLASSIFY
016 Customizing setting for inspection lot Audit Trail AUT01
In transaction AUT01 the logging flag will be activated for the following fields: AUT02
o QALS-LMENGEIST Actual Lot Quantity
o QALS-PASTRTERM Inspection Start Date
o QALS-PAENDTERM End Date of the Inspection
o QALS-KTEXTLOS Short Text
o QALS-LTEXTKZBB Log Exists for Usage Decision
o QALS-WAPOS Maintenance Item

Activate table logging for the following table:


- QALS

In transaction AUT02 the following links between transaction and tables will be defined:

Trans. Table
QA02 QALS

420750868.doc Page 72 of 81
Project Unity Functional Specification - Audit Trail

Cust. No Customizing Description with Values T. Code or Path

QA11 QALS
QA12 QALS

017 Customizing setting for Inspection lot long text Audit Trail AUT04
In transaction AUT04 the following entry should be deactivated:

Text object Text ID


QPRUEFLOS QALS

A job is schedule that deletes all the long texts flagged in table TTXID. Current job scheduled run program AUT_DEL.

018 Customizing setting for Usage Decision Audit Trail AUT01


In transaction AUT01 the logging flag will be activated for the following fields: AUT02
o QALS-STAT34 Stock Postings Completed
o QALS-STAT35 Usage Decision Has Been Made
o QALS-LMENGE01 Quantity Posted to Unrestricted-Use Stock
o QALS-LMENGE02 Quantity Posted to Scrap
o QALS-LMENGE03 Quantity Posted to Sample
o QALS-LMENGE04 Quantity Posted to Blocked Stock
o QALS-LMENGE05 Quantity Posted to Reserves
o QALS-LMENGE06 Quantity Posted to Another Material
o QALS-MATNRNEU Material Number to Which the Quantity is Posted
o QALS-CHARGNEU Batch to Which Goods Are Transferred
o QALS-LMENGE07 Quantity Returned to Vendor
o QALS-LMENGE08 Other Quantity Posted from Inspection Lot Stock
o QALS-LMENGE09 Other Quantity (2) Posted from Inspection Lot Stock
o QALS-LMENGEZUB Quantity That Must Be Posted

Activate table logging for the following table:


- QALS

In transaction AUT02 the following links between transaction and tables will be defined:

Trans. Table

420750868.doc Page 73 of 81
Project Unity Functional Specification - Audit Trail

Cust. No Customizing Description with Values T. Code or Path

QA11 QAVE
QA12 QAVE

019 Customizing setting for Inspection lot long text Audit Trail AUT04
In transaction AUT04 the following entry should be deactivated:
Text object Text ID
QPRUEFLOS QAVE

A job is schedule that deletes all the long texts flagged in table TTXID. Current job scheduled run program AUT_DEL.

020 Customizing setting for Quality Inspection – Sample Drawing Procedure Audit Trail AUT01
In transaction AUT01 the logging flag will be activated for the following fields: AUT02
o QPRVK-GUELTIGAB Valid-from date
o QPRVK-SORTFELD Search Field
o QPRVK-QMASTAUTH Authorization Group QM Basic Data
o QPRVK-GEBANZ Physical-Sample Drawing Based on No. of Containers
o QPRVK-KZQUIT Confirmation Required for Physical-Sample Drawing
o QPRVK-ERSTELLER Name of User Who Created the Data Record
o QPRVK-AENDERER Name of User who Most Recently Changed the Data Record
o QPRVK-DATUMERST Date on Which the Data Record Was Created
o QPRVK-ZEITERST Time Data Record Was Created
o QPRVK-DATUMAEND Date on Which Data Record Was Changed
o QPRVK-ZEITAEND Time of Last Data Record Change
o QPRVK-KZNVPRZV Sample-drawing Procedure Cannot Be Used
o QPRVK-KZVPRZVPL Sample-Drawing Procedure Is Used in Task List
o QPRVP-LOSGEBEH Lot Container
o QPRVP-PROBNRPL Highest Partial Sample No. Valid for Instruction
o QPRVP-GEBINDE1 Physical-Sample Container for Drawing Primary Sample
o QPRVP-STPRPLAN1 Sampling Scheme for Primary Sample Stage of Sample Drawing
o QPRVP-PRSCHAERF1 Insp. Severity in Samp.-Draw. Proc. At Primary Sample Stage
o QPRVP-AQLWERT1 AQL Value in Primary Sample Stage
o QPRVP-PRANZ1 Fixed No. of Physical Samples for Primary Sample Stage
o QPRVP-FAKTORPR1 Factor for Determining the Sample Size of a Primary Sample
o QPRVP-FORMEL1 Formula Field for the Number of Samples
o QPRVP-GEBINDER Physical-Sample Container for Reserve Sample
o QPRVP-ANZRUECKL Number of Reserve Samples
o QPRVP-UMFRUECKL Size of Reserve Sample

420750868.doc Page 74 of 81
Project Unity Functional Specification - Audit Trail

Cust. No Customizing Description with Values T. Code or Path


o QPRVP-MERUECKL Unit of Measure for Reserve Sample
o QPRVP-GEBINDE2 Physical-Sample Container for Drawing Pooled Sample
o QPRVP-STPRPLAN2 Sampling Scheme for Pooled Sample Stage of Sample Drawing
o QPRVP-PRSCHAERF2 Insp. Severity of Samp.-Proc. At Pooled Sample Stage
o QPRVP-AQLWERT2 AQL Value in Pooled Sample Stage
o QPRVP-PRANZ2 Fixed No. of Physical Samples for Pooled Sample Stage
o QPRVP-FAKTORPR2 Factor for Determining the Sample Size of a Pooled Sample
o QPRVP-FORMEL2 Formula Field for the Number of Samples
o QPRVP-ERSTELLER Name of User Who Created the Data Record
o QPRVP-AENDERER Name of User who Most Recently Changed the Data Record
o QPRVP-DATUMERST Date on Which the Data Record Was Created
o QPRVP-ZEITERST Time Data Record Was Created
o QPRVP-DATUMAEND Date on Which Data Record Was Changed
o QPRVP-ZEITAEND Time of Last Data Record Change

In transaction AUT02 the following links between transaction and tables will be defined:

Trans. Table
QPV2 QPRVK
QPV2 QPRVP
021 Customizing setting for Selected sets for Master inspection characteristics Audit Trail AUT01
In transaction AUT01 the logging flag will be activated for the following fields: AUT02
o QPAM-KTX01 (short description)
o QPAC-QCODEGRP (code group)
o QPAC-QCODE (code)
o QPAC-BEWERTUNG (valuation)
o QPAC-FEHLKLASSE (defect class)

In transaction AUT02 the following links between transaction and tables will be defined:

Trans. Table
QS51 QPAM
QS51 QPAC
022 Customizing setting for Inspection Plan Audit Trail AUT01
In transaction AUT01 the logging flag will be activated for the following fields: AUT02

420750868.doc Page 75 of 81
Project Unity Functional Specification - Audit Trail

Cust. No Customizing Description with Values T. Code or Path


o PLKO-VERWE Task list usage
o PLKO-STATU Status
o PLKO-KTEXT Task list description
o PLKO-DELKZ Indicator: Delete completely in reorganization run
o PLPO-STEUS Control key
o PLPO-LTXA1 Short text
o PLMK-QMTB_WERKS Plant for Inspection Method
o PLMK-PMETHODE Inspection Method
o PLMK-VERWMERKM Master Inspection Characteristics
o PLMK-PROBENR Partial Sample No. for Inspection Charac. in Task List
o PLMK-KURZTEXT Short Text for Inspection Characteristic
o PLMK-STICHPRVER Sampling Procedure in Inspection Characteristic
o PLMK-AUSWMENGE1 Assigned Code Group or Selected Set
o PLMK-PRUEFQUALI Inspector Qualification
o PLKO-QDYNHEAD: Level at which Dynamic Modification Parameters are defined
o PLKO-QPRZIEHVER: Sample Drawing Procedure
o PLMKB-FAKPLANME: Factor to convert MatUnit of Measure toSampUnit of Measure
o PLMKB-FAKPROBME: Factortoconvert SampUnitof Measure toMatUnitofMeasure
o RMQSD-REFWERK: Plant
o RMQSD-QUANTITAET: Quantitative Characteristic
o RMQSD-QUALITAET: Qualitative Characteristic
o RMQSD-MSEHI: Unit ofMeasure
o RMQSD-ATNAM: Name of Class Characteristic

In transaction AUT02 the following links between transaction and tables will be defined:

Trans. Table
QP01 PLKO
QP01 PLMK
QP01 PLPO
QP02 PLKO
QP02 PLMK
QP02 PLPO

420750868.doc Page 76 of 81
Project Unity Functional Specification - Audit Trail

Cust. No Customizing Description with Values T. Code or Path

023 Customizing setting for Maintenance Plan Audit Trail AUT01


In transaction AUT01 the logging flag will be activated for the following fields: AUT02

 MPLA-WARPL: Maintenance Plan


 MPLA-WPTXT: Maintenance Plan Text
 MMPT-ZYKL1: Maintenance cycle
 MMPT-ZEIEH: Unit for the performance of maintenance tasks
 MMPT-PAK_TEXT: Text for maintenance package/cycle (time/performance)
 MMPT-OFFSET: Maintenance package offset
 MPLA-VSPOS: Shift Factor for Late Completion
 MPLA-TOPOS: Tolerance for Late Completion (%)
 MPLA-VSNEG: Shift Factor for Early Completion
 MPLA-TONEG: Tolerance for Early Completion (%)
 MPLA-SFAKT: Cycle modification factor
 MPLA-HORIZ: Call horizon for maintenance plan calls
 MPLA-ABRHO: Scheduling Period
 MPLA-HUNIT: Unit in scheduling interval
 MPLA-CALL_CONFIRM: Only Create New Call Object After Completing Predecessor
 MPLA-STRAT: Maintenance Plan Strategy
 MPLA-PLAN_SORT: Sort field for maintenance plans
 MPLA-BEGRU: Technical object authorization group
 MPLA-TPLNR: Functional Location
 MPLA-EQUNR: Equipment Number
 MPOS-PLNTY: Task List Type
 MPOS-PLNNR: Key for Task List Group
 MPOS-PLNAL: Group Counter
 MPLA-START_DATE: Start date for Scheduling
 MPLA-START_TIME: Start timeforscheduling

In transaction AUT02 the following links between transaction and tables will be defined:

Trans. Table
IP01 MPLA
IP02 MPLA

420750868.doc Page 77 of 81
Project Unity Functional Specification - Audit Trail

Cust. No Customizing Description with Values T. Code or Path

024 Customizing setting for General Task List Audit Trail AUT01
In transaction AUT01 the logging flag will be activated for the following fields: AUT02

 PLKO-PLNNR: Key for Task List Group


 PLKO-PLNAL: Group Counter
 PLKO-KTEXT: Task List Description
 PLKO-WERKS: Plant
 PLKO-STATU: Status
 PLPO-PLNNR: Key for Task List Group
 PLPO-VORNR: Operation/Activity Number
 PLPO-LTXA1: Operation short text
 PLPO-WERKS: Plant
 PLPO-ISTKN: BOM Item node Number
 PLPO-RUZUS: Key rounding and additional values

In transaction AUT02 the following links between transaction and tables will be defined:

Trans. Table
IA05 PLKO
IA06 PLKO
IA05 PLPO
IA06 PLPO

025 Customizing setting for Maintenance Order Audit Trail AUT01


In transaction AUT01 the logging flag will be activated for the following fields: AUT02

 AUFK- AUFNR : Order Number


 AUFK- WERKS : Plant
 AUFK- ERDAT : Created on
 AUFK- IDAT2 : Technical Completion date
 AUFK- IDAT3 : Close Date
 AUFK- AUART : Order Type
 AFIH -EQUNR : Equipment Number
 AFIH -WARPL : Maintenance Plan
 AFIH -ABNUM : Maintenance Plan Call Number

420750868.doc Page 78 of 81
Project Unity Functional Specification - Audit Trail

Cust. No Customizing Description with Values T. Code or Path


 AFIH -WAPOS : Maintenance item
 AFIH-ADDAT : PM Order: Reference Date

In transaction AUT02 the following links between transaction and tables will be defined:

Trans. Table
IW31 AUFK
IW31 AFIH
IW32 AUFK
IW32 AFIH
IW33 AUFK
IW33 AFIH
026 Customizing setting for Schedule Maintenance Plan Audit Trail AUT01
In transaction AUT01 the logging flag will be activated for the following fields: AUT02

 AUFK- AUFNR : Order Number


 AUFK- WERKS : Plant
 AUFK- ERDAT : Created on
 AUFK- IDAT2 : Technical Completion date
 AUFK- IDAT3 : Close Date
 AUFK- AUART : Order Type
 AFIH -EQUNR : Equipment Number
 AFIH -WARPL : Maintenance Plan
 AFIH -ABNUM : Maintenance Plan Call Number
 AFIH -WAPOS : Maintenance item
 AFIH-ADDAT : PM Order: Reference Date

In transaction AUT02 the following links between transaction and tables will be defined:

Trans. Table
IP30 AUFK
IP30 AFIH

420750868.doc Page 79 of 81
Project Unity Functional Specification - Audit Trail

Cust. No Customizing Description with Values T. Code or Path

027 Customizing setting for Equipment Audit Trail AUT01


In transaction AUT01 the logging flag will be activated for the following fields: AUT02

o EQUI-EQART Type of Technical Object


o EQKT-EQKTX Description of technical object
o AUSP-ATFLV Internal floating point from
o AUSP-ATAWE Unit of Measurement
o AUSP-ATAW1 Unit of Measurement
o KSSK-STATU Classification status
o JSTO-STSMA Status profile
o JEST-STAT Object status
o ITOBATTR-SERUNI Serial Number

In transaction AUT02 the following links between transaction and tables will be defined:

Trans. Table
IE01 EQUI
IE01 EQKT
IE01 AUSP
IE01 KSSK
IE01 JSTO
IE01 JEST
IE02 EQUI
IE02 EQKT
IE02 AUSP
IE02 KSSK
IE02 JSTO
IE02 JEST

420750868.doc Page 80 of 81
Project Unity Functional Specification - Audit Trail

7. OVERVIEW OF ADDITIONAL DEVELOPMENTS

7.1 REPORTS, FORMS

Dev. No FS-R Document Name Description FS Line No.

7.2 INTERFACES
Dev. No FS-I Document Name Description FS Line No.

7.3 CONVERSIONS
Dev. No FS-C Document Name Description FS Line No.

7.4 ENHANCEMENTS
Dev. No FS-R Document Name Description FS Line No.

420750868.doc Page 81 of 81

You might also like