Hierarchy
IS-OIL (Software Component) IS-OIL⤷
IS-OIL-DS-BDR (Application Component) Bulk Distribution Requirements Planning⤷
OII (Package) BDRP Bulk Distribution Requirement Planning
Basic Data
| Data Element | OII_SOCTYP |
| Short Description | SOC: Storage object type |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | OII_SOCTYP | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table | OIISOCTYP |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | SO type |
| Medium | 15 | Stor.obj.type |
| Long | 20 | Storage object type |
| Heading | 10 | SO type |
Documentation
Definition
The storage object type is used to assign a standard set of storage object characteristics to more than one storage object.
Procedure
If you are referencing the tank type ID, enter the type ID of the tank (or other storage object) that you are defining in this field. From this point the system will propose characteristics from the set of storage object characteristics which have previously been defined for the specified tank type. You can overwrite these proposals wherever specific characteristics of the storage object differ from those defined for the tank type.
If you are creating a tank type, enter the ID of the tank type in this field and proceed as for the creation of any storage object characteristic set.
Examples
A company always installs one of four specific types of tank at all its delivery sites. The company considers that all permanent characteristics of a storage object are the same as defined for the tank type assigned to that storage object (small fluctuations due to manufacturing processes are ignored). These characteristics are therefore defined at type level and 'inherited' at the individual tank level. For legal reasons, the company must strap its tanks individually. The strap characteristics are therefore defined at the individual tank storage object level.
Dependencies
The possibility of defining a tank type ID is dependent on the access mode by which the storage object characteristic document is accessed.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
