SAP ABAP Data Element ALLHISTORY (Indicator: complete history is permissible)
Hierarchy
☛
IS-UT (Software Component) SAP Utilities/Telecommunication
⤷ IS-U-BI (Application Component) Contract Billing
⤷ EE20 (Package) IS-U: Billing
⤷ IS-U-BI (Application Component) Contract Billing
⤷ EE20 (Package) IS-U: Billing
Basic Data
Data Element | ALLHISTORY |
Short Description | Indicator: complete history is permissible |
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 | History |
Medium | 15 | Complete hist. |
Long | 20 | Complete history |
Heading | 1 | H |
Documentation
Definition
During billing, all historical values of the operand are imported, including those from before the start of the billing period.
This special form of processing within billing is used in the following cases:
- Display of historical values on the bill, such as consumption, demand, or average price per kWh for a freely definable number of previous periods.
- Addition of consumption from previous periods or analysis of demand from previous periods using variants QUANTI18 or DEMAND18.
This usage is restricted to operands of the categories QUANT, DEMAND, AMOUNT and QPRICE.
These operands can then be processed by special variants only. These variants have a special indicator set for the corresponding input operand. In this way, it is possible to check that in the rate, only those operands for which this variant usage was selected are allocated to the variant.
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in |