| Author |
Message
|
| huebi |
 Posted: Mon Jul 02, 2001 10:58 pm Post subject: |
 |
|
Novice
Joined: 01 Jul 2001
Posts: 16
|
Does anyone has experience with MQLink/MQSI/SA IDoc Technology ? How do you deal with variable message length in MQSI? The length of an IDoc is unpredictable?
I'm using MQSI on AIX. I do know the SupportPac IA0F, but this is restricted to MQSI on NT.
cu
huebi |
|
| Back to top |
|
 |
| mpuetz |
| Posted: Fri Jul 06, 2001 1:45 am Post subject: |
|
|
Centurion
Joined: 05 Jul 2001
Posts: 149
Location: IBM/Central WebSphere Services
|
Hi,
I had the same trouble with IDOCs. The IDOC Parser plugin works well (under NT), but I couldn't get a timely commitment for an AIX version of it. Thus I wrote two parser subflows in ESQL which parse and construct any Version 4 IDOCs.
It uses similar techniques as the IDOC Parser Plugin (The docs of this plugin are a must read) and you must import the SAP generated C-headers into MRM and define MRM messages for each IDOC segment and the segment headers you plan to use.
I will wrap this up for anyone in need and post a web address where you can download the flows by the end of next week.
Cheers,
Mathias
|
|
| Back to top |
|
|
| Armin |
| Posted: Fri Aug 17, 2001 5:45 am Post subject: |
|
|
Novice
Joined: 24 Jul 2001
Posts: 15
Location: Germany
|
Is this webpage already existing?
I have to generate IDOCs with repeating segments and the repeat-count is not fix.
Armin |
|
| Back to top |
|
|
| jhalstead |
| Posted: Mon Aug 20, 2001 1:23 am Post subject: |
|
|
Master
Joined: 16 Aug 2001
Posts: 258
Location: London
|
Another option is to use NEON adapter manager, this will extract the SAP IDoc meta data and allow the use of the complementary NEON components.
In version 2.0.2 information in the NEON domain is available for interaction with ESQL.
|
|
| Back to top |
|
|
| samimohd |
| Posted: Thu Apr 11, 2002 3:07 am Post subject: |
|
|
Novice
Joined: 25 Mar 2002
Posts: 21
|
Are you using MQ Link for R/3 ?. Every SAP IDOC is has the following structure:
One Control record and multiple repeated segments. Control record is always 524 bytes and each segment is 1063 bytes. I recommend using NEON formatter for in combination with R/3 link. When you download the formats through NEON adapter manager, it creates for you the whole idoc format exactly as the SAP IDOC and total length fields of control record will be 524 bytes and segments will be 1030 bytes.So it is short by 33 bytes. Yuo should add filler of 33 bytes to each sgement of the neon idoc format. So when the idoc comes from sap, even thoough there are only couple of segments and ony couple of fields are used, the formatter takes care of this as long as as the total length of the formatter fields of a segment is 1063. I hope this info is helpful. Let me know if you need more assistance. Or you can send me a note at mohammed@us.ibm.com. |
|
| Back to top |
|
|
|
|
