SAP Central Finance & SEPA Mandates scenario

[nitin_gupta10]

In this particular blog I will discuss how SEPA Mandates (will say SEPA-M from now) are managed in SAP S/4HANA Central Finance (will say CFIN from now).

Before we start with the SEPA-M set up in CFIN, lets understand quickly what’s SEPA – M.

A SEPA Mandate is the authorisation for direct debit given by the customer, which allows the vendor to collect any future business payments from them at any time on their Euro-denominated bank account, of course with due advance notice.

(SEPA – Single Euro Payment Area)

 

Now assuming that this is already set up and running in source ECC system we need to plan to load/replicate this to CFIN system. Before we talk about the technical details, let’s summarise how SAP CFIN supports SEPA-M.

NOTE – This is ONLY needed when Central Payments is activated in SAP CFIN System

• Initial Load
  
  
  
  • In Initial Load the SEPA-M data can be classified by validity date and can be migrated to CFIN via standard SAP Load process
  
  
  
  


• Real time Replication & Error Handling
  
  
  
  • Real time replication of SEPA-M is standard SAP and is supported in AIF error handling.
  
  
  • Name Space - /FINCF
  
  
  • Interface for create - ISEPA_CR_01
  
  
  • Interface for change – ISEPA_CH_01
  
  
  • Interface for save – ISEPA_SR_01
  
  
  
  


• Mappings
  
  
  
  • Mappings are already completed for customer and company codes in SAP (FINS_CFIN_MAP_MANAGE) so those mappings can be leveraged.
  
  
  
  

Reconciliation tool

SAP has provided standard reconciliation tool for SEPA-M. It can be executed as below:

SE38 >> FINS_CFIN_APAR_SEPA_REC >> Enter the criteria >> Execute

Now you will have the result of the reconciliation. Below actions can be done now:

• Review the comparison results for a mandate.


• Modify a mandate if needed


• Synchronize the data for one or more mandates.


• Refresh the comparison result if changed

 

Configuration in Source System:

1. Transaction SM30 >> V_SEPA_CUST

Parameter	Value
ALE: Logical Name of the Consolidation System	PD0CLNT700 (example name of CFIN)
ALE: Load Additional Data	FIN_CFIN_APAR_SEPA_LOAD_SRC
ALE: Unload Additional Data	FIN_CFIN_APAR_SEPA_UNLOAD_SRC
ALE: Filter Data	FIN_CFIN_APAR_SEPA_ALE_FILTER
Function Module for Settable Button 2	FIN_CFIN_SEPA_MIGRATE_BUTTON

 

2. Transaction BD95 >> Specify ALE Objects

• ALE Object Type – Receiver


• Table Name – TBD06


• Field Name – RCVSYSTEM

 

3. Transaction BD96 >> Filter Objects

• Object Type - SEPAMANDAT


• Method – CREATE/CHANGE


• Filter Object Type – RECEIVER

 

4. Transaction BD64 >> Maintain Distribution Model

• Here we need to add the distribution model for all source systems


• Also add a filter group to the BAPI & expand the node for the distribution model and find the receiver determination node under the BAPI method

Configuration in SAP S/4HANA CFIN System:

1. Launch the Customizing activity Enable SEPA for Applications as below

CFINIMG >> Central Payment >> SEPA

Parameter	Value
ALE: Logical Name of the Consolidation System	PD0CLNT700 (example name of CFIN)
ALE: Load Additional Data	FINS_CFIN_APAR_SEPA_LOAD
ALE: Unload Additional Data	FINS_CFIN_APAR_SEPA_UNLOAD
ALE: Filter Data	FINS_CFIN_APAR_SEPA_ALE_FILTER

 

2. CFINIMG >> Central Payment >> SEPA

• ALE Object Type – Receiver


• Table Name – TBD06


• Field Name – RCVSYSTEM

 

3. CFINIMG >> Central Payment >> SEPA

• Object Type - SEPAMANDAT


• Method – SAVEREPLICA


• Filter Object Type – RECEIVER

 

4. CFINIMG >> Central Payment >> SEPA

• Maintain Distribution Model


• Also add a filter group to the BAPI & expand the node for the distribution model and find the receiver determination node under the BAPI method

Key SAP Notes:

1. 1845440 - SEPA composite: Mandates and IBAN


2. 1887572 - SEPA mandates: ALE distribution - tips


3. 1882430 - SEPA mandates: ALE distribution in SEPA mandate management

 

Happy reading & keep learning..