Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U-BI (Application Component) Contract Billing⤷
EE20 (Package) IS-U: Billing
Basic Data
| Data Element | MAINDOCNO |
| Short Description | Billing Document Number of Primary Installation |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | E_BELNR | |
| Data Type | CHAR | Character String |
| Length | 12 | |
| Decimal Places | 0 | |
| Output Length | 12 | |
| Value Table |
Further Characteristics
| Search Help: Name | ERCH | |
| Search Help: Parameters | BELNR | |
| Parameter ID | BEL | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | P-Inst.Doc |
| Medium | 15 | PrimInstDoc.No. |
| Long | 20 | Doc. Number Prim. In |
| Heading | 12 | PrimInstDoc |
Documentation
Definition
The Document Number of the Primary Installation links billing documents that are created when an installation group is billed.
Use
An installation group consists of a primary installation and one or more secondary installations. During billing, the billing documents are used to exchange data between the primary installation and the secondary installations. If the primary installation uses a secondary installation billing document during billing, the document number of the primary installation is entered in this secondary installation billing document.
If the installation group contains a distribution-relevant secondary installation, the document number of the primary installation is initially entered in the billing order.
Using the document number of the primary installation to link billing documents prevents billing documents from secondary installations being used twice when a primary installation is billed. It also allows you to identify documents that have not yet been processed.
Dependencies
If a billing document in a secondary installation contains the document number of the primary installation and is reversed, the number is transferred to the billing order. When the secondary installation is re-billed, the resulting billing document has the same document number of the primary installation.
If a billing document from a primary installation is reversed, the system checks whether the document number has been entered in another billing document or billing order as the document number of the primary installation. If yes, this number is deleted.
Example
Example 1:
- An installation group consists of primary installation A and secondary installation B. In the secondary installation role, the Consumption-Relevant field is selected but the Distribution-Relevant field is not.
- The secondary installation B is billed for the month of June. This generates a billing document with the billing document number 1000. The field Document Number of Primary Installation is first of all empty.
- Then primary installation A is billed for June. The data from billing document 1000 in secondary installation B is used for this. A new billing document with the document 1200 is created. At the same time, 1200 is entered in the field Document Number of Primary Installation in billing document 1000.
Example 2:
- An installation group consists of primary installation C and secondary installation D. In the secondary installation role, both the Consumption-Relevant and Distribution-Relevant fields are selected.
- A billing order for June exists for the primary and secondary installations.
- Primary installation C is billed first of all. Billing simulates the billing order of secondary installation D internally and uses the data from the simulation document. A new billing document is created for the primary installation with the document number 2000. In the billing order of the secondary installation, the value 2000 is entered in the field Document Number of Primary Installation.
- Secondary installation D can now be billed. In the resulting billing document 2200, 2000 is entered in the Document Number of the Primary Installation Field.
History
| Last changed by/on | SAP | 20110809 |
| SAP Release Created in | 472 |
