RE: How Stored Procedures & Joins work internally when we trying to Retrieve information through eConnect using DocType in eConnect_Out_Setup
If I understand you correctly, then you wish to see what SQL is generated by eConnect when using the eConnect_Out_Setup table to fetch data via a eConnect requester doc.
For each row in the out table there is a stored procedure generated, so for your example,
taRequesterCustomer1 is an example of the procedure that relates to the first customer row in the setup table.
The catch is that these procedures (and the procedure that generates them) are encrypted.
Using SQL profiler won't help either.
If you know how to decrypt stored procedures then this is the only option I can see you having.
Tim