Meanwhile, it does!
Take a look at the attachment doc!
Greetings, Andreas
Take a look at the attachment doc!
Greetings, Andreas
Reply: 54
Auto translated
Coding SEPA CT XML file
Hello, all,
after the necessary preparatory work in the context of the conversion to SEPA, I have generated some test data. The payment run and the generation of the XML file in SAP work. There are problems with the import into SFirm. I get the message: Allowed encodings are UTF-8 and ISO-8859 not 'iso-8859-1'!
All my attempts to change the encoding have failed so far. I get the same message when I change the character set in the DMEE. Also calling the XML file with the editor and then saving it with encoding UTF-8 leads to the same result. Where do I have to make the setting?
2nd question: After the message that the namespace pain.001.001.02 is wrong, I have uploaded the current version of SAP and thus changed the namespace to pain.001.001.03. But the required namespace is pain.001.002.03. Is there a more recent version of SAP (I didn't find anything), or is this a technical setting?
I hope you have a solution.
AS123
after the necessary preparatory work in the context of the conversion to SEPA, I have generated some test data. The payment run and the generation of the XML file in SAP work. There are problems with the import into SFirm. I get the message: Allowed encodings are UTF-8 and ISO-8859 not 'iso-8859-1'!
All my attempts to change the encoding have failed so far. I get the same message when I change the character set in the DMEE. Also calling the XML file with the editor and then saving it with encoding UTF-8 leads to the same result. Where do I have to make the setting?
2nd question: After the message that the namespace pain.001.001.02 is wrong, I have uploaded the current version of SAP and thus changed the namespace to pain.001.001.03. But the required namespace is pain.001.002.03. Is there a more recent version of SAP (I didn't find anything), or is this a technical setting?
I hope you have a solution.
AS123
CommercialTRUST.EXCELLENCE.PEOPLEErfahren und agil. Nicht auf dem Sprung, sondern verlässlich an Ihrer Seite.!!
You must be logged in to post a reply.
54 Answers
- Push !
Have exactly the same problem !
- Mh, unfortunately still not
Allowed encodings are UTF-8 and ISO-8859 not 'iso-8859-1'!
'C:\test.xml' contains an XML document which does not comply with the schema definition (2.5 current as of 01.11.2010)!
Line 1/268 : Unknown element 'pain.001.001.02'.
Line 3/567 : Element 'pain.001.001.02' is invalid in content model: '(CstmrCdtTrfInitn,)'
This bothers me line 1/268 : Unknown element 'pain.001.001.02':
Is the error in the DMEE tree rather than in the format adjustments?Last edited 07/30/12 15:20
- Hello,
on the Internet you can compare the format on http://www.ebics.de/index.php?id=77.
Unknown element 'pain.001.001.02' rather indicates an error in the DMEE tree.
In the attachment I have attached the download for pain.002.03 from the DMEE (actually .txt format).
In the preview of the DME administration (transaction F110) I have , after the download I have encoding="iso-8859-1". Who can help here?
Greetings
Hubert - I have fixed my DMEE error with note 1540040.
Get now also the message by the XML Checker , that it is correct SEPA XML document version 2.5 from 01.11.10.
The wrong coding message remains however. Possibly it is also rather a warning message, which can be ignored.
EDIT: Just sent as a test file to our house bank. Accepted without any problems. So as thought warning message.Last edited on 31.07.12 15:42
- Hello,
is there a sure way to fix the encoding error. As soon as the file is read from SAP, the encoding changes from UTF-8 to ISO-8859-1. - Hello
there is also a BADI DMEE_XML_BADI_01 which has to be adapted if necessary
Please also think about codepage entry 4110 if Unicode is in use
With kind regards
Jens Plucinski
www.jensplucinski.de
Consultant Business Economist SAP FI - Thank you very much. Unfortunately, the code page entry did not have any effect. In the system UTF-8 is displayed in the file. As soon as the download is done, the encoding is in ISO 8859-1.
- Hello,
please also implement the BADI that Jens described. Without it it does not work. I know that from my own experience.
We had the same problem. Only the implementation of our DME tree in the Badi brought the desired result.
Good luck.
Eva Weßbecher-Merkel
SAP-FI department supervisor
and accountant - Hello Redfox,
many ways lead to Rome. Maybe you should specify in advance on which way you download the XML file.
That is...
FDTA --> Select data carrier
If you use the export or download function, you will get the following line
If you open the data carrier via the glasses in the screen Data carrier attributes, you will get
Maybe this helps? ;)
Best regards
C. Schweitzer C.Schweitzer:
Hello Redfox,
many ways lead to Rome. Perhaps you should specify in advance, on which way you download the XML file.
That is...
FDTA --> Select data carrier
If you use the export or download function, you will get the line
If you open the data carrier via the glasses in the screen Data carrier attributes, you will get
Maybe this helps?! ;)
Best regards
C. Schweitzer
We had already solved this problem, but since applying the new patches (SAP_APPL 14) it is acute again.
Since we use FDTA by default, we are looking for the solution. Does anyone know the redeeming clue???
Thanks in advance for your effort.
Many greetings
Eva Weßbecher-Merkel
SAP-FI department supervisor
and accountant- Hello,
in Tcode OBPM3 pay attention to the correct codepage - 4110 UTF-8 (see screenshot).
Greetings, consultant - Hello consultant,
We have already checked all this, but that is not the problem. It is encoded correctly, only when downloading via FDTA it is encoded back again. The display of the file via glasses says it is a UTF-8 encoded XML file. Also the parameter DCP is set (4110).
Greetings
Eva Weßbecher-Merkel
SAP-FI department administrator
and accountant - Hello Ms. Weßbecher-Merkel,
all notes concerning UTF-8, UTF-16, code page and BAdI implementation DMEE_XML_BADI_01 can be found in the collective note
Note 1688643 - Composite Note: Exit for XML Files DMEE_BADI_01
Maybe one of the notes mentioned there will help.
Best regards
EC1055 - Hello,
I think the error can be found in these notes. I had the same problem with a customer and addressed the problem to their base. I assume that the problem was then solved base side, since I have not heard anything more from the department.
Greetings, consultant - Thank you very much for the helpful support. It looks like the note 1853156 might solve the problem.
I will contact our base and report the result.
Thanks again for your help.
Many greetings
Eva Weßbecher-Merkel
SAP-FI department manager
and accountant - Hello All,
I too am getting the following warnings with my XMl checker of the S_DD (payment file) file:
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.008.002.02" xmlns:xsi="<a href="http://www.w3.org/2001/XMLSchema-instance"" target="_blank">http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:iso:std:iso:20022:tech:xsd:pain.008.002.02 pain.008.002.02.xsd">
Error message:
fatal error Unexpected element "pain.008.001.01" from namespace "urn:iso:std:iso:20022:tech:xsd:pain.008.002.02".
error Mandatory element "CstmrDrctDbtInitn" is missing.
Can someone please help me?
The code page entry is at 4110.
VG
Ilyas - Hi Ilyas,
if the top level in the format tree SEPA_DD is not CstmrDrctDbtInitn but pain.008.001.01, I suspect that the current format trees from note 1540040 have not been uploaded.
Many greetings
EC1055 EC1055:
Hello Ilyas,
if the top level in the format tree SEPA_DD is not CstmrDrctDbtInitn but pain.008.001.01, I suspect that the current format trees from note 1540040 have not been uploaded.
Regards
EC1055
Hello,
we have uploaded the tree from hint 1540040 and there the pain is called 008.001.01. If we now enter the specific parameters, the header contains 0008.002.02 with schema location etc., but the format tree itself contains the identifier 008.001.01. We then changed the identifier in the file to 008.002.02 during the upload, but this resulted in the xml-checker rejecting the file with the note "unkwon document". Unfortunately we did not get further, because the coding problem is not solved either, despite the hints 1852698, 1853156.
Eva Weßbecher-Merkel
SAP-FI department administrator
and accountant- Hello Ms. Weßbecher-Merkel,
I mean neither the short description nor the parameters but the very first element in the format tree SEPA_DD "Direct Debit Initiation" CstmrDrctDbtInitn, which also ends up as XML tag in the direct debit file. This is just before the "GroupHeader" ().
Sunny greetings
EC1055Last edited 07/18/13 15:01
- Hello EC1055.
There we are in agreement, I mean also.
I have attached the screenshot, uploaded from the note 1540040.
Sunny greetings
Eva Weßbecher-Merkel
SAP-FI department manager
and accountant - Hello Ms. Weßbecher-Merkel,
parallel to your post I had added a screenshot to my last post. What irritates me now: The elements are indeed called differently in your case.
But if you look at the file DMEE_TREE_SEPA_DDV40.xml from the ZIP attachment of the HW 1540040, you see that the very first after the 3 XML attributes is like this:
CstmrDrctDbtInitn
So where does the pain.008.001.01 come from in your case?
Many greetings
EC1055 - Hello EC1055,
I would like to know that too.
I will have another close look at the file from the uploaded note. This indication from you is completely missing, hence surely the error message of the unknown document. All a bit mysterious.
I hope that I will soon be finished with my planning, then I can devote myself again to the SEPA introduction.
Thank you very much for your help and have a sunny afternoon.
Kind regards
Eva Weßbecher-Merkel
EC1055:
Hello Ms. Weßbecher-Merkel,
parallel to your post I had added a screenshot to my last post. What irritates me now: The elements are indeed called differently in your case.
But if you look at the file DMEE_TREE_SEPA_DDV40.xml from the ZIP attachment of the HW 1540040, you see that the very first after the 3 XML attributes is like this:
CstmrDrctDbtInitn
So where does the pain.008.001.01 come from in your case?
Best regards
EC1055
Eva Weßbecher-Merkel
SAP-FI Department Manager
and Accountant - Hello Forum,
Hello EC1055,
it is done!!! Have deleted all format trees present in the system (except the current one), then uploaded from HW1540040 the current version of DD40. Made adjustments, set format parameters, created test file.
XML-checker = ok. Now the correct string is also above the Group Header.
Who says. However, it is more than mysterious to me how the wrong tree got into the system. The depths of electronic data processing.....
At this point I would like to thank all the helpers who gave me good and correct advice.
Have a sunny day
Eva Weßbecher-Merkel
SAP-FI department supervisor
and accountant - Very nice!
Sunny greetings and have a nice weekend in advance!
EC1055 - Hello all,
I just updated the PAIN as well and see "CstmrDrctDbtInitn" instead of "pain.008.001.01" as before.
What is correct here now?
And how / where can I check the XML?
Thanks a lot! - Hello Marco,
the version with the "CstmrDrctDbtInitn" is the correct one.
You can check the XML file with the XML checker of S-firm or similar. Banking software.
Good luck.
Sunny greetings
Eva Weßbecher-Merkel
SAP-FI department administrator
and accountant - Thanks a lot!!
Has jmd by chance a small HowTo what current must be carried out if one wants to copy the format tree into a Z namespace!
SEPA_CT to ZSEPA_CT / analogous to SEPA_DD Marco.K:
Thanks a lot!!
Does jmd by chance have a small HowTo what current must be carried out if one wants to copy the format tree into a Z namespace!
SEPA_CT to ZSEPA_CT / analogous to SEPA_DD
Hello Marco,
this is relatively simple. Save the format tree from note 1540040 locally. Edit the XML file with the XML editor. Enter the Z name (overwrite SEPA_DD), save. Upload the tree with the DMEE, make any adjustments and activate. That's it. Delete the existing tree (with the wrong labels) before.
Good luck.
Kind regards
Eva Weßbecher-Merkel
SAP-FI department administrator
and accountant- Hello Marco,
I cannot add anything to the remarks of Mrs. Weßbecher-Merkel. Except perhaps: Instead of an XML editor, the Windows editor (notepad.exe) is also sufficient in an emergency.
Best regards
EC1055 - Great, worked fine :-)
In the payment run I now get the error "Format tree SEPA_DD for tree type PAYM does not exist".
Which setting have I overlooked here? - Hello Marco,
I'm guessing payment medium format in the payment path? Is the Z-tree in here?
Many greetings
EC1055 - Hello EC1055,
uh no
Ergo, I have to copy the existing payment medium format SEPA_CT & SEPA_DD to ZSEPA_CT / ZSEPA_DD via OBPM1 and store the Z-format tree here!? (do I have to consider something here?)
Subsequently, in the payment method (which I already have) in the PMW store the payment medium format Z_SEPA_XX.
Greetings
Marco - Hello Marco,
yes, copy(s) in the OBPM1. You just have to keep in mind that you copy the dependent entries as well.
Then enter the ZTF in the payment method.
Of course you should not forget the payment medium selection variants (OBPM4).
Many greetings
EC1055 - Hello,
I have implented all the notes mentioned here, as far as they were relevant.
If then the DMEE standard SEPA_CT is supplied with from the latest version SAP Note 1540040, the output works with UTF-8.
If one copies an own format tree e.g. ZSEPA_CT, maintains and also here still the notes 1879119, 1819818 considered
(the SAP version here is 6.04 SP11) the file is output with UTF-16 if you use the FTDA download function.
If you display the xml file and use the download function here it will be output with UTF-8.
I will post an error message.
By the way a question, does anyone here have something to do with the urgent transfers (order type CCU, code UGRP, instruction keys)
to do? Would be interested in info. Looks like we need to create extra payment methods for this and possibly our own format trees.
The info from the bank is still quite sparse that this is "...only to 4.11.2013..." relevant
Greetings Christian - Hello Christian,
the problem with UTF-8 & UTF-16 is well known.
Have a look at HW 1144841 as well as the thread here in the forum - Group SEPA - 10 UTF-8 UTF-16
Best regards - Hello Marco,
was known - still does not work.
Greeting Christian - Hello together,
I also have a comprehension problem here again.
I have now followed point one in HW 1144841 by adding the SE19 around my two ZDEPA_XX format trees into the filter expressions.
Now I create an XML file and regardless of how I download it, I get the following result:
The namespace 'urn:iso:std:iso:20022:tech:xsd:pain.008.001.02' of the root element 'LclInstrm' does not match the required namespace 'urn:iso:std:iso:20022:tech:xsd:pain.008.002.02'
'C:\...\3007_XML_List.XML' contains an XML document that does not match the schema definition (2.5 current as of 01.11.2010)!
Line 2/120 : Unknown element 'Document'.
Line 34/15 : Warning: according to allocation guidelines the element 'PstlAdr' should not be allocated!
Line 84/16 : Warning: according to allocation guidelines the element 'PstlAdr' should not be occupied!
How do I turn off the error "Unknown element Document"?
Do I have to set something else in the BADI?
Thanks and best regards - Hello Marco,
is the MODIFY_OUTPUT_FILE method pronounced (SE19, Interface tab)?
Many greetings
EC1055 - Hello EC1055,
sorry, I am not yet an ABAP professional.
What do you understand by distinct? I see in the SE19 - Interfaces the following (See attachment).
Greetings
Marco
- Hello Marco,
just double-click on the method or the name. Does it say anything there?
Many greetings
EC1055 - Hello EC1055,
yep. Program code for conversion to 4110 probably.
I have already searched for SEPA_DD / SEPA_CT, because I thought I might have to enter my ZSEPA_XX here...
Greetings
Marco - Hello,
I have found it!
Cus - Financials - Debit & Credit - Business transactions - Outgoing payments - Outgoing payments automatically - Payment medium - Payment medium formats of PMW - Create and assign selection variants
Select variant (in my case: ZSEPA_DD/CT) - Sel. Select bank variant - (Menu) Variant - Edit variant - Format parameters (here I have taken the values from HW 1540040).
Proposal again created with data carrier - now the XML Checker says only:
'C:\...3007_xml_liste.XML' contains a correct SEPA XML document (2.5 current as of 01.11.2010)!
Line 34/15 : Warning: according to allocation guidelines the element 'PstlAdr' should not be allocated!
Line 84/16 : Warning: according to allocation guidelines the element 'PstlAdr' should not be used!
Does anyone know the warnings?
Best regards
Marco - Hello Marco,
Congratulations!
You can ignore the warnings. The PstlAdr element is supposed to remain empty, but SAP writes values there anyway.
The file will still be accepted by the house bank.
Many greetings
EC1055 - Hello EC1055,
best thanks!!!
I will now document cleanly and maintain everything necessary in the variants for our house banks and then see what the banks say
Greetings
Marco - Hello together,
must become active here nevertheless once again.
C:\xxx.XML' contains a XML document that does not comply with the schema definition (2.5 current as of 01.11.2010)!
Line 70/14 : Data type error: Type:InvalidDatatypeValueException, Text:Value '' with length '0' falls below the minimum length of '1' .
Line 23/41 : Note: The execution date is not in the future!
Line 29/15 : Warning: according to allocation guidelines the element 'PstlAdr' should not be allocated!
Line 62/16 : Warning: according to allocation guidelines the element 'PstlAdr' should not be occupied!
Does anyone know these messages when creating ZSEPA_CT?
All settings are done so far.
Thanks and best regards
Marco - Hello Marco,
regarding line 70: Which XML tag is there? A value seems to be missing here.
To line 23: The payment run TODAY should have TOMORROW as posting date. Then the execution date ReqdExctnDt is TOMORROW and is therefore in the future.
Regarding line 29/62: As already written, you can ignore this warning.
Many greetings
EC1055 - Hello EC1055,
it says:
Rmt Inf
Ustrd
Presumably that is the intended use. However, I have not yet found why this is not drawn....
Thanks and greetings
Marco - Hello Marco,
even if the intended purpose is not drawn, there should be at least NOTPROVIDED in .
Just check the settings in the OBPM2 and see if the purpose is entered in the payment method.
Many greetings
EC1055 - Hello EC1055,
and this is exactly where the error was.
In the new payment method, the purpose was not entered.
There are simply a lot of dependencies that play a role here!
Thank you and best regards
Marco - Hello all,
I have now received the following hint from two banks (after checking the XML):
3) References and
They use the same value for the as for the .
But both references refer to different contents and help to identify them.
to identify them. The identifies the whole file, while the
the "only" identifies one collector within the file.
At the latest when you send two collectors in one file (e.g. with different
different due dates) you no longer have a clear assignment.
In addition, both references are used e.g. with the EBICS transmission.
Therefore you should name the references differently
4) References and
In the present file on transaction level the is occupied,
but is not. The is actually intended
to be used by a service provider when he submits payments to the bank
for you at the bank. In this case it is only used to
Identify the individual transaction when it is submitted.
If the individual transaction is to be identified, then the assignment
of the is clearly more purposeful! This reference is transferred in all
processing steps. This reference is also part of the
of the EREF+ transaction information and helps the recipient of a payment in the automatic
automatic assignment of a payment, or if the payment cannot be
payment, the return can also be identified via this reference.
identifiable. Thus the is actually the most important ID
and should therefore be clearly documented in any case.
At this point, I would be interested to know which of you has implemented this and in what way?
Best regards
Marco - Hello,
the problem arises when you create your own payment media and do not use standard.
There are two OSS notes for this:
1830590
1688643
Many greetings
Marlies Lampka Marco.K:
If the individual transaction is to be identified, the assignment
of the is clearly more purposeful! This reference is transferred in all
processing steps. This reference is also a component
of the turnover information EREF+ and helps the receiver of a payment with the
automatic assignment of a payment, or if the payment cannot be attached
, also the return is over this reference
identifiable. Thus, the is actually the most important ID
and should therefore be clearly documented in any case.
Hello,
in the standard SAP format tree the is assigned with the clearing document number. This information should not be helpful for the recipient of the payment. The standard assignment is therefore only useful internally for returns or bank statement processing.
But the assignment of the can be changed at Bedrf.
Best regards
InDieDa
(IT consultant, process/project manager)- Hello indieda,
I have now also found out that it affects the returns.
Have you set that with you?
How can I change this sensibly?
Best regards
Matching learning content
Release: Feb 7, 2025
A Practical Guide to Advanced Payment Management with In-House Banking
Mary LoughranPraveen Gupta
- Introduction to SAP advanced payment management
- Advanced payment management and in-house banking supported scenarios
- Confi guration and master data setup in both SAP S/4HANA Cloud Private Edition (PCE) and Public Cloud
- Accounting entries, helpful apps, transaction codes, authorization objects, and security roles
Release: Oct 29, 2020
A Practical Guide to Accounts Payable in SAP S/4HANA Fiori
Oona Flanagan
- Introduction to SAP S/4HANA and Fiori
- Organizational structure and master data
- Purchase-to-pay process, invoice and credit note posting, and the GR/IR reconciliation
- Payments and closing and reporting
Release: Aug 20, 2021
A Practical Guide to the General Ledger in SAP S/4HANA Fiori
Oona Flanagan
- Organizational structure and master data essentials
- General Ledger basics including document splitting and document types
- Key transactions from journal entries to intercompany postings
- Closing tasks and reporting