Professional Documents
Culture Documents
(pain.001.001.03)
Implementation Guideline for CGI_XML_CT
I.
II.
Implementation steps......................................................................................................................... 2
b)
c)
d)
e)
f)
Adjust customizing settings for Language Dependent Address for Company Code ..... 45
g)
Adjust customizing settings for Language Dependent Address for Vendor .................... 48
Page 1 of 59
I.
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 structure FPAYH with fields BSWIFT1, BSWIFT2, and BSWIFT3 (Swift
International Payment)
Enhance structure FPAYP with the field BSTRAS (Street and House Number)
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
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 2 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_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_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_SQNB to get the tax sequence number
Create the exit module DMEE_EXIT_CGI_TP_WHT to get the constant type value WHT
Upload and activate the XML file for the payment format with the DMEE transaction
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 3 of 59
Adjust the customizing settings in Payment Medium Workbench (PMW) for the use of
the new payment method
Adjust the customizing settings for maintaining the Language Dependent Address
Adjust the customizing settings for maintaining the Language Dependent Address in
Company Code
Adjust the customizing settings for maintaining the Language Dependent Address in
Vendor master data
Specify the format name CGI_ XML_CT as a filter value in the BADI implementation
DMEE_BADI_XML_01
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 4 of 59
III.
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.
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 5 of 59
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
FPM_XML_XSI
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 6 of 59
FPM_XML_SCHEMALOCATION
The Create Type STRD box appears. Select Data element and click on the green checkmark as
shown below:
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 7 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:
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 8 of 59
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 9 of 59
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 10 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:
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 11 of 59
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 12 of 59
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:
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 13 of 59
Select the Field Label tab and populate the values as shown below:
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 14 of 59
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 15 of 59
10. Save the changes in package ID-DMEE and activate the table.
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 16 of 59
IV.
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.
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 17 of 59
V.
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)
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 18 of 59
VI.
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 19 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.
VII.
Page 20 of 59
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.
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 21 of 59
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 22 of 59
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 23 of 59
Page 24 of 59
Page 25 of 59
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.
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 26 of 59
VIII.
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.
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 27 of 59
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 28 of 59
IX.
4. Click on Format tree on the menu bar and select Upload XML file from the pull down menu as
shown below:
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 29 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.
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 30 of 59
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 31 of 59
X.
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
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 32 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:
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 33 of 59
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 34 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.
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 35 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.
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 36 of 59
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 37 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:
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 38 of 59
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 39 of 59
Note: The following screen shows a proposal setting populated for Thailand.
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
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 40 of 59
c)
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 41 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:
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 42 of 59
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 43 of 59
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 44 of 59
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 45 of 59
5) In the Edit address: box, click on the International Version button as shown below:
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 46 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).
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 47 of 59
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 48 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:
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 49 of 59
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 50 of 59
XI.
https://www2.swift.com/uhbonline/books/public/en_uk/udic/b5.htm#leme50
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 51 of 59
Description
Length
ISO Code
CGIID
CGI Identification
DE
CGIIR
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
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.
Page 52 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:
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 53 of 59
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 54 of 59
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 55 of 59
XIII.
3. In the DMEE: Copy Format Tree box, enter the value ZCGI_XML_CT (or any other name starting
with Z), as shown below:
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 56 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:
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 57 of 59
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 58 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.
2012 SAP AG
Neurottstr. 16
D-69190 Walldorf
Page 59 of 59