Hierarchy

⤷

⤷

IMG Activity
ID | OLI0IMRCCUST | Make System Settings for Measuring Points and Measurement Documents |
Transaction Code | S_AL0_96000746 | (empty) |
Created on | 20020121 | |
Customizing Attributes | OLI0IMRCCUST | Make System Settings for Measuring Points and Measurement Documents |
Customizing Activity | OLI0IMRCCUST | Make System Settings for Measuring Points and Measurement Documents |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | OLI0IMRCCUST |
In this IMG activity you can make global system settings for measuring points, counters and measurement documents. At the moment there is just one system setting in this IMG activity:
- Generation of interval documents for the counter reading transfer
This concerns an optional activity that is only required in rare cases. You can also make the system settings at a later date.
Example
A commercial aircraft is mapped in the SAP system as a hierarchical structure of technical objects (functional locations and equipment). It contains approx. 2500 pieces of equipment, which are individually maintained using a maintenance plans based on counter readings. The same two counters are assigned to every piece of equipment:
- Flight hours
- Number of starts and landings
When using the counter reading transfer, it suffices to enter the counter readings just once for each aircraft (for each tail number). The system then calculates the difference from the last entry and automatically communicates this difference (and correspondingly the object structure) to all the lower-level functional locations and pieces of equipment.
This simple counter reading transfer is directly activated at the receiving measuring points/counters. You do not need any special system setting for this.
Depending on the frequency of the entries, each aircraft has a daily tally of 5000 or more measuring documents. For a normal stock of 50 to 500 aircraft this gives rise to a mass of documents that can barely (or not at all) be managed by the current database. The high volume of documents is because the counter reading transfer for every counter reading at the highest level generates a single document for every counter at the lower levels.
Use
Because only the most recent counter reading is relevant for the maintenance plan scheduling, an option was created to accumulate the counter readings from the lower levels into interval documents. This means that the same measurement document is used as long as the equipment is installed at the same functional location or main equipment. Thus there is only one measurement document for each installation interval of a piece of equipment. This gives rise to the name "interval document".
As regards the individual measuring point/counter, this global system setting only has one default character. You can further set individual measuring points/counters such that the counter reading transfers from them are mapped in single documents.
Requirements
If you have already used the simple counter reading transfer before Release 4.6, please see SAP note 428786.
Otherwise you can activate the interval documents at any time.
Resetting the system settings for interval documents is quite difficult during operations: Because the system setting has to be considered for the performance optimization of many programs, it can only be reset after all the interval documents have been archived and the counter reading transfer to all measuring points/counters has been reset to single documents.
Using interval documents gives rise to the following restrictions:
- The standard list for measurement documents (transaction IK17) can no longer display detailed single values for lower-level measuring points / counters, as there are no more single documents. This also applies to the corresponding graphics.
However the system can list the corresponding source documents for each interval document, and it can calculate the virtual counter reading for a particular measuring point/counter for any reference time point. - Archiving the measurement documents must take place on uniform key days system-wide. Before archiving, the interval documents must be split usint program RIARCMR1 for the respective key day. For further information, see SAP note 431536.
- If you use the customer exit IMRC0001 or the corresponding Business Transaction Event PM000040_E, you must, if necessary, adapt your implementation to the logic of the interval documents.
Standard settings
The interval documents are not activated in the standard system.
Because of the limitations outlined above, you should only activate this option, if you are forced to by the size of your database.
Activities
Activate the system setting "Transfer-generated interval documents".
If, at the time of activation, measuring points/counters already exist in your system, then you can use programm RIMRCINT to convert these to interval documents. A merging of pre-existing single documents into interval documents is neither necessary nor intended.
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
Mandatory / Optional | 3 | Nonrequired activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | OLI0IMRCCUST | 0 | ALR0000122 O | |
SIMG | OLI0IMRCCUST | 1 | HLA0001591 | Measuring Points and Counters |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
IMRCCUST | S - Table (with text table) | SM30 |
History
Last changed by/on | SAP | 20020121 |
SAP Release Created in | 470 |