Generating SRM Partner Profile in SAP R/3 system

Hi,
Please can someone shed some help as to why I get the message below when attempting to Generate SRM Partner Profile in SAP R/3:
"No messages have been defined for the selection conditions in the model"
I have in fact sucessfully generated this in SRM, but get this message when trying to do the same in R/3 backend.In B64, i have also set it to Transfer Idocs Immeditate.
Thank. You.
Pooja.

Hello Pooja
please check you have supplied correct logical system or not
in the modelview
cross check via scc4.
Re: No messages have been defined for the selection conditions in the model
muthu
Edited by: Muthuraman Govindasamy on Oct 3, 2008 2:48 PM

Similar Messages

Just one partner profile for SAP XI?!

Hi,
well i have some thoughts concerning configuring the partner profile on sender side.
I have different systems to which e.g. IDocs will be send to. Therefore i was thinking to set one partner profile for each connected system.
But on the other hand it is also possible to just configure one partner profile, e.g. called SAP XI, and seperate the different IDocs inside this partner profile because of different Message-Types of the Outb-parameters, and inside this because of the IDoc-Type.
So what is the most propriate way to solve this, is there a suggestion by SAP?!
thx in advance, Jens

Hey guys,
Just thought I'd add my experiences here.
In one of our implementations we created partner profiles with respect to XI. We had multiple source systems , but the Target ECC team was like, we do not care who sends the data to XI, as far as we are concerned we get data from XI. So we create only one partner profile. We agreed to this and so all Idoc's posting from XI had the XI as the sender partner name. The project went into production and things were fine.
Then comes the next release. And what do we realise, that the same Idoc will not be posted from XI but for different source systems with different formats. The Inbound processing for the idoc was also being changed stating that Idoc from Source system A needs to be processed with this T code and Idoc's from System B with this code. reason was different bsuiness rules across different geographies.
Now, at this juncture we realised in vain that it would have been better had we maintained the partner profiles with respect to the End Systems . having it with respect to XI caused issues in the fact that we are unableto trace out which Idoc belonged to which system.
Since, then we always recommend all partner profiles with respect to End Systems and not with respect to XI. Helps the business also understand how many idoc's were posted for which source system and so on.
Just my 2 cents and experience here. Would love to heard more on this topic as well.
Regards
Bhavesh

Generating a partner profile

Hello Gurus,
In BD64 I am trying to generate a partner profile for R/3 to BW system. The RFC destination has been defined correctly.
And WE20 is also maintained in both the systems.
After defining the message types RSSEND, RSINFO and RSRQST in BD64, I am trying to generate partner profile.
But I get an error 'System XXX111 cannot be created as a partner system'.
what can be the issue.
Kindly guide.
Regards,
NIKEKAB

Rersolved

Export partner profiles and SM59 Entries before system refresh

Hello All,
How to Export partner profiles and SM59 Entries before system refresh in Netweaver
thanks
Shyam

In SDN search with name RFC export ..you will get so many answers ..
Once again please find the below prcoess for RFC export/import during system refresh.
RFC Export --
go to trans dir.. and then create .ctl file as below
#cd /usr/sap/trans/bin
#vi export_rfc_<sid>_<date>.ctl
#Please create the data file as u201Cexport_<SID>_rfc_<Date>.datu201D
Export
Client=<XXX>
file '/usr/sap/trans/data/export_<SID>_rfc_<Date>.datu2019
delete from rfcattrib
select * from rfcattrib
delete from rfcdes
select * from rfcdes
delete from rfcdoc
select * from rfcdoc
delete from rzllitab
select * from rzllitab
delete from ZTCA_USER_LANG
select * from ZTCA_USER_LANG
delete from rfcsysacl
select * from rfcsysacl
delete from rzllitab
select * from rzllitab
#After that excute export command as below.
R3trans u2013w <export_rfc_<targetSID>_date.log> export_rfc_<targetSID>_date.ctl>
(Format is: R3trans u2013w <logfile> <controlfile>)
Export is finished....
Import
Example:
#cd /usr/sap/trans/bin
#vi import_rfc_pta_11042004.ctl
#Please enter the exported RFC data file in the import control as follows:
import
file '/usr/sap/trans/data/export_pta_rfc_11042004.dat'
(Enter the file name, which is created during the export process)
Regards,
Srinivas Chapa.

How to generate Business Partner only in SAP for Naksia

Hi Everyone,
Having one issue, if you can help me out
In SAP when we run HRSYNC_PERSON report automatically it will generate Central Person and Business Partner.
Here my question is what options to select in this report to generate Central Person & Business Partner?
If I want to generate only Business Partner, then what options to be select, because in my system Central Person is already created.
Could you please help me on this issue.
Waiting for your response!!
Regards
Utkarsh

Hi Utkarsh:
Well, there's a variety of issues that could be causing this.
It could be your pernr is simply missing a valid infotype 6. A BP needs infotype 0,1,2 and 6 at a minimum to be generated.
It could be a problem with your actual Business Partner configuration. It would be good to see if you can generate a BP from scratch on your own using transaction BP. That will tell you if your BP config has any issues.
It could be a problem with tax jurisdictions in VERTEX or some geocode tables that need refreshing from client 000. It's hard to say from here. The lower left hand corner of the screen when you hit the 'synchronize' button should tell you why a BP wasn't generated.
Let me know what you get when you create a BP through transaction BP. Then let me know what the bottom left hand corner of HR_SYNC_PERSON says after you synchronize.
Thanks,
Chris

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

Generate partner profile

hi guys
i hve got a problem
when i generate a partner profile i get an error "NO ACTIVE PLAN VERSION EXITS" for type parameter

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

Error while generating Partner profiles

Hi,
I am not able to crate the Partner profile. When I try to Generate the Partner Profiles from the Distribution model (Masterial Master) it give me following error,
"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"
Can anybody tell me how to solve this problem??
Thanks in stack.

How did you try to generate the Partner profile?
Can you pls try the following...
execute report "RBDCUS15" and give the model view/partner for which the entries needs to be generated.
Also, give the appropriate values for "Outbound Parameters" like version, packet size and output mode.
Thanks,
Renjith

Partner Profile not Generated

hi! all
Generating the Partner Profile Using BD64
while generating received the message in Green for parameters: Partner (Sender, Receiver); Port (Zport); Outbound Parameter(Zsender).
while checking in WE20 - Partner Profile ; Profile has been generated for the Reciver System with the created message type and port in Outbound parameter. But not generates the Inbound parameter.
As like Profile has not generated for the Sender system.
While testing the idoc using WE19 it says Profile not generated for Sender system
whats the mistake i have done. How to correct it.
Regards,
Kv

Hello,
The distribution model view for which you are generating the partner profile (PP) check the sending & receiving logical systems (LS).
if you want to generate the PP with inbound params you have to assign the your own LS as the receiver & not the sender.
BR,
Suhas
PS: If this bothers you too much maintain the inbound params manually in WE20

Problem BD64- Generate Partner Profile

Hello everybody,
After creation the model view in the transaction SCUA i go in the transaction BD64 and i try to generate the partner profile to the child systems but i got an error as below:
Object type US, ID BASIS unknown (please observe upper/lower case)
    Message no. E0624
Diagnosis
Object BASIS of type US is not known in the system.
Procedure
Enter a valid object and check the type.
    Make sure upper case and lower case are used correctly.
Somebody can help me?
Best Regards,
Fábio Karnik Tchobnian

Hi,
your question is not really related to SQL Server but to the CUA. Please post your question in a different forum (Netweaver Administrator maybe) and I am sure you will get answer there.
Sven

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 Idoc

Hi ,
I have created a partner profile of type logical system. If i dont specify anything in the inbound parameters and send an idoc to this partner profile then how would the system respond.
Regards
Arun

INBOUND processing the IDOCs are transferred to the interface and stored in te SAP system. The document data is generated in the course of workflow.
In this section the SAP system is made known to the upstream system (startrfc program parameters). Conversele, the upstream system is made known to the SAP System via the port definition.
INBOUND Processing - Create Function Module.
This function module is called when a message type, of the ZINVRV, comes into the receiving system. This needs to be configured. The function module is passed the IDOC as a parameter.
Use the T.code WE19 to test inbound function module in debugging mode.
Use the T.code EW05 to view the IDOCs and their statuses.
Rewards if useful.

Partner profile LS PIBCLNT100 SYNCH does not exist

Hi!
I try currently to configure a IDoc to IDoc scenario for SAP ECC 6.0 system with following business 2 systems:
ERP:100 (Sender)
ERP:200 (Receiver)
and XIB:100 (XI system)
I successfully created a message type u201CZCREMRu201D and generated the model view in tcode BD64.
Unfortunately when I try to distribute the model and choose my XI system I get the following error:
Target system: XIB:100
RFC destination for synchronous communication (message type SYNCH)
Partner profile LS PIBCLNT100 SYNCH does not exist
Generate partner profile
or specify outbound partner profiles for message type SYNCH
Questions:
Where do I need to create a partner profile for SAP PI (XIB:100)?
Which message type do I need?
Which parameters inbound/outbound and which process codes do I need?
Thank you very much!
regards
Thom

Hi!
Many thanks!
Unfortunaltely I cannot find the process code "SYNCHRON"
for message type "SYNCH".
Could you tell with process code do I need for the message type "SYNCH"?
How is it possible to create a new process type and assign them to message type?
Thank you very much!
regards
Thom

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

Problem in Message Type of Partner Profiles - IDOCS

Hi everyone,
I have created two Partner Profile's in WE20 attaching the corresponding Message Type with them. I have transferred one Message Type from one Partner Profile to another. When I save the model in BD64 and Generate the Partner Profiles from there I see that ''SYNCH" message type also gets added in the target Profile.
Can you please suggest why it happens and how to rectify this problem so that "SYNCH" message type does not get added anymore.
With warm regards,
Sandeep Panja.

Hi,
U can see SYNCH message type in all the partner profile.
The monitoring object is located in the same client A function module is called locally In this case no further Customizing settings are required
· The monitoring object is located in the same physical system but in a different logical system (client):
In this case you have to assign an RFC destination with a dialog user to the message type SYNCH in the current client for the client to be monitored.
http://help.sap.com/saphelp_nw70/helpdata/en/90/c4b523c4c411d2a5ee0060087832f8/frameset.htm

Generating SRM Partner Profile in SAP R/3 system

Similar Messages

Maybe you are looking for