IDoc adapter inbound channel: Error Error while read

[adnanmaqbool]

Dear All

I am sending idoc from SAP 4.6C to PI. But on SM58 I am getting an error

IDoc adapter inbound channel: Error Error when reading

Which is not complete because field length is 50 characters , double clicking on this message is asking for message class. How can i see the complete message.

Can any one send me configuration detail of receiving IDOC at PI end , I don't want send to it forward from PI.

[former_member183908 · Accepted solution]

Hi

In R/3 system:

1. create logical system using t-code BD54.

2 .assign the created logical system to the existing client using t-code SCC4.

3 . create RFC destination of type 3 pointing to PI system using SM59 t-code

4. create port give your own port name using WE21.

5. create the Partner profiles using WE20 in that the partner no will be the logical system name and under outbound parameters click on add button and maintain the Message type which you are sending to PI.

In PI system:

1. Create RFC destination of type 3 pointing to R/3 system.

2 . create Port using the IDX1 t-code port name should be SAP + SYSTEM ID OF R/3 system.

3. Using IDX2 import the IDOC meta data in to your PI system.

Thanks

[adnanmaqbool · Accepted solution]

Please clear these points.

In PI system:

1. Create RFC destination of type 3 pointing to R/3 system.

2 . create Port using the IDX1 t-code port name should be SAP + SYSTEM ID OF R/3 system.

3. Using IDX2 import the IDOC meta data in to your PI system.

RFC destination to which direction , towards sender of IDOC ?

Port of which system sender system or receiver system?

What about configuration in Integration Directory , is there any configuration required on integration repository and on integration directory.

What will be the procedure of seeing complete message on SM58.

[former_member183908 · Accepted solution]

Please clear these points.

In PI system:
1. Create RFC destination of type 3 pointing to R/3 system.
2 . create Port using the IDX1 t-code port name should be SAP + SYSTEM ID OF R/3 system.
3. Using IDX2 import the IDOC meta data in to your PI system.

RFC destination to which direction , towards sender of IDOC ?

Port of which system sender system or receiver system?

What about configuration in Integration Directory , is there any configuration required on integration repository and on integration directory.

What will be the procedure of seeing complete message on SM58.

-->In PI system while ur creating the RFC destination of type 3 give the hostname and system number of ur R/3 system ie SAP 4.6 c.

-->In PI create Port using the IDX1 t-code port name should be SAP + SYSTEM ID OF R/3 system and in that RFC destination option, maintaine the destinatination name which we created using sm59.

-->coming to IR you need to create the:

1. Receiver data type.

2. receiver message type

3. receiver message interface. No need to create the above 3 for sender.

4.while mapping source is your Idoc and target is your receiver message type.

5. while interface mapping source is Idoc and target is receiver interface.

-->Coming to ID no need to create sender communication channel and no need to create sender agreement.

-->create receiver communication channel and receiver agreement.

--->create Interface determination.

-->create receiver determination.

-->If message got stuck in SM58, unlock it by using double click or activate the selected message.

Thanks

[MakotoS]

Hello,

Please take a look at the SAP Note 940313 "IDoc adapter: Error messages in SM58".

Here is the description like below.

e) Error message: IDoc adapter inbound: Error error

Solution:

You send IDocs to the central XI system, where they are received by the IDoc adapter. The IDocs are converted into IDoc XML, and a corresponding XI message is generated and transferred to the XI Runtime Engine. The Engine tries to read its own business system from the "Exchange Profile". If the Exchange Profile is currently unavailable, the message is not processed and it is returned to the sending system with an error message.

So, please take a look at the exchange profile connection in PI. You can check whether the connection is working or not by going to the transaction SPROXY in PI.

If the connection was broken, you should check the connection in LCRSAPRFC and Exchange profile (via RFC) or http connection SAP_ESR_PROXY (via HTTP).

Regards,

Makoto

[MakotoS]

Hello,

Please take a look at the SAP Note 940313 "IDoc adapter: Error messages in SM58".

Here is the description like below.

e) Error message: IDoc adapter inbound: Error error

Solution:

You send IDocs to the central XI system, where they are received by the IDoc adapter. The IDocs are converted into IDoc XML, and a corresponding XI message is generated and transferred to the XI Runtime Engine. The Engine tries to read its own business system from the "Exchange Profile". If the Exchange Profile is currently unavailable, the message is not processed and it is returned to the sending system with an error message.

So, please take a look at the exchange profile connection in PI. You can check whether the connection is working or not by going to the transaction SPROXY in PI.

If the connection was broken, you should check the connection in LCRSAPRFC and Exchange profile (via RFC) or http connection SAP_ESR_PROXY (via HTTP).

Regards,

Makoto

[former_member183908]

Hi

-->If you want to send your IDOC to only PI and if you dont want to forward further means follow the above mentioned configurations.

Thanks

[Former Member]

First step test RFC destination connection to PI is correct or not?

Steps to be followed are

R/3

1. Create RFC destination of TYPE 3 pointing to PI with logon credentials

2. create port and assocaite RFC destination

3. create logical system name for PI using BD54/sale

4. create partner for the above logical system using tcode we20

PI

1. create RFC destination of type 3 pointing to R/3

2. create port with IDX1 (name should be SAP+SYSID of R/3 )

HTH

Rajesh

[Shabarish_Nair]

Configuration steps required for posting idoc's(XI) -

/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi

ALE configuration for pushing idocs from SAP to XI -

/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

use the above as a reference.

Also use tcode IDX5 for IDoc monitoring in XI.