Peliminary Version Document

Document version: 1.1

User Guide for Implementing and Configuring Payment

Medium Formats (CGI-XML-CT and CGI-XML-DD)
Contents
1 Introduction ...................................................................................................................................................... 3

1.1 Step 1: Implement SAP Notes ......................................................................................................................... 4

1.2 Step 2: Create New or Update Existing XSLT Transformation........................................................................... 5

1.3 Step 3: Create a New or Update Existing DMEE Tree ....................................................................................... 6

Step 3.1 Additional Payment Format Parameters ........................................................................................... 6

Step 3.2 How to Use Instruction Keys in the CGI Solution for Credit Transfer Payments ................................. 9
1.4 Step 4: Customizing Settings for Payment Media .......................................................................................... 12

1. Create Payment Medium Formats (OBPM1 transaction) ......................................................................... 12

2. Adjust Note to Payee (OBPM2 transaction) ............................................................................................. 13
3. Create/Assign Selection Variants (OBPM4 transaction)............................................................................ 14
4. Assign Payment Medium Format and Note to Payee to Payment Method ............................................... 16
5. Set House Bank and Enter Bank Determination Details ............................................................................ 16
6. Create BAdI Implementation as Customer Enhancement in CGI............................................................... 17
1.5 Step 5: Post Customer/Vendor Invoices ......................................................................................................... 20

1.6 Step 6: Execute Payment Run and Generate Payment Medium File ............................................................... 20

2 Additional Information .................................................................................................................................... 21

1. Bank Communication Management ........................................................................................................ 21

2. List of Supported Countries ..................................................................................................................... 21

Preliminary version
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
1 Introduction
According to new regulations regarding the use of payment formats, the 2253571 SAP Note provides you with a
solution on implementing CGI (Common Global Implementation) payment formats for those countries that
support payments in XML file format according to the ISO 20022 standard, and also how these standard payment
formats can be enhanced with country-specific requirements. These payment formats support SEPA, non-SEPA
and check payments as well.
The following payment formats are used:
• CGI_XML_CT payment format for CGI credit transfer (for example, pain.001.001.03 and higher versions),
and its enhancement using a BAdI concept.
• CGI_XML_DD payment format for CGI direct debits (for example, pain.008.001.02 and higher versions),
and its enhancement using a BAdI concept.

We introduce a BAdI concept that you can use to enhance these payment formats according to country-
specific requirements. The payment formats use DMEE trees (called CGI_XML_CT and CGI_XML_DD).
Prerequisites
As a prerequisite to implement SAP Note 2253571 and all its related SAP Notes, ensure that you already have the
SEPA function installed in your system, that is, the SAP Note 1845689 is implemented.

Process
1. You either download the relevant support package listed in PF_Notes_and_SPs_2253571.xlsx
attachment of the 2253571 SAP Note, or you manually implement all the related SAP Notes.
2. If you manually implement the SAP Notes, you then need to create a new XSLT transformation
(IDFI_XML_XSLT), or update an existing one.
3. You upload or create a new DMEE tree.
4. You make Customizing settings in the system for the use of the CGI_XML_CT and CGI_XML_DD payment
formats in your country.
5. You post vendor or customer invoices.
6. You execute the payment run and from here you generate the payment format.

Let’s have a look at the steps of the process in detail one by one.
Please note that certain steps contain specific settings and other steps contain general descriptions, not specific
data. In such steps, you need to enter data according to your requirements. The steps highlight the basic
requirements so that you can use the payment formats but does not give you full description on the general
settings for payments.

Preliminary version
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
3
1.1 Step 1: Implement SAP Notes
So that you can use the function, do the following:
• You can either download the highest possible support package that is available for your release that
contain the changes as listed in PF_Notes_and_SPs_2253571.xlsx attachment of the 2253571 SAP Note.
• You manually implement all the related SAP Notes as it is explained in the following video:

https://www.youtube.com/watch?v=JUCDqtfNk0s

Please note that the system setup of your system can differ from those ones that you can see in the
video.

Preliminary version
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
1.2 Step 2: Create New or Update Existing XSLT Transformation
If you have downloaded the highest available support package in your release, you can skip this step.
If you have manually implemented the SAP Notes, you additionally need to create a new XSLT or update an
existing one. To do so, proceed as follows:
Create new XSLT transformation IDFI_XML_XSLT
1. Download the IDFI_XML_XSLT.TXT file attached to SAP Note 2253571 to your local PC
2. Run transaction XSLT_TOOL
3. Enter transformation IDFI_XML_XSLT 4. Choose the Create button or press [F5] 5. Enter the
following parameters: o Transformation: IDFI_XML_XSLT o Short Text: XSLT Transformation to
Remove All Empty Nodes o Transformation Type: XLST Program
6. Save your entry or press [Enter]
7. Enter package: ID-FI-REU-PAYM and choose Save or press [Enter]
8. Copy the content of the IDFI_XML_XSLT.TXT file to the Source Code tab page
9. Activate the IDFI_XML_XSLT XSLT transformation or press [Ctrl+F3]

Update existing XSLT (if you use an older version)

If you have customer-specific modifications of the original XSLT, make a backup copy of the modified
XSLT using transaction XSLT_TOOL (Ctrl+F5) before you update it to the new version. To update your
existing XSLT, proceed as follows:
1. Download the IDFI_XML_XSLT.TXT file attached to SAP Note 2253571 to your local PC
2. Run transaction XSLT_TOOL in Change mode
3. Copy the content of the IDFI_XML_XSLT.TXT file
4. In the Source Code tab page, replace the existing content with the new one by pasting the copied
content
5. Check the correctness of the previous step with Ctrl+F2
6. Activate the new XSLT with Ctrl+F3

Preliminary version
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
5
1.3 Step 3: Create a New or Update Existing DMEE Tree
If you have downloaded the highest available support package in your release, you can skip this step.
If you have manually implemented the SAP Notes, you additionally need to create a DMEE tree or update your
existing one as follows:
1. Upload/Create new DMEE tree
• To update the version of the DMEE tree, please download the CGI_XML_CT_YYMMDD.XML
(YYMMDD refers to the version attached to the SAP Note) and CGI_XML_DD_YYMMDD.XML files
attached to SAP Note 2253571 to your local PC.
• If you have customer-specific modifications of the original DMEE tree, make a backup copy of the
modified tree by downloading the tree in transaction DMEE before uploading its new version. The
tree is overwritten during upload. If you do not want the standard SAP tree to be overwritten, change
the format name in the DME definition XML file in a text editor before you perform the upload
(change a content of the XML element <Name>... </Name>).
• Log on in the language in which you want to use the DMEE tree (payment format)
• When you perform the upload, the original language of the tree changes to the current logon
language. Later on, the tree can only be changed in the original language
• Press Enter to confirm the warnings that appear during the upload
• If the system display error message DMEE_ABA 130, you need to check your SAP_ABA release and
change the release information in the XML element <BasisRelease> ... </BasisRelease> accordingly
before uploading.
If you have any problems with uploading the DMEE tree, check and implement SAP Note 2309792.

Step 3.1 Additional Payment Format Parameters

SAP delivers common structure named FPM_CGI containing basic set of payment format parameters:
• XML Namespace of Data Medium
• XML Namespace of Schema
• XML Location of Schema
• Structured Remittance Info
• Country ISO code
• Version ID for International Addresses
• Requested Execution Date
• Execute Batch Booking
What steps do I need to perform to add supplementary payment format parameters used only in my project?
First you need to create the DDIC structure which will contain fields for additional payment format parameters.
This will be an append structure of the DDIC structure FPM_CGI that SAP delivers.
1. In transaction SE11 enter Data type FPM_CGI and choose option Display.
2. Then choose from menu option GoTo -> Append Structure.
3. Enter the name of the append structure, for example, ZFPM_CGI_APPEND which will be holder for
additional payment format parameters.
4. Fill in the short description for the append structure - for example, Append Structure for FPM_CGI.
5. You can include an already existing structure created and delivered by SAP or your own existing structure
created in a project environment.
Preliminary version
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
 6. You can enter additional parameters.

The result can look like this:

7. Activate the append structure with [Ctrl+F3].

The appended DDIC structure FPM_CGI can be:

Where I can use these supplementary payment format parameters?

• with the DMEE tree definition as a source of information for the selected node:

• with the conditions used for the selected node:

Preliminary version
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
7
 • fields are ready for usage in the DMEE tree:

• with the selection on payment run (for example, transaction FBPM):

Do I still need to perform other steps?

Only in case you have had a Customer Structure filled in and you now included fields from this Customer
Structure into FPM_CGI append structure, please remove the customizing of Customer Structure in the OBPM3
transaction:

Preliminary version
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
 Step 3.2 How to Use Instruction Keys in the CGI Solution for Credit Transfer
Payments
This document contains recommended settings for the Instruction Keys. When new codes are needed, please
enhance the customizing. For any additional logic, create your own Enhancement Implementation for BAdI
FI_CGI_DMEE_COUNTRIES_CUST.
Where to enter Instructions?
The instructions in the payment transactions are used to give the bank details on how to carry out the payment
orders. Instructions can be defined
1. in the document
2. in the customer/vendor master record using an instruction key
3. in the house bank DME data using the default instruction key
The instructions from the document are used with higher priority, if one of the four fields has been filled out.
Note that we do not recommend that you change the Instruction key during editing the payment proposal.
Instruction 1 (DTWS1)
This key is used to define the code value for the Service Level Code <PmtTpInf><SvcLvl><Cd> or the Check Type
<PmtInf><CdtTrfTxInf><ChqInstr><ChqTp> Recommended way:
In Customizing for Financial Accounting (New) under Accounts Receivable and Accounts Payable → Business
Transactions → Outgoing Payments →Automa c Outgoing Payments → Payment Media → Data Medium
Exchange → Define Instruc ons for Payment Transac ons, enter instructions that control the way in which a
payment is made for a credit institute at two different points in the system as follows:
1. Create application area CGI with short name ISO20022.
2. Define permitted instructions: field 1.
3. Save your entries.
4. Create instructions for field 1 on the Instructions screen:

Preliminary version
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
9
 5. Save your entries.

Instruction 2 (DTWS2)
This key is used to define the code value for the Service Level Code <PmtTpInf><SvcLvl><Cd> or the Check Type
<PmtInf><CdtTrfTxInf><ChqInstr><ChqTp> Recommended way:
In Customizing for Financial Accounting (New) under Accounts Receivable and Accounts Payable → Business
Transactions → Outgoing Payments →Automa c Outgoing Payments → Payment Media → Data Medium
Exchange → Define Instruc ons for Payment Transac ons, enter instructions that control the way in which a
payment is made for a credit institute at two different points in the system as follows:
1. Create application area CGI with short name ISO20022.
2. Define permitted instructions: field 2.
3. Save your entries.
4. Create instructions for field 2 on the Instructions screen:

5. Save your entries.

Payment Type (DTZKA)

This key is used to define the code value for the Instruction Priority in <PmtTpInf><InstrPrty> or the Check
Instruction Priority <CdtTrfTxInf><ChqInstr><InstrPrty>.
There are only two possible values for Instruction Priority: HIGH or NORM according to ISO20022.
When you want to indicate that, the payment should be handled with HIGH priority and you need to do following
steps:
1. In Customizing for Financial Accounting (New) navigate to Accounts Receivable and Accounts Payable →
Business Transactions → Outgoing Payments →Automa c Outgoing Payments → Payment Media → Data
Medium Exchange → Define Instruc on Keys.
2. Enter your bank country in the popup screen and choose Continue.
Preliminary version
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
 3. Choose New Entries.
4. Enter an instruction key (for example, 9) in the Instruction Key field.
5. Enter value 1 in the Payment Type field in group box Payment Medium Instructions and any other values
according to your requirements.
6. Save your changes and use the instruction key (9 in this example), for example in the House Bank settings
(transaction FI12).

Cost Allocation Key (DTKVS)

For SEPA payments created via CGI format, the information in the XML tag <PmtInf><ChrgBr> is always SLEV.
For non-SEPA payments, the information in <PmtInf><CdtTrfTxInf><ChrgBr> is handled via the cost allocation key
in the Define Instruction Keys Customizing activity.
1. In Customizing for Financial Accounting (New) navigate to Accounts Receivable and Accounts Payable →
Business Transactions → Outgoing Payments →Automa c Outgoing Payments → Payment Media → Data
Medium Exchange → Define Instruc on Keys.
2. Enter your bank country in the popup screen and choose Continue.
3. Choose New Entries.
4. Enter data as follows in the Cost allocation key field:
a. 00 (empty) for SHAR (Both parties bear their own charges)
b. 01 for DEBT (All transaction charges are to be borne by the debtor)
c. 02 for CRED (All transaction charges are to be borne by the creditor)
5. Save your changes and use the instruction key (9 in this example), for example in the House Bank settings
(transaction FI12).

Preliminary version
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
11
1.4 Step 4: Customizing Settings for Payment Media

1. Create Payment Medium Formats (OBPM1 transaction)

Create the CGI_XML_CT and CGI_XML_DD payment formats in transaction OBPM1 or in Customizing for Financial
Accounting (New) under Accounts Receivable and Accounts Payable → Business Transac ons → Outgoing
Payments →Automa c Outgoing Payments → Payment Media → Make Se ngs for Payment Medium Formats
from Payment Medium Workbench → Create Payment Medium Formats as follows:
CGI_XML_CT Payment Medium Format
1. Open the Customizing activity in change mode and choose New Entries.
2. Enter the CGI_XML_CT format name in the Format field and the DMEE XML Credit Transfer Format
as per CGI in the Description field.
3. In the Format Output group box, select the Payment medium without docs checkbox and choose 04
XML in its Type field.
4. In the Format Information group box, enter the FPM_DOCU_CGI_XML_CT technical name in the
Documentation module field.
5. In the Program Control group box, enter FPM_CGI in the Struct. for format parameters field, and
select the Mapping using DME engine checkbox.
6. In the Payment medium output divided by level of detail group box, select the Company code and
the House Bank checkboxes.
7. Then navigate to the Event Modules for Payment Formats screen.
8. Attach function module FI_PAYMEDIUM_DMEE_CGI_05 to the format. To do this, choose New
Entries and select Event 05.
9. Then navigate to the Text Fields for Reference Information screen and set the following entries:
Type Field Length No. of Fields

1 Note to payee including lines 35 4

for header
2 Short entry for note to 35 1
payee, internal
3 Short entry for note to payee, 35 1
external
CGI_XML_DD Payment Medium Format
1. Open the Customizing activity in change mode and choose New Entries.
2. Enter the CGI_XML_DD format name in the Format field and the DMEE XML Direct Debit Format as
per CGI in the Description field.
3. In the Format Output group box, select the Payment medium without docs checkbox and choose 04
XML in its Type field.
4. In the Format Information group box, enter the FPM_DOCU_CGI_XML_DD technical name in the
Documentation module field.
5. In the Program Control group box, enter FPM_CGI in the Struct. for format parameters field, and
select the Mapping using DME engine checkbox.
6. In the Payment medium output divided by level of detail group box, select the Company code and
the House Bank checkboxes.
7. Then navigate to the Event Modules for Payment Formats screen.
8. Attach function module FI_PAYMEDIUM_DMEE_CGI_05 to the format. To do this, choose New
Entries and select Event 05.
9. Then navigate to the Text Fields for Reference Information screen and set the following entries:

Preliminary version
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
 Type Field Length No. of Fields

1 Note to payee including lines 35 4

for header
2 Short entry for note to 35 1
payee, internal
3 Short entry for note to payee, 35 1
external
You can modify any of these payment medium formats in in Customizing for Financial Accounting (New) under
Accounts Receivable and Accounts Payable → Business Transac ons → Outgoing Payments → Automa c
Outgoing Payments → Payment Media → Make Se ngs for Payment Medium Formats from Payment Medium
Workbench → Adjust Payment Medium Formats (or transaction OBPM3).

2. Adjust Note to Payee (OBPM2 transaction)

A note to payee is a field on a data medium containing information on paid line items relevant for the business
partner.
Number and length of the note to payee fields are defined in the payment medium format, whilst the content
itself is defined in the note to payee.
To adapt a note to payee, use transaction OBPM2, or in Customizing for Financial Accounting (New), choose
Accounts Receivable and Accounts Payable → Business Transac ons → Outgoing Payments → Automa c Outgoing
Payments → Payment Media → Make Se ngs for Payment Medium Formats from Payment Medium
Workbench → Adjust Note to Payee.
The note to payee consists of a maximum of 6 different line types:
1. Main note to payee for description of the payment, for example with the payment of invoices in the lines
there is the invoice number, the invoice date, and/or the invoice amount.
2. Internal short reference for your company for identification of the transaction in case of failed payment.
This could be the number of the payment document, for example.
3. External short reference for your business partner, a contract/customer number, for example.
4. Payment advice note that replaces the lines of type 1 where there is not sufficient space available.
The note to payee is independent of format, a separate entity that exists alongside the formats. You can assign
the note to payee to a format via the payment method and the origin. You can assign a note to payee to several
formats, thus minimizing the effort involved.
For more information, read the Customizing documentation in the system.
Example

Line type 1 Main note to payee line 1 No. 746 999 from 01.01.2000

Line type 1 Main note to payee line 2 No. 333 934 from 02.15.2000

Line type 1 Main note to payee line 3 No. 4 734 from 02.20.2000

Line type 1 Main note to payee line 4 Visit our homepage: www.sap.com

Line type 2 Internal short reference Payment document 6 785 987

Preliminary version
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
13
 Line type 3 External short reference Our account with you: 345 876

Alternative Payer, Alternative Payee

This example shows in combination in the Payment Medium Workbench how you can handle two special
cases, namely the alternative payer and the alternative payee.
The Note to Payee consists of up to 6 different line types. Line types 5 and 6 are intended for following
special cases:
● Line type 5 supplements the text of line type 1 through specification of an invoicing party where the
payment is made to an alternative payee.
● Line type 6 supplements the text of line type 1 through specification of an invoice recipient where the
payment is made from an alternative payer.

3. Create/Assign Selection Variants (OBPM4 transaction)

Note:

Selection variant maintenance is a requirement for automatically scheduling the payment media of the Payment
Medium Workbench in the payment program (only).

You can generate payment media file in two ways:

1. Using the F110 payment program
In this case you need to make settings in Customizing for Financial Accounting (New), choose Accounts
Receivable and Accounts Payable → Business Transac ons → Outgoing Payments → Automa c Outgoing
Payments → Payment Media → Make Se ngs for Payment Medium Formats from Payment Medium
Workbench → Create/Assign Selec on Variants (or transaction OBPM4).
2. Using transaction FBPM
In this case you do not need to make settings in Customizing (transaction OBPM4) as you enter the
variant directly to the report.

Prerequisites

You have determined the level of detail in Customizing for Adjust Payment Medium Format. The level of detail
governs how payment media are output in payment groups. In selection variant maintenance, the system
displays all defined payment groups that each require assignment of one selection variant.

Procedure

You can enter, assign, and transport selection variants for the generic payment medium program.
Assigning selection variants
At least 1 variant is defined in each payment group for each payment medium format. It is important to assign a
selection variant to each group to ensure that no payment is forgotten.
1. To assign a selection variant, in Customizing for Financial Accounting (New), choose Accounts Receivable
and Accounts Payable → Business Transac ons → Outgoing Payments → Automa c Outgoing Payments →

Preliminary version
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
 Payment Media → Make Se ngs for Payment Medium Formats from Payment Medium Workbench →
Create/Assign Selection Variants (or transaction OBPM4).
2. On the left side of the screen, select the payment medium format to which you want to assign a variant.
The system displays the format on the right side of the screen. In order to make the list easier to work
with, you can use Drag&Drop to copy formats to the favorites list.
3. When you place the cursor over a selection variant field and press F4 (input help) the system displays
possible variants.
4. Choose the variant you require.
5. Carry out assignment for each individual group level. You can speed up this process by using filter, copy,
selection, and paste functions.
6. Save assignment of the selection variants.

Creating selection variants

1. To create a selection variant, in Customizing for Financial Accounting (New), choose Accounts Receivable
and Accounts Payable → Business Transac ons → Outgoing Payments → Automatic Outgoing Payments
→ Payment Media → Make Settings for Payment Medium Formats from Payment Medium Workbench →
Create/Assign Selection Variants.
2. On the left side of the screen, select the payment medium format for which you want to create a variant.
The system displays the format on the right side of the screen.
3. Place the cursor over a selection variant field, enter a name for a new variant, and press continue.
4. The system displays a dialog box where you confirm variant creation.
5. The system displays the selection screen of the generic payment medium program SAPFPAYM.
6. Here, you enter the required selection criteria, then you maintain the attributes before saving the
variant.
7. Choose Back to return to selection variant maintenance for the payment medium formats.
8. Save assignment of the selection variants.

Note:
If you want to work with Dynamic selection you can enter several variants per group using the procedure
described above (Variant → Enter further variants). You should only use Dynamic selections to define
selection variants where no alternative exists. After this, you need to ensure that no payment order has been
carried out in duplicate and that only 1 payment medium has been created for each order.
You can increase the level of detail in Customizing (Adjust Payment Medium Format) as an alternative to
Dynamic selections.

Transporting selection variants

In selection variant maintenance for payment medium creation, it is possible to branch to transport of the
settings made and the selection variants for payment medium creation themselves.
1. To carry out the transport, in Customizing for Financial Accounting (New), choose 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/Assign Selection Variants.
2. To transport the selection variants, choose (Tansport variants to all formats).
3. To transport selection variant assignment, choose (Transport settings to all formats). You can decide
whether you transport the currently selected format or whether you transport all formats.

Preliminary version
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
15
Result

The payment program starts payment medium creation using each selection variant entered.

4. Assign Payment Medium Format and Note to Payee to Payment Method

In transaction FBZP – Pmnt methods in country or in Customizing for Financial Accounting (New), choose
Accounts
Receivable and Accounts Payable → Business Transac ons → Outgoing Payments → Automatic Outgoing
Payments → Payment Media → Make Settings for Payment Medium Formats from Payment Medium
Workbench → Assign Payment Medium Format and Note to Payee to Payment Method, make settings as
follows: Use Payment Medium Workbench
1. On the Change View "Payment Method/Country": Overview screen, call the required combination of
country and payment method by double-clicking the relevant row.
2. The Change View "Payment Method/Country": Detail screen appears.
3. In the Payment Medium screen area, select the Use Payment Medium Workbench option.
4. In the same screen area enter or check the Format and the Format Supplement (if any) and save your
entries.

Check Form Entries

1. In the upper screen area choose (Use in company codes).
2. The system displays the Display View "Maintenance of Company Code Data for a Payment Method":
Overview screen.
3. Choose the change mode and select your company code by double-clicking on it.
4. The system displays the Change View "Maintenance of Company Code Data for a Payment Method":
Detail screen.
5. Choose (Form Data) and check or supplement the existing forms for your company code.
6. Save your data and choose Exit
7. You return to the Change View "Payment Method/Country": Detail screen.

Check Note to Payee by Origin

1. In the selection tree choose Note to Payee by Origin
2. The Change View "Note to Payee by Origin": Overview screen appears.
3. Check or supplement the existing note to payee.
4. Choose Back.
5. You return to the Change View "Payment Method/Country": Detail screen.
6. Save your data.

5. Set House Bank and Enter Bank Determination Details

In transaction FBZP (Customizing: Maintain Payment Program) – Bank determination, or in Customizing for
Financial Accounting (New), choose Accounts Receivable and Accounts Payable → Business Transactions →
Outgoing Payments → Automatic Outgoing Payments → Payment Method/Bank Selection for Payment Program
→ Set Up Bank Determination for Payment Transactions, ensure that you have made all the settings you need.
For more information, read the Customizing documentation in the system.
Also, in transaction FBZP, choose House banks to make your house bank-related settings.
Preliminary version
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
 6. Create BAdI Implementation as Customer Enhancement in CGI
If you have downloaded the relevant support package, or you have manually implemented all the SAP Notes as
explained in Step 1: Implement SAP Notes (in the video), you can access the relevant Business Add-Ins (BAdIs)
that belong to the enhancement spot ES_IDFI_CGI_DMEE. The enhancement spot contains the following BAdI
definitions:

• BAdI for SAP Implementation (FI_CGI_DMEE_COUNTRIES)

This BAdI contains country-specific implementations that you can use to enhance the standard CGI
payment formats (CGI_XML_CT and CGI_XML_DD) with country-specific fields. Note:
You can only activate these BAdI implementations. You cannot make any change in them. If you want a
different behavior, you need to create your own implementation as explained below (BAdI for Customer).

• BAdI for Customer (FI_CGI_DMEE_COUNTRIES_CUST)

You can use this BAdI definition to create your own implementations. You can use these implementations
to modify some parts of the country-specific BAdI implementation that we deliver in the
FI_CGI_DMEE_COUNTRIES BAdI.

If there is no country-specific BAdI implementation that we provide, and you have not created any customer-
specific BAdI implementation, the system uses the CL_IDFI_CGI_DMEE_FALLBACK fallback class to generate the
XML file with the CGI_XML_CT or CGI_XML_DD DMEE trees.

You can access the BAdI implementations in Customizing for Financial Accounting (New), choose Accounts
Receivable and Accounts Payable → Business Transactions → Outgoing Payments → Automatic Outgoing
Payments → Payment Media → SEPA/CGI Payment Formats → Country-Specific Fields for CGI Payment Formats.

For more information, read the Customizing documentation in the system.

If you have not downloaded the relevant support package, create the enhancement spot and the BAdI
implementation manually as follows:
1. Run transaction SE19.
2. Enter the enhancement spot ES_IDFI_CGI_DMEE.
3. Choose Create.
4. Enter a technical name and a short text for the enhancement implementation:
5. Enter a technical name for your BAdI implementation and implementation class and enter
FI_CGI_DMEE_COUNTRIES_CUST in the BAdI Definition field.
6. The system creates the new BAdI Implementation with implementing class.
7. On the Enh. Implementation Elements tab page, create filter values by choosing Filter Val. on the left side and
then Combinations on the right side:
8. Select the following filters:
Filter Filter Type Filter Short Text

BANK_COUNTRY Character-like Country of the House Bank

CREDIT OR DEBIT Character-like Credit (for pain.001) or Debit (for

pain.008)

9. As the first filter value, enter the country of your house bank in the Value 1 field and save it.

Preliminary version
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
17
10. As the second filter value, enter either CREDIT or DEBIT depending on the functionality in the Value 1 field
and save it.
11. Activate the implementation.

Note:

After you have implemented SAP Note 2253924- CGI: CGI_XML_CT, CGI_XML_DD Format Updates #4, you might
face the issue that also o_value must be entered. You might have the following statement in your code:

CASE i_node_path.
WHEN '<PmtInf><-PmtTpInf>'.
c_value = abap_false.
ENDCASE.

that must be replaced with the following code (please note, that o_value is also changed):

CASE i_node_path.
WHEN '<PmtInf><-PmtTpInf>'.
o_value = abap_false.
ENDCASE.

Also, please note that at the beginning of your customer implementation we recommend that you clear
the C_VALUE, P_VALUE, and N_VALUE values. You can use the following coding for this purpose:
CLEAR: C_VALUE, P_VALUE, N_VALUE.

Example Customer Implementation for Denmark

Create customer BAdI Implementation of enhancement spot ES_IDFI_CGI_DMEE as follows:

1. Start transaction SE18 and choose Display.

2. The Denmark-specific version is under BAdI definition FI_CGI_DMEE_COUNTRIES -> Implementations ->
BAdI Implementation IDFI_CGI_DMEE_COUNTRIES_DK.
3. You need to create your own new implementation under BAdI Definition
FI_CGI_DMEE_COUNTRIES_CUST:

1. Select Enhancement Implementation

Preliminary version
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
 2. Fill in values with name of customer BAdI, description and implementing class:

3. Enter filter values:

Example Code for GET_VALUE method

• Double-click the GET_VALUE method:

• Create an implementation of the method and activate it.

Preliminary version
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
19
Please note that you need to clear the value that is coming from the delivered Implementation or Fallback Class,
otherwise it can happen that your logic decides not to fill this value, so the wrong value will be displayed.

1.5 Step 5: Post Customer/Vendor Invoices

As part of your daily or regular business activities, post customer/vendor invoices.

1.6 Step 6: Execute Payment Run and Generate Payment Medium File
You run transaction F110 (Automatic Payment Transactions) to process payment run as follows:
1. Run payment proposal (no posting is done)
2. Execute payment run (with posting)
3. Generate payment file using transaction FBPM (Payment Medium: Creation) – or with the selection
variant defined in OBPM4?

For more information about the payment format generation, read the report documentation in the system.

Preliminary version
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
2 Additional Information
1. Bank Communication Management
For information about the bank communication management and payment batch approval, see SAP Note
1577912. This SAP Note contains a list of frequently asked questions and their answers about the communication
process with banks using the SAP Bank Communication Management.

2. List of Supported Countries

The following countries have sample implementations for CGI with BAdI. Please keep in mind that not all bank-
specific requirements are supported for the listed countries and you may need to create your own customer BAdI
implementation to fulfill those requirements. SAP also can consider changes in provided country version after
communication with local contacts, if you want to be sure, that your changes are not touched after
implementation of the latest SAP Notes from 2253571 - Collective information note: CGI_XML_CT, CGI_XML_DD
extended with BAdI enhancement, please, keep your changes in customer BAdI implementation, because it has
higher priority.

Legend:

• Yes – means that country-specific implementation is needed

• No – means that no special implementation is needed

Country Class Name Credit Transfer Direct Debit

Australia CL_IDFI_CGI_DMEE_AU Yes No
Austria CL_IDFI_CGI_DMEE_AT Yes Yes
Belgium CL_IDFI_CGI_DMEE_BE Yes Yes
Bulgaria CL_IDFI_CGI_DMEE_BG Yes No
China CL_IDFI_CGI_DMEE_CN Yes No
Croatia CL_IDFI_CGI_DMEE_HR Yes No
Denmark CL_IDFI_CGI_DMEE_DK Yes No
Estonia CL_IDFI_CGI_DMEE_EE Yes No
Greece Consulting Note Only Yes No
Hong Kong CL_IDFI_CGI_DMEE_HK Yes No
Hungary Consulting Note Only Yes No
Italy CL_IDFI_CGI_DMEE_IT Yes Yes
Lichtenstein CL_IDFI_CGI_DMEE_CH Yes Yes
Lithuania CL_IDFI_CGI_DMEE_LT Yes No
Luxembourg CL_IDFI_CGI_DMEE_LU Yes Yes
Mexico CL_IDFI_CGI_DMEE_MK Yes No
Poland CL_IDFI_CGI_DMEE_PL Yes Yes
Portugal CL_IDFI_CGI_DMEE_PT Yes Yes
Spain CL_IDFI_CGI_DMEE_ES Yes Yes
Sweden CL_IDFI_CGI_DMEE_SE Yes Yes
Switzerland CL_IDFI_CGI_DMEE_CH Yes Yes
Taiwan CL_IDFI_CGI_DMEE_TW Yes Yes
United Kingdom CL_IDFI_CGI_DMEE_GB Yes Yes
United States CL_IDFI_CGI_DMEE_US Yes Yes
Preliminary version
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
21
Preliminary version
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
Typographic Conventions
Table 4

Example Description

<Example>
Angle brackets indicate that you replace these words or characters with appropriate entries to make
entries in the system, for example, “Enter your <User Name>”.

Arrows separating the parts of a navigation path, for example, menu options
Example Example

Example Emphasized words or expressions

Example
Words or characters that you enter in the system exactly as they appear in the documentation

Textual cross-references to an internet address

www.sap.com

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on
the
Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example
● Words or characters quoted from the screen. These include field labels, screen titles, pushbutton
labels, menu names, and menu options.

● Cross-references to other documentation or published works

Example
● Output on the screen following a user action, for example, messages
● Source code or syntax quoted directly from a program
● File and directory names and their paths, names of variables and parameters, and names of
installation, upgrade, and database tools

EXAMPLE
Technical names of system objects. These include report names, program names, transaction codes,
database table names, and key concepts of a programming language when they are surrounded by body
text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

Preliminary version
© Copyright 2017 SAP SE or an SAP affiliate company. All rights reserved.
23
www.sap.com

© 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. All other product and service names mentioned are the
trademarks of their respective companies. Please see
www.sap.com/corporate-en/legal/copyright/index.epx#trademark
for additional trademark information and notices.