PM Plant Maintenanc

303ODQW0DLQWHQDQFH
0
3
&
5
$
$
&

3
/
(
+
Release 4.0B
®
303ODQW0DLQWHQDQFH 6$3$*
&RS\ULJKW
© Copyright 1998 SAP AG. All rights reserved.
No part of this brochure may be reproduced or transmitted in any form or for any purpose without
the express permission of SAP AG. The information contained herein may be changed without
prior notice.
SAP AG further does not warrant the accuracy or completeness of the information, text, graphics,
links, or other items contained within these materials. SAP AG shall not be liable for any special,
indirect, incidental, or consequential damages, including without limitation, lost revenues or lost
profits, which may result from the use of these materials. The information in this documentation is
subject to change without notice and does not represent a commitment on the part of SAP AG for
the future.
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Microsoft®, WINDOWS®, NT®, EXCEL® and SQL-Server® are registered trademarks of
Microsoft Corporation.
IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®,
AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.
OSF/Motif® is a registered trademark of Open Software Foundation.
ORACLE® is a registered trademark of ORACLE Corporation, California, USA.
INFORMIX®-OnLine IRU6$3 is a registered trademark of Informix Software Incorporated.
UNIX® and X/Open® are registered trademarks of SCO Santa Cruz Operation.
ADABAS® is a registered trademark of Software AG.
SAP®, R/2®, R/3®, RIVA®, ABAP/4®, SAP ArchiveLink®, SAPaccess®, SAPmail®,
SAPoffice®, SAP-EDI®, R/3 Retail®, SAP EarlyWatch®, SAP Business Workflow®, ALE/WEB,
Team SAP, BAPI, Management Cockpit are registered or unregistered trademarks of SAP
AG.
,FRQV
,FRQ 0HDQLQJ
Caution
Example
Note
-XQH
6$3$* 303ODQW0DLQWHQDQFH
&RQWHQWV
303ODQW0DLQWHQDQFH
7KH30B(48,$UFKLYLQJ2EMHFW'HILQLWLRQ 30(40(4
$SSOLFDWLRQ6SHFLILF)HDWXUHV 30(40(4
&KHFNV 30(40(4
'HSHQGHQFLHV 30(40(4
7HFKQLFDO'DWD 30(40(4
5HVLGHQFH7LPH 30(40(4
$SSOLFDWLRQ&XVWRPL]LQJ 30(40(4
$XWKRUL]DWLRQV 30(40(4
&DOOLQJ8S$UFKLYLQJIRU(TXLSPHQW 30(40(4
(YDOXDWLQJ(TXLSPHQW 30(40(4
'LVSOD\LQJ:KHUH8VHG/LVWVIRU(TXLSPHQW 30(40(4
3UHSDUDWLRQ/RJIRU(TXLSPHQW 30(40(4
$UFKLYLQJ/RJIRU(TXLSPHQW 30(40(4
'HOHWLRQ/RJIRU(TXLSPHQW 30(40(4
7KH60B40(/$UFKLYLQJ2EMHFW'HILQLWLRQ 3060$6&
$SSOLFDWLRQ6SHFLILF)HDWXUHV 3060$6&
3UHVHWWLQJV 3060$6&
&KHFNV 3060$6&
'HSHQGHQFLHV 3060$6&
7HFKQLFDO'DWD 3060$6&
5HVLGHQFH7LPH 3060$6&
$SSOLFDWLRQ&XVWRPL]LQJ 3060$6&
$XWKRUL]DWLRQV 3060$6&
&DOOLQJ8S$UFKLYLQJIRU6HUYLFH1RWLILFDWLRQV 3060$6&
(YDOXDWLQJ6HUYLFH1RWLILFDWLRQV 3060$6&
3UHSDUDWLRQ/RJIRU6HUYLFH1RWLILFDWLRQV 3060$6&
$UFKLYLQJ/RJIRU6HUYLFH1RWLILFDWLRQV 3060$6&
'HOHWLRQ/RJIRU6HUYLFH1RWLILFDWLRQV 3060$6&
7KH30B25'(5$UFKLYLQJ2EMHFW'HILQLWLRQ 30:2&023060$6&
$SSOLFDWLRQ6SHFLILF)HDWXUHV 30:2&023060$6&
'HSHQGHQFLHV 30:2&023060$6&
7HFKQLFDO'DWD 30:2&023060$6&
$SSOLFDWLRQ&XVWRPL]LQJ 30:2&023060$6&
6HWWLQJ'HOHWLRQ)ODJVDQG,QGLFDWRUVIRU2UGHUVLQWKH%DFNJURXQG 30:2&0230
60$6&
6HWWLQJ'HOHWLRQ)ODJV2QOLQHIRU2UGHUV 30:2&023060$6&
&KHFNV 30:2&023060$6&
$XWKRUL]DWLRQV 30:2&023060$6&
7KH30B40(/$UFKLYLQJ2EMHFW'HILQLWLRQ 30:2&01
-XQH
$SSOLFDWLRQ6SHFLILF)HDWXUHV 30:2&01

3UHVHWWLQJV 30:2&01
&KHFNV 30:2&01
'HSHQGHQFLHV 30:2&01
7HFKQLFDO'DWD 30:2&01
5HVLGHQFH7LPH 30:2&01
$SSOLFDWLRQ&XVWRPL]LQJ 30:2&01
$XWKRUL]DWLRQV 30:2&01
&DOOLQJ8S$UFKLYLQJIRU0DLQWHQDQFH1RWLILFDWLRQV 30:2&01
(YDOXDWLQJ0DLQWHQDQFH1RWLILFDWLRQV 30:2&01
3UHSDUDWLRQ/RJIRU0DLQWHQDQFH1RWLILFDWLRQV 30:2&01
$UFKLYLQJ/RJIRU0DLQWHQDQFH1RWLILFDWLRQV 30:2&01
'HOHWLRQ/RJIRU0DLQWHQDQFH1RWLILFDWLRQV 30:2&01
7KH$UFKLYLQJ2EMHFW30B3/$1 303507/
$SSOLFDWLRQ6SHFLILF)HDWXUHV 303507/
7HFKQLFDO'DWD 303507/
&KHFNV 303507/
0DLQWHQDQFH7DVN/LVWVZLWK6HYHUDO&KDQJH6WDWXVHV 303507/
0DLQWHQDQFH7DVN/LVWVIURP3UHYLRXV55HOHDVHV 303507/
'HSHQGHQFLHV
$XWKRUL]DWLRQV 303507/
&UHDWLQJ$UFKLYH)LOHVIRU7DVN/LVWV 303507/
'HOHWLQJ7DVN/LVWV 303507/
'HOHWLQJ307DVN/LVWV:LWKRXW$UFKLYLQJ 303507/
&KDQJH6WDWXVHVRI0DLQWHQDQFH7DVN/LVWV 303507/
7KH30B,)/27$UFKLYLQJ2EMHFW'HILQLWLRQ 30(40)/
$SSOLFDWLRQ6SHFLILF)HDWXUHV 30(40)/
&KHFNV 30(40)/
'HSHQGHQFLHV 30(40)/
7HFKQLFDO'DWD 30(40)/
5HVLGHQFH7LPH 30(40)/
$SSOLFDWLRQ&XVWRPL]LQJ 30(40)/
$XWKRUL]DWLRQV 30(40)/
&DOOLQJ8S$UFKLYLQJIRU)XQFWLRQDO/RFDWLRQV 30(40)/
(YDOXDWLQJ)XQFWLRQDO/RFDWLRQV 30(40)/
'LVSOD\LQJ:KHUH8VHG/LVWVIRU)XQFWLRQDO/RFDWLRQV 30(40)/
,PSOHPHQWLQJ0DWFKFRGH6HWXSIRU)XQFWLRQDO/RFDWLRQV 30(40)/
3UHSDUDWLRQ/RJIRU)XQFWLRQDO/RFDWLRQV 30(40)/
$UFKLYLQJ/RJIRU)XQFWLRQDO/RFDWLRQV 30(40)/
'HOHWLRQ/RJIRU)XQFWLRQDO/RFDWLRQV 30(40)/
$UFKLYLQJRI0HDVXUHPHQW'RFXPHQWV 30(406)03&
$SSOLFDWLRQ6SHFLILF)HDWXUHV 30(406)03&
$SSOLFDWLRQ&XVWRPL]LQJ 30(406)03&
9DULDQW6HWWLQJVIRU3UHSDUDWLRQ 30(406)03&
9DULDQW6HWWLQJVIRU$UFKLYLQJ 30(406)03&
-XQH
$XWKRUL]DWLRQV 30(406)03&

/RJRI3UHSDUDWLRQIRU0HDVXUHPHQW'RFXPHQWV 30(406)03&
/RJRI$UFKLYLQJIRU0HDVXUHPHQW'RFXPHQWV 30(406)03&
'LVSOD\LQJ'HOHWLRQ)ODJV 30(406)03&
'LVSOD\LQJ$UFKLYHG0HDVXUHPHQW'RFXPHQWV 30(406)03&
-XQH
303ODQW0DLQWHQDQFH
7KHIROORZLQJWDEOHJLYHV\RXDQRYHUYLHZRIWKHDUFKLYLQJREMHFWVWKDWDUH
DYDLODEOHZLWKLQ3ODQW0DLQWHQDQFH
2EMHFWVLQ3ODQW0DLQWHQDQFH $UFKLYLQJ2EMHFW
Equipments PM_EQUI [Seite 7]
Functional Locations PM_IFLOT [Seite 77]
Measurement Documents PM_IMRG [Seite 93]
Maintenance Notifications PM_QMEL [Seite 49]
Service Notifications SM_QMEL [Seite 22]
Maintenance Orders PM_ORDER [Seite 36]
Maintenance Task Lists PM_PLAN [Seite 63]
6HHDOVR
*HQHUDO$UFKLYLQJ,QIRUPDWLRQ>([WHUQ@
&RPSRQHQW2YHUYLHZIRU$UFKLYLQJ>([WHUQ@
-XQH
7KH30B(48,$UFKLYLQJ2EMHFW'HILQLWLRQ 30(40(4
7KH30B(48,$UFKLYLQJ2EMHFW'HILQLWLRQ 30(40
(4
'HILQLWRQ
Archiving object [Extern] with which you can archive equipment.
6WUXFWXUH
The archiving object for equipment 30B(48, consists of the following tables:
7DEOH 6KRUWWH[W
EQUI Equipment master data
EQKT Multilingual equipment short texts, long texts, and internal remarks
EQKZ Equipment time segments
ILOA Location and account assignment data for the maintenance object
IHSG Plant Maintenance authorization table with long texts
JEST Equipment status
CLDAT Characteristic value assignment for the classification
IHPA Partners
CDHDR Change documents
-XQH
8VH
You can archive equipment master data that you no longer need in the online system using the
archive program. When you archive data, the data is written to archive files and then deleted
from the database.
You archive and delete equipment master data using the archiving object [Extern] 30B(48,.
You can archive equipment in PM while the RQOLQHRSHUDWLRQ is in process.
)HDWXUHV
3UHSDUDWLRQ
The preparation program prepares the data in the database for archiving. The GHOHWLRQIODJV,
with which you flagged the equipment you want to archive are also assigned the system status
IODJJHGIRUGHOHWLRQin the preparation program. However, note that processing can only take
place if the system determines equipment is QRW being used elsewhere in the system.
The preparation produces a log [Seite 19].
$UFKLYLQJ
The DUFKLYLQJSURJUDP writes the database tables of the equipment listed under the object
definition [Seite 7] to the archive.
When 6WDUWDXWRPDWLFDOO\ is set for the delete program in Archiving Customizing

[Extern], and a productive mode is selected for the archiving program, the system
starts the delete program in connection with its productive mode. This means that
the system deletes the archived data from the database.
The archiving program produces a log [Seite 20].
'HOHWLQJ
The GHOHWHSURJUDP deletes all database records for the pieces of equipment which were
successfully archived.
If the delete program is not called automatically after the first archive file is created successfully,
you must wait until all archive files are created before you can delete data from the database.
You can process an entire archiving session with all the archive files created or you can select
individual archive files for processing.
The delete program produces a log [Seite 21].
-XQH
&KHFNV 30(40(4
&KHFNV 30(40(4
8VH
Before archiving, the system must determine whether the equipment is in use elsewhere in the
system (for example, in a task list). For this purpose, XVDJHFKHFNVare made for the individual
pieces of equipment.
3UHUHTXLVLWHV
The equipment master record must have the status'HOHWLRQIODJVHW before it can be archived.
For more information on setting deletion flags, see Setting the deletion flag for equipment
[Extern], (see 3ODQW0DLQWHQDQFH6WUXFWXULQJ7HFKQLFDO6\VWHPV .
)HDWXUHV
The section 8VDJH&KHFNVIRU(TXLSPHQW describes the chronological sequence the system uses
to check for usage. As soon as the system determines that the equipment is being used, you
cannot set status '/7('HOHWLRQ,QGLFDWRUWREHDUFKLYHG) for that piece of equipment.
The system checks the following information for LQGLYLGXDOSLHFHVRIHTXLSPHQW:
• Usage as equipment number
• Usage as superior equipment
• Usage as equipment affected
You can display a where-used list for pieces of equipment which are still used in
the system by using the analysis report RIARCEQ1.
For the exact procedure, see Displaying Where-Used Lists for Equipment (PM-
EQM-EQ) [Seite 18].
The following tables describe the chronological order in which the system checks for equipment
usage. As soon as the system determines that the equipment is being used, you cannot set
status '/7 ('HOHWLRQLQGLFDWRUWREHDUFKLYHG) for that piece of equipment.
8VDJHDV(TXLSPHQW1XPEHU
&KHFN&ULWHULD $SLHFHRIHTXLSPHQWFDQQRWEHDUFKLYHG
LI
Equipment master data It is configured.
Equipment time segment, An address is assigned to it.
location and account assignment for
the maintenance object
Task list A task list is assigned to it.
BOM It is included in a BOM.
-XQH
&KHFNV 30(40(4
Production resources/tools (PRT data) There is a link between equipment and PRT
data.
Order header It is included in an order header.
Maintenance notification It is included in a maintenance notification.
Maintenance plan item It is included in a maintenance plan item.
Object list It is included in an object list.
Object link It is included in an object network.
Measuring point A measuring point is assigned to it.
Document link A document is assigned to it.
Historical order master data It is included in a historical order.
WBS element (work breakdown structure It is included in the master data of a WBS
element) master data element.
Sampling table It is integrated in a sampling table.
8VDJHDV6XSHULRU(TXLSPHQW
&KHFN&ULWHULD $SLHFHRIHTXLSPHQWFDQQRWEHDUFKLYHGLI
Time segment It is a VXSHULRUSLHFHRIHTXLSPHQW in an equipment hierarchy containing
superior and sub-pieces of equipment.
8VDJHDV(TXLSPHQW$IIHFWHG
&KHFNFULWHULD $SLHFHRIHTXLSPHQWFDQQRWEHDUFKLYHGLI
Maintenance notification It is included in a maintenance notification as DIIHFWHG
equipment.
(For example, a notification is entered due to a defective PC,
although the CPU is affected.)
-XQH
When archiving data you must consider data dependencies, such as those between equipment
and maintenance notifications. Generally, you cannot archive data until dependent objects have
been archived.
The network graphic shows dependencies between objects. For more information, see The
Network Graphic [Extern].
-XQH
There is currently no information available on program runtime and hard disk storage
requirements for archiving in Plant Maintenance.
-XQH
Some data must reside in the system for a specified length of time even if it is no longer being
used (for example, for legal reasons). This is called the residence time. The data cannot be
archived until it has been in the system for at least this length of time.
Since the residence time deals with a typical characteristic of Plant Maintenance transaction
data, 30PDVWHUGDWDGRHVQRWUHTXLUHDUHVLGHQFHWLPH.
Once the system establishes that a piece of equipment meets the requirements for archiving, it
can archive the data LPPHGLDWHO\.
6HHDOVR
Residence and Retention Periods [Extern]
-XQH
8VH
In Customizing for Archiving you can adjust the settings for archiving sessions specifically for
individual archiving objects.
Plant Maintenance archiving FDQQRWEHSHUIRUPHGIRUDOOFOLHQWV.
You can run the archiving program either in WHVWPRGH orSURGXFWLYHPRGH. No data is archived
or deleted in test mode.
In Customizing for Archiving the default setting for the delete program is 6WDUW
DXWRPDWLFDOO\. This means that the system DXWRPDWLFDOO\ starts the delete
program after data is written successfully to archive files.
6HHDOVR
Customizing: Overview [Extern]
-XQH
To archive equipment master data in Plant Maintenance you only require general archiving
authorization.
6HHDOVR
User Authorization Checks [Extern]
-XQH
To call up Archiving generally, proceed as follows:
1. Choose 7RROV→$GPLQLVWUDWLRQ→$GPLQLVWUDWLRQ→$UFKLYLQJ
You reach the initial $UFKLYH0DQDJHPHQW screen.
2. Enter the name of the archiving object (30B(48, for equipment master data) and
choose &RQWLQXH.
The system displays the possible actions for the archiving object you entered.
3. You can now select and execute the required actions (for example “3UHSDUDWLRQ”,
“$UFKLYH”).
-XQH
8VH
You can display and evaluate the data from archived equipment.
3URFHGXUH
1. Choose (YDOXDWHYou reach the screen where you can plan a background job for the
program.
2. Use a report variant. The standard SAP variants for Plant Maintenance are:
6$3 7(67(test run variant): display archive contents.
You can only use a variant in RQHjob. As long as there is one job with this
variant, even if it has run successfully, this variant cannot be used in any other
job.
3. Choose 6WDUWGDWH. You reach a screen where you can maintain start dates.
4. Enter the start date and save your entries. You return to the previous screen.
5. Choose 6SRROSDUDPHWHUV. You reach a screen where you can maintain print
parameters for the log created.
6. Enter the required values and save your entries. You return to the initial screen.
7. You have now entered all data required for the background job. Choose &UHDWHMRE.
6HHDOVR
Maintaining the Start Date and Spool Parameters [Extern]
-XQH
'LVSOD\LQJ:KHUH8VHG/LVWVIRU(TXLSPHQW 30(40(4
'LVSOD\LQJ:KHUH8VHG/LVWVIRU(TXLSPHQW 30(40
(4
8VH
Use the analysis report 5,$5&(4 to display a ZKHUHXVHGOLVWRIHTXLSPHQW that is still being
used in the system. You cannot archive pieces of equipment that are still being used in the
system.
3URFHGXUH
1. Choose6\VWHP→6HUYLFHV→5HSRUWLQJ
You reach the $%$3([HFXWH3URJUDPscreen.
2. Enter the report name in the 3URJUDP field. For equipment master data, the report
name is 5,$5&(4.
3. Choose one of the following options:
3URJUDP→([HFXWH
3URJUDP→([HFXWHZLWKYDULDQW
The system displays a list that shows where each selected piece of equipment is
used.
If you GRQRW mark the field 6WDWXVFKHFN, the system displays equipment usage
regardless of whether the equipment has a deletion flag or not.
If you GR mark the field 6WDWXVFKHFN, the system checks whether the equipment
has a deletion flag. The existing usages are displayed only if it does.
If the selection is performed ZLWKRXWGHOLPLWDWLRQ of (TXLSPHQWQR, (TXLSPHQW
FDWHJRU\, or (TXLSPHQWW\SH, the system selects only equipment for which the
status '/7('HOHWLRQIODJ) is set.
-XQH
'HILQLWLRQ
When you run the preparation program for equipment as a background job, the system creates a
log that describes how many pieces of equipment were flagged for deletion by HTXLSPHQWW\SH
DQGFDWHJRU\.
6WUXFWXUH
The log contains the following detailed information:
• Selection criteria and parameter settings used
• Each piece of processed equipment

– With the confirmation “System status '/7('HOHWLRQLQGLFDWRU) set”
– Exception messages
For example, if you executed the program in “test mode”, the where-used lists for
each piece of equipment will be listed if necessary
• Statistics regarding processed equipment master records

6HHDOVR
The Archive Management Menus [Extern]
-XQH
'HILQLWLRQ
When you run the archiving program as a background job, the system produces a log.
6WUXFWXUH
The log contains the following information:
• Each processed equipment with exception messages if necessary

For example, if you executed the program in test mode, the where-used lists for each
equipment will be listed.
• Statistics regarding archived objects
• Number of created archive files
• All administrative data
• Associated tables
• Number of processed table entries
If you make the settings for the archiving object “PM-EQUI” in Customizing
according to the SAP standard, the delete program will be run in a later job step
DXWRPDWLFDOO\. This also produces a log [Seite 21].
6HHDOVR
-XQH
'HILQLWLRQ
If you make the settings for the archiving object 30(48, in Customizing according to the SAP
standard, the delete program will be run in a later job step DXWRPDWLFDOO\.This also produces a
log.
6WUXFWXUH
The delete program contains the following data:
• Statistics regarding the processed objects for each archiving session.

6HHDOVR
-XQH
7KH60B40(/$UFKLYLQJ2EMHFW'HILQLWLRQ 3060$6&
7KH60B40(/$UFKLYLQJ2EMHFW'HILQLWLRQ 3060$
6&
'HILQLWLRQ
Archiving object [Extern] with which you can archive service notifications.
6WUXFWXUH
The archiving object for service notifications 60B40(/ includes the following tables:
7DEOHQDPH &RQWHQWV
QMEL Notification header data
QMFE Items
QMMA Activities
QMSM Tasks
QMUR Causes
QMIH Plant Maintenance data
ILOA Location data
IHPA Partners
PMLP Print log
MCIPMIS PMIS update, Before Image table, object data
CDHDR, CDPOS Change documents
KSSK Classification
JEST, JESTO Status
SWW_CONTOB Workflow, Workitem
THEAD Long text
Workflow can only be archived, and not deleted. You can archive Workflow using
the archiving object WORKITEM.
For more information on this topic, see the SAP document %&$SSOLFDWLRQ'DWD
$UFKLYLQJ%&%DVLV.
-XQH
8VH
You archive notifications in Service Management using the archive program. When you archive
data, it is written to archive files and then deleted from the database if the operation was
successful.
Currently, you can only archive service notifications in Service Management. You can archive
and delete service notifications with the 60B40(/archiving object [Extern].
You can archive Service Management notifications while the RQOLQHRSHUDWLRQ is in process.
)HDWXUHV
3UHSDUDWLRQ
The preparation program prepares the data in the database for archiving. The objects that you
IODJJHGIRUGHOHWLRQ are also assigned the system status 0$5& (IODJJHGIRUDUFKLYLQJ).
$UFKLYLQJ
The archiving program writes the database tables of the service notifications listed under the
object definition [Seite 22] to the archive.
'HOHWLQJ
The delete program deletes all database records for the service notifications which were
If the delete program is not started automatically after the first archive file is created successfully,
you must wait for all archive files to be created (see &XVWRPL]LQJIRU$UFKLYLQJ). You can process
an entire archiving session with all the archive files created or you can select individual archive
files for processing.
-XQH
3UHVHWWLQJV 3060$6&
3UHVHWWLQJV 3060$6&
Service notifications must have the status )ODJJHGIRUGHOHWLRQ before they can be archived.
You can set the deletion flagin two ways:
• The service notifications can be flagged for deletion [Extern] manually.
• You can flag completed service notifications for deletion using the report RIARCSM3:
To flag service notifications for deletion, choose /RJLVWLFV → 6HUYLFHPDQDJHPHQW
→ 6HUYLFHSURFHVVLQJ→1RWLILFDWLRQV→6HWGHOHWLRQIODJ
– If you run the report in 7HVWPRGH, you can determine which service notifications
are completed, and for which notifications the completion date is n days in the
past (check for <=). For example, where n=200, the system checks all completed
service notifications whose completion date is more than 200 days in the past.
– If you run the report in $FWLYHPRGH, the system sets the status '/7 'HOHWLRQ
)ODJ for the service notifications found.
6HHDOVR
Application Customizing (PM-SMA-SC) [Seite 29]
-XQH
&KHFNV 3060$6&
&KHFNV 3060$6&
8VH
Before archiving, the system must determine whether the service notification is in use in a
service order. For this purpose, XVDJHFKHFNVare performed for the individual service
notifications.
When the system determines a service notification is being used, the system
status '/7 (Deletion indicator) can be set but the system only archives the
service notification if the maintenance order, the historical order, and the
customer order have been deleted.
You can display a verification list of service notifications that are still in use in the
system and that are flagged for deletion using the preparation program [Seite 33].
To do this, carry out preparation in 7HVWPRGH.
-XQH
When archiving, you must consider data dependencies, for example, between service
notifications and service orders. Generally, you cannot archive an object until dependent objects
have been archived.
You can set the status '/7 (Deletion indicator) when the system determines that
a service notification is being used, but the system only archives the service
notification if the maintenance order, the historical order, and the sales order have
been deleted.
The network graphic displays dependencies between archiving objects. For more information,
see The Network Graphic [Extern].
-XQH
requirements for archiving in Service Management.
-XQH
You control residence time using a report. You determine how long a completed service
notification remains in the system before being flagged for deletion using the report RIARCSM3
[Seite 24].
If the system determines that a service notification meets the requirements for archiving, you can
archive the data LPPHGLDWHO\.
6HHDOVR
-XQH
8VH
In Customizing for Archiving you can adjust settings for archiving sessions specifically for
You FDQQRW archive Service Management data IRUDOOFOLHQWV.
You can run the archiving program either in 7HVWPRGH or in 3URGXFWLYHPRGH. No data is
archived or deleted in test mode.
6HHDOVR
-XQH
The system checks by means of the authorization object I_VORG_MEL whether the following
authorizations are available for:
• Setting the status '/7 ('HOHWLRQIODJ)
• Setting the status0$5& ()ODJJHGIRUDUFKLYLQJ)

If the authorizations are not available, the system terminates processing.
6HHDOVR
-XQH
&DOOLQJ8S$UFKLYLQJIRU6HUYLFH1RWLILFDWLRQV 3060$6&
&DOOLQJ8S$UFKLYLQJIRU6HUYLFH1RWLILFDWLRQV 3060$
6&
2. Enter the name of the archiving object you want to use (60B40(/ for notifications in
Service Management).
Choose &RQWLQXH. The system displays the available actions for this archiving object.
3. You can now select the required actions (for example “Preparation”, “Archive”) and
proceed as described in the relevant procedures.
-XQH
8VH
You can display archived service notifications.
3URFHGXUH
1. Choose (YDOXDWH. You reach a screen in which you can plan a background job for the
program.
2. Use a report variant. The standard variants for Service Management are:
job.
5. Choose 6SRROSDUDPHWHUV. You reach a screen where you can specify the
background print parameters for the processing log.
6HHDOVR
-XQH
'HILQLWLRQ
When you run the preparation program for archiving as a background job, the system creates a
list in log form.
6WUXFWXUH
• Each processed service notification

− With the confirmation “System status MARC (flagged for archiving) set”
− Exception messages
For example, if you ran the program in test mode, the log lists where each service
notification is being used in the system.
• Statistics regarding processed service notifications

6HHDOVR
-XQH
'HILQLWLRQ
When you run the archiving program as a background job, the system creates a log in list form.
6WUXFWXUH
The log contains the following data:
• Each processed service notification with exception messages if necessary

For example, if you ran the program in test mode, the log lists where each service
notification is being used in the system.
• Respective number of processed table entries
If you make the appropriate settings for the archiving object SM_QMEL in
Customizing, the delete program will start DXWRPDWLFDOO\. This also produces a
log [Seite 35].
6HHDOVR
-XQH
'HILQLWLRQ
If you use the default settings for the archiving object SM_QMEL in Customizing for Archiving,
the delete program will be started DXWRPDWLFDOO\ when the first archive file is created. This
produces a log.
6WUXFWXUH
The log contains statistics on the objects processed for each archiving session.
6HHDOVR
-XQH
7KH30B25'(5$UFKLYLQJ2EMHFW'HILQLWLRQ 30:2&
023060$6&
'HILQLWLRQ
Archiving object for archiving maintenance orders (PM orders) and service orders.
6WUXFWXUH
The archiving object [Extern] 30B25'(5 for archiving maintenance orders contains the
following order data:
7DEOH 6KRUWWH[W
AFIH Maintenance order header
IHPA Partners
IHSG, IHGNS Permits
ILOA Location and account assignment for the PM object
OBJK Object list
PMCO Cost structure and overview of the PM order
MCIPMIS Order data for PMIS
PMPL Print data for order
PMSDO PM Organizational data for SD documents
By using archiving classes (3B2UGHUDQG7H[W), the system also archives the following data:
• Order header overall (table AUFK, AFKO)
• Costs report
• Settlement rule
• Operations
• Material components
• Production resources/tools
• Confirmations
• Status of order header and operation
• Long text for order header and operation
• Purchase requisition for operation and components
-XQH
• Confirmation for operation and components
• Goods movement
Since Release 3.0F, it has been possible to generate an historical order

simultaneously during an archiving session from a maintenance order.
If you use the indicator &UHDWHKLVWRURUGHUVon the initial screen for an archiving
session, the delete program simultaneously deletes the maintenance order and
creates the maintenance order in condensed form in the R/3 online database.
The number of the maintenance order is retained.
6HHDOVR
The Archiving Object: Overview [Extern]
-XQH
$SSOLFDWLRQ6SHFLILF)HDWXUHV 30:2&023060$
6&
8VH
You can archive Plant Maintenance orders and service orders that are no longer needed in the
system using the archive program. Archiving writes data to archive files and then deletes the data
from the database if the operation was successful.
You archive Plant Maintenance orders using the 30B25'(5 archiving object [Seite 36].
)HDWXUHV
3UHSDUDWLRQ
The preparation program prepares the data in the database for archiving. The deletion flags, with
which you flagged the maintenance or service orders you want to archive are also assigned the
system status Deletion indicator in the preparation program. However, note that processing can
only take place if the check criteria described under Checks (PM-WOC-MO, PM-SMA-SC) [Seite
46] have been fulfilled.
$UFKLYLQJDQG'HOHWLQJ
The archiving program writes the database tables of the maintenance and service orders listed
under the object definition [Seite 36] to the archive.
Normally, the system creates archive files and then deletes them automatically as the SAP
standard setting 6WDUW$XWRPDWLFDOO\is set. The delete program deletes all database records of
the orders which have been successfully archived. You can however, perform these steps
individually.
For more information, see Deleting [Extern].
+LVWRULFDO2UGHUV
Since Release 3.0F, it has been possible to generate an historical order simultaneously during an
archiving session from a maintenance order.
If you use the indicator &UHDWHKLVWRURUGHUVon the initial screen for an archiving session, the
delete program simultaneously deletes the maintenance order and creates the maintenance
order in condensed form in the R/3 online database. The number of the maintenance order is
retained.
6HOHFWLRQ&ULWHULD
You can select orders for archiving according to the following criteria:
• Order number
• Order type
• Maintenance planning plant

Orders are only archived if the following criteria are met:
• Deletion indicator is set
-XQH
• Residence time 2 has elapsed
-XQH
There are no dependencies to other archiving objects.
6HHDOVR
The Network Graphic [Extern]
-XQH
7HFKQLFDO'DWD 30:2&023060$6&
7HFKQLFDO'DWD 30:2&023060$6&
Since the size of maintenance orders can vary greatly, it is difficult to give a general estimate for
runtime. The best way to determine how long it will take to archive data is to do a small test run.
That way you can estimate runtime from the number of orders.
-XQH
Before you can archive maintenance orders (PM orders) or service orders, the system performs
different checks [Seite 46].
One of the checks concerns the residence times. Residence times are part of the order type. You
can set them in Customizing for maintenance orders by using 30RUGHUPDQDJHPHQW → 30
RUGHUVDQGVHUYLFHRUGHUV→0DLQWHQDQFHRUGHUW\SHVIXQFWLRQVDQGVHWWLQJV →&RQILJXUHRUGHU
W\SHV.
-XQH
6HWWLQJ'HOHWLRQ)ODJVDQG,QGLFDWRUVIRU2UGHUVLQWKH%DFNJURXQG 30:2&023060$6&
6HWWLQJ'HOHWLRQ)ODJVDQG,QGLFDWRUVIRU2UGHUVLQWKH
%DFNJURXQG 30:2&023060$6&
8VH
You can set deletion flags and indicators not only online [Seite 45], but also for areas that meet
the same selection criteria.
For each selection area, you can:
• Set deletion flag only
• Set deletion indicator only
• Set deletion flag and deletion indicator simultaneously

However, the system can only set the status when the delete criteria described in Checks (PM-
WOC-MO, PM-SMA-SC) [Seite 46] are met.
3URFHGXUH
2. Enter the name of the object you want to use (30B25'(5 for maintenance orders).
Choose &RQWLQXH. The system displays the actions relating to this object.
3. Choose 3UHSDUDWLRQ.
4. Use a report variant. If no variant is available, choose 0DLQWDLQ to maintain the
required variant.
job.
If you want to create a new variant, enter a name for the variant and choose 0DLQWDLQ.
You reach the variant maintenance screen for archiving maintenance orders. The
variant contains the selection criteria that the system uses to determine which data is
archived.
5. Maintain the selection criteria.
Choose &RQWLQXH and enter the attributes for the variant.
You can also maintain the following attributes in the section $FWLRQV:
– 6HWGHOHWLRQIODJ
Mark 6HWGHOHWLRQIODJ.
– 6HWGHOHWLRQLQGLFDWRU
-XQH
6HWWLQJ'HOHWLRQ)ODJVDQG,QGLFDWRUVIRU2UGHUVLQWKH%DFNJURXQG 30:2&0230
60$6&
Mark 6HWGHOHWLRQLQGLFDWRU.
– 6HWGHOHWLRQIODJDQGGHOHWLRQLQGLFDWRUVLPXOWDQHRXVO\
Mark 6HWGHOHWLRQIODJ and6HWGHOHWLRQLQGLFDWRUSave the variant.
6. Specify the start date.
7. Specify the spool parameters.
8. Choose (GLW→&UHDWHMRE
The deletion flags and indicators are set in the background.
6HHDOVR
-XQH
6HWWLQJ'HOHWLRQ)ODJV2QOLQHIRU2UGHUV 30:2&023060$6&
6HWWLQJ'HOHWLRQ)ODJV2QOLQHIRU2UGHUV 30:2&02
3060$6&
6HWWLQJ'HOHWLRQ)ODJVLQWKH0DLQWHQDQFH2UGHU
1. Choose /RJLVWLFV → 3ODQWPDLQWHQDQFH→30SURFHVVLQJ→ 2UGHUV → &KDQJH
2. Enter the relevant order number and choose &RQWLQXH.
You reach the order header.
3. Choose 2UGHU → )XQFWLRQV→'HOHWLRQIODJ→6HW
The system sets the status '/7.
4. Save the maintenance order.
6HWWLQJ'HOHWLRQ)ODJVLQWKH6HUYLFH2UGHU
1. Choose /RJLVWLFV → 6HUYLFHPDQDJHPHQW→6HUYLFHSURFHVVLQJ→ 2UGHUV →
&KDQJH
2. Enter the relevant order number and choose &RQWLQXH.
You reach the order header.
3. Choose 2UGHU → )XQFWLRQV→'HOHWLRQIODJ→6HW
The system sets the status '/7.
4. Save the service order.
-XQH
&KHFNV 30:2&023060$6&
&KHFNV 30:2&023060$6&
8VH
A maintenance order (PM order) can only be archived after a deletion flag and a deletion
indicator are set for it:
You can set the deletion flag in two ways:
• Setting Deletion Flags Online for Orders (PM-WOC-MO, PM-SMA-SC) [Seite 45]
• Setting Deletion Flags and Indicators for Orders in the Background (PM-WOC-MO,
PM-SMA-SC) [Seite 43]
5HVLGHQFH7LPHV
A maintenance order can only be archived after the residence times have elapsed. There are two
different residence times:
• 5HVLGHQFHWLPH is the time between the activation of the deletion flag and the
activation of the deletion indicator.
If the duration of residence time 1 is zero, the deletion flag and the deletion indicator
can be set at the same time.
• 5HVLGHQFHWLPH is the time between the activation of the deletion indicator and the
time at which the order can be archived and deleted from the database.
After the second residence time has elapsed, the orders are archived and
VLPXOWDQHRXVO\ deleted from the database.
For more information about setting residence times, see Application Customizing (PM-WOC-MO,
PM-SMA-SC) [Seite 42].
&KHFN&ULWHULDIRU6HWWLQJWKH'HOHWLRQ)ODJ
Before a deletion flag is set, the following prerequisites must be fulfilled:
• Any manually added purchase requisitions or purchase orders for the order must be
deleted.
• There must not be a balance for the order.The deletion flag can only be set when
the order has been settled or when there are no actual costs for the order. This
means that the balance of the actual costs for the order must be zero.
• Commitments relating to the order must be deleted.
• Unprocessed and incorrect goods movements relating to the order must be

processed first
When the deletion flag is activated, any capacity requirements present are
deleted. A deletion indicator will also be set in any existing reservations.
An order that has been flagged for deletion cannot be changed. You can,
-XQH
&KHFNV 30:2&023060$6&
however, cancel the deletion flag.
&KHFN&ULWHULDIRU6HWWLQJWKH'HOHWLRQ,QGLFDWRU
The system cannot convert the deletion flag to a deletion indicator if:
• The maintenance order is included in an order hierarchy or order network.
• The order has a relationship.

This function will be implemented as part of a later release.
-XQH
'HILQLWLRQ
Authorization object for archiving and deleting Plant Maintenance orders and service orders.
6WUXFWXUH
You require the following authorization for archiving maintenance orders:
$XWKRUL]DWLRQREMHFW $FWLYLW\ 2UGHUFDWHJRU\

C_AFKO_ATY 06 30
6HHDOVR
-XQH
7KH30B40(/$UFKLYLQJ2EMHFW'HILQLWLRQ 30:2&01
7KH30B40(/$UFKLYLQJ2EMHFW'HILQLWLRQ 30:2&
01
'HILQLWLRQ
Archiving object [Extern] with which you can archive maintenance notifications.
6WUXFWXUH
The archiving object for maintenance notifications 30B40(/ consists of the following tables:
7DEOHVWKDWDUHDUFKLYHG
7DEOH &RQWHQWV
QMEL Notification header data
QMFE Items
QMMA Activities
QMSM Tasks
QMUR Causes
QMIH PM data
ILOA Location data
IHPA Partners
PMLP Print log
MCIPMIS PMIS update, Before Image table, object data
CDHDR, CDPOS Change documents
KSSK Classification
JEST, JESTO Status
SWW_CONTOB Workflow, Workitem
THEAD Long text
Workflow can only be archived – not deleted – but you can archive Workflow
using the WORKITEM archiving object.
For more information on this topic, see the SAP document %&$SSOLFDWLRQ'DWD
$UFKLYLQJ%&%DVLV.
-XQH
8VH
You archive maintenance notifications that are no longer needed in the system using the archive
program. In archiving, the data is written to archive files and then deleted from the system if the
operation was successful.
You can archive and delete maintenance notifications using the 30B40(/ archiving object
[Extern].
You can archive Plant Maintenance notifications while the RQOLQHRSHUDWLRQis in process.
)HDWXUHV
3UHSDUDWLRQ
with which you flagged the objects you want to archive are also assigned the system status
0$5& ()ODJJHGIRUDUFKLYLQJ) in the preparation program.
$UFKLYLQJ
The DUFKLYLQJSURJUDP writes the database tables of the maintenance notifications listed under
the object definition [Seite 49] to the archive.
When Start automatically is set for the delete program in Archiving Customizing
[Extern], and a productive mode is selected for the archiving program, the system
starts the delete program in connection with its productive mode. This means that
the system deletes the archived data from the database.
'HOHWLQJ
The GHOHWHSURJUDP deletes all database records for the maintenance notifications which were
-XQH
3UHVHWWLQJV 30:2&01
3UHVHWWLQJV 30:2&01
As a presetting for Archiving, you must have set the status '/7 ('HOHWLRQIODJ) in the
maintenance notifications.
You have the following options for setting the deletion flag:
• The maintenance notifications can be manually flagged for deletion [Extern].
• You can flag completed maintenance notifications for deletion using the report
RIARCQM3:
To do this, choose /RJLVWLFV → 3ODQWPDLQWHQDQFH→30SURFHVVLQJ→1RWLILFDWLRQV
→6HWGHOHWLRQIODJ
– If you run the report in 7HVWPRGH,you can determine which maintenance
notifications are completed and for which notifications the completion date is n
days in the past (check for <=). For example, where n=200, the system checks all
completed maintenance notifications whose completion date is more than 200
days in the past.
– If you run the report in 3URGXFWLYH PRGH, the system sets the status '/7 ('HOHWLRQ
)ODJ) for the maintenance notifications found.
6HHDOVR
Application Customizing (PM-WOC-MN) [Seite 56]
-XQH
&KHFNV 30:2&01
&KHFNV 30:2&01
8VH
Before maintenance notifications can be archived, the system must determine if they are being
used in a maintenance order. For this purpose, XVDJHFKHFNVare performed for the individual
maintenance notifications
As soon as the system determines that a maintenance notification is used in a maintenance
order, the system status 0$5& )ODJJHGIRUDUFKLYLQJ can be set, but the system only archives
the maintenance notification if the maintenance order and the historical order have already been
deleted.
You can display a verification list of maintenance notifications that are still in use
and flagged for deletion by running the preparation program.
-XQH
When archiving you must consider dependencies between archiving objects, for example,
between maintenance notifications and maintenance orders. Generally, data for an archiving
object cannot be archived until the preceding objects have been archived.
As soon as a maintenance notification is used in a maintenance order, the system status 0$5&
()ODJJHGIRUDUFKLYLQJ) can be set, but the system only archives the maintenance notification if
the maintenance order and the historical order have already been deleted.
If you want to call up a network graphic to show the dependencies between archiving objects,
refer to The Network Graphic [Extern].
-XQH
-XQH
Some data must reside in the system for a specified length of time (for example, for legal
reasons) even if it is no longer being used. This is called the residence time. The data cannot be
You control the residence time for maintenance notifications using a report. Use the report
RIARCQM3 [Seite 51] to determine how long a completed maintenance notification must remain
the system before it can be flagged for deletion.
If the system establishes that a maintenance notification fulfills the requirements for archiving, it
can archive the archiving objects LPPHGLDWHO\ without a further residence time.
6HHDOVR
-XQH
8VH
In Customizing for Archiving you can change settings for archiving sessions specifically for
You FDQQRW archive Plant Maintenance data IRUDOOFOLHQWV.
You can run the archiving program either in WHVWPRGH or in SURGXFWLYHPRGH. No data is
archived or deleted in test mode.
program after data is written to archive files.
6HHDOVR
-XQH
The system checks by means of the authorization object I_VORG_MEL whether the following
authorizations are available for:
• Setting the status '/7('HOHWLRQIODJ)
• Setting the status 0$5& ()ODJJHGIRUDUFKLYLQJ)

If the authorizations are not available, the system terminates processing.
6HHDOVR
-XQH
&DOOLQJ8S$UFKLYLQJIRU0DLQWHQDQFH1RWLILFDWLRQV 30:2&01
&DOOLQJ8S$UFKLYLQJIRU0DLQWHQDQFH1RWLILFDWLRQV 30
:2&01
2 Enter the name of the archiving object you wish to use (30B40(/ for maintenance
notifications) and choose &RQWLQXH.
The system displays the available actions for the archiving object.
2. You can now select the required actions (for example “Preparation”, “Archive”) and
procedd as described in the relevant procedures.
-XQH
8VH
You can display archived maintenance notifications using a report.
3URFHGXUH
1. Choose (YDOXDWH. You reach a screen where you can plan a background job for the
program.
2. Use a report variant. The standard SAP variants for Plant Maintenance are:
job.
5. Choose 6SRROSDUDPHWHUV. You reach a screen where you can maintain the
background print parameters for the log created.
6HHDOVR
-XQH
3UHSDUDWLRQ/RJIRU0DLQWHQDQFH1RWLILFDWLRQV 30:2&01
3UHSDUDWLRQ/RJIRU0DLQWHQDQFH1RWLILFDWLRQV 30
:2&01
'HILQLWLRQ
The system creates a log when you run the preparation program for maintenance notifications as
a background job.
6WUXFWXUH
• Each processed maintenance notification

– With the confirmation “System status0$5&(flagged for archiving) set”
For example, if you ran the program in “test mode”, the system will list where-
used lists if necessary.
• Statistics regarding processed maintenance notifications

6HHDOVR
-XQH
$UFKLYLQJ/RJIRU0DLQWHQDQFH1RWLILFDWLRQV 30:2&01
$UFKLYLQJ/RJIRU0DLQWHQDQFH1RWLILFDWLRQV 30:2&
01
'HILQLWLRQ
The system creates a log when you run the archive program as a background job.
6WUXFWXUH
The log contains the following data:
• Each archived maintenance notification with exception messages if necessary

For example, if you ran the program in test mode, the log displays where-used lists if
there are any.
• Statistics regarding archived maintenance notifications
• Respective number of processed table entries
If you make the appropriate settings for the archiving object PM_QMEL in
Customizing for Archiving, the delete program will be run in a later job step
DXWRPDWLFDOO\. This also produces a log [Seite 62].
6HHDOVR
-XQH
'HOHWLRQ/RJIRU0DLQWHQDQFH1RWLILFDWLRQV 30:2&01
'HOHWLRQ/RJIRU0DLQWHQDQFH1RWLILFDWLRQV 30:2&
01
'HILQLWLRQ
If you set the option 6WDUWDXWRPDWLFDOO\ for the delete program in Customizing, the delete
program will be run DXWRPDWLFDOO\ after Archiving. This also produces a log.
6WUXFWXUH
The log contains statistics regarding processed maintenance notifications per archiving session.
6HHDOVR
-XQH
2EMHFW
Archiving object [Extern] for archiving maintenance task lists (PM task lists).
8VH
You archive and delete maintenance task lists with the 30B3/$1 archiving object. The archiving
object comprises individual task lists which are identified uniformly by task list group and group
counter, but not entire task list groups, so that you can archive and delete individual task lists at
any time. As before, you can archive and delete entire task list groups.
You cannot import task list data.

Displaying archived task lists will only be possible from a later release.
6WUXFWXUH
The 30B3/$1 archiving object contains the following data:
• Task list header
• Operations and sub-operations
• Material components
• Production resource/tool
• Classification data
• Service packages
• Inspection characteristics and inspection characteristics values
• Texts
The archiving of object dependencies is only planned for a later release.
7DEOHV,QYROYHG
The following tables are involved in Archiving:
7DEOH 'HVFULSWLRQ
PLKO Task list header
PLKZ Time-independent header data (for example, administrative data)
MAPL Material-task list allocations
KALC Formulae for material quantity calculation
KALT Texts for the formulae
-XQH
EAPL Equipment allocations

TAPL Allocations of functional locations
PLFL Task list sequences
PLPO Operations
PLAS Allocations of operations to sequences
PLMZ Material component allocations
PLWP Preventive maintenance package allocations
PLFH Production resources/tool allocations
PLMK Inspection plan characteristics
PLMW Inspection plan characteristic values
PLAB Task list relationships
PLTX PMS texts
PLPH Phases and partial operation of CAP
PLFT Process instructions
PLFV Process instruction characteristics and partial operation parameters
MLST Milestones
EINA Purchasing info record (general data)
EINE Purchasing info record (data for purchasing organization)
ESLL Lines of service packages
ESLH Service package header data
-XQH
8VH
You can archive Plant Maintenance task lists (PM task lists) that are no longer needed in the
system using the archive program. Archiving writes data to the archive files and then deletes the
data from the database if the operation was successful.
You can archive and delete Plant Maintenance task lists using the 30B3/$1 archiving object
[Extern].
)HDWXUHV
&KDQJHVWDWXVHVIURPSUHYLRXV55HOHDVHV
Task lists from previous R/3 releases may only have one deletion flag for individual release
statuses.
You can release existing deletion flags to all release statuses of the maintenance task list using
the report RCPREDEL [Seite 70]. You use this report RQFH after the data transfer from a
previous release in order to create the same prerequisites for both old and new maintenance task
list data.
&XVWRPL]LQJ
Use the SAP enhancement (user exit) CPRE0001 in Customizing to define criteria which the
system should check before a maintenance task list can be archived. Note that the standard
system already performs several usage checks [Seite 63].
For more information about Customizing, see Archive Customizing [Extern].
6HOHFWLRQFULWHULD
You can select maintenance task lists for archiving according to the following criteria:
• Task list type, task list group and group counter
• Plant
• Status
• Task list usage
• Planner group
• Preventive maintenance strategy
• Assembly
• Time of last planning delivery schedule

All task lists whose usage is before the key date are selected.
• Date when last used
-XQH
Date on which the task list was last used in a Plant Maintenance order or Service
Management order.
• Deletion flag
If you enter the deletion flag as a criterion for the archiving session using the delete
program, you can only choose 'HOHWHRYHUZKROHWLPHSHULRG.
You can also delete maintenance task lists which do not have a deletion flag.
Deletion flags are not a prerequisite.
If you archive the task lists from previous releases (selection criterion deletion
flags), without previously having used the report RCPREDEL [Seite 70], only
those task lists which have a deletion flag on DOO releases are archived. Task lists
which have deletion flags on individual releases are not selected if you enter
deletion flags as a criterion.
$FWLYLWLHV
If the selection criteria in the standard program are not sufficient, or if you want different criteria,
you can define your own FXVWRPHUVSHFLILFVHOHFWLRQFULWHULD.
1. Define your own archiving object. Use the PM_PLAN archiving object as a reference.
2. Write your own selection report. Use the report RPMREWR1 as a reference. Only
change
– RCPPMSEL for 6HOHFWLRQSDUDPHWHUV
– RCPPMF01 for 6HOHFWLRQV
-XQH
0HPRU\5HTXLUHPHQW
A maintenance task list with twelve operations, four material components and two production
resources/tools requires approximately 40 Kilobytes of memory for archiving.
You can check the maximum length of the individual data records in the Data Dictionary
information system.
3URJUDP5XQWLPH
There is currently no information about the runtime for archiving maintenance task lists.
6HHDOVR
Memory Gained by Archiving [Extern]
-XQH
&KHFNV 303507/
&KHFNV 303507/
8VH
If you change maintenance task lists (PM task lists) or task list objects XVLQJDFKDQJHQXPEHU,
the task list consists of several change statuses. If you never change using a change number,
the task list and all its task list objects have only one individual change status.
You can delete your data in the following ways:
• Over the entire time period
• On the key date
'HOHWLQJRYHUWKHHQWLUHWLPHSHULRG
If you delete over the entire period of time, all task lists which met your selection criteria are
deleted (for example,. for equipment and status).
You can also enter existing deletion flags as selection criteria. If you do not enter
deletion flags explicitly as criteria, task lists are deleted regardless of whether
they have a deletion flag.
'HOHWLQJRQWKHNH\GDWH
Deleting on the key date is sensible above all if you have accumulated historical data statuses
which you no longer need.
The subsequent checks only concern maintenance task lists which you have created ZLWK a
change number.
If you delete on the key date, all change statuses [Seite 76] which end EHIRUH this key date are
deleted. For periods EHIRUH the key date, it does not matter whether task lists or task list objects
have deletion flags or whether they have been deleted online at an earlier date.
The system also checks change statuses which lie on or DIWHU the key date. The key factor here
is whether these change statuses have already been deleted RQOLQH. The system deletes these
change statuses from the database although they lie on or after the key date. For this, there are
no time gaps. This means that if a change status GRHV QRW have an online deletion indicator, the
following change statuses are not deleted from the database, even if you already have an online
indicator.
6HHDOVR
Maintenance Task Lists with Several Change Statuses (PM-PRM-TL) [Seite 69]
-XQH
0DLQWHQDQFH7DVN/LVWVZLWK6HYHUDO&KDQJH6WDWXVHV 303507/
0DLQWHQDQFH7DVN/LVWVZLWK6HYHUDO&KDQJH6WDWXVHV
303507/
If you change maintenance task lists (PM task lists) or maintenance task list objects with a
FKDQJHQXPEHU, the task list consists of several change statuses. If you never change with a
change number, the task list and all its task list objects have only one change status.
'HOHWLQJD7DVN/LVW2QOLQH
If you GHOHWH a change status online in a maintenance task list with several change statuses, a
change status for further processing will only be blocked for this one, together with all lower-level
objects. You can continue to access the remaining change statuses.
'HOHWLRQ)ODJZLWK6HYHUDO&KDQJH6WDWXVHV
If you set a GHOHWLRQIODJ for a change status in a maintenance task list with several change
statuses, the deletion flag is set simultaneously in the entire maintenance task list. If you enter
deletion flags as criteria for an archiving session, the entire task list with all the task list objects
will be archived and deleted. Similarly, if you cancel a deletion flag, this always applies to the
entire task list.
To delete a task list with several release statuses completely from the database, choose on of
the following options:
• Set a deletion flag in the task list header. For the archiving session with the delete
program, choose 'HOHWLRQIODJV as a selection criteria. For more information on setting
a deletion flag in the task list, see 300DLQWHQDQFH7DVN/LVWV.
• Specify the task list completely in the selection criteria of the archiving session and
delete RYHUWKHHQWLUHWLPHSHULRG.
-XQH
0DLQWHQDQFH7DVN/LVWVIURP3UHYLRXV55HOHDVHV 303507/
0DLQWHQDQFH7DVN/LVWVIURP3UHYLRXV55HOHDVHV
303507/
8VH
Since Release 3.0D, deletion flags always refer to all change statuses [Seite 76] of a
maintenance task list (PM task list). If you set a deletion flag for a change status, the deletion flag
is set simultaneously in the entire task list.
In older R/3 releases, deletion flags were treated differently. For this reason, there is report
RCPREDEL.
Use this report RQFH after the data transfer from a previous release to create the same
prerequisites for old and new maintenance task list data. You do not need this report for data
which you create in releases from 3.0D onwards.
5HSRUW5&35('(/
Task lists from previous R/3 releases may only have one deletion flag for individual change
statuses.
You can release existing deletion flags to all change statuses of the task list using the report
RCPREDEL. This is important above all if you want to enter deletion flags as a criterion for your
archiving session with the delete program.
If you archive task lists from previous releases (selection criterion 'HOHWLRQIODJV),
without previously having used the report RCPREDEL, only those task lists which
have a deletion flag on DOO change statuses are archived. Task lists with deletion
flags on individual change statuses are not selected, if you enter deletion flags as
a criterion.
-XQH
'HSHQGHQFLHV
'HSHQGHQFLHV
You archive your inspection lots (QM_CONTROL archiving object) before you archive
maintenance task lists.
Before deleting, the system checks whether the maintenance task lists (PM task lists) are used in
the following objects:
• 0DLQWHQDQFHLWHP
• ,QVSHFWLRQORW
This criterion is only relevant if you use the 4XDOLWlW\0DQDJHPHQW (QM) application
component. The system can only archive the maintenance task list if it is no longer
being used in an inspection lot.
• 6HUYLFHRUGHUV
Is the maintenance task list used to create service orders automatically?
• 2WKHUXVHV
You can use the SAP enhancement CPRE0001 to define criteria that the system
should check before a maintenance task list can be archived.
:KDWKDSSHQVLIDWDVNOLVWLVVWLOOEHLQJXVHG"
If a usage check finds a task list which is still being used and meets your customer-specific check
criteria (SAP enhancement CPRE0001), you can do one of the following:
• The archiving session terminates. You receive a message with information about the
task list which is still being used. If you want to use this option, do QRW select the
indicator /RJin the variant maintenance.
• The archiving session finishes completely. At the end, you receive a log [Extern]
with a list of all task lists which have not been archived or deleted owing to the usage
check.
If you want to use this option, select the indicator /RJ in the variant maintenance.
6HHDOVR
The Network Graphic [Extern]
-XQH
To archive task lists, you need authorization for the object ,B5287 and general archiving
authorization [Extern].
To delete ZLWK Archiving for
• Activity : Generate archive files
• Activity : Delete the database

To delete ZLWKRXW Archiving for
• Activity : Delete the database
-XQH
You reach the initial screen for Archiving.
2. Enter the archiving object (for 30B3/$1 task lists) and choose $UFKLYLQJ.
3. Enter a variant.
If you want to create a new variant, enter the name of the variant and choose
0DLQWDLQ.
You reach the variant maintenance for archiving task lists. The variant contains the
selection criteria for archiving and deleting task lists.
Maintain the selection criteria and note the deletion criteria [Seite 68]. Then choose
&RQWLQXH.
4. Define the start date.
5. Define the spool parameters.
6. Choose &UHDWHMRE.
The archive files are created for the start date in the background. After the archiving
session, you receive a standard log [Extern].
If 6WDUWDXWRPDWLFDOO\ is set for the delete program in Archive Customizing

[Extern], the delete program is called up automatically, as soon as the first
archive file is created. Note that this indicator is set as standard.
6HHDOVR
Archive Management: The Create Archive Files Screen [Extern]
-XQH
3UHUHTXLVLWHV
You have created an archive file. If the delete program is not called up automatically after the first
archive file is created, (see Archive Customizing [Extern]), you must start the delete program
manually, if the system has created all the archive files.
You can also delete maintenance task lists which do not have a deletion flag.
Deletion flags are not a prerequisite.
You can either:
• Process an entire archiving session with all archive files created.
• Choose individual archive files for processing.
3URFHGXUH
2. Enter the archiving object (30B3/$1 for task lists) and choose 'HOHWH.
You reach the $UFKLYH0DQDJHPHQW([HFXWH'HOHWH3URJUDP screen.
3. Choose $UFKLYHVHOHFWLRQ.
A dialog box shows you all archiving sessions which are available for the archiving
object selected.
4. If you want to process a complete archiving session, select the archiving session and
choose &RQWLQXH.
If you only want to process certain archive files, choose 'LVSOD\GDWD.
You receive all archiving sessions which have not yet been processed, together with
your archive files. Select the required archive files and choose &RQWLQXH.
5. Define the start date.
6. Define the spool parameters.
7. Choose &UHDWHMRE.
The task lists selected are deleted for the start date in the background. At the end of
the delete program, you receive a standard log [Extern].
6HHDOVR
Archive Management: The Execute Delete Program Screen [Extern]
-XQH
3URFHGXUH
1. Choose /RJLVWLFV→3ODQWPDLQWHQDQFH→0DLQWHQDQFHWDVNOLVWV→([WUDV→'HOHWH
WDVNOLVWV→:LWKRXWDUFKLYLQJ
You reach the 'HOHWH7DVN/LVWV:LWKRXW$UFKLYLQJ screen.
2. Maintain the selection criteria for deleting task lists or task list objects and note the
deletion criteria [Seite 68].
3. Choose ([HFXWH.
The task lists or task list objects selected are deleted completely from the database.
You receive a standard log [Extern].
-XQH
&KDQJH6WDWXVHVRI0DLQWHQDQFH7DVN/LVWV 303507/
&KDQJH6WDWXVHVRI0DLQWHQDQFH7DVN/LVWV 30350
7/
If you change maintenance task lists (PM task lists) or maintenance task list objects with a
change number, the task list consists of several change statuses. If you never change with a
change number, the task list and all its task list objects have only one individual change status.
-XQH
7KH30B,)/27$UFKLYLQJ2EMHFW'HILQLWLRQ 30(40)/
7KH30B,)/27$UFKLYLQJ2EMHFW'HILQLWLRQ 30(40
)/
'HILQLWLRQ
Archiving object [Extern] with which you can archive functional locations.
6WUXFWXUH
The archiving object for functional locations 30B,)/27 consists of the following tables:
7DEOH 6KRUWWH[W
IFLOT Functional location master data
IFLOTX Multilingual short texts and long texts for functional locations
ILOA Location and account assignment data for the maintenance object
IHSG PM authorization table with long texts
JEST Functional location status
KSSK Characteristic assignment for the class
CDHDR Change documents
-XQH
8VH
You archive functional location master data that you no longer need in the system by using the
archiving program. The archive program writes data to archive files and then deletes it from the
database if the operation was successful.
You archive and delete functional location master data using the archiving object [Extern]
30B,)/27.
You can archive functional locations in PM while the RQOLQHRSHUDWLRQ is in process.
)HDWXUHV
3UHSDUDWLRQ
with which you flagged the equipment you want to archive are also assigned the system status
'HOHWLRQLQGLFDWRUin the preparation program. However, note that processing can only take place
if the system determines equipment is QRW being used elsewhere in the system.
$UFKLYLQJ
The DUFKLYLQJSURJUDP writes the database tables of the functional locations listed under the
object definition [Seite 7] to the archive.
DXWRPDWLFDOO\. This means that all successfully archived data is then
DXWRPDWLFDOO\ deleted.
'HOHWLQJ
The GHOHWHSURJUDP deletes all database records for the pieces of equipment which were
-XQH
&KHFNV 30(40)/
&KHFNV 30(40)/
8VH
Before functional locations can be archived, the system must determine whether functional
locations are used elsewhere (for example, in a task list). To do this, the system performs XVDJH
FKHFNVfor individual functional locations.
3UHUHTXLVLWHV
The functional location must have the status 'HOHWLRQIODJ as a presetting for Archiving.
For more information on setting deletion flags, see Setting the funtional locations [Extern] (30
6WUXFWXULQJ7HFKQLFDO6\VWHPV .
)HDWXUHV
The section &KHFNVIRU)XQFWLRQDO/RFDWLRQV describes the chronological sequence in which the
possible usages in the system are checked. As soon as the system determines that the
functional location is being used, you cannot set the status '/7 ('HOHWLRQLQGLFDWRU) for that
functional location.
The system checks the following information for IXQFWLRQDOORFDWLRQV:
• Usage as functional location
• Usage as superior functional location
• Usage as functional location affected
You can display a list of instances where functional locations are used in the
system by using the analysis report RIARCTP1 Where-Used Lists for Functional
Locations [Seite 88]
The following tables describe the chronological order in which the system checks for usage of
functional locatons. As soon as the system determines that the functional location is being used,
you cannot set status '/7 ('HOHWLRQLQGLFDWRU) for that functional location.
8VDJHDV)XQFWLRQDO/RFDWLRQ
&KHFNFULWHULD $IXQFWLRQDOORFDWLRQFDQQRWEHDUFKLYHGLI
Location and account assignment for An address is assigned to it.

maintenance object
Task list A task list is assigned to it.
BOM It is included in a BOM.
Location and account assignment for It is included in other account assignments of
maintenance object the maintenance object.
Measuring point A measuring point is assigned to it.
-XQH
&KHFNV 30(40)/
Document link A document is assigned to it.

Object link It is included in an object network.
Order header It is included in an order.
Historical order It is included in an historical order.
Maintenance notification (PM notification) It is included in a PM notification.
Object list It is included in an object list.
WBS element (work breakdown structure It is included in the master data of a WBS
element) element.
Capital investment program It is included in the item of a capital
investment program.
Maintenance plan item It is included in a maintenance plan item.
8VDJHDV6XSHULRU)XQFWLRQDO/RFDWLRQ
Functional location, master data It is contained in a location hierarchy as a superior

functional location
8VDJHDV)XQFWLRQDO/RFDWLRQ$IIHFWHG
Maintenance notification It is contained in a PM notification as an affected functional

location.
-XQH
When archiving data you must consider data dependencies, such as those between functional
locations and Plant Maintenance (PM) notifications. Generally, you cannot archive an object until
dependent objects have been archived.
The network graphic, shows dependencies between objects. For more information, see The
Network Graphic [Extern].
-XQH
-XQH
Since the residence time deals with a typical characteristic of Plant Maintenance (PM)
transaction data, 30PDVWHUGDWDGRHVQRWUHTXLUHDUHVLGHQFHWLPH.
Once the system establishes that a functional location meets the requirements for archiving, it
can archive the data LPPHGLDWHO\.
6HHDOVR
-XQH
8VH
In Customizing for Archiving, you can adjust the settings for archiving sessions specifically for
You FDQQRW archive Plant Maintenance data IRUDOOFOLHQWV.
You can archive data either in WHVW or SURGXFWLYHPRGH. No data is archived or deleted in test
mode.
6HHDOVR
-XQH
To archive functional locations for Plant Maintenance, you only require general archiving
authorization.
6HHDOVR
-XQH
&DOOLQJ8S$UFKLYLQJIRU)XQFWLRQDO/RFDWLRQV 30(40)/
&DOOLQJ8S$UFKLYLQJIRU)XQFWLRQDO/RFDWLRQV 30(40
)/
To call up Archiving generally, proceed as follows:
2. Enter the name of the archiving object (30B,)/27 for functional locations). Choose
&RQWLQXH.
The system displays the available functions for the archiving object.
3. You can now select the required actions (for example, “3UHSDUDWLRQ´, “$UFKLYH´) and
proceed as described in the relevant procedures.
-XQH
8VH
You can display and evaluate the data from archived functional locations:
3URFHGXUH
1. &KRRVH(YDOXDWH. You reach the screen where you can plan a background job for the
program.
2. Use a report variant. The standard variants for Plant Maintenance (PM) are:
job.
3. Choose 6WDUWGDWH. This brings you to a screen where you can maintain start dates.
5. Choose 6SRROSDUDPHWHUV. You reach a screen where you can maintain the
background print parameters for the log created.
6HHDOVR
-XQH
'LVSOD\LQJ:KHUH8VHG/LVWVIRU)XQFWLRQDO/RFDWLRQV 30(40)/
'LVSOD\LQJ:KHUH8VHG/LVWVIRU)XQFWLRQDO/RFDWLRQV
30(40)/
8VH
Use the analysis report 5,$5&73()XQFWLRQDOORFDWLRQZKHUHXVHGOLVWV) to display a where-
used list for functional locations that are still used in the system and therefore cannot be
archived.
3URFHGXUH
1. Choose 6\VWHP→6HUYLFHV→5HSRUWLQJ
You reach the $%$3([HFXWH3URJUDPscreen.
2. Enter the report name 5,$5&73 in the 3URJUDP field.
3URJUDP→([HFXWH
3URJUDP→([HFXWHZLWKYDULDQW
The system displays a list that shows where each functional location is used.
If you GRQRW mark the field 6WDWXVFKHFN, the system displays usages regardless
of whether the technical object has a deletion flag or not.
If you GR mark the field 6WDWXVFKHFN, the system checks whether the technical
object has a deletion flag. The existing usages are displayed only if it does.
If the selection is performed ZLWKRXWGHOLPLWDWLRQ of )XQFWLRQDOORFDWLRQ
)XQFWLRQDOORFDWLRQFDWHJRU\or 6WUXFWXUHLQGLFDWRU the system selects only
functional locations for which the status '/7('HOHWLRQLQGLFDWRU) is set.
-XQH
,PSOHPHQWLQJ0DWFKFRGH6HWXSIRU)XQFWLRQDO/RFDWLRQV 30(40)/
,PSOHPHQWLQJ0DWFKFRGH6HWXSIRU)XQFWLRQDO
/RFDWLRQV 30(40)/
1. Choose 7RROV→$%$3:RUNEHQFK→'HYHORSPHQW→'LFWLRQDU\
You reach the initial 'LFWLRQDU\ screen.
2. Enter the name of the matchcode in the 2EMHFWQDPH field (,)/0 for functional
locations).
3. Mark the field 0DWFKFRGHREMHFWV in the 'LFWLRQDU\REMHFWVblock.
'LFWLRQDU\REMHFW→&KDQJH
'LFWLRQDU\REMHFW→'LVSOD\
6HHDOVR
Customizing: Matchcode Setup
-XQH
'HILQLWLRQ
When you run the preparation program for functional locations as a background job, the system
creates a log that describes how many functional locations were flagged for deletion by
IXQFWLRQDOORFDWLRQFDWHJRU\DQGVWUXFWXUHLQGLFDWRU.
6WUXFWXUH
• Each processed functional location

– With the confirmation “System status'/7(Deletion indicator) set”
For example, if you executed the program in “test mode”, the system will list the
where-used lists for each functional location if necessary.
• Statistics regarding processed functional locations

6HHDOVR
-XQH
'HILQLWLRQ
When you run the archiving program as a background job the system produces a log.
6WUXFWXUH
The log contains the following information:
• Each processed functional location with exception messages if necessary

For example, if you executed the program with the parameter “test mode”, the where-
used lists for each functional location will be listed
• Number of processed table entries
If you make the appropriate settings for the archiving object PM_IFLOT in
Customizing, the delete program will start DXWRPDWLFDOO\ after archiving and
deletes all successfully archived files. This also produces a log [Seite 92]
6HHDOVR
-XQH
'HILQLWLRQ
If you set the option 6WDUWDXWRPDWLFDOO\ for the archiving object PM_IFLOT in Customizing for
Archiving, the delete program will start DXWRPDWLFDOO\ after archiving and deletes all successfully
archived data. This also produces a log.
6WUXFWXUH
The delete program contains the following data:
• Statistics regarding the processed objects for each archiving session.

6HHDOVR
-XQH
$UFKLYLQJRI0HDVXUHPHQW'RFXPHQWV 30(406)03&
$UFKLYLQJRI0HDVXUHPHQW'RFXPHQWV 30(406)
03&
'HILQLWLRQ
Archiving object [Extern] with which you can archive measurement documents in the Plant
Maintenance application component.
6WUXFWXUH
The archiving object for measurement documents 30B,05* includes the following tables:
7DEOH 6KRUWWH[W
CDHDR Change document header
CDPOS Change document item
IMRG Measurement document
THEAD Long text
-XQH
8VH
You can use the archiving object [Extern] to archive and delete measurement documents which
do not need to be accessed directly in the system.
)HDWXUHV
You can only delete measurement document areas, this means, from the first measurement
document entered until a key date. You cannot archive and delete individual measurement
documents.
At least one measurement document is usually retained when archiving. This is the ODWHVWQRQ
FDQFHOHG measurement document. However, in the following cases, more than one
measurement document is retained:
• If there are canceled measurement documents after the latest measurement

document, then the latest measurement document and all subsequent canceled
measurement documents are retained.
• If there are several measurement documents with the same entry date and the same
(exact to the second) entry time, then all of the “latest” measurement documents are
retained. This can occur, for example, if you enter test data.
You can also archive and delete all the measurement documents for a measuring point or
counter, as required. For more information, see Variant Settings for Preparation (PM-EQM-SF-
MPC) [Seite 97].
3UHSDUDWLRQ
The preparation program prepares the data in the database for archiving. In the preparation
variants, you enter the selection criteria for the measurement documents which you want to
archive and delete. The system sets a deletion flag (DFLAG) internally for all measurement
documents selected.
You cannot reset deletion flags which have been set for measurement
documents.
$UFKLYLQJ
The archiving program writes the database tables of the measurement documents listed under
the Object Definition [Seite 93] to the archive.
You can:
• Perform archiving in a test run
• Only archive measurement documents
• Archive and delete measurement documents
-XQH
'HOHWLQJ
If you have selected $UFKLYHDQGGHOHWHGRFXPHQWV in the archiving variants, the deletion
program deletes all the measurement documents which the system has archived successfully.
If the deletion program is not called up automatically after the activity $UFKLYH has been
completed successfully, you must wait until all the archiving is completed. You can process an
entire archiving session with all the archive files created or you can select individual archive files
for processing.
-XQH
8VH
You set parameters for Archiving in the application-specific Customizing:
)HDWXUHV
In the application-specific Customizing, you can define the maximum number of data objects
[Extern] per archive. For the archiving of measurement documents, the R/3 System creates a
new data object when the following conditions are fulfilled:
• A new measuring point or counter begins.
• 500 measurement documents have already been archived for a measuring point or
counter.
The system archives measurement documents in sequence for each measuring point or counter.
For more information about Customizing settings, see General Archiving Customizing [Extern].
$FWLYLWLHV
To call up the application-specific Customizing, in the initial archiving screen, choose Goto
→ &XVWRPL]LQJand then 7HFKQLFDOVHWWLQJV.
-XQH
8VH
For the archiving object PM_IMRG, you can enter selection criteria in the variant for the
preparation. For the selected measurement document area, the system sets a deletion flag
(DFLAG) and thereby selects the measurement documents for archiving and deleting. You
cannot archive and delete individual measurement documents.
You cannot reset deletion flags.
)HDWXUHV
In the variant maintenance for the preparation, the selection criteria available include:
• 0HDVXULQJSRLQW (all measurement documents for a measuring point or counter)
• (TXLSPHQW (all measurement documents for a piece of equipment)
• 8QWLOPHDVXULQJWLPH (all measurement documents from the start until the stated
measuring time [key date])
You can perform archiving in a test run, only archive measurement documents, or archive and
delete measurement documents.
To ensure that at least one measurement document is retained for each measuring point or
counter, the field 5HWDLQPHDVXUHPHQWGRFXPHQWSHUPHDVXULQJSRLQW is selected in the
standard system.
Do not select this field if you want to archive and delete collective measurement documents. This
can be advisable in the following cases:
• You have only previously entered test data, which you want to delete, for a measuring
point or counter, in order to restart the measuring point or counter.
• You want to delete all the measurement documents for a measuring point or counter,
in order to then delete the measuring point or counter.
-XQH
8VH
For the archiving object PM_IMRG, you can enter selection criteria in the variant for the archiving
program. For the selected measurement document area, the archiving program writes the
database tables of the measurement documents listed under Object Definition [Seite 93] to the
archive. From the selected measurement document area, the system only archives measurement
documents which have retained a deletion flag in the preparation.
)HDWXUHV
As in the preparation variant, the selection criteria available in the variant maintenance for
archiving include:
• 0HDVXULQJSRLQW (all measurement documents for a measuring point or counter)
• (TXLSPHQW (all measurement documents for a piece of equipment)
• 8QWLOPHDVXULQJWLPH (all measurement documents from the start until the stated
measuring time [key date])
You can perform archiving in a test run, only archive measurement documents, or archive and
delete measurement documents.
-XQH
To archive measurement documents, you only require general archiving authorization.
6HHDOVR
Authorization Check [Extern]
-XQH
/RJRI3UHSDUDWLRQIRU0HDVXUHPHQW'RFXPHQWV 30(406)03&
/RJRI3UHSDUDWLRQIRU0HDVXUHPHQW'RFXPHQWV 30
(406)03&
'HILQLWLRQ
The preparation for the archiving of measurement documents produces a log.
6WUXFWXUH
It contains the following detailed data:
• Start and end of the preparation
• Statistics
− Number of selected measurement documents
− Number of selected measuring points
− Number of deletion flags set
-XQH
/RJRI$UFKLYLQJIRU0HDVXUHPHQW'RFXPHQWV 30(406)03&
/RJRI$UFKLYLQJIRU0HDVXUHPHQW'RFXPHQWV 30
(406)03&
'HILQLWLRQ
The system produces a log when archiving measurement documents.
6WUXFWXUH
It contains the following detailed data:
• Number of data objects
• Size of data objects
• Statistics
− Number of archived change documents
− Number of archived document items
− Number of archived measurement documents
-XQH
3UHUHTXLVLWHV
You have performed the preparation productively.
3URFHGXUH
1. Display the measurement documents using the list variant. To do this, choose
/RJLVWLFV → 3ODQWPDLQWHQDQFH→ 7HFKQLFDOREMHFWVand then (TXLSPHQW→
0HDVXUHPHQWGRFXPHQWV→ /LVWHGLWLQJ→ 'LVSOD\
You reach the measurement document selection screen.
2. Enter the required data.
3. In the measurement document list, you can expand the current display variant with
the field 'HOHWLRQIODJ. To do this, choose 6HWWLQJV→ 'LVSOD\YDULDQW→ &XUUHQW.
For more information about working with lists and list variants, see Working with Lists [Extern].
-XQH
'LVSOD\LQJ$UFKLYHG0HDVXUHPHQW'RFXPHQWV 30
(406)03&
)XQFWLRQ 0HQXSDWK :KDW\RXVKRXOGNQRZ

Displaying archived /RJLVWLFV→ 3ODQW You use this function if you
measurement PDLQWHQDQFH→7HFKQLFDO are just editing measurement
documents from the REMHFWV→ documents.
application (TXLSPHQW)XQFWLRQDO The system displays the
ORFDWLRQ!→ 0HDVXUHPHQW measurement documents in
GRFXPHQWV→ /LVWHGLWLQJ→ list form, as if they were still
'LVSOD\DUFKLYH available in the R/3 System.
Displaying archived In the initial archiving screen, You use this function if you
measurement choose (YDOXDWH. are just working in the
documents from the archiving administration.
Then choose the program
archiving
5,$5&50,. You can choose between
administration
batch or dialog processing.
The system displays all the
data for the measurement
documents in list form, as if
they were still available in the
R/3 System.
-XQH
Displaying archived In the initial archiving screen, You use this function if you
measurement choose (YDOXDWH. only want to display the most
documents using the important measurement
Then choose the program
PRGHOUHSRUW document data in tabular
5,$5&506.
form.
You can choose between
batch or dialog processing.
The program displays the
most important measurement
document data.
- Measuring point
- Measurement documents
- Document numbers
- Date and time
- Measurement reading
entered with unit
- Valuation codes (code
catalog, code group,
valuation catalog)
You can use the model report
as a copy reference for
customer-specific reports.
Essentially, it contains the
function modules for procuring
and selecting measurement
documents from the archive.
-XQH

PM Plant Maintenanc

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PM Plant Maintenanc

Uploaded by

Copyright:

Available Formats

303ODQW0DLQWHQDQFH

$SSOLFDWLRQ6SHFLILF)HDWXUHV 30:2&01  

$XWKRUL]DWLRQV 30(406)03&  

When 6WDUWDXWRPDWLFDOO\ is set for the delete program in Archiving Customizing

• Usage as equipment number

• Usage as superior equipment

• Usage as equipment affected

• Selection criteria and parameter settings used

• Each piece of processed equipment

• Statistics regarding processed equipment master records

• Selection criteria and parameter settings used

• Each processed equipment with exception messages if necessary

• Statistics regarding archived objects

• Number of created archive files

• All administrative data

• Number of processed table entries

• Selection criteria and parameter settings used

• Statistics regarding the processed objects for each archiving session.

• The service notifications can be flagged for deletion [Extern] manually.

• Setting the status '/7 ('HOHWLRQIODJ)

• Setting the status0$5& ()ODJJHGIRUDUFKLYLQJ)

• Each processed service notification

• Statistics regarding processed service notifications

• Each processed service notification with exception messages if necessary

• Statistics regarding archived objects

• Number of created archive files

• All administrative data

• Respective number of processed table entries

• Order header overall (table AUFK, AFKO)

• Status of order header and operation

• Long text for order header and operation

• Purchase requisition for operation and components

• Confirmation for operation and components

Since Release 3.0F, it has been possible to generate an historical order

• Maintenance planning plant

• Deletion indicator is set

• Residence time 2 has elapsed

• Set deletion flag only

• Set deletion indicator only

• Set deletion flag and deletion indicator simultaneously

• Commitments relating to the order must be deleted.

• Unprocessed and incorrect goods movements relating to the order must be

however, cancel the deletion flag.

• The maintenance order is included in an order hierarchy or order network.

• The order has a relationship.

$XWKRUL]DWLRQREMHFW $FWLYLW\ 2UGHUFDWHJRU\

• The maintenance notifications can be manually flagged for deletion [Extern].

• Setting the status '/7('HOHWLRQIODJ)

• Setting the status 0$5& ()ODJJHGIRUDUFKLYLQJ)

• Each processed maintenance notification

• Statistics regarding processed maintenance notifications

• Each archived maintenance notification with exception messages if necessary

• Statistics regarding archived maintenance notifications

• Number of created archive files

• All administrative data

• Respective number of processed table entries

You cannot import task list data.

• Task list header

• Operations and sub-operations

• Inspection characteristics and inspection characteristics values

EAPL Equipment allocations

• Task list type, task list group and group counter

• Task list usage

303ODQW0DLQWHQDQFH

$SSOLFDWLRQ6SHFLILF)HDWXUHV 30:2&01

$XWKRUL]DWLRQV 30(406)03&

• Activity : Generate archive files

• Activity : Delete the database

• Activity : Delete the database