PO Revision Number mismatch between two systems
We are using the PRISM product integrated with OCI to Oracle Financials. Most of the POs gets generated from PRISM and flow thru OCI to the Oracle Purchasing module. We have a customization developed on the Oracle Purchasing side, which allows to update the PO ( Using the standard CANCEL API) on certain conditions. All these POs which have been updated in the Oracle Purchasing side are out of SYNC with the PRISM POs. The Setup option "Archive On" was set to "Approval" and will be increasing the revision number and archives the versions to the standard Archive tables.
Is there a quick way to deal with this situation, to maintain the archival history and to make both the products in SYNC. Increasing the PRISM version number to match with the Oracle POs version number is ruled out as it is more cumbersome.