Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U-BI (Application Component) Contract Billing⤷
EE20 (Package) IS-U: Billing
Basic Data
| Data Element | OPTIONAL |
| Short Description | Optional billing step |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | OPTIONAL | |
| 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 | Optional |
| Medium | 15 | Optional |
| Long | 20 | Optional |
| Heading | 1 | O |
Documentation
Definition
Schema steps can only be executed during billing if values are provided for all input operands in the entire period for the step. If this is not the case, the billing program depends on the "optional" indicator as follows:
- If the indicator is not set, billing of the contract is terminated.
- If the indicator is set, the schema step is not executed. Processing continues with the next schema step.
You can use this indicator to structure flexible rates.
Example
You insert an optional step with a discount variant. The discount is not supplied with values in the rate facts or in the rate category facts. This means that the discount variant is only executed for the customers for whom a discount is specified in the installation facts.
Only set the "optional" indicator in exceptional cases, since missing operand values generally result in an error message. If you have set the "optional" indicator and operand values are missing for an input operand, then no error message is displayed.
Some variants are not suitable for optional steps (for example, IF variants). The "optional" indicator is not ready for input for these variants.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
