<b> i got ur point.U r already aware that for IDOC we need not require any communication channel and sender agreement.i.e we dont use the IDoc adapter.This is becoz Idoc adpater is in ABAP stack...
so how the Idoc structure idata is transformed into XML.right???</b>
I guess Idoc adapter is used internally though we dont define it in CC.idoc metdata is needed in the xi system, beacuse xi server doesnt have the standard idoc structure. we import the metadata from the r/3 system using the transaction IDX2.
an idoc adapter receives an idoc from an r/3 system and converts that idoc into an xml idoc structure.
that means IDoc (Intermediate Document) metadata comprises structures for the corresponding IDoc types that are required by the IDoc adapter to convert these IDocs to IDoc XML format and the other way around.
IDOC adapter resides on Integration server, so Integration engine takes care of the conversion format from IDOC to XML, hence there is no need configure the sender Adapter .Also since its resides on Integration server you can directly post the message in the Integration engine..
IDoc adapter if you want to use the Integration Server to process IDocs. The IDoc adapter converts the IDocs to IDoc XML format so that they can be processed by the Integration Server pipeline.
Message interface, sender agreement, & sender communication is not required when Idoc is directly triggered from sender system to XI.
The module processor of the Idoc adapter does the conversion from Idoc to xml. At outbound side, the sender agreement is not required. But the data is passed through the Idoc adapter in this case also. So same procedure is followed at both the end
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.