Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
MRM (Package) Appl.development R/3 decentralized invoice verification
Basic Data
| Data Element | TYP |
| Short Description | Item category for tree structure - ENJOY |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TYP | |
| 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 | 1 | C |
| Medium | 3 | Cat |
| Long | 0 | |
| Heading | 0 |
Supplementary Documentation - TYPTX 0000
Examples
Variant BOM - A number of similar products are described
in one BOM.
Multiple BOM - A product can be manufactured using different
manufacturing processes and from different
components and component quantities, ie. a
product has a number of alternative BOMs.
Supplementary Documentation - TYP_ADWP_PACK_PERMISSION3333
Use
Access permission.
Dependencies
Example
Supplementary Documentation - TYP_ID 3000
Use
All business events of this business event type which are displayed
in the specified language in the specified period, are listed.
The required business event type can also be determined by a
superordinate business event group. Using the function "Selection
via business event group" it is possible to enter a business event
group and afterwards to list all the business event types subordinate
to this group (business event group / business event type hierarchy).
In this list
- the business events offered for a business event type can be output
via function key
- a business event type can be chosen for transfer to the entry screen of the transaction.
Procedure
Example
Dependencies
Supplementary Documentation - TYP_ID 7000
Use
During bookings, cancellations and rebookings (transactions PP12, PP13 and PP19):
The field is both an input field as well as an output field, depending on how the user enters the required business event:
- by specifying the business event type ID, the business event language and the required start date
-> The business event type ID is an input field
- by direct specification of a business event ID
-> If the business even ID is valid, the respective business event type ID of the system is shown
-> Business event type ID is output field
For pre-bookings (Transaction PP15):
Object ID of the business event type for which the attendee should be prebooked.
Procedure
Example
Dependencies
Supplementary Documentation - TYP_ID_SRK1000
Use
The object ID is used as a distinguishing criterion for objects of the same type.
Within HR Planning object IDs should not be "mnemonic".
When creating a business event, the specification of a respective
business event type is absolutely necessary for technical reasons.
If the business event to be created cannot be usefully allocated
to a business event type or the user does not want to manage any
business event types, he must at least create a meaningless "
"collective business event type" to which he links each of
his training business events.
The business event type ID can also be determined using the search function. For this the user can enter a search string directly into this field (masked if necessary).
The entry * supplies a list of all the available business events
types; By entering *HR* a list of all the business event types which
contain the string HR in the identification code or in the long text is displayed.
Procedure
Example
Dependencies
Supplementary Documentation - TYP_ID_SRK3000
Use
The object ID is used as a distinguishing criterion for objects of the same type.
Within HR Planning object IDs should not be mnemonic.
All business events of this business event type that are displayed in the entered language and in the entered period are listed.
The required business event type can also be determined by a
superordinate business event group. Using the function "Selection
via business event group", it is possible to enter a business event
group and to list all the business event types subordinate to this group afterwards (business event group/business event type hierarchy).
In this list
- the business event offer for a business event type can be output
using the function key
- a business event type can be chosen for transferring the transaction to the entry screen.
The business event type ID can also be determined using the search
function. To do this, the user can enter a search string directly into this field (masked if necessary).
The entry * provides a list of all the available business event
types; By entering *HR*, a list of all the business event types are
displayed which contain the string HR in the identification code or in the long text.
Procedure
Example
Dependencies
Supplementary Documentation - TYP_ID_SRK7000
Use
The object ID is used as a distinguishing criterion for objects of the same type.
Within HR Planning, object IDs should not be "mnenomic".
During bookings, cancellations and rebookings (Transactions PP12, PP13 and PP19):
The field is both an input and an output field, depending on how the user enters the required business event:
- by specifying the business event type ID, the business event
language and the required start date
-> business event type ID is input field
- by direct specification of a business event ID
-> If it is a valid business event ID, the respective business
event type ID of the system is shown
-> business event type ID is output field
During pre-bookings (Transaction PP15):
Object ID of the business event type, on which the attendee should be prebooked.
The business event type ID can also be determined using the search
function. To do this the user can enter a search string directly into this field (masked if necessary).
The entry * supplies a list of all the available business event
types; by entering *HR*, a list of all the business event types which
contain the string RP in the identification code or in the long text is displayed.
Procedure
Example
Dependencies
Supplementary Documentation - TYP_ID_SRK8000
Use
The object ID is used as a distinguishing criterion for objects of the same type.
Within HR planning, object IDs should not be "mnemonic".
During bookings, cancellations and rebookings (Transactions PP12, PP13 and PP19):
The field is both an input and an output field, depending on how the user enters the required business event:
- by specifying the business event type ID, the business event language and the required start date
-> business event type ID is input field
- by direct specification of a business event ID
-> If the business event ID is valid, the respective business
event type ID of the system is shown
-> business event type ID is output field
For pre-bookings (Transaction PP15):
Object ID of the business event type to which the attendee
should be prebooked.
The business event type ID can also be determined using the search
function. To do this the user can enter a search string directly into this field (masked if necessary).
The entry * provides a list of all the available business event
types; By entering *HR*, a list of all the business event types is
displayed which contains the string HR in the identification code or in the long text.
By entering '+' the business event type can be transferred from
the line directly above.
Procedure
Example
Dependencies
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
