09-04-2011 7:47 AM
Dear gurus,
i use the tree type 'PAYM' and format tree 'sepa_ct' but i am getting the below output in a different format
<?xml version="1.0" encoding= "utf-8"?><Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.02" xmlns:xsi="http://www.w3.org/20
um>0.00</CtrlSum><Grpg>MIXD</Grpg><InitgPty><Nm/><PstlAdr><Ctry/></PstlAdr></InitgPty></GrpHdr><PmtInf><PmtMtd>TRF</PmtMtd><PmtTpInf><Sv
><DbtrAcct>##<Id><IBAN/></Id></DbtrAcct><DbtrAgt><FinInstnId><BIC/></FinInstnId></DbtrAgt><ChrgBr>SLEV</ChrgBr><CdtTrfTxInf><PmtId><EndT
d></CdtrAgt><Cdtr><Nm/><PstlAdr><Ctry/></PstlAdr></Cdtr><CdtrAcct><Id><IBAN/></Id></CdtrAcct><RmtInf><Ustrd/></RmtInf></CdtTrfTxInf></Pm
i use the tree type ' ASLD' and format tree ' AUSTRIA_ZM_XML' ,for that i am getting the expect output
<?xml version="1.0" encoding="utf-8" ?>
- <ERKLAERUNGS_UEBERMITTLUNG>
- <INFO_DATEN>
<ART_IDENTIFIKATIONSBEGRIFF>FASTNR</ART_IDENTIFIKATIONSBEGRIFF>
<IDENTIFIKATIONSBEGRIFF />
<PAKET_NR />
<DATUM_ERSTELLUNG type="datum">2011-09-04</DATUM_ERSTELLUNG>
<UHRZEIT_ERSTELLUNG type="uhrzeit">12:02:51</UHRZEIT_ERSTELLUNG>
<ANZAHL_ERKLAERUNGEN>0001</ANZAHL_ERKLAERUNGEN>
</INFO_DATEN>
- <ERKLAERUNG art="U13">
<SATZNR />
- <ALLGEMEINE_DATEN>
<ANBRINGEN>U13</ANBRINGEN>
<ZRVON type="jahrmonat" />
<ZRBIS type="jahrmonat" />
<FASTNR />
<KUNDENINFO />
</ALLGEMEINE_DATEN>
- <ZM>
<UID_MS />
<SUM_BGL type="kz">0000000000</SUM_BGL>
</ZM>
</ERKLAERUNG>
</ERKLAERUNGS_UEBERMITTLUNG>
if anyone know give me a thread.
09-05-2011 3:47 AM
09-05-2011 3:47 AM
09-05-2011 6:54 AM
hi madhu,
thanks for your reply,
i am able to create dmee structure and the format tree is consistent but output is not in a valid xml file format,
for example
****************************************************************************************************
(1) Tree type = 'PAYM' and Format tree = 'ZTEST1'
i have created the node like this.
dmee tree: properties
header
value
output is
<?xml version="1.0" encoding="utf-16"?><header><value>13</value></header>
*********************************************************************************************************
(2) Tree type 'ASLD' and Format tree 'ZTEST1'
I created the node like this.
dmee tree: properties
header
value
output is
<?xml version="1.0" encoding="utf-8" ?>
- <heading>
<value />
</heading>
Here also I have created same node however I get the output in a valid xml format.
so please guide me what shall i do for getting valid xml file in PAYM tree type.
09-21-2011 5:58 PM
Hello
If your SAP is upgraded to UNICODE, maybe you have a problem with it, as the FDTA download may either download a UTF 16 file , which means you have blanks between each character of your file ( this with using codepage 1402 ) , either download an AN'SI file with a parasit byte at the beginning ( with codeapge 1100 )
This makes your file invalide. You can check with an hexadecimal editor .
Maybe this tip might help : in FDTA transaction, insted of downloading your file with the standard option, first display it on screen. Then , use the option XML / Download / this will create a much nicer file from the display , not from the stored file .
I hope this helps
Best regards
CG
09-22-2011 12:35 PM
09-22-2011 12:42 PM
hi gurus
i want to download XML file automatically after executing the payment run and generated xml file should save in the bank server .
expecting your reply.
regards
srinivasan. R
09-22-2011 4:06 AM
Hi ,
as CG said , nothong wrong with the file.
check tcode FBPM for given Payment runs.
regards
Prabhu
10-05-2011 2:06 PM
Hi Citizen
By default , the file is stored as a TEMSE , which is not easily accessible.
Optionnally :
In report SAPFPAYM , which creates the payment medium , once you have selected your Payment Medium Format , a checkbox parameter becomes available :
==> Output to file system , and you can select the dataset name and location you want.
For example : /usr/sap/PR1/COMM/my_pmw.xml
You can save a report variant with this option, which is the variant to be called by your payment cycle.
You can then retrieve the dataset using a ftp transfer or write a report to download it on your disk or a server.
Be aware that it will be overwritten by the next payment cycle. Maybe you can maintain a variable of variant to limit the risk
So as to have for example :
/usr/sap/PR1/COMM/my_pmw_20111005.xml today ,
/usr/sap/PR1/COMM/my_pmw_20111012.xml next week , etc ...
I do not know what will happen with the unicode problem in this case.
I hope this helps
Best regards
CG
10-05-2011 6:23 PM
Hello
After consulting some OSS notes ...
In fact there is a Badi to solve the initial problem ( incorrect XML file ).
Copy the Badi DMEE_XML_BADI_01 as a ZDMEE_XML_BADI_01. ( transaction SE19 )
In your specific new Badi :
Add your Z_tree format in the filter characteristic, remove the standard tree SEPA_CT and SEPA_DD to be safe.
Activate the Badi. That's enough ...
I just tested this ... :=)
Or you could change the standard BADI ( which is a standard modification , so I don't )
Best regards
Catherine
12-08-2011 8:10 PM
Catherina ..
Do i need to save this ZBADI in the same package as of Classic BADI ?
Thanks,
Komaravolu
12-09-2011 10:01 AM
Hello Komaravolu
I didn't create this Z_badi... in a SAP standard package , but in a specific ZF01 we have on our system.
(ZF for Specific in Finance ....)
I use SAP standard Package only for SAP standard modifications related to OSS notes ...
Best regards
Catherine