Account Origination Purpose

In the banking environment, you can use this scenario to support the advisory and application process for financial service products, such as consumer loans or real estate financing, and map this in the system. The scenario helps you to analyze customer data and asset targets, to calculate and create customerspecific quotations, to assess risk, and to conclude contracts. The scenario includes two application components: SAP Customer Relationship Management (SAP CRM) is used as a front-end application that you use to access the functions of various back-end applications. As a result, you have a central point of access for executing processes that previously ran on separate systems with redundant data and can integrate these processes in your companys overall system landscape. To map the account origination process, you need the following components: SAP CRM 2007 SAP NetWeaver 7.0: SAP NetWeaver Exchange Infrastructure (SAP NetWeaver XI) 7.0 You need at least one contract system for the operational management of contracts. As part of the scenario, SAP provides content for loans that is integrated with the following SAP contract and support systems: ECC 6.0 (SAP ERP 6.0) with EA-FINSERV using SAP Collateral Management (FS-CMS) ECC 6.0 (SAP ERP 6.0) with EA-FINSERV using SAP Loans Management (FS-CML)

The following functions are available for account origination:

To ensure the comfortable and simple handling of all functions that you need in the account origination process, you can use the role Financial Services Sales Manager (FS Sales Manager). For more information, see User Interface and Roles. You can map financial service products (FS products) in the system using a separate product type. You can also group together several products to form product bundles and create relationships between products. For more information, see Product. To maintain and manage customer data, you use the SAP business partner for financial services. For more information, see SAP Business Partner for Financial Services. To map your FS products in the system, you can enhance both the product master data and business transactions, and can also enhance distribution of the data to the back-end applications. For more information, see Enhancement of the Product Master and Business Transaction. You use Case Management to centrally manage and maintain the information for the origination process for a business partner. For more information, see Case Management in Account Origination. You can use the Business Rule Framework to perform checks during account origination, for example to verify completeness or consistency. For more information, see Business Rule Framework in Account Origination. You can use the FS Quotation transaction type to create and maintain quotations for financial services. For more information, see Maintenance of a Financial Service Quotation.

Financial Service Product (FS Product)

Definition
A data store for financing-relevant attributes that define the basic conditions for financial services.

Use
If you want to use FS products, note the following:
In account origination, you map the sales view of FS products, which means you cannot use these products in an operational context, as the calculation functions are located in the relevant back-end systems, such as loan management. When you create an FS product in SAP Customer Relationship Management (SAP CRM), you must create a corresponding product in the connected contract system. You must enter the same attribute values for these products in both systems. You then use derivation rules to assign the sales products from SAP CRM to the corresponding inventory products in the contract system.

Creating Financial Service Products

Use
You use financial service products (FS products) to map sales products from the financial services area in the system and use them in business transactions.

Prerequisites
To create FS products, you must have done the following:

In Customizing you have executed the report that creates the base hierarchy for FS products or you have created the base hierarchy manually. For more information, see the Implementation Guide (IMG) for Financial Services under Account Origination p Financial Service Product (FS Product) p Create Base Hierarchy for FS. Because SAP Customer Relationship Management (SAP CRM) maps only the sales view of products, you have to create the operational view of your products in the inventory management system. You have also assigned the operational products to the sales products in SAP CRM. For more information, see Connection of External Systems.

Set Types for Financial Service Products

Use
You use set types to group together attributes that describe a financial service product (FS product).

Features
SAP provides example set types for FS products of the categories Loans and Collateral Agreements. These set types are integrated in the account origination process, which means that when you use an FS product in the business transaction, the system adopts the settings that you entered in the product master data.

Set types that are integrated in the account origination process are also available to you in the Business Rule Framework (BRF) for the definition of rules. For more information, see Business Rule Framework in Account Origination. The following set types are available for the categories Loans and Collateral Agreements, for example: Set Types for FS Products Category Loans Loans Loans Loans Loans Loans Loans Loans Collateral agreement Set Type Name Age of applicant Term Interest fixing Interest and payments Usage category Premium and discount Payment structure Special arrangement Agreement type Set Type ID CRM_PROD_FS001 CRM_PROD_FS002 CRM_PROD_FS006 CRM_PROD_FS003 CRM_PROD_FS004 CRM_PROD_FS005 CRM_PROD_FS007 CRM_PROD_FS010 CRM_PR_FSCA01

The following set types are required for the categories of all product types: Set Types for All Product Types

Set Type Name Short text Units of measure Sales: Control fields, quantities Sales: Groupings

Set Type ID COMM_PR_SHTEXT COMM_PR_UNIT CRMM_PR_BTR CRMM_PR_SALESG

Loans: Age of Applicant

Use
You use the Age of Applicant set type (CRM_PROD_FS001) to specify that you want to sell a financial service product (FS product) to customers of a certain age group only.

Loans: Term

Use
You use the Term (CRM_PROD_FS002) set types to define the possible terms of a financial service product (FS product).

Definition of the term is only relevant for FS products of the category Consumer Loan.

Loans: Fixed Interest Period

Use
You use the Fixed Interest Period set types (CRM_PROD_FS006) to define the periods for which you guarantee a customer a fixed interest rate.

Definition of the fixed interest period is only relevant for FS products of the category Mortgage Loan

Loans: Interest and Payments

Use
You use the Interest and Payments set types (CRM_PROD_FS003) to define settings for interest calculation and loan disbursement.

Loans: Usage Category

Use
You use the Usage Category set types (CRM_PROD_FS004) to define the possible uses for a loan.

Loans: Premium and Discount

Use
You use the Premium and Discount set types (CRM_PROD_FS005) to define when you calculate the markdown for a payment or partial payment and credit it to the customer side.

Loans: Payment Structure

Use
You use the Payment Structure set type (CRM_PROD_FS007) to define the periods and one-time inflows and outflows of loan amounts. From a financial mathematics point of view, the payment structure has the character of a condition, and is the basis for determining the payment schedule in the business transaction.

Loans: Special Arrangements

Use
You use the Special Arrangements set type (CRM_PROD_FS010) to define the possible arrangements with loan customers, such as special repayments or extended commitment periods.

Collateral Agreement: Agreement Type

Use
You use the Agreement Type set type (CRM_PR_FSCA01) to specify the type of collateral agreement, such as group lien or certified land charge.

The set type is relevant only for financial service products (FS products) of the category Collateral Agreement.

Mapping of a Collateral Constellation

Use
When you process product master data, you create collateral constellations for financial service products (FS products), in order to safeguard mortgage loans, for example. You create a collateral constellation by creating relationships between FS products and product categories.

Features
The following figure shows a collateral constellation typically used for mortgage loans:

An overview of the elements of a collateral constellation is provided below:

Elements of a collateral constellation that you map using products:

y y y

Object: Mapped as a product of the type Material and category Real Estate. For more information, see Mapping of Objects. Collateral agreement: Mapped as a product of the type Financial Service (FS product) and category Collateral Agreement. Receivable: Mapped as a product of the type Financial Service (FS product) and category Loan.
Elements of a collateral constellation that you map using relationships:

Charge: Determines the amount by which an asset (object) is debited by a collateral agreement. Mapped as an FS relationship with the purpose Collateral Charge. Purpose declaration: Defines the scope of collateral for the receivables assigned to a collateral agreement. Mapped as an FS relationship with the purpose Collateral Scope. For more information, see Linking of FS Products and Product Categories.

You can also link a receivable (mortgage loan) to an asset value. This makes sense if you want to transfer the conditions of the object to the loan item in the business transaction, for example. To do this, you link the loan product with either the object directly or for a more flexible option with the category of the object.

Mapping of Objects

Use
In account origination for loans, you use products of the type Material and category Real Estate to map assets or objects to be financed, for example

Linking of FS Products and Product Categories

Use
You link financial service products (FS products) with product categories in order to map a business dependency between products. For each of these FS relationships, you define the purpose, which specifies in more detail the type of relationship involved. You define that an FS product in the business transaction needs a product of a specific category for a defined purpose. The advantage of linking FS products with categories rather than linking them to other FS products is that you can design your product landscape more flexibly

Creation of a Product Bundle

Use
You use product bundles to group together independent products for marketing and price reasons and sell them together under one name in a business transaction. In the business transaction, the system displays the individual products of a product bundle as separate items.

Business Partners for Financial Services

Definition
People, organizations, or groups of people/organizations in which your company has a business interest.

Use
You use business partner data in a series of business transactions. If you use the same business partner in different business partner roles and centrally store the master data, the only source of information for all system functions, then you have to enter data only once and your systems do not retain any redundant data. For more information, see Distribution of Business Partner Data.

Structure
The business partner concept is based on the following:
Business partner category: Depending on the business partner category, you can enter data in certain fields in business transactions. Business partner role: A business partner can take on different business partner roles that allow you to have different views of the business partner data, according to the business function. Business partner relationship: A relationship connects business partners and is characterized by the business partner relationship category.

For more information, see

Concepts.

When you create and maintain business partners, you enter general business partner data that applies for all business partners in SAP Customer Relationship Management (SAP CRM), and data that is only needed for business partners in the area of financial services:
General business partner data, such as address and communication data or marketing attributes. For more information, see Address and Communication Data and Marketing Data. Business partner data in the area of financial services, such as: Classification and

y y y y

Employment data, such as the type, duration, and status of the business partner s current or past employment relationships Enterprise data, such as information about the balance sheet and annual results Financial data, such as net income Regulatory reporting data, which is forwarded to the supervisory financial institutions in Germany and Austria
For more information, see Data for the Business Partner for Financial Services.

Employment Data

Use
You can enter information about a business partner s current and past employment situation.

Enterprise Data

Use
Enterprise data includes information from annual and consolidated results as well as business-based key figures for a business partner. The fiscal year data provides you with a comprehensive insight into the business partner s business relationships.

Balance Sheet Data

Use
You enter the balance sheet data for your business partner to document the business partner's economic situation.

Financial Data

Use
For business partners of the type Person, financial data includes information on the monthly and annual income.

Regulatory Reporting Data

Use
Regulatory reporting data is information about a business partner that is passed on by financial institutions to higher-level regulatory bodies as part of legal rulings on reporting obligations. The bank or insurance supervisory authority uses this data to analyze the business development of the regulated credit institutions, insurance companies, and financial services institutions. The supervisory regulations focus in particular on the liquidity and credit business of the institutions in question, for example. However, the regulatory reporting data can also be used for banking statistics or the compilation of information about foreign trade for the German Federal Bank.

Business Agreement

Definition
Groups together the attributes required to manage business transactions in invoicing and open item accounting.

They are required if you have connected to an ERP system and have activated FI-CA (contract accounts receivable and payable) as the open item accounting component.

Use
The business agreement data is used to define processes based on the business partner, and select the personal data of a business partner, such as address, bank details, and payment card. This enables you to control the processing of payments, bill creation, and correspondence. You can create several business agreements for a business partner. These agreements are displayed in an overview. You can maintain one or more business partners and save all the changes simultaneously. You choose a business partner for processing by selecting one from the overview, or entering the business partner number.

Integration
If you distribute business partner master data from CRM to the ERP system, the ERP system creates or changes contract accounts for the corresponding business agreements. You must assign business transactions to business agreements. When you do this, the system copies several fields from the business agreement to the business transaction. If this data is subsequently changed then you must change the business transactions manually.

Rating of Business Partners

Use
You can rate business partners for various business processes using external agents or company-specific internal procedures. A rating provides information about a customer s creditworthiness.

Integration
To rate a business partner, SAP Customer Relationship Management (SAP CRM) uses the credit rating check of a credit management system (for example, SAP Credit Management), which it accesses via SAP NetWeaver Exchange Infrastructure (SAP NetWeaver XI). For more information, see XI Content for Account Origination.

For more information about rating in SAP ERP Credit Management, see SAP Help Portal at help.sap.com p mySAP ERP 2005 p SAP ERP Central Component p Financials p SAP Financial Supply Chain Management (FIN-FSCM) p SAP Credit Management (FINFSCM-CR). If you want to deactivate the functions for the credit rating check, see SAP Note 1006362 Switching Off the Credit Standing Check

Display of Total Commitment

Use
With the total commitment, you can display all the contracts concluded with your company by one business partner or several related business partners. The information about the various contracts may exist in different systems, for example in loans management and account management. With the total commitment, you can merge this distributed information and therefore view the most important data about the customer s existing commitment at a glance.

Prerequisites
To display information in the total commitment that you want to manage in external systems, you have defined the required systems and applications that are to provide the business partner contract data. For more information, see Customizing for Financial Services p Basic Functions p Total Commitment p Total Commitment: General Settings p Set Total Commitment. You have checked the settings for total commitment. For more information, see Customizing for Financial Services p Basic Functions p Total Commitment p Total Commitment: General Settings p Check Settings for Total Commitment. To also display leases in the total commitment, you have defined the relevant transaction types to be included in the total commitment. For more information, see Customizing for Financial Services p Basic Settings p Total Commitment p Total Commitment for Leasing. You can replace the standard print form for total commitment with a customer-specific form. For more information, see Customizing for Financial Services p Basic Settings p Total Commitment p Print Form for Total Commitment. You can use Business Add-Ins (BAdIs) to modify the displayed information and appearance of the total commitment according to your particular requirements. You find these BAdIs in Customizing for Financial Servicesby choosing Basic Functions p Total Commitment p Total Commitment: General Settingsp Business Add-Ins (BAdIs).

Features
At the top of the screen, the total commitment displays information about the business partner, such as date of birth and information about business partner relationships.

In the total commitment, you can display totals for the contract amount, account balance, and account or card limit. You can select a contract in the total commitment and display the contract details. You can print out the total commitment. In Case Management, you can save a business partners total commitment as a document that you have created for the business partner.

Example
You are an employee in a credit institution and want to find out information about the customer Vera Sorokin in preparation for a credit advisory meeting. You display the total commitment and get an overview of her accounts and contracts. Ms Sorokin is married and has a joint current account with her husband. Both own a credit card and the bank has granted a credit limit on the account. The account balance is positive. Ms Sorokin also has two savings accounts and a securities account and has taken out a mortgage loan. The total commitment displays all this customer information at a glance. See also: Case Management in Account Origination

Distribution of Business Partner Data

Use
You use SAP NetWeaver Exchange Infrastructure (SAP NetWeaver XI) to distribute business partner data between SAP Customer Relationship Management (SAP CRM) and the back-end systems. When you create or edit master data for a business partner, SAP CRM distributes this data to the relevant management systems, such as loans management. Business partner data is also distributed in the opposite direction, namely from the back-end systems to SAP CRM. For more information, see SAP NetWeaver Exchange Infrastructure.

Features
For account origination, you must exchange business partner data between several systems. You must enable data distribution for the following systems: SAP CRM and loans management, for example SAP Loans Management in SAP ERP SAP CRM and collateral management, for example SAP Collateral Management in SAP ERP SAP CRM and credit management, for example SAP Credit Management in SAP Financial Supply Chain Management

Case Management in Account Origination

Use
Case Management enables you to manage and process all information that arises during the account origination process in a central object: the case. You can group different information in a case, such as business partners and documents.

You can use Case Management to process complex situations that involve multiple processing steps or multiple processors. Case Management therefore supports the processing and communication flow between organizational units and ensures an efficient workflow.

Business Rule Framework in Account Origination

Use
You use the Business Rule Framework (BRF) to define rules for checks that the system executes in account origination. You can define in which business transactions and at what point in time the system starts these checks. The BRF is therefore a flexible and powerful tool that you can use to integrate automated process flows into the origination process.

Maintaining a Financial Service Quotation

Use
A financial service quotation (FS quotation) can contain various products from the broad range of financial services, such as consumer loans, mortgage loans and collateral agreements. In SAP Customer Relationship Management (SAP CRM), you create quotations for financial services and enter the relevant data. Calculation functions that you use in FS quotations are located in the connected backend systems. When you have verified and approved an FS quotation, the system creates the contract in the appropriate backend system.

Transfer of Products to Financial Service Quotations

Use
When you create a quotation for financial services (FS quotation) you transfer to the FS quotation products for which you have defined master data. You define the special, customer-specific instance of the product in the quotation.

Maintenance of a Loan Item

Use
When you maintain loan items, you enter concrete, customer-specific data and therefore store an individual instance of the financial service quotation (FS quotation). Depending on the item category (mortgage loan or consumer loan), you can enter different data and use different functions.

Configuration of the Payment Structure

Use
When you include a loan product in a financial service quotation (FS quotation), the system transfers the data on the payment structure from the master data of the financial service product (FS product). In this process, the system interprets the date rules on the basis of the date profile of the individual items and transfers the amounts and percentages from the conditions. You can change payment structure settings in the FS quotation.

Calculation of the Payment Schedule

Use
The payment schedule displays the concrete periods in a loan. This is the interest and repayment schedule that lists all payments in the fixed interest period, the composition of these payments, and the remaining balance.

Maintaining a Real Estate Item

Use
You use real estate in the financial service quotation (FS quotation) as an asset to safeguard a loan or as an object to be financed. In day-to-day business, it is usual that the object to be financed and the asset are one and the same thing.

Maintenance of the Relationships in a Collateral Constellation

Use
In the financial service quotation (FS quotation), you can maintain the collateral charge and collateral scope that are mapped by item relationships.

Set Types for Business Transactions

Use
In addition to the set types that you use to describe products in the master data, you can use set types that you can process only in the business transaction. It makes sense to differentiate between these kinds of set types because the set types in the business transaction describe data that defines a product on a customer-specific basis. The set types that you use in the master data are also integrated in the business transaction. Depending on the set type, you can change the settings from the master data in the business transaction. For more information, see Set Types for Financial Service Products.

Subsequent Processing for a Financial Service Quotation

When you have finished maintaining a financial service quotation (FS quotation), you carry out subsequent processing. Subsequent processing involves a number of steps, which you perform in a predefined sequence. During subsequent processing, the document is assigned a number of different statuses. For more information, see:
Status Management for a Financial Service Quotation Distributing Loan Data Distributing Collateral Data

Status Management for a Financial Service Quotation

Purpose
During the account origination process, a financial service quotation (FS quotation) is assigned a number of statuses in a fixed sequence. You can set some statuses manually, while the system sets other statuses automatically after certain functions have been performed. For general information about statuses in business transactions in SAP Customer Relationship Management (SAP CRM), see Status Management in Business Transactions.

Prerequisites
When it manages the status of an FS quotation, the system uses functions that are located not in SAP CRM but in external systems. These functions are connected both synchronously (for example, for the calculation of the payment schedule) and asynchronously (for example, for the distribution of loan data). For more information, see Connection of External Systems.

Process Flow
The following figure shows the possible system statuses of an FS quotation:

Distribution of Loan Data

Use
In SAP Customer Relationship Management (SAP CRM), you create, maintain, and release financial service quotations (FS quotations). The system replicates the contracts for these quotations in the connected loans management system.

Features
When you set the status of an FS quotation to Signed (when the contract partners have signed the contract), the system transfers the loan data to the connected systems.

For more information, see Status Management for a Financial Service Quotation. Once SAP CRM has triggered replication of the data in loans management, the following events can occur:

y y

If you have created the contract, you see a corresponding entry in the FS quotation in the Document Flow area. If you have not created the contract, you find information about this in Monitoring for XML Messages. For more information, see Central Monitoring.

Distribution of Collateral Data

Use
In SAP Customer Relationship Management (SAP CRM), you create, maintain, and release financial service quotations (FS quotations), including collateral constellations. The system replicates the collateral data in the connected collateral management system.

Features
When you set the status of the FS quotation to Signed, SAP CRM transfers the collateral data to collateral management. For more information, see Status Management for a Financial Service Quotation. Once SAP CRM has triggered replication of the data in collateral management, the following events can occur:

y y

If you have entered the data in collateral management, you see a corresponding entry in the FS quotation in the Document Flow area. If you have not entered the data in collateral management, you find information about this in Monitoring for XML Messages. For more information, see Central Monitoring.

Connection of External Systems

Use
In the account origination process, you can use functions that are in external systems and not in SAP Customer Relationship Management (SAP CRM). To be able to use these functions, you need to replicate data between systems. You can transfer data synchronously and asynchronously. Asynchronous Connection If you connect SAP CRM to external systems asynchronously, data distribution uses both CRM Middleware and SAP NetWeaver Exchange Infrastructure (SAP NetWeaver XI): The CRM system generates a business document (BDoc) that it transfers to CRM Middleware. In CRM Middleware, external interface adapters (XIF adapters) convert the data to XML and select the data to be transferred. Data is then exchanged via SAP NetWeaver XI, where further mapping is possible if required.

Communication takes place with a time delay, which means that the back-end system does not return the result to SAP CRM immediately. You use the asynchronous connection when you create stock data in the back-end systems, for example contracts. Synchronous Connection If you connect SAP CRM to external systems synchronously, data distribution takes place via SAP NetWeaver XI alone; CRM Middleware is not involved. Communication takes place in real time, which means that the back-end system returns the result to SAP CRM immediately. You use the synchronous connection when you use calculation functions in the back-end system, such as the calculation of a payment schedule for a loan.

Integration
You need at least one contract management system to map the account origination scenario.

The standard system contains examples of settings for initiating secured and unsecured loan contracts. These settings are aligned with SAP back-end systems, which are available in SAP ERP 6.0. However, you can also use back-end systems from other manufacturers. You use CRM Middleware to control the replication of documents for asynchronous connection. For more information, see CRM Integration Services. You use SAP NetWeaver XI to handle synchronous and asynchronous communication between SAP CRM and external systems. For more information, see SAP NetWeaver Exchange Infrastructure. There is one integration scenario in SAP NetWeaver XI for the account origination scenario. The integration scenario describes all objects that you need for the semantic and technical integration of loan origination, for example interfaces and data types. You can use the integration scenario as a template for setting up a connection to external systems. For more information, see ContractOrigination.

Prerequisites
Settings in Back-End Systems Before you can use the functions in SAP back-end systems, you must make the following settings:

The following are examples of settings in the back-end systems and are based on the following conditions:

y y y

SAP ECC 6.0 (SAP ERP 6.0) with extension EA-FINSERV is used for loans management SAP ECC 6.0 (SAP ERP 6.0) with extension EA-FINSERV is used for collateral management SAP Credit Management Server 6.0 is used as the credit management server
If you are using other contract or support systems, you can use the following information as a guideline.

The technical implementation of the Account Origination scenario requires at least one contract system for the operational management of contracts. Before you configure your system landscape for the technical implementation of the scenario, check the existing limitations of the contract system you plan to use as the back-end system for the operational management of contracts in combination with account origination. For more information, see SAP Service Marketplace at service.sap.com/notes. Loans management (SAP Banking): XI Interfaces for Loan Origination: New Business Collateral management (SAP Banking): Settings in Collateral Management Credit management (SAP Credit Management): Settings in Credit Management for Account Origination

Settings for Asynchronous Connection in SAP CRM Before you can use the asynchronous connection to replicate loan and collateral data, you must make the following settings:
To connect SAP CRM and SAP NetWeaver Exchange Infrastructure, you have created for SAP CRM a site with the type External Interfaces for XI. To enable the exchange of data, you have created subscriptions for the site with the type All Business Transactions. For more information, see the Implementation Guide (IMG) for Customer Relationship Management under CRM Middleware and Related Components p Exchanging Data with External Componentsp XIF Adapter Setup p Outbound Direction p Create Sites and Subscriptions. You have assigned a BDoc type and one of the following interfaces to the site:

y y y y

CRMXIF_COLLAT_CONST_CONF_SAVE CRMXIF_COLLAT_CONST_CREA_SAVE CRMXIF_LOANC_CONFIRM_SAVE CRMXIF_LOANC_CREATE_SAVE

For more information, see the IMG for Customer Relationship Management under CRM Middleware and Related Components p Exchanging Data with External Components p XIF Adapter Setup p Outbound Direction p Assign Site and BDoc Type to Interface Type. You have defined which items of a document you want to distribute to the external settings using the XIF adapter. For more information, see the IMG for Financial Servicesunder Basic Functions p Connection of External Systems p Asynchronous p Configure Status Management for XI Adapter.

Connection to Loans Management When you release financial service quotations (FS quotations) in SAP CRM, the system copies the data to the connected loans management system:
You have assigned the corresponding payment methods for the connected loans management system to the payment methods defined for each country in CRM. For more information, see the IMG for Financial Servicesunder Basic Functions p Connection of External Systems p Asynchronous p Connection to Loan Management p Assign Payment Methods.

You can use a Business Add-In (BAdI) to modify how data is updated when it is transferred from financing transactions to loans management. For more information, see the IMG for Financial Servicesunder Basic Functions p Connection of External Systems p Asynchronous p Connection to Loan Management p BAdI: Create Financial Services Contract. You can use a BAdI to modify how data is updated for financial transaction confirmations from loans management. For more information, see the IMG for Financial Servicesunder Basic Functions p Connection of External Systems p Asynchronous p Connection to Loan Management p BAdI: Process Confirmation of Financial Services Contract.

Connection to Collateral Management When you release an FS quotation in SAP CRM, the system copies the data relating to the collateral constellation to the connected collateral management system:
You can use a BAdI to modify the message that the system transfers to collateral management when it creates the collateral constellation. For more information, see the IMG for Financial Servicesunder Basic Functions p Connection of External Systems p Asynchronous p Connection to Collateral p BAdI: Create Collateral Constellation. You can use a BAdI to modify the message that confirms the creation of collateral in collateral management to meet your requirements. For more information, see the IMG for Financial Servicesunder Basic Functions p Connection of External Systems p Asynchronous p Connection to Collateral p BAdI: Post Confirmation of Collateral Constellation.

Settings for Synchronous Connection in SAP CRM Before you can use the functions that are synchronously connected to SAP CRM, you must make the following settings:
You have integrated the functions that are synchronously connected to SAP CRM by using actions in business transactions. In account origination, you can also define a sequence in which the system is to perform the actions (action choreography). For more information about actions, see the IMG for Customer Relationship Management under Basic Functions p Actions p Actions in Transaction. For more information about action choreography, see the IMG for Financial Services under Basic Functions p Connection of External Systems p Synchronous p Reset Calculation Status/Define Action Choreography. You have used a BAdI to define how to filter out the data to be transferred from the business transaction and how to transfer the results to the business transaction. For more information, see the IMG for Financial Servicesunder Basic Functions p Connection of External Systems p Synchronous p BAdI: Define Data Retrieval from Transaction/Results Transfer to Transaction. For credit standing queries between SAP CRM and the Credit Management server, you can use a BAdI to change the Credit Management return values or generate error messages. For more information, see the IMG for Financial Servicesunder Basic Functions p Connection of External Systems p Synchronous p Connection to Credit Management Systemp BAdI: Process the Credit Servers Return Values.

Features
In conjunction with account origination, asynchronous and synchronous connections to external systems are required. Asynchronous Connection An asynchronous connection is required to replicate inventory data for the following account origination functions:
Creation of loan contracts in loans management Creation of collateral constellations in collateral management

Synchronous Connection A synchronous connection is required to exchange transaction data for the following account origination functions:
Calculation of the payment schedule for loans in loans management Credit rating of business partners in credit management Transfer of existing collateral from collateral management

ContractOrigination

Purpose
You use this integration scenario to exchange data between the front-end system SAP Customer Relationship Management (SAP CRM) and external back-end systems during account origination. The integration scenario offers you central access to all objects that you need for semantic and technical integration, for example interfaces and data types.

Process Flow
The following figure shows the process flow for the complete integration scenario:

Settings in Collateral Management

Use
In the account origination process, you use functions that are in the connected collateral management system, and not in SAP Customer Relationship Management (SAP CRM); these include the use of existing assets and collateral agreements and the creation of the collateral constellation. You use SAP NetWeaver Exchange Infrastructure (SAP NetWeaver XI) to synchronize data between SAP CRM and collateral management.

The technical implementation of the Account Origination scenario requires at least one contract system for the operational management of contracts. Before you configure your system landscape for the technical implementation of the Account Origination scenario,

check the existing limitations of the contract system you plan to use as the back-end system for the operational management of contracts in combination with account origination. For more information, see SAP Service Marketplace at service.sap.com/notes.

Integration
The message exchange between SAP CRM and collateral management is part of the ContractOrigination integration scenario. For more information, see XI Content for Account Origination.

Note that the standard system:

y y

Supports the asset type Real Estate (000001) only Supports collateral agreements of the category Group Lien (000001) only

Features
To enable data synchronization between SAP CRM and collateral management, you can:
Manually copy the settings defined in collateral management to SAP CRM Create settings in SAP CRM for collaterals and assign these to the settings in collateral management using value mappings in SAP NetWeaver XI

Activities
The following table lists the settings in SAP CRM and collateral management that you must either make in each system or assign to each other using value mappings.
Settings for Assets and Collateral Objects Settings in Customizing for SAP Banking p Collateral Management p Assets p Define Asset Types p Collateral Management p Object Management p Collateral Objects p Real Estate p Define Usages p Collateral Management p Object Management p Assets p Real Estate p Define Macro Descriptors, setting: Macro Locations p Collateral Management p Object Management p Assets p Real Estate p Define Micro Descriptors, setting: Micro Locations Settings in Customizing for Financial Services p Account Origination p Financial Service Product (FS Product) p Property Values p Real Estate p Define Object Types p Account Origination p Financial Service Product (FS Product) p Property Values p Real Estate p Define Usages p Account Origination p Financial Service Product (FS Product) p Property Values p Real Estate p Define Macro Locations p Account Origination p Financial Service Product (FS Product) p Property Values p Real Estate p Define Micro Locations

p Collateral Management p Object Management p Assets p Real Estate p Define Macro Descriptors, setting: Transport Connections

p Account Origination p Financial Service Product (FS Product) p Property Values p Real Estate p Define Transport Connections

Settings for Collateral Agreements Settings in Customizing for SAP Banking p Collateral Management p Collateral Agreement p Define Collateral Agreement Types Settings in Customizing for Financial Services p Account Origination p Financial Service Product (FS Product) p Collateral Agreements p Define Agreement Types

Settings in Loans Management

Use
If you are using SAP ECC 6.0 (SAP ERP 6.0) with extension EA-FINSERV for loans management, you find information about the required settings in the following sections:  XI Interfaces for Loan Origination: New Business  Products and Conditions for Loan Origination  Derivation Rules for Loan Origination