Professional Documents
Culture Documents
services from
SAP
Release 7.0
Instructor
Demonstration
Exercises
Activity
Summary
Objectives
Business Scenario
Warning or Caution
Internal Note
SAP AG FS241 – SAP Loans Management for Banking
Training System
SAP Contacts..............................................................................................................3
Walldorf.............................................................................................................................................. 3
Subsidiaries....................................................................................................................................... 3
Training System..........................................................................................................5
Data Required....................................................................................Error! Bookmark not defined.
User ID and Passwords for Course Participants................................Error! Bookmark not defined.
Preparation in the System.................................................................................................................. 7
Example ABAPs................................................................................................................................. 8
CATTs................................................................................................................................................ 8
Technical Hints.................................................................................................................................. 8
Unit: <Name>.............................................................................................................12
SAP Contacts
Walldorf
Subsidiaries
Course Details
Duration
3 days
Country-Specific Units
No country specific units are available.
Support
Open a CSN IT Support ticket in the TRAI component or call the Hotline +49 6227 7 40030 for a
worldwide 24*7 support.
Training System
System Landscape
The following systems are required:
banking services from SAP system, release 7.0.
SAP FI-CA: Financial Accounting – Contract Accounts Receivable and Payable (SAP ERP
release 6.0)
Please make sure to test demos, exercises and solutions in advance in the test system and/or in
the training system.
Only use the training system in the week when your course is scheduled. In other weeks
the system is used by other courses and interference might lead to severe problems in
those classes. Unauthorized usage of a training system may result in a fee!
Example ABAPs
None
CATTs
None
Technical Hints
You need to enable the maintenance of Customizing tables for several users simultaneously.
You need to deactivate the table lock in SAP systems: transaction SE38 and the report
ZSENQON. You can deactivate this function by executing the report ZSENQOFF.
Course Schedule
Course Schedule:
Day One
Approximate Content: Units and Topics Activities: Instructor
Duration and Participant
30 min Introduction Instructor
0 – Integration of Deposit Management and Loans
Management on banking services to other components
Module: Loans Management
2 hours 1 – Account Model Instructor
1 hour 1 – Account Model Exercise Participants
1 hour 2 – Cash Flow Instructor
30 min 2 – Cash Flow Exercise Participants
45 min 3 – Scenario Specific Conditions Instructor
Day Two
Approximate Content: Units and Topics Activities: Instructor
Duration and Participant
30 min 3 – Scenario Specific Conditions Exercise Participants
45 min 4 – Payment Principles Participants
45 min 5 – Disbursement Instructor
45 min 5 – Disbursement Exercise Participants
1,5 hour 6 – Billing & Invoicing Instructor
1 hour 6 – Billing & Invoicing Exercise Participants
30 min 7 – Payment Distribution Instructor
Day Three
Approximate Content: Units and Topics Activities: Instructor
Duration and Participant
1 hour 7 – Payment Distribution continued Instructor
30 min 7 – Payment Distribution Exercise Participants
2 hours 8 – Business Operations Instructor
1 hour 8 – Business Operations Exercise Participants
15 min 9 – Insurance Management Instructor
15 min 10 – Integration with CMS Instructor
30 minutes presentation
Contents of Unit
- Introduction
- Sample Integration
Putting the Unit in Context
This chapter can be used as an introduction for the following training courses:
- FS240 Banking services from SAP – Basics and Generics in Transaction Banking.
- FS241 Banking services from SAP – SAP Loans Management for Banking
- FS242 Banking services from SAP – SAP Deposits Management for Banking
Many processes for Loan Accounts and Deposit Accounts do not run only end-to-
end in Account Management (Deposits Management + Loans Management), they
also require the integration of additional components. These components are
introduced here. The unit can also be used as a point of reference for questions that
may come up in one of the training courses mentioned above.
All processes shown here are explained in more detail in one of the above mentioned
training courses.
SAP Business Maps for Banking, which are available on sap.com, are used as a
point of reference for the business processes that are included in this presentation.
For a detailed process description, go to
http://www.sap.com/industries/banking/index.epx
and click on SAP Business Maps for banking.
Slide 6: Overview integration map for Account Management
Contents of Unit
- Account Structure concept
- Loan-specific Contract Elements and Attributes
- Create Change Loan Account
- Due date processing
Putting the Unit in Context
Postings are kept logically separate: The payment distribution process (post
incoming payment to Clearing Account – distribute the incoming payment from the
Clearing Account to the Loan Account) is the same whether the Clearing Account is
separate from or the same as the Loan Account.
Slide 18: Condition Fixing Agreement
A condition fixing agreement should not be confused with a fixed interest rate. The
condition fixing agreement determines conditions for a term. This can be – among
January 2010 Page 12
SAP AG FS241 – SAP Loans Management for Banking
Training System
other condition types - a fixed or a variable interest rate. Example: A variable
interest of a certain reference interest rate + 1 % is fixed for 2 years. Depending on
the interest adjustment agreement, the interest to be paid floats based on changes to
the reference interest rate.
Slide 18/20: Condition Fixing Agreement/Inpayment Agreement
These slides show the creation of the initial agreements. To create additional
condition fixing and/or inpayment agreements, you can use "Manual Renewal"
business operation. Agreements may not overlap. However, you can create a new
CFA/IPA by changing the account master data manually as well instead of using the
order "Manual Renewal". However, in the context of a renewal process we
recommend using the Business Operation that provides more options, for example,
calculating the new commitment capital.
Slide 25: Loan specific contract elements: Posting Data
Definition of available amount for a loan account:
+ Contract capital
+/- Capital increase/reductions
= Disbursement obligation
- Planned/scheduled disbursements to customer
= Extended disbursement obligation (available amount)
The "Relevant for Billing" attribute is not shown on this page because it has been
replaced by the Billing feature. However, if the feature Billing is used, this attribute
has to be activated.
Slide 31: Account Changes – Examples
When executing the Payment Plan Change Order (PPC), the payment conditions are
changed. You can also do this manually with a direct change to the condition
(Transaction "Change account"). However, it is easier to use the order.
- Less data to capture
- Fail-safe (a manual condition change is more likely to cause an error due to the
complexity of conditions)
- Control of authorization
- Reason codes
- Reversal option
System demo at the end of Lesson 3 (Create and Change Loan Account)
Note that the contract created in this demo will be used for demos in subsequent
lessons/units.
Content:
1. Loan Creation
2. Loan specific attributes
3. Clearing Account replication to FI-CAX
Demonstrate:
1) Check of Business Partner on banking services and FI-CAX
- Same BP-ID on both systems (use JIM TRAINING_00 with BP_ID:
January 2010 Page 13
SAP AG FS241 – SAP Loans Management for Banking
Training System
CUST_00)
- banking services: "account holder" role and "correspondence recipient"
role
- FI-CAX: "Contract Partner" role
- validity of roles and correspondence address must match with bank posting
area's posting date
2) Create Loan Account:
Menu: Financial Services – Account Management – Account – Account
Master Data – Create Account
Set Contract Start Date = Posting Date for Payment Transactions
Contract Manager: RT00 (00_Dublin)
Product: LO_FRIL_TR
Account Holder ID: CUST_00
3) Replicate Clearing Account to FI-CAX
Menu: Financial Services – Account Management – Periodic Tasks –
Communication with External Systems – Distribute Account Master Data
4) Show Contract Account on FI-CAX
Menu: Accounting – Financial Accounting – Contract Accounts Receivable
and Payable – Master Data – Contract Account – Display
The contract account number can be found by using F4:
- Contract acct name = "*[Loan Account Number]"
5) Execute Initial Billing
Menu: Financial Services – Account Management – Periodic Tasks –
Account Billing – Execute Account Billing
Contents of Unit
- Overview
- Input Data
- Display
- Calculation
- Key Figures
Putting the Unit in Context
Cash Flow
The Cash Flow is one of the basic elements of a loan account and is used by
many functions. Understanding the Cash Flow helps to understand many
subsequent units/lessons because the impact of various functions on the
Cash Flow can be explained by showing the change in the Cash Flow.
Examples:
o Business Operations such as Payment Plan Changes, Extensions,
and so on
o Billing
o Payment Distribution
o Settlement
Contents of Unit
- Overview
- Interest Conditions
- Charge Conditions
- Other Conditions
Putting the Unit in Context
Conditions
The general concept of conditions for banking services is explained in the
training for generic features and functions. Some loan-specific conditions
such as manual waiver and payment condition are handled there, too.
You use this unit to demonstrate the implementation of conditions for loan
products.
Slide 8: Overview
This figure shows which conditions could be relevant for a loan account on the basis
of the business process – irrespective of the product and banking services from SAP:
Light blue labels designate the interest conditions.
Dark blue labels designate the charge conditions
Waiver condition can be set up in connection with every other condition.
Therefore, waivers have a special position within the condition system.
Insurance premiums can be calculated like a charge or an interest condition.
Slide 11: Interest Conditions – Variable Nominal Interest
The figure shows that EURIBOR changes do not have an immediate effect on the
customer’s interest rate. The 2-point mark-up is only adjusted on the defined dates.
This means the bank’s margin can increase or decrease between the adjustment
dates.
The figure shows an extreme example to clarify the effect. The EURIBOR changes
daily in small increments.
Slide 12: Interest Conditions – Variable Nominal Interest
Note that the dates for the first fixing and adjustment are necessary for interest
calculation. This means the first adjustment has to include the start date of interest
calculation.
SAP Menu: Financial Services -> Account Management -> Account -> Account
Master Data -> Create Account
Open account (product LO_MORG_TR) with essential data. For event
conditions delete the condition group and create a new individual condition:
o Use the condition type ‘Direct Charges Loans’.
o Select ‘Deferral’ as the feature and ‘Create or Generate’ as the
activity.
o Enter the contract creation date as Valid From
o Enter the amount for the condition.
Show the cash flow. There is no entry for the event condition because the
event has not occurred yet.
45 minute presentation
Contents of Unit
- Introduction and Overview
o Definition and Classification
o Definition of Terms
- Comparison of Principles
o Exact Payment
o Late Payment
o Underpayment
- Configuration
o Settings for Payment Principles
o Payment Principles in Application
o Associated Settings
- Appendix
o Early Payment
o Overpayment
Payment Principles do not appear in special functions but take effect indirectly in other functions.
Note: Some terms can have varying intent or emphasis in different countries. For
example: the term ‘annuity’ is closely connected with mortgage loans and the
payment plan principle in Germany. In North America the constant installment with
changing shares of interest and repayment is also very common, but not called
‘annuity’.
Unit: Disbursement
Contents of Unit
- Overview
- Disbursement Order
- Disbursement Process
Putting the Unit in Context
Disbursement
The disbursement order is the first business operation introduced in Loans
Management. The general concept of business operations is part of "Generic
Features and Functions", in the "Order Management" unit.
The release process is available to all business operations. Since the most
relevant business operation for reversal is the disbursement, it is part of this
unit.
Contents of Unit
- Creating Open Items
o Classification
o Billing & Invoicing Process
- Billing Characteristics
- Billing Correction
o Reversal
o Automatic Correction
- Direct Debit Process
Putting the Unit in Context
Billing & Invoicing are the core elements of due date processing with the objective of creating Open
Items for expected payments.
Background information about coupon books – mention this only if questions come
Hint: You configure the creation of a payment order on the payment method level.
1. IMG: Financial Accounting (NEW) – Contract Accounts Receivable and
Payable – Business Transactions – Payments –Incoming/Outgoing Payment
Creation – Define Payment Method
2. Select a country and double-click on Payment Method in the menu
Double-click on the Payment Method in the list
Contents of Unit
- Overview
- Concept
- Technical Objects
- Process
- Configuration
Putting the Unit in Context
Contents of Unit
- Skip
- Extension
- Deferral
- Capitalization
- Waiver
- Payment Plan Change
- Payoff
- Manual Renewal
- Cancellation/Rescission
- Account Closure
- Product Change
- Account Holder Change
Typically, the processing of a loan is fully automated once it has been disbursed.
However, during the loan’s life cycle events that require manual intervention
may occur. banking services from SAP provides Business Operations for these
events.
Give a brief system demo on configuration which is the same for all business
operations
1. Show how to enable/disable conditions for using by a business operation:
Exercise Deferral to be done after the system demo of the skip and presentation
of lesson on Deferral.
Exercise Payoff to be done after the presentation and system demo of lesson on
Payoff.
Slide 78: Handling of Business Operations in the Account Holder Change Order
Reverse/delete/deactivate business operations: A business operation can be regarded
as a change request that was negotiated individually with the old account holder,
such as a Skip of some future payments. With the execution of the AHC to the new
account holder, the following activities are executed if selected as follow-up activity
in the AHC order:
- Entered business operations are deleted
- Activated business operations are deactivated (for example, Payoff Quote)
- Executed business operations are reversed (e.g. Payment Plan Change)
if configured and selected as optional follow-up activity in the AHC order. Do not
mention more details about the status concept of loan specific business operations
here.
Slide 89 Example: Scenario (2) - Forward Renewal
Explain another scenario of a forward renewal using the graphic: Assume that the
Inpayment Agreement 1 has the same term as the Agreement. Then the manual
renewal would only add a new Condition Fixing Agreement 2 but no new Inpayment
Agreement. However, business requirements in which Inpayment Agreement and
Condition Fixing are not identical are rare.
Contents of Unit
- Overview
- Setup of a Loan Related Insurance Policy
- Processing of an Insurance Policy
- Ending of a Loan Related Insurance Policy
- Configuration
Preparation
Create an account to which the insurance policy is to be assigned.
Replication to FI-CA or disbursement is not necessary.
Slide 8: Overview
The listed insurance types are only common examples. Other possible insurance
types are:
Occupational disability insurance
Property insurance
Pension insurance
Natural hazard insurance
The interface for exchanging data with the insurance company is allocated to CMS.
Slide 9/10: Overview
There are two possible scenarios for processing insurance policies linked to loan
accounts:
The customer already has an insurance contract and this should be linked to a
loan account. In this case, the insurance master data has to be delivered by the
insurance company or by the customer. The insurance company holds the
original insurance master data, the CMS stores a copy.
Insurance is sold in the context of loan origination. The bank acts as a broker for
the insurance company. In this case, the insurance master data is created first at
the bank. But the master data has to be delivered to the insurance company who
stores it in the main insurance master data system.
If the insurance company cooperates with an insurance tracking vendor (ITV), the
ITV could substitute the insurance company as regards data exchange, premium
payment, and so on. The scope of the involvement depends on the individual service
contract.
Slide 12: Setup – Insurance Master Data
The automatic import of insurance policy master data cannot be shown here; instead
Contents of Unit
- Overview
- Data Exchange
Putting the Unit in Context
Slide 8: Overview
At first, the figure shows a very high level business process for a loan account.
On the second level, the quantity of sub processes is only implied. Only sub
processes that are relevant for the integration of loans management and CMS
are named. The processes during the contract management phase, in particular,
are just examples.
The diagram of components shows a scenario with the integration of account
origination in CRM and collateral management in banking services. The
account origination is only mentioned to show the whole business process. It is
not necessary to use the integration of loans management and CMS.
Without account origination in CRM, the loan account and the collateral
constellation would be created manually or by another system (integration using
enterprise services).
Slide 9: Overview
Note that the term ‘Receivable’ does not mean the same thing in CMS as it does in
loans management!
In CMS, receivables are the different accounts and so on, that should be
collateralized.
In loans management receivables are expected payments
System Preparation
To show the delivery of a new loan account and the changes during its life cycle, it is
useful to prepare a collateral agreement with a collateral object in advance.
Check the receivable value and the coverage gab in the collateral agreement.
Go to Calculations tab page:
Check the Max Risk (80,000) and the Curr Risk (0.00) in the line Receivable
Value
Check the Max Risk (30,000) and the Curr Risk (0.00) in the line Coverage
Gap.