Partner profile generation

Hi,
while generating the partner profile it is askimg for partner no but i don't have any partner system is there any option to configure the same system as seneder and receiver , if it is possible tell me the procedure how can we do that.
Thanks in advance,
Sasi.

u can use a business service as sender as well as reciever.
click on the business service->give the outbound message interface name in Outbound + (below) give the inbound message interface name....so during reciever determination u can give the sender service as the reciever.

Similar Messages

No details getting populated in Log for Partner Profile Generation...

Hi,
When I create a distribution model in BD64 and then go to environment -> Generate Partner profiles, enter all the required parameters like model view, type, id, version, packet size and all necessary stuff, but when I execute I get a message in log for partner profile generaation saying, "No messages have been defined for the selection conditions in the model".
Can someone tell me as how can I eliminate this error ?
Thanks.
Regards,
Tushar.

Hi,
When you create a model view, first you have to save the entries and then generate partner profiles.
This should help
Vamsi

Generation Partner Profiles from ALE Distribution Model

Hi ABAP/EDI experts,
I am a trainee. I am getting training from Pvt consultancy. I am working on SAP Demo systems.
I am trying t generate an IDoc using ALE method.
IN SALE window, I created two logical systems,ZVK_SS_800 and ZVK_SS_820. I assigned them to two clients 800 and 820 respectively.
In SM59 i created an RFC connection ZVK_RFC004 of type 3. Here I gave the client Number as 820. ( I'm not sure what to give)
In BD64, I created an ALE Model and added the message type MATMAS with Sending and Receiving Logical systems.
From the Environment drop down menu , selected generate partner profiles and executed with defaults checked. ( Transfer IDocs Immediatley and Trigger Immediately).
I got the following log.
Log For Partner Profile Generation:
Partner:
In Green Color
Partner ZVK_SS_800 as partner has been Created ( Sending System)
Partner ZVK_SS_820 as partner has been Created (Receiving System)
Port:
In Red Color
Port Cloud not be Created
RFC destination ZVK_SS_820 not specified for system ZVK_SS_820
Enter the RFC destination and Restart the generation.
Please help me to fix this probelm.
Any kind of Help will be surely rewarded.
Thanks,

From SM59, you can Test your RFC Connections between Clients. I would do this from Client 800 and test the Connection to Client 820. If that checks okay, I would then try SM59 on Client 820. Check the RFC Connection from Client 820 to Client 800. Be sure you have your Logical Systems defined on Both Clients. You can also double click on your Error Message to see if there is a Long Text Available that might give you further information as what needs to be corrected. I am not an Expert in this area, but have setup several ALE Models for my Variant Configuration without any problems. If you could include your EMail Address on your Business Card I could EMail you my instructions. Your Basis person may also be able to help you based upon your Error Message.

Partner Profile problem while creating IDOC

hi!
I have attached the Partner Profile for the Generated model by assigning the Created Sender, Receiver and message Type and Distributed too.
While checking the attached partner using the T.code WE20 the Message Type is differing from what i have given in the model. its taking SYNCH and the Basic Type as SYNCHRON but the receiver port has been attached correctly.
whats the mistake i have done
Regards
Kv

Hello Gautam,
I am 100% sure about this (anyways FYI i am in ECC5.0). If you debug the BD64 transaction, you will find that it uses some FM (i donot have the SAP system with me so cannot give you the name of the FM) to update table EDP13 directly.
once you generate the partner profile then SYNCH message will automatically be added in partner profile
Then what is the use of adding SYNCH message? In fact the SYNCH message has to be added manually in WE20 & is used by the partner profile generation program to get the port details.
The FMs which SAP uses are: MODEL_ADD_MESSAGE_TYPE_LINK & EDI_AGREE_OUT_MESSTYPE_INSERT. You can refer to the program RBDCUS15.
BR,
Suhas
Edited by: Suhas Saha on Feb 2, 2010 3:46 PM

Generation of partner profile

Hello,
I am new to ALE/IDOC , I am trying to generate profile to test my outbound idoc. I followed following steps to come to BD64.
created segment
created idoc type
created message type
assignment of the message type
RFC destination
Port creation
BD 64
BD 82
while generating profile I am getting the message and I dont see the profile in WE20.
No messages have been defined for the selection conditions in the model.
Any clue is appriciated,
Thanks in advance
Jane

Hi ,
After the port creation , u need to create the Partner profile, It is improt and tell u the what type of our receiver system is , and sender system is..Here we have different kinds of Partner profiles.B,BP, GP,Ku,LI,LS ...
I think in your case if the LS ,
So create it. And in the Outbound params. u need to add the message type , Receiver port ,output mode ,Basic type..
Regards,
Bharani

Error MSG : Create a partner profile for message type 'MATMAS'

Getting Error MSG : Create a partner profile for message type 'MATMAS'
While running LSMW Idoc generation process

See the below link and it has all screen shots how to configure ALE like partner profile,logical systems,RFC
http://searchsap.techtarget.com/general/0,295582,sid21_gci1130337,00.html

Partner profile for message type.

Dear All,
I am using bapi in lsmw for data conversion.
I am getting error in 13th step of lsmw, ie, when I execute Start Idoc Generation, it's saying,
Create a partner profile for message type - MATERIALVALUATION_PRICECHANGE.
I already created a partner profile and assigned in the initial screen of lsmw.
Kindly let me know where I am missing.
Thanks in Advance,
Ranjan

See if any of the follwing helps:
1. The port used in the partner profile should be a file port, not tRFC.
2. The checkbox 'Unicode Format' for the port LSMW in WE21 should remain unchecked.

Generating partner profile in idoc

hello experts,
When i am generating partner profile, following error is generated.
Port could not be created
RFC destination 0000000810 not specified for system 00000000810.
enter the rfc destination and restart the generation.
what is solution for the error?
Edited by: amar_war on Mar 6, 2011 8:28 AM

Actually I have already created rfc connection......
i have connected 2 clients 800 and 810.
in 800 i have created rfc connection for 810
in 810 rfc connection for 800.
i have also created ports....... but its still giving me error...
is my process is wrong to create rfc connection?

Partner profiles in idoc.

Dear Experts,
I am using 800 client for sending and 810 for recieving.
I am using message type MATMAS to send material to 810.
for this how to create ports and partner profiles I am getting confuse in these two areas remaining are ok .
help me in this case

Hi,
To create partner profiles and ports,
At the sender (client 800):
Port: Port is required for the outbound message type and hence port generation is required only at the sender. Goto transaction WE21and selecting u201CTransactional RFCu201D under u201CPortsu201D and clicking on u201CCreateu201D at the application toolbar as shown will pop up an option if you want to u201CGenerate port nameu201D or u201COwn port nameu201D. Selecting u201CGenerate port nameu201D will end up in a system generated port name, while selecting u201COwn port nameu201D would ask the user to enter the port name of his choice. You need to provide the RFC destination created in SM59 in the previous steps connecting to client 810.
Partner Profile: At client 800, you will create the outbound message type, MATMAS. Enter the message type (MATMAS in this case). Mention the port created in the previous step. Select the Output mode as u201CTransfer IDoc immediatelyu201D or u201CCollect IDocsu201D based on the requirement. When u201CCollect IDocsu201D is created, it will ask for the packet size (which tells how many IDocs would be transferred in one LUW) else, packet size is taken as u201C1u201D by default when u201CTransfer IDoc immediatelyu201D is selected. Fill in the u201CBasic Typeu201D (can be obtained from transaction WE82). Click on u201CSaveu201D.
At the receiver (client 810):
Port: Not required as we are not sending back any acknowledge messages from the reeiver.
Partner Profile: At client 810, you will create the inbound message type, MATMAS. Enter the message type (MATMAS in this case). Mention the process code (obtained from transaction WE64). The u201CProcessing by Function Moduleu201D can either be u201CTrigger by background programu201D or u201CTrigger Immediatelyu201D as per the requirement. Click on u201CSaveu201D.
Hope this makes it clear regarding your query on creating ports and partner profiles.
~ Bineah.

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

Partner profile in lsmw using idocs

Hii!
I have a requirement where i need to convert article master in SAP Retail. I am using LSMW using IDOC. I have followed all the steps of configuration like created a partner profile, a message type(zmsg_type), processcode etc.
However in LSMW Step: Start Idoc Generation , i get the foll. error:
<b>Create a partner profile for message type zmsg_type.</b>
Please help me with this.
Thanks.

Go to WE20 and then take your partner profile type from the left hand side and check you have assinged the message type in outbound or inbound parameter(in the right hand side).. if you have not then you will get this error.
Award if usefule
Prince

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.

Logical system and partner profile configuration

Hi,
I have a SQL server which is defined as a Business system in my landscape. It is sending records to ECC 6.0 which makes it a JDBC to IDOC scenario (inbound IDocs)
First question is do I have to mention a logical system name for the SQL server Business system too ?
Second question is do I create a Logical system in the ECC system (BD54/SALE) for the SQL system or would it be for the client of the ECC system itslef?
Third question is do I maintain partner profile configurations in WE20 for the SQL business system or for the ECC business system?
Thanks in advance.
Cheers,
S

Hi Sam,
> First question is do I have to mention a logical system name for the SQL server Business system too ?
Yes, In SLD You have to specify logical system name of the SQL server business system while creating SQL system.After importing business system into Integration directory,in Adepter-Specific Identifiers you can see logical system name of SQL server business sytem which you defined in SLD.
> Second question is do I create a Logical system in the ECC system (BD54/SALE) for the SQL system or would it be for the client of the ECC system itslef?
Yes,You have to create Logical system in ECC system for SQL system(Logical system name must be with the same name as logical system name you have given in XI SLD in previous question)
> Third question is do I maintain partner profile configurations in WE20 for the SQL business system or for the ECC business system?
In WE20 You have to maintain partner profiles for SQL server Logical system
For example: If SQL server Business system name is SQLDEVBS and logical system name is SQLDEVLS
In ECC you have to create logical system as SQLDEVLS and
Partner profiles for SQLDEVLS in WE20.
Please let me know if you have any issues.
Cheers,
JAG

Multiple Logical Systems in Partner Profile for one instance

Can we create multiple Logical Systems in Partner Profile (WE20) for one instance or one System? If it is possible, can we create Logical System with respect to Plant/Country?

I am not quite sure if I understood your problem completley. But let's see...
Usually you use on on MSCS Cluster Group per SAP instance. So you have your already existing NW 7.0 ABAP stack in a separated Cluster Group, and you create a new Cluster Group for your new Java system.
You can find more information about it in this guide here on SDN:
Link: [High Availability;
More information about High Availability Setups for SAP System can be found here on SDN:
Link: [High Availability]
If you want to use the same database for your clustered ABAP stack and your new Java stack you can do a MCOD installation.
Please see Link: [SAP Note 388866 - Multiple Components on One Database - Installation|https://service.sap.com/sap/support/notes/388866]
Hope this helps.
Best regards,
Mathias

Partner profile is not getting updated in FSCM.

Hi All,
We are using FSCM for credit management. We have a issue wherein partner profile are not created for a customer.
We created a customer and hwne checked we found that the partner profile is not there for the customer. We are checking the master data but not able to find the exact reason.
Can somebody help me solving this issue.
Regards,
Satish.

Which version of ECC are you using?
In ECC 6.0, you have to activate CVI (Customer Vendor Integration)

Partner profile generation

Similar Messages

Maybe you are looking for