Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CUS-TOL-NAV (Application Component) Business Navigator⤷
SDFM (Package) Maintenance of Reference Structure and Processes
Basic Data
| Data Element | OT |
| Short Description | Owner type ('O'=object definition) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
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 | x |
| Medium | 15 | x |
| Long | 20 | x |
| Heading | 0 |
Supplementary Documentation - OTEIL 0001
Use
If you can determine more precisely where the damage determined occurred at the object, then enter the object component affected in this field.
Procedure
To do this, press the F4-key on the field. You obtain a list of object components from the table of catalog types. Select the object component at which the damage occurred.
Examples
Dependencies
If you have already entered an equipment in the PM notification, the selection list only contains the object components of the catalog allocated to the equipment.
If you have not entered an equipment in the PM notification, the selection list contains the object components of the catalog types which were defined centrally for the notification type.
Supplementary Documentation - OTEIL 0002
Procedure
If you can localize the defect or problem, enter the defect location or the affected object part in this field.
Use the possible entries help to call up a list of defect locations or object parts from the table of catalog types. Then select the defect location or object part where the defect or problem occurred.
Dependencies
If you specified a material in the quality notification, the selection list only contains the object parts or defect locations in the catalog that are assigned to the material.
If you did not specify a material in the quality notification, the selection list contains the object parts or defect locations in the catalogs that were centrally defined for the quality notification type.
Supplementary Documentation - OTEIL 0003
Definition
Key that identifies the location of the deviation in more detail.
Procedure
If you can localize the defect or the location of the deviation, enter the defect location in this field.
Use the input help to call up a list of defect locations from the table of catalog types. From this list, choose the defect location, where the deviation has occurred.
Supplementary Documentation - OTGRP 0001
Use
Key for the code group that groups the codes for the location of the variance (defect location).
For the coding of the defect location, use the catalog for catalog type Object parts/>.
Dependencies
Example
Supplementary Documentation - OTYPE 0004
Use
Dependencies
Enter all object types for which this attribute is to be offered for maintenance within this scenario.
Note, that infotype 1222 must be permitted for this object type.
Example
Supplementary Documentation - OTYPE 0100
Use
Enter the type abbreviation of the organizational unit whose task authority you wish to display.
Dependencies
Example
Supplementary Documentation - OTYPE 0560
Use
Use this field to identify the type of object you are relating with a position, for example, a person (if you work with master data), or user.
To complete the field either:
- type in the appropriate code, or
- request a list of object types and make a selection by either:
. Pressing F4, or
. Clicking on the down arrow
Supplementary Documentation - OTYPE 1000
Use
RHINTE00: This parameter specifies with which object type the cost centers are to be linked.
Procedure
Examples
Dependencies
The validity of the entry is compared against the table 778O (object types) and the table 777E (allowed relationships).
Supplementary Documentation - OTYPE 1001
Use
This field and the Object ID field are only used when you want to refer to a third element (another object) involved in a relationship.
For example, if you are working in Organization and Planning and you are relating tasks with a position, you may want to create a link with the job that a position is based on.
Or, if you are relating qualifications with a person, you may wish to refer to the position related to the person (so that you can compare the person's qualifications with the position requirements).
Procedure
Use this field to identify the type of object you wish to reference. To do so:
- type in the appropriate code, or
- request a list of types of objects and make a selection by:
. pressing F4, or
. clicking on the down arrow
Supplementary Documentation - OTYPE 1002
Use
Use this field to identify the type of object you want to work with. To do so:
- type in the appropriate code, or
- request a list of object types and make a selection by either:
. pressing F4, or
. clicking on the down arrow
Supplementary Documentation - OTYPE 1003
Use
Use these fields only when you request a structural evaluation for this report (using the Set structure conditions option or the Structural parameters fields).
When a structural evaluation is carried out, it is possible that several different types of objects will be extracted for the report.
These fields allow you to select which objects should be documented in your report.
To do so:
- Name a single type of object in the From field, for example, S. The report only documents the specified object.
- Name a list of types of objects, for example, S and O. To list more than two types of objects, click on the right direction arrow. A window appears that allows you to enter a list.
Supplementary Documentation - OTYPE 2000
Use
Use this field, together with the Object field, to identify which object should be used as the "root" object. The root object is the object the system uses as a starting point, when it traces the structure, to determine which objects meet the conditions set. The system checks from the root object, down through the structure.
Procedure
Use this field to identify the type of object the root object is.
To do so:
- type in the appropriate abbreviation, or
- request a list of object types and make a selection by:
. pressing F4, or
. clicking on the down arrow
NOTE: The root object may be different from the check object. For example, the check object may be positions, but the root object may be an organizational unit.
Supplementary Documentation - OTYPE 7001
Use
Company type
Object type which is allowed as a company type in Room Reservation Management, that is, whose object can be entered as a company and can be booked for events.
Procedure
Examples
Dependencies
Supplementary Documentation - OTYPE 7002
Use
Attendee type
If individual attendees can also be specified for a company of the entered company type with their names, the object type of these individual attendees is to be entered into this field.
Procedure
Examples
Dependencies
Supplementary Documentation - OTYPE 7003
Use
Attendee type
The specifications in this table apply in each case to all attendees of a category. This means that the link is carried out always identically for all company types in the table T77R3 with which this attendee type is set.
Procedure
Examples
Dependencies
Supplementary Documentation - OTYPE 7004
Use
Object type of the room
Only used here in the program and is irrelevant for the user.
Procedure
Examples
Dependencies
Supplementary Documentation - OTYPE 7005
Use
Object type of the canteen
Only used in the program and is irrelevant for the user.
Procedure
Examples
Dependencies
Supplementary Documentation - OTYPE 7006
Use
Object type of the event
Only used in the program and is irrelevant for the user.
Procedure
Examples
Dependencies
Supplementary Documentation - OTYPE 7007
Use on the initial screen of the transaction (PP30)
Object type of the organizer of the business event
The object type of the organizer of the event can be specified here. This object type must be marked in the table T77R3 as a valid organizer since the input value is checked against this table.
The entry of an organizer only affects the search for business events, thus for displaying, changing, deleting and firmly booking, as well as the search for business events of an organizer.
Use when displaying, changing, deleting, creating and firmly booking an event
Object type of the organizer of the business event
The object type of the organizer of the business event must be specified here. This object type must be marked in the table T77R3 as a valid organizer since the input value is checked against this table.
Supplementary Documentation - OTYPE 7008
Use on the initial screen of the transaction (PP30)
Object type of the attending company
The object type of an attending company of a business event can be specified here. This object type must be contained in the table T77R3 as a company since the input value is checked against this table.
The entry of a company only affects the search for business events of a company and when creating an event.
Use when displaying, changing, deleting, creating and firmly booking a business event
Object type of the attending company
The object type of an attending company of the event must be specified here. This object type must be contained in the table T77R3 as a company since the input value is compared against this table.
Supplementary Documentation - OTYPE 7009
Use
The company object type must be marked as such in the table T77R3, that is, the object type must be contained in the table. If no attendee type is specified to do this in the table T77R3, the company is chosen from the matchcode file M_PLOME, otherwise, the input parameters of this report are transferred to the report RHRAUM40.
Procedure
Examples
Dependencies
Supplementary Documentation - OTYPE 7010
Use
The attendee type results explicitly from the attending company specified in the previous screen. In table T77R3, an object type must be specified for every object type for attending companies for attending individuals.
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 19961104 |
| SAP Release Created in |
