Skip to main content

Working with Noetix Query Users and Roles

Gather User Information

Before you create the Noetix query users, 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:

  • Name of each user

  • Appropriate Noetix roles to be assigned to each query user.

NOTE: insigihtsoftwarerecommends that 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 Noetix Views (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. For more information, see Grant a Role.

Important: IMPORTANT: 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 business groups that need to be assigned to each Noetix query user so that the users can access only the data corresponding to the assigned business groups in the Noetix views for Oracle Human Resources, Oracle Advanced Benefits, Oracle Payroll, and Oracle Time and Labor. For more information, see Manage Access to Data Based on Business Groups.

  • Decide the ledgers/set of books that need to be assigned to each Noetix query user so that the users can access only the data corresponding to the assigned ledgers in the Noetix views for Oracle Assets, Oracle U.S. Federal Financials, and Oracle General Ledger. For more information, see Manage Access to Data Based on Ledgers.

NOTE: In accordance with the changes made in Oracle E-Business Suite Release 12, all references to the term “set of books” have been replaced with “ledger” .

  • Decide the operating units that need to be assigned to each Noetix query user so that the users can access only the data corresponding to the assigned operating units in the Noetix views for Oracle Install Base, Oracle Order Management, Oracle Payables, Oracle Projects, Oracle Purchasing, Oracle Receivables, and Oracle Service Contracts. For more information, see Manage Access to Data Based on Operating Units.

  • Decide the inventory organizations that need to be assigned to each Noetix query user so that the users can access only the data corresponding to the assigned inventory organizations in the 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. For more information, see Manage Access to Data Based on Inventory Organizations.  

  • Decide the service request types that need to be assigned to each Noetix query user so that the users can access only the data corresponding to the assigned service request types in the Noetix views for Oracle Depot Repair, Oracle Field Service, and Oracle TeleService. For more information, see Manage Access to Data Based on Service Request Types.

  • Decide the flexfield security rules that need to be assigned to each Noetix query user for accessing Accounting Flexfield data returned by the views based on the flexfield security rules assigned to the users. For more information, see Manage Access to Accounting Data Based on Flexfield Security Rules.

Was this article helpful?

We're sorry to hear that.