‎2007 Apr 26 6:35 PM
Hi All
The scenario is to send idoc from R/3 to XI.
Partner is LS, medium ALE.
I am getting an error " No partner profiles (message control) maintained " when I try to create a PO idoc from ME22 n transaction. But I have the partner profile maintained in we20. In my case, it is custom output type copied from NEU, ME11 process code and EF application. In the message control outbound, I added these entries. Am I missing some entries here. Any help is really appreciated.
Thanks
Anand
‎2007 Apr 26 6:44 PM
check SALE transaction whether ur Logical system is maintained correctly.
‎2007 Apr 26 6:46 PM
‎2007 Apr 26 6:46 PM
Hi,
- Use process code is <b>ME10 instead of ME11</b>.
- <b>The output medium should be 6 - EDI</b> NOT A - ALE
Also, in WE20 under table "message control" add one more line with the same entry; application = EF , Message type = 'your custom message type', process code = ME10' <b>AND the change flag set</b>.
Let me know if you still get an error.
Regards,
RS
‎2007 Apr 26 6:50 PM
This is for change PO. So I need to use ME11.
This is the error message in detail.
"No IDOC partner profiles have been created for the message control for for application EF, condition key ZNEX and change message '' with partner type 'LS' and partner role ' '. "
How many entries do I need to maintain in the message control
Right now I am maintaining only one entry
EF ZNEX ME11. Please tell me clearly the entries need to be maintained
Thanks
‎2007 Apr 26 7:01 PM
If I use EDI as medium, I am getting Maintain outgoing EDI-connection data for partner LOGI1X error
And I tried using ME10 also.
Thanks
‎2007 Apr 26 7:08 PM
Hi,
We use process code ME10 for both PO create and change.
You have to maintain two entries. In the second entry you select the "Change' flag. This is the last column where you define, application, process code and message type.
Hope this helps. Let me know if you still have an issue.
Regards,
RS
‎2007 Apr 27 1:25 AM
Hi Anand,
Did you check whether any condition records are maintained for that condition type? If not ,please maintain once. And then, once go to BD64 and select your systems and then go to Environment->Generate Partner profiles by setting the Check Run flag and then execute. If everything is fine, then you will get the result.
Its fine if you ME11 and type of connection ALE only.
Note: Dont forget to reward points if message is helpful.
Thanks,
Adithya K
SAP Practise
‎2007 Apr 27 2:15 AM
hi,
set ur message type in <b>BD64</b> i think u didnt set it properly .there u wil spec both th sys n the type of msg u gona send.
if helpful reward
ravi
‎2007 Apr 27 2:33 PM
I am still facing lot of troubles in setting up the idoc trigger from PO
Here is what I am doing
Created an output type ZNEX copied from NEU and assigned the program RSNASTED, EDI_PROCESSING form routine. Medium 6 for EDI.
Checked the checkboxes, Access to conditions and Multiple issuing.
Given the Access sequence.
Maintained condition records for PO type Pur. Org
In the condition records, for Pur Org, I have given POtype, Partner as Partner no of XI and Part Fn as LS medium 6 and 4 for idoc generation after saving immediately.
Created partner profile outbound for ORDCHG message type, assigned the
Partner no. and Part type LS, Message type ORDCHG, Receiver port A00026, Pack Size 1, Transfer idoc immediately, BAsic type ORDERS05, Syntax check checked.
Message control as EF ( Application), ZNEX (Output type), and Process Code ME11.
Created Dist. model in bd64 and assigned the sender, receiver, message type for the model view.
Testing
ME22N, changed the PO quantity, went to messages. It is giving short dump
PERFORM_PARAMETER_MISSING
CX_SY_DYN_CALL_PARAM_MISSING
Could anyone help me what is wrong in the setting
Thanks
‎2007 Apr 29 3:13 PM
‎2007 May 21 11:05 PM
Anand,
Were you able to solve this issue? I am facing the same problem. I am using transmission medium as ALE for ORDERS and process code as ME10 and I cretaed a new output type (a copy of NEU), 'cos I wanted to use the partner functions "ALE with LS".
Please let me know if you have solved your issue. May be this will shed some light into my problem here.
Thanks,
RS