Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U-BI (Application Component) Contract Billing⤷
EE20 (Package) IS-U: Billing
Basic Data
| Data Element | DISTTYPE |
| Short Description | Distribution Type for Installation Groups |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DISTTYPE | |
| Data Type | CHAR | Character String |
| Length | 8 | |
| Decimal Places | 0 | |
| Output Length | 8 | |
| Value Table | TE675 |
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 | Distr.Type |
| Medium | 15 | Distr. Type |
| Long | 20 | Distribution Type IG |
| Heading | 4 | DTyp |
Documentation
Definition
Distribution type for installation groups that exchange data from primary to the secondary installation.
Use
When you bill installation groups, data can be exchanged between primary and secondary installations. You can bill a primary installation and distribute quantities or amounts between secondary installations. These distributed quantities or amounts are then taken into consideration when the secondary installations are billed.
You can specify different rules that control the distribution of quantities or amounts among secondary installations. SAP recommends that you create a distribution type for every rule. You must enter the rules you want to use for an installation group in the grouping type of the primary installation. This is initially for information purposes. The variant program that you use to determine distribution in the primary installation's billing schema specifies how the distribution is actually carried out.
The variant program UTILIT96 is a template for this kind of variant. If you want to distribute quantities or amounts based on other rules, you must copy this variant program and encode your own rules. You can define the variant program so that different rules can be used for each distribution type. You can also define additional customer-specific tables, which contain further information for the variant program. This information is dependent on the distribution type.
Example: Installation fact operands from the secondary installation that contain distribution criteria.
Dependencies
If you enter a distribution type in a grouping type, you must select the field Role is Distribution-Relevant for at least one installation role.
Example
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in | 472 |
