Skip to main content
insightsoftware Documentation insightsoftware Documentation
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Gather User Information

You need to determine which users in your organization need to access Noetix views before adding them as Noetix query users.

Before you begin, you should make a list of the Oracle E-Business Suite users and responsibilities, and the database users who need to be set up as Noetix query users to grant them access to the views. This list should include:

  • The name for each user.

  • The appropriate Noetix roles to be assigned to each query user.

Note: We recommend you to create a new database user for each new Noetix query user rather than using the existing database users to avoid conflict in the security of the existing database users with the NoetixViews security owing to the granting of roles.

The following guidelines should be taken into consideration before adding a Noetix query user. These guidelines are applicable depending on the modules available in Oracle E-Business Suite and the corresponding NoetixViews modules that you have purchased:

  • Decide the Noetix roles corresponding to the NoetixViews modules that need to be granted to each Noetix query user. Before generating Noetix views and setting up database users, determine which Oracle
    E-Business Suite instance each Noetix query user should access through a Noetix role. The Noetix roles available at your site will vary depending on the types of modules you have installed, your Oracle configuration, and the NoetixViews product enhancements in your product package (for example, Cross Operations Extension (XOP)). When assigning roles to a Noetix query user, consider the level of access that the user should have to Oracle E-Business Suite data (for example, data rolling up to an inventory organization, an operating unit, or a ledger/set of books). For more information about how to assign roles, see Gather User Information.

    Note: Oracle E-Business Suite restricts the number of roles that can be granted to a user. The number varies based on the Oracle Database version. Assigning a user more than the maximum number of roles prevents the user from logging on. Neither Oracle E-Business Suite nor NoetixViews checks this limit; therefore, you need to keep track of how many roles you grant to the user.

  • Decide the flexfield security rules that need to be assigned to each Noetix query user requiring access to Accounting Flexfield data in Noetix views for General Ledger. Users can be set up to have no or full access to the Accounting Flexfield data. Custom access can be set for each combination of a chart of accounts and ledger/set of books. The responsibilities the users log on with can also determine Accounting Flexfield data access. For custom access, you must decide on the flexfield security rules that should be assigned to the user for each combination of a chart of accounts and ledger/set of books to limit access to Accounting Flexfield data. You can retrieve a list of flexfield security rules for each existing General Ledger user from General Ledger. Users who do not have access to data in Noetix views for General Ledger should ensure that their flexfield security rules are specified appropriately. For more information about how to assign flexfield security rules, see Gather User Information.

  • Decide the business groups that need to be assigned to each Noetix query user. The row-level security of each Noetix query user is determined based on the business groups and security profiles assigned to them in Oracle E-Business Suite. The row-level security determines their access to data in the Noetix views for the Oracle Advanced Benefits, Oracle Human Resources, Oracle Payroll, and Oracle Time and Labor. Both standard and global views of these modules allow users to access employee data based on business groups and security profiles. Global views also allow you to override the row-level security so that users can access all business groups within the organization hierarchy of a global security profile or access a custom list of business groups. For more information about how to assign business groups, see Gather User Information.

  • Decide the ledgers/sets of books that need to be assigned to each Noetix query user. The row-level security of each Noetix query user is determined based on the ledgers/sets of books assigned to them in Oracle
    E-Business Suite. The row-level security determines their access to data in the Noetix views for the Oracle Assets, Oracle U.S. Federal Financials, and Oracle General Ledger. Row-level security based on the ledgers/sets of books assigned is supported in the global Noetix views for Assets, U.S. Federal Financials, and General Ledger. However, row-level security based on the ledgers/sets of books and budget access levels is supported only in the global Noetix views for U.S. Federal Financials. A security similar to row-level security is also available for the standard and XOP forms of the views for U.S. Federal Financials. In the global form of the views, you can also override the existing row-level security of a Noetix query user to allow Noetix query users access all ledgers/sets of books or access a custom list of ledgers/sets of books. Also, for the Noetix views for U.S. Federal Financials, you can create custom lists of ledgers/sets of books and assign appropriate budget access levels for the Noetix query users to control their access to those ledgers/sets of books. For more information about how to assign ledgers/sets of books, see Gather User Information.

  • Decide the operating units that need to be assigned to each Noetix query user. The row-level security of each Noetix query user is determined based on the operating units assigned to them in Oracle E-Business Suite. The row-level security determines their access to data in Noetix views for Oracle Install Base, Oracle Order Management, Oracle Payables, Oracle Projects, Oracle Purchasing, Oracle Receivables, and Oracle Service Contracts. For Noetix views for Install Base, the row-level security of each Noetix query user is determined based on the combination of an item instance and operating unit assigned to them in Oracle
    E-Business Suite. In the global form of the views, you can override the row-level security to allow Noetix query users access all operating units or access a custom list of operating units. For more information about how to assign operating units, see Gather User Information.

  • Decide the inventory organizations that need to be assigned to each Noetix query user. The row-level security of each Noetix query user is determined based on the inventory organizations assigned to them in Oracle E-Business Suite. The row-level security determines their access to data in Noetix views for Oracle Bills of Material, Oracle Cost Management, Oracle Enterprise Asset Management, Oracle Inventory, Oracle Master Scheduling/MRP, Oracle Quality, and Oracle Work in Process. In the global form of the views, you can override the row-level security to allow Noetix query users access all inventory organizations or access a custom list of inventory organizations. For more information about how to assign inventory organizations, see Gather User Information.

  • Decide the service request types that need to be assigned to each Noetix query user. The row-level security of each Noetix query user is determined based on the service request types assigned to them in Oracle
    E-Business Suite. The row-level security determines their access to data in Noetix views for Oracle Depot Repair, Oracle Field Service, and Oracle TeleService. In the global form of the views, you can override the row-level security to allow Noetix query users access all service request types or access a custom list of service request types. For more information about how to assign service request types, see Gather User Information.

Published:

Gather User Information

You need to determine which users in your organization need to access Noetix views before adding them as Noetix query users.

Before you begin, you should make a list of the Oracle E-Business Suite users and responsibilities, and the database users who need to be set up as Noetix query users to grant them access to the views. This list should include:

  • The name for each user.

  • The appropriate Noetix roles to be assigned to each query user.

Note: We recommend you to create a new database user for each new Noetix query user rather than using the existing database users to avoid conflict in the security of the existing database users with the NoetixViews security owing to the granting of roles.

The following guidelines should be taken into consideration before adding a Noetix query user. These guidelines are applicable depending on the modules available in Oracle E-Business Suite and the corresponding NoetixViews modules that you have purchased:

  • Decide the Noetix roles corresponding to the NoetixViews modules that need to be granted to each Noetix query user. Before generating Noetix views and setting up database users, determine which Oracle
    E-Business Suite instance each Noetix query user should access through a Noetix role. The Noetix roles available at your site will vary depending on the types of modules you have installed, your Oracle configuration, and the NoetixViews product enhancements in your product package (for example, Cross Operations Extension (XOP)). When assigning roles to a Noetix query user, consider the level of access that the user should have to Oracle E-Business Suite data (for example, data rolling up to an inventory organization, an operating unit, or a ledger/set of books). For more information about how to assign roles, see Gather User Information.

    Note: Oracle E-Business Suite restricts the number of roles that can be granted to a user. The number varies based on the Oracle Database version. Assigning a user more than the maximum number of roles prevents the user from logging on. Neither Oracle E-Business Suite nor NoetixViews checks this limit; therefore, you need to keep track of how many roles you grant to the user.

  • Decide the flexfield security rules that need to be assigned to each Noetix query user requiring access to Accounting Flexfield data in Noetix views for General Ledger. Users can be set up to have no or full access to the Accounting Flexfield data. Custom access can be set for each combination of a chart of accounts and ledger/set of books. The responsibilities the users log on with can also determine Accounting Flexfield data access. For custom access, you must decide on the flexfield security rules that should be assigned to the user for each combination of a chart of accounts and ledger/set of books to limit access to Accounting Flexfield data. You can retrieve a list of flexfield security rules for each existing General Ledger user from General Ledger. Users who do not have access to data in Noetix views for General Ledger should ensure that their flexfield security rules are specified appropriately. For more information about how to assign flexfield security rules, see Gather User Information.

  • Decide the business groups that need to be assigned to each Noetix query user. The row-level security of each Noetix query user is determined based on the business groups and security profiles assigned to them in Oracle E-Business Suite. The row-level security determines their access to data in the Noetix views for the Oracle Advanced Benefits, Oracle Human Resources, Oracle Payroll, and Oracle Time and Labor. Both standard and global views of these modules allow users to access employee data based on business groups and security profiles. Global views also allow you to override the row-level security so that users can access all business groups within the organization hierarchy of a global security profile or access a custom list of business groups. For more information about how to assign business groups, see Gather User Information.

  • Decide the ledgers/sets of books that need to be assigned to each Noetix query user. The row-level security of each Noetix query user is determined based on the ledgers/sets of books assigned to them in Oracle
    E-Business Suite. The row-level security determines their access to data in the Noetix views for the Oracle Assets, Oracle U.S. Federal Financials, and Oracle General Ledger. Row-level security based on the ledgers/sets of books assigned is supported in the global Noetix views for Assets, U.S. Federal Financials, and General Ledger. However, row-level security based on the ledgers/sets of books and budget access levels is supported only in the global Noetix views for U.S. Federal Financials. A security similar to row-level security is also available for the standard and XOP forms of the views for U.S. Federal Financials. In the global form of the views, you can also override the existing row-level security of a Noetix query user to allow Noetix query users access all ledgers/sets of books or access a custom list of ledgers/sets of books. Also, for the Noetix views for U.S. Federal Financials, you can create custom lists of ledgers/sets of books and assign appropriate budget access levels for the Noetix query users to control their access to those ledgers/sets of books. For more information about how to assign ledgers/sets of books, see Gather User Information.

  • Decide the operating units that need to be assigned to each Noetix query user. The row-level security of each Noetix query user is determined based on the operating units assigned to them in Oracle E-Business Suite. The row-level security determines their access to data in Noetix views for Oracle Install Base, Oracle Order Management, Oracle Payables, Oracle Projects, Oracle Purchasing, Oracle Receivables, and Oracle Service Contracts. For Noetix views for Install Base, the row-level security of each Noetix query user is determined based on the combination of an item instance and operating unit assigned to them in Oracle
    E-Business Suite. In the global form of the views, you can override the row-level security to allow Noetix query users access all operating units or access a custom list of operating units. For more information about how to assign operating units, see Gather User Information.

  • Decide the inventory organizations that need to be assigned to each Noetix query user. The row-level security of each Noetix query user is determined based on the inventory organizations assigned to them in Oracle E-Business Suite. The row-level security determines their access to data in Noetix views for Oracle Bills of Material, Oracle Cost Management, Oracle Enterprise Asset Management, Oracle Inventory, Oracle Master Scheduling/MRP, Oracle Quality, and Oracle Work in Process. In the global form of the views, you can override the row-level security to allow Noetix query users access all inventory organizations or access a custom list of inventory organizations. For more information about how to assign inventory organizations, see Gather User Information.

  • Decide the service request types that need to be assigned to each Noetix query user. The row-level security of each Noetix query user is determined based on the service request types assigned to them in Oracle
    E-Business Suite. The row-level security determines their access to data in Noetix views for Oracle Depot Repair, Oracle Field Service, and Oracle TeleService. In the global form of the views, you can override the row-level security to allow Noetix query users access all service request types or access a custom list of service request types. For more information about how to assign service request types, see Gather User Information.

For an optimal Community experience, Please view on Desktop
Powered by Zendesk