Skip to Content
Exchange infrastructure may be implemented in many environments
where IDOC exchange between different SAP systems has been working
for a very long time. You can use XI with new scenarios but is it realy not worth
to update the old scenarios too?

1. What could we gain?

IDOC monitoring … is WE02/WE05 enough? Did you ever have to build your own,
custom monitoring transactions to monitor the IDOC flow? STOP that…
start using the Runtime Workbench.

2. You’re affraid it takes too much work to move your IDOC to IDOC scenarios?

You just have to create one object inside the Integration Repository – not even create,
just import the idoc definition – that’s all. Then you just have to do the standard
integration directory part.

3. You might be affraid that IDOC exchange through the XI will be slower
then without the use of the integration engine?

Have you heard about the IDOC to IDOC exchange without the XML conversion?

XI allows you to send IDOCs without changing them into XML messages.
If you don’t need to do the mapping within the XI you don’t have to.

How can you configure such a scenario?

Only one step:

– go to TCODE – SXMB_ADM

– Integration Engine configuration

– set the XML_CONVERSION parameter to value 2

Possible Values (from the Help)

a) 0 – Every IDoc is saved as a table; no IDoc-XML conversion

b) 1 – Every IDoc is converted to IDoc-XML

c) 2 – An IDoc is converted to IDoc-XML if requested by the service

image

Now when you configure and IDOC to IDOC flow without any mapping you’ll see that the tunelling feature is [ON].

image

The payload of your document won’t be application/xml cause when using this option IDOCs
are transported as tables and not as the XML messages.

image

Probably the IDOC exchange could even be a little bit faster if we could turn [OFF]
another IDOC parameter – SYNTAX_CHECK but since SAP does not recommend doing it this will not be a part of this weblog.

To report this post you need to login first.

11 Comments

You must be Logged on to comment or reply to a post.

  1. Hi Michal,

    one more good weblog from you. i am learning more IDOC from our weblog.

    Keep pouring…

    cheers,
    Naveen

    (0) 
  2. Hi Michal,

    According to your blog value 2 implies – “An IDoc is converted to IDoc-XML if requested by the service.”

    Can you please let us know where in the service we can specify this -> convert to IDOC-XML.

    Regards
    Sidharth

    (0) 
  3. Hi Michal,

    Can you explain more on using RWB instead of WE02/WE05. In the past, I have developed custom programs to display IDOC data meaningful to the user and for error-handling as business users always went crazy seeing the IDOC structure. This was more useful especially in handling application errors (for e.g. wrong material number).

    How do you think we can resolve this using RWB. Is it a wise choice for allowing business users (for e.g customer service) to access RWB?

    Thanks
    KK

    (0) 
  4. Jacob Ellsworth
    This was a good message which will help when I get ready to change our IDOC to IDOC scenarios to use XI. 
    I am wondering though, when you do this, do you still use the tRFC port in WE21 and a standard RFC R/3 connection in SM59?  I am trying to do this using the XML HTTP port and HTTP to R/3 System RFC.

    Thanks for this information,
    Jake

    (0) 
  5. Ulf Tilly

    <Trace level=”2″ type=”T”>Partytype = LS fallback to logical system</Trace> <br/>  <Trace level=”3″ type=”T”>Sender Interface</Trace> <br/>  <Trace level=”3″ type=”T”>ZDIVERSE.ZDIVERSE03 <br/>Hi,<br/>We have tried to set this XML_CONVERSION parameters but without success…<br/>We always get the payload in XML???<br/>Do you have any ideás?<br/>Do we need to reboot to take effect?<br/>/Regards Uffe<br/><br/><br/><br/><br/>urn:sap-com:document:sap:idoc:messages</Trace> <br/>  <Trace level=”1″ type=”T”>Syntax-Check-Flag X</Trace> <br/>  <Trace level=”1″ type=”T”>IDoc-Tunnel-Flag</Trace> <br/>  <Trace level=”1″ type=”T”>Queueid</Trace> <br/>- <Trace level=”1″ type=”B” name=”IDX_IDOC_TO_XML”><br/>  <Trace level=”1″ type=”T”>Get the Metadata for port SAPSD1</Trace> <br/>

    (0) 
  6. Sameel Baker
    ALE-AUDIT-IDoc-Inbound Handling
      IDoc-Inbound-Handling
      Syntax-Check-Flag X
      IDoc-Tunnel-Flag X
      Queueid

    Hi,

    I tried this scenario with XML_CONVERSION value as 1 & 2 with SYNTAX_CHECK ON but payload came as XML message in both cases :(. Any inputs ??

    (0) 
  7. Sameel Baker
    ALE-AUDIT-IDoc-Inbound Handling
      IDoc-Inbound-Handling
      Syntax-Check-Flag X
      IDoc-Tunnel-Flag X
      Queueid

    Hi,

    I tried this scenario with XML_CONVERSION value as 0 & 2 with SYNTAX_CHECK ON but payload came as XML message in both cases :(. Any inputs ??

    (0) 
  8. Sameel Baker
    ALE-AUDIT-IDoc-Inbound Handling
      IDoc-Inbound-Handling
      Syntax-Check-Flag X
      IDoc-Tunnel-Flag X
      Queueid

    Hi,

    I tried this scenario with XML_CONVERSION value as 0 & 2 with SYNTAX_CHECK ON but payload came as XML message in both cases :(. Any inputs ??

    (0) 

Leave a Reply