http://help.sap.com/saphelp_crm700_ehp02/helpdata/en/4c/05fc4a49a0404be10000000a15822b/content.htm Created on May 17, 2014 The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal. Note This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included. 2014 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. Table of content PUBLIC 2014 SAP AG or an SAP affiliate company. All rights reserved. Page 1 of 4 Table of content 1 Installed Base Components 1.1 Objects in Installed Bases PUBLIC 2014 SAP AG or an SAP affiliate company. All rights reserved. Page 2 of 4 1 Installed Base Components
Individual elements of an installed base at the customer site that contain service-relevant information and can be referred to in business processes. All components for an installed base are arranged in a structure. An object becomes a component of this installed base by being included in an installed base structure. You can assign additional objects to each installed base component. In this way, an installed base can be organized hierarchically and on multiple levels. Structure An installed base component has the following optional parts: An identifier (ID) A description A link to involved parties and organizations, and a link to an address A link to warranties Qualification requirements for the service employee Counters and counter readings In addition, an installed base component always has a specific component type. The following component types are possible: Product You can assign an existing product to an installed base as a component. General information is displayed for this product. Text You can assign a text component to an installed base. In the text component, you can manually define any short text you like. Installed base You can assign an existing installed base to another installed base as a component. Note You can incorporate one installed base into another installed base as a component (a reference is created to the incorporated installed base). You can use this approach, for example, to group all installed bases for a customer under a new, higher-level installed base. Object You can assign an object to an installed base as a component. An object contains data that uniquely identifies the object. For more information about objects, see Objects in Installed Bases. Components can be arranged hierarchically below one other in substructures or they can be incorporated individually into the installed base. 1.1 Objects in Installed Bases
Enable you to uniquely identify specific individual objects and to track them in business processes. They enable you to manage specific information that is valid for a certain object and support the mapping of business processes that require a unique reference to a certain object (such as a service contract for an object). Objects complete the existing product options. The product contains general information about the goods or services that it describes. However, it cannot provide specific details about the objects that could possibly exist for the product. The object contains individual data that is valid for exactly one object, such as location and identification number. You can also use objects to map relevant business environment objects that are not directly objects of service processes or sales processes (such as buildings). Examples of objects: A computer monitor with the manufacturers serial number 123xyz Mr. Smiths washing machine at 109 Fell Street in San Francisco. Although this washing machine does not have a number, it would be practically impossible to confuse it with another washing machine. A life insurance policy, which can be identified by its unique policy number A building with an address Each object belongs to an object family (such as household appliances or software licenses). Settings at object family level define which fields you can maintain for the objects. All other object settings are also made at object family level. For more information, see Objects.
To use the installed base component Object , you have made settings in Customizing for Customer Relationship Management under Master Data Installed Base Objects/Object Family . An object is created as follows: By creating a new entry under Object Components For more information, see Working with Objects. By creating and installing an installed base component with the type Object in an installed base. This installed base component is then an object. By replicating equipment from SAP For more information, see Replication of Equipment Between SAP CRM and SAP ECC. It is a prerequisite that the following occurs in Customizing: 1. Installed base categories have been created. 2. Object families have been created. 3. The object families that can be used with each installed base category have been defined. 4. Set types have been defined for each object family. PUBLIC 2014 SAP AG or an SAP affiliate company. All rights reserved. Page 3 of 4 Note For more information, see Customizing for Customer Relationship Management under Master Data Installed Base Objects/Object Family . Note By assigning an object as component type Object in an installed base structure, it is "created" as a new object in the installed base. However, the system does not automatically assign it an ID. This means that you allocate the object ID manually during assignment; this assignment is not made internally by the system. Therefore, check which IDs you want to allocate to your objects before assignment. Entry of an object ID is mandatory. The description, which you can assign in addition, is displayed in the structure overview. Just as for the other installed base components, you can also assign the parties and organizations involved and address data to the object, and it is integrated in service processes. Example You define an installed base category Custom Kitchen in Customizing and assign the object families Kitchen Appliances (Electric) and Kitchen Cabinets to this installed base category. You create an installed base of the category Custom Kitchen in installed base management. The refrigerator "Kitchenette 1007C", with the manufacturer's serial number "K1007 C-2000-152-fgt", should be installed as an object in this installed base and become a reference object for service processes. You assign an installed base component of type Object to the structure of the installed base, by creating a new object in the Object Components screen area: 1. Choose the object family Kitchen Appliances (Electric) . 2. Choose the Category ID . 3. Enter Object ID K1007C-2000-152-fgt. 4. In the Description field, enter Refrigerator Kitchenette 1007C. Finally, confirm your entries so that the components appear in the structure with the description. PUBLIC 2014 SAP AG or an SAP affiliate company. All rights reserved. Page 4 of 4