Resolution:
The format in which TIB/Adapter for R/3 2.0 handles messages is
indeed the AE2.0 wireformat. When you want to handle the
communication between TIB/Adapter for R/3 and MessageBroker, both share the
common AE 2.0 wireformat standard and therefore need no
translation.
However, to actually load the structure of the IDOC into MessageBroker
typically, what you would need is to load the xml file
related to the IDOC type you are working with, via TIB
Repository into a MessageBrokerschema Plugin.  
The key therefore, is to have TIB Repository handle the translation of xml files
(you have downloaded using the MetaDataAdapter component of
the TIB/Adapter for R/3), so MessageBrokerand the TIB/Adapter for R/3 can communicate.
Contact support@tibco.com for a sample MessageBrokersheet
showing a schema plugin with IDOC structure loaded.

[This KA was unapproved and obsolete when migrated.] How do I send IDoc message data (EDI_DC, E1MARAM andE1MAKTM) at the same time to the TIB/Adapter for R/3 2.0?

Product: TIBCO Adapter for R/3 (SAP) Version: 2.0.0 OS: Not Specified OS --------------------