This is strait out of the manual…

read more »

This is for new hire exports where you only want the most recent offer to be returned.  Remember to set the ownerQuery name.

<quer:filtering xmlns:quer="http://www.taleo.com/ws/integration/query">
<quer:equal>
<quer:field path="Offers"/>
<quer:query projectedClass="Offer" alias="My_Offer_Subquery">
<quer:projections>
<quer:projection alias="MaxOffer">
<quer:maximum>
<quer:field path="Offers,Number"/>
</quer:maximum>
</quer:projection>
</quer:projections>
<quer:filterings>
<quer:filtering>
<quer:equal>
<quer:field path="Application,Offers"/>
<quer:field ownerQuery="NewHire" path="Offers,Number"/>
</quer:equal>
</quer:filtering>
</quer:filterings>
</quer:query>
</quer:equal>
</quer:filtering>

You are correct, normally a record that is dropped from a net-change data file will result in it being deleted or de-activated in the zone by following net-change run.  However if there was a net-change setup run before the next ‘normal’ net-change than this wouldn’t happen.   This is because the net-change setup will delete the current net-change data repository and then re-populates it with zone values, but only for those records in the data file.  I’ve recently written an example for this scenario that may make this more clear.
read more »