SEPA Configuration/Set-Up Guide

SEPA Integration in CRM

On February 1, 2014, Europes unified payment transaction system will be launched. The national
processes will be adjusted by then. In the future, in Europe only SEPA Credit Transfers (SCT) and
SEPA Direct Debits (SDD) will take place. It will then be mandatory in all SEPA countries to use
these two payment methods. Optionally, each country can decide on an extended changeover
period, up to February 1, 2016.
SEPA means Single Euro Payments Area.
The SEPA functionality is available in:
Enhancement Pack 3 for CRM 7.0
Enhancement Pack 2 for CRM 7.0, SP08 (NW 731, SP08)
Enhancement Pack 1 for CRM 7.0, SP11 (NW 702, SP11)
SEPA mandates can be exchanged between SAP CRM and the following SAP ERP components:
Contract Accounts Receivable and Payable (FI-CA), OR
Accounts Receivable (FI-AR)

Mandates cannot be entered in SAP CRM unless integration with one of the above SAP ERP components is in
place.

1.1

SEPA Business Function/Switches in CRM

To use SEPA mandates in CRM business partners, the business function Single Euro Payments
Area (SEPA) Mandates (CRM_SEPA_1) needs to be activated. To check activation status of switch:
Transaction SFW5:

In Transaction SFW2, you can see the corresponding switches.

Generated by Jive on 2015-04-28+02:00

1

SEPA Configuration/Set-Up Guide

1.2

Activate FI-AR or FI-CA Customizing

In Customizing table SEPA_CUST the SEPA Mandate Management application needs to be set as active in
CRM. You can check this in the SAP Reference IMG under Customer Relationship Management # Master Data
# Business Partner # Make Settings for SEPA Mandates:

Generated by Jive on 2015-04-28+02:00

2

SEPA Configuration/Set-Up Guide

1.3

SEPA Documentation in CRM

1.3.1

Application Help: SEPA Mandates

1.3.2

Application Help: SEPA Direct Debits

1.3.3
IMG)

IMG Activity: Make Settings for SEPA Mandates (See

1.3.4

1.4

Switch Documentation: Single Euro Payments Area (SEPA) Mandates

SEPA Customizing in CRM

You need to define in Customizing for Customer Relationship Management under Master Data # Business
Partner # Make Settings for SEPA
Mandates which scenario is to be activated (FI-AR or FI-CA scenario).

Generated by Jive on 2015-04-28+02:00

3

SEPA Configuration/Set-Up Guide

Warning: do not activate both applications at the same time in the same client!

1.4.1

Define Payment Method (for a EURO Relevant Country)

Generated by Jive on 2015-04-28+02:00

4

SEPA Configuration/Set-Up Guide

SAP Implementation Guide # Customer Relationship Management # Master Data # Business Partner #
Business Agreement # Define Parameters for Business Agreement # Payment Methods. In the Customizing
activity Define Payment Methods, define a Payment Method for a Euro-relevant country
such as Germany that requires a SEPA mandate:

Customizing of payment method data maintained in SAP ERP can be loaded to SAP CRM by means of the
initial download (R3AS). The download now also includes the field Mandate Req. Either manually choose this
payment method in relevant sales/service transactions or assign it to Payment Terms (see next section), which
have to be assigned to the Business Partner data (Sales Area Data # Billing):

Generated by Jive on 2015-04-28+02:00

5

SEPA Configuration/Set-Up Guide

1.4.2

Define Terms of Payment

In the Customizing activity Define Terms of Payment, Payment Terms for SEPA for which the checkbox
PayMeth. (Payment Method) is checked needs to be defined:

Generated by Jive on 2015-04-28+02:00

6

SEPA Configuration/Set-Up Guide

Customizing of terms of payment data maintained in SAPERP can be loaded to SAP CRM by means of the
initial download (R3AS). The download now includes the field PayMeth.
Terms of Payment are defaulted based on the payer master data.

1.4.3

Define Countries Relevant for SEPA

In CRM: SM30: View: V_T005SEPA. AP introduced some new customizing in View. V_T005SEPA. Here you
can define which countries are relevant for SEPA:

FM: SEPA_COUNTRY_SPECIFIC_CHECKS

1.4.4

Define Modifiable Fields for Mandate Versioning

Delivery Customizing can be displayed in transaction SM30, Table View: V_SEPA_SFIELDS.

You can overwrite this or include further fields in View V_SEPA_FIELDS.

Generated by Jive on 2015-04-28+02:00

7

SEPA Configuration/Set-Up Guide

1.4.5

Define that CRM Billing Application is to Support SEPA

The Billing Application being used needs to be defined as being able to support SEPA in Customizing for
Customer Relationship Management under Billing
# Configure Application. This must be activated in order for the mandate information to be transferred to your
financial accounting system (for example, in SAP ERP).

Generated by Jive on 2015-04-28+02:00

8

SEPA Configuration/Set-Up Guide

Note: After setting the checkbox, you have to regenerate the Billing Application!

1.4.6

Define Incompleteness Procedure

An incompleteness procedure ensures that the user is informed about missing mandate information in a
business transaction.
The incompleteness procedure SEPA is available
The incompleteness message is only shown if the business transaction is SEPA relevant

SAP Implementation Guide # Customer Relationship Management # Transactions # Basic Settings #

Incompleteness Check # Define Incompleteness Procedures.

Generated by Jive on 2015-04-28+02:00

9

SEPA Configuration/Set-Up Guide

If you want to enable incompleteness checks, maintain the sub-dialog Assignment: Transaction Type
Incompleteness Group and create a new entry for a dedicated transaction type.

1.5

CRM UI Configuration

1.5.1

Bank Details AB in CRM Account OVP (FI-AR)

Generated by Jive on 2015-04-28+02:00

10

SEPA Configuration/Set-Up Guide

1.5.2

Bank Details AB in CRM Account OVP (FI-CA)

1.5.3

Mandates View Set in Bank Details Form View (FI-AR)

Generated by Jive on 2015-04-28+02:00

11

SEPA Configuration/Set-Up Guide

1.5.4

Mandates View Set in Bank Details Form View (FI-CA)

Note the additional fields Business Agreement, Subapplication, Contract that are available for the FI-CA
scenario.

1.5.5

Mandates AB in CRM Account OVP (FI-AR)

The Mandates AB is available via configuration only.

Generated by Jive on 2015-04-28+02:00

12

SEPA Configuration/Set-Up Guide

1.5.6

Mandate Details View (FI-CA)

Note the additional fields Business Agreement, Subapplication, Contract that are available for the FI-CA
scenario.

1.5.7
Billing Assignment Block in CRM Service/Sales
Transactions
Mandate ID, Status, and Payment Method are hidden fields in the default UI configuration, as these fields are
typically only relevant for customers in the Euro zone. Change the UI configuration of relevant sales or service
transactions and add these fields to the Billing assignment block at header and item level:

1.5.8

CRM Billing Document

Generated by Jive on 2015-04-28+02:00

13

SEPA Configuration/Set-Up Guide

Payment Terms, Mandate ID, and Payment Method are hidden fields in the default UI configuration, as these
fields are typically only relevant for customers in the Euro zone. Change the UI configuration and add these
fields to the Billing Document Details assignment block:

1.6

FI-AR Specifics in CRM

1.6.1

Scenario Prerequisites

As a first prerequisite the SAP CRM system needs to be connected with the SAP ERP (FI-AR) system so that
accounts created in SAP CRM are distributed to SAP ERP and created there as Customers (and vice versa).
In addition, in Customizing table SEPA_CUST the SEPA Mandate Management application CRM with ERP
Accounts Receivable needs to be set as active in CRM. You can check this in the SAP Reference IMG under
Customer Relationship Management # Master Data # Business Partner # Make Settings for SEPA Mandates:

Generated by Jive on 2015-04-28+02:00

14

SEPA Configuration/Set-Up Guide

Navigate to the Details of the FI-AR Application to make further settings if required:

Note: No reference to a business agreement or contract is necessary in SEPA mandates that are distributed to/
from FI-AR of SAP ERP.

1.7

FI-CA Specifics in CRM

1.7.1

Scenario Prerequisites

As a first prerequisite the SAP CRM system needs to be connected with the SAP ERP (FI-CA) system so that
accounts created in SAP CRM are distributed to SAP ERP and created there as Customers (and vice versa).

Generated by Jive on 2015-04-28+02:00

15

SEPA Configuration/Set-Up Guide

In addition, in Customizing table SEPA_CUST the SEPA Mandate Management application CRM with ERP
Contract Accounts A/R and A/P needs to be set as active in CRM. You can check this in the SAP Reference
IMG under Customer Relationship Management # Master Data # Business Partner # Make Settings for SEPA
Mandates:

Navigate to the Details of the FI-CA Application to make further settings if required:

Generated by Jive on 2015-04-28+02:00

16

SEPA Configuration/Set-Up Guide

When replicating the business agreement in an ERP system, the values are entered in the corresponding fields
of the .

1.8

SEPA Integration in ERP

1.9

SEPA Business Function/Switches in ERP

1.10

SEPA Documentation in ERP

1.10.1

Application Help: SEPA Mandates

Generated by Jive on 2015-04-28+02:00

17

SEPA Configuration/Set-Up Guide

1.10.2

Application Help: SEPA Direct Debits

1.10.3
Application Help: Use of SEPA Mandates by Multiple
Applications
1.10.4

IMG Activity: General Settings (See IMG)

1.10.5

IMG Activity: Activate SEPA (See IMG)

1.10.6

IMG Activity: Define Terms of Payment (See IMG)

1.10.7
IMG Activity: Set Up Payment Methods per Country for
Payment Transactions (See IMG)

1.11

SEPA Customizing in ERP

Generated by Jive on 2015-04-28+02:00

18

SEPA Configuration/Set-Up Guide

1.12

FI-AR Specifics in ERP

Generated by Jive on 2015-04-28+02:00

19

SEPA Configuration/Set-Up Guide

Generated by Jive on 2015-04-28+02:00

20

SEPA Configuration/Set-Up Guide

1.12.1

Define Terms of Payment

1.12.2
Define Payment Methods per Country for Payment
Transactions

Generated by Jive on 2015-04-28+02:00

21

SEPA Configuration/Set-Up Guide

Display Details of Payment Method:

Display Use in (Paying) Company Code:

Generated by Jive on 2015-04-28+02:00

22

SEPA Configuration/Set-Up Guide

1.12.3

Create/Change/Display a Customer in ERP (FI-AR)

In ERP: TA XD01/02/03 # Create/Change/Display Customer

1.12.4
in CRM

Create Distributed CRM Customer in a Company Code

If you want to create a mandate for a customer that has been created based on a distributed
account from CRM, make sure to create this customer in ERP in a company code:

Generated by Jive on 2015-04-28+02:00

23

SEPA Configuration/Set-Up Guide

You need to create this customer in the account group KUNA:

Generated by Jive on 2015-04-28+02:00

24

SEPA Configuration/Set-Up Guide

You need to create it with a company code, such as 0001

You need to create it with an external ID, starting with a letter, for example A100. Note:
The corresponding account in CRM will be created with the
same ID. If this already exists in CRM an error occurs. Please use a different ID in such a
case.

1.13

FI-CA Specifics in ERP

Generated by Jive on 2015-04-28+02:00

25

SEPA Configuration/Set-Up Guide

Further Hints

2.1

Data Replication

2.1.1

Data Replication of Accounts from CRM

Ensure that you maintain your CRM Accounts with the role Sold-To Party to enable them to be replicated to the
ERP system.

2.1.2

Data Replication of Mandate Changes (CRM to ERP)

Note that in the FI-AR scenario there is a check on the ERP side that the location, signature and SWIFT code
are needed in order for a Mandate to be replicated from CRM to ERP. Therefore, in order to be replicated from
CRM to ERP:
Active mandates need a signature date and location
Mandates need a SWIFT code

If changes do not automatically arrive in ERP:

Start SMQ2 in CRM-System (Q2D/504)
Unlock queue with name R3AUBUPA<account ID>

2.2

Authorization Object for Mandates in ERP

Users need to have the following authorizations in ERP for mandates:

Authorization Object: F_MANDATE
BUKRS = *
ACTVT = *

Generated by Jive on 2015-04-28+02:00

26

SEPA Configuration/Set-Up Guide

2.3

IBAN/SWIFT Calculation

For calculating IBAN / SWIFT you can use: http://www.iban-swift-bic-rechner.de/.

IBANs are NOT generated automatically in the CRM WebClient UI. However, in the ERP system you can call
transaction XD02 (Change Customer) and maintain Bank Details for a customer including an IBAN on the
Payment Transactions tab. On saving,
these Bank Details and IBAN should also be available in the CRM WebClient UI.

2.4

Paying Company Codes

If a creditor is not available in the CRM WebClient UI, call transaction FBZP (Maintain Payment Program) in the
ERP system and click on the button Paying Company Codes, to display a list of available company codes and
their details.

3
Rollout Material/Presentations/
Further Information
SEPA Note: 1828238: This note provides customers with an overview of the SEPA functionality. A presentation
is also available as an attachment to the note.
European Payments Council: SEPA Direct Debit (SDD)

Generated by Jive on 2015-04-28+02:00

27

SEPA Configuration/Set-Up Guide

Generated by Jive on 2015-04-28+02:00

28