Hi,
I am still very uncertain what the main research goal of your project is but my feeling tells me that you should check the underlying technologies and concepts a bit more first.
1.) From the BPEL model itself you cannot find the target information of a service invocation because BPEL uses only the protocol-independent parts of the WSDL; except when you override the partner link information with WS-A information (see your other question),
2.) The deployment descriptor will specify the mapping of physical endpoints for every partner link. So the first step that you need to do is to check the deployment descriptor. Those are very product-specific and not standardized.
3.) The endpoint configured in the deployment descriptor can be pointing to an ESB that will do some kind of rounting, so it might be necessary to explore the routing configuration of the ESB
4.) The ESB can use content-based routing, i.e. you would need to trace the messages
5.) The endpoint in the ESB can be virtual and only be resolved during runtime.
For answering your question, you will need much more background around the infrastructure in which the BPEL process is deployed. Depending on the infrastructure, it can also be impossible to answer your question with static analysis.
Regards,
Daniel