Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U-CS-BT-IO (Application Component) Move-In/Out⤷
EE06 (Package) IS-U: Move-In/Out
Basic Data
| Data Element | ECPBILLOFFSET |
| Short Description | Move-In/Out: Interval to Structure Per. Bill. Orders in Futr |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ANZTA | |
| Data Type | NUMC | Character string with only digits |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| 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 | IntPerBiO |
| Medium | 15 | IntPerBillOrder |
| Long | 40 | Interval for Future Per. Billing Orders |
| Heading | 4 | IPBO |
Documentation
Definition
Defines the period after the system date in which billing orders can be created for periodic billing can be created as part of move-in or move-out processing.
This period ends on the system date plus the specified number of days.
Use
When you create/reverse move-outs and move-ins, vacant status periods are either created or canceled. When you create a mass order for a meter reading unit a billing order is generally not created for inactive installations.
In certain cases it is therefore necessary to create missing periodic billing orders/delete unnecessary orders during move-in and move-out processing. This ensures that Billing and budget billing creation run smoothly.
The interval ensures that future billing dates for which you do not yet want to create billing orders are not taken into account.
Examples
You have specified an interval of 30 days. A move-out with a move-out date of January 31 is created for an installation.
- Case 1: In accordance with the schedule of the meter reading unit to which the installation belongs, the planned meter reading date is scheduled for February 16.
On February 14 the system runs a mass order creation. Since the installation in question is inactive on February 16, a billing order is not created.
On February 20, the move-out is reversed. As part of the reversal, the billing order for the scheduled meter reading date on February 16 is re-built.
- Case 2: In accordance with the schedule of the meter reading unit to which the installation belongs, the planned meter reading date is scheduled for April 30.
In this case a billing order is not created when the move-out is reversed. The system assumes that mass order creation takes place for the entire meter reading unit after February 20.
Dependencies
See the documentation on creating past periodic billing orders.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
