| Author |
Message
|
| sebastian |
 Posted: Thu Sep 02, 2004 5:03 am Post subject: Using v2.1 Message sets for reading/writing SAP IDOCS |
 |
|
Centurion
Joined: 12 Nov 2003
Posts: 110
Location: Philadelphia
|
Has anyone successfully used the v2.1 Message sets to read and write SAP IDOCS? Our shop uses Neon transform nodes whenever we have message flows connect to SAP IDOCS. We are trying to use message sets instead but have not been successful. We run into problems when a nested child segment is defined as optional-repeating. Is the MRM capable of defining nested segment types as optional-repeating?
I would be very interested in hearing from any v2.1 developers who have created flows connecting to SAP IDOCS. Is there any documentation for creating message sets specifically for IDOCS? What CSD level are you using? Are you using Neon? Have you been able to create functioning message sets? Is some adapter the better option? If so, which adapter are you using?
Any feedback is greatly appreciated,
Sebastian
_________________
sebastian signature |
|
| Back to top |
|
 |
| chanduy9 |
| Posted: Thu Sep 02, 2004 5:25 am Post subject: |
|
|
Disciple
Joined: 28 Nov 2001
Posts: 177
Location: USA
|
Hi,
I did some SAP integration in couple of projects....we used SAP BC, NEON Adapter and SAP Adapter(WBIA)...
Creating messages sets for SAP IDOCs is really time consuming factor. So better to use some adapters.
Thanks,
Chandra. |
|
| Back to top |
|
|
| sebastian |
| Posted: Thu Sep 02, 2004 5:39 am Post subject: |
|
|
Centurion
Joined: 12 Nov 2003
Posts: 110
Location: Philadelphia
|
Thanks for the feedback. I spent a great deal of time creating message sets that do not seem to work. It would help if I could talk to someone who has actually done this successfully.
Have you ever worked with flows that use message sets instead of adapters to connect to SAP?
thanks again,
Seb
_________________
sebastian signature |
|
| Back to top |
|
|
| contactop |
| Posted: Thu Sep 02, 2004 5:55 am Post subject: |
|
|
Acolyte
Joined: 26 Jun 2003
Posts: 50
|
It would be very difficult if u create message set for an IDOC, so better use neon formatter, which would generate the message set and then u can use the same.
If any changes require din the messageset, do it in the neon formatter itself, as u cannot make changes to the message set from 2.1 . |
|
| Back to top |
|
|
| chanduy9 |
| Posted: Thu Sep 02, 2004 6:02 am Post subject: |
|
|
Disciple
Joined: 28 Nov 2001
Posts: 177
Location: USA
|
Hi,
I created Message set for IDOC in TDS format...but it is really time consuming....I think there is a support pac available.
Get the IDOC defination from SAP in (i think) C Header/XSD/DTD format..then create the message set using exported format.For me it took long time...but where as with any Adapeter it is fairly simple and easy.
Thanks,
Chandra. |
|
| Back to top |
|
|
| shanson |
| Posted: Thu Sep 02, 2004 6:20 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
IBM has a solution for this via supportpac IA0P but it is chargeable. It consists of a utility that runs against SAP to export the IDOCs you are interested in, then automatically creates the equivalent message set. It works for V2.1 and is being readied for V5.
I would definitely investigate this before you go the neonformatter route. In V5, neonformatter metadata is not visible from the broker toolkit.
If you have any questions about IA0P, e-mail dubadapt@ie.ibm.com |
|
| Back to top |
|
|
| sebastian |
| Posted: Thu Sep 02, 2004 6:38 am Post subject: |
|
|
Centurion
Joined: 12 Nov 2003
Posts: 110
Location: Philadelphia
|
Thanks for the input. We are trying to avoid the Neon route but our deadlines are forcing us to use this option until a better long term solution is found.
Has anyone used third party adapters to resolve similar issues?
If the adapter is just an automated method to create a message set usable for IDOC reading/writing, then it would be logical to assume that I should be able to create this manually regardless of the time and effort involved.
Seb
_________________
sebastian signature |
|
| Back to top |
|
|
| chanduy9 |
| Posted: Thu Sep 02, 2004 7:12 am Post subject: |
|
|
Disciple
Joined: 28 Nov 2001
Posts: 177
Location: USA
|
Hi,
You can use SAP BC, which gives you the XML out of IDOC....and SAP Adapter (WBIA) which gives you the BO out of IDOC which is also in the XML format...
Thanks,
Chandra. |
|
| Back to top |
|
|
| sebastian |
| Posted: Thu Sep 02, 2004 7:21 am Post subject: |
|
|
Centurion
Joined: 12 Nov 2003
Posts: 110
Location: Philadelphia
|
We receive and transmit all data to/from SAP via an R3 link. All of our data is text string with RFH headers.
Would this adapter still apply?
Seb
_________________
sebastian signature |
|
| Back to top |
|
|
| shanson |
| Posted: Thu Sep 02, 2004 7:26 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
The supportpac that Chandra mentioned (IA0F) is now part of the base broker product (from 2.1 CSD3 onwards). With this you extract the IDOCs as C structures and import them to create the message set. Then you specify 'IDOC' as the parser which invokes a separate IDOC parser that call the MRM (CWF) under the covers to do the donkey work.
So I would say you have 3 alternatives to New Era:
- Dublin SAP solution using MQ R3 link
- Broker built-in IDOC parser using MQ R3 link
- XML solution using WBI adapter |
|
| Back to top |
|
|
|
|
