Please help with error message invoking external service from BPEL

Question

Yes, I'm new to Oracle SOA Suite and BPEL Process manager. I've searched the forums, OTN, and Google and have not found any description of this error message:
"oracle.fabric.common.FabricException: Number of SOAP body elements and parts do not match in operation: <operation-name>"
Using JDeveloper 11.1.1.2.0 and WebLogic/SOA 10.3.2.0.
The BPEL process was built completely using JDeveloper's graphical tools... I haven't done any raw editing of the BPEL files yet. What types of things might I possibly be doing wrong that would cause this error to occur? Any idea what two things the server is comparing and deciding that there's a mismatch? It doesn't look like it is even attempting to invoke the external service, but bailing out before that, thinking that it's going to send bad data. Below is a bit more detail.
Also, I loaded up the WSDL (same one that I gave to JDeveloper) into SOAPUI. Then I took the payload that SOA was about to send (see below) and pasted it into SOAPUI. SOAPUI didn't complain and the target web service accepted the message and produced a "success" response. It looks like the payload is correct, so I don't know why SOA is complaining.
Thanks for any help you can offer.
=====================================================
Faulted while invoking operation "UpsertEmp" on provider "SiebelUSEmployeeIntegration".
<messages>
<input>
<UpsertEmpInput>
<part name="SiebelMessage">
<SiebelMessage>
<ns1:USEmployment>
<ns1:globalId>123456abcdef</ns1:globalId>
<ns1:employeeId>000123456</ns1:employeeId>
<ns1:effDt>1/1/2009</ns1:effDt>
<ns1:emplStatus>A</ns1:emplStatus>
<ns1:supported>N</ns1:supported>
<ns1:employed>Y</ns1:employed>
<ns1:activeStatus>Y</ns1:activeStatus>
<ns1:hrEditOnly>Y</ns1:hrEditOnly>
<ns1:paygroup/>
<ns1:statusCode/>
<ns1:origHireDate/>
<ns1:termDate/>
<ns1:latestHireDate/>
<ns1:locationCode/>
<ns1:locationDescr>Somewhere</ns1:locationDescr>
<ns1:positionCode/>
<ns1:jobCode/>
<ns1:jobDescr/>
<ns1:supervisorEmplid>000654321</ns1:supervisorEmplid>
<ns1:deptCode>ITG</ns1:deptCode>
<ns1:deptDescr>Information Technology Group</ns1:deptDescr>
<ns1:ministryCode/>
<ns1:ministryDescr>Core Services</ns1:ministryDescr>
<ns1:subministryCode/>
<ns1:subministryDescr>Information Technology Group</ns1:subministryDescr>
<ns1:wwcFreeSubFlag>N</ns1:wwcFreeSubFlag>
<ns1:lakeHartMC>1234</ns1:lakeHartMC>
<ns1:testFlag>Y</ns1:testFlag>
</ns1:USEmployment>
</SiebelMessage>
</part>
</UpsertEmpInput>
</input>
<fault>
<bpelFault>
<faultType>
<message>0</message>
</faultType>
<remoteFault>
<part name="summary">
<summary>oracle.fabric.common.FabricException: Number of SOAP body elements and parts do not match in operation: UpsertEmp</summary>
</part>
<part name="detail">
<detail>Number of SOAP body elements and parts do not match in operation: UpsertEmp</detail>
</part>
</remoteFault>
</bpelFault>
</fault>
<faultType>
<message>0</message>
</faultType>
</messages>

Answer 1

Welcome to BPEL. Take a moment, and write "it's a namespace issue" on a sheet of paper. Post it near your monitor. It won't always be a namespace issue, but it's usually a good thing to suspect first! Is the namespace prefix ns1: defined somewhere? Does your XML that is being sent really match what the WSDL has for input to the UpsertEmp operation? The namespaces for each element level in the XML need to match, not just the lowest level.
When problems like this get really sticky, you can use TCP tunneling (obtunnel shell?) to capture what is really being sent to the server, and compare that to what is sent from SOAPUI. That's more useful if it's a subtle header problem, but you may get better error messages if you catch the BPEL message and send it using SOAPUI.
Good Luck, Andy