Implementing Transactional Security in Single OU through form personalization Version 1.0

Overview:
This document explains the procedure & step-by-step approach for implementing transactional security in single operating unit based on a segment in Chart of Accounts or any given criteria.

White Paper: Implementing transactional security in single operating unit of Oracle Applications Version 11.5.10

Introduction:

Transactional security has traditionally been one of the driving factors for businesses to opt of multiple operating units in Oracle Application Implementations. However, a large number of business establishments are now increasingly looking for transactional security even in the single operating unit. Transactional security in an operating unit can be of two types: ➢ To restrict access to transactional entry, say AP invoices etc, based on a specific chart of account or any given criteria ➢ To prevent users from viewing transactions, say AP invoices etc, with a specific chart of account or any given criteria even if the opt for a blind query by pressing Ctrl + F11

General Ledger security rules come handy in implementing the first part of the transactional security i.e. to prevent users from entering transactions with specific COA segments. However, GL security rules can be used only if the criterion is based on the COA segments. Also GL security rules have no effect on query mode. So viewing cannot be prevented with the help of security rules.

Solution Area

Transaction security can be achieved in single operating unit with the help of Forms personalization. Using this, we can even prevent users from viewing a particular transaction based on the given criteria. Even if the user enters Ctrl + F11 the form will retrieve all the transactions except the ones which we are trying to prevent. As the security is