Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U-DM-MR (Application Component) Meter Reading⤷
EE16 (Package) IS-U: Meter Reading Order Creation
Basic Data
| Data Element | I_NOTE |
| Short Description | Dynamic note to field service |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | G_NOTE | |
| 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 | Note |
| Medium | 15 | Dynamic note |
| Long | 20 | Dynamic note |
| Heading | 3 | DN |
Documentation
Definition
This field contains the key for dynamic notes to field service. The notes are analyzed at runtime by the relevant print or download program. If the contents of the note apply to a certain object, then the note is either output on the relevant form or written to the download file for mobile data entry.
The table is a control table in which SAP and the customer each have their own key areas. The key of the notes provided by SAP begin with 0.
You can activate the notes by setting the output indicator. The priority number specifies the sort sequence of several notes. The address data can be used to determine valid recipient groups and forms for the notes.
The following note keys have been defined:
01 Installation & manually blocked from meter reading
The installation was manually blocked from meter reading because the meter reading blocking reason was set.
02 Installation &1 inactive since &2
No contract is allocated to the installation when meter reading takes place. If a contract has never been allocated to the installation, the date corresponds to the installation date of the first device. Otherwise, the date is the same as the last move-out date.
03 Device &1 disconnected since &2
The device was disconnected using the transaction Disconnect.
04 Device &1 read by customer &2 times
The device was read n times in succession by the customer.
05 Device &1 estimated &2 times
The meter reading results of the device were estimated n times in succession.
06 Device &1 not read &2 times
The device was not read by the utility company n times in succession. This means that the meter reading results were either estimated or taken by the customer.
07 Previous meter reading of device & implausible
The most recent meter reading result of the device is implausible.
08 Meter reading of device & already entered
A meter reading result was already entered on the scheduled meter reading date for the device.
09 Customer reading already entered for device &
A meter reading result reported by the customer was already entered on the scheduled meter reading date.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
