| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MRM - How to parse a file IDOC - MB 7 |
« View previous topic :: View next topic » |
| Author |
Message
|
| jbanoop |
 Posted: Wed Jun 16, 2010 11:50 am Post subject: MRM - How to parse a file IDOC - MB 7 |
 |
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
All,
I am back with an IDOC parsing question.
Problem: Need to parse File IDOC(s) using WMB 7.0 with MRM or DataObject or any other means.
An exercpt from the following article http://www.ibm.com/developerworks/websphere/library/techarticles/0810_hanson/0810_hanson.html
pasted below indicates that this is supported. However I have tried multiple times without success.
I did everything as mentioned below. The DC is getting parsed and the first DD is also parsing. However it is still looking for 1063 bytes of data although while importing the C header file I selected the preprocessing step as "file IDOC". There is also painfully little documentation surrounding file IDOCs with WMB.
I was hoping someone could point me in the right direction.
| Quote: |
MRM TDS now has all the capability to parse both ALE and File IDocs. In WebSphere Message Broker V6.1, it is recommended that text IDocs sent from the WebSphere MQ Link for R/3 or exported to the file system are parsed using MRM TDS. The IDOC domain is officially deprecated. Note that, IDocs received as business objects from the new WebSphere Adapter for SAP should be handled by the new DataObject domain.
The procedure for modeling SAP text IDocs is now:
Import a pre-built TDS model of an IDoc DC/DD into your message set using the New Message Definition File From ... IBM Supplied Message wizard. There are pre-built models for ALE and File flavours. This will create a TDS physical format called Text_IDoc if none exists.
Ensure your TDS physical format has Messaging Standard property set to User Defined Text.
Import the user structure C header files using the New Message Definition File From ... C wizard, and select the new option for ALE or File IDocs. No pre-processing is needed, as the IA0F utility logic is now in the wizard. The user structures are linked to the DD using MRM multipart messaging.
Conveniently, the default TDS model created by the C importer correctly models the user structure without any manual editing, because IDoc data is all fixed length strings.
|
Regards,
Anoop[/url] |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Wed Jun 16, 2010 11:57 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
I will go for DataObject, thats quite easy to do.
hope you have done the following tasks:
Discovered the business object from SAP using the SAP Adapters and even the adapter component is also created once you discovered the business object.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| jbanoop |
| Posted: Wed Jun 16, 2010 12:08 pm Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
Gaya3,
I am talking about file delimited IDOCs. The DataObject and the enterprise service discovery you have mentioned deal with ALE R3 Link format which is a different format.
I am specifically asking about the parsing of IDOCs in the "Flat" format. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jun 16, 2010 8:00 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| jbanoop wrote: |
Gaya3,
I am talking about file delimited IDOCs. The DataObject and the enterprise service discovery you have mentioned deal with ALE R3 Link format which is a different format.
I am specifically asking about the parsing of IDOCs in the "Flat" format. |
Take a preprocessing step with the EDI_DC40 and EDI_DD40 formats.
You can then read a line of text and assign it to either one of those formats.
A collector node can collect all records for a same idoc and create the final message, alternatively you could achieve that with a group identifier...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jbanoop |
| Posted: Thu Jun 17, 2010 5:54 am Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
fjb_saper,
Thanks for the suggestion.
We have multiple IDOC types for which we would have to process these file IDOCs. So I was looking at something that is created using standard message broker features that could be used across the whole project with no/minimal customization.
How are others parsing flat IDOCs using WMB ? Does the mySAP adapter support the parsing of flat IDOCs ?
Regards, |
|
| 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
|
|
|
|
