Performance Profile
Definition
Master data that specifies the amount of planned operational use for a particular period (for example, operating hours per month for the period January to March). Performance profile details are planning-version dependent.
Use
You use performance profiles to determine the average performance of:
Maintenance objects without external reference.
Maintenance objects with external reference, if you want to use average performance data in SAP SCM, instead of the average performance data that is recorded in SAP R/3 for the corresponding equipment or functional location. This allows you to use different counter types, valid-from dates, and counter consumptions from those transferred from SAP R/3.
You define the performance profiles in the
Performance Profile
transaction and assign the performance profiles in the
Maintenance Object
transaction.
Structure
Performance profiles are structured as follows:
Field Name |
User Entry |
Meaning |
|---|---|---|
|
< Name of Profile > |
Unique name of profile. |
|
< Description of Profile > |
Meaningful description of profile. |
Field Name |
User Entry |
Meaning |
|---|---|---|
|
< Date > |
Date from which the profile comes into effect. |
|
Counter type |
Identifies what the counter measures. Use value help. You create the counter types in Customizing for
|
|
Internal, language-independent measurement unit format. |
|
|
< Quantity > |
Shows how much a maintenance object has been used over a certain past period. This is usually shown as a quantity, such as operating hours. The difference between the current counter reading and the previous counter reading is the current consumption of the object. This can be either an increasing or decreasing amount. |
|
Time unit |
Temporally defines a profile in units such as weeks, months, and so on. For example, a maintenance object has a performance of 300 operating hours per week. |