SAP ABAP Data Element FINALBILL (Immediate Final Billing)
Hierarchy
☛
IS-UT (Software Component) SAP Utilities/Telecommunication
⤷
IS-U-BI (Application Component) Contract Billing
⤷
EE20 (Package) IS-U: Billing
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U-BI (Application Component) Contract Billing⤷
EE20 (Package) IS-U: Billing
Basic Data
| Data Element | FINALBILL |
| Short Description | Immediate Final Billing |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | KENNZX | |
| 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 | FinalBill. |
| Medium | 15 | Final Billing |
| Long | 20 | Immediate Final Bill |
| Heading | 2 | FA |
Documentation
Definition
Ensures that final billing orders from secondary installations with distribution can be billed immediately.
Use
This indicator only has an affect on installation roles that have the Distribution-Relevant indicator selected. If you generate a billing order for a distribution-relevant secondary installation, the Billing Sequence Control is set to 1 = Order Cannot Be Billed, Not Been Activated. A secondary installation can only be billed after the primary installation has been billed.
- This will also apply to final billing orders if you do not set the Immediate Final Billing indicator. In this case, final billing can only be executed when the primary installation is billed together with all other secondary installations.
- If you set the Immediate Final Billing indicator, the Billing Sequence Control in the final billing order is set to the value ' ' = Order Can Be Billed. This means that final billing can be executed immediately. When this happens, the system cannot access distribution data because the primary installation document does not exist yet. As a result, you must define the billing schema of the secondary installation so that this does not terminate the process.
Dependencies
Example
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in | 472 |
