| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SAP IDOC PAssthrough Issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| jbanoop |
 Posted: Fri May 21, 2010 11:24 am Post subject: SAP IDOC PAssthrough Issue |
 |
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
All,
Env: WMB 7.0, toolkit: 7.0.0 IFIX2, WinXP SP3
I have configured the SAPInput node in ALE Passthrough mode and am receiving the IDOC as BLOB from the SAP system.
The flow is extracting the BLOB IDOC content and sending it to a particular queue (using code given in the pattern sample).
Now, as documented in the help, I am setting the parse options on the MQInput node reading out of the queue to DataObject, the msgset name and selecting SAP ALE IDOC in the message format.
However, when it is trying to parse the message, the following error is thrown:
| Code: |
| com.ibm.j2ca.sap.ale.inbound.exception.SAPAleInboundException: getAccessor called for non existent accessor: Cursor = SapIDocControlRecord, accessor = EXPRESS\r\ngetAccessor called for non existent accessor: Cursor = SapIDocControlRecord, accessor = EXPRESS\r\ngetAccessor called for non existent accessor: Cursor = SapIDocControlRecord, accessor = EXPRESS\r\n |
I read through a similar post http://www.mqseries.net/phpBB2/viewtopic.php?t=48780&view=next&sid=e76d5e3bbba7d24b08ab2e99e6a9d531
and I understand that it was caused by some fields missing in the control segment.
However, this message set that I am using was generated by the SAP Node adapter component itself and works perfectly when used directly on the adapter component (in case of parsed option).
Any thoughts on what I might be missing would be really appriciated.
I was also wondering if anyone of you have already used this pattern successfuly in V7.
Regards, |
|
| Back to top |
|
 |
| jbanoop |
| Posted: Fri May 21, 2010 12:13 pm Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
The IDOC control segment content in the parsed mode is :
| Code: |
<SapIDocControlRecord>
<RCVPOR>A000000005</RCVPOR>
<SNDPRT>LS</SNDPRT>
<SNDPFC></SNDPFC>
<TEST></TEST>
<MESCOD></MESCOD>
<IDOCTYP>SHP_IBDLV_SAVE_REPLICA04</IDOCTYP>
<SNDPRN>SE1CLNT100</SNDPRN>
<STD></STD>
<ARCKEY></ARCKEY>
<CRETIM>193112</CRETIM>
<DOCTYP></DOCTYP>
<TABNAM>EDI_DC40</TABNAM>
<CREDAT>20100521</CREDAT>
<REFGRP></REFGRP>
<OUTMOD>2</OUTMOD>
<MANDT>100</MANDT>
<RCVSAD></RCVSAD>
<MESTYP>SHP_IBDLV_SAVE_REPLICA</MESTYP>
<RCVPRN>DIRSD008</RCVPRN>
<STDVRS></STDVRS>
<RCVLAD></RCVLAD>
<DIRECT>1</DIRECT>
<SNDLAD></SNDLAD>
<EXPRSS></EXPRSS>
<SNDSAD></SNDSAD>
<DOCREL>701</DOCREL>
<SERIAL>20100405174855</SERIAL>
<SNDPOR>SAPSE1</SNDPOR>
<DOCNUM>0000000000012266</DOCNUM>
<STDMES>SHP_IB</STDMES>
<REFINT></REFINT>
<RCVPFC></RCVPFC>
<REFMES></REFMES>
<MESFCT></MESFCT>
<CIMTYP></CIMTYP>
<STATUS>30</STATUS>
<RCVPRT>LS</RCVPRT>
</SapIDocControlRecord> |
|
|
| Back to top |
|
|
| jbanoop |
| Posted: Wed May 26, 2010 11:08 am Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
Just to close the thread, I got it to work finally. Leaving all settings to default while creating the message set using ESD is the way to go I guess.
Wehen options such as 'creating field names based on SAP field descriptions' and such were selected, that apparently was causing the issues.
Not yet sure what exactly the issue was but leaving all settings to default values seems to work. |
|
| Back to top |
|
|
| whydieanut |
| Posted: Tue Nov 08, 2011 3:23 am Post subject: |
|
|
Disciple
Joined: 02 Apr 2010
Posts: 186
|
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
