Note
See the following video to learn more about the various data transfer options when creating a functional location hierarchy:Data Origin
Data Origin
For reference functional locations and functional locations, you can display the origin of the data in the master data fields. There are two different display options available, including the following:
- Individual display for an individual field
- Overview display
For reference functional locations and functional locations, you can determine where entered data needs to originate for the individual master data fields. For reference functional locations, you can specify whether the data needs to originate from a superior location in the structure or needs to be maintained individually for the master record. For functional locations, you can specify whether data needs to originate from a superior location in the structure or reference functional location, or whether it needs to be maintained individually for the master record.
For pieces of equipment, there's an overview display (list of data origin) for each tab page, but there's no field-based display or change option.
Mass Changes
Mass Changes and Data Origin
- Fields with no specified data origin are changed for all selected objects.
- Fields with a specified data origin are changed if it is set to Maintained Individually.
When you perform a mass change, note the following points regarding data origin:
- Fields for which no data origin has been specified (for example, Description) are changed for all of the selected objects.
- Fields for which a data origin has been specified are only changed if the data origin is set to Maintained Individually. If the data origin is Functional Location or Superordinate (Superior) Equipment (for equipment) or Reference Location or Functional Location (for functional locations), then the mass change is not performed.
Note
Inheritance Breaks
- When you perform a mass change, all of the technical objects that are under the selected technical object in the hierarchy are also changed. If a large number of objects have to be processed, you may experience lock table overflow. Resulting inheritance breaks can be processed using the transaction code IL21.
- If there's an inheritance break in an object before you perform a mass change, this inheritance break is repaired during the mass change. It's also repaired for the other objects under the same superior object.
- If inheritance breaks are repaired, the message log contains a general message to this effect. It does not contain messages for each individually repaired object. This is to avoid cluttering the message log with information that's not related to the mass changes function.