PO Change History Page Only Displays Changed Order Information For the Default Operating Unit (Doc ID 1679247.1)

Last updated on JUNE 08, 2017

Applies to:

Oracle iSupplier Portal - Version 12.2.3 and later
Information in this document applies to any platform.

Symptoms

In Oracle Purchasing and Oracle iSupplier Portal, Release 12.2.3, when searching for revised purchase orders on the PO Change History page, the changed purchase orders are only found for the defaulted operating unit. If the defaulted Operating Unit (OU) value is changed to a different OU, the existing changed orders for the other OUs are not found.

It is expected that the PO Change History page display the revised POs for the selected operating unit.


Steps To Reproduce

The issue can be reproduced at will with the following steps in a Vision Demo environment:
1. Log in to Oracle Applications, using the Purchasing, Vision Operations responsibility.
2. On the Personal Profiles form, set the MO: Default Operating Unit profile to "Vision Operations" at the User level. Log out and log back in to Oracle Applications.
(Note: This may also require a clearing of the functional cache for the change to take full effect.)
3. Create a new standard purchase order, one line/shipment/distribution. Save and approve the PO.
4. Increase the quantity on the line --> this creates the document revision. Save and approve the document revision.
5. Navigate to Purchase Orders > PO Change History.
6. On the Purchase Order Revision History page, the Operating Unit field has defaulted to value "Vision Operations" (as per the profile option setting in Step 2 above). Enter the PO Number created in Step 3, and click the Go button.
- In the search results, the PO with Revision 1 appears. This is the expected result and is proper functionality.
7. Now, on the Personal Profiles form, set the MO: Default Operating Unit profile to "Vision Services" at the User level. Log out and log back in to Oracle Applications.
(Again, this may also require a clearing of the functional cache for the change to take full effect.)
8. Navigate to Purchase Orders > PO Change History.
9. On the Purchase Order Revision History page, the Operating Unit field has now defaulted to value "Vision Services" (as per the profile option setting in Step 7 above). Enter the same PO Number created in Step 3, and click the Go button.
- In the search results, the message "No results found" appears.



Business Impact

Due to this issue, users cannot view the PO changes from other operating units, without changing to a responsibility tied specifically to that operating unit.



Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms