Why does recievig partnerrequire outbound parameter setting for the message

Question

Hi,
    I was configuring the partner profiles for outbound billing and sales order cycles.Interestingly for outbound scenario, we had to maintain the settings for outbound parameters in receiving partner.
For example, if i sending ORDERS  message type from sender to receiver, then after maintaining the details in partner profile(outbound parameters for sender in we20) for sender, then not only i need to put the orders details in inbound parameters for reciever, but also the outbound parameters for receiver(both inbound and out bound parameters to be filled for the message type for reciver partner).
I checked other systems and founf this is how it is being maintained in outbound cycle.But could anyone provide any insight of why this is required.I did not find anything from bd64 or others about this.
why would the outbound parameters needs to be filled for particular message type in reciver sytem, when it is only required to fill the inbound parameters only for receiver system?

Answer 1

I got help for this issue over at CreativeCow's FCP pages -- it turns out, all I had to do was open a new project using an easy setting and project setting for vanilla PAL 25 fps SD stuff. All of the audio was correctly brought in -- then I disconnected all of the clips, made them dual mono, reconnected them, and copied them over to my old gristly project folder.
Now I can marry these dual mono 25fps files to the video files without having FCP incorrectly compensate for "30fps" by speeding these clips up slightly, so things stay in sync.