cgi_xml_ct_img

© 2012 SAP AG Neurottstr. 16 D-69190 Walldorf

Title: Implementation Guide CGI_XML_CT

Version: 1.1

Date: 30.12.2011

of 59

XML (ISO 20022) Payment File for Credit Transfer Initiation

(pain.001.001.03)

Implementation Guideline for CGI_XML_CT

I. Overview of the new CGI_XML_CT Format................................................................................... 2

II. Implementation steps ......................................................................................................................... 2

III. Format Parameter Structure FPM_CGI: ......................................................................................... 5

IV. Enhance Structures FPAYP, FPAYH and FPAYHX ................................................................... 17

V. Apply Additional Notes .................................................................................................................... 18

VI. Create Function Group DMEE_CGI .............................................................................................. 19

VII. Create Function Modules and Exit Modules under Function Group DMEE_CGI .................. 20

VIII. Create XSLT Transformation CGI_XML_CT_XSLT to Eliminate Empty Tags ....................... 27

IX. Upload and activate the XML File .................................................................................................. 29

X. Maintain Customizing settings........................................................................................................ 32

a) Adjust customizing settings in Payment Medium Workbench (PMW) ............................. 32

b) Adjust customizing settings of instruction keys ................................................................... 37

c) Adjust customizing settings of Format Supplement for text ............................................... 41

d) Adjust customizing settings for Maintaining the Title .......................................................... 42

e) Adjust customizing settings for Language Dependent Address ....................................... 44

f) Adjust customizing settings for Language Dependent Address for Company Code ..... 45

g) Adjust customizing settings for Language Dependent Address for Vendor .................... 48

XI. Use of BICOrBEI element in the format ........................................................................................ 51

XII. Assign the format name in the BADI Implementation to get the correct XML file in UTF-8

format ................................................................................................................................................. 52

XIII. Steps to create a new node in the DMEE format (Optional) ..................................................... 56



Version: 1.1

Date: 30.12.2011

of 59

I. Overview of the new CGI_XML_CT Format

The CGI_ XML_CT format is used by SAP ERP Financials to generate XML payment files for outgoing international and domestic credit transfers. The format structure is based on the ISO 20022 payment initiation message (pain.001.001.03). The CGI_ XML_CT format corresponds to the Implementation template defined by banks and corporate customers through the Common Global Implementation (CGI) initiative, includes country specific information, and is fully Single Euro Payment Area (SEPA) compliant.

II. Implementation steps

You must execute the following activities to utilize CGI_ XML_CT:

Create the format parameter structure FPM_CGI for transmitting structured information

Enhance structures FPAYH, FPAYHX and FPAYP

o Enhance structure FPAYH with fields BSWIFT1, BSWIFT2, and BSWIFT3 (Swift International Payment)

o Enhance structure FPAYHX with the field DTURG (Urgent Payment)

o Enhance structure FPAYP with the field BSTRAS (Street and House Number)

Apply requisite additional Notes

Create Function Group DMEE_CGI

Create Function Module FI_PAYMEDIUM_DMEE_CGI_05 to:

o Use the address details of both the creditor and debtor

o Determine if the payment is SEPA

o Get the bank identification for the house bank

Create the exit module DMEE_EXIT_CGI_ XML to get the parameter values for the nodes ‘Id’,'BICOrBEI', and ‘Issr’ based on company code and party name

Create the exit module DMEE_EXIT_CGI_DEBT_NAME to get the language dependent debtor name



Version: 1.1

Date: 30.12.2011

of 59

Create the exit module DMEE_EXIT_CGI_CRED_NAME to get the language dependent creditor name

Create the exit module DMEE_EXIT_CGI_CRED_CITY to get the language dependent creditor city

Create the exit module DMEE_EXIT_CGI_CRED_PO_CITY to get the language dependent creditor PO city

Create the exit module DMEE_EXIT_CGI_CRED_REGION to get the language dependent creditor region

Create the exit module DMEE_EXIT_CGI_CRED_STREET to get the language dependent creditor street

Create the exit module DMEE_EXIT_CGI_EQVTAMT to get the amount in payment currency

Create the exit module DMEE_EXIT_CGI_CCYOFTRF to get the currency for automatic payment

Create the exit module DMEE_EXIT_CGI_CRED_TAXID to get the creditor Tax ID

Create the exit module DMEE_EXIT_CGI_TAXAMT_RATE to get the tax amount rate

Create the exit module DMEE_EXIT_CGI_TAXAMT_TTLAMT to get the total tax amount

Create the exit module DMEE_EXIT_CGI_TAXAMT_TXBASEAMT to get the taxable base amount

Create the exit module DMEE_EXIT_CGI_TAX_CATEGORY to get the tax category

Create the exit module DMEE_EXIT_CGI_TAX_CTGRY_DTLS to get the tax category details

Create the exit module DMEE_EXIT_CGI_TAX_FORMS_CODE to get the tax forms code

Create the exit module DMEE_EXIT_CGI_TAX_METHOD to get the tax method

Create the exit module DMEE_EXIT_CGI_TAX_SQNB to get the tax sequence number

Create the exit module DMEE_EXIT_CGI_TP_WHT to get the constant type value WHT

Create XSLT Transformation CGI_XML_CT_XSLT to eliminate empty tags

Upload and activate the XML file for the payment format with the DMEE transaction

Maintain Customizing settings:



Version: 1.1

Date: 30.12.2011

of 59

o Adjust the customizing settings in Payment Medium Workbench (PMW) for the use of the new payment method

o Adjust the customizing settings for the instruction keys

o Adjust the customizing settings for the format payment supplement

o Adjust the customizing settings for maintaining the text title

o Adjust the customizing settings for maintaining the Language Dependent Address

o Adjust the customizing settings for maintaining the Language Dependent Address in Company Code

o Adjust the customizing settings for maintaining the Language Dependent Address in Vendor master data

Select desired use of BICOrBEI element in the format

Specify the format name CGI_ XML_CT as a filter value in the BADI implementation DMEE_BADI_XML_01

Create a new node in the DMEE format (Optional)

Note: Ensure every object is saved in the package ID-DMEE.



Version: 1.1

Date: 30.12.2011

of 59

III. Format Parameter Structure FPM_CGI: The format parameter structure FPM_UI is used to specify additional information or choose additional

file structure formatting options.

With a certain transaction the user can create variants for the formatting options per House Banks per

payment method. Go to transaction SPRO and choose SAP Reference IMG In the IMG tree, choose

Financial Accounting > Accounts Receivable and Accounts Payable > Business Transactions > Outgoing

Payments > Automatic Outgoing Payments > Payment Media > Make settings for payment medium

formats for payment medium > Create/Assign Selection Variant

In CGI_XML_CT, structured remittance information can be transmitted within the file. The user selects

this option by populating the Structured Remittance Info checkbox as shown below.

The user can also choose to publish country specific information by specifying the appropriate two digit

ISO 3166-1 code of the required country in the ISO code parameter.

The Address Version parameter is used to support local language requirements for values such as

debtor name or creditor name. The user needs to specify the version of international address to

accomplish this. Detailed information for values are identified below under the customizing steps for

language dependent address.

The Requested Execution Date parameter is the date the initiating party requests the clearing agent to

process the payment.



Version: 1.1

Date: 30.12.2011

of 59

Steps to create the format parameter structure FPM_CGI:

1. Initiate transaction SE11

2. Enter the database table name as FPM_SEPA and click on the Copy button

If you have the structure FPM_SEPA in your system, proceed to step 3 – Copy structure FPM_SEPA

to FPM_CGI. If you do not have the structure FPM_SEPA, then seen the Note – Creating structure

FPM_SEPA below.

Note: Creating Structure FPM_SEPA

Steps to create the format parameter structure FPM_SEPA:

A) Create the following three data elements with the domain TEXT70 in SAP package

BFIBL_PAYM

FPM_XML_XMLNS (XML Namespace of Data Medium)

FPM_XML_XSI (XML Namespace of Schema)



Version: 1.1

Date: 30.12.2011

of 59

FPM_XML_SCHEMALOCATION (XML Location of Schema)

Save and activate the element in the package BFIBL_PAYM

B) Create Data Element FPM_STRD with the domain XFELD in SAP package BFIBL_PAYM as

shown below

In the ABAP Dictionary: Initial Screen, select Data type, enter the value FPM_STRD, and click on the

Create button:

The Create Type STRD box appears. Select Data element and click on the green checkmark as

shown below:



Version: 1.1

Date: 30.12.2011

of 59

The Dictionary: Display Data Element screen appears. Populate Short Description with the value

Structured Remittance Info. Select the Data Type tab and populate as shown below:

Select the Field Label tab and populate as shown below:



Version: 1.1

Date: 30.12.2011

of 59

Save and activate the element in the package BFIBL_PAYM.

C) Once you create all four data elements, then create the ABAP structure FPM_SEPA

(Payment medium: Parameters for SEPA formats) in the package BFIBL_PAYM with the

fields of the ABAP Dictionary: Initial Screen populated as shown below:



Version: 1.1

Date: 30.12.2011

of 59

D) Save and activate the above structure in the package BFIBL_PAYM.

3. Copy structure FPM_SEPA to FPM_CGI

As shown below, click on the Copy Structure button, ensure the value FPM_SEPA is in the

From Structure box and enter the value FPM_CGI in the To Structure Box. Click on the

green checkmark.



Version: 1.1

Date: 30.12.2011

of 59

4. Save the newly created FPM_CGI structure in the package ID-DMEE and activate it.

5. Add new field component INTCA to structure FPM_CGI. Go to transaction SE11.

Select Database table and enter the value FPM_CGI. Click on the Change button.

6. In the Dictionary: Change Structure screen, select the Components tab. In a blank

Components field, enter component INTCA. Populate the corresponding

Component Type, Data Type, Length, Decimal, and Short Description fields as

shown below:



Version: 1.1

Date: 30.12.2011

of 59

7. In the Components tab, add additional component NATION. Populate the

corresponding Component Type, Data Type, Length, Decimal, and Short

Description fields as shown below:

8. Create new data element DUEDATE_CGI. Go to transaction SE11. Select Database

table and enter DUEDATE_CGI. Click on the Create button as shown below:



Version: 1.1

Date: 30.12.2011

of 59

Select Data element and click on the green check mark:

In the Dictionary: Display Data Element screen, populate the Short Description field

with the value Requested Execution Date. Select the Data Type tab and populate

the Domain field with the value DATUM and its corresponding parameters as shown

below:



Version: 1.1

Date: 30.12.2011

of 59

Select the Field Label tab and populate the values as shown below:



Version: 1.1

Date: 30.12.2011

of 59

Save the changes and activate it in the package ID-DMEE.

9. In the Dictionary: Display Structure screen, select the Components tab. In a blank

Components field, enter the value DUEDATE_CGI. Populate the corresponding

Component Type, Data Type, Length, Decimal, and Short Description fields as

shown below:



Version: 1.1

Date: 30.12.2011

of 59

10. Save the changes in package ID-DMEE and activate the table.



Version: 1.1

Date: 30.12.2011

of 59

IV. Enhance Structures FPAYP, FPAYH and FPAYHX

It is necessary to enhance structures FPAYP, FPAYH and FPAYHX. To accomplish this, implement

Note 1625129 and Note 1637533 in your system.

Note 1625129 contains instructions for fields BSWIFT1, BSWIFT2 and BSWIFT3 for the FPAYH

structure.

Note 1637533 contains instructions for fields FPAYHX-DTURG and FPAYP-BSTRAS.



Version: 1.1

Date: 30.12.2011

of 59

V. Apply Additional Notes The following additional Notes must be applied as specified:

Note 1305012 – DMEE format for SEPA credit transfer – version EPC 3.2. There is no need to

upload the SEPA_CT format. However, the user must:

o Execute Note Steps One through Four

o Implement the code correction instruction

Note 1576634 – GET_BANKCODE – ExternalClearingSystemMemberIdentification

Note 1677298 – Field UBISO in the Structure FPAYHX. (Need to implement this note only for

releases 470 and 500)



Version: 1.1

Date: 30.12.2011

of 59

VI. Create Function Group DMEE_CGI

1. Go to transaction SE80. Specify the package as ID-DMEE and then right click on object name

ID-DMEE, select Create, then select Function Group as shown below:



Version: 1.1

Date: 30.12.2011

of 59

2. In Create Function Group, enter the value DMEE_CGI in the Function group field and the value Function Group for CGI Tree in the Short text field. Click on the Save button.

3. Save it in the package ID-DMEE.

VII. Create Function Modules and Exit Modules under Function

Group DMEE_CGI

a) Create Function Module FI_PAYMEDIUM_DMEE_CGI_05

1. Go to transaction SE37.

2. In the Function Builder: Initial Screen, enter the value FI_PAYMEDIUM_SAMPLE_05 in the Functional Module field and click on the Copy button.

3. In the Copy Functional Module box, enter the value FI_PAYMEDIUM_DMEE_CGI_05 in the To Function module field and the value DMEE_CGI in the Function group field and click on the Copy function.



Version: 1.1

Date: 30.12.2011

of 59

4. Save and activate the function module in the package ID-DMEE.

b) Create Function Module DMEE_EXIT_CGI_XML


2. In the Function Builder: Initial Screen, enter the value DMEE_EXIT_TEMPLATE_EXTEND_ABA (for releases 500 and above) or DMEE_EXIT_TEMPLATE_EXTENDED (for 470 release) in the Functional Module field and click on the Copy button.

3. In the Copy Functional Module box, enter the value DMEE_EXIT_CGI_XML in the To Function module field and the value DMEE_CGI in the Function group field and click on the Copy function.



Version: 1.1

Date: 30.12.2011

of 59

4. Save and activate the function module in the package ID-DMEE.

c) Create Function module DMEE_EXIT_CGI_DEBT_NAME


2. In the Function Builder: Initial Screen, enter the value DMEE_EXIT_TEMPLATE_EXTEND_ABA (for releases 500 and above) or DMEE_EXIT_TEMPLATE_EXTENDED (for 470 release) in the Functional Module field and click on the Copy button.

3. In the Copy Functional Module box, enter the value DMEE_EXIT_CGI_DEBT_NAME in the To Function module field and the value DMEE_CGI in the Function group field and click on the Copy function.



Version: 1.1

Date: 30.12.2011

of 59

4. Save and activate the function module in package ID-DMEE.

d) Create Function module DMEE_EXIT_CGI_CRED_NAME

Follow the steps for Create Function Module DMEE_EXIT_CGI_XML substituting the value

DMEE_EXIT_CGI_CRED_NAME for DMEE_EXIT_TEMPLATE_EXTEND_ABA (for releases 500

and above) or DMEE_EXIT_TEMPLATE_EXTENDED (for 470 release) in the Function Module

field in step 2.

e) Create Function module DMEE_EXIT_CGI_CRED_CITY


DMEE_EXIT_CGI_CRED_CITY for DMEE_EXIT_TEMPLATE_EXTEND_ABA (for releases 500


field in step 2.

f) Create Function module DMEE_EXIT_CGI_CRED_PO_CITY


DMEE_EXIT_CGI_CRED_PO_CITY for DMEE_EXIT_TEMPLATE_EXTEND_ABA (for releases

500 and above) or DMEE_EXIT_TEMPLATE_EXTENDED (for 470 release) in the Function

Module field in step 2.

g) Create Function module DMEE_EXIT_CGI_CRED_REGION


DMEE_EXIT_CGI_CRED_REGION for DMEE_EXIT_TEMPLATE_EXTEND_ABA (for releases



h) Create Function module DMEE_EXIT_CGI_CRED_STREET


DMEE_EXIT_CGI_CRED_STREET for DMEE_EXIT_TEMPLATE_EXTEND_ABA (for releases





Version: 1.1

Date: 30.12.2011

of 59

i) Create Function module DMEE_EXIT_CGI_EQVTAMT


DMEE_EXIT_CGI_EQVTAMT for DMEE_EXIT_TEMPLATE_EXTEND_ABA (for releases 500


field in step 2.

j) Create Function module DMEE_EXIT_CGI_CCYOFTRF


DMEE_EXIT_CGI_CCYOFTRF for DMEE_EXIT_TEMPLATE_EXTEND_ABA (for releases 500


field in step 2.

k) Create Function module DMEE_EXIT_CGI_CRED_TAXID


DMEE_EXIT_CGI_CRED_TAXID for DMEE_EXIT_TEMPLATE_EXTEND_ABA (for releases 500


field in step 2.

l) Create Function module DMEE_EXIT_CGI_TP_WHT


DMEE_EXIT_CGI_TP_WHT for DMEE_EXIT_TEMPLATE_EXTEND_ABA (for releases 500 and

above) or DMEE_EXIT_TEMPLATE_EXTENDED (for 470 release) in the Function Module field

in step 2.

m) Create Function module DMEE_EXIT_CGI_TAX_METHOD


DMEE_EXIT_CGI_TAX_METHOD for DMEE_EXIT_TEMPLATE_EXTEND_ABA (for releases 500


field in step 2.

n) Create Function module DMEE_EXIT_CGI_TAX_SQNB


DMEE_EXIT_CGI_TAX_SQNB for DMEE_EXIT_TEMPLATE_EXTEND_ABA (for releases 500



Version: 1.1

Date: 30.12.2011

of 59


field in step 2.

o) Create Function module DMEE_EXIT_CGI_TAX_FORMS_CODE


DMEE_EXIT_CGI_TAX_FORMS_CODE for DMEE_EXIT_TEMPLATE_EXTEND_ABA (for

releases 500 and above) or DMEE_EXIT_TEMPLATE_EXTENDED (for 470 release) in the

Function Module field in step 2.

p) Create Function module DMEE_EXIT_CGI_TAX_ CTGRY_DTLS


DMEE_EXIT_CGI_TAX_ CTGRY_DTLS for DMEE_EXIT_TEMPLATE_EXTEND_ABA (for releases



q) Create Function module DMEE_EXIT_CGI_TAX_ CATEGORY


DMEE_EXIT_CGI_TAX_ CATEGORY for DMEE_EXIT_TEMPLATE_EXTEND_ABA (for releases



r) Create Function module DMEE_EXIT_CGI_ TAXAMT_RATE


DMEE_EXIT_CGI_ TAXAMT_RATE for DMEE_EXIT_TEMPLATE_EXTEND_ABA (for releases



s) Create Function module DMEE_EXIT_CGI_TAXAMT_TTLAMT


DMEE_EXIT_CGI_TAXAMT_TTLAMT for DMEE_EXIT_TEMPLATE_EXTEND_ABA (for releases



t) Create Function module DMEE_EXIT_CGI_TAXAMT_ TXBASEAMT



Version: 1.1

Date: 30.12.2011

of 59


DMEE_EXIT_CGI_TAXAMT_ TXBASEAMT for DMEE_EXIT_TEMPLATE_EXTEND_ABA (for

releases 500 and above) or DMEE_EXIT_TEMPLATE_EXTENDED (for 470 release) in the

Function Module field in step 2.

Note: The code for the aforementioned function and exit modules will come from the correction instructions of the note. But for now, the code for the above functional module and exit module is provided in the document. After performing all the above manual steps for creating the function and exit modules, put the code in the tab Source for the respective Function Modules from the given document.



Version: 1.1

Date: 30.12.2011

of 59

VIII. Create XSLT Transformation CGI_XML_CT_XSLT to Eliminate

Empty Tags 1) Go to Transaction SE80. Specify the package as ID-DMEE. Specify the package as ID-DMEE and

then click on Object Name ID-DMEE, right click on Transformations, and select Create as shown

below:

2) In Create Transformation, enter the value CGI_XML_CT_XSLT in the Transformation field, the

value XSLT transformation for elimination of self-contained tags in the Short Description field,

and select the value XSLT Program as the Transformation Type. Click on the Save button.



Version: 1.1

Date: 30.12.2011

of 59

3) Save it in the package ID-DMEE.

4) Open transformation CGI_XML_CT_XSLT and enter the source code as mentioned in the

attachment of the note.

5) Save and activate the transformation.



Version: 1.1

Date: 30.12.2011

of 59

IX. Upload and activate the XML File

1. Call transaction DMEE.

2. Enter the value PAYM in the Tree type field.

3. Enter the value CGI_XML_CT in the Format tree field.

4. Click on Format tree on the menu bar and select Upload XML file from the pull down menu as

shown below:



Version: 1.1

Date: 30.12.2011

of 59

5. In the XML file name field, specify the path where you saved the file and click on the Copy button.

6. Ignore the warning message (in yellow) and click on the Enter button. The system will display the new version in edit mode.

7. Select node RmtInf-> Ustrd and confirm the Atom handling field is set to the value Ø1.



Version: 1.1

Date: 30.12.2011

of 59

8. Save and activate the format.



Version: 1.1

Date: 30.12.2011

of 59

X. Maintain Customizing settings

a) Adjust customizing settings in Payment Medium Workbench (PMW)

1. Create Payment Medium Format in Transaction OBPM1 A) Go to transaction OBPM1 B) Click on New Entries button. C) Enter the value CGI_XML_CT in the Format field, and populate the other fields as

shown below:

D) In the Dialogue Structure tree, click on Event Modules for Payment Formats E) Attach function module FI_PAYMEDIUM_DMEE_CGI_05 to the format. To do this click

on New Entries in the menu bar and select Event 05 as shown below



Version: 1.1

Date: 30.12.2011

of 59

F) In the Dialogue Structure tree, click on Text Fields for Reference information and make any necessary changes to the number and length of text fields as shown below:



Version: 1.1

Date: 30.12.2011

of 59

2. Define New Country Payment Method – Transaction FBZP The following steps are necessary to define a new payment method for a country such as Thailand (for example Payment method 'T')

A) Fill in appropriate fields for your particular circumstances as shown in the example for

Payment Method T in Thailand as shown below:



Version: 1.1

Date: 30.12.2011

of 59

B) For Payment Medium, select Use payment medium workbench and populate the Format field with the value CGI_XML_CT as shown below:

C) In the New Entries: Overview of Added Entries screen, assign the Note to Payee to the format in transaction FBZP.

Note:

Before specifying the Note to Payee in the above dialog box, you need to create the Note to Payee structure in transaction OBPM2 per your business requirement.

For e.g.: Maintain the note to payee setting in the transaction OBPM2 as below. You can modify the below mentioned values also as per your business requirement. For this, complete the following steps:

i. go to transaction OBPM2

ii. Click on New entries and populate the fields as shown below:



Version: 1.1

Date: 30.12.2011

of 59

iii. In the Dialog Structure box, click on Note to payee, click on Default Note to Payee, click on New entries, and populate as shown below:

iv. Save the changes and assign the Note to Payee to the format in transaction FBZP.



Version: 1.1

Date: 30.12.2011

of 59

3. Assign Payment Method and Country to Company Code - transaction FBZP

Assign new country payment method and country specific information to the company code of your

choice.

b) Adjust customizing settings of instruction keys

1. Define instructions for payment transactions:

A) Go to transaction SPRO and select SAP Reference IMG B) In the IMG tree, choose Financial Accounting > Accounts Receivable and Accounts

Payable > Business Transactions > Outgoing Payments > Automatic Outgoing Payments > Payment Media > Data Medium Exchange > Define Instructions for Payment Transactions

C) The country specification is needed to distinguish between local requirements. Specify the App. Area and Short Name as appropriate (i.e. TH and Thailand) and select the corresponding Country checkbox as shown below:



Version: 1.1

Date: 30.12.2011

of 59

D) In the Dialog Structure box of the Change View “Permitted instruction fields”: Overview screen, click on Permitted instructions in the dialog structure and populate the field box with the value 1 as shown below:

E) In the Change View “Instructions in Payment Transactions”: Overview screen maintain the instructions as shown below:



Version: 1.1

Date: 30.12.2011

of 59

F) In the Change View “Instruction Keys”: Details screen, do the following:

To specify the charge bearer, use the Cost allocation key

To maintain Instruct. Key 1, Choose the key value from F4 help

Tick the Urgent box only if it is an urgent payment, otherwise leave it blank. G) Save the changes.



Version: 1.1

Date: 30.12.2011

of 59

Note: The following screen shows a proposal setting populated for Thailand.

Maintain Payment type as 1, if it is urgent payment. Maintain Instruct. Key1 through F4 help, as per your business requirement. The cost allocation key is used with the following values in Thailand for foreign bank transfers via DME:

All charges payable by payer -> DEBT (if cost allocation key is set to 1)

All charges payable by payee -> CRED (if cost allocation key is set to 2)

If no allocation key is defined then payer and payee pay their own charges -> SHAR For the use of SEPA payments the code is automatically set as -> SLEV



Version: 1.1

Date: 30.12.2011

of 59

c) Adjust customizing settings of Format Supplement for text

1. Go to transaction SM30

2. In the Maintain Table Views: Initial Screen, enter the value V_TFPM042FZ in the

Table/View field and click on the Maintain button as shown below:



Version: 1.1

Date: 30.12.2011

of 59

3. In the Determine Work Area: Entry box, select CGI_XML_CT in the Pmnt medium

format field and click on the green checkmark.

4. In the Change View “Format supplement with text”: Overview, in the Format Suppmt

box, maintain the Format supplement name as shown below:

5. Save the changes.

d) Adjust customizing settings for Maintaining the Title

1. Maintain the Title or Forms of Address

A) Go to transaction SPRO and select SAP Reference IMG B) In the IMG tree, choose Financial Supply Chain Management> Treasury and Risk

Management> Basic Functions> SAP Business Partner for Financial Services> General Settings> Business Partner> Basic Settings> Forms of Address> Maintain Forms of Address

C) Click on New Entries in the menu bar. D) Maintain Title as shown below:



Version: 1.1

Date: 30.12.2011

of 59

E) Save the changes.



Version: 1.1

Date: 30.12.2011

of 59

e) Adjust customizing settings for Language Dependent Address

1. Go to transaction SPRO 2. Select SAP Reference IMG 3. In the IMG Tree, Choose SAP Net weaver-> Base-> Basis Services-> Address Management->

International Settings-> Activate International Address Versions. Alternatively, you can maintain it in the view V_TSADV.

4. In the Change View “International address versions”: Overview, activate the language in which you need to maintain the address by checking the appropriate active box as shown below for the Thai language:



Version: 1.1

Date: 30.12.2011

of 59

f) Adjust customizing settings for Language Dependent Address for Company

Code

1) Go to transaction SPRO 2) Select SAP Reference IMG 3) In the IMG Tree, Choose Financial Accounting ->Financial Accounting Global Settings ->

Global Parameters for Company Code ->Enter Global Parameters. 4) In the Change View “Company Code Global Data”: Details, select your Company code

and click on the Address button as shown below:



Version: 1.1

Date: 30.12.2011

of 59

5) In the Edit address: box, click on the International Version button as shown below:



Version: 1.1

Date: 30.12.2011

of 59

6) In the Edit address: box, you can maintain the international version as appropriate. For example, shown below is an example of maintaining the communication language in Thai (For this you need to activate the version in view V_TSADV as described above).



Version: 1.1

Date: 30.12.2011

of 59

7) When finished, click on the green checkmark to save the changes.

g) Adjust customizing settings for Language Dependent Address for Vendor

1) G to either transaction FK01 Create Vendor Master or transaction FK02 Change Vendor Master.

2) Click on the button Internat. Versions as shown in the Change Vendor: Address screen below:



Version: 1.1

Date: 30.12.2011

of 59

3) Choose the desired International address version. These address versions come by activating the version in the view V_TSADV as described above.

4) Click on the green checkmark to enter as shown below:

5) In the Address maintenance: Maintain Version “<Language>” (where the value <Language> is the international version selected in the previous step) you can maintain the address for the <language> value. For example, shown below is an example of maintaining the address for the <language> value of THAI.



Version: 1.1

Date: 30.12.2011

of 59

6) When finished, click on the green checkmark to save the changes.



Version: 1.1

Date: 30.12.2011

of 59

XI. Use of BICOrBEI element in the format The Specification of the Customer to Bank payment initiation version 4 from EPC legal dated 01.11.2010

has introduced the tag BICOrBEI. To be able to use this Element with the SAP delivered DMEE Format,

additional customizing steps are necessary. In the IMG under Maintenance of Additional Data for

Company Codes, you may assign the appropriate value to the field CGI Initiat. Prty. Ident. Which is used

for the given identification from SWIFT, and the appropriate value to the field CGI Initiat. Prty. Issuer

used to identify the institution that gives you the identification id.

For example, if you get a BIC ID from SWIFT, the fields will look as follows:

CGI Initiat. Prty. Ident. : <Valid BIC ID>

CGI Initiat. Prty. Issuer : SWIFT

If you get a BEI from another institution, the fields will look as follows:

CGI Initiat. Prty. Ident. : <Valid Institution ID>

CGI Initiat. Prty. Issuer : <Name of the Institution which assigned the ID>

To be able to maintain these customizing elements, Table T001Z with additional fields CGIID and CGIIR

should be enhanced, and the fields assigned to the particular country for which you want to use them.

Additional Information about the structure of BIC and BEI from swift as follows:

BIC

A code that is used in automated processing. This code unambiguously identifies a financial institution, or non-financial institution. The ISO 9362 standard specifies the elements and the structure of a BIC. A BIC consists of either eight (BIC8) or eleven (BIC11) contiguous characters. These characters comprise either the first three, or all four, of the following components: institution code, country code, location code, and branch code. The International Organization for Standardization has designated SWIFT as the BIC registration authority.

Business Entity Identifier

Abbreviated: BEI

The scope of the ISO Standard 9362 has been extended to enable the identification of financial and non-financial institutions with a BIC. Before this extension, SWIFT has allocated BEIs to non-financial institutions. Such identification enables to facilitate the processing of telecommunication messages. The BEI consists of 8 or 11 contiguous characters, and has the same structure as a BIC.

https://www2.swift.com/uhbonline/books/public/en_uk/udic/b5.htm#leme50









Version: 1.1

Date: 30.12.2011

of 59

Steps to maintain the values CGIID and CGIIR:

1) Goto transaction SM30 and put the view name as V_T001I and press 'maintain'.

2) Then push 'new entries' and now you can maintain the values here:

Maintain two rows, one for Par. type as CGIID and another for Par. Type as CGIIR.

Maintain description as per your need and maintain length as 5. ISO code should be your ISO country

code. For e.g.:

Par. Type Description Length ISO Code

CGIID CGI Identification 5 DE

CGIIR CGI Issuer Identification 5 DE

3) After that go to transaction OBY6 and select your company code that is linked with the above defined

ISO country code.

Open the details of your company code.

Go to push button 'Additional Data' of your company code.

Now you will get the above defined description as Name and here you need to maintain the parameter

value what you need as per your business requirement. For e.g.:

Name Parameter value

CGI Identification CGIID (according to your requirement)

CGI Issuer Identification CGIIR (according to your requirement)

Now goto transaction SE16 and execute it for your company code.

Here you will be able to get the PARTY and PAVAL, which you have defined for your company code.

XII. Assign the format name in the BADI Implementation to get

the correct XML file in UTF-8 format

If you want to download the XML DME file to your local machine and open it in the UTF-8 format, you need to proceed as follows:



Version: 1.1

Date: 30.12.2011

of 59

1. Go to transaction OBPM3 2. Maintain the code page 4110 for the format CGI_XML_CT as shown below:

3. Maintain this tree in the BADI implementation DMEE_XML_BADI_01 so that above codepage will be filled and the DME file shall be created in 4110 (Unicode UTF-8 format)

4. Go to transaction SE19. 5. In the BAdI Builder: Initial Screen for Implementations, select Classic BAdI and enter the value

DMEE_XML_BADI_01 in the Implementation field as shown below:



Version: 1.1

Date: 30.12.2011

of 59

6. Click on the Change button. 7. In the Business Add-In Builder: Display Implementation DMEE_XML_BADI_01 screen, assign

the format tree name CGI_XML_CT as a filter value of the implementation DMEE_XML_BADI_01 as shown below:



Version: 1.1

Date: 30.12.2011

of 59

8. Save the changes and activate the implementation.



Version: 1.1

Date: 30.12.2011

of 59

XIII. Steps to create a new node in the DMEE format (Optional) You should always avoid making any changes to the standard format. If you want to add a new field in the DMEE format to meet your specific business requirements, then create a Z* variant as follows: as shown below:

1. Go to transaction DMEE 2. In the DME Engine: Initial Screen, specify the standard Tree type and Format tree and click on

the Copy button as shown below:

3. In the DMEE: Copy Format Tree box, enter the value ZCGI_XML_CT (or any other name starting with Z), as shown below:



Version: 1.1

Date: 30.12.2011

of 59

4. In the DME Engine: Initial Screen, enter the name of your Z* version in the Format tree field and click on the Change button as shown below:



Version: 1.1

Date: 30.12.2011

of 59

5. Create a new element as shown below by:

A) Select the desired node – for example: ‘NbOfTxs’ B) Right Click on the selected node C) Select Create Element -> Same level or As Subnode depending on your requirement.



Version: 1.1

Date: 30.12.2011

of 59

D) Choose Enter E) A <New element> appears in the DMEE format tree as shown below:

F) In the Name field in the Attributes tab, specify the desired element Name, Short descript., Mapping procedure and all required entries in all of the Tabs.

G) Save the changes and activate the new DMEE format.

cgi_xml_ct_img

Documents

ct format

xml iso

new cgi

format structure

implementation guide

xml payment files

correct xml file

ct version