E1: SEC: JAS Message "UPDATE OPERATION IS NOT ALLOWED ON TABLE" in Headerless Detail Form Application P4105 After Update to Tools Release 184.108.40.206 and above
(Doc ID 2702726.1)
Last updated on AUGUST 20, 2020
Applies to:JD Edwards EnterpriseOne Tools - Version 9.2 and later
Information in this document applies to any platform.
After update to tools release 9.2.3.x in Headerless Detail form in P4105 user gets popup message
|JAS_MSG349: Row Security Violation - Update operation is not allowed on table|
including message in e1root.log :
|[UPDATE_VALUE_NOT_VALID_FOR_FIELD] Update value <row security secured value> not valid for field Table.DDAlias
e.g. [UPDATE_VALUE_NOT_VALID_FOR_FIELD] Update value 07 not valid for field F4105.LEDG.
when web runtime issues table update on table column set up with Inclusive row security Change=N though user has not changed the value in the grid column.
This confuses users who think the message is for the grid column value they are allowed to change with Inclusive row security Change=Y when in fact the change has been updated in the table.
By design, ALL grid rows in Headerless Detail form are updated, even grid rows where grid column values have not been changed.
The "Row Security Violation" popup message occurs as a result of <Bug 28276570> implemented in tools release 220.127.116.11. Additional details in E1: SEC: Row Security with Restricting Update Actions Does Not Restrict Users from Changing Based on the Defined Row Security (WEB Client Only) (Doc ID 2433777.1).
Prior to tools release 18.104.22.168 users get no popup message.
Web runtime issues table update, then Inclusive Row security process appends values users have access to (Change=Y) in the "Where clause" of the SQL Update. Hence SQL Update does not process on the values users are secured from.
Update to tools release 9.2.3.x, 22.214.171.124 through 126.96.36.199.
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