Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U-MD (Application Component) Master Data⤷
EE01 (Package) IS-U Master Data
Basic Data
| Data Element | E_GEMFAKT |
| Short Description | Invoice Contracts Jointly (Mandatory Contracts) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | E_GEMFAKT | |
| 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 | Joint Inv. |
| Medium | 15 | Joint Invoicing |
| Long | 23 | Joint Invoicing |
| Heading | 2 | JI |
Documentation
Use
Here you specify whether this contract is to be invoiced together with other contracts, and how this is to be done.
Dependencies
If you change the entries, these changes will take effect when the next bill is created for the contract account of the contract. On the basis of the specification in the contract, the periodic, final, or interim billing documents of the contract are invoiced together with the billing documents of other contracts of the contract account.
Example
Account 4711 contains four contracts. Contracts 1, 2 and 3 must be invoiced together. No entry has been made for contract 4. Contracts 1, 2 and 4 have already been billed, but contract 3 has not.
In invoicing, only contract 4 is invoiced. Since contracts 1 and 2 must be invoiced together with contract 3, they are not invoiced until contract 3 has been billed.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
