LinkedIn emplea cookies para mejorar la funcionalidad y el rendimiento de nuestro sitio web, así como para ofrecer publicidad relevante. Si continúas navegando por ese sitio web, aceptas el uso de cookies. Consulta nuestras Condiciones de uso y nuestra Política de privacidad para más información.
LinkedIn emplea cookies para mejorar la funcionalidad y el rendimiento de nuestro sitio web, así como para ofrecer publicidad relevante. Si continúas navegando por ese sitio web, aceptas el uso de cookies. Consulta nuestra Política de privacidad y nuestras Condiciones de uso para más información.
Installed Base Configuration -Ripunjay Singh RathaurIntroductionInstalled Base is created for Technical objects where services are needs to be done. Installed base stores thestructure 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.
Step by Step configuration for Installed Base1. Define Installed Base category and Installation Rules
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 CategorySAP delivers the partner determination procedure 00000032 as standard. It permits all partners without anyparticular rules and is assigned to the installed base categories 01 in the standard system. It can also be assigned toadditional installed base categories.
Customization related to Objects1. Define Object FamiliesAn 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 objectsinclude: - Monitor of a computer with the manufacturer serial number ‘abc’ - A life insurance policy - A building with an addressEach object belongs to an Object Family. Object family groups together the same types of object based on theproperties of the object.So the object family Bus includes all types of buses regardless of what they are used for (or example, as a schoolbus 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 turncan have different characteristics (set types and attributes). Both categories, however, have the same objectfamily.
Go to Assigned Attribute Tab and assign existing attribute or create as per your requirement.3. Assign Object families to Installed base categoriesDo not assign object families to an IBase category that is used in variant configuration.
4. Define Characteristics of Object FamiliesDifferent types of structure components are symbolized by icons in the display of an installed base structure (forexample, text item, and product).Objects in an installed base can be symbolized by different icons, depending on which object family an objectbelongs to.You assign an icon to an object family in this activity.