Formulator: Cannot Use Organization Access To separate Update Rights To Responsibilities
(Doc ID 1367420.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Process Manufacturing Product Development - Version 12.0.6 and later
Information in this document applies to any platform.
***Checked for relevance on 22-JUL-2013***
On : 12.0.6 version, Setup Issues
You know Formula Security functionality but you don’t want to implement it due to impact on custom functionality of apps initialization procedure that should be included in several custom objects that access to formula tables.
This customer is not using the formula security, but setting up the organization access to the responsibility level. When the formula is queried for an organization which has no access, the form should be in query mode only.
So expectation is to be able to define responsibilities with assigned only one organization access and to be able with this responsibilities to update formula details only for the granted organization: formulas for all other organizations should be visible but non updatable..
But organization access is not honored and you’re able to modify formulas of organizations (not granted) belonging even to other operating units.
The issue can be reproduced at will with the following steps:
1. Setup Organization access for Formulator responsibility to different Organizations A01 and A02.. A04:
Resp 'N01 Formulator' linked to Org A01
Resp 'N02 Formulator' linked to Org A02
Resp 'N03 Formulator' linked to Org A03
Resp 'N04 Formulator' linked to Org A04
2. From a responsibility N04 Formulator A01 (for example) it wasn't possible to update a version formula that belong another organization.
3. Consider formula's F102version 1 item 10020600 that belongs to organization A02.
The problem is that is possible to update formula from responsibility N01 formulator whereas system should allow to update formula's version of organization A01 only
The issue has the following business impact:
Due to this issue, loose of use of organization access to restrict access
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|