cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Unable to convert the sender service

Go to solution
Former Member

on ‎08-01-2006 6:09 PM

0 Kudos

Hi,

On my new system XI 7.0, I try to configurate a simple "File -> Idoc" scenario without BPM, but I have still a classical dump:

  <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code> 
  <SAP:Stack>Unable to convert the sender service to an ALE logical system</SAP:Stack>

Note: My Business Service's (of ECC) doesn't appeared between "sender service" and "to an ALE".

Moreover, in my payload, my IDoc has an <u>EMPTY</u> EDI_DC40 segment. Is it normal ?

I have checked:

1) the Logical System name in the SLD

2) the port definition in WE20 compared to this one of CC

3) the RFC destination in SM59 compared to this one of CC

4) the Adapter specific identifier of my Business System

5) then played with sxi_cache...

I'm a few dissapointed... I beleived to have check everything. Maybe not!

Mickael

Show replies
Show replies
Answer

Accepted Solutions (1)

Accepted Solutions (1)

udo_martens
Active Contributor
‎08-02-2006 8:16 AM
0 Kudos

Hi Mickael,

switch on full SXMB_MONI trace (SXMB_ADM / Configuration of Integration Engine / TRACE = 3) and look at "Call a Adapter / SOAP Header / IDOC Outbound" (translated from German) to find out how the adapter filled EDI_DC40 fields.

Your error usually raises when the SENDER logical system (control it at adapter specific identifiers of bus system) is not available at R/3 (control at WE20).

Regards,

Udo

Show replies
Show replies
Former Member
‎08-02-2006 9:25 AM
0 Kudos

Hi Udo,

Here's the result:

  <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> 
- <!--  Call Adapter 
  --> 
- <SAP:OutboundBinding xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SAP:OutboundBindingEntry version="30">
  <SAP:OutboundBindingObjectId>EDB7E1C839603FB9B04057583BE29980</SAP:OutboundBindingObjectId> 
  <SAP:FromPartyName /> 
  <SAP:FromServiceName>BS__TESTXID_1</SAP:FromServiceName> 
  <SAP:ToPartyName /> 
  <SAP:ToServiceName>ECB_BS_MDT720</SAP:ToServiceName> 
  <SAP:ToInterfaceName>DEBMAS.DEBMAS06</SAP:ToInterfaceName> 
  <SAP:ToInterfaceNamespace>urn:sap-com:document:sap:idoc:messages</SAP:ToInterfaceNamespace> 
- <SAP:OutboundBindingAttributes>
  <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" /> 
  </SAP:OutboundBindingAttributes>
- <SAP:HeaderMapping>
  <SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30" /> 
  </SAP:HeaderMapping>
- <SAP:ChannelEntry version="30">
  <SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30" /> 
  <SAP:ServiceName xmlns:SAP="http://sap.com/xi/XI/Message/30">ECB_BS_MDT720</SAP:ServiceName> 
  <SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">CCR_ECBMDT720_IDOC</SAP:ChannelName> 
  <SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:AdapterName> 
  <SAP:AdapterNamespace xmlns:SAP="http://sap.com/xi/XI/Message/30"><a href="http://sap.com/xi/XI/System" TARGET="test_blank">http://sap.com/xi/XI/System</a></SAP:AdapterNamespace> 
  <SAP:AdapterSWCV xmlns:SAP="http://sap.com/xi/XI/Message/30">B38BCD00E47111D7AFACDE420A1145A5</SAP:AdapterSWCV> 
  <SAP:AdapterEngineType xmlns:SAP="http://sap.com/xi/XI/Message/30">IS</SAP:AdapterEngineType> 
  <SAP:AdapterEngineName xmlns:SAP="http://sap.com/xi/XI/Message/30" /> 
  <SAP:MessageProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:MessageProtocol> 
  <SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30" /> 
  <SAP:TransportProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:TransportProtocol> 
  <SAP:TransportProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30" /> 
  <SAP:ChannelDirection xmlns:SAP="http://sap.com/xi/XI/Message/30">O</SAP:ChannelDirection> 
  <SAP:FromPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" /> 
  <SAP:FromPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" /> 
  <SAP:ToPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" /> 
  <SAP:ToPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" /> 
- <SAP:ChannelAttributes xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:Attribute>
  <SAP:Name>interfaceVersion</SAP:Name> 
  <SAP:Value>3</SAP:Value> 
  </SAP:Attribute>
- <SAP:Attribute>
  <SAP:Name>passControlSetValues</SAP:Name> 
  <SAP:Value>1</SAP:Value> 
  </SAP:Attribute>
- <SAP:Attribute>
  <SAP:Name>passReceiverValue</SAP:Name> 
  <SAP:Value>0</SAP:Value> 
  </SAP:Attribute>
- <SAP:Attribute>
  <SAP:Name>passSenderValue</SAP:Name> 
  <SAP:Value>0</SAP:Value> 
  </SAP:Attribute>
- <SAP:Attribute>
  <SAP:Name>port</SAP:Name> 
  <SAP:Value>SAPECB</SAP:Value> 
  </SAP:Attribute>
- <SAP:Attribute>
  <SAP:Name>queueing</SAP:Name> 
  <SAP:Value>0</SAP:Value> 
  </SAP:Attribute>
- <SAP:Attribute>
  <SAP:Name>restoreOriginalParty</SAP:Name> 
  <SAP:Value>0</SAP:Value> 
  </SAP:Attribute>
- <SAP:Attribute>
  <SAP:Name>rfcDestination</SAP:Name> 
  <SAP:Value>ECBCLNT720</SAP:Value> 
  </SAP:Attribute>
- <SAP:Attribute>
  <SAP:Name>sapRelease</SAP:Name> 
  <SAP:Value>640</SAP:Value> 
  </SAP:Attribute>
- <SAP:Attribute>
  <SAP:Name>segmentVersion</SAP:Name> 
  <SAP:Value /> 
  </SAP:Attribute>
  </SAP:AdapterTypeData>
  </SAP:ChannelAttributes>
  </SAP:ChannelEntry>
  </SAP:OutboundBindingEntry>
  </SAP:OutboundBinding>

it seems it's ok: receiver, sender, port, rfc destination are found. But my EDI_DC40 is still empty

  <?xml version="1.0" encoding="UTF-8" ?> 
- <DEBMAS06>
- <IDOC BEGIN="">
- <EDI_DC40 SEGMENT="1">
  <TABNAM /> 
  <DIRECT /> 
  <IDOCTYP /> 
  <MESTYP /> 
  <SNDPOR /> 
  <SNDPRT /> 
  <SNDPRN /> 
  <RCVPOR /> 
  <RCVPRN /> 
  </EDI_DC40>
- <E1KNA1M SEGMENT="1">
  <KUNNR>123777</KUNNR> 
  <NAME1>Adams</NAME1> 
  <NAME2>James</NAME2> 
  </E1KNA1M>
  </IDOC>

Mickael

Answers (5)

Answers (5)

Former Member
‎08-02-2006 5:42 PM
0 Kudos

Hi,

in fact the solution was given by Udo... and the 1st times I did not see it:

In the Business System used in my sender agreement (this one which takes my file and gives it to XI), the Logical System was forgotten. After to have writen "toto" inside this field, the idoc has been sent to R/3. Strange!

Thanks to Udo and Loic.

Mickael

Show replies
Show replies
Former Member
‎08-02-2006 3:00 PM
0 Kudos

Hi,

You can refer the following weblog:

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

Show replies
Show replies
Former Member
‎08-02-2006 4:42 PM
0 Kudos

Hi everybody,

thanks for all, but I'm still my problem. I have checked and checked again all points of my ALE config plus these one of my scenario, but without to find what is missing...

Is there somebody who can send me a doc?

(car là j'en perds mon latin...)

Note: Currently I use NW2004S with a SLD defined on Solution Manager. In my previous project (NW2004), I realized the same flow without any pb. Ahrrrr.

Mickael

Former Member
‎08-02-2006 4:44 PM
0 Kudos

Hi everybody,

thanks for all, but I'm still my problem. I have checked and checked again all points of my ALE config plus these one of my scenario, but without to find what is missing...

Is there somebody who can send me a doc?

(car là j'en perds mon latin...)

Note: Currently I use NW2004S with a SLD defined on Solution Manager. In my previous project (NW2004), I realized the same flow without any pb. Ahrrrr.

Mickael

Former Member
‎08-02-2006 2:58 PM
0 Kudos

Hi,

There are two ways to deal with the population of the control record in case of inbound idoc scenario.

One is to dissable the control record in the mapping stage and leave the checkboxes in the receiver idoc adapter :

Apply control record values from payload

Take sender from payload

Take receiver from payload

unchecked.

Other is to populate the control record in the mapping stage with appropriate values and then check

above mentioned checkboxes.

Show replies
Show replies
former_member181955
Contributor
‎08-02-2006 9:38 AM
0 Kudos

Hi Mickael,

The logical system whatever you have given as part of creation of Business system for file in SLD must be created in SAP system where idoc is received(SALE)

Example

1.BS_FILE is your file Busines systen in SLD

2.LS_FILE is the logical system you have given during the creatiog of Business (BS_FILE) in SLD.

3.IN SAP R/3 Execute tcode SALE create the logical system LS_FILE.

The error

<b>Unable to convert the sender service to an ALE logical system</b> won't come again.

thanks

Prasad Babu Nemalikanti

Show replies
Show replies
Former Member
‎08-02-2006 10:10 AM
0 Kudos

Hi prasad,

unfortunately, my LS (used in my BS) is correctly defined in my R/3 (ECC).

Maybe a pb with partner profile (inbound idoc) inside ECC, or maybe a pb with acknowledgment...

Mickael

MichalKrawczyk
Active Contributor
‎08-01-2006 6:26 PM
0 Kudos

Hi,

in your receiver agreement

did you set

Sender Service = your business system (ECC)?

Regards,

michal

Show replies
Show replies
Former Member
‎08-02-2006 8:59 AM
0 Kudos

Hi Michal,

No, because my ECC is my receiver (not my sender).

Mickael

Former Member
‎09-24-2008 2:50 PM
0 Kudos

Hi Mical,

I have a scenario Webservice to Idoc ,the data is going into XI but having an error like this

IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV

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

I have consulted your webblog on this but my configuration is right.My SP is 14 also.

Should I specify the sender service as the Business system name in header mapping in Receiver Agreement in id?

My Business system is receiver system basically.

Please suggest.

Abhishek

Ask a Question