Users/Roles Security in Oracle R12


Application Security is vital for ERP systems. Especially administrator has to monitor number of users accessing system and what roles and responsibilities does people have.

Manage start and end period of users to access into application.

Activate and de-activate user accounts and their responsibilities according to your corporate security policies

SQL query to find active users and their responsibilities

select user_name, application_name, responsibility_name,
       security_group_name,
       greatest(u.start_date, ur.start_date, r.start_date) start_date,
       decode(
             least(nvl(u.end_date, to_date('01/01/4712','DD/MM/YYYY')),
                      nvl(ur.end_date, to_date('01/01/4712','DD/MM/YYYY')),
                      nvl(r.end_date, to_date('01/01/4712','DD/MM/YYYY'))),
             to_date('01/01/4712','DD/MM/YYYY'), '',
             least(nvl(u.end_date,  nvl(ur.end_date, r.end_date)),
                      nvl(ur.end_date, nvl(u.end_date,  r.end_date)),
                      nvl(r.end_date,  nvl(u.end_date,  ur.end_date)))) end_date
from fnd_user u, fnd_user_resp_groups_all ur, 
     fnd_responsibility_vl r, fnd_application_vl a,
     fnd_security_groups_vl s
where a.application_id = r.application_id
and u.user_id = ur.user_id
and r.application_id = ur.responsibility_application_id
and r.responsibility_id = ur.responsibility_id
and ur.start_date <= sysdate
and nvl(ur.end_date, sysdate + 1) > sysdate
and u.start_date <= sysdate
and nvl(u.end_date, sysdate + 1) > sysdate
and r.start_date <= sysdate
and nvl(r.end_date, sysdate + 1) > sysdate
and ur.security_group_id = s.security_group_id
and r.version in ('4','W','M')
order by user_name, application_name, responsibility_name, 
      security_group_name

SQL query to find active responsibilities and their active users

select  application_name,responsibility_name,
       security_group_name, user_name,
       greatest(u.start_date, ur.start_date, r.start_date) start_date,
        decode(
             least(nvl(u.end_date,to_date('01/01/4712','DD/MM/YYYY')),
                     nvl(ur.end_date,to_date('01/01/4712','DD/MM/YYYY')),
                      nvl(r.end_date,to_date('01/01/4712','DD/MM/YYYY'))),
             to_date('01/01/4712','DD/MM/YYYY'),'',
 least(nvl(u.end_date,  nvl(ur.end_date, r.end_date)),
             nvl(ur.end_date, nvl(u.end_date,  r.end_date)),
             nvl(r.end_date,  nvl(u.end_date,  ur.end_date)))) end_date
from fnd_user u,fnd_user_resp_groups_all ur,
     fnd_responsibility_vl r,fnd_application_vl a, 
     fnd_security_groups_vl s
where a.application_id = r.application_id
and   u.user_id = ur.user_id
and   r.application_id = ur.responsibility_application_id
and   r.responsibility_id = ur.responsibility_id
and   ur.start_date <= sysdate
and   nvl(ur.end_date, sysdate + 1) > sysdate
and   u.start_date <= sysdate
and   nvl(u.end_date, sysdate + 1) > sysdate
and   r.start_date <= sysdate
and   nvl(r.end_date, sysdate + 1) > sysdate
and   ur.security_group_id = s.security_group_id
and   r.version in ('4','W','M')
order by application_name,responsibility_name,security_group_name, user_name



Comments

Post a Comment

Popular posts from this blog

How to use lexical parameters in Data template (XML document) R12

Lexical parameters can be added in data definition using &variable name This is flexible variable string where you can execute runtime conditions based on user-inputs Example 1. Append &gc_journal_filter at the end of sql statement 2. Define beforereport function in package signature FUNCTION beforereport RETURN BOOLEAN; 3. Define all the report parameters as a package variable in package signature including lexical parameters 4. Implement beforereport function by building your runtime conditions to be added to SQL statements  FUNCTION beforereport RETURN BOOLEAN IS  BEGIN          IF p_journal_source IS NULL THEN       gc_journal_filter := ' AND jh.je_source IN (''AutoCopy'',''Manual'')';     END IF;          IF p_journal_category IS NULL THEN       gc_journal_filter := 'AND jh.je_category IN (''Other'') ';     END IF;    RETURN TRUE;  END;
Read more

Query to get FSG report details with row/column set

Below query is to fetch FSG report titles, names, and description along with will give a view to list of row sets and column sets associated with the report. -- FSG REPORTS -- SELECT fst.id_flex_structure_name , R.NAME , R.report_title , R.DESCRIPTION , R.column_set "COLUMN SET" , rw2.structure_id , rw2.DESCRIPTION "COL DESC" , R.row_set "ROW SET" , rw.DESCRIPTION "ROW DESC" , R.report_display_set "DISPLAY SET" , R.content_set "CONTENT SET" , R.row_order "ROW ORDER" , R.rounding_option "RND" , u.user_name , u.DESCRIPTION , R.creation_date FROM rg_reports_v R    , fnd_id_flex_structures_v fst    , fnd_user u    , rg_report_axis_sets_v rw    , rg_report_axis_sets_v rw2 WHERE r.structure_id = fst.id_flex_num AND R.row_set_id     = rw.axis_set_id AND r.column_set_id  = rw2.axis_set_id AND SUBSTR(fst.id_flex_structure_name,1,2) IN ('DC') AND R.created_by     = u.user_id OR
Read more

Sub Inventory Transfer API.

Image
Sub Inventory transfer is used to move materials from one sub-inventory to another within same organization. This is especially used to 1. Adjust on-hand quantities between sub-inventories 2. Transfer to another sub-inventories for specific business need like additional sales 3. Damages/expiry products can be moved to non-asset sub-inventories to discard it from inventory valuation report and so on., Key elements 1. From sub inventory 2. To sub inventory 3. Organization 4. Inventory item 5. Transact quantity 6. Transact unit of measure 7. Transaction type 8. Transaction action 9. Transact Reference 10. Transact date 11. Lot Number Open Interfaces mtl_transactions_interface - is used to populate sub inventory transfer details mtl_transaction_lots_interface - is used to populate lot details for particular sub inventory transfer Base Tables mtl_material_transactions - is used to get all type of material transactions like sub-inventory transfer, inter-org tra
Read more