Hierarchy

⤷

⤷

Basic Data
Data Element | DEVREPLACE_DIALOG |
Short Description | Device Replacement (Dialog) Automatically Taken into Account |
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 | Dev.Repl. |
Medium | 15 | Dev.Repl.Dialog |
Long | 20 | Dev.Replacem.Dialog |
Heading | 1 | D |
Documentation
Use
This means that when you enter meter reading results, the system checks in the dialog (single entry), whether a device replacement exists. If a device replacement does exist, the system takes this into account and automatically allocates the meter reading result to the newly installed device.
Dependencies
If you do not select this field, the system does not check, for every reading, whether a device replacement exists. If this is the case, device replacement is only taken into account when entering meter reading results, if the meter reader entered the note with control function 05 (device replacement). If the meter reader does not enter this note, and the meter reading date is after the replacement, the system cannot allocate the meter reading result.
You receive an error message.
Example
Planned MR Date of Order Creation: 05.15.
Device Replacement: 05.17.
Meter Reading: 05.20.
The meter reader comes to the newly installed device. However the meter reading data refers to the old device.
- If you selected this field, the system recognizes that a device replacement has occurred and takes this into account when uploading the data.
- If did not select this field, the meter reader must enter an appropriate note so that the device replacement is taken into account.
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in | 464 |