Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U (Application Component) SAP Utilities⤷
EE00 (Package) IS-U: General (Domains and General Objects)
Basic Data
| Data Element | CONS_MONTH |
| Short Description | Consumption Month |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BUPER | |
| Data Type | ACCP | Posting period YYYYMM |
| Length | 6 | |
| Decimal Places | 0 | |
| Output Length | 7 | |
| 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 | Month |
| Medium | 15 | Month |
| Long | 20 | Month |
| Heading | 6 | Month |
Documentation
Definition
Period reference when making updates in the Business Warehouse
Use
When extracting billing document data into the Business Warhouse, the corresponding consumption values and revenues are distributed over the calendar months, to which they relate.
Dependencies
When updating mass simulation data in the Business Warehouse, this field can contain specifications for the consumption quarter rather than the reference to the consumption month. In the case of a mass simulation, this field must be interpreted in connection with the period pattern when updating in Business Warehouse. This information is available int he INTLENGTH field in the BIW_ISU_ESTA_SIM extraction structure.
Example
In the case of a quarterly period pattern, the period field for each consumption year can only have the following four values (for example, for the consumption year 2006):
- 01.2006 means 1st quarter of 2006
- 04.2006 means 2nd quarter of 2006
- 07.2006 means 3rd quarter of 2006
- 10.2006 means 4th quarter of 2006
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
