My Oracle Support Banner

Need To Restrict The Operating Unit when search is done in OAT View Transactions (Doc ID 1607268.1)

Last updated on JULY 14, 2020

Applies to:

Oracle Asset Tracking - Version 12.1.3 to 12.1.3 [Release 12.1]
Oracle Installed Base - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
Unable to Restrict The Operating Unit when search is done in OAT View Transactions


All the pending transactions from every Operating Unit are displayed in the OAT Transactions Tab, when it is necessary to identify the pending transactions to send from Oracle Asset Tracking to Oracle Fixed Assets Mass Additions.
This occurs even though the profile option: "CSI: Operating Restriction" is enabled and properly configured.

EXPECTED BEHAVIOR
-----------------------
Expect to be able to use "CSI: Operating Restriction" in OAT > Transactions tab

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Set up "CSI: Operating Restriction" for user to view one OU "xx"
1. "Asset Tracking Super User" responsibility
2. Transactions > View Transactions
3. Search any "Source Transaction Type"
4. Results show transactions from ALL Operating Units, not just OU "xx", as expected.

Changes

 

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!


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