Hierarchy
⤷ IS-M (Application Component) SAP Media
⤷ JSD (Package) Appl. dev. R/3 Publishing Sales and Distribution System
Basic Data
Data Element | BALANCING_DAYS |
Short Description | IS-M/SD: Monitoring Control, Balancing Days |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | BALANCING_DAYS | |
Data Type | DEC | Counter or amount field with comma and sign |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
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 | Bal. Days |
Medium | 15 | Balancing Days |
Long | 20 | Balancing Days |
Heading | 3 | BDy |
Documentation
Definition
In the case of monitoring-controlled subscriptions that are always renewed on the same date in the month (for example, on the 1st or 15th of each month), the payment amount does not always fully cover the period until the next due date.
Example
If there are a large number of days (and Sundays) in a particular month and a Sunday edition costs more than a weekday edition, the monthly payment, which amounts to 1/12 of the payment for the year, does not cover the whole month.
To prevent the system from requesting a further monthly installment in this case, you must define a certain period during which the system does not begin a new monitoring cycle even if the subscription has not (yet) been paid. In the course of a year, the monthly installments add up to the full year's payment, so that the periods for which too much or too little is paid cancel each other out.
However, if a subscription is terminated before a year has passed, there may be days (depending on the termination date) on which the subscription was delivered but for which the system does not issue a payment request.
You can define this period for each monitoring procedure in this field.
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in | 464 |