Class Verbrauch
Abbildung eines zeitlich abgegrenzten Verbrauchs.
Inherited Members
Namespace: BO4E.COM
Assembly: BO4Enet.dll
Syntax
public class Verbrauch : COM
Properties
| Improve this Doc View SourceCENTRAL_EUROPE_STANDARD_TIME
Central Europe Standard Time as hard coded default time. Public to be used elsewhere ;)
Declaration
public static TimeZoneInfo CENTRAL_EUROPE_STANDARD_TIME { get; }
Property Value
Type | Description |
---|---|
TimeZoneInfo |
Einheit
Gibt die Einheit zum jeweiligen Wert an.
Declaration
public Mengeneinheit Einheit { get; set; }
Property Value
Type | Description |
---|---|
Mengeneinheit |
Enddatum
Ende des Zeitraumes, für den der Verbrauch angegeben wird.
Declaration
public DateTime Enddatum { get; set; }
Property Value
Type | Description |
---|---|
DateTime |
Obiskennzahl
Die OBIS-Kennzahl für den Wert, die festlegt, welche Größe mit dem Stand gemeldet wird.
Declaration
public string Obiskennzahl { get; set; }
Property Value
Type | Description |
---|---|
System.String |
Examples
1-0:1.8.1
| Improve this Doc View SourceStartdatum
Beginn des Zeitraumes, für den der Verbrauch angegeben wird.
Declaration
public DateTime Startdatum { get; set; }
Property Value
Type | Description |
---|---|
DateTime |
Type
type
Declaration
public Verbrauchsmengetyp? Type { get; set; }
Property Value
Type | Description |
---|---|
System.Nullable<Verbrauchsmengetyp> |
Examples
arbeitleistungtagesparameterabhmalo | veranschlagtejahresmenge | TUMKundenwert
| Improve this Doc View SourceWert
Gibt den absoluten Wert der Menge an.
Declaration
public decimal Wert { get; set; }
Property Value
Type | Description |
---|---|
System.Decimal |
Wertermittlungsverfahren
Gibt an, ob es sich um eine PROGNOSE oder eine MESSUNG handelt.
Declaration
public Wertermittlungsverfahren Wertermittlungsverfahren { get; set; }
Property Value
Type | Description |
---|---|
Wertermittlungsverfahren |
Methods
| Improve this Doc View SourceFixSapBugs(StreamingContext)
Declaration
protected void FixSapBugs(StreamingContext context)
Parameters
Type | Name | Description |
---|---|---|
StreamingContext | context |
FixSapCdsBug()
Our SAP Core Data Service view definition reading the profile values has a bug: The time stamp of both start- and enddatum is simply a concatenated string using the date (defining the table row) and the time (determining the column). The design of the table eprofval is pure PITA but we've got to deal with it anyway. Since it's impossible to artificially increment the date directly in the definition of the ABAP/SQL view (as of SAP 7.51), we're attempting to fix it here. On 363 days a year the symptom is easy to detect: The last time slice of the day ranges from 23:45 of the current day and has the enddatum t 00:00 still on the same day instead of the following. What makes it difficult are the edge cases. What happens on the day we switch from daylight saving time to non-daylight saving time? The time difference could be in the order of magnitude of 22 to 25 hours. Please add new unit tests for every edge case.
Declaration
public void FixSapCdsBug()
FixSapCdsBug(Verbrauch)
static version of FixSapCdsBug()
Declaration
public static Verbrauch FixSapCdsBug(Verbrauch v)
Parameters
Type | Name | Description |
---|---|---|
Verbrauch | v | verbrauch to be fixed |
Returns
Type | Description |
---|---|
Verbrauch | new Verbrauch instance with fixed bugs |