This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
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
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
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.
4. Save and activate the function module in the package ID-DMEE.
b) Create Function Module DMEE_EXIT_CGI_XML
1. Go to transaction SE37.
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.
4. Save and activate the function module in the package ID-DMEE.
c) Create Function module DMEE_EXIT_CGI_DEBT_NAME
1. Go to transaction SE37.
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.
Follow the steps for Create Function Module DMEE_EXIT_CGI_XML substituting the value
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.
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
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:
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
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:
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:
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:
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
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:
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:
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).
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.
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.
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:
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:
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.
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.