j91 s4hana1611 Bb Configguide en Financial Services Network (J91) Building Block Configuration Guide

SAP S/4HANA October 2016 English

Financial Services Network (J91) Building Block Configuration Guide

SAP SE Dietmar-Hopp-Allee 16 69190 Walldorf Germany

SAP Best Practices

Financial Services Network (J91): Configuration Guide

Copyright © 2016 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.

© SAP SE

Page 2 of 10

SAP Best Practices

Financial Services Network (J91): Configuration Guide

Revision

Change Date

Description

1

12/15/2014

Content dev.

© SAP SE

Page 3 of 10

SAP Best Practices

Financial Services Network (J91): Configuration Guide

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.



Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP SE

Page 4 of 10

SAP Best Practices

Financial Services Network (J91): Configuration Guide

Content FSN Connector: Configuration Guide ........................................................................................ 6 1 Purpose .............................................................................................................................. 6 2 Preparation ......................................................................................................................... 6 2.1 Prerequisites ............................................................................................................ 6 2.2 Supported Deployments ........................................................................................... 6 3 Configuration ...................................................................................................................... 6 3.1 Create Payment Medium Formats ........................................................................... 6 3.2 Maintain Number Range for Message ID ................................................................. 7 3.3 Maintain Selection Variants for Bank Statements .................................................... 7 3.4 Maintain Bank Statement Selection Variants ........................................................... 8 3.5 Activation of scope-dependent background job definitions ...................................... 9 4 Manual Build Steps ............................................................................................................ 9

© SAP SE

Page 5 of 10

SAP Best Practices

Building Block Title (ID): Configuration Guide

FSN Connector: Configuration Guide 1 Purpose The purpose of this document is to describe the general configuration steps required to manually set up the configuration within the system landscape that has already been installed using the corresponding installation or configuration guides for installation. If you want to install SAP S/4HANA locally (on-premise) and if you do not want to configure manually and prefer an automated installation process using BC Sets and other tools, you can set up a best-practice client and activate the implementation content. For more information, see the „Administration Guide for the Implementation of SAP S/4HANA, on premise edition“• which is linked in the content library (included in the documentation package).

2 Preparation 2.1 Prerequisites Before you start installing this scenario, you must install the prerequisite building blocks. For more information, see the Building Block Prerequisites Matrix.

2.2 Supported Deployments The configuration guide provides the implementation content for the different SAP S/4HANA products: 

SAP S/4HANA Cloud – (CE) minimal scope and content

 SAP S/4HANA – (OP) installed locally (on-premise), full scope and content coverage Depending on the use case/deployment option/ S/4HANA product version, you need to implement the required scope/content starting with the Public cloud chapter and proceed with the next required sections. 

For the full scope of the on premise scope & content – PC and OP are required



For the SAP S/4HANA Cloud scope & content – CE is required; OP is not required

3 Configuration 3.1 Create Payment Medium Formats Use In this activity you can create payment medium formats yourself.

Procedure 1. Access the transaction choosing one of the following navigation options: IMG menu

Financial Accounting (new)  Accounts Receivable and Accounts Payable  Business Transactions  Outgoing Payments  Automatic Outgoing Payments  Payment Media  Make Settings for Payment Medium Formats from Payment Medium Workbench  Create Payment Medium Formats

Transaction

OBPM1

© SAP SE

Public

Page 6 of 10

SAP Best Practices

Building Block Title (ID): Configuration Guide

Code 2. On the Change View “Payment Medium Formats”: Overview screen, in the Dialog Structure pane, double-click Payment Medium Formats  Payment Format FSN_CT_00100103. 3. Choose the Customer settings for Format button. 4. Choose Change. 5. Choose Event Modules. 6. On the Change View “Event Modules” screen, choose New Entries. 7. Make the following entries: Event

Function module name

21

/BSNAGT/FI_PAYMEDIUM_DMEE_20

31

FI_PAYMEDIUM_FSN_PAIN001_CT_30

8. Save your entries.

3.2 Maintain Number Range for Message ID Use In this Customizing activity, you maintain the number range for Message IDs. The system uses this number range to generate a unique message ID when a message ID is not provided to the system during message creation.

Procedure 1. Access the transaction choosing one of the following navigation options: IMG menu

Financial Services Network Connector  Maintain Number Range for Message ID

Transaction Code

SPRO

2. On the Change View “Maintain Intervals: NR for file”, make the following entry: Field name

Description

User action and values

No.

N2

From No.

0000000001

To Number

9999999999

Comment

NR Status External Assignment 3. Save your entries.

3.3 Maintain Selection Variants for Bank Statements Use In this Customizing activity, you maintain the Variant for a SenderID/ReceiverID and Message Type in the view BSNAGT/V_VARI. The system processes incoming messages according to the message type, which is specified in the Web service interface. For MT940 (bank statement), MX camt.053 and MT942 (account report), or MX camt.052, the report RFEBKA00 (transaction FF.5) is executed with the relevant variant, as configured in this Customizing activity.

© SAP SE

Public

Page 7 of 10

SAP Best Practices

Building Block Title (ID): Configuration Guide

Prerequisite You must create a variant in customizing before you can maintain it. 1. Access the transaction SE38

Transaction Code 2. In the Program field, enter RFEBKA00 and choose Variants. 3. Use the following variant: Field name

Description

Variant

User action and values

Comment

for example, FSN_053

4. Choose Create. 5. In the Edit Variants view, enter the following parameters: Field name

Description

User action and values

Import data

X

Elect. Bank statement format

X XML or Bank-Specific Format

XML or Bank specific Format

CAMT.053.001.02

Post immediately

X

Session names

1

Assign value date

X

BELNR number interval

1

BELNR number interval

To

9999999999

To

ZZZZZZZZZZZZZZZZ

Comment

XBLNR number interval XBLNR number interval Print bank statement

X

Print posting log

X

6. Choose Save as Variant. 7. On the Variant Attributes screen, create the following settings: Field Name

Entry Value

Variant Name

FSN_053

Description

Variant for FSN BS processing

8. Save your entries.

3.4 Maintain Bank Statement Selection Variants Procedure 1. Access the transaction choosing one of the following navigation options: IMG menu

Financial Services Network Connector  Maintain Selection Variants for Bank Statements

Transaction

SPRO

© SAP SE

Public

Page 8 of 10

SAP Best Practices

Building Block Title (ID): Configuration Guide

Code 2. On the Change View “Maintain Bank Statement Selection Variants” screen, make the following entries: Field name

Description

User action and values

Comment

Sender ID Message Type

CAMT.053.001.02

Variant

FSN_053

3. Save your entries.

3.5 Activation of scope-dependent background job definitions Procedure 1. Access the transaction choosing one of the following navigation options: Transaction Code

SM30

On the Maintain Table Views: Initial Screen, enter STJR_JOBD_SCOPE in Table/View, and choose Maintain. On the Change View “Scope switch of technical jobs”: Overview screen, choose New Entries. 2. On the New Entries: Overview of Added Entries screen, create the following settings: Field Name

Entry Value

Job Definition Name

SAP_FIN_FSN_MESSAGES_PULL

3. Save your entry.

4 Manual Build Steps Some settings cannot automatically be transported between systems or clients. In these cases, you either transport the settings manually, if possible, or make the settings in the target system or client. The following table lists the configuration activities where automatic transport is not possible. Refer to the details and sequence in the sections above. Configuration activity

Manual transport possible

Manual action in target system / client required

3.3 Maintain Selection Variants for Bank Statements

No

Yes

3.4 Maintain Bank Statement Selection Variants

Yes

No

Remarks

We recommend that you plan especially for doing these manual build steps and rehearse the sequence in advance, if possible well before cut over.

© SAP SE

Public

Page 9 of 10

SAP Best Practices

© SAP SE

Building Block Title (ID): Configuration Guide

Public

Page 10 of 10