25 Answers

• 00

  

  User #36912 10/20/23, 1:56 PM

  Hello Together,
  How long is the VWZ allowed to be for foreign payments - i.e. non sepa?
  Thanks for the information.
  Many greetings
  S. Wechsler

  report
• 00

  

  User #36912 10/20/23, 1:56 PM

  Hello Joko,
  I will be looking into this over the next few weeks.
  My customer has already had a developer set things up.
  In the next days/weeks I will do the customizing and tests.
  If someone already has more experience, I would also appreciate information.
  Otherwise I will contact you again in the next weeks.
  Many greetings
  Silke Wechsler

  report
• 00

  

  Plucinski 10/20/23, 1:56 PM

  Hello Silke,
  If you make a NON SEPA payment, this means that the recipient bank is not located in the known 32 SEPA countries.
  This means then again that one treats such payments as before as DTAZV, thus a completely normal foreign payment, as before also. One creates thus a completely regular TXT file...with e.g. payment method L.
  Now again to the HW 1665873, which the previous speaker mentioned. Does anyone have practical experience with it. The manual contains 59 pages. Is this new format tree now SEPA-compliant for all 32 countries and therefore generally valid?
  With kind regards
  Jens Plucinski
  www.jensplucinski.de
  Consultant Business Economist SAP FI

  report
• 00

  

  User #36912 10/20/23, 1:56 PM

  Hello Jens,
  the CGI_XML_CT format is for non-sepa countries.
  It is for third country payments with XML.
  DTAZV is not XML after all.
  So there is now a new format to map foreign payment using XML.
  I am in the process of implementing this at a customer (the bank wants an XML format there).
  I can say more about this in the next week.
  Many greetings
  Silke

  report
• 00

  

  Plucinski 10/20/23, 1:56 PM

  Hello Silke,
  thanks for the info
  With kind regards
  Jens Plucinski
  www.jensplucinski.de
  Consultant Business Economist SAP FI

  report
• 00

  

  joko (Author)10/20/23, 1:56 PM

  (Hehres) The aim of this format is to establish a uniform and comprehensive payment medium format for international payments.
  established. If this succeeds, it would really be a breakthrough in international payments in my eyes.
  We are currently trying to bring our international payments (i.e. not only payments from DE to XY country, but also from non-DE company codes to foreign countries) to a uniform xml format.
  Deutsche Bank also offers a DMEE format tree for this purpose (ZDB_INTL), but it is DB-bank specific.
  Under the OSS note 1590159 (must be activated via the DB) the corresponding format trees are made available.
  Sincerely
  joko

  report
• 00

  

  User #36912 10/20/23, 1:56 PM

  Hello Jens, Hello Joko,
  it took a little longer.
  The 59 pages of the note HW 1665873 are installed. The transports in the test system.
  Now I could generate the first XML files.
  It works.
  But now I have to rebuild the DMEE, i.e. the XML format according to the banks wishes.
  I already had to do that with Sepa-CT payments.
  But so far everything looks good.
  I will report again when the tests are done.
  Many greetings
  Silke

  report
• 00

  

  joko (Author)10/20/23, 1:56 PM

  Hello Silke,
  Thanks for the info.
  I'm glad it worked out right away.
  Can you also say something about the bank requests?
  Would be interesting to see what bank specific customization requests there are for the format.
  MfG
  joko

  report
• 00

  

  weeh1 10/20/23, 1:56 PM

  Hello Joko,
  so I am implementing and the CGI_XML_CT supports a lot among others SEPA. Unfortunately the documentation doesn't describe so exactly how to access the different payment media. What I have seen so far the XML formats are:
  SEPA
  SDVA
  URGP
  NURG
  URNS
  is supported. This is partly controlled by the instruction keys. Unfortunately I can't find any reasonable documentation how the CGI_XML_CT has to be controlled in detail to get the desired result. Does anyone have more information about this or has already found something in the SAP OSS?
  Best regards
  Werner

  report
• 00

  

  User #36912 10/20/23, 1:56 PM

  Hello Joko,
  so, the bank adjustments were very intensive for me.
  My bank still had the pain...02, so I adapted the DMEE to pain...02.
  If the bank ever goes to the newer format, yes I still have the original CGI_XML_CT format.
  Something I puzzled out was that the bank did not accept the IBAN from the own house bank account.
  (IBAN is filled and delivered).
  The account number, on the other hand, was no longer populated, so I could not easily include this field.
  I have now, the field IBAN taken and from the place 14 from 8-characters - which corresponds to the account number.
  Otherwise I could adapt the DMEE without problems - even if here just the adaptations were very much.
  From the procedure: I sent the file to the bank for testing and they reported the errors back to me.
  I expect that we will now go live with this (pragmatic) solution in the coming week.
  Many greetings
  Silke

  report
• 00

  

  joko (Author)10/20/23, 1:56 PM

  Hello Silke,
  thanks for the info.
  If I understand your information correctly, it means that bank specific adjustments to the format are needed,
  so that it can be used.
  Can the format now be used for other banks without further adaptations or are new adaptations then necessary?
  I suspect the latter :-(
  The consequence can then only be to reduce the number of banks in the payment traffic as far as possible.
  Or to specialize in DMEE; I think there will soon be a great demand for specialists here :-)
  MfG
  joko

  report
• 00

  

  Plucinski 10/20/23, 1:56 PM

  I am again concerned with the HW for creating the CGI_XML_CT. This seems to be relevant for countries like Denmark. Has anyone of you installed the 59 page HW ?? How long does the installation take ?
  Is there anything special to note after installing the HW ??
  Please for info
  With kind regards
  Jens Plucinski
  www.jensplucinski.de
  Consultant Business Economist SAP FI

  report
• 00

  

  pkoenicke 10/20/23, 1:56 PM

  Hello Jens,
  I have already implemented this note for three of my customers - takes about half a day. Backgrounds for the use were different with my customers - on the one hand the one house bank wanted to accept with the start of SEPA only XML files (also for non-EUR payments) and on the other hand internal harmonization wishes to use only the PMW and XML as data carrier format.
  Now I don't remember any special problems with the installation of the note - but it is still necessary to coordinate and if necessary adapt with the individual banks afterwards.
  In the next two weeks I will probably implement this hint again for another customer.
  Best regards,
  Patrick

  report
• 00

  

  jkspeedy 10/20/23, 1:57 PM

  Hello and good evening,
  I have a little problem with the CGI format tree. In the fields InitgPty > Id > OrgId > Othr > Id and Dbtr > Id > OrgId > Othr > Id the field should be filled with the content from the field DTKID via the structure FPAYHX.
  What is the origin of the DTKID field in the structure? I have filled the corresponding field Customer number under Data medium exchange for the house bank, but nothing arrives.
  Then I tried to set the field as a constant, but nothing is displayed here either.
  What error could there be?

  report
• 00

  

  jkspeedy 10/20/23, 1:57 PM

  Hello,
  we have solved the above problem in InitgPty > Id > OrgId > Othr > Id by changing the function block in OBPM1 at event 05. Now the information is taken there from the house bank master data field DTKID and filled into the field of the structure FPAYHX-REF02.
  However, this field cannot be entered in the node or field of the format tree Dbtr > Id > OrgId > Othr > Id. No matter what is stored there, whether reference to the aforementioned node, reference to the structure field or constant. The field is simply ignored. Does anyone know the effect?
  Many greetings
  Jürgen Kötting

  report
• 00

  

  jkspeedy 10/20/23, 1:57 PM

  So,
  the bank has now done the roll backwards and only needs the changed knot! For whatever reason.
  Now I still have a problem with the instruction key. Implemented is everything for GB URGP, SDVA, SEPA URNS as instruction (code word). If I enter the instruction key for SEPA, I would expect the InstrPrty = Norm information in the XML under PmtTpInf and SEPA in SvcLvl. For Non urgent payments this works. Does anyone have an idea what the problem could be? The instruction key is entered in the document, but the node PmtTpInf is hidden, which means that no information was pulled into the payment medium.
  Does anyone know this phenomenon and can tell me what could be the reason?
  Greetings
  Jürgen

  report
• 00

  

  viraghk 10/20/23, 1:57 PM

  Hello,
  we are implementing CGI_XML_CT tree for CZ, PL and RO countries.
  Can you please explain what controls the instruction key? How should it be set?
  Thanks.
  LG,
  viraghk

  report
• 00

  

  Plucinski 10/20/23, 1:57 PM

  Please go to the transaction fi12. From there you can get to the house bank of the company codes. There you can enter instructions concerning the payment transactions in SAP.
  With kind regards
  Jens Plucinski
  www.jensplucinski.de
  Consultant Business Economist SAP FI
  

  Last edited on 06.12.13 19:31

  report
• 00

  

  viraghk 10/20/23, 1:57 PM

  Hello,
  I have problems with the bank control key.
  For CZ in the created XML file the bank control key was not inside and the bank accepted it like that.
  For RO actually the same DMEE tree is used. However, in the XML file created for RO the key was inside, but it was empty: . So the bank did not accept the file: must be either removed or filled.
  What can be the reason that it was in one file (but empty) and not in another file?
  Thank you.
  LG,
  viraghk

  report
• 00

  

  Phil2908 10/20/23, 1:57 PM

  Hello viraghk,
  this is due to an incorrect XSLT transformation. SAP Note 1942196 gives instructions on how to fix this problem.
  Best regards,
  Philipp

  report
• 00

  

  jkspeedy 10/20/23, 1:57 PM

  Hello and good evening,
  I am struggling with the problem that the format tree does not generate SEPA payments.
  I had read that from the combination of currency and recipient country for the payments in the SerivceLevel SEPA is automatically entered.
  So it is about the entry :
  
  
  SEPA
  
  
  SEPA under Tag CD.
  Thanks for the help
  Greetings Jürgen

  report
• 00

  

  jkspeedy 10/20/23, 1:57 PM

  Phil2908:

  ---

  Hi viraghk,
  this is due to an incorrect XSLT transformation. SAP Note 1942196 gives instructions on how to fix this problem.
  Best regards,
  Philipp
  

  
  Apparently the note has been withdrawn or is being revised. Current message is: document is not released!
  Greetings
  Jürgen

  report
• 00

  

  Fischera 10/20/23, 1:57 PM

  I have problems with the CGI format.
  Apparently SAP builds in country specific requirements which then result in the format not being accepted in other countries.
  Current example:
  Note 2007449.
  There are adjustments made to the format tree in various places. For example, BIC Not Provided appears if no BIC is available in the system. This brought a well-known German bank, which we use in Italy, on the plan, since there expliozit Not Provided is not desired. According to the bank, they strictly adhere to the corresponding specifications according to ISO.
  In the CGI format, there are country-specific adaptations in various places, which are controlled by validation of the country (in variant of SAPFPAYM). The developer of/for 2007449 has not provided his Spain-specific changes with any queries on the country.
  OSS "discussion" is ongoing.
  The bank told me (3 months ago) that they wanted to approach SAP again, as it could not be that adjustments would be made to the SAP CGI_XML standard that would not fit the ISO standard. Apparently there is no news yet. So now I have to "screw" the CGI format so that it still fits for the countries that are supposed to use it.
  Where the issue really lies is not clear to me. ADazuste I would have to compare ISO, the format certification of the bank and SAP standard. A tedious business.
  How do others solve this, who work in a system with several posting areas in different countries ? Just use Z formats ?

  report
• 00

  

  cellman99 10/20/23, 1:57 PM

  Hello all,
  I have created the CGI_XML_CT format for a customer. But the bank reported back that the field AddtlRmtInf is a mandatory field and must be filled:
  
  Test
  The error message reads:
  The field '/CdtTrfTxInf/RmtInf/Strd/AddtlRmtInf' should be filled in. The field '/CdtTrfTxInf/RmtInf/Strd/AddtlRmtInf' should be provided and non-empty.
  How can I fill this field? All relevant fields are filled in the document. "Test" has been written in by the bank. We are using the latest format tree.
  Can someone help me here?
  Thank you very much and best regards
  

  Last edited on 30.07.20 21:36

  report
• 00

  

  renbau 10/20/23, 1:57 PM

  Hello,
  can someone help me?
  I get the following error message when uploading the file (outgoing payment ISR):
  0003: Error in the structure of the XML element /Document/CstmrCdtTrfInitn/PmtInf[1]/CdtTrfTxInf[1]/CdtrAgt/FinInstnId/ClrSysMmbId-->.
  
  
  
  
  
  
  UNDEF
  
  
  This is how it should possibly look like:
  CHBCC
  
  89095
  
  
  This seems to concern the bank data. These are completely pleged, with bank key and BLZ.
  The format updates 12-33 are not imported. Can this be the reason?
  VG+Thanks!
  

  Last edited on 13.11.20 14:33

  report