Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U-BI (Application Component) Contract Billing⤷
EE20 (Package) IS-U: Billing
Basic Data
| Data Element | DELOPERAND |
| Short Description | Deletion operand |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | E_OPERAND | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table | TE221 |
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 | Del. oper. |
| Medium | 15 | Deletn operand |
| Long | 20 | Deletion operand |
| Heading | 10 | Del. oper. |
Documentation
Definition
The deletion operand is required for structuring billing schemas, which are to execute best-rate billing using deletion variants (from category 07). The deletion operand connects the schema steps of the deletion variants to other schema steps.
In best-rate billing, a contract is billed using different alternatives. The results of these alternatives are made available to a schema step with a deletion variant via the amount update. An amount operand corresponds to each alternative. The variant compares the amounts and deletes the billing line items of all previous steps that do not belong to the optimal alternative. In addition, subsequent steps can be set as inactive, resulting in the steps not being executed.
The deletion operand establishes which schema steps are influenced by the deletion variant. Use the deletion operand as follows:
- For all schema steps that update an amount to a deletion variant, you must enter the affected amount output operand as a deletion operand.
- Also set the deletion operand for other schema steps for which the billing line items are to be deleted if they do not belong to the optimal alternative. Example: steps for converting values whose info lines are only required for one alternative.
- Set a deletion operand for steps that are after a deletion variant and are only to be executed if they belong to the optimal alternative.
Note that the deletion variants do not cancel the update performed by a schema step.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
