ATTRIBUTE_INV_SND_SERV

When I receive a message of a party I get the following message
Unable to convert sender XI party http://sap.com/xi/XI/SiXe/ to an IDoc partner
The WE20 customizing in R/3 is KU / SP / 0000001070
I tried already a lot of settings with header mapping and schema's but I don't get it working.
Any suggestions?
Ron

Hi,
For the business sytem you have to mention the adapter specific identifiers in the Integration Directory.
Go to Int. Directory -> Double Click on your IDoc Business System -> Menu -> Service -> Adapter Specific Identifiers
Maintain Logical System name and System ID and Client number.
Unable to convert sender service to an ALE logical system
ATTRIBUTE_INV_SND_SERV
XI 3.0, Party and Service problems (IDoc inbound)
Trouble shooting file to IDOC and IDOC to file
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
Refer below links for indepth troubleshooting
File to IDOC, trouble shooting
Refer below steps
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
IDOC to File steps to be followed please verify your scenario with it
R3 system.
1. Create SM 59 RFC destination to XI,.
2. We21 - Create port to XI.
3. We 20 -- Maintain Partner Profile for the outbound Idoc.
XI SLD
1. Create technical system for R3 system
2. Create Business System for the Client of the R3 system.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
These are the required steps for IDoc to File scenario...
In R3 (i.e., your IDES system)...
RFC dest to XI (sm59) - any name
Logical system (bd54) - any name
Port to XI (we21) - any name
Partner profile for the logical system (we20) - use Logical system name created in bd54
In XI...
RFC dest to R3 (sm59) -
Port to R3 (idx1) -
create metadata for the idoc (idx2)
In sld...
create business system for R3 with Logical system name as r3 sys.
In we19
and give in control record as
Sender : Port ; Partner
Receiver : Port = <Port created in WE21> ; Partner = <Partner created in we20>
see the below links
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
Also
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
Thanks
Swarup

Similar Messages

Idoc-to-File Scenario ATTRIBUTE_INV_SND_SERV Error

Hi All,
I am working on PI 7.1. I have an Idoc-to-File scenario. The scenario is working fine, but there is an error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>FILE_BC</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Unable to convert the sender service FILE_BC to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
PI is trying to send an acknowledgment back to the Sender ECC system. But in the IDX_NOALE, 'Do not request acknowledgement' is already checked. Still there is this error. It doesnt show up in MONI unless the Acknowledgement message is clicked, but alerts are getting triggered for these cases. Can anybody please help me in resolving this? I do not want the acknowledgements to be sent back to the ECC system.
Thanks,
Geetha

Thanks everybody! It has got fixed. I just requested No acknowledgements.
Geetha
Edited by: Geetha on Nov 11, 2009 5:45 PM

Problem adapter idoc - file ATTRIBUTE_INV_SND_SERV

Hello All,
please help me for my problem on adapter in my system XI for a scenario idoc -> file an I have an message error.
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>BS_ADONIX</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert the sender service BS_ADONIX to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please help if you have some idea BS_ADONIx is a business service.
Thanks for your reply

Steps IDOC to File.
IN IR
1. Import the IDOC in XI (input).
2. Create a Data type of (output) i.e. file.
3. Create a Message type of (output) i.e. file used the above data type.i.e.Step 2
4. Create a Message interface of(output) .i.e file used the above messagetype. i.e.Step3.
5. create Mappping select source as IDOC and target as Message type you created.
6, In Interface mapping select source as IDOC and Target Interface Message Interface of file i.e.Step 4.
In ID.
Select the recevier determination of .
1.select sender system as R/3 system recivr as File Bunisees system
2. create interface determination select sender system as R/3 Sender interface as IDOC . in interface determination select inbound message whihc createdin step 4
and message interface we created in step 5.
3. create recevier determination sender r/3 interface IDOC and reciver File business system . so create reciver file adapter and assign to file business system
Please reward points
Thanks
Sreeram.G.Reddy

XI - IDOC: ATTRIBUTE_INV_SND_SERV

Dear all,
I had a FILE - XI - IDOC scenario in which some vendor data was communicated. The scenario worked like a charm.
Now I have to use a multi-mapping: FILE - XI - 2*IDOC. So, I created the multimapping, the abstract interfaces, and the integration process. Now, the sender has changed from the system to the integration process. And now I get the following error at the IDOC adapter.
ATTRIBUTE_INV_SND_SERV
I have read some blogs and forum messages concerning LS names, however, it does not make sense to me as the previous scenario worked fine.
Can anyone help out?
Cheers.

> Hi,
>
> Now, your original business system is no longer the
> sender of the IDoc, but your Integration Process is
> the IDoc Sender.
>
> To resolve the error, either assign a Logical System
> Name to the Integration process in the Directory
> (under Service -> Adapter specific identifiers in the
> Integration Process), or assign the original business
> system as the sender in the receiver agreement.
>
> Kind regards,
>
> Koen
Hi Koen,
When I adjust the Adapter specific identifiers -which was empty- for my Integration Process, and I fill out an arbitrary name, the distribution model of r/3 cannot find a partner profile. Do I need to create then a new logical system in r/3 and corresponding partner profile for each Integration Process?
What am I doin' wrong???
Cheers
Message was edited by:
A. Schotanus

ATTRIBUTE_INV_SND_SERV (partner number different of SLD logical system)

Hi,
I'm implementing an interface with XI 3.0. In my scenario, I've created one IDOC communication channel. and i try to send some data from file (File --> XI --> IDOC R/3)
I am using a XSL mapping to build an Idoc-XML from this input file and I'm filling the sender and receiver partner name (different of the default logical system of SLD)
In a first test, the Idoc adapter changed the partners name by the default ALE name of SLD, then when Idoc couldn't be processed in R/3 system because EDI partner was not customized. We would like to use the logical system of our mapping instead of the logical system froM SLD.
Then, I've applied next changes:
- I've checked "Apply Control Record Value from Payload"
- I've changed the Header mapping, indicating:
 Sender service as XPath = ..../SNDPRN
 receiver service as XPath = .... /RCVPRN
- The schema as ALE#LS
But althought these modifications, we are having this error in the monitoring (SXMB_MONI)
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please, i would really appreciate if anybody of you can help me to fix this problem.
Thanks in advance,
Gerardo

Hi michal,
 I've reviewed your weblog and it's very helpful as verifications guide.
 We've imported the Business system from the SLD, but we don't want to use its logical name. We would like to use the logical name of our XSL mappings.
 We've also checked the receiver agreements in SXI_CACHE, and both seems to be ok:
ReceiverService /.../IDOC/EDI_DC40/RCVPRN
SenderService /.../IDOC/EDI_DC40/SNDPRN
 And as last step, we've applied oss note 791181, but i have still the same error message ATTRIBUTE_INV_SND_SERV.
 Anyway, thanks a lot for you help. Please, if you have any more idea, please, i would really appreciate your help.
Regards,
Ger

IDOC_ADAPTER - ATTRIBUTE_INV_SND_SERV

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

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

XI 3.0 - attribute_inv_snd_serv error

Hello,
I am transferring from 3rd party to Idoc. Is the solution using table IDXNOALE also valid for a receiver IDOC adapter? I entered the values in the table and indeed the "attribute_inv_snd_serv" error disapeared but the message is now in status "Scheduled for Outbound Processing" in sxmb_moni.
Thanks
Boaz

Hi Boaz,
You messages is in the output queue, waiting to be processed.
Open up the queue by clicking on the queueid. You will probably see a failed messgae in the queue block all the messages after it. You will need to resolve the problem causing the message not to be processed, or delete it if it is of no consequences.
Regards,
Bill

IDOC Adapter error"ATTRIBUTE_INV_SND_SERV'

I am doing small example like Using HTTP Client to submit Order Response XML from my browser and Converting Order Response XML file to an order response IDOC of type ORDERS05 idoc. I have developed all the necessary objects in Integartion Repository & Integration Directory and posted the Order Response XML file through HTTP client.
I am getting the error message(in SXMB_MONI)like "Unable to convert sender service OrderResponse to an ALE logical system".
Appritiate, if some one help me On this .
Thanks
Sudha

For the business sytem you have to mention the adapter specific identifiers in the Integration Directory.
Go to Int. Directory -> Double Click on your IDoc Business System -> Menu -> Service -> Adapter Specific Identifiers
Maintain Logical System name and System ID and Client number.
Check the following blog.
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
regards
Shravan

ATTRIBUTE_INV_SND_SERV Error

Hi all, I have configured a File-to-Idoc Integration Scenario and y get the next error (SXMB_MONI)
 tag?
Thanks

Thank Rajevv.
I have recoded my java mapping to write a correct xml. Now I have a xml this this structure
<ZRI_CONTRATOS>
 <IDOC BEGIN="">
 <EDI_DC40 SEGMENT="">
 <TABNAM/>
 <MANDT/>
 <DOCNUM/>
 <DOCREL/>
 <STATUS/>
 <DIRECT/>
 <OUTMOD/>
 <EXPRSS/>
 <TEST/>
 <IDCOTYP/>
 <CIMTYP/>
 <MESTYP/>
 <MESCOD/>
 <MESFCT/>
 <STD/>
 <STDVRS/>
 <STDMES/>
 <SNDPOR/>
 <SNDPRT/>
 <SNDPFC/>
 <SNDPRN/>
 <SNDSAD/>
 <SNDLAD/>
 <RCVPOR/>
 <RCVPRT/>
 <RCVPFC/>
 <RCVPRN/>
 <RCVSAD/>
 <RCVLAD/>
 <CREDAT/>
 <CRETIM/>
 <REFINT/>
 <REFGRP/>
 <REFMES/>
 <ARCKEY/>
 <SERIAL/>
 </EDI_DC40>
 <ZRS_CABECERA_CNT SEGMENT="">
 <OBJECT_EX/>
 <TYPE_CNT/>
 <OBJECT_ID/>
 <PARTNER_NUMBER/>
 <PARTNER_FCT/>
 <PARTNER_NUMBER2/>
 <PARTNER_FCT2/>
 <PARTNER_NUMBER3/>
 <PARTNER_FCT3/>
 <PARTNER_NUMBER4/>
 <PARTNER_FCT4/>
 <DATE_BEGIN/>
 <DATE_END/>
 <DATE_SIGN/>
 <ESTAT/>
 <CURRENCY/>
And I get the next error:
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Fehler: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
But the fiedl Fehler: I::000 gaves me little information ( Error: I::000). Does any one any idea of where the problem cuold be.
Thanks

Error in IDOC - File scenario

Hi Experts,
This is my error :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>INTEGRATION_SERVER_XID</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert the sender service INTEGRATION_SERVER_XID to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
OTHER ERROR FOR PAYLOAD OF SENDER PART IS AS BELOW :
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
The character '>' was expected. Error processing resource 'file:///C:/Documents and Settings/ABC/Local Settings/Tempor...
<?xml version="1.0" encoding="UTF-8" ?><ZZ/AFS/FUNACK><IDOC BEGIN="1"><EDI_DC40 SEGMENT="1"><TABN...
Please Help,
Regards,
Study SAP

Hi,
The problem occurs when sender and receiver business system or business service does not have a logical system name.
ID - Integration Directory
Posting the IDOC'S into SAP R/3 System, sender and receiver business system or business service requires the logical system name. If the business system (Web As ABAP) does not have the logical system name, then add the logical system for business system.
In technical system browser
If business system type = Web AS ABAP, then add the Logical system in Technical System level and Save.
If business system type = Third-Party, then add the logical system in business system level and Save.
If the business service does not have the logical system name in ID, it needs to be configured as follows.
Check the below screen shot which shows how to add the logical system for business service.
Go to ID and click the Business service -> Services -> Adapter Specific Identifiers. Enter the logical system name and Save.
Apply and activate.
Hope this will help you.
regards
Aashish Sinha
PS : reward points if helpful

Error in IDOC to SOAP

I am doing IDOC to SOAP(3rd party) scenario and I get this error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have searched the forums and there is lot of info on this,
According to this blog
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
He says Click on the Business System and see the adapter specific Identifiers,So do I have to click on my 3rd pary Business System here? since for IDOC sender there will be no BS.Am I correct.
Thanks

Hi Guest
first login to SDN with good name
This problem occurs due to INVALID SENDER SERVICE
kindly check in your configuration whether you have given a valid name to your sender service and also check the conditions in RCVR deetermination
if not modify that and activate again .Make a CACHE refresh
hope this will work for you
Regards
sandeep
PS if helpful kindly reward good points

Http - iDoc scenario - ID

Hi,
HTTP - XI - iDOC is my scenario.....
i am facing problem in iDoc adapter...
the error category is idoc adapter and the error id is "ATTRIBUTE_INV_SND_SERV"
Which RFC destination and port should in mention in Communication Channel? Either the receiver or XI?
forward your suggestions....
Thanks,
RPN

hi rpn,
check this links
Go to Int. Directory -> Double Click on your IDoc Business System -> Menu -> Service -> Adapter Specific Identifiers
Maintain Logical System name and System ID and Client number.
Check the following blog.
The specified item was not found.
Unable to convert sender service to an ALE logical system
ATTRIBUTE_INV_SND_SERV
XI 3.0, Party and Service problems (IDoc inbound)
Trouble shooting file to IDOC and IDOC to file
Troubleshooting File-to-IDOC Scenario in XI.
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
see the below links
ALE configuration for pushing idocs from SAP to XI
Introduction to IDoc-XI-File scenario and complete walk through for starters.
idoc settings Configuration steps required for posting idoc's(XI)
Also
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
IDOc testing - Generate Test Case for an IDOC Scenario
regards
srinivas

Unable to convert the sender service to an ALE logical system

Hello,
file adapter > XI 3.0 > Idoc adapter > r/3 system
In sxmb_moni I receive "Unable to convert the sender service to an ALE logical system".
In we05 in r/3 system no Idocs are arrving. I have no problem with idoc > XI > idoc scenario to this same r/3 system (using same sld business system)
I read other topics on this error but it seems they all talk about an IDOC outbound interface.
What should I check?
Thanks
Boaz

I do have the same problem as Boaz Paz
When I try :
file adapter > XI 3.0 > Idoc adapter > r/3 system
> This is a B2B scenario where "AVTItalia" is the external party trying to send via its "AwayOrders" business service (a file pickup) an idoc to business system "UPG" (non party service)
I get an error while XI tries to call its IDoc Adapter:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>AwayOrders</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service AwayOrders to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
With the following trace logs :
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external = AVTItalie</Trace>
<Trace level="1" type="T">Sender party normalized = AVTItalie</Trace>
I ve tried to (cf. /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc ):
1. add a logical system name "ACYAVTFBC1" in "Adapter specifier Id" of "AwayOrders"
In the runtime cache > services an entry appears for " ... Logical System | AVTItalia | ACYAVTFBC1...".
2. declare "AVTItalia" as a business partner in SLD with the logical system name
Plz help!

File to IDOC scenario error...

Hi all,
we hhave created an File to Idoc scenario .
we are getting the following error in SXMB_MONI t-code.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>BUS_SENDER</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service BUS_SENDER to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
can any one plz say wat this error might be..
TIA
Regards,
Raj

Hi,
The problem occurs when sender and receiver business system or business service does not have a logical system name.
ID - Integration Directory
Posting the IDOC'S into SAP R/3 System, sender and receiver business system or business service requires the logical system name. If the business system (Web As ABAP) does not have the logical system name, then add the logical system for business system.
If business system type = Web AS ABAP, then add the Logical system in Technical System level and Save.
If business system type = Third-Party, then add the logical system in business system level and Save.
If the business service does not have the logical system name in ID, it needs to be configured as follows.
Go to ID and click the Business service -> Services -> Adapter Specific Identifiers. Enter the logical system name and Save.
Apply and activate.
hope this will help you.
regards
Aashish Sinha
PS : reward points if helpful

XI 3.0, Party and Service problems (IDoc inbound)

Hi,
The scenario is:
Flatfile (J2SE plain adapter) => XI => IDoc => R3
The basic functionality Service Without a Party works ok. But I run into a restriction when trying to have more than one Business System having the
same Logical System Name (XI doesnt allow it). Basically I dont want to have one unique Logical System Name for every business scenario, especially when they come from the same legacy system (Technical System).
Is it possible to have only one Logical System Name for all the interfaces that comes
from the same legacy application (or even from all the legacy systems)?
Tried even to do the same with Party objects, but there I run into errors (cant even get the IDoc through):
"IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV
or
"IDOC_ADAPTER">ATTRIBUTE_INV_RCV_PARTY
depending on the configuration.
Is there any documentation about how these configurations
should be made?
br.samuli

Hallo Samuli,
i guess, you have the same problem that has already been discussed in here. That is if you create a new Business Scenario in the Configurator you can not see your business system you want to use. But that is not an error and also not a restriction of XI as you will discover in the post "can't assign business system twice". It is possible to use the logical system name of a legacy system for all interfaces coming from this system, everything else would not make sense.
Here the link to the message: can't assign business system twice
Best Regards
Christine

ATTRIBUTE_INV_SND_SERV

Similar Messages

Maybe you are looking for