Last Review: 26th July 2019

Remarks: This blog will be updated accordingly

Reading Time: 5 minutes

Managing Payment Media can be time consuming and requires extensive testing not only for the media generation, but also integration to the banks.

While in the On Premise world we could easily add custom code using user exits to quickly create content, in S/4HANA Cloud this option is greatly reduced focused largely on using the SSCUI “Map Payment Format Data” to map the outgoing files according to the requirement of the bank.

If you are now just starting your S/4HC journey and you consider one or more payment formats as part of the project scope, check the content below.

Pre-delivered Formats

SAP delivers a lot of standard formats that follow specific rules depending on the country. These formats can be used as an accelerator in order to meet the specific requirements of the bank. So, let’s look at two examples:

  •       CGI: DMEE XML Format as per ISO20022 – these formats follow an ISO standard for electronic data interchange between financial institutions. Each country has its own specification but SAP currently delivers a single version across countries.

  •       Country/Region Specific Payment Formats – besides the ISO mentioned in the aforementioned example, some countries have other very specific requirements – these include for example:

a.       Febraban format for Brazil

b.       BACS format for the United Kingdom

c.       ACH for US

SAP also delivers pre-build formats for other countries. You can find information on the delivered formats here .

What if the format delivered by SAP is not enough?

Although banks will follow the general standards outlined for a specific format, sometimes customers may need to change the mapping rules of the format in order to align to the bank specific requirements. Examples of such changes include:        

  • concatenation of fields to support reconciliation
  • setting of fields from optional to mandatory
  • replacing the standard mapping for customer specific mapping

It’s not possible to edit the format mapping delivered by SAP, instead you may copy the required format and adjust it in accordance to your needs.

In the following section, you may find some of the steps involved in adapting payment formats to meet specific project requirements.  

In the SSCUI Map Payment Format Data (100558), it is possible to import, add new nodes, edit existing attributes to ensure the financial institution can process your payment.

Note that, currently, mapping Payment Format Data has very limited extensibility options. Despite that, it is possible to add custom fields. For more details, read the following blog

Can I have tested mapping formats and use them?

In order to accelerate implementation, you may find some mapping formats attached that have already been tested with banks in certain countries.

As a disclaimer: please note that these formats are provided as an accelerator only and may still need to be reviewed and aligned to the specific bank/country requirements.

The list below shows the formats available with the respective bank. Please note that you should always test the formats with your bank.

Format Name

Bank

Country

Format

NL_CGI_XML_001

CITI

NL

WorldLink

NL_CGI_XML_002

CITI

NL

WIRE

NL_CGI_XML_003

CITI

NL

SEPA

GB_CGI_XML_001

CITI

GB

Wire

GB_CGI_XML_002

CITI

GB

SEPA

VE_MER_FLATFILE_001

Mercantil

Venezuela

n/a

VE_BVC_FLATFILE_001

BVC

Venezuela

n/a

Find the formats here


To use the available mapping formats, it is necessary to create a new Payment Medium format and use the import function.

How to:       

In Manage your solution go to SSCUI 500283 – Manage Payment Media – this SSCUI is the main configuration point. The last step is to assign the format created to a payment method.

       1)   Start with task ID 100558 – Map Payment Format Data
It you want to create an .xml file, you can create a new one or copy an existing one under a tree node, like in the example below. It is advisable to create one using the latter approach.

       2)  In task ID 102 569, you can create a payment medium format and define its attributes

       3) You can now go back to Map Payment Format Data – it is time to import one of the pre built files.

       Select the Payment format created in step 1 and press Import.
You may see the following error:


In order to fix this, you need to change the Parent ID Tree in the .xml file.

If you don’t have an xml editor, it is possible to use Notepad. Open the file in Notepad and make changes in the following tags:

<TreeID>

</XML_TREE><PARENT_ID>

Replace the content in this tag for the payment mapping name you gave the file.

After successfully importing the file, you may require to test tag mapping, as you may need to make some changes. To better understand the options for editing the payment formats, please visit the Help Portal here

Now it is time to link this payment format to a payment method.
In SSCUI 500012 – task ID 101972 - Set Up Payment Methods per Country for Payment Transaction

Other useful information

For further details on the functions of Map Format Data SCCUI, please check the help portal here

Other Blogs in the series:

Blog II - How to Create Payment Media Format 

Blog III - How to Create Payment Media Format - Real Examples