SAP ABAP Data Element SCENE (Scenario of Meter reading Activities on Transaction Date)
Hierarchy
☛
IS-UT (Software Component) SAP Utilities/Telecommunication
⤷
IS-U-BI (Application Component) Contract Billing
⤷
EE20_JBP (Package) IS-U: Japanese Billing Preriod
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U-BI (Application Component) Contract Billing⤷
EE20_JBP (Package) IS-U: Japanese Billing Preriod
Basic Data
| Data Element | SCENE |
| Short Description | Scenario of Meter reading Activities on Transaction Date |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SCENE | |
| Data Type | NUMC | Character string with only digits |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| 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 | MR Scen. |
| Medium | 15 | MR Scenario |
| Long | 20 | Meter Reading Scen. |
| Heading | 8 | MR Scen. |
Documentation
Definition
Unique numbering for a special scenario of meter reading activities that are executed on the same transaction date.
Scenarion Example:
A device replacement on Jan 31,2002 at 10:00. and a final meter reading on Feb. 31, 2002 at 14:00.
A scenario normally describes a conflict where the agent has to determine how meter reading dates are stored and interpreted in billing.
In the example above, you cannot use the JBP billing period for the final meter reading since it would mean that the device removal takes place before the final meter reading, which in turn means that useful time slices could not be determined for billing.
Dependencies
Example
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in | 471 |
