Partner Profiles: Outbound parameters

I want to send a IDOC ORDERS05 to SAP ECC6.0.
I have a partner type LS.
In outbound parameters I can not define message type ORDERS ???
The error message ==> "Logical message ORDERS does not exist"
Anyone can give some tips?
Thanks a lot!

hi,
when you send IDOCs from XI to ERP you don't use WE20
it's a competely different procedure
also XI does not have ERP idoc types (that's why
you cannot choose it in WE20)
check out my book to find out step by step how to do it:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Similar Messages

WE20 use&E0336 EDI: Partner profile outbound logical message not available

Hi
When I am creating the vendor master, after selecting payment advise by EDI tick under APP Transactions i am issued a warning message as Account XXX has not yet been agreed as being EDI partner and its directing me to T.Code WE20. What is the use of this.
I have maintained WE20 for the vendor and after running payment run (F110) with payment method as E (Electronic payments-BACS) payment medium file is getting created. But when i go and see the SP01 in the error log the message is shown as E0336 EDI: Partner profile outbound logical message not available.
Can anybody explain what is the use of WE20 t.code and why i am getting the error message.
Brahma

Hi Deepak,
I am facing the same problem with a different message type.
But same effect. I can copy the IDoc with WE19 and it will process nicely, completely unchanged.
Have you found the reason for this?
Thanks,
Florian

Partners profile - outbound parameters - package size ?

Hi,
My scenario: IDOC(R/3)-XI-File.
R/3 settings: WE20 - While filling out outbound parameters in partners set up i am getting error "please enter a value for package size" highlighting Receiver port in red. My receiver port is tRFC type whose RFC destination would be XI server.
I have created logical systems(SALE) for sender(R/3) and receiver(XI) as well assigned them to clients.
Please help.

Hi Bhavesh,
This is what exactly I did and I ended up getting this error message. I did some research on how to generate partner profiles on sdn.
"transaction SALE), choose Modeling and Implementing Business Processes ®Maintain Distribution Model and Distribution Views (transaction BD64)."
So,I have created a model view called "EC4_TO_PI1".
Then I chose Environment----> Generate Partner profiles. Now, I have to select two model views. (From & To). From Model View I have selected the above model view " EC4_TO_PI1". I am not sure about TO field.
Can you please guide me to helpful documentation ? I am not even sure what is distribution model is. Thank you for your help.
By the by, I have already created logical systems for sender(R/3) and receiver(XI). fyi.

BD64 - generate partner profile - outbound parameter; wrong receiver port

Hi all,
I'm using a distribution model (transaction BD64) for creating partner profiles in my system.
This works fine, exept for one thing.
The receiver port used in the outbound parameter is wrong.
It's using the tRFC port of the destination system instead of the tRFC port of the SAP XI/PI system.
If I send an Idoc it's now going directly to the destination system instead of going to XI/PI first.
I could modify this manually (which is a lot of work), but I would like to know how SAP determines which tRFC port is used when generating the partner profile and creating the outbound parameters.
Can anybody help me with this?
Reagrds,
Roy

Hi,
According to my knowledge, if you have a receiving logical system name is same as the RFC destination name, then the SAP will take the RFC destination properly and will generate the port automatically (for Ex: if you have a port A00..12 then it will create a port A..13). the generated port will be used in partner profile.
Or
Give a try by assign the RFC destination (The receiving logical system name and RFC destination name should be same) for a port and use it while generating the partner profile by using BD64 or SALE.
Regards,
Venu V

Partnet Profiles : Outbound Parameters

Hello -
When i try to create outbound parameters in Partner Profile in R/3, sometimes i don't get the packet size, i just see only the Receiver Port.
Any ideas why i could not see this option?
Thanks,
Tirumal

Hi Tirumal,
when u enter once the field gets activated. when u click on enter again you will get a message saying
Please enter a value for packet size.
If your radio button for 'Output mode' is Transfer Idoc immediately then u need not fill this value.
If the radio button is on collect IDoc you have to fill in this field.
Regards
Vijaya

Edi partner profile inbound parameters urgent plz

hi
iam trying to make settings for inbound parameters of edi for bank, iam wondering what is partner number if partner type is "b"(bank). my partner number will be bank key or house bank or what , bcoz it is not accepting bank key or house bank id

Hi,
In Transaction code FI12 - Change House Bank - Details, there is an push button to create EDI Partner Profiles. Click on that and enter the EDI Partner number. This is not House Bank number / Bank Key. After entering the EDI Partner number, you can click on Partner Profiles and complete the setting up of Partner Profile.
Thanks
Murali.

WE20 - partner profiles: inbound parameters - how to determine process code

Running standalone scenario on SRM 5.0.
First of all, it is not possible to "generate partner profiles" automatically in BD64 (distrubution model) in the backend system for message types:
BBPIV, BBPCP, ACC_GOODS_MOVEMENT, ACLPAY and MBGMCR.
The following error is displayed:
BBPCO
Inbound parameters for message type BBPCO could not be created
Enter a valid process code
etc.
When trying to create partner profiles manually in WE20, how do I determine the process codes for the different message types?

Note 330401 - Process code does not exist f. BBPCO01, BBPIV01
Solution
Check and if necessary, correct the following entries:
1. Assign function module to message type
Transaction WE57
The following entries are required:
Module IDOC_INPUT_BBP_IV IDOC_INPUT_BBP_ACC_PO
Type F F
Basic type BBPIV01 BBPCO01
Msg type BBPIV BBPCO
Direction 2 2
Object type BBPBUS2081 (not for Release 3.1)
Note that object type BBPBUS2081 is not defined in Release 3.1*. In
this case, the 'Object type' entry remains empty.
2. Characteristics of inbound function modules
Transaction BD51
The following entries are required:
Inbound FM IDOC_INPUT_BBP_IV IDOC_INPUT_BBP_ACC_PO
Input type 1 1
03.09.2008 Page 2 of 3
Note 330401 - Process code does not exist f. BBPCO01, BBPIV01
Dialog allowed No No
3. Create the missing process code with Transaction WE42 (change inbound
process code). You can name the process code whatever you want. 'IV01'
or 'CO01' are examples.
The entry should look like this:
Process code IV01 (CO01)
Description BBPIV (BBPCO) inbound invoice
Option ALE Processing with ALE service
Processing Type Processing by function module
Save the entry. You are then on the detail screen. Enter:
Module (inbound)
Function module
IDOC_INPUT_BBP_IV (IDOC_INPUT_BBP_ACC_PO)
Application object
Object type
BBPBUS2081 (- no entry -)
4. Maintain the process code that has just been created in the partner
profile for the logical system.
Transaction WE20
Partner type 'LS'
regards
Muthu

ERROR WHEN GENERATING PARTNER PROFILE

I AM GETTING THE FOLLWING ERRORS WHEN GENERATING PARTNER PROFILE
Outbound parameters for message type MATMAS MATMAS05 could not be created
Please enter a valid value for the output mode
Outbound parameters for message type SYNCH SYNCHRON could not be created
Please enter a valid value for the output mode

Hi Willard,
Checl the output mode and outbound parameters for those both of message types.
Hope this helps you..
Regards,
Kumar.

Partner Profile Configuration(Outbound Enteries)

Hi,
I was trying to make a business partner with the BP Role Master Tenant with Customer Account. At the time of saving I got following error:
Entry in Outbound Table not found
Message No E0400
No partner profile(Outbound) could be foundusing following key
B3TCLNT800/LS//HRMD_ABA///
This refers to key fields in Table EDP13
RCVPRN Partner Number
RCVPRT Partner Type
RCVPFC Partner Function
MESTYP Logical Message
MESTYP Message Code
MESCOD Message function
TEST Test indicator
Please check EDI profiles.
And it directed me to transaction code WE20.
Could you please help me in making the desired settings and explain why this needs to be done.
Regards,
Lata

Hi,
I guess either you are using CRM or Flexible Real Estate Management.
Pl confirm the exact transaction code you are using. Are you using BAPI ?
For creating the Partner profile,
Go to WE20,
Click on Create button.
Give the Partner Number, Give Partner Type as " LS"
User type- US
Agent - Your User ID
Give the Message types in the Outbound/ inbound parameters.
Pl reply for further clarifications
Thanks
Siva

Wrong logical system for partner profile

Dear gurus,
we have been sending ORDERS Idocs for some time now, using to a logical system called MSC_MM_PRD, a RFC connection called MSC_MM_PRD and a port for Idoc processing called A000000003.
Now, we would like to send ORDERS Idocs to another logical system. We created that new logical system called MES001, a RFC connection (MES) and a Port for IDoc processing using that RFC destination (A00000004).
After that we maintained a partner profile for the new logical system MES001 with outbound parameters for ORDERS Idocs. So far, so good.
But then, I had to create a new message type for purchase orders to use that new connection (called ZEDI) and I guess that is where I made a mistake: I copied the existing message type for the old ALE connection and changed some parameters (like name etc.).
Now, when I create a new purchase order and add a message of the new type and save the order, I get an error message:
EDI: Partner profile outbound process code not available
Message no. E0335
Diagnosis
An outbound partner profile could not be found with the following key:
/MSC_MM_PRD/LS//EF/ZEDI//
[u2026]
Procedure
Please check the outbound partner profiles for the assignment of the process code:
As you can see, SAP tries to find an outbound partner profile using the old logical system (MSC_MM_PRD) and the new message type (ZEDI) as a key and obviously fails.
Can anyone please tell me why SAP uses the old logical system and how I can change that?
Cheers
Alicia

Hi,
problem was, that we had not created a proper distribution model for the message type (BD64). After we did that, it worked fine.
Cheers
Alicia

What is the difference between generate partner profile and creat partner

What is the difference between generate partner profile and creat partner profile ?

Create Partner ProfilesAlthough partner profiles are usually created automatically, because of the unusual inbound and outbound profiles needed on the same system, the manual generation of certain profiles is required.
The following subsections describe the partner profile settings for the standard client (assumed here to be ALExxxCyyy), as well as for the corresponding dummy client (assumed to be DUMxxxCyyy). The dummy client partner profiles should have been generated by the automatic generation process completed previously. Nevertheless, these should be checked to ensure that all profiles exist.
Generation of Partner Profiles
The following messages should be added to the 4xx-ORDR model for ALExxxCyyy to DUMxxxCyyy on the reference client:
ORDERS
ORDCHG
ZINVRV
ORDRSP
INVOIC
FIDCMT
The partner profiles should first be generated using the standard auto-generation procedure on the reference client (for SYNCH messages to be created).
This model should now be distributed to the both ALExxxCyyy and DUMxxxCyyy.
The partner profiles should now be generated on the client being configured (i.e. yyy) using the auto-generation procedure defined in the standard ALE configuration procedures.
Generate partner profiles for sending system. (Can only do this if at least 1 message type exists against the sending system's LS). This automatically generates the port if the LS and RFC name are the same.
generate partner profiles tcode BD82
creating partner profiles tcode WE20
 There are two methods for maintaining the partner profile:
 Maintain partner profile manually:
To navigate to the partner profile in the sender system, choose Partner profile -> Partner type of Logical System and click on the required Target system. Under Outbound parameters, choose the Create outbound parameters icon, and enter the values for the outbound parameters according to the slide Sender: Partner Profile (outbound).
To navigate to the partner profile in the sender system, choose Partner profile -> Partner type of Logical System and click on the required Sending system. Under Inbound parameters, choose the Create inbound parameters icon and enter the values for the inbound parameters according to the slide Sender: Partner Profile (inbound).
 Generate partner profile:
Prerequisite: The current distribution model is distributed to all participating systems.
In the sender system, choose: Generate Partner Profile, then check the result in the partner profile (outbound)
In the sender system, choose: Generate Partner Profile, then check the result in the partner profile (inbound)
Regards
Vasu

Hi gurus i am learning what is partner profile

hi gurus i am learning what is partner profile

Logical System name is used to indiacte the application system to which you are ging to send the data.
Partner profiles use the above Logical System name to determine the system to which the data is to be sent ie you have to tell wether inbound or outbound.
Suppose If you are doing IDOC to File scenario ,have to mention the Outbound Parameter in we20 ie IDOC message type name.
For IDOC to file scenario:
SAP R/3 tcode:
WE21 - create port for XI
WE20 - create partner profile LS and add idoc to outbound
XI tcode:
in SM59 - create a type 3 conn from XI to R/3
in IR import IDOC from R/3 in XI
Follow these steps.....
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
Create Partner ProfilesAlthough partner profiles are usually created automatically, because of the unusual inbound and outbound profiles needed on the same system, the manual generation of certain profiles is required.
The following subsections describe the partner profile settings for the standard client (assumed here to be ALExxxCyyy), as well as for the corresponding dummy client (assumed to be DUMxxxCyyy). The dummy client partner profiles should have been generated by the automatic generation process completed previously. Nevertheless, these should be checked to ensure that all profiles exist.
Generation of Partner Profiles
The following messages should be added to the 4xx-ORDR model for ALExxxCyyy to DUMxxxCyyy on the reference client:
ORDERS
ORDCHG
ZINVRV
ORDRSP
INVOIC
FIDCMT
The partner profiles should first be generated using the standard auto-generation procedure on the reference client (for SYNCH messages to be created).
This model should now be distributed to the both ALExxxCyyy and DUMxxxCyyy.
The partner profiles should now be generated on the client being configured (i.e. yyy) using the auto-generation procedure defined in the standard ALE configuration procedures.
Generate partner profiles for sending system. (Can only do this if at least 1 message type exists against the sending system's LS). This automatically generates the port if the LS and RFC name are the same.
generate partner profiles tcode BD82
creating partner profiles tcode WE20
 There are two methods for maintaining the partner profile:
 Maintain partner profile manually:
To navigate to the partner profile in the sender system, choose Partner profile -> Partner type of Logical System and click on the required Target system. Under Outbound parameters, choose the Create outbound parameters icon, and enter the values for the outbound parameters according to the slide Sender: Partner Profile (outbound).
To navigate to the partner profile in the sender system, choose Partner profile -> Partner type of Logical System and click on the required Sending system. Under Inbound parameters, choose the Create inbound parameters icon and enter the values for the inbound parameters according to the slide Sender: Partner Profile (inbound).
 Generate partner profile:
Prerequisite: The current distribution model is distributed to all participating systems.
In the sender system, choose: Generate Partner Profile, then check the result in the partner profile (outbound)
In the sender system, choose: Generate Partner Profile, then check the result in the partner profile (inbound)
Reward Points If Useful.

Task properties - General task - Partner profile

Hi Experts,
I'm using user decision step for manager approval, and in development server i've selected task as general task in task properties and everything was working fine in development server.
When above workflow development transported to testing server, the task properties are not transported. So, agent assignment is de-activated. And when i'm trying to set general task attribute in task properties, its saying "Entry in outbound table not found" error message. Can anyone help me in resolving this.
Entry in outbound table not found
Message no. E0400
Diagnosis
No partner profile (outbound parameter) could be found using the following key:
DC1CLNT10/LS//HRMD_ABA///
This refers to the key fields in table EDP13:
RCVPRN Partner number
RCVPRT Partner type
RCVPFC Partner function
MESTYP Logical message
MESTYP Message code
MESCOD Message function
TEST Test indicator
Thanks in advance,
Siva Sankar.

Hi Siva,
I have always found that I need to go make change the agent assignment on custom tasks to 'General' as the workflows get transported - or you can investigate here:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d00a1cb4-913c-2c10-d991-caf663ab9b16&overridelayout=true
As Jocelyn Dart has said:
Folks, This is an oldie but a goodie.
You need to execute program RHMOVE30 to add your General Task settings to Transports.
Enter your task numbers (you can enter a workflow and use eval path TASK_HIER to pick up all sub tasks) Select the Transport checkbox
On the second screen
Select all and press Add to Transport
Select all again and press Transport/Delete
You should get a message confirming they have been added to your change request.
You will see infotype 1217 entries on your transport request.
However your issue seems to be a different one. I searched and it looks as though you need to check partner profiles using WE20? Have you tried this?
Hope this helps,
Sue

How can we transport the partner profiles and Port configurations

Hi everybody,
How can we transport the partner profiles and Port configurations. While creating these , system will not ask for Dev class and we cant assign any Transport request number. Then How can we transport these settings?
Your replies are really apreciable.
Thanks and Regards,
Vijay.

Hi,
please have a look of the OSS note: 182172
>>
The partner profiles are stored in the following tables:
Table EDPP1: General partner profile
Table EDP12: Partner profile outbound, additional data NAST
Table EDP13: Partner profile outbound
Table EDP21: Partner profile inbound
Table EDIPHONE: Connection to SAP telephony (optional)
You can use R3TR TABU to manually set the tables into a Customizing request (as of Release 46, into a SYST-type request).
<<
Rgd
Frédéric

HR master data & EDI partner profiles

Hi,
I want to link my user to a PERNR in PA30 (infotype 105 subtype 0001).
When I try to save, I get:
"Entry in outbound table not found. No partner profile (outbound parameter) could be found using the following key: .. Please check the EDI partner profiles."
Where can I define the link between HR master data (PA30) & EDI partner profiles (we20) + what is the purpose?
Thanks

Dear JV,
Let us know on EDI partner profiles.
In 0105 IT subtype 0001 is System user name.
It is the linkage point with SAP R/3 and ESS Portal.
After maintaince of data in 0105 IT with subtype 1,we can view the details in Portal according to data maintainnace.
Regards,
Sairam.

Partner Profiles: Outbound parameters

Similar Messages

Maybe you are looking for