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.

Similar Messages

What is logical system in ALE

Dear all
I still confuse with Logical System in ALE where we already have Client.
And I see that relationship between Client and Logical System is 1:1
So why we need Logical System instead just use Client ?
Regards,
Halomoan

I think this is what you want to read:
A logical system is an unique identifier of a system/client combination.
That is why SAP recommends to use the notation <SID>CLNT<CLT> to set the logical system. For example, assume you have client 400 for system QA1 and you have client 400 for system DV1. Then the logical system name would be:
for QA1/400: QA1CLNT400
for DV1/400: DV1CLNT400
The logical system is used in the IDOCS that you transmit from one system to the other. So with this, you know the source system of the IDOC, and this tells you where the business document was created.
Using only the client as identifier is not enough, because you can have the same client number in several systems.
Nevertheless, you should read the documentation!!
Regards,
Juan

BPM--cannot convert sender logical system to ALE

Hi
My Scenario is file-bpm-idoc.. Where i am getting an error saying "cannot convert sender logical system to ALE" for the BPM.
i tried entering the logical system for the BPM in adapter specific attributes but it says logical system is already being used by some other service..
So i tried header mapping in receiver agreement now the messages are failed at the intital stage before entering the BPM only only saying cannnot find recvr agreement..
My sender system BS_EXT_100
BPM IP_calldoc
Recvr system BS_EDCR/3_200
i did the header mapping for recvr agreement of BPM by selecting the sender service and entering "BS_EXT_100"
Where am i going wrong...

solved it myself.. Thanks

Why do we create logical systems in ALE?

Hi All,
i got this question in interview.
Why do we create logical systems in ALE?
Thanks & Regards
suresh

Hi
In addition to above .
A logical system is used to identify an individual client in a system, for ALE communication between SAP systems. That's why you see a field for 'logical system' in the client master data in SCC4 (table T000).
/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
http://help.sap.com/saphelp_nw04/helpdata/en/b5/1d733b73a8f706e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/69/c24ca94ba111d189750000e8322d00/content.htm
http://72.14.203.104/search?q=cache:J-uDLyT0w54J:www.topxml.com/biztalkutilities/walkthroughs/SAP%2520Configuration.pdfwhatislogicalsystems+(SAP)&hl=en&gl=in&ct=clnk&cd=5
http://help.sap.com/saphelp_nw04/helpdata/en/78/217dc151ce11d189570000e829fbbd/content.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/d7/9c73631d6c11d2a56e0060087832f8/content.htm
This guide is really good shows step by step procedure.
http://72.14.203.104/search?q=cache:Xyl0zxpyEXsJ:www.sappoint.com/abap/ale.pdfLogicalsystem(ALE)&hl=en&gl=in&ct=clnk&cd=9
for one client config
http://www.sappro.com/downloads/OneClientDistribution.pdf#search=%22Logical%20system(ALE)%22
Please reward for the same.

How to create Logical System for ALE?

Hi All,
I'm an abaper and want to create Logical System For ALE. When i tried to make it using Tcode: SALE, msg appears that "Caution: The table is cross-client", when clik on continue button it shows "You are not allowed to change cross-client customizing". Help with proper documentation.
Thanks in Advance.

Hi,
what you did is correct but you don't have the authorization for cross-clients in your sever.First take the authorization for cross-clients then follw the steps
Here i am giving link go through that and do practice,
http://www.****************/Tutorials/ALE/MaterialMaster/Distribute1.htm
http://www.****************/Tutorials/ALE/ALEMainPage.htm
Reward if it useful
lakshmi.

Logical systems for ALE

HI all,
I'm configuring for an IDoc to be generated and downloaded to a file via a file port.
This IDoc is of message type PAYEXT.
The file is to be sent ot the bank via the meansa of third party software.
Do I have to create logical systems for these? Or only the outbound logical system?
Do I also need to set up the distribution model , and if so, how far do i need to set it up?
Points wil be awarded. Thanks!

Hi
Use BD64 Tcode to setup distribution Model
Define the 2 logical systems.
see the flow:
Outbound:
Step 1. Application document is created when transaction is saved.
         2. Message control is invoked.
         3. Messages are processed by system.
         4. Messages are Edited (if desired).
         5. Output (ALE / EDI) is checked
         6. Validate against Message control record from Partner Profile
         7. Application Document is saved.
         8. Entry NAST table is created for every selected output program
              along with Medium & Timing.
         9. Check for Process Immediately .
                 If (yes)
                   Determine Processing Program from TNAPR Table.
                 ELSE
                   Execute RSNASTED Program.
       10. Read Partner Profile to determine Process Code.
       11. Process Code points to the Function Module & Invoked.
       12. IDoc is generated.
       13. Check for ALE Request.
                    if (Yes)
                        Perform Filters, Conversions, Version Changes etc.
                    Else.
                        IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
        2.   Subsystem calls Functional Module                                 EDI_DATA_INCOMING from startRFC program.
         3. Data in Control Record is validate against the Partner                       Profile.
        4. IDoc is generated in Database and syntax check is                      carried out.
        5. IDoc file is deleted once file read.
        6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
                   7. Check for Process Immediately.
               If NO
                 Execute RBDAPP01 Program
               Else
                  Read Process Code from Partner Profile
                       Process Code Points to Function Module
                 Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Reward points if useful
Regards
Anji

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

Setting up Logical system in ALE Config !

Hi,
I have set up the ALE logical system in SAP to transfer data. Basically RFC destination setting. While I am trying to test the connection, I am getting an Error Program INBOUNDASYNC not registered.
Could any one help me out here.
Thanks,
Senthil

Hello,
Please make sure you have completed the starting of SMD agent also after the setup, u can find it in the guide.
also check the p4 or Https port number is correctly mentioned.
The user and pass mostly would be that of SMDadmin, created during the setup, or u can use SIDADM which will wrk fine.
sometimes root needs to be used as even sidadm can be restricted in ur envt. ( just in case).
Regards,
Kaustubh.

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

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..

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 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

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.

In ale client and logical system

Hi,
do we need to assing logical system to client in ale configuration.
thanks,
Jigar

Hi,
Yes, you need to define and assign logical system for ALE client.
Path: SALE -> Basic Settings -> Logical Systems -> Define Logical System
Path: SALE -> Basic Settings -> Logical Systems -> Assign Logical System to Client
Regards,
Ferry Lianto

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*

Logical systems in ALE iDoc

Similar Messages

Maybe you are looking for