Hierarchy

⤷

⤷

IMG Activity
ID | /AIN/TOBJ_CAT_V | Define Physical Object Categories |
Transaction Code | /AIN/79000015 | (empty) |
Created on | 20060828 | |
Customizing Attributes | /AIN/TOBJ_CAT_V | Maintenance of Physical Object Categories |
Customizing Activity | /AIN/TOBJ_CAT_V | Define Physical Object Categories |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /AIN/TOBJ_CAT_V |
Use
In this IMG activity you define categories for classifying physical objects. The blank category settings are applied to all objects w/o category.
Physical object categories allow you to model different types of real world objects such as equipment, kanban, and returnable containers. For each physical object category you define category specific attributes. A physical object can only belong to one physical object category that it retains throughout its life cycle.
- You assign a set of attributes to a given physical object category by creating and assigning a table to that category. SAP Auto-ID Infrastructure supports attributes that are not defined as category-specific attributes and those attributes are stored in the current object context table. For example, the physical object category machine has attributes such as operating status (normal, out-of-order) and horsepower (150) that are defined in the current object context table rather than in a physical-object-category-specific table.
- You assign a set of quantity related characteristics to a given physical object category by creating and assigning a data element set to that category (Auto-ID Infrastructure -> Basic Settings -> Data Profile Settings -> Maintain Element Sets and Attributes). This element set contains the names of characteristics that are used for quantity aggregation. Those quantities are used to match against document line items. New characteristics can directly be passed by the RFID reader as physical object context and are matched against the document line item context. See also BADI Auto-ID Infrastructure -> Business Add-Ins (BAdIs) -> BAdIs for Document-Related Tasks -> BAdI: Generate Object Quantity for Aggregation.
Requirements
For each physical object category, you use transaction SE11 to define an Object Category Definition Table to contain the physical-object-category-specific attributes. The first two fields in that table must be the following:
- CLIENT (MANDT)
- OBJ_GUID (RAW16)
Standard settings
SAP delivers default object category 'blank' with the following settings:
- Object Category Description: Default
- Object Category Definition Table: /AIN/DM_OBJ_ATTR
- Quantity-Related Characteristic Set: SAP_POBJ_QCHAR_SET
Activities
To define a new physical object category, perform the following steps:
- Choose New Entries.
- Enter a two-character code that identifies your physical object category.
- Enter a description for your physical object category.
- Enter the name of the appropriate Object Category Definition Table .
Example
You might wish to create a physical object category for machines. In this case, your entries might look something like this:
- Object Category: Z1
- Object Category Description: Machine
- Object Category Definition Table: Z_MACHINE_DEF. The table has the following fields:
- CLIENT
- OBJ_GUID
- OP_STATUS
- POWER
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-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 | /AIN/TOBJ_CAT_V | 0 | /AIN/R4D0000002 | Application |
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 |
/AIN/TOBJ_CAT_V | V - View | SM30 |
History
Last changed by/on | SAP | 20070221 |
SAP Release Created in | 600 |