Installed base is used to store product structure and hierarchy for services. It can contain different component types like products, texts, other installed bases, and objects assigned to a component. Customizations include defining object families and categories, maintaining set types and attributes, and assigning object families and characteristics to installed base categories. The configuration involves defining installed base categories and rules, activating partner and address inheritance, and assigning a partner determination procedure.

1. Installed Base Configuration
-Ripunjay Singh Rathaur
Introduction
Installed Base is created for Technical objects where services are needs to be done. Installed base stores the
structure or hierarchy of the product. You can see an example below:
We can use different types of components within Installed bases:
• Product Components
• Text Components
- Text components can also be used to structure an Ibase
• An Ibase as a component of another Ibase
• Objects
An object can only be assigned to one installed base component; therefore objects may not be copied.
• Structure Gap
Are used to keep knowledge about the characteristic and a place in a structure of an Ibase component,
even if the component is dismantled for exchange, repair or maintenance.
• Customer-specific component types
- Customer-specific component types are, like, cars, washing machines, telephones, and so on. These
can be grouped in object families.
- An object family can be assigned to a multiple categories.
• We can mix all component types in any way within one structure.

2. Installed base Relationship

3. Step by Step configuration for Installed Base
1. Define Installed Base category and Installation Rules

4. 2. Activate Partner and Address Inheritance
The Inheritance of partners and addresses is a logical rather than a physical inheritance.
3. Assign Partner Determination Procedure to Installed Base Category
SAP delivers the partner determination procedure 00000032 as standard. It permits all partners without any
particular rules and is assigned to the installed base categories 01 in the standard system. It can also be assigned to
additional installed base categories.

5. Customization related to Objects
1. Define Object Families
An object used is in our daily environment and is a distinct single unit which can be uniquely identified.
An object is generally identified by a number or a fixed relationship or description (short text). Examples of objects
include:
- Monitor of a computer with the manufacturer serial number ‘abc’
- A life insurance policy
- A building with an address
Each object belongs to an Object Family. Object family groups together the same types of object based on the
properties of the object.
So the object family Bus includes all types of buses regardless of what they are used for (or example, as a school
bus or for public transport or ownership (leased, rented, or privately owned).
To distinguish between a public and a private bus, for example, you can create different categories, which in turn
can have different characteristics (set types and attributes). Both categories, however, have the same object
family.

7. 2. Maintain Settype and Attributes

11. Go to Assigned Attribute Tab and assign existing attribute or create as per your requirement.
3. Assign Object families to Installed base categories
Do not assign object families to an IBase category that is used in variant configuration.

12. 4. Define Characteristics of Object Families
Different types of structure components are symbolized by icons in the display of an installed base structure (for
example, text item, and product).
Objects in an installed base can be symbolized by different icons, depending on which object family an object
belongs to.
You assign an icon to an object family in this activity.