ALE logical system to client

Hi,
Is assignment of SAP logical system to client mandatory...
I understand that we can give dummy names like SAP_A as logical systems but is it mandatory to assign them to clients..
I think Idoc can be sent to the respective SAP system through ports instead of a particular LS

this client assignment to logical system is about your sending system.
the steps for ALE config are following only:
1)     IMG > SAP NetWeaver > Application Server > IDoc Interface / Application Link Enabling (ALE) > Basic Settings > Logical systems > Define Logical System
2)     IMG > SAP NetWeaver > Application Server > IDoc Interface / Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Configure Predefined ALE Business Processes > Logistics > Logistics <-> External Systems > External Transportation Planning Systems > Maintain ALE Port Definition (Transaction WE21)
3)     IMG > SAP NetWeaver > Application Server > IDoc Interface / Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Global Organizational Units > Cross-System Company Codes (Transaction OB72, SALE, OBB5)
4)     IMG > SAP NetWeaver > Application Server > IDoc Interface / Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Maintain Distribution Model and Distribute Views (Transaction BD64)
5)     IMG > SAP NetWeaver > Application Server > IDoc Interface / Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Configure Predefined ALE Business Processes > Logistics > Master Data Distribution > Proposal for distribution model: Customer and vendor masters (Transaction WYL2)
6)     IMG > SAP NetWeaver > Application Server > IDoc Interface / Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Configure Predefined ALE Business Processes > Logistics > Logistics <-> External Systems > External Transportation Planning Systems > Maintain ALE Partner Profiles (Transaction WE20)

Similar Messages

Receiver service ??? cannot be converted into an ALE logical system

Hi,
I am hoping for some help with an Idoc issue in XI version 3.0. The scenario is like this:
Flat file->File adapter->XI->Idoc adapter->R/3
I have configured a scenario in one system like this that works fine. But in the current system I am getting the error message "Receiver service ??? cannot be converted into an ALE logical system" from the Idoc adapter.
As it is XI 3.0, I have set the Agency and Scheme in the destination communication channel to <Service>, ALE#LS and in the destination party, I have created a alternative identifier <Service>, ALE#LS, SYSCLNT200.
I have configured an ALE logical system name in the SLD.
I have cleared the SLD cache in the integration builder.
The ALE logical system name was not in the SLD when the message first appeared, but I thought clearing the cache would fix that. I have not tried deleting the service and re creating it. That is my next step....if all else fails.
Not sure what else I haven't tried.
Can anyone offer any advice?

Thanks Sam Raju for the reply.
On your questions:
1. I checked IDX1 - port for the receiving R/3 is defined as SAPIR1_300 (port: SAPIR1 and Client: 300) and it is mapped to RFC destination of IR1300.
2. Checked RFC destination IR1300 - it is setup as R/3 connection and checked test connection and remote login and both are working fine
3. Checked IDX5 - did find one message (status is successful) corresponding to the file I am sending into R/3 and this entry is an Outbound entry.
Question: Should there be two entries here in IDX5 - one for inbound and the other for outbound?
May be I am doing something wrong here in setting up the interface mapping and endpoints. Anyway when I check the IDOCOutbound in the Soap Header, I see the following:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/exchange/MessageFormat/">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>100</SAP:MANDT>
<SAP:DOCNUM>0000000000008002</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>FLIGHT_SAVEREPLICA01</SAP:IDOCTYP>
<SAP:MESTYP>FLIGHT_SAVEREPLICA</SAP:MESTYP>
<SAP:SNDPOR>SAPBXI</SAP:SNDPOR>
<SAP:SNDPRN>PRISM</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:RCVPOR>SAPIR1</SAP:RCVPOR>
<SAP:RCVPRN>IR1CLNT300</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
</SAP:IDocOutbound>
Do you see anything wrong or missing here. SNDPOR is XI port, SNDPRN is the source partner (file) and RCV... information is all the receiving R/3.
I am suspecting that something is missing either here or in the endpoint setup.
Also, in the TechnicalRouting I have this:
- <SAP:address version="20">
<SAP:systemKey>IR1CLNT300</SAP:systemKey>
<SAP:endpointType>IDOC</SAP:endpointType>
<SAP:url>IDOC://SAPIR1?RFCDEST=IR1300&DOCREL=&VERSION=3&SAPREL=46C</SAP:url>
</SAP:address>
Any issues you see here in url?
Also, when I look on the XI server, I do not see these files deposited anywhere- so they are going somewhere (as the status in IDX5 is successful)!
Do I need to activate any queues or triggers anywhere.
Can you please offer advice and help us out.
Thanks again.
Srini
[email protected]

ERROR"Unable to convert sender service to an ALE logical system,(Urgent)

Hi All when i am not giving the sender service address in the Receiver Aggrement i am getting this perticular 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_IDOC_METADATA</SAP:Code>
<SAP:P1>Transaction IDX1: Port SAPRP1, client , RFC destination contain errors</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Transaction IDX1: Port SAPRP1, client , RFC destination contain errors</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
==========================================
And if i am giving this one then i am not getting any such error rather i am getting another error "Unable to convert sender service to an ALE logical system" for this also i have checked the LS system name in the Adapter specific Identifier and the logical name are exactly same. But still i am getting 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>
=============================================
Still i am getting this error can anyone please let me know what to do now..??
Please treat this as urgent

Hi,
This error is caused when Sender System name does not match the logical system name of partner. As you mentioned you have done all the steps to ensure that, here's a checklist that could be helpful:
1. Check adapter specific parameters for sender system.
2. Maintain header mapping in receiver agreement and ensure that sender service name provided is same as business partner name required in R3 and business partner type is LS.
3. This may sound very basic, but ensure that checkbox for 'Apply control record from payload' is not checked and if it is then the values passed through payload are appropriate.
Hope this would be helpful.
Thanks,
Bhavish

ERROR" unable to convert the service as an ALE logical system"

Hello All,
In SOAP to IDOC scenario I tested the webservice with the client tool. Its hitting the integration engine but its throwing up an error" unable to convert the service as an ALE logical system". How can I maintain a logical system for a service as its outside our landscape. Can any one let me know how to proceed with this.
Looking forward to expert comments.
Thanks and regards,
Neelima

Hi,
Check this blog by Michal.
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
Regards,
Sudheer.

Regarding Error: Unable to Convert Sender System to ALE Logical System

Hi friends,
in File to IDoc scenario, i created a sender business system called bs_filetoidoc_send based on Standalone technical system and a receiver business system based on ABAP r/3 system. in my SAP IDES system which is dual stack (abap+java), XI client is 001 (LS: devclnt001) and r/3 client is 800 (LS: t90clnt090) i.e i'm posting idoc to t90clnt090.
I tried to send a text file. but while processing xml message in XI, i got an error saying "Unable to Convert Sender System to ALE Logical System".
then i searched the blogs and forum and found the solution. it was saying LS name was not assigned to BS bs_filetoidoc_send. so i went to SLD and tried to assign LS devclnt001 to my sender BS bs_filetoidoc_send, but got an error saying that "A business system with LS devclnt001 already exists". when i checked which is that BS, it is supposed to be the INTEGRATION SERVER itself with BS name INTEGRATION_SERVER_DEV.
then i configured my sender BS as INTEGRATION_SERVER_DEV itself which picked up the text file successfully and also receiver abap server received the IDOC with correct data and format with status 51. so scenario worked fine when i used my sender BS as INTEGRATION SERVER itself.
please clear my following doubts which arose after this scenario.
1) why the scenario didn't work when I used only standalone sender business system?
2) why should we assign a LS name of XI server to sender business system only in this scenario?
scenario worked according to my requirement, but using integration server itself as a sender BS confused though.
Many Thanks.

1) I can create any no of LS names using SALE
Yes you can create.
> 2) But I can assign a client to any one of those LS names (or 1 client will have only one LS name associated with it)
One Client will have one LS associated to it...and that can be any one of the LS..created.. use SCC4 to find the associated Ls for all the clients of a system
3) So anyways INTEGRATION_SERVER_DEV has to associated with the client 001 only, so finally I have to use INTEGRATION_SERVER_DEV only as my sender BS. Probleum is that I can't remove the LS name DEVCLNT001 from INTEGRATION_SERVER_DEV and assign it to bs_filetoidoc_send BS right. If I do so, I think I would get an error saying that INTEGRATION_SERVER_DEV is not associated with the LS name of client 001.
As the logical system defined in Partner profile is expected to arrive in Control record of IDoc..it should be passed in that...
Did u checked this blog../people/rajeshkumar.pasupula/blog/2009/03/16/unable-to-convert-the-sender-service-to-an-ale-logical-system so as per you need the explaination in the blog need to associate the logical system name .
HTH
Rajesh

ALE: Logical system

Hi
I want to send IDOCS from SAP(client100) to a non-SAP system through an RFC port.
I created 2 logical systems.
100SAP : Sending system
NONSAP : Receiving system
Am i correct to say that i need to assign LS-NONSAP to client100. or should it be LS-100SAP ?
Message was edited by: Giovanni Baumann
Message was edited by: Giovanni Baumann

Hai
Check the following Setting
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Thanks & regards
Sreenivasulu P

ALE logical systems for business service or process

Hi,
I am trying to send an IDOC into my R/3 system. It is the same IDOC type that I have sucessfully sent out to parties. All the config is in place for communicating with the system, because I have sent others IDOCs in the past. However, they always were sent from another R/3 business system. They processed sucessfully.
I am now trying to sending IDOC's from a BPM,as well as, from a business service. They are under the "With Party" section of the directory. These obviously do not have logical systems, so when I try to send the IDOC I get
"Unable to convert the sender service Purchase_Orders to an ALE logical system", where purchase_Orders being the name of the business serice.
How can I handle this problem?
Should I hard code values somewhere?
Which ones?
I have read the other posts for the error above, but my situation seems to be different.
Help!
Chris

Hi,
To solve your problem, here my solution:
1/ In your Business Process of your ID (configurator), go to menu "Service > Adapter-specific identifier" and in the part "IDoc Adapter", write your Logical System.
2/ Create this Logical System on your target system (R/3).
WARNING: XI allows you to used a Logical System for only one service (Business Process). Thus, if you are several interfaces, you must used different Logical Systems.
Mickael.

Error while assigning Logical System to Client

Hi,
I am trying to perfomr data transfer suing Idoc from SAP R/3 to PI.
For this, I have created a logical system PD1CLNT100.
But when I try to assign the client 100 to this Logical system through SALE, I ge the following error
"An entry already exists with the same key SALE"
but I am unable to see this entry in the client list in SALE.
Please tell me where is it picking the entry from?
regards,
Piyush

Hi Piyush Mathur SAP
Check once again for Client 100 ... there willl be entry (Assign the Logical System to Client)
Check in table V_TBDLS for Logical Systems..
T000 for Clients
Log out from the system and log in once again and check it....
i hope Above info helps you
Thanks
Ramesh

Unable to Convert Sender Service to an ALE Logical system

Hi,
I am doing a simple SOAP -> PI 7.11 -> IDOC scenario. All objects are created and activated. In testing I get an error
Unable to convert the sender service TemporaryDisconnection_Sender to an ALE logical system
Sender is a Business Service.
I search SDN and found this blog /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
I did the Compare with SLD for the Business System. But still the error comes.
In mapping I Disable EDI_DC40 segment.
Also find one suggestion which tells to change the Header Mapping in Receiver Agreement, what exactly should I put in Sender Communication Component of the Header mapping?
Thank you,
Pankaj.

Hi,
In this thread I could find a solution by Michal: Unable to convert the sender service to an ALE logical system
3. click on sender service (header mapping section) and select your business system that represents XI business system
Will try if it works for me also.
If there are any suggestions, then please do post.
Thank you,
Pankaj.

ALE logical system - File -- XI -- R/3 scenario

Hi
I have the following scenario which I'm trying to run.
File --> XI --> R/3 scenario.
I have created a sender agreement XID|ASN_out|NBD where XID is my XI 3.0 system and NBD is my R/3 system. I have also created an interface determination and receiver determination.
The following error is in transaction SXMB_MONI in my XID system:
"Unable to convert the sender service to an ALE logical system"
Both XID and NBD are business systems defined in SLD and they have both a logical system assigned.
Why do I get this error and how can I fix it?
Best regards
Göran
Message was edited by: Göran Westin
Message was edited by: Göran Westin

Ok. I fixed the problem.
In the Integration Builder - Configuration > Select business system of choice > Menu > Service > Adapter specific identifiers > IDOC Adapter > Logical system - got a value after reading/refreshing it from the SLD.

Steps to create a logical system for client 001.

Hi,
In client 000 go to transaction scc4. There you create your new client for sap netweaver abap trial version for BI?
Here, can you give me steps to create a logical system with client 001 using tcode scc4.
Thanks,
Kannan

hi
     First log on to SAP R/3 server connections Go to SCC4 in R/3 & in Scc4 BW server. A screen opens in that logical name of the system would be opened in both (R/3 & BW).
     Take notepad in it save .R/3 & BW logical names go to R/3 & click SM59 to create R/3 connections click then a screen opens gives BW logical name in RFC Destination option & give connection. type 3 & give some description & then press enter.
     You will get another screen under it then at target host gives BW server name we will get it from BW logon change ID, IP address option & give the system no. The system no go to logon pad just drag it then you will see the name.
     Then click on log on securities go to log on give BW server details like No, client user Password. Then save it then click test connection tab if there are errors then it gives yellow color if they are no error the whole thing come as white.
     Then click on the Remote Logon then we go to BW server give RFC SM59 & click create. Then give the server name which is at the bottom right corner give it then give the no, name, password in logon Security save it & test connection & then remote logon.
     R/3 - B W - R/3
     Logical connection source system connection is used to transfer the data from R/3 to BW. Go to BW system& click RSA1 go to source system option go to top to the source systems right click on it. Then click create then a screens opens then.
     PC Flat file , DB  Database
     Select the option manual then a screen appears RFC Destination, Logical source name then click OK then it goes to opens other screen save it test connection then remote login then it go back to the then a screen opens then click only activate.
     BW  RS1  SOURCE SYSTEM  CREATE MANUAL AUTOMATIC CELL
     R/3  Test connections login  back  replicate method  active data R/3 Source system you will able to.
regards
ashwin

Check and assign a logical system to client

Hi,
How to check and assign a logical system to clients (for example client number 100)?
Thanks & regards
Duypm

BD54- Create Logical system
http://help.sap.com/saphelp_sm32/helpdata/en/69/c24ca94ba111d189750000e8322d00/content.htm
This link also
http://www.sap-img.com/bc059.htm
Regards,
Subhash
Edited by: Subhash Chandra on May 14, 2009 10:21 PM

"Logical System" & "Assign Logical System to Client"

Hi Experts,
I'm new to Basis, I have the following systems installed:
1. EBP and SUS are installed in same server with different client:
    EBP: E01 with client 100
    SUS: E01 with client 200
2. ECC system is installed at a separate setver
    ECC: D01 with client 100
My question is, in EBP client which logical systems and client assigments need to be done?
What I confused is, for the EBP and ECC they have same client number 100, in EBP client , the client number 100
should be assigned to EBP or to ECC?
Kindly please guide.
Thanks and best regards
Jack

Hello Jacky,
                   You can assign the client number 100 to EBP and ECC systems, it doesn't create any problem. Because when you logical system in EBP, you need to create two logical systems one for EBP and ECC, but you need to assign client 100 to EBP only, same goes to the other side also.
Regards,
Prasanna

Logical system for client 001 for SAP NETWEAVER ABAP TRIAL VERSION for BI

Hi,
I have installed SAP NETWEAVER ABAP TRIAL VERSION for BI. In that I have to create logical system for client 001. I have taken a list of available clients from the abap R3 side. Here is a list of it.
Clients View
Cl. Name City Crcy
000 SAP AG Konzern Walldorf EUR
001 Auslieferungsmandant R11 Kundstadt USD
066 Test EarlyWatch Profiles Walldorf EUR
I cannot get inside the BW side for it asks me to create a logical system for client 001. What to do?
Kindly help me.
Kannan

hi,
? First log on to SAP R/3 server connections Go to SCC4 in R/3 & in Scc4 BW server. A screen opens in that logical name of the system would be opened in both (R/3 & BW).
? Take notepad in it save .R/3 & BW logical names go to R/3 & click SM59 to create R/3 connections click then a screen opens gives BW logical name in RFC Destination option & give connection. type 3 & give some description & then press enter.
? You will get another screen under it then at target host gives BW server name we will get it from BW logon change ID, IP address option & give the system no. The system no go to logon pad just drag it then you will see the name.
? Then click on log on securities go to log on give BW server details like No, client user Password. Then save it then click test connection tab if there are errors then it gives yellow color if they are no error the whole thing come as white.
? Then click on the Remote Logon then we go to BW server give RFC SM59 & click create. Then give the server name which is at the bottom right corner give it then give the no, name, password in logon Security save it & test connection & then remote logon.
? R/3 - B W - R/3
? Logical connection source system connection is used to transfer the data from R/3 to BW. Go to BW system& click RSA1 go to source system option go to top to the source systems right click on it. Then click create then a screens opens then.
? PC ?Flat file , DB ? Database
? Select the option manual then a screen appears RFC Destination, Logical source name then click OK then it goes to opens other screen save it test connection then remote login then it go back to the then a screen opens then click only activate.
? BW ? RS1 ? SOURCE SYSTEM ? CREATE MANUAL AUTOMATIC CELL
? R/3 ? Test connections login ? back ? replicate method ? active data R/3 Source system you will able to.
hope it helps u
Ramesh

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!

ALE logical system to client

Similar Messages

Maybe you are looking for