Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U-BI (Application Component) Contract Billing⤷
EE20 (Package) IS-U: Billing
Basic Data
| Data Element | ERCHV_BW_REL |
| Short Description | Not Relevant for Consumption History in BW |
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 | NRel.ConsH |
| Medium | 15 | Not Rel. BW CH |
| Long | 20 | Not Rel. f. CH in BW |
| Heading | 2 | NR |
Documentation
Definition
Indicates whether the consumption history must be extracted to BW.
Use
This field is only relevant if you implement the IS-U/CRM Integration Marketing component.
If a variant of variant category 12 (variant for writing consumption history) is stored in a schema step, you can use this field to control when the billing quantity and net amount from the resulting entry in the consumption table are not transferred to BW by DataSources 0UC_ISU_CONSUMPT_02 and 0UC_ISU_CONSUMPTION (IS-U historical consusmption values).
Example
In two schema steps you calculate different demand quantities and their amounts for the same contract and the same time slice of your billing period. You decide which demand quantity is to be used in BW for marketing analyses, and in the other schema step you must select the field if the demand quantity is not to be taken into account in BW. If you do not select the field, the demand quantities are added together during extraction of the consumption history to BW.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in | 464 |
