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
Similar Messages
-
Once again: Unable to convert sender service to an ALE logical system
Hi,
I know there's a lot of threads regarding that error but I didn't find one that fits to our current scenario:
IDoc -> XI -> File
We have checked if the logical system name in SALE (of sending system) fits to the one in the business system and it does now.
It didn't fit at first but we've changed it in the SLD and reimported the business system.
We still get the same message:
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:Stack>Unable to convert sender service to an ALE logical system</SAP:Stack>
There is no logical system entered in the receiver business system. Do we need that? But of which logical system?
Thanks for any advice
KarstenHi,
Acknowledgments
Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender.( Ex : Idoc----File). Here by default Idoc has the inbuilt feature of requesting the Ack.
Acknowledgments are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments.
Sender adapters of the Adapter Engine do not request any acknowledgments
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
Regards
Seshagiri -
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" ?>
- <!-- Call 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_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" ?>
- <!-- Call 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 />
<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 urgentHi,
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 -
Getting error message ' Unable to convert sender service to an ALE logical
Hi,
I am using idoc to file.
and my xi system is working fine. at sudden when i process one idoc . I got this message.
Unable to convert sender service to an ALE logical system
Here in monitoring, i am able to see the success falg but in acknowledgement column, i see system error..
I did no change in configuration.
Your inputs will be appreciable.Hi,
Also, is it possible that the XI system was recently upgraded?
As you indicated that no config changes were done, therefore, such error should not just pop up with no reason.
In an earlier release of XI (sorry I cannot recall the SP level), IDOC ack was not provided. However, in a later release, it is the default.
Regards,
Bill -
Sender Logical system lost in BPM
Hi, we have the next scenario:
3 Sender Business Systems(file)->BPM->R/3System(IDOC).
We want that the inbound idocs arrive to R/3 with their corresponding Sender Logical System.
The problem is that the idocs arrive with the Logical system of BPM. I can do a header mapping, but the idocs arrive with one static Logical system, I've lost the information about the original sender logical systems.
What are my alternatives ?.
1- Make 3 'little' BPMs after the general BPM ?.
2- 'Tri-peat' the general BPM?
Thanks,
Franciscosolved 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
sureshHi
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. -
BI 7.0, BDLS is not converting all logical systems for datasources
Hello all,
We have refreshed an ECC system, and during the post steps in BI, we were running into issues.
We've ran BDLS to convert the logical system from ECCCLNTXXX to ECCCLNTYYY, but it's was not converting for several datasources.
One in particular was causing several problems, and terminating the conversion.
0FC_CI_01. It is still hanging on to the old logical system. BDLS terminates with the following information:
Short text:
Active version of emulated 3.x DataSource 0FC_CI_01 cannot...
Basically, the exact symptom of Note 936644.
Eventually, through a series of trials, we discovered we could assign non-active sourcesystem/logical system combinations to the objects. As a result, we deleted the source systems entirely, ran BDLS to the ECCCLNTYYY, then recreated the sources.
This finally worked. What I need now is a root cause. Why would BI refuse to change the logical system of an object to an active one, but have no problem with an inactive?Mike,
After running BDLS, you need to replicate the source system in BW, change the contents of the target host and fields for all R/3 and Data Mart(note 184754). Update the target BW system name in table T000 using SM30. Change logical system name in all BW tables using BDLS (note 325525)
Refer to the below doc for detail. Also refer to note 886102.
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/805eefcd-5428-2d10-c0ab-dc27a95b2c81?quicklink=index&overridelayout=true]
Below note talks about similar issue.
How to change all infosources to the new source system automatically
Hope this helps. -
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. -
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,
HalomoanI 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 -
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 AMHi
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 -
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. -
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. -
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,
SenthilHello,
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. -
Not converting the logical system through BDLS
Hi Experts,
I did the system copy of BI system from production to developemnt
To change the logical system in RSA1 --> Source systems
I have choose client role as test in scc4 and in tcode BDLS i have given the old logical system name new logical system name
after completing the job RBDLSMAP i checked in the RSA1 there is no change in logical sytem
i got the following message
SM37 log
Job started
Step 001 started (program RBDLSMAP, variant &0000000000005, user ID ABCD)
Logical system name ABC500-1 does not match SAP's recommendation
Job RBDLSMAP no longer exists
Converted table: 'RSSTATMANSTATUS'; number of changes: ''
Converted table: 'RSSTATMANSTATDEL'; number of changes: ''
Converted table: 'RSSTATMANREQMAP'; number of changes: ''
Converted table: 'RSSTATMANREQMDEL'; number of changes: ''
Converted table: 'RSSTATMANPSA'; number of changes: ''
Converted table: 'RSMDATASTATE_EXT'; number of changes: ''
Job finished
Spool log
Table Name Field Name Number of Relevant Entries Number of Converted Entries
/BI0/ABP_CUST00* LOGSYS 0 0
/BI0/ABP_CUST40* LOGSYS 0 0
/BI0/ABP_VEND00* LOGSYS 0 0
/BI0/ABP_VEND40* LOGSYS 0 0
/BI0/ACDS_DS0400* LOGSYS 0 0
/BI0/ACDS_DS0440* LOGSYS 0 0
/BI0/ACDS_DS0500* LOGSYS 0 0
/BI0/ACDS_DS0540* LOGSYS 0 0
/BI0/ACLM_DS0300* CLM_FISY 0 0
LOGSYS 0 0
/BI0/ACLM_DS0340* CLM_FISY 0 0
LOGSYS 0 0
/BI0/ACLM_DS0600* CLM_FISY 0 0
LOGSYS 0 0
/BI0/ACLM_DS0640* CLM_FISY 0 0
LOGSYS 0 0
/BI0/ACRM_CMGL00* LOGSYS 0 0
/BI0/ACRM_CMGL40* LOGSYS 0 0
/BI0/ACSM_LINK00* LOGSYS 0 0
/BI0/ACSM_LINK40* LOGSYS 0 0
/BI0/AGN_BP00* GN_PAR_LSY 0 0
/BI0/AGN_BP40* GN_PAR_LSY 0 0
/BI0/AGN_CONV00* LOGSYS 0 0
/BI0/AGN_CONV40* LOGSYS 0 0
Could any body help me in this
Thanks & Regards,
ArunHi experts,
I have done the system copy form Production to Developement.
Transfermations and DTP(Data transfer process) are still connected from Produciton R3 which should be from developemnt R3.
I have tryied to change the logical sytem name through BDLS. But the logical system name is not changed
i got the job log which is in above conversation in my thread.
Please let me know how to change the logical system name in Transfermations and DTP in RSA1
Thanks & Regards,
Arun -
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
Maybe you are looking for
-
A couple of days ago, I connected to the Internet as usual & opened Firefox, only to be greeted by an almost blank screen with a Google-type search box in the middle & this message from McAfee: "Your default search settings have changed. This may pos
-
In Billing Base Price should be in grey mode and in Sales order Change mode
Hi I have one requirenment the Base price (ZPR0) should pick automatically from condition records and system should allow to change ZPR0 in Sales Order item level , where as it should be Grey mode in billing document item level. 1. In the condition t
-
I just updated my mac to leopard and when I try to open appleworks 6 a window comes up giving me the option to ignore, report or relaunch. It will not relaunch so I reported it. What do I do to fix this.
-
Upgrade to 8.1 failing - 0x87D00324
Hi guys, I am trying to deploy Windows 8.1 as an available upgrade via Software Center however when trying to install I get the following error: 0x87D00324 (-2016410844) I know this error is related to the detection method I have selected but I canno
-
Hi, I am trying to findout what which function module gets called when i click on Edit Plan on benefits enrollment plan. I was able to dig in the code until i reached doPlanEdit( ) method in Component Controller of the Component VcBenefitsPlanSelecti