Description:
Steps to reproduce:

1.  Create a Business Process.
2.  Import the attached WSDLs and XSDs.
3.  Copy and paste the following Import, Partner Link and Variables statements
into your existing BPEL (for convenience, you may create by scratch if you like)
4.  Create a Receive activity in the Sequence.
5.  Select the Property Editor for the Receive activity
6.  Try to browse for a variable.

Result:  There is no variable to choose from, even though a number of variables
have already been declared.

Expected Result:  All variables declared should be available to assign to the
Receive activity.

Description (Entry 2):
In the receive property editor, did you select a PartnerLink and Operation
before going to Browse.  The variables available under Browse are filtered based
on the partnerlink/operation chosen.

Evaluation:
I see a problem but I would describe it differently.

If I create a project and a BPEL process. 
Then I use the Retrieve WSDL/XSD wizard to retrieve all of the xsd and wsdl
files in the attachment for this bug.
Thne I copy and paste the bpel source from the attached bpel file into my bpel
process.
Then I look at Navigator and Diagram.
I see variables in the Navigator.
But I do not see any partner links in the diagram. 

Even though the bpel now contains this set of partner link definitions:
        <partnerLink name="Finance" partnerLinkType="ns1:FinancePartnerLinkType"
partnerRole="Finance"/>
        <partnerLink name="BookValue"
partnerLinkType="ns1:BookValuePartnerLinkType" partnerRole="BookValue"/>
        <partnerLink name="AdjusterCallback"
partnerLinkType="ns1:SubmitAdjustmentPartnerLinkType" myRole="Insurer"/>
        <partnerLink name="Adjuster"
partnerLinkType="ns1:AdjusterPartnerLinkType" partnerRole="Adjuster"/>
        <partnerLink name="ClaimNumberer"
partnerLinkType="ns1:ClaimNumbererPartnerLinkType" partnerRole="ClaimNumberer"/>
        <partnerLink name="Customer"
partnerLinkType="ns1:FileClaimPartnerLinkType" myRole="ClaimServiceProvider"/>

None of them are being rendered as PartnerLinks.

Now if I DnD the Wrapper.wsdl into the Diagram, I am presented with ParnterLink
editor and I can choose from the drop down list any of the PLTs defined in
Wrapper, and I can create the exact same PartnerLink definition as above, and
this time it will render. Then I can create web service activities to connect my
process to the partners and the variables show up just fine.

So for me the problem and question is why are the PartnerLinks not rendering in
the initial BPEL source copy / paste phase? What is difference b/t the OM
resulting from the action of DnD'ing a partner WSDL? It appears to generate
exactly the same PL definition. Yet one renders and one does not?

This is the bpel in the attachment which is not rendering

        <partnerLink name="Finance" partnerLinkType="ns1:FinancePartnerLinkType"
partnerRole="Finance"/>

This is the bpel that the IDE generated after I DnD'd the Wrapper.wsdl into the
very same process. And this does render properly?

    <partnerLink name="Wrapper" partnerLinkType="ns1:FinancePartnerLinkType"
partnerRole="Finance"/>

Evaluation (Entry 2):
Following the Mike's scenario, i found that missing PL is a diagram bug. Model
just says that PartnerLinkContainer was added. Diagram ignores this event
because it have no visual representation for container itself. But this new
container have some PLs inside which needs to be displayed. The same situation
with PartnerLinkContainer deletion. In that case PLs remains on diagram and
results in IllegalStateException if user tries to open custom editor for it(I
already reported this issue to QA to file bug).

Workaround:
Type in the code:

Add in the receive parameters, variable="FileClaimInput"