on 07-18-2009 1:52 PM
Hiii
when im doing file to idoc.. in SXMB_MONI im getting a error msg like
"Unable to convert the sender service to an ALE logical system" ... so i followe the
https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/13562. [original link is broken] [original link is broken] [original link is broken]
As per blog said i did adapter specific identifier... i clicked the Compare SLD button and apply.. but still the problem exist.
But when i check my configuration through CHECH CONFIGURATION tool.. im not getting any error..
what is the problem here?
Regards,
Balaji
Hi Balaji
Your sender business system does not have a logical system name.
go to SLD and give any name as logical system for your third party sender business system.
After cache refresh do compare SLD in adapter specific identifier.
If you can see logical system name in adapter specific identifier...issue is resolved.
Otherwise create new business system with logical system name and do the configuration according to new B.S.
Regards
Abhijit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hii my Receiver Business system do have a logical system.. since i gave the logical system is SLD itself.. i mean once i assigned the client no.. the logical system for the client automatically assigned to my receiver business system.. i also created partner profile for inbound added the idoc type in inbound parameter..... i used IDX1 IDX2 for port configuration from xi. sm59 for receiver r/3 system from xi system...
When i check my congirutaion in ID using "TEST CONFIGURATION" its was successfully processed.. but SXMB_MONI showing the same error.. and IDOC not generated in R/3 system...
Regards,
Balaji
Hi Michael,
Nice to see your reply,
In your reply what do u mean by "click on sender service (header mapping section) and select your business system
that represents XI business system"
I couldnt understand the term xi business system here..
My scenario has stand alone type sender business system and web As Abap type receiver business system.
Regards,
Balaji
Hi,
>>>But i dont understand the concept.. Can u explain.. whats the logic behind your suggestion.. please explain
more details you can find in my book
http://www.sap-press.de/katalog/buecher/titel/gp/titelID-2086?GalileoSession=50249550A39Xd..iZgI
Regards,
Michal Krawczyk
Saw this was unanswered...
In the code inside PI around Logical Systems (after all other logic), it has a habit of clearing the Party (and only retaining the Component Name) before looking up Adapter Specific Info... so it tries to look up your Component with a BLANK Party to find the Adapter Specific Logical System config. And it doesnu2019t find it because you have a Party defined.
So you either overwrite the sender component with an identity that has no party (like Michael suggested), or if you want and or need to keep the Sender Logical System there is an alternative:
Copy the Component and erase the Party on the Component Copy. This will still have the Sender Specific Adapter details in it. A Message can then be reprocessed and you should find it works correctly.
Regds Doug.
Hi PI Experts,
I am getting same error 'Unable to convert the sender service to an ALE logical system' for the scenario SOAP --> PI --> IDOC.
I have tried giving Sender communication component and Receiver Communication component in Receiver Agreement under Header mapping, but still am getting the same error.
Could you please let me know, if i need to do some thing else to fix this issue.
Thanks in advance.
Chakradhar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.