CONFIG_TXS_2009343411320742153

Configuration Guide for Funding Management (FS-TXS)

Page 1

Configuration Guide

Funding Management

(FS-TXS)

Release 2.0

Status: 2009-03-20


Page 2

Copyright © Copyright 2005 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. These materials are subject to change without notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML, and W3C are trademarks or registered trademarks of the W3C, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only without representation or warranty of any kind. And SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.


Page 3

Introduction .......................................................................................................................................4

1 Basic Settings ............................................................................................................................5 1.1 Number Ranges .....................................................................................................................5 1.2 Specify Logging Settings ........................................................................................................5 1.3 Define RFC Systems ..............................................................................................................7

2 Funding Portfolio .......................................................................................................................7 2.1 Creating Funding Portfolios ....................................................................................................7 2.2 Assign Funding Categories.....................................................................................................8 2.3 Assign Interest Rates .............................................................................................................8

3 Funding Types ...........................................................................................................................9 3.1 Define Funding Types ............................................................................................................9 3.2 Assign Business Transaction ................................................................................................ 10 3.3 Assign Product Types .......................................................................................................... 10

4 Funding Transaction ................................................................................................................ 11 4.1 Define Key Figures ............................................................................................................... 11

5 Cash Flows ............................................................................................................................... 12 5.1 Define Internal Cash Flow Components ................................................................................ 12 5.2 Assign Cash Flow Category ................................................................................................. 13 5.3 Define Mapping of Cash Flow Components .......................................................................... 13

6 Investor Contracts ................................................................................................................... 14 6.1 Define Intervals Tolerances .................................................................................................. 14 6.2 Assigning Flow Types and Conditions to Contract Types ...................................................... 15 6.3 Defining Flow Type for Application Function ......................................................................... 15 6.4 Define Discount .................................................................................................................... 16

7 Monitoring ................................................................................................................................ 17 7.1 Define Events ....................................................................................................................... 17 7.2 Define Event Categories ....................................................................................................... 18 7.3 Define Handling Notes.......................................................................................................... 19 7.4 Assign Events and Handling Notes ....................................................................................... 19

8 Customer-Specific Enhancement Options (BAdI) .................................................................. 20 8.1 Application Logic .................................................................................................................. 20 8.2 Inbound interfaces ................................................................................................................ 23 8.3 Outbound interfaces ............................................................................................................. 27


Page 4

Introduction SAP Funding Management is a component of the SAP for Banking solution architecture and is used to fund assets. It is the goal of this application component to support funding processes. SAP Funding Management supports the structuring (pre-closing) as well as the processing (post-closing) of funding transactions. Two different scenarios are supported:

Syndication Scenario

This scenario consists of the funding of asset pools with one or more investors SAP Funding Management supports pool structuring by providing extensive selection and sampling functions. To manage the investors participating in the consortium, the creation and maintenance of investor contracts based on flexible conditions is provided. SAP Funding Management also ensures the aggregation and distribution of the funded cash flows for the asset pool. This gives you the option of distributing due payments automatically of manually for optimum control of payment distribution. A series of provided business transactions lets you manage the entire life cycle of a syndication. For example, the business transactions replenishment and asset buyback as well as loss allocation are offered to investors.

Securitization Scenario

This scenario supports the securitization of asset pools. For this purpose, SAP Funding Management provides an interface for the integration of each SPV. This permits you to tender the assets to be securitized in the form of an SPV sales file. The assets bought by the SAP are read on file basis and lead to the corresponding structuring of the asset pool of the funding transaction.

It is valid for both scenarios that the underlying funding conditions are defined by creating a funding program. This includes, for example, the determination of the permitted asset class (such as loan contracts), entering the maximum funding amount and specifying the maximum funding period. On the basis of a funding program, a concrete funding occurs is specified in the form of a funding transaction. All parameters for a syndication or securitization are defined in detail with a funding transaction. This includes the specification of the cash flow components to be funded (for example, repayment and interest), structuring the asset pool as well as details specifications for payment distribution (automatic or manual payments). To enable you to monitor the complete term phase of a funding transaction, the monitoring of events of the contract managing systems and the execution of internal monitoring functions (triggers) are provided. You can make the settings for these monitoring functions individually for each funding transaction.

The configuration of SAP Funding Management is described below: This configuration guide is structured largely according to this process flow. First the basic settings are described, followed by the descriptions for the configuration of funding programs and funding transactions. There are separate sections for setting up investor contracts for the "syndication" scenario and for defining the parameters for payment distribution. The conclusion of the implementation guide consists of a description of monitoring settings and options for the modification-free enhancement of Funding Management.

Navigation to the Implementation Guide (IMG) for SAP Syndications Management

Transaction: SPRO IMG Structure: Funding Management


Page 5

1 Basic Settings

1.1 Number Ranges 1.1.1 Use

A series of business objects has a number range interval that you have to define separately. You have to maintain the following number ranges for them:

Number Range Short Description Funding Programs Specify Number Range Interval for Funding Programs Investor Agreements Specify Number Range Interval for Investor Agreements Funding Transactions Specify Number Range Interval for Funding Transactions Investor Contract Templates Specify Number Range Interval for Investor Contract

Templates Condition Items Specify Number Range Interval for Condition Items of

Investor Contract Templates Trigger Specify Number Range Interval for Triggers (internal

monitoring functions in Monitoring)

1.1.2 Activities

Navigation in the Implementation Guide (IMG)

Basic Settings Number Ranges

Create a number range interval with the number 01 for each number range.

1.2 Specify Logging Settings 1.2.1 Use SAP Funding Management offers a variety of options for technical logging. You can configure logging for different subareas of the application and activate these separately. Logs are available for online reports (ONLINE), for batch processing (BATCH), for inbound interfaces (INBOUND), and for outbound interfaces (OUTBOUND). A developer trace (TRACE) is also available.

You can specify the following parameters for each log:


Page 6

Parameter Short Description Collect? This indicator controls whether the generated messages are to be collected

and returned to the caller. Returning messages is relevant only for technical interfaces but not for the execution of reports (and so on) by users. Collecting and returning is important for calls made by RFC. The technical inbound interfaces (Services) for SAP Funding Management can then return error messages and so on to the systems that delivered them. If this is not necessary, you can switch off the response here.

Write? This indicator controls whether messages are issued directly when a report is executed. If a report is started directly, the messages are display on the screen right after it has been executed. If a report is started in the background, the messages are collected as a spool request and can be evaluated by the Job Selection Overview.

SAP Log? This indicator controls whether the messages should be written to the SAP application log during logging. The generated application logs can be evaluated in the SAP application log. All logs are stored under the object /TXS/ and the corresponding subobjects. The batch reports usually write messages to the SAP application log.

Continue? This indicator controls whether the last application log of the same name is updated. If you set this indicator, no new application log is generated. Instead, the last application log of the same name and from the same day is used again. If none exists, a new log is created. The indicator has an effect only if the SAP Log indicator is set.

1.2.2 Activities


Basic Settings Specify Settings for Logging

Configure the logging settings according to your requirements

1.2.3 Example

Log Name Log Description Collect? Write? SAP Log? Continue?

BATCH Batch reports X

INBOUND Inbound interfaces X X

ONLINE Online reports X

OUTBOUND Outbound interfaces X

TRACE Developer trace


Page 7

1.3 Define RFC Systems 1.3.1 Use SAP Funding Management supports the distribution of application systems with the option of maintaining RDC connection for the required feeder systems and downstream systems. To use SAP Funding Management, you need to have access to SAP Loans Management Business Suite Edition 2005. You use SAP Loans Management to manage investor contracts (loans taken). However, it is possible (but not necessary) to access this application component remotely. To do so, you have to maintain an RFC target address for the CML Investor Contract system. You can also use SAP Loans Management to fund loan contracts (loans given). You can also set up an RFC connection for this use. An entry for the CML Loans system is required for this. SAP Funding Management uses the SAP Business Partner for Financial Services to manage business partner information. You can maintain RFC access to the application components by making an entry for the BP Investor system.

1.3.2 Activities


Basic Settings Define RFC Systems

If RFC access to the applications components SAP Loans Management Business Suite Edition 2005 or SAP Business Partner for Financial Services is required, you have to make entries for the respective RFC target address in the above mentioned Customizing activity.

2 Funding Portfolio

2.1 Creating Funding Portfolios 2.1.1 Use By defining a funding portfolio (funding), you determine the set of assets to be funded. With the funding portfolio you define the asset category (for example, leasing contract or loan contract) as well as the permissible funding types for each. You have to assign a funding portfolio to each funding program when you create it. By doing so, you use the funding portfolio to define essential parameters for funding.

2.1.2 Activities


Funding Portfolio Create Funding Portfolio

For every funding portfolio, you need to enter a sequential number, a name, and an asset category (such as leasing). You also have to define the current status of the funding portfolio. You can block an existing portfolio from new funding processes using the status value. To do so, set the status to closed.

2.1.3 Example

Funding Portfolio

Name of the Funding Portfolio

Asset category

Funding Status

1 Leasing Leasing Open

2 Loans Loans Open


Page 8

2.2 Assign Funding Categories 2.2.1 Use You have to assign at least one funding category to each funding portfolio. SAP Funding Management supports the funding categories loans, receivables sale, external funding, and securitization.

2.2.2 Prerequisites To assign funding categories, you need to have maintained the funding portfolios (see 2).

2.2.3 Activities


Funding Portfolio Assign Funding Categories

You need to define at least one funding category for each funding portfolio.

2.2.4 Example

Funding Portfolio

Funding Category

1 Loans

1 Receivables Sale

1 External Funding

1 Securitization

2 Loans

2 Receivables Sale

2 External Funding

2 Securitization

2.3 Assign Interest Rates 2.3.1 Use Net present value calculations are made in SAP Funding Management to evaluate assets for a variety of purposes. The interest rate you need for this is usually derived for the funded asset from the respective funding transaction For non-funded assets, you must define the funding interest rate explicitly You make this default setting in Customizing for SAP Funding Management for each asset category.

2.3.2 Prerequisites The assigned reference interest rates have to be maintained in tables V_T056R and V_T056P.

2.3.3 Activities


Page 9


Funding Portfolio Assign Interest Rates

You have to define a reference interest rate for discounting of non-funded assets for each asset category.

2.3.4 Example

Asset Category

Reference Interest Rate

Leasing Refzins_L

Loans Refzins_D

3 Funding Types

3.1 Define Funding Types 3.1.1 Use Funding categories are predefined by SAP Funding Management (see section 2.2) By defining funding types, you can configure the characteristic values for them individually. Each funding type is therefore based on a funding category. You also have to define whether the funding type permits automatic and/or manual payment forwarding. You can also define whether a switch between payment forwarding methods is permissible in the term of a funding transaction. Because the funding types are indirectly assigned to a funding portfolio through the funding category and because each funding program has to reference a funding portfolio, the permissible funding types for funding programs are defined in this way.

3.1.2 Prerequisites The respective funding category for the funding type must be assigned to a funding portfolio (see 2.2).

3.1.3 Activities


Funding Types Define Funding Types

You have to assign at least one funding type for a funding categories that is assigned to a funding portfolio.

3.1.4 Example

Fdg Type

Description of the Funding Type

Payment Forwarding Type

Change Payment Forwarding Type

10 Loans No Restrictions Permitted

20 Sale of Single Receivable No Restrictions Permitted

30 Securitization

40 External Funding


Page 10

3.2 Assign Business Transaction 3.2.1 Use For each funding type, you have to define the permissibility of the business transactions provided by SAP Funding Management. Asset and transaction buyback, loss allocation and recovering loss allocation are all possible business transactions, as are the capital adjustment of investor contracts and the replenishment of funding transactions.

3.2.2 Prerequisites To assign business transaction categories, you need to have maintained the funding types (see 3).

3.2.3 Activities


Funding Types Assign Business Transactions

Define the permitted business transactions for each funding type.

3.2.4 Example

3.3 Assign Product Types 3.3.1 Use Investor contracts (loans taken) are created in the syndication scenario for the management of funded amounts.There you have to define exactly one product type and one loans type for the investor contracts for the funding types Loans and Receivables Sale.

Fdg Type Type of Business Transaction

10 Asset Buyback

10 Loss Allocation

10 Recovering Loss Allocations

10 Transaction Buyback

10 Capital Adjustment

10 Replenishment

20 Asset Buyback

20 Loss Allocation

20 Recovering Loss Allocations

20 Transaction Buyback

20 Capital Adjustment

30 Replenishment

40 Replenishment


Page 11

3.3.2 Prerequisites The assigned product types and loans types have to be configured accordingly in SAP Loans Management Suite Edition 2005.

3.3.3 Activities


Funding Types Assign Product Types

3.3.4 Example

4 Funding Transaction

4.1 Define Key Figures 4.1.1 Use Transaction-specific key figures are calculated to support decision making when structuring and processing funding transactions. SAP Funding Management provides a series of standard key figures. You can implement additional, customer-specific key figures using the /TXS/RATIO BAdI (see 8.1). To calculate and display transaction key figures, you need to define these in Customizing for SAP Funding Management.

4.1.2 Activities


Funding Transaction Define Key Figures

In this Customizing activity, you need to enter a unique number and a description for each key figure. You can then use the key figures when you create a funding transaction. For all key figures activated for a transaction, the /TXS/RATIO BAdI (see 8.1), in which the calculation is made, is called at runtime.

Fdg Type Product Type Loan Type

10 37B 22

20 37B 22


Page 12

4.1.3 Example The following key figures are provided in the standard system:

Key Figure ID Name 1 Number of Assets 2 Weighted average remaining term 3 Outstanding receivables of the 10 largest assets 4 Total outstanding receivables 5 Total residual value 6 Total nominal value 7 Total Installments

5 Cash Flows

5.1 Define Internal Cash Flow Components 5.1.1 Use Cash flows can be funded for different components on a transaction-specific basis. In SAP Funding Management, you need to define the granularity for cash flow components. When you create a funding transaction, you can select cash flow components that are maintained in Customizing for the funding process. Consequently, for example, you can fund just individual cash flow components of an asset (for example, installments only) in a transaction.

5.1.2 Prerequisites The respective contract-managing feeder system has to support the delivery of the cash flows according to the granularity that has been configured. During delivery, the cash flow structure of the feeder system has to be mapped to the internal cash flow components of SAP Funding Management.

5.1.3 Activities


Cash Flows Define Internal Cash Flow Components

You need to enter a unique number and description for each cash flow component.

5.1.4 Example

CF Comp. Name

1 Repayment

2 Interest

3 Remaining Value

4 Installment

5 Charge


Page 13

5.2 Assign Cash Flow Category 5.2.1 Use In SAP Funding Management, cash flows are divided into the categories of installment and residual value. This distinction is used for various displays and calculations.

5.2.2 Prerequisites Internal cash flow components must be defined in SAP Funding Management (see 5) before cash flow categories can be assigned.

5.2.3 Activities


Cash Flows Assign Cash Flow Category

You assign a cash flow category (installment or residual value) to each cash flow component.

5.2.4 Example

CF Cat. CF Comp.

Installment 1

Installment 2

Installment 4

Installment 5

Residual value 3

5.3 Define Mapping of Cash Flow Components 5.3.1 Use The structure of the cash flows defined in SAP Funding Management (see 5) has to match the structure used in the corresponding contract managing system (for example, the loans system). For this reason, you have to map the cash flow components supplied and used externally to the internal cash flow components in SAP Funding Management, depending on the asset category (for example, loan contract).

5.3.2 Prerequisites The definition of internal cash flow components (see 5) as well as the assignment of cash flow categories (see ??) needs to be completed.

5.3.3 Activities


Cash Flows Define Mapping of Cash Flow Components

For each cash flow component supplied by the contract-managing feeder system, you have to assign an internal cash flow component based on the asset category.


Page 14

5.3.4 Example

Asset Category External CF Comp. Internal CF Comp.

Leasing CHARGE 5

Leasing INSTALLMENT 4

Leasing REMAINING VALUE 3

Loans 0110 2

Loans 0115 1

Loans 0120 1

Loans 0125 1

Loans 3210 2

Loans 3215 1

Loans 3220 1

Loans 3225 1

6 Investor Contracts

6.1 Define Intervals Tolerances 6.1.1 Use Payment intervals are used in SAP Funding Management for the conditions of investor contracts in the syndication scenario as well as for discounting assets. You can configure the length of possible payment intervals. For each payment interval, you need to specify a description and the length in months.

6.1.2 Activities


Investor Contracts Define Payment Intervals

Define all required payment intervals.

6.1.3 Example

Frequency Description

1 Monthly

3 Quarterly

6 Half-yearly

12 Annually


Page 15

6.2 Assigning Flow Types and Conditions to Contract Types 6.2.1 Use The specific features of an investor contract depend on the product type used in SAP Loans. All investor contract product types, however, are based on product type 370 (investor contract). You define the permitted condition types for investor contracts based on the company codes that are used, You can only use the assigned condition types for creating investor contracts. You also have to specify for each condition type whether it is valid for the payment form assumed payment.

6.2.2 Prerequisites You must have configured the assigned condition types in SAP Loans Management Business Suite Edition 2005.

6.2.3 Activities


Investor Contracts Assign Flow Types and Conditions to Contract Types

Define all permitted condition types based on the company code for condition-based investor contracts. In the Assume Pay column, you define the forms of payment permitted.

6.2.4 Example

Co.Code Contract Type Assume Pay

Flow /Cond.

0001 Condition-Based 5110










0001 Condition-Based X 5150

0001 Condition-Based X 5155

6.3 Defining Flow Type for Application Function 6.3.1 Use In SAP Funding Management, certain application functions (such as loss allocations) lead to flows in investor contracts. You must define the flows that you can assign in each application function in SAP Funding Management. When you do this, you also define the application function flow types that


Page 16

generate a payment for the investor contract. If you use the appropriately configured flow type and set the indicator for immediate generation of incoming payments, you can ensure the reduction of contract capital for investor contracts but that no payments to investors (such as loss allocations) are generated.

6.3.2 Prerequisites To enter flow types for application functions in full, you must have maintained the indicators used for the immediate generation of incoming payments in SAP Loans Management Business Suite Edition 2005.

6.3.3 Activities


Investor Contracts Define Flow Type for Application Function

You have to define all the permitted flow types according to the company code and application function (such as loss allocation, buyback, and so on). You also need to define whether a payment is generated immediately when the debit position is created for the respective flow type. To do so, you have to set a corresponding indicatorError! No bookmark name given..

6.3.4 Example

Co.Code Application Function Flow Type OP

0001 Buyback/Termination – Buyback Flow I025

0001 Buyback/Termination – Discount Charges I025 81

0001 Buyback/Termination – Markup I030

0001 Buyback/Termination – Markdown I025 81

0001 Loss Allocation – Buyback Flow I025 81

0001 Loss Allocation – Loss (Charge) I036

0001 Late Recovery - Recovery I037

0001 Contract Creation – Incoming Payment I000

0001 Capital Adjustment - Unscheduled Repayment I025

6.4 Define Discount 6.4.1 Use To end a funding transaction automatically, execute the report End Transaction (Report: /TXS/R_BATCH_TRA_END). To end a funding transaction, a number of prerequisites need to be fulfilled. One of these is that no discount exists for any of the assigned investor contracts. You have to specify the flow types that lead to the posting or writing off of a discount in SAP Funding Management.

6.4.2 Prerequisites You have to maintain the flow types for the posting and writing-off of discounts in SAP Loans Management Business Suite Edition 2005.


Page 17

6.4.3 Activities


Investor Contracts Define Discount

6.4.4 Example

Flow type Discount

8803 Written off

I040 Posted

I883 Written off

7 Monitoring

7.1 Define Events 7.1.1 Use Events are the focal point in monitoring. They can be divided into two classes. External events are triggered by operative feeder systems (such as loan systems). Depending on the asset category (for example, loan contract) you have to maintain all external events that are to be taken into account in Monitoring. In addition to external events, a range of internal events also affects the funding process. These include, for example, internal events that are triggered on the basis of customer-specific monitoring criteria (triggersError! No bookmark name given.). You also have to make the settings for all internal events in Customizing.

7.1.2 Prerequisites Creating external events depends on the range of events triggered and delivered by the respective feeder system. However, the number of internal events is predefined by SAP Funding Management.

7.1.3 Activities


Monitoring Define Events

You have to maintain all external and internal events in SAP Funding Management. You have to enter an identifying description (key) as well as en event text for external events. You have the option of adjusting the event text for internal events.


Page 18

7.1.4 Example

Event Type Event ID

Event Text

Ext. Leasing BUYO Purchase at End-of-Lease

Ext. Leasing EBUY Early Buyout

Ext. Leasing INSO Insolvency

Ext. Leasing … …

Ext. Loans CREA Creation of a new loan

Ext. Loans FLOW Change to the cash flow

Ext. Loans LOAN Loan change

Ext. Loans … …

Trigger 1 Payment Default for Asset

Trigger 2 Transaction losses exceed defined maximum value

Trigger 3 Transaction losses exceed defined warning limit

Trigger 4 Asset does not match the selection criteria

Business Operations 1 Buyback performed

Business Operations 2 Loss allocation performed

Business Operations 3 Recovering loss allocations performed

Business Operations 4 End of transaction reached

Business Operations 5 No assets in the transaction

Business Operations 6 Termination performed

Business Operations 9 Transaction was closed

Business Operations 10 Replenishment performed

Business Operations 11 Capital adjustment performed

7.2 Define Event Categories 7.2.1 Use In monitoring, you can group events into event categories. In this way, you can group events that come from different sources according to their semantics (see 7.4 ). For example, you could define a default event category Internal and external events in this category allocate a status to the asset in question that is to be considered a default. In Funding Management, you have to maintain all event categories that you require for Monitoring.

7.2.2 Activities


Monitoring Define Event Categories

You need to enter a unique number and description for each event category.


Page 19

Event Category ID Description of the Event Category 1 Normal 2 Loss 3 Non Compliance 4 Liquidation 5 Check 6 Early Termination 7 Interruption of Revolving 8 Termination of Revolving

7.3 Define Handling Notes 7.3.1 Use You can store transaction-based handling notes for internal and external events in Monitoring by SAP Funding Management (see 7.4). These handling notes are used to support decision making in the processing of funding transactions. You have to maintain all required handling notes in SAP Funding Management.

7.3.2 Activities


Monitoring Define Handling Notes

You need to enter a unique number and description for each handling note.

7.3.3 Example

Handling Note ID

Handling Note Description

1 Create asset buyback

2 Perform a loss allocation

3 Adjust conditions

4 Terminate transaction early

5 Check transaction

7.4 Assign Events and Handling Notes 7.4.1 Use When you create a funding transaction, you have to assign monitoring-relevant internal events (triggers) and external events to an event category (see 7.2) and to a handling note (see 7.3). This assignment depends on how the respective funding transaction is actually structured. To simplify the assignment, the system generates default values when you create a transaction. These default values must be defined in Customizing for SAP Funding Management.


Page 20

7.4.2 Prerequisites You need to have maintained the event categories (see 7.2) and the handling notes (see 7.3) to be able to make assignments.

7.4.3 Activities


Monitoring Transaction-Independent Event Configuration

You need to link all monitoring-related internal and external events with an event category and a handling note.

7.4.4 Example

Event Type Event Event Category Handling Note

Ext. Leasing BUYO 5 5

Ext. Leasing EBUY 5 5

Ext. Leasing INSO 2 1

Ext. Leasing …

Ext. Loans CREA 5 5

Ext. Loans FLOW 5 5

Ext. Loans LOAN 5 5

Ext. Loans … 5 5

Trigger 1 2 1

Trigger 2 6 4

Trigger 3 1 5

Trigger 4 3 1

8 Customer-Specific Enhancement Options (BAdI)

8.1 Application Logic 8.1.1 BAdI: Key Figure Calculation for Transactions

8.1.1.1 Use The /TXS/TRA_RATIOS Business Add-In (BAdI) enables you to implement key figures for transactions. The calculation results are displayed on the KeyFigures tab page on the transaction user interface. However, you must first create key figures in Customizing for SAP Funding Management (see 4). On the Details tab page, you can then select these key figures and activate them for the relevant transaction. When you switch to the KeyFigures tab page, the /TXS/TRA_RATIOS BAdI is called, which then (re)calculates the activated key figures. Key figures are calculated for information purposes only and used to support decision making. The process flow is not affected by the results. The default implementation of the /TXS/TRA_RATIOS BAdI already calculates certain key figures. You can include additional key figures in the implementation. In this case, the BAdI is supplied with a reference to the respective funding transaction at runtime.


Page 21

8.1.1.2 Prerequisites Before you implement further key figures, you have to create them in the Customizing activity Define Key Figures (see 4 ). In the BAdI, you then need to implement the calculation algorithm for the additional key figures.

8.1.1.3 Standard Setting The BAdI is active in the standard SAP system. The default source code calculates the following key figures:

Key Figure ID Description 1 Number of Assets 2 Weighted average remaining term 3 Outstanding receivables of the 10 largest assets 4 Total outstanding receivables 5 Total remaining value 6 Total nominal value 7 Total Installments

Key figures are calculated only if they have been activated for the respective transactions on the Details tab page.

8.1.1.4 Activities You need to implement a calculation algorithm for each additional key figure. Key figures and algorithms are assigned in the BAdI using the key figure ID (see 4).

8.1.1.5 Example Enter one of the new key figures XYZ:

1. Enter XYZ in Customizing (see 4) with ID 8.

2. Change the source code in the BAdI so that a calculation result is generated for the key figure with ID 8.

8.1.2 BAdI: Customer-Specific Trigger

8.1.2.1 Use You use the /TXS/TRA_TRIGGER BAdI to implement customer-specific triggers. Triggers allow you to define transaction-specific monitoring criteria. They can be created to monitor a funding transaction and generate an event when a monitoring-specific rule is violated. The specific trigger definition depends on the object being monitored. SAP Funding Management is shipped with a series of standard triggers. You can implement additional triggers using this BAdI.

8.1.2.2 Prerequisites Before you implement the BAdI, define all events that can be triggered by customer-specific triggers (see 7 ). You also need to configure these events (see 7.4) to be able to view them in monitoring in SAP Funding Management when you create a funding transaction.

8.1.2.3 Standard Setting This BAdI is active in the standard SAP system. The /TXS/R_TRIGGER report calls it for funded transactions after the standard triggers have been started, provided that customer-specific triggers were selected for execution on the report selection screen. When it is called, it is supplied with events


Page 22

for the customer triggers, again provided that these were activated for the relevant transaction when the transaction was prepared. There is no standard implementation.

8.1.2.4 Activities An implementation must be created for the BAdI. In this implementation, all customer-specific monitoring rules are defined. To create the monitoring rule, the BAdI is supplied with a reference to the funding transaction monitored at runtime.

8.1.2.5 Example You may be required to monitor the transaction volume at runtime. You can implement this monitoring rule in the BAdI by evaluating the transaction volume and, if required, generating an event. As a result, the event is displayed in monitoring in SAP Funding Management together with all other monitoring-relevant events for the transaction.

8.1.3 BAdI: Net Present Value Calculator

8.1.3.1 Use You use the BAdI /TXS/BADI_NPV to adjust the central algorithm for calculating net present values from cash flows for customer-specific requirements. You use this BAdI for all net present value calculations in Funding Management.

8.1.3.2 Standard Setting A default implementation (fallback implementation /TXS/CL_BADI_NPV) is available.

8.1.3.3 Activities You can create an additional implementation for the BAdI if required and mark it as active, so that the default implementation is not used. You can have only one active implementation. The following functions are available in the BAdI:

CALCULATE Calculates the NPV for a specified cash flow. In addition to the cash flow to be discounted, the following are

included in the method as parameters : - Calculation Date

- Indicator of whether calculation date is inclusive (for interest days)

- Indicator of whether installment is excluded on the calculation date

- Interest rate

- Interest calculation method

- Interest calculation type (linear or exponential)

- Payment frequency (in months)

- Factory calendar for interest calculation

8.1.4 BAdI: Asset Enhancement

8.1.4.1 Use You use the BAdI /TXS/BADI_ASSET to display enhancements to asset data structures in the application Display Assets.

8.1.4.2 Prerequisites Customer-specific fields were added to the DDIC structures /TXS/STR_AST_DATA_LEASING or


Page 23

/TXS/STR_AST_DATA_LOANS with APPEND. They are therefore part of the database table /TXS/AST_BUFFER and used in the selection rules for funding programs and funding transactions. The additional fields are displayed there automatically. No additional measures need to be taken.

8.1.4.3 Standard Setting There is no default implementation.

8.1.4.4 Activities If required, you create an implementation for the BAdI and mark it as active. You can have only one active implementation.

This BAdI includes a screen enhancement that you use to add a customer-specific screen in the asset display on the Details tab page. You can display the additional fields here. Data exchange occurs according to the guidelines described in the chapter on the Enhancement Framework in the SAP Library. You use the methods GET_DATA and SET_DATA to transfer the data to be displayed.

The following methods are available in the BAdI:

SET_DATA The Display Assets application uses this method to transfer enhancement data for the current assets to the BAdI implementation. This occurs before the customer screen is displayed (in the PBO of the subscreen container). The method implementation saves the data temporarily.

GET_DATA In its PBO, the customer-specific screen uses this method to query the data that was specified by SET_DATA and to place it in the screen fields.

Currently, Display Asset does not let you change data. You can also use the interface described above to transfer changed contents in the opposite direction (SET_DATA from the screen and GET_DATA in Display Asset).

8.2 Inbound interfaces 8.2.1 BAdI: Mapping for Service "Asset Existence Check"

8.2.1.1 Use You use BAdI /TXS/BADI_IN_MAP_ASSET_EXISTS to implement customer-specific enhancements for mapping inbound data of the service Check Asset Existence to the internal data structure in Funding Management. It is called up after the mapping of incoming data that is always implemented in the service. It is used to change contents or fill additional fields, if necessary. This can become necessary in connection with the enhancement of the asset database table /TXS/AST_BUFFER This BAdI can be implemented multiple time. This means that multiple active implementations exist and that this can be called up in succession.

8.2.1.2 Prerequisites You use the service Check Asset Existence to check for the existence of assets in Funding Management from external systems.


8.2.1.4 Activities You can create an implementation for the BAdI if necessary.


Page 24

The following functions are available in the BAdI:

MAPEXT2INT Enhancement of mapping from external asset ID and feeder system.

8.2.1.5 Example You can convert the supplied external asset ID here.

8.2.2 BAdI: Mapping for Service "Change Asset ID"

8.2.2.1 Use You use BAdI /TXS/BADI_IN_MAP_ASSET_ID_CHAN to implement customer-specific enhancements for mapping inbound data of the service Change Asset ID to the internal data structure in Funding Management. It is called up after the mapping of incoming data that is always implemented in the service. It is used to change contents or fill additional fields, if necessary. This can become necessary in connection with the enhancement of the asset database table /TXS/AST_BUFFER.

8.2.2.2 Prerequisites You use the service Change Asset ID to change assets in Funding Management from external systems.




MAPEXT2INT Enhancement of the mapping external asset data.

8.2.2.5 Example You can convert the supplied external asset ID here.

8.2.3 BAdI: Mapping for Service "Mass Delivery of Assets"

8.2.3.1 Use You use BAdI /TXS/BADI_IN_MAP_ASSET_SEND to implement customer-specific enhancements for mapping inbound data of the service Mass Delivery of Assets to the internal data structure in Funding Management. It is called up after the mapping of incoming data that is always implemented in the service. It is used to change contents or fill additional fields, if necessary. This can become necessary in connection with the enhancement of the asset database table /TXS/AST_BUFFER.

8.2.3.2 Prerequisites You use the service Mass Delivery of Assets to change assets in Funding Management from external systems.



Page 25




8.2.3.5 Example Here you can add customer-specific contents that are already available in the SAP System to the supplied data.

8.2.4 BAdI: Mapping for Service "Asset Split"

8.2.4.1 Use You use BAdI /TXS/BADI_IN_MAP_ASSET_SPLIT to implement customer-specific enhancements for mapping inbound data of the service Asset Split to the internal data structure in Funding Management. It is called up after the mapping of incoming data that is always implemented in the service. It is used to change contents or fill additional fields, if necessary. This can become necessary in connection with the enhancement of the asset database table /TXS/AST_BUFFER.

8.2.4.2 Prerequisites You use the Asset Split service to split assets in Funding Management from external systems. This means you can split an existing asset into two or more new assets.





8.2.4.5 Example Here you can add customer-specific contents that are already available in the SAP System to the supplied data.

8.2.5 BAdI: Import ABS Files

8.2.5.1 Use You use BAdI /TXS/BADI_ABS_IMPORT_FILE to implement both the file import interface and the customer-specific enhancements for mapping inbound data from the SPV data delivery to the internal data structure in Funding Management. The BAdI is called at the beginning of the functions Complete Sales and Process Position Comparison.

8.2.5.2 Prerequisites You are funding assets in the transactions for funding type ABS.


Page 26

8.2.5.3 Standard Setting The SAP file selection dialog and the standard file import function GUI_UPLOAD are implemented as the default. The file format is CSV. The conversion of CSV to SAP formats has also been implemented.

8.2.5.4 Activities If you want to use other file import functions or if you need to enhance mapping, you have to create a customer-specific implementation for the BAdI.


IMPORT_ABS_FILE Import of ABS Files

8.2.5.5 Example Here you can implement the processing and saving of additional data from the ABS file.

8.2.6 BAdI: Mapping for Service "Delivery of Assets from CML"

8.2.6.1 Use You use BAdI /TXS/BADI_IN_MAP_LOAN_SEND to implement customer-specific enhancements for mapping inbound data of the service Delivery of Assets from CML to the internal data structure in Funding Management. It is called up after the mapping of incoming data that is always implemented in the service. It is used to change contents or fill additional fields, if necessary. This can become necessary in connection with the enhancement of the asset database table /TXS/AST_BUFFER.

8.2.6.2 Prerequisites You use the asset-side delivery of loans from CML with the Asset Split service.




MAPEXT2INT Enhancement of Mapping of CML Data to Internal Asset Data

8.2.6.5 Example Here you can complete the mapping of loans to assets in Funding Management. Here you have the option of filling enhancements (APPENDS) to asset table /TXS/AST_BUFFER with contents from VDARL, and so on.


Page 27

8.3 Outbound interfaces 8.3.1 BAdI: Loans Proxy

8.3.1.1 Use You use the /TXS/PROXY_LOANS BAdI to implement the outbound interface to the passive system. The passive system manages the investor contracts. The architecture of the outbound interfaces in SAP Funding Management comprises two interfaces – one permanent, internal interface, and one interface that can be adapted to the external system. The function calls to the external system are encapsulated in this BAdI. It comprises all key functions for creating and managing investor contracts. You can use this BAdI to adapt SAP Funding Management to external passive systems. Create an implementation for this BAdI only if you do not want to use the standard implementation.

8.3.1.2 Prerequisites To implement this BAdI, you must have detailed knowledge of the data available in SAP Funding Management and knowledge of managing investor contracts.

8.3.1.3 Standard Setting The BAdI has a default implementation that encapsulates all of the functions for creating and managing investor contracts in SAP Loans Management Business Suite Edition 2005. SAP Funding Management manages the basic data for creating investor contracts.

8.3.2 BAdI: Proxy Loans Mapping

8.3.2.1 Use You use the /TXS/PROXY_LOANS_MAP BAdI in SAP Funding Management to implement mapping functions for calls to the passive system for investor contracts. SAP Funding Management uses a defined dataset to create and manage investor contracts and to communicate with SAP Loans Management Business Suite Edition 2005. However, the system does not fill all incoming data structure fields in SAP Loans Management Business Suite Edition 2005 completely. Implement this BAdI if you want to fill other fields in these structures with business data and transfer them to SAP Loans Management Business Suite Edition 2005. You call this BAdI every time you want to create or change investor contracts.

8.3.2.2 Prerequisites Note: A number of files in these structures have control functions in SAP Loans Management Business Suite Edition 2005. Changing the contents of these fields can lead to undesirable results in SAP Loans Management Business Suite Edition 2005 (such as inconsistencies in the cash flow). Perform Customizing for SAP Funding Management and SAP Loans Management Business Suite Edition 2005 completely.

8.3.2.3 Standard Setting This BAdI has a standard implementation of the MAP_CONTR_MAIN_DATA function. In this implementation, the maturity of the investor contract is calculated on the basis of the contract term.


Page 28

8.3.2.4 Activities The following functions are available in the BAdI:

MAP_CONTR_MAIN_DATA Mapping of Contract Master Data (Create)

MAP_PARTNER_DATA Mapping of Partner Data for Contract (Create)

MAP_CONTR_COND_DATA Mapping of Conditions for Contract (Create)

MAP_CONTR_MAIN_DATA_CHNG Mapping of Contract Master Data (Change)

MAP_PARTNER_DATA_CHNG Mapping of Partner Data for Contract (Change)

MAP_CONTR_COND_DATA_CHN Mapping of Conditions for Contract (Change)

MAP_POST_INPAYMENT Mapping of Posting Data

8.3.2.5 Example To fill the “Loan Type” field: Implement the MAP_CONTR_MAIN_DATA function. Assign the value to the STITEL field of structure C_STR_LOAN, taking the permitted values into account.

8.3.3 BAdI: Mapping for Outbound Service: Confirmation to CML

8.3.3.1 Use You use BAdI /TXS/BADI_OUT_MAP_CML_NFY to implement customer-specific enhancements for mapping outbound data of the service Confirmation to CML to the external data structure in CML. It is called up after the mapping of incoming data that is always implemented in the service. It is used to change contents or fill additional fields, if necessary.

8.3.3.2 Prerequisites You use the asset-side delivery of loans from CML.




MAPINT2EXT Enhancement of Mapping of Internal Asset Data to CML Data

8.3.4 BAdI: Outbound Service: Confirmation to Asset Source System

8.3.4.1 Use You use BAdI /TXS/BADI_SRV_ASSET_NFY to implement customer-specific enhancements for connections to asset source systems. You can implement a separate BAdI for each source system. The BAdI is informed about the change of funding status of an asset pool.

8.3.4.2 Prerequisites Assets delivered to the inbound service have a feeder system. This is used as a filter for the BAdI call.


Page 29

8.3.4.3 Standard Setting There is no default implementation. There is an implementation for the CML source system.



Execute Connection to an external source system, if required

8.3.5 BAdI: Export ABS Files

8.3.5.1 Use You use BAdI /TXS/BADI_ABS_EXPORT_FILE to implement both the file export interface and the customer-specific enhancements for mapping the internal data structure of Funding Management to the SPV outbound data. You call the BAdI as the last processing step for the functions Create Offer File and Create Position Comparison.

8.3.5.2 Prerequisites You are funding assets in the transactions for funding type ABS.

8.3.5.3 Standard Setting The SAP file selection dialog and the standard file export function GUI_DOWNLOAD have been implemented as the default. The file format is CSV. The conversion of SAP formats to CSV has also been implemented.

8.3.5.4 Activities If you want to use other file export functions or if you need to enhance mapping, you have to create a customer-specific implementation for the BAdI.


EXPORT_ABS_FILE Import of ABS Files

8.3.5.5 Example You can use this to implement the enrichment of additional data for the export of data.


Page 30

8.3.6 BAdI: Outbound Service: Business Operation Report

8.3.6.1 Use You use BAdI /TXS/BADI_SRV_BP_NFY to implement customer-specific enhancements for connections to any systems. You call this BAdI for the execution of all Business Operations. It provides the relevant information.

Asset Buyback

Capital Adjustment

Loss Allocation

Transaction Buyback

Replenishment

Change of Funding Status in a Transaction

.

8.3.6.2 Prerequisites None




Execute Connection to an external source system, if required

Date post:	20-Dec-2015
Category:	Documents
Upload:	prabhakar-vanam
View:	2 times
Download:	1 times

CONFIG_TXS_2009343411320742153

Documents