How to map IntegrationProcress to ALE Logical System Name

Hy,
i'm triying to send an Idoc from my IntegrationProcess MY_IP
to out Backend SAP System XX1.
Konfiguration has been done with an valid ReceiverAgreement.
But neverless i got the following error:
"Sender Service MY_IP cannot be mapped to an ALE Logical System"
1. Where do i specify this Mapping? (I tried Header Mapping ReceiverAgreement
without success)
2. In my message mapping EDI_DC40 has mandatory fields like RCVPRN.
But hardcoding the Receiver here cannot be the solution. Do the value
i map there do have any effect at all?
Thanks in advance.
Gunnar

Hello Nilesh,
you're right - now it works. I just defined any LS and SID. No the IDoc runs into the system, but cannot be processed since the originator is unknown. But this can be solved now with SALE and we20.
To be honest: there are so many blogs concernig this case. But i didn't find any which explains why the behavior is different when you send an IDoc from an Integration Process and what happens behind the scene. In the documentation
i didn't find anything at all...
Thank you very much.
Gunnar

Similar Messages

How to change or rename the logical system name T90CLNT090 IN BI 7

HI Expert's,
i am really digging for the solution of changing or renaming the logical system name technical name T90CLNT090.
in our company we are using ecc5.0 with bi 3.5 and ecc6 with bi 7. In BW 3.5 having a connection with R/3 and the technical name of the myself bw source system(logical system) is T90CLNT090.
In bi 7 also the logical system name is same as T90CLNT090. Because of the same system name(Logical name) it is not active in BI7 and also it's giving error when i am activating the DSO Object as Transfer structure prefix for source system T90CLNT090 is not defined.
because of this i am not able to create the source system between r/3 also.
so how to change this source system name for T90CLNT090.
regards
harikrishna N

Hi,
Pls follow this OSS note : 325525.
Note 325525 - Copying and renaming systems in a BW environment
Summary
Symptom WARNING: THIS NOTE HAS BEEN REPLACED. FOR MORE CURRENT AND MORE COMPREHENSIVE INFORMATION SEE NEW NOTE 886102.
You want to copy and or rename one or more systems (database or client copy). One or more of the systems is a BW system or is connected to a BW system.
Caution: This note only deals with problems that occur in the BW source system connections. Other problems that occur in the BW environment (indexes) are NOT dealt with. See URL http://www.service.sap.com/bw --> Services & Implementation --> System copy & Migration.
Other terms BW, source system, OLTP, database copy, client copy, system infrastructure, transport system, connections, RFC connection, trfc, transfer structure, IDoc, ALE customizing, logical system name, system changeability, renaming systems, system copy
Solution Several scenarios are possible in this environment. Find the scenario relevant to your situation below and execute the steps listed or read the note(s) specified:
Scenario 1) You do not want to copy a system but only want to rename one (changing a logical system name).
           Solution scenario 1): Execute Transaction BDLS both in the client to be renamed and in the connected BWs or BW source systems. To do this, see Notes 121163 and 369758.
           Check the RFC destinations in all connected BWs/BW source systems as described in Note 524554.
           Reactivate all partner agreements that carry the new logical system name after renaming.
Scenario 2) You want to copy the entire system infrastructure connected by the BW source system connections (that means the entire system group) by a database copy. SAP recommends this procedure for copying systems.
           Solution scenario 2):
If you want to rename one or more of the copied systems, then execute Transaction BDLS both in the client you wish to rename and in all the connected BW and BW source systems. See Note 121163.
                    Make sure that an RFC destination exists with the new logical name in every connected BW or BW source system.
                    Reactivate all partner agreements that carry the new logical system name after renaming.
Change the hosts in the appropriate RFC destinations so that they refer to the correct computer. For this, see Note 524554.
Scenario 3) You want to copy a single BW system of the group by database copy.
Scenario 3)a) You only want to exchange the hardware of your system but do not want to rename the system.
                     Solution scenario 3)a): You do not need to execute follow-up work regarding the system connections, except for adjusting the IP address in the RFC destinations of the connected system.
Scenario 3)b) You want to keep the original system of the copy so that you have two systems after copying.
                     Solution scenario 3)b): See Note 184754.
Scenario 4) You want to copy a single source system of the group by database copy.
Scenario 4)a) You only want to exchange the hardware of your system but do not want to rename the system.
                     Solution scenario 4)a): You do not need to execute follow-up work regarding the system connections, except for adjusting the IP address in the RFC destinations of the connected system.
Scenario 4)b) You want to keep the original system of the copy so that you have two systems after copying.
           Solution scenario 4)b): See Note 184322.
Scenario 5) You want to import a client copy in a source system.
           Solution scenario 5): See Note 325470.
Thanks & Regards,
Suchitra.V

How to get RFC Destination and Logical System name dynamically

Hi all,
I have a RFC FM written in CRM. I need to call this FM in R/3. So, i use the syntax " Call function <func> destination <destination name>. My problem is that i need to fetch the destination name dynamically..
There is a way to do so in CRM which is as follows:
DATA: lt_siteselect TYPE TABLE OF siteselect INITIAL SIZE 0,
           ls_siteselect TYPE siteselect.
CALL FUNCTION 'SMOF0_READ_SITESELECT'
    TABLES
      to_siteselect = lt_siteselect.
READ TABLE lt_siteselect INTO ls_siteselect
         WITH KEY sitetypeid = cl_smw1_siteprovider=>c_sitetype_r3oltp.
The above piece of code returns the site and also takes care of the client you are currently working on. But the specified FM is present only in R/3..
I want to achieve the functionality fulfilled by the above code in R/3.
Kindly help.
Useful answers will be rewarded.
Thanks in advance,
Karan Merwana
I can not use FM LOG_SYSTEM_GET_RFC_DESTINATION as for that i need to provide the logical system name. And the logical system name would be different for different clients.
Message was edited by:
        Karan Merwana

For those referring this thread later, I could not find a solution to this and ultimately had to do away with hardcoding of system names based on the DEV, Q, and PROD system names.
If anyone does manage to get a workaround, please let me know.

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]

Clarification Regarding Logical System Names

HI all,
I read the blogs regarding Logical System Name, even I am having the some problems in my system.
For PI system client is 100.
R/3 System Client is 100 is created.
IN PI when I checked the sale->basic setting-> LOgical Settings-> Assign Logical Systems
I found there is only one client 100, and it is having the same logical system name as 'PICLNT100'.
In SLD one Business System is created for Client 100 and having the Logical System Name is 'PICLNT100'.
When I checking in the R/3 system that logical system Name ('PICLNT100') is not there and for r/3 client 100 having the different logical system name.
IN ID when I found the Goto ID->File Buinsess system and Menu ->Services->Adapter Specific Identifiers->Logical Ssytem,
It is different from the SLD logical System Name.
How Can I know in PI, that Logical System is belongs to r/3 or PI client 100,
when I running the sceanrio it is giving error as ATTRIBUTE_INV_SND_SERV while doing the file to Idoc scenario.
How I have to maintain the logical system names in this case?
please help me in this.
Regards,
Sree

hi.
each r3 system has his own SLN (PI,BI,ECC,etc). this name identify each R3 sytem.
http://help.sap.com/saphelp_nw04/helpdata/en/78/217dc151ce11d189570000e829fbbd/frameset.htm
IN ID when I found the Goto ID->File Buinsess system and Menu ->Services->Adapter Specific Identifiers->Logical Ssytem,
to export data of your R3 system to SLD, just do it from TCODE RZ70 in your r3 system, not PI.
once you configure it all data from r3 system is exported to SLD.
if the SLN does not match in Adapter Specific Identifiers->Logical Ssytem, edit the Bussines System (press in the little pencil) go to Adapter Specific Identifiers->Logical Ssytem and prees in the little hand icon. in the SLN in not refresh, go to menu enviroment--> CLEAR SLD DELTA CACHE. and repeat the steps before.
each time you send data to an R3 system and the sender system is a legacy. in your receiver communication channel>header mapping>sender system--> select the PI Bussines system and try again.
hope its helps
Rodrigo
PD: rewards points if useful

Changing Default logical system names of a model.

Hi
    How could i change the
     Default logical system name for model instances:
     Default logical syatem name for RFC metadata:
    values for existing model? without recreating the model.
     Thanx

Hi shah kond,
you can change rfc destinations of model in 2 differnet ways.
firs one: right clcik on project
          from the context menu select propeties
          it will open a dialogbox from that select dynpro references then click on jco references tab
by using add and remove buttons u can add and remove joc destnations
2.expand ur model class double click output class.now seelct properties view.there u can change the jco destination
hope this will use ful for u
Regards
Naidu

Defining Logical System name for ALE using T.C- SPRO?

Hi,
Can anybody tell, how to define logical system name using T.C SPRO?
Where can I find the "Define Logical System for ALE"?
Thanks
Balaji

HI,
Use the SALE transaction , there you can have all steps clearly,
please see the below links
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping
Regards
Chilla..

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.

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.

Unable to convert the sender service BS_PARTNER to an ALE logical system..!

Hi All,
File to IDoc scenario.
1. Business system is correct because its working for other scenarios.
2. I checked Adapter Specific attributes in Business service and given Partner number which in maintained in WE20 for the partner in R/3.
3. Refreshed cache.
But still... its showing the below 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_INV_SND_SERV</SAP:Code>
<SAP:P1>BS_PARTNER</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert the sender service BS_PARTNER to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any idea what might be wrong?
Regards
Deepthi.

Hi Experts,
Could you please help me to fix this.
SCENARIO: SAP - IDOC -
> XI -
> SOAP Adapter (Webservice)
Workaround:
1. Verified Adapter Specific configurations and its fine with same Logical system in SLD and ALE service.
2. Header mapping in Receiver com channel : Sender service and Receiver Service is assigned
3. Identifier Tab in comm channel details: Its empty - no values.
SXMB_MONI :
Error Details:
<?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="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>CAPTOR3_PRU</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service X12345X to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks in Advance,
Sunil.

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

Hi,
I have a JMS (Party) --> PI --> IDOC scenario.
Party: ABC_Party
Service: ABC_Service
I am getting the error Unable to convert the sender service ABC_Service to an ALE logical system when I test the scenario using RWB -> Component Monitoring -> Integration Engine -> Test Message.
I have already done the below settings:
1) Defined Header Mapping in Receiver Agreement for IDOC (Sender Party, Sender Service and even Receiver Service are specified)
2) Business Component (ABC_Service) -> Adapter Specific Identifiers -> mentioned details for SAP (IDOC) system.
The scenario works perfectly fine for a party-less communication JMS -> PI -> IDOC
Have already seen:
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/rajeshkumar.pasupula/blog/2009/03/16/unable-to-convert-the-sender-service-to-an-ale-logical-system
Thank you,
Pankaj.

You need to create party if its a B2B scenario
Under Identifiers
under agency select any standard agency , scheme name will automatical;ly get populated and name you can give manually as sender name
Please refer this for more details
http://help.sap.com/saphelp_nwpi71/helpdata/en/b9/64663c7a6c2545ae292fb26d8c33c4/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/81/104bb1fbab254c8644877c7f856bbf/content.htm
Re: Party Configuration
In case of cross company process it is required
Regards
Ninad
Edited by: Ninad Sane on Nov 18, 2010 11:17 AM

Unable to convert the service as an ALE logical system

nHi to All..
I'm facing a problem in one scenario IDOC to RNIF. I got this problem "Unable to convert the sender service to an ALE logical system. In that Interface is working properly but the thing is Acknowledgement is showing error and when I was triggring the IDOC from ECC at the time message Data Receiving successfully but coming to Acknowledgement Am getting ERROR. Any one can please do the needful for this.
Note:- Sender is Business system and Receiver is Business Service
Thanks and Regards
Srinivas

Hi srini
Receiver System is SEND the acknowledge to ECC here only we are facing the problem
help me uderstand correctly ...
your asyn interface is ECC(sender)-to- Bservice receiver .(works fine)
now Bservice (sends an ACK)- to -ECC (receiver) - do u have other asyn interface for this .. must be.
if not this means you are trying out sync scenario in which you are expecting the ack to go back to ECC syn (which i think not possible or u need to use BPM as the idoc interface will be always asyn).
try giving the LS name in the Bservice , not in the Bsystem as you mentioned.or
open your receiver agreement and select header mapping - Sender service
choose your PI's business system
Regards,
Srinivas

Problem converting Integration Process to ALE logical system(acknowledgmen)

Hello,
I have a scenario where a sender SAP system sends an IDoc via an Interface Mapping to an Integration Process.
This worked perfectly fine on our development environment, but after transporting the scenario to our quality systems I got the following acknowledgement error:
Unable to convert the sender service <i>name of integration process</i> to an ALE logical system.
What could be the reason for this? We have a logical system on the sender SAP system set up for the XI system itself but not for the Integration Process.
We also use SYSTAT IDocs and there we set the the logical sender system name to the logical system for SAP XI and not for the integration process.
Is this also necessary for acknowledgements? Where could this be done. Strange thing is that it works perfectly fine on our development environment.

I raised the same question a few months back.Answer to this question is in the same thread.
Idoc Acknowledgements - Logical System Name
You will have to select option "Restore Original Parties for Idoc Acknowledgments " in the Acknowledgment Idoc adapter.
Regards
Bhavesh

Unable to convert sender service BPM_Name to an ALE logical System

Hello ,
While sending from BPM to R/3 ( IDOC) i am getting the following error :
"Unable to convert sender service <BPM_Name> to an ALE logical system"
Please kindly advice,
Reddy

Hi Bujji,
I just remembered that you have to maintain your adapter specific parameters for your business process. The side effect however is that you have to define the business process name as logical system in your receiving SAP system and that you have to maintain partner profile settings.
The answer to your question is there in this Blog:
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
If the above solution doesnot work.....
You can also try this, don't enter the "adapter specific settings" on the Integration Process. Instead enter a "Header Mapping" Sender Service in the Receiver Agreement. this should be the real sending system.
When you enter "adapter specific settings" in a BPM, the receiving SAP systems ALE layer thinks the sending system is your BPM - using the method discussed here we are overriding that so that ALE see's that its communicating with the real sending system.
I hope it helps....
Regards,
Abhy
Message was edited by: Abhy Thomas

How to map IntegrationProcress to ALE Logical System Name

Similar Messages

Maybe you are looking for