Hierarchy

⤷

⤷

IMG Activity
ID | COM_PRODUCT_OBJFAM | Define Object Families |
Transaction Code | S_AEC_66000636 | (empty) |
Created on | 20010412 | |
Customizing Attributes | COM_PRODUCT_OBJFAM | Define Object Families |
Customizing Activity | COM_PRODUCT_OBJFAM | Define Object Families |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | COM_PRODUCT_OBJFAM |
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:
- The monitor of a computer with the manufacturer serial number "xyz"
- Mr. Smith's washing machine at 25 George Street, London
Although the washing machine does not have a number, it is not likely to be confused with any other washing machine.
- A life insurance policy
- A building with an address
You can represent your objects in the system (for example, to describe the objects used in the services you provide).
Each object belongs to an Object Family. An 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.
The object family to which an object belongs cannot be changed, however, the categories to which it is assigned can be changed.
The steps you need to take to tailor objects to your requirements are described below. Links in the text take you directly to the relevant activities.
Note that a number of these steps are client-dependent. This may mean - depending on the settings in your system - that you will need to maintain the Customizing settings in various clients.
Objects are technically a particular form of a product. Therefore certain steps and settings need to be made in the product area to ensure consistency in the overall system.
Activities
- Define Object Family
These entries apply to all clients.
- Enter a four-character ID and a description for the object family.
- Assign the object family the product type Material (objects can only be created with this product type). This determines from which base hierarchy the object will have to be assigned a category.
- Define Fields
These settings apply to all clients.
In this step, you specify the fields you want to use to describe the objects.
For example, you create the attribute Gears for the object with the values 4 gears, 5 gears, and Automatic, and the attribute Air conditioning with the values Yes and No.To do this, choose Attribute.
- Define Groups of Fields (Set Types)
These settings apply to all clients.
A set type should group related fields together. The fields of a set type are shown in a subscreen (table) on the interface and processed as a unit in programs. - Choose Set Type.
- Assign the product type you specified for the object family (for example, Material).
- Do not set the Dependent on Distribution Chain indicator.
- Leave the Object Family field blank initially.
- Assign the attributes to the set type, but leave the ConfigRelevancy column blank.
- Include Set Types in API/BDOC Structures
The attributes are stored as data elements in the ABAP Dictionary and the set types as structures and tables. In this step you:
- Assign the correct package. Consult your system administrator as to which package should be used for the set type.
- Include the structures in the interface of the function modules used for maintaining products.
- Choose Attributes/Set Types -> Transport -> Include in Request.
- Enter the ID of the set type.
- Set the Create API Append indicator.
Note
You should only perform this step if you intend to transport the set types to another system. You do not generally require this step for test purposes unless you are testing the API interface.
- Create Categories for Object Families
This step is client-specific. It has to be carried out in every client in which the object family is used. To transport a hierarchy from one client to another, carry out the Customizing activity Transport Categories (under SAP Products -> Product Category).
Using the Maintain Categories and Hierarchies transaction (COMM_HIERARCHY), maintain the categories for the object family.
Also refer to the online documentation (Help -> SAP Library -> SAP NetWeaver -> Application Platform -> Cross-Application Services -> SAP - Product -> Concepts -> Categories and Hierarchies).
- Initialize Number Assignment
Choose Number Ranges for Product (Product Type Material.
In this step, you define the number ranges for external number assignment (only external numbers are supported for objects). For more information, see Define Number Ranges for Materials.
IMPORTANT
Be aware that you are maintaining an application table and not a Customizing table. You cannot transport this table between systems. - Reserve Set Types for an Object Family
These entries apply to all clients.
This step is optional. A set type can in principle be used for products and individual objects. However, if one of the fields in the set type contains data that is only relevant for an individual object, such as "mileage" or "next service", you can reserve this set type for individual objects. This means that the set type can only be used for individual objects in this object family and cannot be used for products. - Choose Set Type.
- Make an entry in the Object Family field.
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | COM_PRODUCT_OBJFAM | 0 | A4C0000261 | Central Part of Product Master |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
COMV_PR_OBJ_FAM | C - View cluster | SM34 | Define Object Family |
History
Last changed by/on | SAP | 20030228 |
SAP Release Created in | 30A |