Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Error in BD64 while partner generation and model distribution

Former Member
0 Likes
1,504

Dear all,

My scenario is as follows.

Transfer MATMAS from TTP105 to TTP100 system.

The steps I followed so far are as below.

<b>On the Sender system TTP105</b>

<b>----


</b>

1) <b>BD54</b> - Created the logical systems for sender & receiver (TTP100 and TTP105)

2) <b>SM59</b> - Created the RFC destinations (TTP100 and TTP105) for both the sender and the receiver and checked the connections. They are working perfectly.

3) <b>WE21</b> - Created the sender port as TTP100 (to represent that it points to the receiver system). The Type is USER and the Agent is my userid. Nothing in the outbound and inbound parameters sections.

4) <b>BD64</b> - Created a modelview with the sender system as TTP105 and the Receiver system as TTP100 and the message type MATMAS. No filters defined. Saved it.

<i><b>The problem begins here...</b></i>

<u><b>Problem#1</b></u>

When I chose the created modelview and then choose Environment->Generate Partner Profiles.. I'm getting the message as <u><b> No messages have been defined for the selection conditions in the model </b></u>

Can anyone guess why this error is occuring?

<u><b>Problem#2</b></u>

When I chose the created modelview and then choose Edit->ModelView->Distribute, again I'm getting another error which is as below.

<u><b>

RFC destination for synchronous communication (message type SYNCH)

Partner profile LS TTP100 SYNCH does not exist

</b></u>

Has anyone encountered such error message before? If yes, then please respond and rewards guaranteed for sure.

Cheers,

Sam

1 ACCEPTED SOLUTION
Read only

former_member189059
Active Contributor
0 Likes
1,042

1. There is not need to create an RFC destination for the sender system

2. If the receiver logical system and rfc destination have the same name, then there is no need to create ports, they are created automatically with the 'generate partner profiles'

3. Try saving your data before going to 'Generate Partner Profiles'

4. Problem#2 is caused because the step for Problem#1 did not execute successfully

Message was edited by:

Kris Donald

Dear all,

My scenario is as follows.

Transfer MATMAS from TTP105 to TTP100 system.

The steps I followed so far are as below.

<b>On the Sender system TTP105</b>

<b>----


</b>

1) <b>BD54</b> - Created the logical systems for sender & receiver (TTP100 and TTP105)

2) <b>SM59</b> - Created the RFC destinations (TTP100 and TTP105) for both the sender and the receiver and checked the connections. They are working perfectly.

3) <b>WE21</b> - Created the sender port as TTP100 (to represent that it points to the receiver system). The Type is USER and the Agent is my userid. Nothing in the outbound and inbound parameters sections.

4) <b>BD64</b> - Created a modelview with the sender system as TTP105 and the Receiver system as TTP100 and the message type MATMAS. No filters defined. Saved it.

<i><b>The problem begins here...</b></i>

<u><b>Problem#1</b></u>

When I chose the created modelview and then choose Environment->Generate Partner Profiles.. I'm getting the message as <u><b> No messages have been defined for the selection conditions in the model </b></u>

Can anyone guess why this error is occuring?

<u><b>Problem#2</b></u>

When I chose the created modelview and then choose Edit->ModelView->Distribute, again I'm getting another error which is as below.

<u><b>

RFC destination for synchronous communication (message type SYNCH)

Partner profile LS TTP100 SYNCH does not exist

</b></u>

Has anyone encountered such error message before? If yes, then please respond and rewards guaranteed for sure.

Cheers,

Sam

3 REPLIES 3
Read only

former_member189059
Active Contributor
0 Likes
1,043

1. There is not need to create an RFC destination for the sender system

2. If the receiver logical system and rfc destination have the same name, then there is no need to create ports, they are created automatically with the 'generate partner profiles'

3. Try saving your data before going to 'Generate Partner Profiles'

4. Problem#2 is caused because the step for Problem#1 did not execute successfully

Message was edited by:

Kris Donald

Read only

former_member189059
Active Contributor
0 Likes
1,042

One more thing, in SALE transaction, you have to assign the logical system to your client.

Have you done that?

Read only

0 Likes
1,042

Thanks Kris for the reply. I actually solved this in another way.

The issue was in SCC4, the client 105 sender which was supposed to be assigned to my logical system had been changed by someone else to another. This was creating the whole issue.

I started all over from the scratch and found out the mistake at that step. Now everything is working fine.

Thanks for your help too!

Cheers,

Sam