on 03-13-2009 10:17 AM
Hi! I'm trying this scenario https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
And and have an error "Unable to convert the sender service MDM_to_CRM_BC to an ALE logical system". What maybe wrong in my scenario ?
In the receiver business system, check Adapter Specific identifier and make sure that the logical system name present there is same as the logical system name present in SLD.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you all very much! It works
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In we20 i can't find where to input Sender port. But in we02 I have some sender port.
And receiver port is empty... Is that right situation?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you all very much! I have done this
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, but now I have a message "Unable to convert the sender service to an ALE logical system"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
While generating the idoc control record for your scenario, it needs the mandatory fields like SNDPRN RCVPRN SNDPRT RCVPRT ,.........so on
This will be generated at runtime from your business systems logical names (Sender and Receiver) if it is not able to find then it will throw an error as what you have posted
Go to Business system/service of File and check the Adapter Specific identifier and similarly for the Receiver Business system/service .
Once this is done let me know you should get an error in R/3 (status code as 56 )
Rajesh
Yeah all you need to do now is go to R/3 and create a logical system name using BD54 and create the partner using we20 and add the idoc message in the inbound parameters
Note : you should create the same partner name as idoc of SNDPRN which is coming form XI then only it will work
Gud luck
Rajesh
Dear Rajesh
My scenario doesn't works I still have error 56.
I have business component mdm_crm_bc - it takes file from folder.
I have exported business system of my PI integration server - p1d_is. In SLD it have logical system name p1d_is. In my receiver agreement I have turned on header mapping to PI integration server system.
And I have CRM business system - crm_c2d. It has a logical name in SLD - lc100. Name of logical systems are available in Adapter Specific identifier of each system.
In CRM I have created logical system in BD54 and partner with name p1d_is in we20 in CRM.
And I still got an "56" error
Edited by: Andrey Bolshakov on Mar 13, 2009 8:41 PM
Hi
Once the Idoc reaches the R/3, technically (from XI's perspective) the set-up is complete
Now, Open the control record of the error Idoc, match the values to the values in Partner profile for partner (p1d_is). each and every entry has to match. Partner type (LS, KU/LI... etc), inbound(in ur case)/outbound Idoc types, msg code, msg func.....etc
If you send an Idoc with any one different entry and the rest being the same, still you will get the error.
So recheck and once you figured out the diff, you can adjust at XI or R3 side as per reqmt.
Regards
Vishnu
Hi,
I have already explained in my reply above,
open two screens, we02 results(where u see the error idocs) & we20 - partner profiles
now start comparing Each & Every entry this includes every entry - sndprt, sndprn, msg func, msg code.....etc etc...
R3 allows idocs which match the entries of partner profiles. so now compare the idocs which tried to enter & its matching filters (Partner profiles).
check the 3rd part of the wiki you follow, that has got step by step overview including screen shots
Regards
Vishnu
Vishnu, I'm very sorry, but:
I've opened we02 ---> Inbound idocs ---> CRMXIF_PARTNER_SAVE_M ---> Status 56
Then I've opened my idoc and see:
Control Rec
Data records - idoc fields
Status records --> 56 --> EDI: Partner profile not available
-
Message no. E0332
Diagnosis
A partner profile could not be found with the following key:
/ls_p1d /LS/
This involves the key fields of the table EDPP1:
-PARNUM partner number
-PARTYP partner type
Procedure
Please check the EDI partner profiles.
-
What should I do now?
I need to check "Sender Communication Component" and select my Business Component that sends file?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I can't find Adapter Specific identifier in Business System
I use PI 7.1
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please send " Logical System name" in "Adapter Specific Identifier" in Service Menu of Business System
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
ref:
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.