We are currently involved in pushing Idocs from SAP IS-U with partner type SP to file server (partner type LS). It highlights the use of party in this context and how it has helped our project in configuring outbound Idoc scenarios.
The mismatch of the partner type always resulted in a runtime error Unable to convert ALE service at the receiver determination. Since third party systems created in SLD are always identified as partner type LS, we have to introduce the term Party to just fool around XI by generating the alternative partner profile at runtime.
Entire work around is achieved by creating the dummy party with the sender partner profile in the integration directory. I dont know why it works but it works! I edited the images for confidentiality purposes.
Configuration Steps in the Integration Directory:
1.Create a Party with the name of sender partner profile Party X by clicking the Party object under the configuration scenario.
2.Specify the agency scheme in the identifiers tab as shown below.
3.Assign the SAP IS-U business system, which is created in the SLD in the services as shown below.
Once the above step is done select the party name in the receiver determination, interface determination objects and receiver agreements as shown below.
With this configuration we are able to successfully send Idocs to our file server. This is just a work around I tried in my project. Suggestions are always welcome if there are any other better options.