IDOC-XI-JMS Adapter
Hi
I have to build interface for scenario IDOC-XI-JMS adapter and legacy syetem is MQ-series. All the jar files has been deployed which is the pre-requisite to use JMS adapter.
Can anyone tell me if I should send data in file or as message.
Also if you can tell me the steps to build this interface. Please refer to some relevant blogs but would appriciate if you can explain me steps.
Points will be rewarded for the appropirate replies.
Regards
Hi,
>IDOC-XI-JMS adapter
Sender Side IDOC Adapter, Hence No Need Sender Agreement, Import the IDOC in XI System , Declare the Data Type for the Receiver side..Message Type..Message Interface as Ingoung..Do Message Mapping..Interface Mapping..In Configuratio Receiver JMS Adapter. Mention the Driver Information,User ID & Password and go ahead and test it
Regards
Agasthuri Doss
Similar Messages
-
EDI Idoc -- Receiver JMS Adapter.
Hi,
I'm facing this issue from few days.
Sender is EDI Idoc and contains header and Footer.
This is placed in the application server of SAP system.
From there xi picks the EDI Idoc and sends to JMS server.
Facing problem on the receiver JMS Adapter.
Find the error message.
"Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: No transition found from state: ERROR, on event: process_commence for DFA: CC_JMS_RCV_DEVWR0000000:165b1638fd823a8f822f0db8a9b1d488"
I have provoded the "dict" and "doc" value also.
Pls suggest.
Thanks in advance,
Jeevan.Hi Guys,
There could be some problem while deploying the libraries. Check out the thread No transition found from state: STARTING
Thanks,
PP -
Idoc xml message in JMS adapter
Hi All,
Question 1:
My scenario is MQ series(JMS adaptr) to SAP(IDOC adptr) . In my mapping both source and target structure is same IDOC structure.Where MQ series will send IDOC xml. In such case shall i need to do content conversion at JMS adapter level or not.whthr IDOC xml can be directly handle at Mapping level without doing any content conversion in adapter level.
Question 2(viceversa):
SAP(IDOC adptr) to MQ series(JMS adaptr) . In my mapping both source and target structure is same IDOC structure.Where MQ series expect me IDOC xml. How to handle content conversion at JMS recvr adapter level.
my assumption only in case of (xml to plain) and (plain to xml) require content conversion here my Input and output is IDOC xml.Saravanan,
As Expert Vishnu Mentioned,
>In such case shall i need to do content conversion
NO need to use
>How to handle content conversion at JMS recvr adapter level
http://help.sap.com/saphelp_nw04/helpdata/en/24/4cad3baabd4737bab64d0201bc0c6c/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-adapters/how%20to%20use%20the%20content%20conversion%20module%20with%20xi%203.0%20j2ee%20jms%20adapter.pdf
Cheers
Agasthuri Doss -
How to get the incoming file name using JMS adapter and SOAP adapter
Hi Everybody,
In one of my interface i need to get the file name of incoming flat file using JMS adapter at sender side. and then i am using xslt to convert it to IDOC and then posting to SAP IDOC.
my incoming filname are in this form price<DateTimestamp>.txt. when i do the tranformation this incoming file name should be part of one element in the IDOC which i am posting.
EX:
<IDOC
<REF>price<DateTimestamp>.txt</REF>
</IDOC>
Hope it is clear to everybody. I need your suggestion how i can capture this incoming file name and send it as part of IDOC.
Thanks
rajIf they are passing it in message id or correlation id,
you can access it using
<xsl:variable name="dynamic-conf"
select="map:get($inputparam, 'DynamicConfiguration')" />
<xsl:variable name="dynamic-key"
select="key:create('http://sap.com/xi/XI/System/JMS', 'DCJMSMessageID/ DCJMSCorrelationID')" />
<xsl:variable name="dynamic-value"
select="dyn:get($dynamic-conf, $dynamic-key)" />
Check this:
http://help.sap.com/saphelp_nw70/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
Thanks,
Beena. -
JMS Adapter setting the header data of MQ message
Hi All,
I need to set the properties in JMS adapter for setting the header data of MQ message.
JMS_IBM_MQMD_Format = MQFMT_NONE.
Thanks in advance
RavijeetHi All,
I am stuck in a typical XI issue.......I have a scenario where my input to XI is IDoc and output is xml message going to IBM MQ.
The IDoc is sending some chineese character which is fine is SXMB_MONI Integration server and also fine in the payload of message monitoring, so feel the message is going fine from XI to MQ.
But the receiver EDI system which is picking the message from MQ queue says the chinese characters are getting corrupted. They say that you need to set the additional properties in MQ header data
JMS_IBM_MQMD_Format = MQFMT_NONE.
How do I do this in communication channel for jms adapter ? How to I set the MQ header data in jms communication channel ?
Thanks in advance
Ravijeet
Edited by: RAVIJEET DAS on May 12, 2009 8:27 AM
Edited by: RAVIJEET DAS on May 12, 2009 8:27 AM -
How o place Flat file Using JMS Adapter.
Hi Frnds,
I have one scenario ,
Sender side i am having IDOC, i want convet the IDOC into Flat file. But my receiver side i have to use only JMS Adapter,
Flat file i have to place in FTP Server using JMS Adapter.
Can ne share your thoughts..
Regards,
rajRaj,
The below Link will help
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50061bd9-e56e-2910-3495-c5faa652b710
Surya,
Welcome Back to SDN.
Regards
Agasthuri Doss -
MessageTransformBean in sender JMS Adapter flat file to xml conversion
Hi All,
The scenario is MQ (Flat File ) --->PI -
>Idoc
The flat file structure is
112233
AABBCC
The expected XML Structure after using MessageTransformBean in the sender JMS adapter is
<Record>
<Row>
<f1>11</f1>
<f2>22</f2>
<f3>33</f3>
</Row>
<Row>
<f1>AA</f1>
<f2>BB</f2>
<f3>CC</f3>
</Row>
</Record>
But I am getting 2 SEPARATE xml messages each with only one Row in it like the following
1st XML:
<Record>
<Row>
<f1>11</f1>
<f2>22</f2>
<f3>33</f3>
</Row>
</Record>
2nd XML:
<Record>
<Row>
<f1>AA</f1>
<f2>BB</f2>
<f3>CC</f3>
</Row>
</Record>
I would like to have one xml message with all rows in it.It seems the MessageTransformBean is not recognizing the end of line in the flat file.Do i need to use endSeparator explicitly.
I followed the "How to use Content Conversion in JMS Adapter " and configured the adapter,still no luck..
Any Help greatly Appreciated
Thanks,
CHi Chirag,
The parameter name sequence changes alphabetically by itself when I save and activate it eventhough I enter as it is in the document.How to stop changing this sequence or put it the order as required in the Module Processor.
Currently my sequence is
Transform.Class
Transform.ContentType
xml.conversionType
xml.documentName
xml.documentNamespace
xml.fieldFixedLengths
xml.fieldNames
xml.processFieldNames
xml.structureTitle
Let me know how to change the sequence ,if that is the issue.
Thanks,
C -
Content conversion in Sender JMS Adapter
Hi,
Scenario is file to IDoc
My source file is ' ; ' separated file coming from MQ via JMS adapter. now I need to convert this to XI.
Source DT looks like
Root
HEADER (Occurance 1)
Field 1
ISOCURCD
TRANKODE
IDENTIFIER
DATO
TIME
DETAIL(Occurance 1 to unbounded)
ISOCURCD
TRANKODE
EFFDATE
COMMDATE
DKKVAL1
USDVAL1
TRAILER(Occurance 1)
ISOCURCD
TRANKODE
TRANCOUNT
According to How to use content conversion in JMS guide from SDN i have configured the content conversion parameters in the module of JMS sender adapter.
In the processing sequence given the module name as localejbs/AF_Modules/MessageTransformBean and module Key as Plain2XML.
And in module configuration
Parameter Name Parameter Value
Transform.Class com.sap.aii.messaging.adapter.Conversion
Transform.ContentType text/xml;charset=utf-8
xml.keyFieldName TRANKODE
xml.keyFieldType CaseSensitiveString
xml.recordsetName Root
xml.documentName MT_ROOT
xml.documentNamespace http://XXX.XXX.XX/xi/XXXXX
xml.processFieldNames fromConfiguration
xml.conversionType StructPlain2XML
xml.recordsetStructure HEADER,1,DETAIL,*,TRAILER,1
xml.HEADER.fieldNames Field1,ISOCURCD,TRANKODE,IDENTIFIER,DATO,TIME
xml.HEADER.fieldSeparator ";"
xml.HEADER.keyFieldValue H
xml.fieldSeparator ";"(if i don't use this then the file is not being picked and getting an error in the CC monitoring of RWB saying xml.field separator missing.)
Similarily for Detail and Trailer records as well.
But when I run the scenario, the file is being picked up but I am not getting any payload into the inbound message.
Can you please help me where I have configured wrongly. And one more thing will this configuration help for ; separated file .
Thanks & Regards,
Kumar
Edited by: Kumar on Dec 19, 2007 11:11 AM
Edited by: Kumar on Dec 19, 2007 11:15 AMHI,
Have you gone through the below pdf i think it will help to find ur mistake.
How to use conversion modules in JMS - https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
Thnx
Chiarg -
Change of Encoding in Sender JMS Adapter
Hi,
My scenario is like that:-
FTP->MQ Queue->JMS Queue->XI->R/3
From JMS Queue IDOC xml is coming in UTF-8 encoding to XI. In that IDOC xml certain special characters are there, say, some Latin or European character. But for the scenario XI->R/3, data are not getting posted to R/3. In XI side, it is not giving any error, but it is giving a flag (in QRFC Monitor) which is Error between two Character Sets.
I am unable to rectify this error. One solution I have guessed that is, it will be possible to resolve this issue if I can change the encoding in XI to ISO-8859-1. But I dont know how to change the encoding in Sender JMS Adapter in XI. Could you please help me to resolve this issue?
BR
Soumya BHi,
Check following:
1. In SXMB_MONI, what is the XML structure generated for inbound and outbound message. Check the encoding used in both. This could be checked by looking at the first line of XML generated. For UTF encoding, usually, the first line should look as follows:
<?xml version="1.0" encoding="UTF-8" ?>
2. If the encoding for both is different, try to figure out which encoding is used for Message Type in XI. For matching the encodings, you could change the XSD used for creating message type in XI. This way, the character encoding could be changed. And this solution should suffice if the problem has occured between XI to R3 scenario.
Also, for learning more about character encodings, you could visit following link:
http://www.cs.tut.fi/~jkorpela/chars.html
Hope it helps.
Bhavish.
Reward points if comments found useful:-) -
How to remove header data from JMS Queue while sending by jms adapter
Hi.
I have a problem regarding the MQ-series JMS adapter.
When writing the file the JMS adaptor putting some additional tags.
Actually we are converting idoc-xml to flat file by using ABAP mapping which is available in SAP document. We are using JMS Receiver adapter, whiel sending flat file to JMS QUEUE, it is displaying some extra xml tags. I think this is the header data available in IDoc XML. Can any body help me in removing header data.
There must be some way for XI's JMS adaptor to not include these information.
My example looks like this:
RFH Ø
¸MQSTR
¸ " is junk that I really dont need in the file.
How can you setup the JMS adaptor not to put in these information?
Thanks & Regards,
Madhusudhannot related
-
Hi Experts,
I am recivieng an IDOC into PI and sending to legacy using JMS adapter in MONI i am able to see successfull flag but in RWB its showing Status: System error
error code : CHANNEL_ DETERMINATION_FAILED
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException
Error while processing message 'db0458de-26fd-11e1-8c18-000030facf5b'; detailed error description: java.lang.NullPointerException at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.disconnectOnDemand(ConnectorImpl.java:225) ...
Can you help me on this.
Regards,
Prasad.hi Prasad,
check in your CC the connection option like "Create Connection on Demand": [http://help.sap.com/saphelp_nw70/helpdata/en/c1/739c4186c2a409e10000000a155106/content.htm]
check also with your JMS provider, if connection is operational.
Mickael -
Regarding Module Configuration of Receiver JMS Adapter
Hi,
Now i am working on IDoc to JMS interface, I am facing complexity in creating the structure in Module tab of Receiver JMS Adapter. Because the target system is expecting fixed length file so i should use the Local EJBs available in Module tab of Receiver JMS adapter and i need to pass the fieldFixedLegth parameters for all the nodes coming from DELVRY01 Idoc. I think creating structure for all the nodes in receiver jms adapter is so complex, If you are having any other alternatives, please share with me.
The below is the IDoc xml which is coming from source side.
<?xml version="1.0" encoding="UTF-8" ?>
<DELVRY01>
<IDOC BEGIN="1">
<EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT>100</MANDT>
<DOCNUM>000000000999999</DOCNUM>
<DOCREL>1145</DOCREL>
<STATUS>1</STATUS>
<DIRECT>1</DIRECT>
<OUTMOD>2</OUTMOD>
<IDOCTYP>DELVRY01</IDOCTYP>
<MESTYP>abcde</MESTYP>
<SNDPOR>efghi</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>LMNOP100</SNDPRN>
<RCVPOR>A000000023</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>TB</RCVPRN>
<CREDAT>20056556</CREDAT>
<CRETIM>183734</CRETIM>
<SERIAL>12345678</SERIAL>
</EDI_DC40>
<E1EDL20 SEGMENT="1">
<VBELN>006456451</VBELN>
<VSTEL>4656</VSTEL>
<VKORG>1665</VKORG>
<ABLAD>ABCDEDFJSDFDF</ABLAD>
<ROUTE>DFSDF</ROUTE>
<VSBED>08</VSBED>
<BTGEW>3.000</BTGEW>
<NTGEW>333.000</NTGEW>
<GEWEI>NNN</GEWEI>
<VOLUM>450.190</VOLUM>
<VOLEH>DMBG55TERTQ</VOLEH>
<ANZPK>00000</ANZPK>
<XABLN>0001995346331</XABLN>
<LIFEX>N</LIFEX>
<E1EDL22 SEGMENT="1">
<VSTEL_BEZ>ABCDEFGHIIJFLD</VSTEL_BEZ>
<VKORG_BEZ>SDFKJSDFSDF</VKORG_BEZ>
<ROUTE_BEZ>FSDNFKSDJFKJASDKFJSDJFL</ROUTE_BEZ>
<VSBED_BEZ>FNSDKFSD,F,MSDF,</VSBED_BEZ>
</E1EDL22>
<E1EDL21 SEGMENT="1">
<KDGRP>10545</KDGRP>
<BEROT>teGHGHst FGHHFGHXI </BEROT>
<TRAGR>0001</TRAGR>
<E1EDL23 SEGMENT="1">
<LFART_BEZ>Outbound delivery</LFART_BEZ>
<KDGRP_BEZ>LPHG Wholesale</KDGRP_BEZ>
<TRAGR_BEZ>On HHFH</TRAGR_BEZ>
</E1EDL23>
</E1EDL21>
<E1EDL18 SEGMENT="1">
<QUALF>ORI</QUALF>
</E1EDL18>
<E1ADRM1 SEGMENT="1">
<PARTNER_Q>AG</PARTNER_Q>
<PARTNER_ID>00000GHF12889</PARTNER_ID>
<LANGUAGE>EN</LANGUAGE>
<FORMOFADDR>Makro SA</FORMOFADDR>
<TELEPHONE1>041 3600TERTE605-C...</TELEPHONE1>
<TELEFAX>041 36006TRT47</TELEFAX>
<COUNTRY1>ZHFGHA</COUNTRY1>
<REGION>EHGHC</REGION>
<E1ADRE1 SEGMENT="1">
<EXTEND_Q>100</EXTEND_Q>
<EXTEND_D>6HG15FGHFG05006416</EXTEND_D>
</E1ADRE1>
</E1ADRM1>
<E1ADRM1 SEGMENT="1">
<PARTNER_Q>WE</PARTNER_Q>
<PARTNER_ID>00000178E87T</PARTNER_ID>
<LANGUAGE>EN</LANGUAGE>
<FORMOFADDR>Makro SA</FORMOFADDR>
<NAME1>Makro Port Elizabeth Br 14</NAME1>
<NAME3>t/a Makro SA</NAME3>
<STREET1>CDFJSDLFJLS d</STREET1>
<COUNTRY1>ZFSDFA</COUNTRY1>
<REGION>EFSDFC</REGION>
<E1ADRE1 SEGMENT="1">
<EXTEND_Q>100</EXTEND_Q>
<EXTEND_D>6001534453505006416</EXTEND_D>
</E1ADRE1>
</E1ADRM1>
<E1ADRM1 SEGMENT="1">
<PARTNER_Q>54OSP</PARTNER_Q>
<PARTNER_ID>404534501</PARTNER_ID>
<LANGUAGE>EN</LANGUAGE>
<COUNTRY1>Z5454A</COUNTRY1>
</E1ADRM1>
<E1ADRM1 SEGMENT="1">
<PARTNER_Q>OSO</PARTNER_Q>
<PARTNER_ID>1054400</PARTNER_ID>
<COUNTRY1>Z5453A</COUNTRY1>
</E1ADRM1>
<E1EDT13 SEGMENT="1">
<QUALF>006</QUALF>
<NTANF>2005455470706</NTANF>
<NTANZ>000000</NTANZ>
<NTEND>2005453470706</NTEND>
<NTENZ>00053454000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000000</ISDZ>
<IEDD>00005340000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
<E1EDT13 SEGMENT="1">
<QUALF>003</QUALF>
<NTANF>20070706</NTANF>
<NTANZ>000000</NTANZ>
<NTEND>200705345706</NTEND>
<NTENZ>000000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000053455400</ISDZ>
<IEDD>00000000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
<E1EDT13 SEGMENT="1">
<QUALF>001</QUALF>
<NTANF>20070706</NTANF>
<NTANZ>000000</NTANZ>
<NTEND>20070706</NTEND>
<NTENZ>000000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000000</ISDZ>
<IEDD>00000000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
<E1EDT13 SEGMENT="1">
<QUALF>007</QUALF>
<NTANF>20070709</NTANF>
<NTANZ>000000</NTANZ>
<NTEND>20070709</NTEND>
<NTENZ>000000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000000</ISDZ>
<IEDD>00000000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
<E1EDT13 SEGMENT="1">
<QUALF>010</QUALF>
<NTANF>20070705</NTANF>
<NTANZ>000000</NTANZ>
<NTEND>20705</NTEND>
<NTENZ>000000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000000</ISDZ>
<IEDD>00000000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
<E1EDL28 SEGMENT="1">
<ROUTE>ED545S1</ROUTE>
<DISTZ>0.000</DISTZ>
<E1EDL29 SEGMENT="1">
<ROUTE_BEZ>FKLSDJFLSJDFJSDFJLSDJFLKSD</ROUTE_BEZ>
</E1EDL29>
</E1EDL28>
<E1EDL24 SEGMENT="1">
<POSNR>000010</POSNR>
<MATNR>000000000000</MATNR>
<MATWA>000000000</MATWA>
<ARKTX>OmFDFS 2kg.</ARKTX>
<MATKL>FSD5345FSDFLAUND</MATKL>
<WERKS>10FDF40</WERKS>
<LGORT>01</LGORT>
<LFIMG>10545.000</LFIMG>
<VRKME>C54T</VRKME>
<LGMNG>10553545.000</LGMNG>
<MEINS>CT534555345545345</MEINS>
<NTGEW>1653454.000</NTGEW>
<BRGEW>181.000</BRGEW>
<GEWEI>KGM</GEWEI>
<VOLUM>450.190</VOLUM>
<VOLEH>DMQ</VOLEH>
<LADGR>0534543002</LADGR>
<TRAGR>0001</TRAGR>
<VKBUR>UF53401</VKBUR>
<VKGRP>160</VKGRP>
<VTWEG>00</VTWEG>
<SPART>00</SPART>
<GRKOR>000</GRKOR>
<EAN11>16001085031034</EAN11>
<POSEX>000000</POSEX>
<E1EDL25 SEGMENT="1">
<LGORT_BEZ>Main s53453453454tore</LGORT_BEZ>
<LADGR_BEZ>Forklift</LADGR_BEZ>
<TRAGR_BEZ>On pallets</TRAGR_BEZ>
<VKBUR_BEZ>Gener534534al Trade</VKBUR_BEZ>
<VKGRP_BEZ>RSM E534 Cape</VKGRP_BEZ>
<VTWEG_BEZ>FKLSDFKLS</VTWEG_BEZ>
<SPART_BEZ>FSDFSDFJoducts</SPART_BEZ>
</E1EDL25>
<E1EDL26 SEGMENT="1">
<PSTYV>TAN</PSTYV>
<MATKL>FGUND</MATKL>
<PRODH>0125VH</PRODH>
<UMVKZ>1</UMVKZ>
<UMVKN>1</UMVKN>
<KZTLF>B</KZTLF>
<UEBTO>0.0</UEBTO>
<UNTTO>0.0</UNTTO>
<KVGR1>Z4FDFSDFSD</KVGR1>
<KVGR2>TPS</KVGR2>
<E1EDL27 SEGMENT="1">
<PSTYV_BEZ>Standard Item</PSTYV_BEZ>
<PRODH_BEZ>OmoFFD Regular 8X2kg.</PRODH_BEZ>
<WERKS_BEZ>ConFSDFgella DC</WERKS_BEZ>
<KVGR1_BEZ>PE Cust Del</KVGR1_BEZ>
<KVGR2_BEZ>rd party sales</KVGR2_BEZ>
</E1EDL27>
</E1EDL26>
<E1EDL43 SEGMENT="1">
<QUALF>C</QUALF>
<BELNR>FDF</BELNR>
<POSNR>000010</POSNR>
<DATUM>FFSDF</DATUM>
</E1EDL43>
<E1EDL41 SEGMENT="1">
<QUALI>54</QUALI>
<BSTNR>test I Link</BSTNR>
<BSTDT>00000000</BSTDT>
<POSEX>000010</POSEX>
</E1EDL41>
</E1EDL24>
</E1EDL20>
</IDOC>
</DELVRY01>duplicate blog
-
Content conversion question for JMS adapter
Hi,
I need to put this again here.
I have the scenario R/3 IDoc -> XI -> MQ (webshpere). MQ requires plain text.
I have the IDoc ORDERS05 in multi level (nested in layers). But using the how to guid to convert the content I could go up to on level.
Based on the thread
Process Integration (PI) & SOA Middleware
It is not possible to use the conversion modules with XML2Plain key with parameter xml.conversionType value StructXML2Plain.
Please confirm if this is possible to convert a structure like below,
<ZSYSEX01>
.<IDOC BEGIN="1">
....<EDI_DC40 SEGMENT="SEGMENT0">
........<FIELD1>HEADER</FIELD1>
....</EDI_DC40>
....<E1STATS SEGMENT="SEGMENT1">
........<FIELD2>100</MANDT>
........<Z1HDSTAT SEGMENT="SEGMENT2">
...........<FIELD3>0200000716</FIELD3>
...........<Z1ITSTAT SEGMENT="SEGMENT3">
...............<FIELD4>1000</FIELD4>
...........</Z1ITSTAT>
........</Z1HDSTAT>
........<Z1HDSTAT SEGMENT="SEGMENT2">
...........<FIELD3>0200000717</FIELD3>
...........<Z1ITSTAT SEGMENT="SEGMENT3">
...............<FIELD4>1000</FIELD4>
...........</Z1ITSTAT>
...........<Z1ITSTAT SEGMENT="SEGMENT3">
...............<FIELD4>1001</FIELD4>
...........</Z1ITSTAT>
...........<Z1ITSTAT SEGMENT="SEGMENT3">
...............<FIELD4>1002</FIELD4>
...........</Z1ITSTAT>
........</Z1HDSTAT>
....</E1STATS>
.</IDOC>
</ZSYSEX01>
to plain text in JMS adapter.
Thanks!
JasonHi,
You have to use Content Converiosn in JMS Adapter Receiver side,
Module Sequence in the Receiver Channel
No. Module Name Module Key
1 localejbs/AF_Modules/MessageTransformBean XML2Plain
2 localejbs/SAP XI JMS Adapter/ConvertMessageToBinary CallJMSService
3 localejbs/SAP XI JMS Adapter/SendBinarytoXIJMSService Exit
Bases on Structure you have to configure the processing parameters,
please see the below link, it will helps you more
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
Regrads
Chilla.. -
Regarding Module Configuration of JMS Adapter
Hi,
Now i am working on IDoc to JMS interface, I am facing complexity in creating the structure in Module tab of Receiver JMS Adapter. Because the target system is expecting fixed length file so i should use the Local EJBs available in Module tab of Receiver JMS adapter and i need to pass the fieldFixedLegth parameters for all the nodes coming from DELVRY01 Idoc. I think creating structure for all the nodes in receiver jms adapter is so complex, If you are having any other alternatives, please share with me.
The below is the IDoc xml which is coming from source side.
<?xml version="1.0" encoding="UTF-8" ?>
<DELVRY01>
<IDOC BEGIN="1">
<EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT>100</MANDT>
<DOCNUM>000000000999999</DOCNUM>
<DOCREL>1145</DOCREL>
<STATUS>1</STATUS>
<DIRECT>1</DIRECT>
<OUTMOD>2</OUTMOD>
<IDOCTYP>DELVRY01</IDOCTYP>
<MESTYP>abcde</MESTYP>
<SNDPOR>efghi</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>LMNOP100</SNDPRN>
<RCVPOR>A000000023</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>TB</RCVPRN>
<CREDAT>20056556</CREDAT>
<CRETIM>183734</CRETIM>
<SERIAL>12345678</SERIAL>
</EDI_DC40>
<E1EDL20 SEGMENT="1">
<VBELN>006456451</VBELN>
<VSTEL>4656</VSTEL>
<VKORG>1665</VKORG>
<ABLAD>ABCDEDFJSDFDF</ABLAD>
<ROUTE>DFSDF</ROUTE>
<VSBED>08</VSBED>
<BTGEW>3.000</BTGEW>
<NTGEW>333.000</NTGEW>
<GEWEI>NNN</GEWEI>
<VOLUM>450.190</VOLUM>
<VOLEH>DMBG55TERTQ</VOLEH>
<ANZPK>00000</ANZPK>
<XABLN>0001995346331</XABLN>
<LIFEX>N</LIFEX>
<E1EDL22 SEGMENT="1">
<VSTEL_BEZ>ABCDEFGHIIJFLD</VSTEL_BEZ>
<VKORG_BEZ>SDFKJSDFSDF</VKORG_BEZ>
<ROUTE_BEZ>FSDNFKSDJFKJASDKFJSDJFL</ROUTE_BEZ>
<VSBED_BEZ>FNSDKFSD,F,MSDF,</VSBED_BEZ>
</E1EDL22>
<E1EDL21 SEGMENT="1">
<KDGRP>10545</KDGRP>
<BEROT>teGHGHst FGHHFGHXI </BEROT>
<TRAGR>0001</TRAGR>
<E1EDL23 SEGMENT="1">
<LFART_BEZ>Outbound delivery</LFART_BEZ>
<KDGRP_BEZ>LPHG Wholesale</KDGRP_BEZ>
<TRAGR_BEZ>On HHFH</TRAGR_BEZ>
</E1EDL23>
</E1EDL21>
<E1EDL18 SEGMENT="1">
<QUALF>ORI</QUALF>
</E1EDL18>
<E1ADRM1 SEGMENT="1">
<PARTNER_Q>AG</PARTNER_Q>
<PARTNER_ID>00000GHF12889</PARTNER_ID>
<LANGUAGE>EN</LANGUAGE>
<FORMOFADDR>Makro SA</FORMOFADDR>
<TELEPHONE1>041 3600TERTE605-C...</TELEPHONE1>
<TELEFAX>041 36006TRT47</TELEFAX>
<COUNTRY1>ZHFGHA</COUNTRY1>
<REGION>EHGHC</REGION>
<E1ADRE1 SEGMENT="1">
<EXTEND_Q>100</EXTEND_Q>
<EXTEND_D>6HG15FGHFG05006416</EXTEND_D>
</E1ADRE1>
</E1ADRM1>
<E1ADRM1 SEGMENT="1">
<PARTNER_Q>WE</PARTNER_Q>
<PARTNER_ID>00000178E87T</PARTNER_ID>
<LANGUAGE>EN</LANGUAGE>
<FORMOFADDR>Makro SA</FORMOFADDR>
<NAME1>Makro Port Elizabeth Br 14</NAME1>
<NAME3>t/a Makro SA</NAME3>
<STREET1>CDFJSDLFJLS d</STREET1>
<COUNTRY1>ZFSDFA</COUNTRY1>
<REGION>EFSDFC</REGION>
<E1ADRE1 SEGMENT="1">
<EXTEND_Q>100</EXTEND_Q>
<EXTEND_D>6001534453505006416</EXTEND_D>
</E1ADRE1>
</E1ADRM1>
<E1ADRM1 SEGMENT="1">
<PARTNER_Q>54OSP</PARTNER_Q>
<PARTNER_ID>404534501</PARTNER_ID>
<LANGUAGE>EN</LANGUAGE>
<COUNTRY1>Z5454A</COUNTRY1>
</E1ADRM1>
<E1ADRM1 SEGMENT="1">
<PARTNER_Q>OSO</PARTNER_Q>
<PARTNER_ID>1054400</PARTNER_ID>
<COUNTRY1>Z5453A</COUNTRY1>
</E1ADRM1>
<E1EDT13 SEGMENT="1">
<QUALF>006</QUALF>
<NTANF>2005455470706</NTANF>
<NTANZ>000000</NTANZ>
<NTEND>2005453470706</NTEND>
<NTENZ>00053454000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000000</ISDZ>
<IEDD>00005340000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
<E1EDT13 SEGMENT="1">
<QUALF>003</QUALF>
<NTANF>20070706</NTANF>
<NTANZ>000000</NTANZ>
<NTEND>200705345706</NTEND>
<NTENZ>000000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000053455400</ISDZ>
<IEDD>00000000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
<E1EDT13 SEGMENT="1">
<QUALF>001</QUALF>
<NTANF>20070706</NTANF>
<NTANZ>000000</NTANZ>
<NTEND>20070706</NTEND>
<NTENZ>000000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000000</ISDZ>
<IEDD>00000000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
<E1EDT13 SEGMENT="1">
<QUALF>007</QUALF>
<NTANF>20070709</NTANF>
<NTANZ>000000</NTANZ>
<NTEND>20070709</NTEND>
<NTENZ>000000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000000</ISDZ>
<IEDD>00000000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
<E1EDT13 SEGMENT="1">
<QUALF>010</QUALF>
<NTANF>20070705</NTANF>
<NTANZ>000000</NTANZ>
<NTEND>20705</NTEND>
<NTENZ>000000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000000</ISDZ>
<IEDD>00000000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
<E1EDL28 SEGMENT="1">
<ROUTE>ED545S1</ROUTE>
<DISTZ>0.000</DISTZ>
<E1EDL29 SEGMENT="1">
<ROUTE_BEZ>FKLSDJFLSJDFJSDFJLSDJFLKSD</ROUTE_BEZ>
</E1EDL29>
</E1EDL28>
<E1EDL24 SEGMENT="1">
<POSNR>000010</POSNR>
<MATNR>000000000000</MATNR>
<MATWA>000000000</MATWA>
<ARKTX>OmFDFS 2kg.</ARKTX>
<MATKL>FSD5345FSDFLAUND</MATKL>
<WERKS>10FDF40</WERKS>
<LGORT>01</LGORT>
<LFIMG>10545.000</LFIMG>
<VRKME>C54T</VRKME>
<LGMNG>10553545.000</LGMNG>
<MEINS>CT534555345545345</MEINS>
<NTGEW>1653454.000</NTGEW>
<BRGEW>181.000</BRGEW>
<GEWEI>KGM</GEWEI>
<VOLUM>450.190</VOLUM>
<VOLEH>DMQ</VOLEH>
<LADGR>0534543002</LADGR>
<TRAGR>0001</TRAGR>
<VKBUR>UF53401</VKBUR>
<VKGRP>160</VKGRP>
<VTWEG>00</VTWEG>
<SPART>00</SPART>
<GRKOR>000</GRKOR>
<EAN11>16001085031034</EAN11>
<POSEX>000000</POSEX>
<E1EDL25 SEGMENT="1">
<LGORT_BEZ>Main s53453453454tore</LGORT_BEZ>
<LADGR_BEZ>Forklift</LADGR_BEZ>
<TRAGR_BEZ>On pallets</TRAGR_BEZ>
<VKBUR_BEZ>Gener534534al Trade</VKBUR_BEZ>
<VKGRP_BEZ>RSM E534 Cape</VKGRP_BEZ>
<VTWEG_BEZ>FKLSDFKLS</VTWEG_BEZ>
<SPART_BEZ>FSDFSDFJoducts</SPART_BEZ>
</E1EDL25>
<E1EDL26 SEGMENT="1">
<PSTYV>TAN</PSTYV>
<MATKL>FGUND</MATKL>
<PRODH>0125VH</PRODH>
<UMVKZ>1</UMVKZ>
<UMVKN>1</UMVKN>
<KZTLF>B</KZTLF>
<UEBTO>0.0</UEBTO>
<UNTTO>0.0</UNTTO>
<KVGR1>Z4FDFSDFSD</KVGR1>
<KVGR2>TPS</KVGR2>
<E1EDL27 SEGMENT="1">
<PSTYV_BEZ>Standard Item</PSTYV_BEZ>
<PRODH_BEZ>OmoFFD Regular 8X2kg.</PRODH_BEZ>
<WERKS_BEZ>ConFSDFgella DC</WERKS_BEZ>
<KVGR1_BEZ>PE Cust Del</KVGR1_BEZ>
<KVGR2_BEZ>rd party sales</KVGR2_BEZ>
</E1EDL27>
</E1EDL26>
<E1EDL43 SEGMENT="1">
<QUALF>C</QUALF>
<BELNR>FDF</BELNR>
<POSNR>000010</POSNR>
<DATUM>FFSDF</DATUM>
</E1EDL43>
<E1EDL41 SEGMENT="1">
<QUALI>54</QUALI>
<BSTNR>test I Link</BSTNR>
<BSTDT>00000000</BSTDT>
<POSEX>000010</POSEX>
</E1EDL41>
</E1EDL24>
</E1EDL20>
</IDOC>
</DELVRY01>not related
-
Converting QoS from EO to EOIO in Receiver JMS Adapter
Hello All -
We are currently working with SAP XI 3.0 SP12. Our scenario is something like this:
IDoc -> XI (BPM) -> JMS Adapter
The BPM splits up the incoming IDoc into multiple JMS messages.
The problem is that when the BPM sends the message to the JMS adapter the QoS changes from EOIO to EO. This essentially means that when the messages are written to the JMS Queues, there is no gurantee that they would be written in exactly the same order in which they are produced.
The requirement is to write the messages in exactly the same order in the target queues.
One solution is to capture the transport level acknoledgements and then send the next message from the BPM only on the receipt of the acknoledgement which takes a lot of time.
Is there any other mechanism to ensure the messages going out in an EOIO fashion.
AshishIts like this , i ve file -> bpm -> idoc scenario. 've configured EOIO as the QOS for both adapters. file adapter is configured to pick up a pattern , say *.abc.
The picking option is "By Date". Say there are 5 files in the directory before a particular polling interval which has about 5 sec time delay b/w them in their timestamp.
Now the file adpater picks the files in order , delivers it to ccBPM, i can see 5 diff ccBPM instances(diff workitem IDs).
Say, the third file has less data , the transformation happens faster in the 3rd ccBPM instance and so it delivers it to the idoc adapter vefore the 1st or 2nd one completes. So my order is lost.
Now , i tried setting "transport ack" in send step , but didnt help.Is there any other specific setting to be done ?
Thanks
Saravana
Maybe you are looking for
-
Another Safari "Quits" Problem. Error Code Enclosed.
Process: Safari [467] Path: /Applications/Safari.app/Contents/MacOS/Safari Identifier: com.apple.Safari Version: 8.0.2 (10600.2.5) Build Info: WebBrowser-7600002005000000~1 Code Type: X86-64 (Nat
-
Has FM 9 or 10 a better working dictionary for non-english languages?
I am using FM 7 (latest update) on Windows Vista. As it is now, there's a limit of how many characters a word can have for it to be entered into the dictionary. We here in Sweden have 3 letters that are not present in the English language, å, ä and ö
-
Has anyone had experience with these 2.5 IDE enlosures...?
Hello, Has anyone had any experience with 2.5 " HD enclosures as seen on site like ebay for a buck...it says ts only wnodows based but its USB right? Super slim 2.5 inch USB2.0/1.1 Aluminium Hard Disk Drive Case/Enclosure transfer-rate of up to 480 M
-
HT201303 Hi, I forgot my security questions. how to get back.thx
Hi, I forgot my security questions. how to get back.thx
-
Foreign JMS Connectiing to MQ Series
Hi All, Our client complians that, Everytime Foreign JMS Server is deployed on Server, it open 13 connections to MQ Queue. I believe that single JMSConnection is open and connected to Message producer and that creates JMSSessions. Then what