Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U-IN (Application Component) Invoicing⤷
EE25 (Package) IS-U: Budget Billing Amounts
Basic Data
| Data Element | TAKE_AMOUNT |
| Short Description | Amount Transfer |
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 | AmntTransf |
| Medium | 15 | Amount Transfer |
| Long | 20 | Amount Transfer |
| Heading | 2 | AT |
Documentation
Definition
Transfers previous amount to the new budget billing plan.
Use
There are two different cases depending on the type of budget billing cycle in question:
- The new and the previous budget billing plans have the same budget billing cycle
The amounts are always copied from the previous budget billing plan. You can control this yourself in event R923. For more information, read the documentation on the Sample Module for Amount Transfer (R923). The function module Standard Module for Amount Transfer (R923) (ISU_AMOUNT_PORTION_CHANGE) runs as default in this event. In this module, the deactivated amounts are transferred in the same sequence to the new due dates. If necessary, the amounts from the last due date of the previous budget billing plan are copied to the remaining due dates of the new budget billing plan.
Example:
The previous budget billing plan finished on December 31st. The new budget billing plan finishes on March 31st of the following year.
Previous Deactivated New
01.25. 100.00
02.15 100.00
03.15. 100.00
04.15. 100.00
05.15. 100.00
06.15. 100.00 X 06.20. 100.00
07.15. 100.00 X 07.20. 110.00
08.15. 120.00 X 08.20. 120.00
09.15. 130.00 X 09.20. 130.00
10.15. 140.00 X 10.20. 140.00
11.15. 150.00 X 11.20. 150.00
12.15. 160.00 X 12.20. 160.00
01.20. 160.00
02.20. 160.00
03.20. 160.00
If you want another type of amount transfer, you must define an individual function module in event R923.
- Both budget billing plans have different budget billing cycles
In this case, you can specify whether the amounts are extrapolated and then transferred to the new budget billing plan from the extrapolation, or whether the amounts are transferred in event R923. You can use the Do Not Extrapolate During Cycle Change indicator in the budget billing plan control parameters to do this.
If you set this indicator, the amounts are transferred in event R923. The standard module for amount transfer (ISU_AMOUNT_PORTION_CHANGE) cannot deal with a cycle change. As a result, you must define your own function module for amount transfer in event R923. You can use the function module Proposal for Procedure During Cycle Change (R923) (ISU_AMOUNT_PC_CYCLE_CHANGE) as a template. This module is delivered but not used as default.
Dependencies
Example
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in | 472 |
