Infrastructure Planning Object Object for planning the infrastructural equipment of a force element with pieces of land and buildings.
You use an infrastructure planning object (IPO) to map a combination of buildings and/or land types . By assigning infrastructure planning objects to a force element, you define the authorized infrastructure of the force element, that is, the specific types of buildings and land required so that the organizational entity represented by the force element can carry out its tasks.
The multilevel structure of an infrastructure planning object enables you to map both a rough and detailed planning level.
The infrastructure planning object groups multiple building and/or land types in a typical combination . You map the individual building and land types using objects from the first and second planning levels of the infrastructure planning object.
At the first planning level (mandatory), an infrastructure planning object includes one or more objects that represent a specific building or land type.
At the second planning level (optional), each object of the initial planning level (building or land type) includes one or more objects for mapping subordinate building sections (rooms) or land sections (spaces) for differentiated mapping.
Note
To evaluate an infrastructure planning object in an authorized/actual comparison, you have to define at least the first planning level.
You can also use objects from the first or second planning levels as correction values for the authorized infrastructure.
You map infrastructure planning objects and their planning levels as a hierarchy consisting of
architectural objects
with functions of the
Flexible Real Estate Management
component. When doing do so, you can use the following
object types
and corresponding
relationships
between these object types (hierarchy of planning levels):
Planning Level |
Type |
Description |
Symbol |
Use |
|---|---|---|---|---|
IPO |
IPO0 |
IPO level 0 |
|
Represents the overall infrastructure planning object |
First IPO planning level |
IPO1 |
IPO level 1 main object buildings |
|
Represents the first planning level for buildings (assignment to IPO0) |
IPO2 |
IPO level 1 main object land |
|
Represents the first planning level for land (assignment to IPO0) |
|
Second IPO planning level |
IPO3 |
IPO level 2 subobject buildings |
|
Represents the second planning level for buildings: rooms (assignment to IPO1) |
IPO4 |
IPO level 2 subobject land |
|
Represents the second planning level for land: spaces (assignment to IPO2) |
These
object types
are defined in Customizing for
Flexible Real Estate Management
under
using the BC Set /ISDFPS/BC_RE_IPO_ARCH.
The assignment of object types to the
planning levels
(hierarchy) is defined in Customizing for
Defense Forces & Public Security
under
(using the BC Set /ISDFPS/BC_RE_IPO_DFPS) as well as in Customizing for
Flexible Real Estate Management
under
(using BC Set /ISDFPS/BC_RE_IPO_ARCH).
This specifies that architectural objects of types IPO1 and IPO2 (main objects) can be assigned to an architectural object of type IPO0. Subobjects of type IPO3 can be assigned to a main object of type IPO1, and subobjects of type IPO4 can be assigned to a main object of type IPO2.
Note
A main object or subobject can be assigned only to the subordinate object for which you created it. Assignment to multiple subordinate objects is not possible.
To display and edit the properties of infrastructure planning objects, use the
RE Navigator
application (transaction RE80) or the
Architectural Object
application (transaction REBDAO) of the
Flexible Real Estate Management
component.
For more information about the object properties of architectural objects as well as the applications listed, see SAP Library under .
The
Defense Forces & Public Security
component enhances these applications to include object type-specific views using the Customizing settings for
Flexible Real Estate Management
with the BC Sets /ISDFPS/BC_RE_IPO_BDT (tab pages) and /ISDFPS/BC_RE_RE80_OVERVIEWS (overview DFPS_IP_MC).
The following section describes only component-specific fields and how fields are used. The system uses these properties in the authorized/actual comparison for infrastructure .
Function (all IPO* object types)
On the
General Data
tab page, you define the
business
function
of the infrastructure planning object and the main object or subobject. You use this function in the authorized/actual comparison to compress values.
Note
The assignment of a function to objects of type IPO0 is for information purposes only and is not relevant for the authorized/actual comparison.
.
Common Usage (all IPO* object types)
On the
General Data
tab page, you specify whether the pieces of land, buildings, rooms, or spaces from the assigned force element are to be used
exclusively
and evaluated accordingly in the authorized/actual comparison. Marking an object as exclusive or non-exclusive is relevant for its measurements (including the measurement for the number) and fixtures and fittings.
The system evaluates exclusive and non-exclusive values (number, measurements, or fixtures and fittings) separately in the authorized/actual comparison.
Note
Objects of type IPO0 are identified for information purposes only and is not relevant for the authorized/actual comparison.
This property is not passed onto higher-level or subordinate objects.
Measurements (object types IPO1 to IPO4)
On the
Measurements
tab page, you define the following values using measurement types:
Geographical properties of the required pieces of land, buildings, spaces, or rooms
Note
Note that the measurement types used here must match those that you use in the usage view (actual infrastructure) for an authorized/actual comparison to be possible.
Number of required pieces of land, buildings, spaces, or rooms
When defining the internal object hierarchy of an infrastructure planning object, you define the number of required buildings, pieces of land, rooms, or spaces (IPO1 to IPO4) for each assignment using a corresponding measurement type of the same name (IPO1 to IPO4).
You define measurement types in Customizing under and specify whether object types are permitted by choosing .
You also assign the measurement types for the number to the object types in Customizing for
Defense Forces & Public Security
by choosing
(using BC Set /ISDFPS/BC_RE_IPO_ARCH).
This property is not passed onto higher-level or subordinate objects.
Fixt./Fittings Characteristics (object types IPO1 and IPO3)
On the
Fixt./Fittings Characteristics
tab page, you define the required
fixtures and fittings
of the pieces of land, buildings, spaces, or rooms using fixtures and fittings characteristics.
Note
Note that the fixtures and fittings characteristics used here have to match those that you use in the usage view (actual infrastructure) for an authorized/actual comparison to be possible.
You define fixtures and fittings characteristics in Customizing under and specify whether object types are permitted by choosing .
During the authorized/actual comparison, the system takes into account only those fixtures and fittings that fulfill the following conditions:
The
Number
indicator is set in Customizing for the fixtures and fittings characteristic.
The
Applicable
indicator is set on the
Fixt./Fittings Characteristics
tab page.
This property is not passed onto higher-level or subordinate objects.
You can use object type-specific overviews on the
Overviews
tab page
(for a
ll IPO* object types)
:
IPO – Measurements/Fixtures and Fittings
(
DFPS_IP_MC
)
Measurements and fixtures and fittings of the object, as well as subordinate objects
Force Element Assignments
(DFPS_IP_SE):
Force elements to which the object is assigned as authorized infrastructure or a correction factor
For information about mapping, see also Data Structure of the Infrastructure Planning Object .