Banking Services from SAP 8.0
October 2014
EnglishEnglish
Connectivity Settings for Account Management to Master Contract Management - Configuration Guide
(L93)
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany

© SAP SE Page 4 of 4

SAP Best Practices

Connectivity Settings for Account Management to Master Contract Management (L93): Configuration Guide

Copyright

© 2014 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

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

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company 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.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.


Icons

Icon / Meaning
/ Caution
/ Example
/ Note
/ Recommendation
/ Syntax

Typographic Conventions

Type Style / Description
Example text / Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.
Cross-references to other documentation.
Example text / Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT / Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.
Example text / Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.
EXAMPLE TEXT / Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.
Example text / Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.
<Example text> / Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.


Content

Connectivity Settings for Account Management to Master Contract 5

1 Preparation 5

1.1 Prerequisites 5

2 System Preparation 5

2.1 Activating Service for Integration Engine 5

2.2 Maintaining RFC Connection in Transactional Banking System 6

2.2.1 PI internal Communication to PI System 6

2.2.2 Application Communication to the PI System 7

2.2.3 PI Communication to the Integration Server 7

2.2.4 PI Communication to the Integration Directory 8

2.2.5 Communication to the ESR on Banking Services System 9

2.3 SLD API Customizing 9

2.4 Maintaining SLD Administration in Transactional Banking System 10

2.5 Integration Engine Configuration in Banking System 10

2.6 Managing Queues Configuration in Transactional and Analytical Banking System 11

3 PI Configuration 12

3.1 Checking Technical Systems on SLD PI System 12

3.2 Creating Business Systems in SLD 12

3.3 Assigning Business Systems in Integration Directory 13

3.4 Creating Configuration Scenario for Deposit Management 14

3.5 Assigning Business Systems to Configuration Scenario 15

3.6 Creating Receiver Communication Channel 16

3.7 Creating Sender Communication Channel 17

3.8 Assigning Communication Channels to Configuration Scenario 19

3.9 Creating Integrated Configuration 20

3.9.1 BankMasterContractProcessingBankAccountContractMasterContractParticipationOut 20

3.9.2 BankAccountContractProcessingBankAccountContractMasterContractParticipationOut 21

3.9.3 BankMasterContractProcessingManageBankAccountContractMasterContractParticipationOut 23

3.10 Assigning Integrated Configuration to Configuration Scenario 25

3.11 Configuration of Service BankAccountContractProcessingBankAccountStatementRequestOut for Combined Statement 26

Connectivity Settings for Account Management to Master Contract

This Configuration Guide helps consultants and customer project members to implement the SAP Deposit Management rapid-deployment solution V2.800 (RDS).

The guide focuses on technical implementation aspects, usage of the SAP Solution Manager and the SAP Best Practices Solution Builder add-on. The document mentions all the required steps for a successful implementation of the SAP Deposit Management rapid-deployment solution V2.800 and directs to more detailed documentation where necessary.

The System Landscape Prerequisites section lists all the system pre-requisites that have to be fulfilled by customers before implementing the rapid-deployment edition can start. Installation of the required systems is not part of the SAP Deposit Management rapid-deployment solution V2.800’s delivery scope.

The Preparation Activities section explains the tasks that need to be carried out specifically for implementing the SAP Deposit Management for Banking rapid-deployment solution. The preparation activities are part of the SAP Deposit Management rapid-deployment solution V2.800.

The Implementation section guides you step-by-step through the current technical implementation process. What is actually implemented and configured is subject to a previous scoping effort.

The SAP Deposit Management rapid-deployment solution V2.800 addresses core functional needs of IT Service Operation. From a technical implementation perspective the content of this guide is valid for the SAP Deposit Management rapid-deployment solution V2.800.

The term SAP Deposit Management rapid-deployment solution V2.800 is used where the software part of the package is concerned. The package as a whole (that is software and implementation services) is called SAP Deposit Management for Banking rapid-deployment solution.

1  Preparation

1.1  Prerequisites

The following Building Blocks are designed to function independently, but they can also be migrated:

·  L76 Connectivity Settings for Transactional Banking to Collaterals Management

·  L77 Connectivity Settings for Transactional Banking to Payment Engine

·  L93 Connectivity Settings for Account Management to Master Contract Management

If customer choose to use more than one building block, most steps in Chapter 3 and Chapter 4.1-4.8 only need to be implemented one time.

If BB L77 or L78 is implemented before this document(L77), you can start directly from chapter 4.9.

2  System Preparation

Some or all of these steps may have already been completed by IT or Basis consultants who installed the systems or created the clients for the Transactional Banking and Analytical Banking systems.

2.1  Activating Service for Integration Engine

Use

Service need to be activated for Integration.

Service is cross client configuration.

Procedure

1.  In the Transactional Banking system access the activity using the following transaction:

Transaction code / SICF

2.  Enter ENGINE as the Service Name and choose the Execute.

3.  Right-click the engine node and select Activate Service.

4.  Choose Yes to confirm the dialog box.

Result

Sevice Engin is activated.

2.2  Maintaining RFC Connection in Transactional Banking System

2.2.1  PI internal Communication to PI System

Use

RFC connections have to be created between the ABAP systems and the SAP PI system.

This destination will be used later for PI communication to the PI System.

Procedure

1.  Access the activity using the following transaction:

Transaction code / SM59

2.  Choose the Create pushbutton (F8).

3.  Enter the following data:

Field / Entry /
RFC Destination / SAPSLDAPI
Connection Type / T (TCP/IP Connection)
Description / SAPSLDAPI Connector

4.  Choose activation type Registered Server Program.

5.  Choose Enter and make the following entries:

Technical Settings
Program ID / SAPSLDAPI_<PI- system ID>
Gateway Host / <Message-Server PI -System>
Gateway service / sapgw<System instance number PI System>
Unicode
Unicode / Selected

6.  Choose Save.

7.  Test the newly created RFC connection using Connection Test.

2.2.2  Application Communication to the PI System

Use

RFC connections have to be created between the ABAP systems and the SAP PI System.

This destination will be used later for PI communication to the PI System.

Procedure

1.  Access the activity using the following transaction:

Transaction code / SM59

2.  Choose the Create pushbutton (F8).

3.  Enter the following data:

Field / Entry /
RFC Destination / LCRSAPRFC
Connection Type / T (TCP/IP Connection)
Description / LCRSAPRFC Connector

4.  Choose activation type Registered Server Program.

5.  Choose Enter and make the following entries:

Technical Settings
Program ID / LCRSAPRFC _<PI- system ID>
Gateway Host / <Message-Server PI -System>
Gateway service / sapgw<System instance number PI System>
Unicode
Unicode / Selected

6.  Choose Save.

7.  Test the newly created RFC connection using Connection Test.

2.2.3  PI Communication to the Integration Server

Use

RFC connections have to be created between the ABAP systems and the SAP PI system.

This destination will be used later for PI communication to the PI System.

Procedure

1.  Access the activity using the following transaction:

Transaction code / SM59

2.  Choose the Create pushbutton (F8).

3.  Enter the following data:

Field / Entry /
RFC Destination / INTEGRATIONSERVER_<ID_PISYSTEM>
Connection Type / G (HTTP Connection to External Serv)
Description / Integration server PI System

4.  Choose Enter and make the following entries:

Technical Settings
Target Host / <Message-Server PI -System>
Service No. / <http-service No - PI -System>
Path Prefix / /XISOAPAdapter/MessageServlet?ximessage=true
Logon & Security
SSL / inactive
Logon Procedure / Basic Authentication
User / PIAPPL_<Banking Services system ID>
Password / Enter PIAPPL_<Banking Services system ID> password from PI System.

5.  Choose Save.

6.  Test the newly created RFC connection using Connection Test.

2.2.4  PI Communication to the Integration Directory

Use

RFC connections have to be created between the ABAP systems and the SAP PI system.

This destination will be used later for the cache update of the XI runtime cache.

Procedure

1.  Access the activity using the following transaction:

Transaction code / SM59

2.  Choose the Create pushbutton (F8).

3.  Enter the following data:

Field / Entry /
RFC Destination / INTEGRATION_DIRECTORY_HMI
Connection Type / H (HTTP Connection to ABAP System)
Description / Integration Directory PI System

4.  Choose Enter and make the following entries:

Technical Settings
Target Host / <Message-Server PI -System>
Service No. / <http-service No - PI -System>*
Path Prefix / /dir/hmi_cache_refresh_service/ext
Logon & Security
Logon Procedure / Select Basic Authentication
SSL / inactive
Language / EN
Client / 001
User / PIIS _<Banking Services system ID>
Password / PIIS _<Banking Services system ID> password in PI System
For example: ‘XIPASS’ (**)

5.  Choose Save.

6.  Test the newly created RFC connection using Connection Test.

2.2.5  Communication to the ESR on Banking Services System

Use

RFC connections have to be created between the ABAP systems and the SAP PI system.

This destination will be used later for ESR communication to the PI System.

Procedure

1.  Access the activity using the following transaction:

Transaction code / SM59

2.  Choose the Create pushbutton (F8).

3.  Enter the following data:

Field / Entry /
RFC Destination / SAP_PROXY_ESR
Connection Type / G (HTTP Connection to External Serv)
Description / ESR PI System

4.  Choose Enter and make the following entries:

Technical settings
Target Host / <Message-Server PI -System>
Service No. / <http-service No - PI -System>*
Path Prefix / /rep
Logon & Security
Logon Procedure / Basic Authentication
SSL / Inactive
User / PIAPPL_<Banking Services system ID>
Password / PIAPPL_<Banking Services system ID> password in PI System

5.  Choose Save.

6.  Test the newly created RFC connection using Connection Test.

2.3  SLD API Customizing

Use

This configuration will be used for communication to SLD in Transactional Banking system.

Procedure

  1. In the Transactional Banking system access the transaction using the following navigation transaction:

Transaction code / SLDAPICUST
  1. On the screen Display SLD Access Data, choose Display <® Change.
  2. Enter the values below:

Field name / User action and values / Note
Alias Name / <PI system ID>
Prim. / Check
Host Name / <PI system host name>
Port Number / <PI system HTTP port number>
User / <PIAPPL_<BaS system ID>
Password / <Password for above user> / Choose pencil button
  1. Choose Save.
  2. Select the created line item and choose Test.

If the test result shows “Connection to SLD works correctly“, the SLD API customizing is complete. Otherwise please check and correct the setting of connection.

2.4  Maintaining SLD Administration in Transactional Banking System

Use

System information of application(ABAP) systems need to be registered in SLD.

Procedure

1.  Access the activity using the following transaction:

Transaction code / RZ70

2.  Enter the values below:

Field / Entry /
Gateway Host / <Message-Server PI >
Gateway Service / sapgw<System instance number PI >

3.  Choose Save.