Hierarchy

⤷

⤷

Basic Data
Data Element | TARGET_OP_SUB |
Short Description | Target Operand for Data Ex. from Primary to Second. Inst. |
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: S Inst |
Long | 21 | Target Op.: Sec. Inst |
Heading | 10 | Target Op. |
Documentation
Definition
Target operand for exchanging data from the primary to the secondary installations.
Use
When you bill a secondary installation in an installation group, you can transfer billing data from the corresponding primary installation. Prerequisite: The primary installation in your billing schema must generate special consumption information lines (ERCHV) for secondary installations. In the secondary installation role, the field Role is Distribution-Relevant must be selected.
The quantities or amounts from these bill lines can be used in the billing schema of the secondary 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 indicator Supply Using ERCHV 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 or currencies are not converted. You must make sure yourself that the units of measurement or currencies 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 primary installation, the variant UTILIT96 generates consumption information lines for all secondary installations with the role 0001. The operand in this consumption history is SUMDIST.
- The value in the primary installation must be transferred in the billing schema of the secondary installations. The consumption information line generated for each secondary installation in the primary installation document is read when a secondary installation is billed. The billing schema can access the value in the consumption information line. The operand used for this is called DISTCONS.
As a result, you must maintain the table for the data exchange from the primary installation to the secondary installation as follows:
Grouping type Role Source operand Target operand
0001 0001 SUMDIST DISTCONS
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in | 472 |