Logical System in file 2 idoc

Hi
I am developing an scenario of file to idoc.
My problem is, when it is generating the idoc in target system, the Parner Number in control record is filling with the logical system name given when creating the business system.
I tried changing the logical system name with actual partner number which I want but giving an error ' The selected integration server already has a business system with logical name "pidclnt001". Select a different integration server or change the logical name. '
Can anybody advice me, is it not possible to create two scenarios to send same Idoc to same system ?
Regards,
Shylesh

Hi Shylesh !
You need to enable the header mapping option in your receiver agreement to overwrite the Logical System name that is sent to the R/3 destination system...which now is the Logical System name linked to your sender system (info is in SLD if is a business SYSTEM or in the Adapter Specific identifier attributes if it is a business SERVICE)
You cannot have more than 1 business service/system with the same Logical System name...but you can overwrite the sender logical system name that arrives to the destination R/3 system using the header mapping section of the receiver agreement as noted above.
Regards,
Matias.

Similar Messages

Logical systems in ALE iDoc

Hi,
For exchanging data between two systems(not between two clients of the same system) using ALE iDoc , logical systems should be maintained in both the systems?
For eg: there are two systems, system A and system B.
i have maintained the logical systems as SYSA (for system A) and SYSB ( for system B) in the system A using the transaction 'SALE'. Should this need to be maintained in system B also?
Thanks & Regards,
Soumya.

Hi,
In both the systems you have to Define the Logical systems,
but in you assign only one to the client,
i.e. in system A you assign the Logical Sytem of of A to the Client in SALE
transaction the same goes for B.
and you don't need to create a distribution model for both the systems,
you can create it in one system and send it to the other system.
Regards,
Samson Rodrigues.

Filt to IDoc: cannot convert sender to ALE logical system

Hi there,
i have used forum search for my issue, but could not figure out the issue by myself so far.
I tried to read a file into PI 7.0, map to and IDoc and send IDoc to SAP system. I have the following configuration:
Sender: SYSTEM_A
---Logical System <none>
Receiver: SYSTEM_B
---Logical System: EIECLNT300
the IDoc i'm sending looks like this (most of them dummy values):
<?xml version="1.0" encoding="UTF-8"?>
<ORDERS05>
<IDOC BEGIN="value2">
---<EDI_DC40 SEGMENT="value2">
<TABNAM>value2</TABNAM>
<DIRECT>value2</DIRECT>
<IDOCTYP>value2</IDOCTYP>
<MESTYP>value2</MESTYP>
<SNDPOR>EIECLNT300</SNDPOR>
<SNDPRT>value2</SNDPRT>
<SNDPRN>PITCLNT001</SNDPRN>
<RCVPOR>value2</RCVPOR>
<RCVPRN>EIECLNT300</RCVPRN>
---</EDI_DC40>
---<E1EDK01 SEGMENT="value2">
---</E1EDK01>
</IDOC>
</ORDERS05>
PITCLNT001 is the logical System name of PI. Do i need to configure "PITCLNT001" as logical system at SYSTEM_A (besides, thats not possile)?
regards,
MS
Edited by: Manuel Schlestein on Jan 28, 2009 10:39 AM
Edited by: Manuel Schlestein on Jan 28, 2009 10:40 AM

Hi
Create a logical system for SYSTEM_A in SLD (you can give some string) and create that same logical
system in IDOC side (SALE).
Thanks
Prasad Nemalikanti

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: Receiver Service Cannot be converted into an ALE logical system

While doing scenario FILE to SAP R/3 by using BPM we get following error message:
<IDOC_Adapter> Attribute_INV_REC_SERV
SAP system is not able to receive the output.

Hi,
Goto Integration directory.
Click on your integration Process ( imported BPM).
Then check the Service in the menu bar of the Integration process.
You will have adapter specific paramters.
Give the logical system name of PI for the integration process.
This name will be used as the logical system when sending IDOC.
Hope this helps.
Regards,
Viany.

Local logical system is not defined

Hello
We are trying to setup a logical system - created or defined the logical system
when we try the BD64 it gives out the error "Local Logical system not defined"
I am using ECC 6 version
IS there any way to bypass and do the setup ?

HI Anil,
Best Methodology for creating a RFC Destination that also includes setting up Logical System is:
Use Transaction -> SALE /b]
1) Define Logical system :
Select Idoc Interface / Application Link Enabling (ALE) -> Basic Setting -> Logical System -> Define Logical System

2) Assign Client to Logical system:
Select Idoc Interface / Application Link Enabling (ALE) -> Basic Setting -> Logical System -> Assign Logical System to Client
3) Create RFC Destination: T-CODE (SM59)
Select Idoc Interface / Application Link Enabling (ALE) -> Basic Setting -> Communication -> Create Rfc Connection
Follow steps in sequence. Hope it answers every thing.
Cheers,
*RAJ*
*POINTS IF FOUND HELPFULL*

Error "Unable to convert the sender service to an ALE logical system"

Hi,
I send I message from XI to R3 and I get the error "Unable to convert the sender service to an ALE logical system" in transaction "sxmb_moni". I've configured the idoc-adapter, as following:
-I have created a business system "r3sys_bs" with a logical system "r3system". This business system is the idoc-adapter. This logical system is also created in transaction "bd54". In the ID I have assigned the business system the logical system (adapterspecific identification).
So, this error still appears.
Can anybody help me please?
Regards
Stefan

Hi,
our scenario is JMS --> XI --> IDoc
so, I have created a business system "jms_bs" without a logical system in sld, that I use for the jms-connection to another software. so, the business system is a "third party".
Then I have created a business system with assigned logical system for the IDoc-Receiver as I in my first posting mentioned.
Which of both business systems need a logical system?
Thanks
Regards
Stefan

XI 3 File to IDoc scenario - Still referencing Old Logical system

Hi
Dont know if you can help. I have a file to idoc scenario using XI 3 to R/3 4.6c system.
I had the interface working from a third party system XMLHUB to SAP R/3. The Logical system name for the XMLHUB was XMLHUB01 in the SLD which I have set up as a partner profile in R/3. I have recently changed the logical system name to XMLHUBDEV01 in the SLD and created that logical system in R/3 and changed the partner profile to XMLHUBDEV01.
Unfortunately in the sender information of the IDoc the partner number is still XMLHUB01 and not XMLHUBDEV01. I don't understand where this partner is sent from to get into the control record of the IDoc.
I have cleared the SLD cache in both the Repository and the directory. Is there somewhere else I should be looking? Any help would be appreciated.
Regards
Daniel

hi daniel...
this thread wud answer ur query....
Re: IDOC Payload
regards..
vishal

Integration server as logical system in IDoc to file scenario

Hi,
Will we configure integration server as logical system in IDoc to file scenario or the RFC destination related to the port will be suffice?
For which logical system will the outbound partner profile configured?
Regards,
Gajendra.

Hello,
I feel that the RFC destination linked to the port is the key here.
Because the scenario (IDoc to File) works in both the cases:
Case 1: Used the logical system as Integration server
Case 2: Used the logical system related to the file (third party) in the SLD.
In both the above cases the RFC destination points to the integration server.
Is this the case that in the XI scenarios (where IDoc are sent) the logical system name in the partner profile is just dummy and has not much significance??
It is the port that matters and once the Idoc reaches XI the routing takes place based on the configuration in ID.
Thanks.
Regards,
Gajendra.

IDoc Adapter - Logical System - File to IDOC configuration

I have a scenario reading a File ->XI->IDoc in R/3. I'm looking to have the control record parameter for SNDPRN reflect the Environment dealt with. I unchecked the 'Apply Control Record Values from Payload' & 'Take Sender from Payload' boxes but the problem I'm getting is that the system is reading from the business service (IDoc Adapter - Logical System) and feed it in the Partner Profile in the IDOC. This means that I should all the time redefine 3 this Logical System in config before transporting my scenario from DEV/QA/PRD. Any idea how I can avoid this kind of 'hardcode' ?
Thanks

Hi,
Why u r using three different LS can't u use only one LS and send all the IDOCs to same LS. That will ease ur task.
Do let me know why u r going for three different LS.
In the file r u getting any data which will help u to identify that this file is for which LS. IF that is the scenario then u can use the value mapping and based on the value which is coming in file u can map it to the IDOc filed which u have mentioned and in the configuration it will take the respective configuration.
Thnx
Chirag

Where to define third party logical system name in file to idoc scenario

Hi Friends,
I am shalini shah.
I have one doubt, where I can define the logical system name in File to Idoc scenario.
I created Logical system for R/3 system in SALE t.code, but where to define the Third party logical system ,
In SALE or any where.
Please give me solution.
Warm Regards,
Shalini Shah

Hi Shalini,
You need to create Business system in SLD and import the business system in ID.Then u will start with the configuration.
Just refer the below link for configurations with step by step solution.
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
Thnx
Chirag

File to idoc scenario . how to create logical system

logical system asking user authorization what should i do.
what should be logical for whic we should degine partner profiles
apoclnt800 or xi7clnt001

Hi,
The partner profile to be maintained in we20 (in backend systems -ECC/CRM etc) should be based on logical system for the sender.
For ex: Src (File) -> PI -> Tgt(ECC)
In SLD you have created Technical System(TS) and Business System(say BS) for Src. Also a Logical System name (Say LSNAME) is associated with BS.
In ECC, goto tcode - sale, create a logical system of name LSNAME. Now goto we20 and create a partner profile of name LSNAME. Provide the message type of Idoc in the required place.
Souvik

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.

Logical System for R/3 IDoc processing

Is there a way to use one logical system when data is coming from multiple sender communication channels?
We get data from several MQ Queues via JMS Sender Communication Channels. There is a separate queue per plant. No matter which queue a file comes in on, it needs to create the same IDoc type in R/3. So, they all need to be assigned the same logical system. Is this possible?

It is possible in the reciever agreement to define which service the message should come from.
See http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
Here you can make a header mapping and define which service you want the message to come from.

Idoc Acknowledgements - Logical System Name

All,
Stuck with a few issues with Idoc Acknowledgments which I hope SDN can help me with. For ease of understanding the problem, am splitting this into 2 Scenarios ,
Scenario 1
SAP R3 (Idoc ) - XI - File ( Business Service)
R3 Triggers Idoc to XI and XI sends this as a File to the target Application. AleAdudits can be sent back to the R3 system as shown in <a href="/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc">this</a> blog by Saravana by adding the Logical System Name to the Business Service.
Issue :
R3 has configured Partner Profile with respect to XI and this cannot be changed. To send the Idoc Ack's back to R3 we need to add the Corresponding Logical System Name to the Business Service.
The problem is - what if the Idoc is to be sent to 2 Different Business Service / Systems. The R3 expects an Acknowledgment with XI as the sender partner but we cannot share the same logical system across different Business Systems / services . The easiest solution seems to be to create different partner profiles in R3, one for each Business System / Service. But this is not possible currently.
Scenario 2: 
R3 - XI - BPM - Target
Idoc triggered from R3, are sent to a BPM and then from the BPM to a file. Everything works fine.
But, the problem lies that when the Ack needs to be sent back to R3, The ack errors out because no Logical System Name is associated with the BPM.
We do not want to add another logical system name to the BPM and thereby create another partner profile and the problem is similar to Scenario 1.
Solutions Explored
1. In the ACK_IDOCAdapter , I tried to select option Take Sender From Payload and Take Receiver from Payload.
But this does not seem to help. I can see the trace in MONI saying the ACK_IDOC adapter is choosen to send the ack back to R3 , but it does not take the Partner Names from the payload of the AleAdudit and errors out with error Unable to convert..
2. As this AleAduit is sent from XI back to R3 and is not a R3 (AleAduit) - XI - R3 (aleaduit) case, adding a entry as shown in Section 6 in
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb">this</a> document will not help.
Has anyone tried something of this sort. Any known solutions?
I hope the description of the problem made sense, if no, do let me know.
Regards
Bhavesh

Bhavesh,
Your problem as i understand -> The problem is - what if the Idoc is to be sent to 2 Different Business Service / Systems. The R3 expects an Acknowledgment with XI as the sender partner but we cannot share the same logical system across different Business Systems / services . The easiest solution seems to be to create different partner profiles in R3, one for each Business System / Service. But this is not possible currently.

If the IDOC is sent to 2 different business services/systems/Integration Processes, then it is very logical that an ALEAUDIT be sent for each of these business systems/services. Ideally, you SHOULD NOT look at sending a common ALEAUDIT for different recievers in XI, the reason being, failures could happen only for one receiver and NOT for others. Failure could be in the mapping/content conversion. I am assuming here that you are configuring XI to send back "ALEAUDITs" only for System Error Acks(hoping it is possible, since i see 3 XXXs in the IDXNOALE table).
So, it is logical that you configure a different LS in R/3 for each reciever system/service/IP, all these LS's will have one entry for ALEAUDIT in the Inbound params entered in WE20.
If your intention is to send ALEAUDITs back only in case of errors, it makes sense to create an entry for each receiver in R/3. If not, then it is a limitation.
Regards
Saravana

Logical System in file 2 idoc

Similar Messages

Maybe you are looking for