Manual Renewal
A business object for Account Management (FS-AM) that you can use to extend the maturity of an existing loan. This extension is performed manually by the bank.
You can execute a Manual Renewal order various circumstances, which depend on the following 2 aspects of the manual renewal:
The day on which the new condition fixing agreement or inpayment agreement period begins in relation to the existing condition fixing agreement and inpayment agreement period. A renewal can be early, exact, or late.
The day on which the new condition fixing agreement or inpayment agreement period begins in relation to the existing posting date (or system date) for payment transactions. A renewal can be backdated, forward, or exact.
The following table outlines the different circumstances:
Relative to Posting Date for Payments |
Relative to End Date of Old Condition Fixing Agreement and Inpayment Agreement |
||
Before |
On the Date |
After |
|
After |
n/a |
||
On the Date |
|||
Before |
|||
The renewal can result in a changed agreement period, a new condition fixing period, and a new inpayment agreement. You can manually reverse the new data. For more information, see Loan.
In the Account Management (FS-AM)
system, a manual renewal is managed as an order by Order Management (FS-AM-OM). When you activate the order, the manual renewal is
flagged in the system for processing; when you execute it, the manual renewal is set.
Structure
The structure description of the Manual Renewal object is divided into attributes, methods, and customer enhancements.
Methods
In Account Management (FS-AM)
, you can use one of the following channels for processing the Manual Renewal object:
Dialog
Enterprise Services
Dialog
The Manual Renewal function can use the Entry Origin
or Processing Origin
field to identify the channel used to process it. This can be the dialog channel for which the system displays the entry origin BORENW (Manual Renewal Dial).
You can call the dialog processing using transaction BCA_OR_RENW
.
You can call the following methods using dialog processing:
Create and enter
Create and activate
Change and enter
Change and delete
Change and activate
Display
You can also use the Execute Renewal and Contract End Processing mass run.
You can find this on the SAP Easy Access screen under 
Financial Services
Account Management
Periodic Tasks
Manual Renewal (Loans)
Enterprise Services
You can use enterprise services of the business object Loan Contract Prolongation Request
. For more information, see SAP Help Portal at http://help.sap.com/ -> SOA -> SAP for Industries -> SAP for Banking -> Enterprise Services
for banking services from SAP.
Integration
When the system processes a manual renewal order, the corresponding release object and the various authorization objects have
a controlling function for the program flow. The system calls the following objects from Account Management (FS-AM)
for processing:
Objects Checked by the System
The system checks the account and displays messages accordingly if one or more of the following requirements have not been met:
The loan account exists and the account product permits renewal.
The account has the contract status
Active, Used
.The account is not
In Release
.The system runs authorization checks.
You have made entries in all of the mandatory fields.
The posting date is not in the past.
The value date is defined.
Objects Changed by the System
After activating the order, the new condition fixing or inpayment agreement appears on the account. In addition, there may be changes to the agreement term and individual conditions.
Objects Generated by the System
The system generates a change document that meets auditing requirements.
Work Item
If required on the basis of the Customizing settings you have made, the system generates a work item for the release process.
If required, the system generates correspondence for the following operations:
Activate
Deactivate
Execute
Reverse