Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U-BI (Application Component) Contract Billing⤷
EE20 (Package) IS-U: Billing
Basic Data
| Data Element | TARGET_OP_MAIN |
| Short Description | Target Operand for Data Ex. from Second. to Prim. Installatn |
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 | Targ. Op. |
| Medium | 15 | Targ.Op: P Inst |
| Long | 23 | Target Op.: Prim. Inst. |
| Heading | 10 | Target Op. |
Documentation
Definition
Target operand for data exchange from a secondary installation to a primary installation.
Use
When you bill the primary installation of an installation group, you can transfer billing data from the corresponding secondary installation. Prerequisite: The secondary installation in your billing schema must generate special consumption information lines (ERCHV). The field Role Relevant for Consumption Determination must also be selected in the installation role. The quantities or amounts from these bill lines can be used in the billing schema of the primary installation. In this field, you can enter the operand to be supplied with these values as the target operand.
Dependencies
- Only target operands from the categories AMOUNT or QUANT are permitted.
- The Supply Using ERCHV indicator must be set in the target operand.
- The source operand and the target operand must have the same operand category.
- When a value is transferred from the source operand to the target operand, it is not checked and the units of measurement are not converted. You must make sure yourself that the units of measurement in the source and target operands are compatible.
Example
- An installation group consists of a primary installation with the grouping type 0001 and several secondary installations with the installation role 0001.
- In the billing schema of the secondary installations, variant QUANTI22 generates a consumption information line with the SUBCONS operand.
- In the billing schema of the primary installation, you want the total consumption of all secondary installations with the role 0001 to be used in a schema step with the operand SUMSUB.
- As a result, you must maintain the table for data exchange from the secondary installation to the primary installation as follows:
Grouping type Role Source operand Target operand
0001 0001 SUBCONS SUMSUB
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in | 472 |
