Hierarchy
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 | CVAR |
| Short Description | Variant for Customer-Defined Conflict Resolution |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CVAR | |
| Data Type | CHAR | Character String |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| 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 | Variant |
| Medium | 15 | Variant for Con |
| Long | 20 | Variant for Con.Res. |
| Heading | 10 | Variant |
Documentation
Definition
Use this variant to override the SAP solution scenario for a meter reading conflict.
Example:
If
(meter reading period, operand group, meter reading scenario) = ( J, REPL , 1 )
describes a conflict with the solution in the above-mentioned SAP table, you can store an alternative solution under
(variant, meter reading period, operand group, meter reading scenario) =
( VALL,J,REPL,1 ).
Note
There are currently two variant names; these have the following meaning:
- VALL: the solution scenario stored here is the default basis for meter reading processing.
- VEXP: the solution stored here is only used if it is selected via a function key in meter reading processing.
As far as possible, use these variants so that VALL is always linked to automatically executed solutions, and VEXP is only configured for experts who required a broad selection of solutions in order to solve conflicts. This avoids an unnecessary workload for agents, since conflict problems are only solved by experts.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in | 471 |
