Scope filters for Authorizations Insight for Oracle

Authorizations Insight for Oracle enables you to select the following filters to define your analysis scope:

  • Exclusions

    By default, an analysis will not produce violations for excluded objects. Use this filter to include or ignore excluded users and responsibilities.

  • Analysis Filters

    By default, all primary violating objects are selected for analysis. Use this filter to analyze users, responsibilities, or both.

  • Active/Inactive Users

    By default, inactive users are not considered when identifying a violation. Use this filter to include inactive users.

  • Active/Inactive Responsibilities

    By default, inactive responsibilities are not considered when identifying a violation. Use this filter to include inactive responsibilities.

  • Active/Inactive User- Responsibilities

    By default, inactive user responsibilities are not considered when identifying a violation. Use this filter to include inactive user responsibilities.

  • Profile Options

    Select this option if you want an analysis to consider the violations that occur within the same profile options. Select profile option as follows:

    1. Click the Browse icon. The Browse Profile Options pop-up window is displayed.
    2. Select the required profile options and click OK. The number of profile options selected will be displayed in the Scope Filters section on the user interface.
      Note: If you want to identify violations in the same operating unit, then the option Same Operating Unit should be selected during analysis. If violations need to be identified across different operating units, this option should not be selected.
      Note: You may select multiple profile options to schedule an analysis.
  • Analyze NULL Prompts: Select this option to analyze the prompts to which menus and functions are not assigned.
    Note: You can set limits for responsibility violations and user violations through Analysis Settings. When this limit is reached during analysis, no more violations will be generated.

Scenarios in case of different time zones

After scoping the data using these filters, the actual data that is analyzed may vary if ERP server and the Infor Risk & Compliance application server are in different time zones.

For example, consider that the Infor Risk & Compliance application server is in India and ERP server is in US. In such cases the following scenarios may occur:

  • Users or user-responsibility assignments valid in ERP may not participate in the analysis.
  • Users or user-responsibility assignments expired in ERP may undergo an analysis.

Consider a user is assigned a responsibility in Oracle and the responsibility assignment expiry date is 12th June 2012. Perform an analysis on 13th June 8.00 am IST (which is 12th June 10.30 PM EST).

As per the application server time zone, the user-responsibility assignment is expired and will not be participate in the analysis (unless explicitly selected the scoping filter to analyze expired assignments), whereas the user-responsibility assignment is actually valid in the ERP system.