Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U-IDE (Application Component) Intercompany Data Exchange⤷
EECC_EDI (Package) IS-U: Deregulation
Basic Data
| Data Element | E_NOSCENARIO |
| Short Description | Service Type Not Relevant for Supply Scenario |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | KENNZX | |
| 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 | Not Rel.SS |
| Medium | 15 | Not Rel. for SS |
| Long | 20 | Not Rel. f. SuppScen |
| Heading | 6 | N.R.SS |
Documentation
Definition
Indicator for service types that are not relevant for the supply scenario.
Use
Set this indicator for service types that are not relevant for determining the supply situation.
When you define a supply scenario you can also use these service types. The existence of a point of delivery service or a contract for the point of delivery is optional for this service type.
Dependencies
Example
For points of delivery with automated meter reading (AMR), the AMR system in question is defined as the point of delivery service. This allows data to be exchanged automatically with the AMR system.
The existence of an automated meter reading for a point of delivery has no effect on its actual supply situation. This is essentially determined using the grid usage and supply service types. Therefore, the Automated Meter Reading service type is marked as Not Relevant for the supply scenario.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in | 472 |
