Hierarchy
⤷ CRM-MSE (Application Component) Mobile Service
⤷ IWOC (Package) Application Development R/3 Work Order Cycle
Basic Data
Data Element | HERKZ |
Short Description | Origin Indicator for Notification |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | HERKZ | |
Data Type | CHAR | Character String |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
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 | OrigInd |
Medium | 15 | Origin Indic. |
Long | 20 | Origin Indicator |
Heading | 4 | OInd |
Documentation
Definition
Indicates the screen sequence control for a
Use
The screen sequence control is determined in the system for
- PM notifications
- malfunction reports
- activity reports
- maintenance requests
- Service notifications
- customer reports
- service reqests
- customer complaints
- notifications of defects to vendors
- internal problem notifications
If you define your own notification type, you must enter which of the notifications listed above is to be used for the screen sequence for your notification type. If for example your notification type is to contain the screens defined in the standard system for activity reports, enter the origin indicator for activity reports. In this way you can, for example, enter activity reports in two different plants which you can differentiate on the basis of the notification types.
Procedure
Examples
Dependencies
The following applies for quality notifications:
All notification types with the origin Complaint against a vendor are taken into account in the Complaints area for vendor evaluation, if the status caused externally is set after processing is complete.
History
Last changed by/on | SAP | 19991102 |
SAP Release Created in |