IDOC_ADAPTER - ATTRIBUTE_INV_SND_SERV

[Former Member]

I´ve read all the thread regarding this problem, but I still can't solve it.

My interface is synchronic from an Idoc. it goes through a BPM and then reaches a WebService

The messagge arrives perfectly but the ACK has the following error:

IDOC_ADAPTER - ATTRIBUTE_INV_SND_SERV

Unable to convert sender service R3_FPA_SALDOSBANC_BPM to an ALE logical system

[Former Member · Accepted solution]

Hi,

This error normally appears when there is problem with Logical system. I hope you might have already confirmed about the Sender and Receiver logical systems with related to the Business systems or services that have used.

Have a look at this SAP note:767500 & SAP Note : 777175

And also following link for more-

For BPM, check receiver agreement have sender party as Web Service service column checked. In your Receiver Agreement to your IDoc type(where you mention the idoc adapter), in the header mapping section, select the 'Sender Service' check box on and select your sender business system from the pop up help that appears. Try once more after activating the Receiver Agreement.

Thanks

Swarup

[Former Member]

hi

for Unable to convert the sender service to an ALE logical system

In ID, double click on ur Business system. Click on Service->Adapter Specific Identifiers. There u will see an entry for Logical system. You have to enter a proper Logical system there. You can create this new Logical system in SALE transaction.

and check the below blog:

/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system

Note: reward points if solution found helpfull

Regards

Chandrakanth.k

[Former Member]

Hi,

i think there is a problem with the Logical systems or ALE settings that you have performed.

Kindly follow or verify the steps:

Steps for ALE settings:-

Steps for XI

Step 1)

Goto SM59.

Create new RFC destination of type 3(Abap connection).

Give a suitable name and description.

Give the Ip address of the R3 system.

Give the system number.

Give the gateway host name and gateway service (3300 + system number).

Go to the logon security tab.

Give the lang, client, username and password.

Test connection and remote logon.

Step 2)

Goto IDX1.

Create a new port.

Give the port name.

Give the client number for the R3 system.

Select the created Rfc Destination.

Step 3)

Goto IDX2

Create a new Meta data.

Give the Idoc type.

Select the created port.

Steps for R3.

Step 1)

Goto SM59.

Create new RFC destination of type 3(Abap connection).

Give a suitable name and description.

Give the Ip address of the XI system.

Give the system number.

Give the gateway host name and gateway service (3300 + system number).

Go to the logon security tab.

Give the lang, client, username and password.

Test connection and remote logon.

Step 2)

Goto WE21.

Create a port under transactional RFC.(R3->XI)

Designate the RFC destination created in prev step.

Step 3)

Goto SALE.

Basic settings->Logical Systems->Define logical system.

Create two logical systems(one for XI and the other for R3)

Basic settings->Logical Systems->Assign logical system.

Assign the R3 logical system to respective client.

Step 4)

Goto WE20.

Partner type LS.

Create two partner profile(one for XI the other for R3).

Give the outbound or inbound message type based on the direction.

Step 5)

Not mandatory.

Goto BD64.

Click on Create model view.

Add message type.

Step 6)

Goto WE19

Give the basic type and execute.

fill in the required fields.

Goto IDOC->edit control records.

Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)

Click outbound processing.

Step 7)

Go to SM58

if there are any messages then there is some error in execution.

Goto WE02.

Check the status of the IDOC.

Goto WE47.

TO decode the status code.

BD87 to check the status of IDOC.

In case if not authorized then go to the target system and check in SU53, see for the missing object

and assign it to the user.

SAP r3

sm59(status check)(no message)

WE02(status check)

WE05(status check)

BD87(status check)

Xi

IDx5(Idoc check)

SU53(authorization check)

Reward points if helpful

Prashant

[Former Member]

HI

Please Refer the following thread.This might help you

Regards

Abhishek Mahajan

***Please reward points if helpful**