You can ignore my my question from last Thursday, I actually figured why I cannot deploy the appliance in vSphere. The problem is that vSphere sees the value of ovf:capacity field in the DiskSection of the OVF and thinks that it is too small. Oracle VM and VirtualBox are both ok with this field, maybe they don't even look at it. I am not sure what vSphere is comparing ovf:capacity against in order to come to that conclusion though. To work around this issue I was able to double the value of the ovf:capacity field and run OVF Tool against it. And in fact, if I pass the --lax parameter to OVF Tool without your workaround on May 8 I am still able to deploy the OVF appliance. I successfully tried this technique with both the PeopleSoft HCM and FSCM PUM OVAs. (I think they call this revision of their OVAs 'PI 6')
In summary, here's what I did:
I have attached a copy of the OVF file that I edited as described above.