Archiving Maintenance and Service Orders (PM-SMA-SC/PM-WOC-MO)
Archiving object
PM_ORDER, which you can use to archive maintenance orders and service orders in the
Plant Maintenance
application component.
Note
You can use this archiving object in
Information Lifecycle Management
. You must have activated the corresponding business functions to do this. The system then shows the
ILM Actions
group box. You can use these actions, for example, to evaluate the retention periods stored in the Information Retention Manager during archiving. Additionally, you can create snapshots (copies) of data or destroy data if it matches the requirements. For more information, see
Activating SAP NetWeaver ILM
.
The archiving object PM_ORDER contains all of the data relating to the order:
Table |
Contents |
AFIH |
Order header |
AFAB |
Network - Relationships |
IHPA |
Partner |
IHSG, IHGNS |
Approvals |
ILOA |
Location and account assignment for the maintenance object |
OPROL |
Operation link to object list entry |
MSM_COMM_LOG_1 |
Communications log for MSM for paging |
MSM_COMM_LOG_2 |
Communications log for MSM for paging status |
PMCO |
Cost structure and overview of the order (order header) |
PMCO_OP |
Cost structure and overview of the order (order item |
MCIPMIS |
Order data for PMIS |
PMCOQT |
Quantity structure for the maintenance order (order header) |
PMCOQT_OP |
Quantity structure for the maintenance order (order item) |
PMPL |
Print data for the order |
PMSDO |
PM organizational data for SD documents |
SER00 (see note) |
General header table for serial number management |
SER05 (see note) |
Document header for serial numbers for the refurbishment order |
OBJK (see note) |
Object list |
AFPO (see note) |
Order item |
DRAD (see Note) |
Document-Object Link |
Note
The archiving process for archiving object PM_ORDER operates independently of whether an account assignment was made for the order at the order header level or the order item level.
Note
If the order in question is a refurbishment order , the system archives the tables SER00, SER05, and OBJK. However, these tables are not deleted. You can archive these tables together with the serial number history ( Archiving Object PM_OBJLIST ).
Table AFPO is only available for refurbishment orders and is therefore only archived for these orders.
Note
The entries in table DRAD are archived by the write program and deleted by the deletion program.
If you want to assign documents to the maintenance order at header level and archive the document assignments, activate the business function
Simplified Management
of EAM Functions 2
(LOG_EAM_SIMPLICITY_2).
If you want to assign documents to the maintenance order at header and operation level in SAP GUI and archive the document assignments, activate the business function
Enterprise Asset Management Part 6
(LOG_EAM_CI_6).
Alternatively, you can activate the business function
EAM, Integration with SAP 3D Visual Enterprise
(LOG_EAM_VE_INT). By activating this business function, you activate the function
Assignment of Documents to Maintenance Orders
at header and operation level in SAP GUI and in SAP Web UI.
Implement SAP Note 1771336 as well.
By including the archiving classes (
P_ORDER
and
TEXT
), the following data is also archived:
Order header overall (table AUFK, AFKO)
Cost report
Settlement rule
Operations
Material components
Production resources/tools
Completion confirmations
Status of order header and operation
Long text for order header and operation
Purchase requisition for operation and components
Completion confirmation for operation and components
Goods movement
Note
It is possible for you to create a historical order parallel to your archiving session.
If you set the
Historical Orders
indicator on the initial screen for the archiving run, the deletion program deletes the order from the database of the ERP system and simultaneously creates a historical order in aggregated form on the database. The order number remains the same.
The following programs are delivered for the PM_ORDER:
Program |
Function |
RIARCORVS |
Initial Run |
RIARCORAS |
Write |
RIARCORDS |
Delete |
The write program supports the ADK interruption concept, enabling you to interrupt the write phase and continue it at a later point in time. For more information, see Interrupting and Continuing Archiving Sessions .
An update message is regularly output in the job log and in the dialog (status bar) both in the write run and in the deletion run.
See also: