topic Re: about idoc... in Application Development and Automation Discussions

about idoc...

former_member192432 — Mon, 09 Jun 2008 09:22:21 GMT

Hi Friends.

What is an ADAPTER . Is IDOC is an ADAPTER or what.

regards..

Re: about idoc...

Former Member — Mon, 09 Jun 2008 09:24:58 GMT

hi there....

Purpose

The IDoc adapter enables you to process IDocs (Intermediate Documents) using the Integration Engine. IDocs from SAP systems Release 3.1x or higher are supported.

The IDoc adapter is used by SAP systems to connect to a centrally configured Integration Engine using IDocs. A system that has an Integration Engine of this type is referred to as the Integration Server. External systems can also use the IDoc adapter to connect to an Integration Server.

Implementation Considerations

Only use the IDoc adapter to integrate SAP systems with the Integration Server if a scenario of this kind suits your requirements. For example, if you want to make IDoc data in the form of XML messages available to additional receivers, or if you want to connect different components or integration processes that were previously not integrated. Only stop using existing functioning IDoc scenarios after serious consideration.

Integration

The IDoc adapter is part of the Integration Server. Essentially, the IDoc adapter comprises two parts, namely an adapter at the Integration Server inbound channel, and an adapter at the Integration Server outbound channel. The metadata for the IDoc types involved is shared.

The adapter at the inbound channel is located before the Integration Server pipeline and calls this pipeline. The adapter at the outbound channel, however, is called by the pipeline, and can therefore be regarded as part of the pipeline.

The connected systems transfer or receive IDocs through their IDoc RFC interface.

Features

You require the IDoc adapter to connect SAP systems (or external systems) to the Integration Server using IDoc communication.

You need the 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.

The IDoc adapter only evaluates the payload of a received XML message. Additional attachments are ignored and not forwarded.

It is also possible to transfer XML received by the Integration Server in IDoc format to connected systems. The Integration Server pipeline must convert the received XML to IDoc XML, and then transfer this IDoc XML to the IDoc adapter. The IDoc adapter converts the IDoc XML to native IDoc format and sends the IDoc to the identified receiver system using the standard IDoc interface. The IDoc adapter can also call external subsystems.

If none of the pipeline services require the IDoc XML, then you can set a corresponding configuration parameter so that IDocs are not converted to IDoc XML, but are transported as tables instead. This only makes sense if IDocs are to be received on the Integration Server and sent again as IDocs without changes to the data records. Avoiding unnecessary conversions from and to XML can lead to improvements in system performance.

You can improve performance further by processing IDoc XML messages to the same receiver in packages. To create these message packages, use event-driven message processing.

You can also use the following transactions and functions:

● Maintain ports in the IDoc adapter (IDX1)

● Load, display, and delete metadata (IDX2)

● Display IDoc XML messages (IDX5)

● Configuring Acknowledgment Requests

● Sending Acknowledgment IDocs as XI Request Messages

You cannot execute transactions that have the locked symbol (), because you do not have the required authorizations.

The authorizations for the individual transactions are tailored to requirements and are assigned as derivations of the following roles. They are all based on the authorization object S_XMB_AUTH or S_XMB_DSP.

do reward if helpful.

Re: about idoc...

Former Member — Mon, 09 Jun 2008 09:25:14 GMT

Hi,

IDoc Adapter

Purpose

The IDoc adapter enables you to process IDocs (Intermediate Documents) using the Integration Engine. IDocs from SAP systems Release 3.1x or higher are supported.

Implementation Considerations

Integration

The connected systems transfer or receive IDocs through their IDoc RFC interface.

To COnfigure IDOC Adapter

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098

Re: about idoc...

Former Member — Mon, 09 Jun 2008 09:29:18 GMT

Hi,

SAP XI IDoc Adapter is by and far the most widely used adapter. This article describes its configuration on sender and receiver end along with related settings in XI and the involved SAP application systems. The configuration is fairly easy and straightforward. This article simply summarizes the different steps involved.

IDoc Adapter converts the incoming IDoc to XML and XML messages to outgoing IDoc. The IDoc adapter resides on the ABAP stack of the integration server and hence no Sender Agreement is necessary in order to setup the sender adapter. A point to note is that using IDoc adapters, we can only have asynchronous (tRFC) processing. Apart from using Runtime Workbench and transaction SXMB_MONI, IDoc messages can be monitored using transaction IDX5.

Now, let us understand the settings required in order to send an IDoc from SAP Application system to XI.

IDoc Sender Adapter Configuration

The source SAP Application system must be setup to send IDoc to the XI server. In one of my previous articles, I have described how to set up the source SAP Application system to send an outbound IDoc.

On the XI system, create a RFC destination of type R/3 connection, pointing to the source SAP Application system. Also, create a port for the source system using transaction IDX1. Mention the above created RFC destination in the IDX1 port configuration. This is required as XI uses this configuration to read the IDoc metadata from the source system. Once you have done this, your XI system is ready to receive IDocs from the source SAP system.

The metadata for an IDoc is loaded in the Integration Server when the first message for the particular IDoc is processed by the Integration Engine. You can see the IDoc metadata using the transaction IDX2. If you dont see the metadata for your IDoc in transaction IDX2, you can manually load it using the Menu options in IDX2. You need to specify the port and the IDoc type before you can import the IDoc metadata.

You can then import the IDoc definition from the source SAP system in XI Integration Repository and build your scenario on it. Then complete the Directory configuration necessary for your scenario. You donu2019t need to create any sender agreement as IDoc adapter resides on integration engine itself.

IDoc Receiver Adapter Configuration

Configuring IDoc Receiver Adapter is equally easy. On the XI system, create the RFC destination of type R/3 connection, pointing to target SAP Application system using transaction SM59. Create a port for the target SAP system using transaction IDX1. Mention the above created destination and port names in the communication channel used in your receiver agreement. Adjacent figure shows the configured IDoc receiver.

In the target system, you should create the partner profile for the source system using the transaction WE20. For a detailed understanding refer my post on Settings in R/3 Partner System to Receive IDocs. This post discusses the steps assuming you are using a custom IDoc. In case you are using a standard IDoc you are only required to define the source system in transaction BD54 and create a partner profile using WE20 as discussed in the same article.

Regards,

Jagadish

Re: about idoc...

Former Member — Mon, 09 Jun 2008 10:05:30 GMT

Adapater is terminology used in XI,it is a way of communication between XI and sender or reciever.

There are amny adapters .

JDBC,RFC,IDOC ,SOAP,HTTP,XI,third party .

Please reward if useful.

Re: about idoc...

former_member192432 — Thu, 10 Dec 2009 12:11:39 GMT

thanks for reply