JMS adapter appears on wrong side in the BPEL

JDeveloper 11g (11.1.1.5.0)
I drag & drop a JMS adapter(for enqueue) on the right swim lane of composite, and wired a BPEL with it.
However when I open the BPEL, the JMS adapter appears on the left side of the Partner links, not
the right side. What's wrong? and How to fix it? Thanks.

Hi,
It has to do with the operation type that you select when you're configuring the JMS adapter...
Cheers,
Vlad
Give points - it is good etiquette to reward an answerer points (5 - helpful; 10 - correct) for their post if they answer your question
https://forums.oracle.com/forums/ann.jspa?annID=330

Similar Messages

JMS Adapter Configuration at reciver side

Hi,
Actaully I have to configure JMS adapter HAving Content Conversion.
I m getting XML throuh XI and wan to convert it to TEXT File.
Can anyone tell me wat MODULE NAME, TYPE, MODULE Key , PARAmeter NAMe and VAlue i have to take.
Hemant

Hi,
Take a look at this document,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
Regards,
Bhavesh

Created path and used trim but the line appears from the wrong side?

Hey,
I've created a rectangle by using the pen tool, then applied a stroke to it. I've then added "trim paths" and the end value at 0seconds is 0% and then at 5 seconds its at 100% however the line appears from the wrong side of the screen, basically it's reversed, yet the reverse path symbol is not ticked.
The line is meant to appear from left to right of the screen with a 2px stroke, which will then have a mask applied to show a large black box appear from this line and fill the rest of the screen up.
Anyone able to help me at all?
Thank you.

If you animated the start then animate the end. Simple as that.

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
Ravijeet

Hi 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

Configuring JMS adapter for a BPEL process which puts a msg in a Q of MQ

Hi,
I am trying to develop a BPEL process which picks up a message from a Q in Websphere MQ and puts that message in another Q of MQ after processing that.
I have updated the oc4j-ra.xml with the following inputs:
<connector-factory location="eis/MQSeries/Queue" connector-name="Jms Adapter">
          <config-property name="connectionFactoryLocation" value="com.ibm.mq.jms.MQQueueConnectionFactory"/>
          <config-property name="factoryProperties" value="QueueManager=TestManager;TransportType=1;Hostname=machine's ip address;Port=1414;Channel=channel name for connecting to client"/>
          <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
          <config-property name="isTopic" value="false"/>
          <config-property name="isTransacted" value="true"/>
          <config-property name="username" value="admin"/>
          <config-property name="password" value="welcome"/>
     </connector-factory>
But while testing the BPEL process, I get the error:
<remoteFault>
<part name="code" >
<code>null</code>
</part>
<part name="summary" >
<summary>file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Adapter Framework unable to create outbound JCA connection. file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141 ERRJMS_CONN_FAC_NOT_FOUND. Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor com.ibm.mq.jms.MQQueueConnectionFactory neither through JNDI nor instantiate it as a Java class Please examine the log file to determine the problem. ; nested exception is: ORABPEL-12511 Adapter Framework unable to create outbound JCA connection. file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141 ERRJMS_CONN_FAC_NOT_FOUND. Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor com.ibm.mq.jms.MQQueueConnectionFactory neither through JNDI nor instantiate it as a Java class Please examine the log file to determine the problem. Please examine the log file for any reasons. Enable DEBUG logging in the BPEL Console. </summary>
</part>
<part name="detail" >
<detail>null</detail>
</part>
</remoteFault>
Can anyone tell me what has gone wrong in setting the connection factory for the Q or what else I have to configure to sort out this problem?
Thanks,
Jayatu

I am experiencing the exact same issue while configuring for Tibco EMS!!!
I have also checked the oc4j-xa.xml file etc and I am also unable to find any guidance on the steps required from XML config files through to adapter wizard entries!

Error in JMS Adapter:

Receiving the below error, thought of JMS Drivers problems undeployed and re-deployed several times, but still problem persist in XI.
Success     MP: Processing local module localejbs/SAP XI JMS Adapter/ConvertMessageToBinary
2010-09-09 11:45:21     Error     MP: Exception caught with cause com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.
2010-09-09 11:45:21     Error     Exception caught by adapter framework: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.
Error     Delivery of the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary..
2010-09-09 11:45:22     Success     The message status set to WAIT.
2010-09-09 11:45:22     Success     The asynchronous message was successfully scheduled to be delivered at Thu Sep 09 11:50:21 CDT 2010.
The JNDI Libraries are available in Visual Admin, not sure what else causing the issue. Any guru's help is appreciated

XI 3.0 SP20
Regarding the note, that only applied below sp4. We are on SP20. The default values appears but those are not working.This seems to be a problem with Dev only, Q and P is working fine at this moment
If i actually delete module processor's from Sender and Receiver channel, things are working fine. But not sure if it is going to break anything. And this needs to be applied in all landscape. But i have to present a reason, why this weird behavior all of a sudden
Sender
    SAP XI JMS Adapter/ConvertJMSMessageToBinary
    SAP XI JMS Adapter/ConvertBinaryToXMBMessage
Receiver
    SAP XI JMS Adapter/ConvertMessageToBinary
    SAP XI JMS Adapter/SendBinarytoXIJMSService

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

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

PI unable to connect via JMS adapter to Weblogic

Hello All,
We have implemented JMS adapter on PI 7.11 for the first time in our landscape which connects to Weblogic server. When i test my scenario i get this Error on JMS Communication Channel. Could some one help me out .. where things are going wrong?
Am using Transport protocol as : Access JMS Provider with JNDI
CASE 1 :
284272 A channel error occurred. The detailed error (if any) : com.sap.aii.adapter.jms.api.connector.ConnectorException: Error creating initial context with
environment: {java.naming.provider.url=t3s://usdatlpc64m----
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory}for profile: ConnectionProfile of channel: JMS_RCV_IA_WorkOrderStatuson node: 28427250 having object id: 035dd91446303f17bf0e7ad9a4dbd564: RuntimeException: Exception occurred while reading the license file.<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:65)<br> ...
CASE2:
A channel error occurred. The detailed error (if any) : com.sap.aii.adapter.jms.api.connector.ConnectorException: Error creating initial context with environment: {java.naming.provider.url=----
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory}for profile: ConnectionProfile of channel: JMS_RCV_IA_WorkOrderStatuson node: 28427251 having object id: 035dd91446303f17bf0e7ad9a4dbd564: javax.naming.NamingException: String index out of range: -1<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:65)<br> ...

Hi ,
Were you able to resolve the issue?
We are facing similar issue when trying to integrate (SOAP over JMS) with WebSphere 7.x server to read JMS messages. We are using SAP PI 7.1 version and after providing the JNDI connection factory as "com.ibm.websphere.naming.WsnInitialContextFactory".....the error returned is :
======
Channel error occurred. Detailed error (if any) : com.sap.aii.adapter.jms.api.connector.ConnectorException: Error creating initial context with environment: {java.naming.provider.url=iiop://10.60.5.115:2809, java.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory, java.naming.security.principal=admin, java.naming.security.credentials=admin}for profile: ConnectionProfile of channel: JMSSender_MESon node: 8649950 having object id: a8c808c859f33b40a41d0ced2088fb18: javax.naming.NoInitialContextException: Cannot instantiate class: com.ibm.websphere.naming.WsnInitialContextFactory<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:65)<br> ...
=====
Thanks in Advance
-Naveen

Calling Foreign JMS in SOA Suite 11g JMS Adapter

Hi,
Just want to get some guidance in the implementation of Foreign JMS in WebLogic 10.3.
I followed the creation of the Foreign JMS Server using this document:
http://download.oracle.com/docs/cd/E12839_01/apirefs.1111/e13952/taskhelp/jms_modules/foreign_servers/CreateForeignServers.html
I am trying to connect to a remote Weblogic 10.3 JMS queue but cannot get pass the JDev wizard stage.
I need to call the foreign JMS via the Fusion 11g JMS Adapter but cannot lookup the destination from the JDev wizard. My composite will produce a message that will end up in the remote queue.
Has anybody got this to work? Is this supported in JMS Adapter? I've read quite a few using MDB to call the Foreign JMS but not JMS Adapter.
Regards,
Robert

Please refer to the following document that shows how to access remote wls jms queues and topics. This is the preferred way when accessing remote wls destinations.
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10231/adptr_jms.htm#BABJACJA
Thanks
Aman

Invoking Jms Adapter from BPEL with enque stoped

Hi guys, I have an issue.
In my BPEL flowI have an invoke activity which has a jms adapter as a partner link.
The thing is that if you stop the enque in the DB, your flow in BPEL continues like nothing happened. It just passes the payload to the jms adapter. From it's point of view is asynchronous , but I want to make sure that the payload is in the queue before I continue the flow.
Any ideas?

Hi Oracler,
I don't understand what you mean by XML schema inline? Where do you define that in a JMS adapter ? Can you be more specfic when you say Try including both the elements(TEXT_LOB , TEXT_VC ) in the schema? I don't have those elements in my schema at all. I have tried the opaque option I still get the same Translator NULL error.
Please anyone help....

ORABPEL-12141 JMS Adapter

BPEL 10.1.2.0.2 Deployed on OAS on Linux OS.
Trying to use a BPEL Process which is trying to Connect to JMS on Weblogic Server but getting error as below in the domain.log
Added the weblogic.jar in the application.xml under integration/orabpel/system/appserver/oc4j/j2ee/home/config/application.xml
Entry added : <library path="/home/bpel/weblogic/server/lib/weblogic.jar"/>
XML file entry for JMS Adapter in BPEL :-
<connector-factory location="eis/jms/topic/rdh/Notification" connector-name="Jms Adapter">
<config-property name="connectionFactoryLocation" value="oracle.enterprise.crm.rdh.jms.connection.factory"/>
<config-property name="factoryProperties" value="java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://MYMACHINE:7050"/>
<config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
<config-property name="isTopic" value="true"/>
<config-property name="isTransacted" value="false"/>
<config-property name="username" value=""/>
<config-property name="password" value=""/>
</connector-factory>
Portion of Domain.log file :-
<2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: JNDI Naming exception when looking up oracle.enterprise.crm.rdh.jms.connection.factory: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory
<2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: Will now try to determine if the 'ConnectionFactoryLocation' oracle.enterprise.crm.rdh.jms.connection.factory is a loadable Java class. If so, the above exception can be ignored.
<2007-08-17 03:25:29,148> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> Error while creating managed connection:
<2007-08-17 03:25:29,150> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound>
ORABPEL-12141
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor oracle.enterprise.crm.rdh.jms.connection.factory neither through JNDI nor instantiate it as a Java class
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:206)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getTopicConnectionFactory(JMSConnectionFactoryFactory.java:109)
at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:123)
at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:107)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:365)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConnectionFactory.java:356)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:319)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:101)
at oracle.tip.adapter.jms.JmsDefaultConnectionManager.allocateConnection(JmsDefaultConnectionManager.java:76)
at oracle.tip.adapter.jms.JmsConnectionFactory.getConnection(JmsConnectionFactory.java:94)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:201)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:158)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:115)
at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:113)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
at java.lang.Thread.run(Thread.java:534)
Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:652)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.java:186)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:133)
... 16 more
Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
at com.evermind.naming.ContextClassLoader.findClass(ContextClassLoader.java:318)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at com.evermind.naming.ContextClassLoader.loadClass(ContextClassLoader.java:143)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.evermind.server.ApplicationContextClassLoader.findClass(ApplicationContextClassLoader.java:19)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:649)
... 21 more

BPEL 10.1.2.0.2 Deployed on OAS on Linux OS.
Trying to use a BPEL Process which is trying to Connect to JMS on Weblogic Server but getting error as below in the domain.log
Added the weblogic.jar in the application.xml under integration/orabpel/system/appserver/oc4j/j2ee/home/config/application.xml
Entry added : <library path="/home/bpel/weblogic/server/lib/weblogic.jar"/>
XML file entry for JMS Adapter in BPEL :-
<connector-factory location="eis/jms/topic/rdh/Notification" connector-name="Jms Adapter">
<config-property name="connectionFactoryLocation" value="oracle.enterprise.crm.rdh.jms.connection.factory"/>
<config-property name="factoryProperties" value="java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://MYMACHINE:7050"/>
<config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
<config-property name="isTopic" value="true"/>
<config-property name="isTransacted" value="false"/>
<config-property name="username" value=""/>
<config-property name="password" value=""/>
</connector-factory>
Portion of Domain.log file :-
<2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: JNDI Naming exception when looking up oracle.enterprise.crm.rdh.jms.connection.factory: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory
<2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: Will now try to determine if the 'ConnectionFactoryLocation' oracle.enterprise.crm.rdh.jms.connection.factory is a loadable Java class. If so, the above exception can be ignored.
<2007-08-17 03:25:29,148> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> Error while creating managed connection:
<2007-08-17 03:25:29,150> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound>
ORABPEL-12141
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor oracle.enterprise.crm.rdh.jms.connection.factory neither through JNDI nor instantiate it as a Java class
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:206)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getTopicConnectionFactory(JMSConnectionFactoryFactory.java:109)
at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:123)
at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:107)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:365)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConnectionFactory.java:356)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:319)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:101)
at oracle.tip.adapter.jms.JmsDefaultConnectionManager.allocateConnection(JmsDefaultConnectionManager.java:76)
at oracle.tip.adapter.jms.JmsConnectionFactory.getConnection(JmsConnectionFactory.java:94)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:201)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:158)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:115)
at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:113)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
at java.lang.Thread.run(Thread.java:534)
Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:652)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.java:186)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:133)
... 16 more
Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
at com.evermind.naming.ContextClassLoader.findClass(ContextClassLoader.java:318)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at com.evermind.naming.ContextClassLoader.loadClass(ContextClassLoader.java:143)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.evermind.server.ApplicationContextClassLoader.findClass(ApplicationContextClassLoader.java:19)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:649)
... 21 more

Problem with JMS Adapter after upgrade to 7.1

Hi All,
After an upgrade the JMS adapter connecting IBM Websphere MQ gives the following error:
Error connecting due to missing class: com.ibm.mq.jms.MQQueueConnectionFactory. Ensure that all resources required are present in the JMS provider library: aii_af_jmsproviderlib.sda
Since we are now on PI 7.1, the directory the JMS adapter should be looking for the libraries should be com.sap.aii.adapter.lib.sda. Has anyone else come across this problem after an upgrade? Should we remove the old aii_af_jmsproviderlib.sda?
Edited by: Luqman on Oct 31, 2008 5:39 PM

does following JAR files in place in aii_af_jmsproviderlib.sda.
●      com.ibm.mq.jar
●      com.ibm.mqbind.jar
●      com.ibm.mqjms.jar
●      connector.jar (use the JAR file from the J2EE client directory)
can u check n confirm.
i hopw u have followed the proper deployement process.
chirag

Getting PO account assignment on both sides of the GR/IR accounting doc.

When the GR/IR accounting document is created in our system for a PO item that is account assigned to an order, network or cost centre, the following occurs. On the Goods Receipt, the GR/IR account does not capture the cost assignment on the GR/IR posting. On the Invoice Receipt, the GR/IR account posting does include the cost assignment on the GR/IR posting.
For Example:
MIGO posting generates this accounting entry
Debit Expense account, Order 12xxxxxx          $100
Credit GR/IR account                                          $100     (no order on GR/IR line)
MIRO
Credit Vendor                                                    $100
Debit GR/IR account, Order 12xxxxxx              $100 (order is posted with GR/IR line)
Although the GR/IR account is a balance sheet account, is it useful, for a reporting task, to have the cost assignment included in the financial posting for both GRu2019s and IRs, but it only appears on the IR side.
Is this something that can be solved by MM configuration?
Comparing posting keys 86 (IR) with posting key 96 (GR) u2013 the cost objects we used are set as optional for both those keys, so it doesnu2019t appear to be posting key configuration.
Note: When the PO item is assigned to a material (GR to inventory) the material appears on both sides of the GR/IR postings in Accounting, which is what we want for items account assigned to orders, networks, and cost center too.
Thank you. Alvin.

Thanks, but we still get the account assignment posted to GRIR during MIRO (as shown in Alvin's original post) so the full explanation cannot be the fact that GRIR is a balance account.
Essentially, we would like GR and IR-events to pass the same account assignment string to GR/IR, except posting key.
Thanks for helping.

JMS adapter: Adapter specific message attributes

Hi,
I have a synchronous SOAP to JMS (MQ series) scenario where Im using sync/async bridge (without BPM).
I need to correlate the message being put on JMS queue (JMS receiver adapter) and the response (JMS sender adapter).
The standard receiver JMS adapter only allows the JMS correlation ID to be set to one of three different values (excluding NULL). 2 of these (reference and conversation ID) will be empty in my scenario, leaving me with only the XI message ID. This ID however exceeds the length of ie. the JMS correlation ID and thus isnt suitable for correlating anything using the field JMS Correlation ID.
NB: it is of no use to try and set the conversation ID at mapping time (using container object) since the changed value only is available during mapping execution.
Surely one way of setting the conversation ID would be to use an adapter module in SOAP sender, but this is not an option. Also the sender system will not provide one either.
Now the problem isnt setting the JMS correlation ID dynamically at runtime (this is achieved without trouble using the dynamic configuration API with the key DCJMSCorreleationID). The problem is to actually have XI correlate the request with the response.
Since the JMS collelation ID is smaller than the XI message ID and the conversation and reference ID isnt available, what I figure is that I need to find a MQ message property to use and then use the Set MSProperty to part instead this property surely needs to be large enough to contain the XI message ID.
So what I did was I looked in http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.amqwak.doc/js50938.htm
where a list of fields in the message descriptor is available figuring I can just use one of these. Looking through the list I notice the field MDRQ (Name of reply queue, 48-byte character string) should be able to hold the XI message ID. So I add MDQR in the Specify additional JMS message properties and set the Java Type to String and also enter this field in the Correlation Setting of the receiver JMS adapter.
Runtime:
When looking in MDT I see:
New JMS message will be correlated with the XI message. Correlation rule: XI_MESSAGEID, correlated property: JMS property MDRM, correlation value: 36158680-5a0c-11dc-8c14-000f203cd3c8
I looks like a success! No data is however set in the field when looking at messages being put on MQ.
If I increase the trace level of the JMS adapter I can see (in defaultTrace) the following:
Cannot read the switch setting for property name DCJMSStringProperty0, switch name dynConfigDCJMSStringProperty0. It is switched off.
What does this error mean?
I have of course clicked Use adapter Specific Message-Attributes and also the Specify additional. In other words everything look ok in configuration.
Since Ive also put a check mark in Fail if adapter specific message attributes is missing I can see that I successfully put a value (using dynamic conf. at mapping time) in the field... but still something isnt right the value of the property never reached MQ.
Now Ive tried with a couple of fields in the message descriptor from the previous URL. XI complains all the time.
Anybody got some ideas?
Best Regards,
Daniel

Hi Vijay,
Thanks for your replay,as per your input i creted dynamic configuration method,
i taget structure luks like this
   <Data>
       <Mesage>
             <gl_update>
                  <header>
                        <ean1>
                        <ean2>
                  </header>
              <gl_update>
       <Message>
i written UDF and mapped to header element gl_update,
but i am getting below error message in MONI
SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_ ffjms_</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ns0:MT_jms_ _a</SAP:P3>
<SAP:P4>sync_out/Data/Message/ GLUpdate. Values missi~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_ ffjms_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:MT_jms_ asyncout/Data/Message/ GLUpdate. Values missi~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
i want to know i mapped to UDF to GL_Update is is correct, to which element i have to map.
i think there is no prob with UDF,its executing ,giving warning messages
help me on this,
Regaards
Raj

JMS adapter appears on wrong side in the BPEL

Similar Messages

Maybe you are looking for