Skip to Content
Author's profile photo Former Member

SEPA: When moving to SEPA in SAP CRM?

Moving to SEPA functionality provided by SAP in standard is a huge challenge for many customers.

It is clear that SAP ERP has a higher priority in this context than SAP CRM. So it is often a question if and when it makes sense to also move SAP CRM to the SEPA functionality provided by SAP in standard.

I would like to provide you some hints that hopefully make this decision a little bit easier.

The main question you need to answer is: Do we actually need SEPA mandates in SAP CRM? Really in SAP CRM, directly integrated, for example in the bank data of the account, stored and integrated with SAP ERP via data replication.

If you only need to be able to maintain SEPA mandates, in the CRM WebClient UI, – only the UI aspect is important here -, then you are possibly okay with having SEPA mandates in SAP ERP only but integrating the maintenance via the transaction launcher. This probably means own effort on your side, but overall it could be at least a first option for you.

As soon as you need to consider SEPA mandates also in business transactions replicated between SAP CRM and SAP ERP you have no real choice any more. In this case I would recommend to better move to SEPA functionality provided by SAP in standard, as soon as possible. You need such a tight integration of SEPA mandates in your CRM processes that trying to adapt on your own only a little bit can lead to more difficulties and more effort than expected.

An example for such a case is: Use of  a SEPA mandate in a service contract.

You can find the details about SEPA in SAP CRM in SAP Note 1828238.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Christian Drumm
      Christian Drumm

      Hi Jutta,

      IMHO there is also a third option, to maintain the SEPA mandates in ERP and perform the CRM integration via UI enhancements and RFC. This has some advantages over the transaction launcher based approach. For example, it is possible to display the state of SEPA mandates inside the appropriate views. This is particularly useful in call center scenarios where one wants to avoid jumping between several screens. Furthermore, this enables us to integrate SEPA mandates into the business processes. It is, for example, possible to trigger the creation of a SEPA mandate from within a guided procedure (e.g. the move in process in the utilities industry). This wouldn't be possible with a transaction launcher based approach.

      If implementing the replication of the SEPA mandates is an option this is the best choice. However, in scenarios where this is not possible (e.g. due to the wrong EhP level) the integration via UI enhancements and RFCs provides a nice alternative.



      Author's profile photo Former Member
      Former Member
      Blog Post Author

      Hi Christian,

      You are right. This is an additional option, and a very reasonable one.

      Overall on the long-term I would always try to go for the standard solution provided by SAP. But dependent on the situation it can make sense to have an intermediate solution approach; for example the one that you suggested.