Savings Scheme
Agreement 
Definition
A function for an account, whereby the payment and monitoring of regular installments are agreed for an account contract. All the other basic functions for an account are also available.
In the bank statement, you can make a key date reconciliation with the savings scheme agreement. You can use this to create a bank statement after the savings year has ended, for example. The time period reconciliation product attribute is available for the bank statement. For more information about product attributes and their characteristics, see: Product.
For information about bonus calculation for a savings scheme agreement, see Calculating Bonus.
For more information on the agreements made when you create a contract for a savings scheme agreement, see Editing a Savings Scheme Agreement.
Use
The savings scheme agreement lasts for a fixed period, agreed upon when you create the contract (term of the savings scheme agreement), and consists of several phases.
· Preliminary phase
¡ Starts on the contract start date
· Savings Phase
¡ Payment and monitoring of the agreed amounts
¡ Starts either with the one-off payment of a special payment amount or on the start of the term of the installment agreement
¡ Ends at the end of the installment agreement
· Inactivity Phase
¡ Starts at the end of the savings phase
¡ No more installments are paid and monitored
· Passive phase
¡ Starts at the end of the inactivity phase
¡ End of the savings scheme agreement. Depending on the product settings in the Account Management Customizing settings, the account is converted to an account product without savings scheme agreement or closed.
The current phase results from the duration of the savings scheme agreement and installment agreement and the current date. It is displayed on the Savings Scheme Agreement tab page in the Phase group box of the account in question, as is the planned action at the end of the savings scheme agreement.
Structure
In the structure of the savings scheme agreement, we distinguish between master data and flow data.
· The master data of a savings scheme agreement is managed by contract element: savings scheme agreement (BCSS).
For additional technical information about the contract element, see the Technical Documentation button on the initial screen of the account.
· The flow data of the savings scheme agreement is monitored and controlled by the payment monitoring and life cycle control functions of the savings scheme agreement.
Methods
In Account Management (FS-AM), you can use one of the following three channels for processing objects:
Dialog
Individual processing:
Transaction Code |
Short description |
BCA_PAYMON_DIA_SHOW |
Display payment history of a savings scheme agreement. |
BCA_PAYMON_DIA_CHNG |
Change payment history of a savings scheme agreement. |
BCA_RC_IBS_NEXT_DUE |
Display next due dates (savings scheme agreement) |
BCA_PAYMON_NEXT_DUE |
Display next due dates (installment agreement only) |
BCA_COUNTER_CHANGE |
Change counter reading |
BCA_DPITEM_CREATE |
Creating Debit Position Items |
BCA_DPITEM_DISPLAY |
Displaying Debit Position Items |
BCA_DEBPOS_NEXT_DUE |
Next debit position date |
BCA_INSMON_NEXT_DUE |
Next monitoring date |
Mass processing:
Transaction Code |
Short description |
BCA_DEBPOS_RUN |
Execute debit positions |
BCA_INSMON_RUN |
Monitoring installment payments |
BCA_RC_IBS_DUECSP_PP |
Create correspondence at end of savings phase |
BCA_RC_IBS_DUECET_PP |
Create correspondence for end of savings scheme agreement |
BCA_RC_IBS_ACTEOT_PP |
End savings scheme agreements as planned |
Business Application Programming Interface (BAPI)
You can call up the following methods using the BAPI Explorer:
Method |
Short description |
PaymentMonitoring.CreateFromData |
Legacy data transfer for payment monitoring |
PaymentMonitoring.GetListNotPaid |
Read unpaid installments (debit positions) |
PaymentMonitoring.ProgressionChange |
Change data for payment monitoring history |
PaymentMonitoring.ProgressionGet |
Read details on payment monitoring history |
Direct Input
For savings scheme agreements, direct input is implemented for the data of contract element: savings scheme agreement (BCSS).
Example
An account contract with a savings scheme agreement was concluded on 02/01/2002 for a period of two years, with a one-month inactivity phase. The account product used comprises an automatic product change at the end of the savings scheme agreement. A special payment was agreed for 02/15/2002. The start of the installment agreement was defined as 03/01/2002. Since a monthly installment payment was agreed for 15th of every month, the first installment is due on 03/15/2002. The end of the installment agreement and also the savings phase is 02/01/2004; the last installment is due on 01/15/2004. The savings scheme agreement enters the inactivity phase, as agreed. Upon entering the passive phase, the account is converted to a follow-up product without savings scheme agreement, as previously specified in the Customizing settings.
Event |
Date |
Phase |
Contract Start |
02/01/2002 |
Preliminary phase |
Date of special payment |
02/15/2002 |
Savings Phase |
Start of installment agreement |
03/01/2002 |
|
Due date of first installment |
03/15/2002 |
|
Due date of last installment |
01/15/2004 |
|
End of the installment agreement or the savings phase |
02/01/2004 |
Inactivity Phase |
End of the savings scheme agreement or the savings phase |
03/01/2004 |
Passive phase |