My Oracle Support Banner

BSO Webservice: Control Actions (Cancel, Finally Close, Close) and Releasing Holds on Purchase Orders Causes Revision Increments (Doc ID 2117282.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Purchasing - Version 12.2.2 to 12.2.4 [Release 12.2]
Information in this document applies to any platform.

Symptoms

Using Purchasing, the customer is using the BSO Webservice to maintain the same po data in 2 instances. When they place a PO on hold in the source instance, then release the hold, the destination (instance the po is copied to) PO ends up with a Rev 1 while the source instance-the PO release still has a REV 0 on it.



IN the example we have 2 instances. Source instance - and Destination instance-this is the instance the Source PO release gets copied to using the BSO Web Service.


STEPS
-------------------
1. Login to the E-Business Suite and choose the Purchasing Module.
2. Create a PO , approve and put on hold
3. Validate the PO is copied to the destination instance and is on hold
4. Remove the hold from the PO in the source instance. Review that the po is now approved and REV is 0
5. BSO webservice is invoked, payload file is created and sent to destination instance and destination po is updated to remove hold
6. Review the destination PO is now not on hold, and is approved, but the REV is 1, Not 0.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.