Alex,
Hmm - that is strange. Well, I'd definitely open an SR with Oracle to get the issue formally resolved.
In the meantime, you should be able to simply extract the bpel_PoSendPoToOtm_1_0.jar file and then edit the BPEL configuration files (bpel.xml and others) to match your server's configuration (such as the OTM URI, DbAdapter and AqAdapter connection strings, etc), then package it back up and deploy it to your BPEL server.
To repackage the jar, you'd use a command like:
Code:
jar c0mvf ./META-INF/MANIFEST.MF ../
bpel_PoSendPoToOtm_1_0.jar *
I'm sure you can accomplish all of this via Oracle's JDeveloper, though I tend to work directly with the xml files.
--Chris