SAP Note 112841 - Steps to Regenerate PMCO & PMIS files
Note Language: English Version: 7 Validity: Valid Since 25.08.2009
Summary
Symptom
Costs not updated correctly,
Other terms
PMCO PMIS RIPMCO00 RIPMS001 Rebuild
Reason and Prerequisites
Solution
Steps Needed to regenerate the PMCO and PMIS files.
You can start the reports RIPMCO00 and RIPMS001 in the following ways:
- use IMG path in customizing:
Logistics general
Logistics Information System
Logistics Data Warehouse
Data basis
Tools
Setup statistical data
Application-specific statistical set up
Perform setup - Plant Maintenance
(please see also online help for this item)
- or start the reports directly with menu path "System / Services /
Reporting" or transaction SA38
Attn:
The following is some helpful information regarding the RIPMCO00 report:
Please make sure note 335028 is implemented in your system before using
report RIPMCO00!!!
-> Test run
No update will be made in the PMCO file. Control list will be
created independent from setting for 'Create control list'.
-> Create control list
Control list will be created with planned and actual costs for
each order.
The Following is the Online help concerning the two reports:
In this step you can initialize the information structures of the Plant
Maintenance Information System.
The following reports are available for this purpose:
· RIPMCO00
This report is designed for the statistical setup of file PMCO (order
costs).
· RIPMS001
09.05.2010 Page 1 of 3
SAP Note 112841 - Steps to Regenerate PMCO & PMIS files
This report is designed for the statistical setup of the information
structures in Plant Maintenance.
The following events are taken into account:
- - Maintenance notification
- - Equipment
- - Functional location
- - PM order (historical and current orders)
The statistical setup of information structures is necessary in the
following situtaions:
- · if you have created new information structures
- · if you have changed the value categories
- · if you have changed the statistics currency
- · if you have upgraded from Release 2.2 to Release 3.0
If you have already created maintenance orders in the 2.2 system, you must
set up the PMCO file (cost view for maintenance orders). Use the report
"RIPMCO00" for this purpose. You need to start this report after you
upgrade from a 2.2 System to a 3.0 System. This report must be carried out
successfully before the information structures of the Plant Maintenance
Information System can be set up via the report "RIPMS001".
If you started with Release 3.0, you always need to start the report
"RIPMCO00" if you have changed the value categories in Customizing. You
then have to carry out the statistical setup of the information structures.
Caution
The file PMCO is the basis file for the information structures og Plant
Maintenance, therefore you absolutely must perform the statistical setupof
this file before you set up the information structures.
Standard settings
If you started with Release 3.0, the information structures will be
automatically and correctly set up by the update programs.
- · If you execute the report RIPMS001, the run name will be
automatically set.
The system will then fill in the field Name of run with the first two
letters of the user name and the current date.
Additional functions
In the Plant Maintenance Information System, the system automatically makes
a log after every completed Online run.
This log can be printed, but not saved.
Note
09.05.2010 Page 2 of 3
SAP Note 112841 - Steps to Regenerate PMCO & PMIS files
Further information can be found in the corresponding Release Information.
Header Data Released for Customer
Release Status: 25.08.2009 07:39:05
Released on:
Master Language: English
Priority:
Category: Recommendations/additional info
Primary Component
Consulting
Secondary Components:
PM-IS Information System
PM-WOC-MO Maintenance Orders
XX-PROJ-IMS-UPGR Application Specific Upgrade
Tools
The Note is release-independent
Related Notes
Number Short Text
996035 Estimated costs after changing the fiscal year variants
455495 RIPMS001: RIPMS001:character-like keys and ASCII/EBCDIC
352155 Too high actual costs in PMIS and PMCO
335028 PMCO restructure: New program version
310726 Reconfiguring of information structures
205073 Errors in order costs and when updating PMIS
204029 Errors in order costs and when updating PMIS
202476 Errors in order costs and when updating PMIS
186513 EMU: Termination with changeover of table PMCO
180047 Cost Distribution to Time Axis and in PMIS/SMIS
168960 Deactivate statistics update for migration
09.05.2010 Page 3 of 3