Administrator Guide - Magnitudesupport.noetix.com/docs/707/610/noetixviewsadministratorguide.pdf ·...

Administrator Guide

®

NoetixViews for Oracle E-Business Suite Administrator GuideNoetixViews 6.1 for Oracle E-Business Suite

This document was released on October 11, 2011. Please go to Answer ID 707 (INFO: Documentation for NoetixViews for Oracle E-Business Suite) on the Noetix online knowledge base; an updated version of this document might be available.

Copyright © 2002–2011 Noetix Corporation. All rights reserved.

No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission from Noetix Corporation.

The information in this document is subject to change without notice. Noetix Corporation strives to keep this information accurate but does not warrant that this document is error-free.

Noetix, NoetixViews, Noetix QueryServer, Noetix WebQuery, and the Noetix logo are registered trademarks of Noetix Corporation. Other “Noetix” marks are trademarks of Noetix Corporation.

NoetixViews is protected by United States Patent 7,350,191.

http://noetix.custhelp.com/cgi-bin/noetix.cfg/php/enduser/std_adp.php?p_faqid=707

Oracle, JD Edwards, PeopleSoft, Retek, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Oracle E-Business Suite, Oracle Database, Oracle Discoverer, Oracle Business Intelligence, SQL*Plus, SQL*Net, SQL*Loader, PeopleSoft Enterprise, Siebel Business Applications, and other Oracle, PeopleSoft, and/or Siebel product names referenced herein are trademarks or registered trademarks of Oracle Corporation. Sun, Java, Java Runtime Environment, and other Sun product names referenced herein are trademarks or registered trademarks of Sun Microsystems, Inc. Microsoft, Microsoft Excel, Microsoft Internet Explorer, Windows, Microsoft SQL Server, Microsoft SQL Server Reporting Services, Internet Information Services, Microsoft .NET Framework, Microsoft ASP.NET, Microsoft Data Access Components, and other Microsoft product names referenced herein are trademarks or registered trademarks of Microsoft Corporation. Adobe, Acrobat, the Adobe PDF logo, Adobe Flash Player, and Adobe Reader are trademarks or registered trademarks of Adobe Systems Incorporated. IBM, Cognos, Cognos Framework Manager, Cognos Configuration, Cognos Query Studio, Cognos Report Studio, Cognos Connection, and other Cognos server or modeling product names mentioned herein are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. SAP is a registered trademark of SAP AG. BusinessObjects is a trademark of Business Objects, an SAP company. Web Intelligence and Xcelsius are trademarks or registered trademarks of Business Objects, an SAP company.All other company and product names mentioned herein are used for identification purposes only and may be trademarks or registered trademarks of their respective owners.

The applications grep, egrep, and sed are distributed with NoetixViews for Oracle E-Business Suite under the GNU General Public License. Noetix hereby offers to give any third party, for a charge no more than our cost of physically performing the distribution, a complete, machine-readable copy of the grep, egrep and/or sed source code, which shall be distributed under the GNU General Public License and supplied on a medium customarily used for software interchange. Requests for source code must be submitted within three years of this offer and should be directed to Noetix Corporation, 5010 148th Ave NE, Suite 100, Redmond, WA 98052-5119, USA.

Contents v

ContentsPreface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiAbout This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiNoetix Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Chapter 1 About NoetixViews. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Benefits of NoetixViews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2NoetixViews Basics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

NoetixViews Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Noetix Help File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Noetix Query Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Noetix Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5General Ledger Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Multi-Currency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

NoetixAnswers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2 Forms of Noetix Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Standard Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10XOP Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

How XOP Views Are Generated . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Guidelines for Using XOP Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Global Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Key Flexfield Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 3 Installing NoetixViews for Oracle E-Business Suite . . . . . . . . . 29Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Preinstallation Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Review System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Grant Administrative Privileges for NoetixViews Administrator. . . . . 31

Install the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Install the Software on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Load the Software on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Upgrade the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Choose an Upgrade Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Option 1: Upgrade the Software on Windows . . . . . . . . . . . . . . . . . . 45Option 2: Upgrade Using Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

vi NoetixViews for Oracle E-Business Suite Administrator Guide

Chapter 4 Generation of Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51Pre-Generation Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Back Up Oracle E-Business Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . .53Obtain Account Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53Determine Oracle Tools Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . .53Create Tablespace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54Install Data Mart (When Using NoetixViews for Oracle Payroll) . . . .55Update Scripts Before Generation . . . . . . . . . . . . . . . . . . . . . . . . . . .55Decide on Noetix System Administration User Name . . . . . . . . . . . .59Name Role Prefixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Choose Help Formats to Generate . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Choose a Generation Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62Option 1: Generate Using NoetixViews Administrator . . . . . . . . . . . . . . . . . . .63

Start NoetixViews Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . .64Stage 1: Create Noetix System Administration User Account . . . . . . .67Stage 2: Grant Limited Privileges to AOL Data . . . . . . . . . . . . . . . . .73Stage 3: Set Up Noetix System Administration User Account. . . . . . .76Stage 4: Generate Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79Verify Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93Generate Noetix Help File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

Option 2: Generate Using Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97Stage 1: Create Noetix System Administration User Account . . . . . . .98Stage 2: Grant Limited Privileges to AOL Data . . . . . . . . . . . . . . . .100Stage 3: Set Up Noetix System Administration User Account. . . . . .101Stage 4: Generate Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102Verify Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109Generate Noetix Help File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

Run Noetix Answer Builder (When Using Noetix Platform) . . . . . . . . . . . . .115

Chapter 5 Noetix Query User Management . . . . . . . . . . . . . . . . . . . . . . .119Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120Gather User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123Create Noetix Query Users Using GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127

Add a Noetix Query User Using an Existing User . . . . . . . . . . . . . .127Create a Noetix Query User Using the Add Wizard . . . . . . . . . . . . .177

Create Noetix Query Users Using Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . .190Add Existing Users as Noetix Query Users . . . . . . . . . . . . . . . . . . . .190Create a Database User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197

Modify Noetix Query Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199Modify Default Flexfield Security Rules . . . . . . . . . . . . . . . . . . . . . .204

Delete Noetix Query Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205

Contents vii

Data Security in NoetixViews. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208View and Answer Authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Data Access Privilege . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Refresh Security for Query Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Provide Row-Level Security in BI Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Manage BI Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222Manage BI Tool Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Update Reporting Tool or EUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230Generate Noetix Query Users into NQS (When Using Noetix Platform). . . . 230

Chapter 6 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232Locate Important Directories and Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

When You Generate Noetix Views. . . . . . . . . . . . . . . . . . . . . . . . . . 232When You Regenerate or Upgrade Views. . . . . . . . . . . . . . . . . . . . . 233

NoetixViews Administrator Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234Change Base Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . 235Explore from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236Grant Select Any Table/Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . 237Override Oracle Tool Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Enable/Disable Administrator Functionality . . . . . . . . . . . . . . . . . . 239

Administrative Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240Available UNIX Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240Run a UNIX Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241Available SQL and MS-DOS Scripts . . . . . . . . . . . . . . . . . . . . . . . . 241Run an SQL or MS-DOS Script . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Resolve Issues in Your Noetix Views Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244Refresh Key Flexfield Data Cache Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Full Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245Incremental Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Refresh Parent-Child Hierarchy Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249NoetixViews Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Understand NOETIX_SYS Schema. . . . . . . . . . . . . . . . . . . . . . . . . 252Customize NoetixViews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253Suppress Noetix Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254Suppress Parent-Child Hierarchy Views in NoetixViews . . . . . . . . . 254Suppress Charts of Accounts in NoetixViews . . . . . . . . . . . . . . . . . . 256NCM Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

viii NoetixViews for Oracle E-Business Suite Administrator Guide

Chapter 7 Regeneration of Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260Choose a Regeneration Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261Option 1: Regenerate Using NoetixViews Administrator . . . . . . . . . . . . . . . .263Option 2: Regenerate Using Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266Option 3: Regenerate Using Scheduled Concurrent Manager Job. . . . . . . . . .268

Initial Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268Schedule Regeneration in Concurrent Manager . . . . . . . . . . . . . . . .278

Option 4: Regenerate Using Scheduled Cron Job . . . . . . . . . . . . . . . . . . . . . .280Initial Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280Schedule Regeneration in Cron . . . . . . . . . . . . . . . . . . . . . . . . . . . .287View Regeneration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291Edit or Delete a Cron Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291

Regenerate Noetix Answers/Help File Separately . . . . . . . . . . . . . . . . . . . . . .293Regenerate Noetix Answers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293Regenerate Noetix Help File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .297

Chapter 8 Uninstalling the Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . .307Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308Uninstall the Software from Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308Uninstall the Software from UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .312

Appendix A Module-Specific Information. . . . . . . . . . . . . . . . . . . . . . . . . .313NoetixViews for Oracle General Ledger . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314

General Ledger Data Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315Archived Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317About Access to Accounting Data. . . . . . . . . . . . . . . . . . . . . . . . . . .317Configure Default Flexfield Security Rules Settings . . . . . . . . . . . . .323

NoetixViews for Oracle Human Resources . . . . . . . . . . . . . . . . . . . . . . . . . . .327About Access to Human Resources Data . . . . . . . . . . . . . . . . . . . . .328Security Policies in Views for HRMS . . . . . . . . . . . . . . . . . . . . . . . .329SIT Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .340EIT Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .342Oracle DateTrack and NoetixViews . . . . . . . . . . . . . . . . . . . . . . . . .343Benefit Classification Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . .357Support for Additional Personal Details Descriptive Flexfield. . . . . .357Default Hours for Salary Calculations . . . . . . . . . . . . . . . . . . . . . . .359Setup Business Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .359Optional Views and Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . .360Performance-Related Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .360

Contents ix

NoetixViews for Oracle Payroll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362About Noetix Payroll Data Mart . . . . . . . . . . . . . . . . . . . . . . . . . . . 363Before Installing Noetix Payroll Data Mart . . . . . . . . . . . . . . . . . . . 364Installing Noetix Payroll Data Mart . . . . . . . . . . . . . . . . . . . . . . . . . 364Populating Noetix Payroll Data Mart. . . . . . . . . . . . . . . . . . . . . . . . 368Maintain Noetix Payroll Data Mart . . . . . . . . . . . . . . . . . . . . . . . . . 370Upgrade Noetix Payroll Data Mart . . . . . . . . . . . . . . . . . . . . . . . . . 373Uninstall Noetix Payroll Data Mart . . . . . . . . . . . . . . . . . . . . . . . . . 374

NoetixViews for Oracle Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376Multi-Currency Terminology in Oracle Projects . . . . . . . . . . . . . . . 377Effect of Multi-Currency on Different Types of Projects . . . . . . . . . 378Multi-Currency Activation in NoetixViews for Oracle Projects . . . . 379Results of Multi-Currency Activation. . . . . . . . . . . . . . . . . . . . . . . . 380Changing the Multi-Currency OptionWhile Regenerating Noetix Views . . . . . . . . . . . . . . . . . . . . . . . . . . 381Subject Areas in Oracle Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382

NoetixViews for Oracle U.S. Federal Financials . . . . . . . . . . . . . . . . . . . . . . . 385Subject Areas of NoetixViews for Oracle U.S. Federal Financials . . . 387

Appendix B Legal Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389Third-Party License Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395

Preface

This preface is an introduction to the NoetixViews for Oracle E-Business Suite Administrator Guide. It discusses the administrator guide’s content and assumptions, as well as how to contact Noetix Corporation for support.

xii NoetixViews for Oracle E-Business Suite Administrator Guide

About This GuideThe NoetixViews for Oracle E-Business Suite Administrator Guide provides system administrators with complete installation instructions for NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator) and generation instructions for NoetixViews for Oracle E-Business Suite (NoetixViews), as well as a general reference for managing and optimizing the product within an enterprise.

This administrator guide assumes that NoetixViews or Oracle E-Business Suite has been purchased from Noetix Corporation and that the reader is primarily responsible for the Noetix views generation and maintenance tasks. This administrator guide also requires a general knowledge of the system environment, client/server architecture, Oracle database, Oracle E-Business Suite configuration, and using common graphical user interfaces.

This administrator guide also assumes that readers have a basic knowledge of any query tool they may use to access NoetixViews.

We welcome your input on the quality, accuracy, and usefulness of this document. Please send your comments and suggestions to Noetix Technical Support.

Noetix Technical SupportThe Noetix Technical Support Web site is available if you have any questions or encounter a problem during installation or operation of your Noetix software. This site is updated regularly with the latest information on Noetix products.

http://support.noetix.com


Chapter 1

About NoetixViews

This chapter provides an overview of the concepts and components of NoetixViews for Oracle E-Business Suite (NoetixViews).

2 NoetixViews for Oracle E-Business Suite Administrator Guide

OverviewNoetixViews for Oracle E-Business Suite (NoetixViews) unlocks the data hidden in corporate databases by providing user-friendly, plug-and-play business views of Oracle E-Business Suite data, helping speed the flow of information throughout the enterprise. Customized to each unique database configuration, the automated generation process is a snap – cutting weeks off typical custom generations. NoetixViews provides the fast track to delivering familiar business terminology right to employees, partners, and customers.

By hiding complexity within metadata, NoetixViews simplifies and greatly accelerates report generation and ad hoc query creation, empowering decision makers and front-line employees with timely and accurate access to critical information. The metadata has been hand-crafted by Noetix Corporation to meet common business reporting needs with each view designed for a specific functional coverage area. Designed with integration in mind, NoetixViews is built on an open architecture platform, extending the power of NoetixViews information to a myriad of third-party reporting and analytical tools.

Benefits of NoetixViewsThe benefits of NoetixViews for Oracle E-Business Suite (NoetixViews) include:

• Quick implementation: In as few as two days, NoetixViews can be up and running, delivering timely and accurate access to critical information. Thus, providing huge savings in the development costs.

• Automatic upgrade protection: The reports written for NoetixViews using any reporting tool are insulated from the Oracle E-Business Suite schema changes. If there is a new release (patches, service packs, or upgrades) of Oracle E-Business Suite and there is some change in the Oracle schema that might result in broken reports, Noetix Corporation will release a compatible version of NoetixViews so that your reports based on the Noetix views will automatically adjust to the new Oracle schema changes and continue to return accurate data. This is available to you at no extra cost.

Chapter 1: About NoetixViews 3

• Comprehensive documentation: NoetixViews comes complete with a comprehensive help file and documentation, providing valuable information to accelerate report development and generation.

• Automatic customized generation: Custom business views simplify data access, yielding immediate return on investment. The NoetixViews scripts detect additional configuration information about the Oracle E-Business Suite schema on which they are installed and generate Noetix views with customer-specific columns, such as descriptive flexfields.

NoetixViews BasicsThis section explains general features and components of NoetixViews for Oracle E-Business Suite (NoetixViews) as well as concepts like roles and security. Being familiar with these terms will assist you in generating and maintaining Noetix views. An expanded introduction to views, roles, and using NoetixViews can be found in your NoetixViews for Oracle E-Business Suite User Guide.

NOTE: In accordance with the changes implemented in Oracle E-Business Suite Release 12, the term "base currency" has been replaced with "primary currency" and the term "foreign currency" has been replaced with "transaction currency."

NoetixViews AdministratorThe NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator) is a Microsoft Windows-based application that allows you to complete a full generation of Noetix views from a client-side PC. A series of wizards guides you through the generation process, from creating a Noetix System Administration User account to generating the customized views for your site.

NoetixViews Administrator is also used for maintenance tasks, such as setting up query users, regenerating views, and generating the Noetix Help File.

For more information about NoetixViews Administrator, see Generation of Views, Noetix Query User Management, and Maintenance.


Noetix Help FileThe Noetix Help File helps you in searching information pertaining to a specific view or column. It helps you to easily locate a NoetixViews topic (for example, role, view, column or query construction) within the help file.

The Noetix Help File is generated for each distinct Noetix System Administration User account and a set of Noetix views. To facilitate report creation by the functional users who do not have technical knowledge about the complicated Oracle table structures, the help file represents the complex Oracle table names and column names with common user terminology.

The Noetix Help File is available in Microsoft WinHelp, HTML, and Query Tool Help formats.

For more information about the Noetix Help File, see Choose Help Formats to Generate in “Generation of Views.”

Noetix Query UsersNoetix query users are database users, Oracle E-Business Suite users, or Oracle E-Business Suite responsibilities that are granted access to a set of Noetix views. Noetix query users can be set up after completing the generation process.

The Noetix System Administration User creates a Noetix query user by selecting a database user (or, with DBA privileges, creating one) and granting this user a set of Noetix roles appropriate for the user’s security level and information access needs. After this setup, this database user is considered a Noetix query user.

Users can also be set up to be authenticated against the Oracle E-Business Suite security. In this case, Oracle E-Business Suite users and/or responsibilities are set up in the NoetixViews Administrator with access to appropriate roles.


User ProfilesTo optimize system resources and reduce the possibility of runaway queries, Oracle provides resource limits. Resource limits control the following four variables:

• A user’s CPU usage and disk I/O• The number of sessions per user• The maximum connect time• The amount of memory used by a multi-threaded server session

You can use the Create Profile dialog box of SQL*DBA to create or modify a user profile. For more information on user profiles, refer to Oracle’s Server Administrator’s Guide and SQL Language Reference Manual.

For more information about query users, see Noetix Query User Management.

Noetix RolesNoetix roles are assigned to Noetix query users to both provide and restrict access to data held in Oracle E-Business Suite. Each role grants access to a set of views. Roles are usually generated according to the level of granularity inherent in a specific Oracle Application.

The concept of a role is an Oracle Database feature. Noetix query users granted a role automatically have access to all the views assigned to that role. Roles are assigned to Noetix query users after generation. For more information about assigning roles, see step 12 in “Add a Noetix Query User Using an Existing User” in “Noetix Query User Management.”

General Ledger SecurityNOTE: In Oracle E-Business Suite Release 12, the concept of set of books has been replaced by ledger. In this guide both “set of books” and “ledger” have been used interchangeably to refer to the same concept.

When a Noetix query user requires access to secure Oracle General Ledger data, you can use NoetixViews Administrator to assign the proper General Ledger security.

General Ledger security rules control access to transactions or balances in General Ledger. These security rules should be predetermined by the Oracle E-Business Suite


Administrator before assigning them to Noetix query users in NoetixViews Administrator.

Noetix query users can be set up to have no access or full access to secure General Ledger data, or to allow the responsibility with which a user logs on to determine what data should be accessible. Users can also be given custom access and assigned security rules for each chart of accounts/ledger. A user can be assigned any valid security rule, regardless of what roles (if any) they have been assigned.

If you add a security rule in Oracle E-Business Suite to a new segment of the Accounting Flexfield or create a ledger, the views must be regenerated before they incorporate the changes. With any change or addition to security rules in Oracle E-Business Suite, you should review and update users’ access to General Ledger data in NoetixViews.

For more information about General Ledger security, see NoetixViews for Oracle General Ledger in “Module-Specific Information.”

Multi-CurrencyOracle E-Business Suite allows you to work with currency amounts in either primary or transaction currency units. Additional functionality has been built into both the views and the Noetix Help File to help you to select the Oracle E-Business Suite data using transaction and primary currency units.

Noetix views are generated with the ability to reflect the use of more than one currency in your applications configuration. In General Ledger, each ledger is defined with a single primary currency unit. Individual transactions can be entered in any currency unit (that is, a currency different from the primary currency for each ledger).

When querying data from NoetixViews, use the Currency_Code column to select the primary or transaction currency in which you would prefer to view the data.


NoetixAnswersNoetixAnswers immediately enhances NoetixViews for Oracle E-Business Suite (NoetixViews) by configuring metadata for prebuilt reports specific to your Oracle E-Business Suite configuration. After the metadata is created, you can generate the metadata into Noetix QueryServer (NQS) and Noetix WebQuery (NWQ) to provide instant answers to common business questions without complicated query development.

To generate metadata created by NoetixAnswers:• Run Noetix Generator for Noetix Platform—Oracle E-Business Suite Edition

(Noetix Generator). For more information about Noetix Generator, see the Noetix Generator for Noetix Platform Administrator Guide for Oracle E-Business Suite.

NoetixAnswers uses the access and translation capability of the installed Noetix products to deliver custom answers without the need to define data locations or write query code. Available for each NoetixViews module, NoetixAnswers facilitates the power within the Noetix metadata to automatically map and create application-specific queries customized to each unique application configuration. With NoetixAnswers, Noetix delivers more than business views – it provides instant access to business information without taxing IT resources.

NoetixAnswers requires the purchase of NQS and NWQ. More information about NoetixAnswers can be found in this administrator guide.

Chapter 2

Forms of Noetix Views

This chapter provides information about the forms of Noetix views for Oracle E-Business Suite.


OverviewNoetix Corporation offers standard, Cross Operations Extension (XOP), and global forms of views for a variety of Oracle E-Business Suite modules.

Standard ViewsThe standard form of Noetix views allows Noetix query users to access data for a specific organizational unit, such as a business group, ledger, operating unit, and inventory organization. The standard views for a specific organizational unit are grouped under the corresponding Noetix role for that organizational unit. When a role is granted to a user, the user can query data related to the specific organizational unit from the views corresponding to the role. With the exception of the standard views for the Oracle Advanced Benefits, Oracle General Ledger, Oracle Human Resources, Oracle Payroll, Oracle Time and Labor, and Oracle U.S. Federal Financial modules, security is not available for the standard views.

XOP ViewsNOTE: In Oracle E-Business Suite Release 12, the concept of set of books has been replaced by ledger. In this guide both “set of books” and “ledger” have been used interchangeably to refer to the same concept. Also, the term "base currency" has been replaced with "primary currency" and the term "foreign currency" has been replaced with "transaction currency."

NoetixViews Cross Operations Extension (XOP) is an extension to the NoetixViews for Oracle E-Business Suite (NoetixViews) product line. This feature allows users to view data across multiple organizational areas and build queries using this data. Depending on your Oracle E-Business Suite setup, this data can span multiple ledgers, operating units, and inventory organizations.

Chapter 2: Forms of Noetix Views 11

For the XOP form of some views, the access of the Noetix query users to data from multiple organizational areas can be customized through the use of the Security Manager dialog box. For information, see Add a Noetix Query User Using an Existing User in “Noetix Query User Management.”

How XOP Views Are GeneratedThe XOP feature creates roles with views that can span your Oracle E-Business Suite environment. The number of XOP roles depends on the specific configuration at your site. The number of views in each XOP role roughly corresponds to the number of views in each NoetixViews standard role.

Each category of views is handled differently depending on how the Oracle E-Business Suite module organizes the data:

• By chart of accounts: The Oracle General Ledger, Oracle U.S. Federal Financials, and Oracle Assets modules are partitioned by ledgers. Each ledger is linked to a chart of accounts that defines the Accounting Flexfield structure. Therefore, views in the General Ledger, U.S. Federal Financials, and Assets modules can span across multiple ledgers, as long as those ledgers have the same chart of accounts.

• By a combination of chart of accounts and item master organization: XOP views corresponding to the Oracle modules at the operating unit level and inventory organization level are partitioned by combinations of charts of accounts and item master organizations. Therefore, these views can span across operating units and inventory organizations that share the same combination of a chart of accounts and an item master organization.

NOTE: Customers who do not have an item master organization defined for their site require customization of NoetixViews, to avail of the XOP functionality. Such customers must use identical flexfield structures for all charts of accounts; the segments, segment names, and segment structures must be the same for the XOP views to return meaningful data.


The following table explains the working of XOP views:

NOTE: XOP views for Projects, Oracle Grants Accounting, and Oracle Grants Proposal display data from multiple operating units having the same chart of accounts. These views are partitioned at the operating unit level and do not consider the item master organization.

Additional columns are generated in the XOP views based on the organizational units across which the views span. The following table provides the list of modules and the corresponding organizational unit column added to the XOP views:

Category Views span across Restriction Modules

Ledger Ledger Chart of accounts must be the same

Oracle General Ledger, Oracle U.S. Federal Financials, and Oracle Assets

Operating unit

Operating units Combination of chart of accounts and item master organization must be the same

Oracle Receivables, Oracle Payables, Oracle Order Management, Oracle Purchasing, Oracle Projects, Oracle Grants Accounting, and Oracle Grants Proposal

Inventory organization

Inventory organizations

Combination of chart of accounts and item master organization must be the same

Oracle Inventory, Oracle Bills of Material, Oracle Cost Management, Oracle Work in Process, Oracle Quality, Oracle Enterprise Asset Management, and Oracle Material Requirements Planning

Modules Column

Oracle General Ledger, Oracle U.S. Federal Financials, and Oracle Assets

Set_Of_Books_Name (for Oracle E-Business Suite versions prior to Release 12) and Ledger_Name (for Oracle E-Business Suite Release 12 and later)


NOTE: The table lists the main columns on the basis of which the organizational units pertaining to records can be identified. Other, additional columns may also be generated in the XOP views.

For information about generating XOP views, see Option 1: Generate Using NoetixViews Administrator or Option 2: Generate Using Scripts in “Generation of Views.”

Oracle Receivables, Oracle Payables, Oracle Order Management, Oracle Purchasing, Oracle Projects, Oracle Grants Accounting, and Oracle Grants Proposal

Operating_Unit_Name

Oracle Inventory, Oracle Bills of Material, Oracle Cost Management, Oracle Work in Process, Oracle Quality, Oracle Enterprise Asset Management, and Oracle Material Requirements Planning

Organization_Name

Modules Column


Guidelines for Using XOP ViewsFor each chart of accounts, a set of XOP views will be generated to cross over all ledgers, operating units, and inventory organizations, depending on your Oracle E-Business Suite setup. This section sets out the guidelines that you should follow for ensuring that the views return accurate results for your users.

If the primary currency and calendar are not the same for all ledgers, XOP views will be generated, but there may be some discrepancy in the currency unit or calendar.

An example of a query that retrieves accurate information from multiple ledgers, each with a different primary currency, would be: “How many products were sold last year across all ledgers?” For the same ledgers, an example of a query that cannot retrieve accurate, currency-related information would be: “What were the gross sales of the products last year across all ledgers?” In the result of this query, the amounts would not be converted to a single currency.

IMPORTANT: For XOP views that retrieve information from ledgers with different primary currencies, the view essays in the Noetix Help File will contain a note cautioning users to be careful while grouping or summing the values in different primary currencies.

XOP Views and Multi-CurrencyThe multi-currency functionality of Oracle E-Business Suite is not supported by XOP views.

NOTE: Irrespective of whether the multi-currency functionality is activated at your environment, Noetix recommends that you use a single primary currency across all ledgers to ensure accurate information from the XOP views.

For example, if your environment has two ledgers without the multi-currency functionality, both having the same primary currency and identical calendar periods, XOP views can retrieve information accurately from those ledgers. Even if your environment has two ledgers with the multi-currency functionality activated, XOP views can retrieve accurate information from them, provided that they have the same primary currency and identical calendar periods.


XOP Views and MRCIf the Oracle Multiple Reporting Currencies (MRC) feature is activated, the data retrieved from multiple ledgers will be in different currencies. For a single ledger, XOP views may be used to retrieve accurate currency-related information. However, when XOP views are used to retrieve information from multiple ledgers that use different currencies, all information except for the currency-related information can be used.

For example, a company has two ledgers for its operations in the United States and Mexico. The primary ledger, representing the entire company (both operations) uses U.S. dollars as its currency. The reporting ledger, representing the manufacturing organizations in Mexico, uses pesos as its currency. The company can use XOP views to retrieve information about Mexican manufacturing organizations from the reporting ledger. The retrieved information, containing financial data in pesos, can be submitted to the Mexican government. The company can also use XOP views to retrieve information about the entire company from the primary ledger. The retrieved information, containing financial data in U.S. dollars, can be used to evaluate the company’s global performance.


XOP Views and Calendar PeriodsThe number of calendar periods you have created for each ledger will determine whether XOP views return accurate information. For accurate information, it is recommended that you use the same number of calendar periods with identical beginning and end dates across multiple ledgers.

For example, if one ledger has six calendar periods in a year, and a second ledger has four calendar periods in a year, then the XOP views may not be able to determine how the data from one ledger should be mapped to the other. Therefore, the information returned may not be accurate.


XOP Views for InventoryTwo types of roles can be generated for the Oracle Inventory module when you have more than one inventory organization – inventory organization-specific roles and global inventory organization roles. You can choose to generate one, both, or neither of these roles. For information about inventory roles, see Option 1: Generate Using NoetixViews Administrator or Option 2: Generate Using Scripts in “Generation of Views.”

In addition to these roles, XOP views for Inventory can also be generated. The XOP views also allow the user to create queries that span multiple inventory organizations, but a set of XOP views will be created for each combination of a chart of accounts and an item master organization in Oracle E-Business Suite.

Whereas the global inventory roles allow you to create queries that span inventory organizations without regard to multiple charts of accounts or item master combinations, the XOP views for Inventory take multiple charts of accounts and item master organizations into account.

For example, assume that your company has two item master organizations, each with three inventory organizations. Additionally, your company uses only one chart of accounts.

You can choose to generate six sets of inventory organization-specific views (one each for the WA, OR, CA, NY, MA, and PA inventory organizations) or one set of global views that will span all the inventory organizations.

If you have purchased XOP views, you can generate two sets of XOP views, one for each item master organization.


Global ViewsNOTE: In accordance with the changes implemented in Oracle E-Business Suite Release 12, the term "base currency" has been replaced with "primary currency" and the term "foreign currency" has been replaced with "transaction currency."

The Noetix global views for Oracle E-Business Suite allow users to view data across organizational units, while assuring that the rows returned are consistent with the business intelligence (BI) tool users’ Oracle E-Business Suite data access privileges. Depending on your Oracle E-Business Suite setup, the data can span organizational units, such as business groups, ledgers, operating units, and inventory organizations.

Global views, like other forms of Noetix views, are organized into roles. Regardless of the complexity of the multi-organizational setup in the supported Oracle E-Business Suite modules at your site, only one global role is created for each module and all global views are accessible through that role.

Some key flexfields are configured with multiple structures in Oracle E-Business Suite. For example, the Accounting key flexfield can have multiple structures, known as charts of accounts. Global views include additional views for key flexfields. They are joined to the key flexfield views to access the concatenated key flexfield segment columns. Optionally, individual segment columns can be included in the global views. For more information, see Key Flexfield Views.

The access of the Noetix query users to global views is determined by the data access privileges granted to them through the NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator). They can query the data that is consistent with the data they view in Oracle E-Business Suite. For information, see Create Noetix Query Users Using GUI and Data Access Privilege in "Noetix Query User Management."

The global form of Noetix views is available for all the supported Oracle E-Business Suite modules except Oracle Grants Accounting and Oracle Grants Proposal. Besides, the following views for Oracle General Ledger do not have a global form:

• GL_Parent_Budget_to_Actuals

• GL_Parent_Child_Balances

• GL_Parent_Child_Budgets


• GL_Rollup_Parent_Balances

• GL_Rollup_Parent_Budgets

Some additional columns are generated in the global views based on the organizational units across which the views span. The following table lists some of the Oracle E-Business Suite modules and the corresponding organizational unit columns added to the global form of the views:

NOTE: If you have purchased the standard and XOP views for Projects, you may have PC_Project_Costing and PB_Project_Billing roles generated at your site to access these views. If you have purchased global views for Projects, you can access the standard, XOP, and global views through the PA_Projects role. The PC_Project_Costing and PB_Project_Billing roles are not generated in that case.

Module Column

Oracle Advanced Benefits and Oracle Payroll

Legislation_Code

Oracle Bills of Materials, Oracle Cost Management, Oracle Enterprise Asset Management, Oracle Master Scheduling/MRP, Oracle Quality, and Oracle Inventory

Chart_Of_Accounts_Name, Master_Organization_Name, and Organization_Name

Oracle Inventory Organization and Organization_Code

Oracle Assets, Oracle U. S. Federal Financials, Oracle General Ledger, Oracle Payables, Oracle Receivables, Oracle Purchasing, Oracle Order Management, and Oracle Projects

Chart_Of_Accounts_Name, Ledger_Name (for Oracle E-Business Suite Release 12 and later), Operating_Unit_Name, and Set_Of_Books_Name (for Oracle E-Business Suite versions prior to Release 12)

Oracle Projects and Oracle Time and Labor

Business_Group_Name

Oracle Human Resources Legislative_Code


Global Views and Multi-CurrencyFor a global role, users can retrieve accurate data from the corresponding global views across ledgers if the ledgers use the same primary currency.

IMPORTANT: For global views that retrieve information from ledgers with different primary currencies, the users need to be careful while grouping or summing the values in different primary currencies.

Global Views and MRCIf the Oracle Multiple Reporting Currencies (MRC) feature is activated, users can use global views to retrieve data from primary ledgers that contain transaction-related information in primary currency units. Users can also retrieve data from the associated reporting ledgers that contain transaction-related information in transaction currency units.

For example, a company has two ledgers for its operations in the United States and Mexico. The primary ledger, representing the entire company (both operations) uses U.S. dollars as its currency. The reporting ledger, representing the manufacturing organizations in Mexico, uses pesos as its currency. The company can use global views to retrieve information about Mexican manufacturing organizations from the reporting ledger. The retrieved information, containing financial data in pesos, can be submitted to the Mexican government. The company can also use global views to retrieve information about the entire company from the primary ledger. The retrieved information, containing financial data in U.S. dollars, can be used to evaluate the company's global performance.

Benefits of Global ViewsThe key features of the global form of Noetix views are the following:

• Enterprise-wide reporting: Data from all organizations is accessible from each global view

• Row-level security: Oracle E-Business Suite user's data access privileges are used to restrict the data returned by the global views, regardless of the BI tool


• Intuitive user interface: An organized and intuitive presentation model in the BI tools

• Rapid Implementation: Fast generations and regenerations mean rapid deployment of upgrades, enhancements, and customizations

Key Flexfield ViewsFor supporting key flexfields, the global views, by default, include only certain columns that return, among other details, the concatenated segment values and segment labels. The segment-specific details are returned by separate, key flexfield views whose names begin with the XXK_ prefix. The advantages of this arrangement are that the global views are not cluttered with too many key flexfield-related columns.

For all key flexfields except the Personal Analysis key flexfield, a data cache value table is created. This table contains the values for individual segments, the values for qualifier segments if they are defined for the Accounting key flexfield, and the concatenated segment values. A data cache description table is also created for the Accounting key flexfield and Territory key flexfield, and the names of the corresponding key flexfield views for these tables have the _D suffix.

The XXK_KEY_FLEXFIELD role provides access to all the key flexfield views generated at your site. While providing access to global views, the global roles also provide access to the related key flexfield views.


The following diagram depicts how the key flexfield views retrieve data:

The following table explains how data is returned for key flexfields in standard, Cross Operations Extension (XOP), and global views:

Standard views XOP views Global views

Support only single key flexfield structures spanning single organizational units.

Support only single key flexfield structures spanning multiple organizational units.

Support multiple key flexfield structures spanning all organizational units within your site.


Key Flexfields Supported by NoetixViewsThe following table lists the key flexfields that are supported by NoetixViews for Oracle E-Business Suite (NoetixViews):

1In Oracle E-Business Suite, a key flexfield may by definition support a single structure or multiple structures.

Flex code Key flexfield name Structure1

BANKBank Details KeyFlexField

Multiple

CAT# Category Flexfield Single

COST Cost Allocation Flexfield Multiple

CT# Territory Flexfield Single

GL# Accounting Flexfield Multiple

GRD Grade Flexfield Multiple

GRP People Group Flexfield Multiple

JOB Job Flexfield Multiple

KEY# Asset Key Flexfield Single

LOC# Location Flexfield Single

MCAT Item Categories2 Multiple

MDSP Account Aliases Single

MICG Item Catalogs Single

MSTK System Items Single

MTLL Stock Locators Single

PEAPersonal Analysis

Flexfield3 Multiple

POS Position Flexfield Multiple


2In Oracle E-Business Suite, the functional areas of the Item Categories key flexfield are tied to single structures that might vary from implementation to implementation. During the generation of the global views that return information for the Item Categories key flexfield, the structures are determined according to the corresponding functional areas in Oracle E-Business Suite, and information is returned for these single structures. The exceptions in this case are the QA_Quality_Specifications and INV_Category_All views that are designed to return information for multiple structures.

A global view is generated for each category in the Item Categories key flexfield. The view name will be in the I NV_Category_<category name> format.

3A global view is generated for each structure in the Personal Analysis key flexfield. The view name will be in the HRG0_SI_Type_<structure name> format. These global views return information on special information types (SITs) and will include columns for individual and concatenated segment values. However, the global views will not include join-to (Z$) columns for the key flexfield view for the Personal Analysis key flexfield.


Columns in Key Flexfield ViewsA key flexfield view has one column for each segment of each structure of the corresponding key flexfield. The view returns one row for each code combination of the key flexfield. Because a code combination belongs to only one key flexfield structure, only the structure-specific columns in the row will return information, and the other columns will return the null value.

If the key flexfield view returns segment values, the following will be returned:

• The primary key column for a code combination (Multiple columns will be returned for a composite primary key.)

• Columns that provide segment values and whose names begin with the SV$ prefix

• A column that returns the concatenated segment values and whose name begins with the CV$ prefix

• The Segment_Name_List column that concatenates the labels of the segments that are relevant to a row

• The Structure_ID column that provides the identifier of the structure that is relevant to the row

• The Structure_Name column that provides the label of the structure that is relevant to the row

• A join-to column for the view

• The columns for qualifier segment values and whose names begin with the QV$ prefix if the view is for the Accounting key flexfield

If the key flexfield view returns segment descriptions, in addition to the previously listed columns, the following will be returned:

• A column that returns the concatenated segment descriptions and whose name begins with the CD$ prefix

• Columns that provide segment descriptions and whose names begin with the SD$ prefix


• The columns for qualifier segment descriptions and whose names begin with the QD$ prefix if the view is for the Accounting key flexfield

• The Language column that indicates the language in which the descriptions have been provided

• A join-to column for the corresponding key flexfield view that returns values

Key Flexfield Columns in Global ViewsWhen a key flexfield has multiple structures, the global views will include the following columns by default:

• A column that returns the primary key value that is relevant to a row and whose name is in the <column name>$<name of primary key column in key flexfield view> format

• A column that returns the label of the structure that is relevant to the row and whose name has the $Structure_Name suffix

• A column that returns the concatenated labels of the segments for the structure and whose name has $Segment_Name_List suffix

• A column that returns the concatenated values of the segments for the structure and whose name is in the <column name>$CV$<short key flexfield label> format

• Columns that return the values for the Balancing, Cost Center, and Natural Account qualifier segments and whose names are in the <column name>$QV$<qualifier segment label> format if the key flexfield is the Accounting key flexfield

• A join-to column for the key flexfield view that returns values (The column name will be in the Z$<column name>$<key flexfield view name> format.)


Of the global views that return information for the Accounting key flexfield or Territory key flexfield, some views contain a column that returns the concatenated descriptions of the segments for the structure and whose name is in the <column name>$CD$<short key flexfield label>format. These global views could also have columns that return the descriptions for the Balancing, Cost Center, and Natural Account qualifier segments and whose names are in the <column name>$QD$<qualifier segment label> format if the key flexfield is the Accounting key flexfield. A join-to column may be provided if required for the key flexfield view that returns descriptions.

The segment-specific columns for key flexfields with multiple structures can be included in the global views through the use of a script before Stage 4 of the generation. For information, see Update Scripts Before Generation in "Generation of Views."

When the key flexfield has a single structure with multiple segments or a single segment, the global view may return segment-specific columns, concatenated columns, or both. The columns will be generated on the basis of what supports optimal use of the view. Join-to columns are not provided for the corresponding key flexfield views.

Chapter 3

Installing NoetixViews for

Oracle E-Business Suite

This chapter provides preinstallation considerations and instructions for installing or upgrading NoetixViews for Oracle E-Business Suite (NoetixViews).


OverviewThis chapter provides information on the preinstallation considerations for the software. It also guides users through the complete installation procedure of NoetixViews for Oracle E-Business Suite (NoetixViews). Users who use Microsoft Windows as the operating system at their site should refer to the procedure describing installation of NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator) for generating and maintaining Noetix views. Users having UNIX as the operating system at their sites should refer to the procedure for loading the script files on a computer running UNIX for generating and maintaining Noetix views.

The chapter also provides detailed procedures of upgrading the software on both the operating systems.

Preinstallation ConsiderationsYou must familiarize yourself with the preinstallation considerations before installing NoetixViews for Oracle E-Business Suite (NoetixViews). This section contains information about the tasks that must be completed before installing the product.

Review System RequirementsThe system requirements for installing NoetixViews can be found in the release documentation included with the product software and in Answer ID 707 (INFO: Documentation for NoetixViews for Oracle E-Business Suite) on the Noetix online knowledge base.

Before beginning an installation, ensure that your system meets the minimum requirements for hard disk drive space, memory, operating systems, and application versions.

http://noetix.custhelp.com/cgi-bin/noetix.cfg/php/enduser/std_adp.php?p_faqid=707

Chapter 3: Installing NoetixViews for Oracle E-Business Suite 31

Grant Administrative Privileges for NoetixViews AdministratorYou must have administrative privileges for each computer on which you plan to install NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator).

To do this, add your user account to the Administrators group on each computer. If you need assistance with this task, contact your system administrator.

Install the SoftwareThe following sections describe the process of installing NoetixViews for Oracle E-Business Suite (NoetixViews) in Microsoft Windows and UNIX environments.

Install the Software on WindowsThe installation of NoetixViews on a Microsoft Windows-based computer consists of installing NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator) and the data (.dat) files. The NoetixViews Administrator uses the data files for generation of views. This section contains instructions for installing all the NoetixViews components on a Windows-based computer.


To install NoetixViews:

1. Run the Setup.exe file. The NoetixViews installation startup screen appears.

2. On the startup screen, click NoetixViews. The Welcome to the NoetixViews Setup wizard page appears.

3. On the Welcome to the NoetixViews Setup page, review the information displayed, and click Next.


4. On the Software License Agreement page, click I Agree to accept the license agreement.


5. On the Installation Location page, click Next. By default, NoetixViews is installed in <hard disk drive>:\Program Files\Noetix Corporation\NoetixViews. To select a different folder, click Browse, select a folder, verify the destination path, and then click Next.


6. On the Choose Start Menu Folder page, enter a Start menu folder name under which you want to create the shortcuts for NoetixViews. By default, it is NoetixViews. If you select a Start menu folder name from the list, the default name is added to the end of the selection. If you do not want to create the shortcuts for NoetixViews, select the Do not create shortcuts check box, and then click Next.


7. On the Installation Summary page, verify the installation settings, and click Install.


8. On the Installation Complete page, click Next when the button becomes available, which will be when the installation is complete. You can click Show Details to view the actions performed by the installation wizard. On clicking Show Details, the detailed information about the installation is displayed. To copy the installation log at a point, you can right-click the information and click Copy Details To Clipboard. You can then paste and save the installation log in any text-editing program.


9. On the next page, click Finish. The wizard exits.

.

Load the Software on UNIXFor generation of Noetix views using scripts, the necessary script files have to be transferred to the UNIX-based computer and consecutively, the files and directory have to be prepared. You can transfer the files either using the Noetix Script Copy Wizard or using a File Transfer Protocol (FTP) client. The instructions for transferring the files using the Noetix Script Copy Wizard and an FTP client and preparing the files and directory are given in the following sections.

Transfer Files Using Noetix Script Copy WizardIf you have installed NoetixViews Administrator on a Windows-based computer, you can use the Noetix Script Copy Wizard to transfer the necessary script files to the UNIX-based computer on which you will perform the scripts-based generation. This wizard will transfer the files using FTP.


To transfer scripts using the Noetix Script Copy Wizard:1. Create a Noetix installation directory on the UNIX-based computer where you

want to generate the Noetix views. If you are generating Noetix views on multiple databases, you must set up a separate directory for each database. Note these directory locations for reference.

2. Click Start > All Programs > NoetixViews > Script Copy Wizard. The Noetix Script Copy Wizard welcome page is displayed. Click Next to start the wizard.

NOTE: If you have not installed NoetixViews Administrator on a client computer, you can access and run the Noetix Script Copy Wizard available with the product software.


3. Type a user name, password, and URL for the network location of the computer to which you would like to transfer the scripts using FTP. Click Next.

4. Type the location of the directory that you created in step 1. Click Next.


5. Confirm the information that you have typed, and click Finish to transfer the files.

6. After the files have been transferred, the Noetix Script Copy Wizard displays the scripter.txt file. Skip to Prepare Files and Directory for Generation of Views Using Scripts for the next step.

Transfer Files Using FTP ClientAs an alternative to using the Noetix Script Copy Wizard, the scripts required for generation can be transferred to the appropriate directory using whatever means available to you. If you have not installed NoetixViews Administrator, you can get the scripts you need from NvAdm\Master\Unix in the folder where you have unzipped the product software.

NOTE: The script files are in text format, meaning that lines are ended with both a carriage return and line feed, rather than just a line feed (as found in UNIX). Whatever process you use to transfer the files, they must be converted to the format that suits the environment you are running the scripts from. Most FTP servers and clients do this conversion when you transfer such files in ASCII mode.


To transfer scripts using an FTP client:NOTE: The instructions below are based on the Windows FTP client, but should be applicable to any FTP client.

1. On the UNIX-based computer from which you want to generate Noetix views, create a Noetix installation directory. If you are generating Noetix views on multiple databases, you must set up a separate directory for each database. Note these directory locations for reference.

2. At the command prompt, change the present working directory to NvAdm\Master\Unix.

3. Type FTP <server_name>, and press ENTER (where server_name is the IP address or name of the UNIX-based server).

4. Type the user name and password when prompted.

5. Change the present working directory to the installation directory on the UNIX-based server.

6. Type ascii, and press ENTER. This puts you in the ASCII transfer mode.

7. Type put setup.sh, and press ENTER. This transfers the script files from NvAdm\Master\Unix to the installation directory on the UNIX-based computer.

8. Type binary, and press ENTER. This puts you in binary transfer mode.

9. Type prompt, and press ENTER. This turns off the interactive mode so you are not prompted to transfer every file.

10. Type mput *.Z, and press ENTER. This transfers the compressed .Z files from NvAdm\Master\Unix to the installation directory on the UNIX-based computer.

11. When the transfer is finished, type bye, and press ENTER. This closes the FTP client. For information about the next steps of the generation, see the following section.


Prepare Files and Directory for Generation of Views Using ScriptsAfter transferring the script files to the UNIX-based computer, you must prepare the files and directory for generating Noetix views using these scripts.

To prepare files and directory for generation of views using scripts:1. Log on to the UNIX-based computer, and go to the NoetixViews installation

directory.

2. Type . ./setup.sh and press ENTER. This command will decompress and untar the scripts.Z, datfile*.Z, and custom.Z files. (The custom.Z file is used for customer-specific configuration and may not be included for all installations.) It also sets the execute permission on all *.sh, *.bat, @echo, and @goto files.

3. Verify the following:

• The users performing the generation of the views have read, write, and exe-cute permissions to the directory.

• The *.sh, *.bat, @echo, and @goto files have execute permission.

4. If you have received custom scripts from Noetix Corporation that are not contained in the custom.Z file, manually transfer these files through FTP to the NoetixViews installation directory at this point.


Upgrade the SoftwareNoetixViews for Oracle E-Business Suite (NoetixViews) should be upgraded if:

• You want to take advantage of new product features and improvements, including new Noetix views and answers.

• You have purchased an additional NoetixViews module.• An issue you have encountered in your environment is resolved in a more recent

version of NoetixViews.• You are upgrading to a version of Oracle E-Business Suite that your current

NoetixViews version does not support.• You are upgrading to a version of the Oracle Database that your current

NoetixViews version does not support.• You would like to use NoetixViews in conjunction with other hardware or

software that your current NoetixViews version does not support.

Refer to the NoetixViews for Oracle E-Business Suite Release Notes for the system requirements of the version that you are upgrading NoetixViews to. Ensure your environment meets the system requirements of the new version of NoetixViews, as these may have changed since your last generation. The release notes will also include any known issues you should be aware of and an overview of changes made since the previous product version. This may include metadata changes that will affect users’ reports.

Customers with a current Noetix support agreement are eligible to receive NoetixViews upgrades. To request an upgrade, submit your request online at the Noetix Technical Support Web site.

?Should I regenerate, or should I upgrade?

• Have you received a new version of NoetixViews? An upgrade installs a new version of NoetixViews.

• Has your Oracle environment changed or do you need to apply a patch? A regeneration recreates your NoetixViews metadata after changes have been made to your database or applications and is often needed to apply patches from Noetix Corporation as well. For more information about regeneration of Noetix views, see Regeneration of Views.



Choose an Upgrade MethodNoetixViews can be upgraded on both Microsoft Windows and UNIX-based computers. On a Windows-based computer, an upgrade can be performed using the NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator). On a UNIX-based server, you need to perform the upgrade using scripts. There is no need to uninstall the existing version of NoetixViews before upgrading it to another version.

Noetix recommends that you upgrade using the same method that you used during installation.

Option 1: Upgrade the Software on WindowsThis section provides you information about upgrading NoetixViews on a computer running Windows.

Upgrade NoetixViews AdministratorTo upgrade NoetixViews, you must upgrade NoetixViews Administrator.

To upgrade NoetixViews Administrator:1. Follow steps 1 through 4 in “Installing the Software on Windows” to proceed with

the upgrade.

2. On the Installation Location page, click Next. The path to the folder in which NoetixViews Administrator is presently installed is displayed. To select a different folder, click Browse, select a folder, verify the destination path, and then click Next.

NOTE: You can create a separate installation folder for upgrading NoetixViews Administrator, but we recommend that you use the same folder you used during the previous installation.


If you select the same folder in which NoetixViews Administrator is presently installed, a message appears asking you to confirm whether you want to overwrite the existing folder.

3. Follow steps 6 through 9 in “Installing the Software on Windows” to complete the upgrade.

NOTE: During installation, a folder is created by default as <hard disk drive>:\Program Files\Noetix Corporation\NoetixViews\Master\Custom to store the custom script files for your site. While upgrading, NoetixViews creates a subfolder in the Custom folder and moves the script files, if any, into the new folder. It also displays a message to that effect.

Additional Steps to Be PerformedAfter NoetixViews Administrator has been upgraded, you need to regenerate the views to complete the process. Perform the following steps for the regeneration.

To perform the additional steps:1. Log on to NoetixViews Administrator as your existing Noetix System

Administration User account. For information, see Start NoetixViews Administrator in “Generation of Views.”

2. Run the pre-update process by clicking Pre-Update Script on the Tools menu. This script prepares your generation for an update of NoetixViews.

NOTE: The pre-update script needs to be run only at the beginning of the upgrade process. If, for some reason, you need to run the generation stages multiple times to successfully complete the upgrade, you do not need to run the script again.

You may receive an error message when running the pre-update process. If this happens, follow the error message instructions to run the iappspkg.sql script before resuming the pre-update process.


3. Complete Stages 2, 3, and 4 of the generation process. Ensure that you save the previous settings for role prefixes and Noetix query users. For information about the stages, see Option 1: Generate Using NoetixViews Administrator in “Generation of Views.”

NOTE: Keep the following points in mind:

• If you have NoetixViews for Oracle Payroll installed, you need to upgrade Noetix Payroll Data Mart before running through these generation stages. For more information, see Upgrade Noetix Payroll Data Mart in “Module-Specific Information.”

• During Stage 4 of the generation process, if you have purchased NoetixAnswers, you will be prompted to run Noetix Answer Builder. You must answer Yes to this prompt. You will also be prompted for whether you want to edit role prefixes. Please note that if you change a role prefix, any reports written against Noetix views within that role will break.

4. Optionally, run the listchng script. This creates a file showing differences between your previous and new generations. start listchng.sql These changes will be contained in the listchng.lst file.

5. If you are using Noetix Platform, you need to regenerate Noetix answers by running Noetix Answer Builder once again. After successfully running Noetix Answer Builder, you must run Noetix Generator for Noetix Platform—Oracle E-Business Suite Edition (Noetix Generator) to update your answers, as well as to generate your query user data into NQS. For more information, see Regenerate Noetix Answers in “Regeneration of Views.”

6. Regenerate the Noetix Help File so that it reflects your upgraded generation. For information about generating and distributing the Noetix Help File, see Option 1: Regenerate Help Using NoetixViews Administrator in “Regeneration of Views.”

7. If needs be, you also need to update the query tools. Refer to your query tool documentation to see if the tools or their meta-layers need to be updated or regenerated to access the latest NoetixViews metadata and security.


If you are using Noetix Generator for Oracle Discoverer (Noetix Generator) in conjunction with Oracle Discoverer, you will need to extract views as described in the Noetix Generator for Oracle Discoverer Administrator Guide to update your End User Layer (EUL). Noetix recommends that you upgrade the Noetix Generator when upgrading NoetixViews, if a new version is available.

Option 2: Upgrade Using ScriptsThis section provides information about upgrading NoetixViews on a UNIX-based server. Upgrading NoetixViews on a UNIX-based server comprises loading script files in the installation directory where the script files for the previous installation were loaded and performing some additional steps.

NOTE: You can create a separate installation directory for upgrading NoetixViews, but we recommend that you use the same directory you created during the previous installation.

Load Script FilesThe following procedure provides the details for loading the new script files for an upgraded version of NoetixViews.

To load the script files:1. Transfer the generation files from the folder where you have unzipped the

upgraded product software to the UNIX-based server. Use the Noetix Script Copy Wizard or an FTP client to transfer the necessary files to the NoetixViews installation directory that you had created while loading the files during the previous installation. For information about transferring files, see Load the Software on UNIX.

2. Using SQL*Plus, connect to the database as the existing Noetix System Administration User: connect <username>/<password>@<dbconnectstring>


Additional Steps to Be PerformedAfter the new script files have been loaded, you need to regenerate the views to complete the process. Perform the following steps for the regeneration.

To perform the additional steps:1. Run the pre-update process by running preupd.sql. This script prepares your

generation for an update of NoetixViews. start preupd.sql

NOTE: The pre-update script needs to be run only at the beginning of the upgrade process. If for some reason you need to run the generation stages multiple times to successfully complete the upgrade, you do not need to run the script again.

You may receive an error message when running the pre-update process. If this happens, follow the error message instructions to run the iappspkg.sql script before resuming the pre-update process.

2. Complete Stages 2, 3, and 4 of the generation process. For information about the stages, see Option 2: Generate Using Scripts in “Generation of Views.”

NOTE: During Stage 4 of the generation process, if you have purchased NoetixAnswers, you will be prompted to run Noetix Answer Builder. You must answer Yes to this prompt. You will also be prompted for whether you want to edit role prefixes. Please note that if you change a role prefix, any reports written against Noetix views within that role will break.

3. Optionally, run the listchng script. This will create a file showing differences between your previous and new generations. start listchng.sql These changes will be contained in the listchng.lst file.

4. If you are using Noetix Platform, you need to regenerate Noetix answers by running Noetix Answer Builder once again. After successfully running Noetix Answer Builder, you must run Noetix Generator for Noetix Platform—Oracle E-Business Suite Edition (Noetix Generator) to update your answers, as well as to generate your query user data into NQS. For more information, see Regenerate Noetix Answers in “Regeneration of Views.”


5. Regenerate the Noetix Help File so that it reflects your upgraded generation. For information about generating and publishing the Noetix Help File, see Option 2: Regenerate Help Using Scripts in “Regeneration of Views.”

6. If needs be, you also need to update the query tools. Refer to your query tool documentation to see if the tools or their meta-layers need to be updated or regenerated to access the latest NoetixViews metadata and security.

If you are using Noetix Generator for Oracle Discoverer (Noetix Generator) in conjunction with Oracle Discoverer, you will need to extract views as described in the Noetix Generator for Oracle Discoverer Administrator Guide to update your EUL. Noetix recommends that you upgrade the Noetix Generator when upgrading NoetixViews, if a new version is available.

Chapter 4

Generation of Views

This chapter describes the steps to generate Noetix views and explains the generation concepts.


Pre-Generation ConsiderationsThe scalability and open architecture of NoetixViews for Oracle E-Business Suite (NoetixViews) provide flexibility in how you generate and use Noetix views within your Oracle E-Business Suite environment. As a part of the installation of NoetixViews, the data (.dat) files for the NoetixViews modules purchased by your organization are installed. They are used by the NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator) to generate the views. Because components of the product are customized for your business environment, an understanding of the basic generation concepts will help you to maximize the effectiveness of NoetixViews within your organization.

We recommend that you familiarize yourself with the pre-generation considerations available in this section before beginning the generation process. Each task involves gathering and preparing information or making decisions.

This chapter will help you accomplish the following pre-generation tasks:

• Back up applications.• Obtain account information.• Determine SQL*Loader version.• Create tablespace.• Install Noetix Payroll Data Mart (when using NoetixViews for Oracle Payroll).• Update scripts before generation.• Decide on a user name and password for the Noetix System Administration User.• Name role prefixes.• Determine which Noetix help formats should be generated.• Decide whether you want to suppress parent-child hierarchy views. For

information about how to suppress parent-child hierarchy views, see Suppress Parent-Child Hierarchy Views in NoetixViews in the "NoetixViews Customization" section in "Maintenance."

• Decide whether you want to suppress charts of accounts. For information about how to suppress charts of accounts, see Suppress Charts of Accounts in NoetixViews in the "NoetixViews Customization" section in "Maintenance."

Chapter 4: Generation of Views 53

Back Up Oracle E-Business SuiteAs a standard precaution, it is recommended that you back up your Oracle E-Business Suite before generating Noetix views. It is also recommended that you generate Noetix views into a non-production environment before rolling out to production.

Obtain Account InformationPrior to generation of Noetix views, you must obtain the following account information:

• The user name and password of an Oracle database user with DBA privileges (i.e., system): This account information is necessary to create the Noetix System Administration User during the generation process.

• The user name and password of an Oracle E-Business Suite APPS or AOL (APPLSYS) user: This information is necessary to grant limited AOL access privileges to the Noetix System Administration User during Stage 2 of the Noetix views generation process. You will have to provide the same password during Stage 4, so that the generation process can access the database tables belonging to each of the Oracle E-Business Suite modules detected.

Determine Oracle Tools VersionsOracle tools comprise SQL*Plus, SQL*Net, and SQL*Loader. SQL*Plus is required to run the scripts while generating Noetix views, and SQL*Net is required by SQL*Plus to connect to the database. SQL*Loader is required during Stage 4 of Noetix views generation. The versions of the Oracle tools that are compatible with NoetixViews are listed in the system requirements.

The versions of these tools have to be compatible with the version of Oracle Home that you are running. A mismatch between the Oracle tools and Oracle Home versions has been known to generate errors in Noetix views generation. Before generating the views, confirm that the versions of the tools installed in the current Oracle Home is correct for your generation.

NOTE: Noetix recommends that the Oracle tools and database be of the same version so that compatibility-related issues are avoided.


To check your SQL*Plus, SQL*Loader versions:1. Start NoetixViews Administrator. To do this, click Start > All Programs >

NoetixViews > NoetixViews Administrator. The welcome dialog box is displayed and prompts you to create an account or connect to an existing account.

2. Type the system administration user name, password, and TNS name to connect to an existing account.

NOTE: The SQL*Plus and SQL*Loader versions can be viewed only after a system administration user account has been set up.

3. In NoetixViews Administrator, on the Help menu, click About. You can see the versions of Oracle Database, SQL*Loader, and SQL*Plus. You can also see the path to Oracle Home.

4. You can use the Override Oracle Tool Detection tool in the NoetixViews Administrator to change the SQL*Plus and SQL*Loader versions detected. For more information about the Override Oracle Tool Detection tool, see Override Oracle Tool Detection in “Maintenance.”

Create TablespaceThe database tablespace size you will need depends on your Oracle E-Business Suite environment and the number of NoetixViews modules to be generated. This tablespace amount is usually between 50 MB and 150 MB, but some generations may require up to 1 GB or more. The amount of tablespace required depends on the particular environment and configuration, including how many ledgers, operating units, inventory organizations, and modules you have. Estimate your tablespace generously for planning purposes and monitor it during the generation. The tablespace can be increased during generation with no adverse effects.

When creating your tablespace, we recommend that you use the locally managed tablespace option, available in Oracle Database versions 8i and later.


Install Data Mart (When Using NoetixViews for Oracle Payroll)The NoetixViews for Oracle Payroll module includes the Noetix Payroll Data Mart, which computes and saves balances for every assignment per payroll run. When the Payroll module is purchased, a directory as Datamart/Payroll is included with the product software, containing all the scripts you will need in order to install the data mart. The data mart must be installed before Noetix views are generated.

For more information about NoetixViews for Oracle Payroll, see NoetixViews for Oracle Payroll in “Module-Specific Information.”

Update Scripts Before GenerationBefore you generate Noetix views, you may need to customize hook scripts based on your requirement.

To Generate Individual Key Flexfield Segment Columns in Global ViewsBy default, individual segment columns are excluded from global views that use key flexfields with multiple structures. The views contain Z$ columns that allow users to join to the key flexfield views and incorporate the individual segment columns to the reports. However, if you want to generate the individual segment columns into the global views, you can do so by updating wnoetx_gseg_flex_kff_cols.sql before Stage 4 of the views generation process.


To incorporate individual segment columns into the global views:1. Open wnoetx_gseg_flex_kff_cols.sql using a text editor. On a

Windows-based computer, the default path to the file is <hard disk drive>:\Program Files\Noetix Corporation\NoetixViews\Installs\<NOETIX_SYS_TNS>.

2. Include the following statement: UPDATE n_f_kff_flexfields

SET kff_cols_in_global_view_flag = 'Y'

WHERE ID_FLEX_APPLICATION_ID = <Application ID>

AND ID_FLEX_CODE = “<Flex code>”;

3. Save the changes, and then close the file.

You can refer to wnoetx_gseg_flex_kff_cols.sql for the application IDs and flex codes of the key flexfields with multiple structures.

NoetixViews for Oracle PayrollIf you have purchased NoetixViews for Oracle Payroll, columns are automatically added to the PAY_US_Payroll_Register view (introduced in NoetixViews 5.8.7) for each of the earnings and deduction balance types used in a specified time period. These columns return balances pertaining to regular earnings (with the "RE" label prefix), supplemental earnings (with the "SE" label prefix), imputed earnings (with the "IE" label prefix), alien or expatriate earnings (with the "AE" label prefix), non-payroll payments (with the "NP" label prefix), pre-tax deductions (with the "PD" label prefix), tax deductions (with the "TD" label prefix), voluntary deductions (with the "VD" label prefix), involuntary deductions (with the "ID" label prefix), employer benefit liabilities (with the "BL" label prefix), and employer tax liabilities (with the "TL" label prefix).

The time period for which these columns are generated can be adjusted through the use of the PAY_NUMBER_OF_MONTHS parameter in the wnoetxu4.sql file. The period calculation always includes the months of the current calendar year, plus an adjustable range of additional months (the default is 36).

For example, if you run Stage 4 in November 2009 and do not change the default number of additional months, NoetixViews will consider the previous 47 months-11


for the current year, plus the additional 36 months-for a time period from January 2006 through November 2009. The PAY_US_Payroll_Register view will have one column for each earnings and deduction balance type used during these 47 months.

These balance columns in PAY_US_Payroll_Register retrieve their data from the Noetix Payroll Data Mart. To assure that each column returns a value for the payroll periods where the corresponding earnings or deduction balance type is used, you must specify a time period that has as its beginning the month that matches the oldest payroll period in the data mart.

If PAY_US_Payroll_Register has already been generated and a new earnings or deduction balance type is used, the view must be regenerated for the corresponding new column to become available.

If the last time the view was regenerated was in a previous calendar year and you want the same beginning month for the time period, be sure to increase the value of the PAY_NUMBER_OF_MONTHS parameter in increments of 12 for each year since the last regeneration.

In the standard form of this view, the additional columns will be restricted to those earnings and deduction balance types used over the given time period within the single business group of the view. The global form of the view, however, will include all earnings and deduction balance types from all business groups over the time period.

To modify the PAY_NUMBER_OF_MONTHS parameter:1. Open wnoetxu4.sql using a text editor. On a Windows-based computer, the

default path to the file is <hard disk drive>:\Program Files\Noetix Corporation\NoetixViews\Installs\<NOETIX_SYS_TNS>.

2. In the PAY/HR SECURITY block, add the following statement: define PAY_NUMBER_OF_MONTHS=<number of months>

3. Save the changes, and then close the file.


NoetixViews for Oracle QualityNoetixViews for Oracle Quality includes two sets of views that are dynamically generated on the basis of the collection plans and collection plan types set up at your site: QA_Rslt_<plan name> and QA_Rslt_PType_<plan type>.

To ensure that these views are correctly generated, you need to modify the parameters in the wnoetx_qa_plan_gen_options.sql file before running Stage 4 of the generation process.

On a Windows-based computer, the script file is stored in <hard disk drive>:\Program Files\Noetix Corporation\NoetixViews\Master\Scripts\scripts.cab. Copy the script file to <hard disk drive>:\Program Files\Noetix Corporation\NoetixViews\Master\Custom. Read the instructions in this file, modify the parameters, and edit the file so that the code is not commented.

NOTE: The QA_Rslt_<plan name> view will not be generated under Cross Operations Extension (XOP) roles.


Decide on Noetix System Administration User NameA user name and password must be decided for the Noetix System Administration User. This database user (NOETIX_SYS by default) will have administrative privileges and own the Noetix views. To maintain appropriate levels of security, the password should not be similar to the user name.

If you are generating on more than one database instance, you can use the same Oracle user name for the Noetix System Administration User in each instance. If you have several installations of Oracle E-Business Suite within one instance, you must use different names for each Noetix System Administration User.

Name Role PrefixesAll Noetix view names include both a prefix and a business name. The prefix identifies the role a view is attached with. All views within a role have the same prefix. The prefix created for each role must be unique, even if the business name is not. This guarantees the uniqueness of every view name.

A role prefix provides a meaningful label for a view, helping to identify the ledger, operating unit, or inventory organization related to the role and the view. The prefix name can also identify the role and view as one belonging to NoetixViews in the database.

During a generation, NoetixViews generates default role prefix names that are the application label and a number (e.g., AP1). While you can use these default names, these are not user-friendly and should be changed. You will be prompted to edit these prefixes.

IMPORTANT: Role prefixes should not be changed after your initial generation. It is highly recommended that you determine a naming convention for role prefixes and change them during the initial generation.


Role Prefix Naming ConventionsTo customize role prefixes during generation, you will need to determine a five-character naming convention for each Oracle E-Business Suite module, ledger, operating unit, and manufacturing /inventory organization within your environment. If you have purchased XOP views, determine how you will distinguish roles for XOP views using role prefixes.

Prefixes are usually created using an abbreviation for the Oracle E-Business Suite module for which the role was created and a meaningful label for each operational area depending on the module. For example, if a role is granted access to a ledger for U.S. operations in Oracle General Ledger, the prefix for this role becomes USGL. Subsequently, all views accessible from this role will be labeled with a prefix of USGL.

NOTE: The role prefix should be created with the abbreviation for the ledger preceding the abbreviation for the application (e.g., USGL instead of GLUS). This way, a wildcard search performed on all objects beginning with the NoetixViews prefix segment US (US%) will pull up objects related to your NoetixViews configuration, whereas a search performed on all objects beginning with the NoetixViews prefix segment GL (GL%) will pull up all objects related to General Ledger and prefixed with GL.

The prefix name can also identify the role and view as one belonging to NoetixViews in the database. If you are aware of other similarly named objects existing in the database, you may want to include the letter N in the prefix to distinguish Noetix views and roles from Oracle’s views and roles residing in the database.

Guidelines for creating role prefixes:• The first character must be an uppercase letter (A to Z).• English letters (A to Z), numbers (0 to 9), and the underscore (_) can be used in

prefixes. However, the last character cannot be an underscore.• Up to five characters may be used in a prefix for identification of modules, ledgers,

operating units, and inventory organizations.• Special or multi-byte characters cannot be used in prefixes.• The prefix for each database role listed on the role prefix dialog box must be

unique. Duplicate prefixes are not permitted.• Prefixes cannot be left blank.

If the guidelines are not adhered to when prefixes are created, an error will occur.


If you have only one ledger, inventory organization, or business group, the default prefix becomes the application label (e.g., GL_Chart_Of_Accounts). In this case, you may want to associate the view with NoetixViews by adding the letter N (e.g., N_GL).

If you have any queries regarding role prefixes after the generation is complete, you can look up the Noetix Help File to view the roles for your environment.

Choose Help Formats to GenerateThe Noetix Help File helps you in searching information pertaining to a specific view or column. It helps you to easily locate a NoetixViews topic (for example, role, view, column or query construction) within the help file.

The Noetix Help File is available in three formats that can be generated during or after generation. You can choose to generate any combination of the following formats:

• Microsoft WinHelp Format: The Noetix Help File for Microsoft Windows contains all information available concerning your generation and includes search capabilities. Users will find this help format similar to that found in many desktop applications. This help format is appropriate for environments running Microsoft Windows or Windows NT.

• HTML Help Format: NoetixViews generates a set of HTML files that can be moved to a Web server and accessed through a Web browser. This help format is appropriate for environments that use an intranet for access to Oracle E-Business Suite data and internal networking.

• Query Tool Help Format: NoetixViews generates comments for each Noetix view and column. Many query tools allow you to access these comments when you are building a query. These views are also helpful while using a query tool that does not directly support comments.

IMPORTANT: The Query Tool Help format is ideal for advanced users who use SQL*Plus, TOAD, and similar tools. As the database comments require a large amount of Oracle tablespace, you must generate Query Tool Help only after a successful generation of Noetix views.


Choose a Generation MethodDepending on your preferences and the platform in which you are operating, you may generate Noetix views using either the NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator) or SQL scripts.

Consider requirements such as the following when making your choice:

• How familiar are you with Noetix view generations? If you are generating Noetix views for the first time, the wizard-based generation provides more information about the prompts asked during the process and the effects of your choices.

• What environment or computer do you currently use for administrative tasks? If you use Microsoft Windows or UNIX for other administrative tasks, you may want to use a similar process for generating Noetix views.

The following table lists additional considerations for each generation method:

Features

Comparing Generation Methods

NoetixViews Administrator

Scripts

Runs on Windows?

Runs on UNIX/Linux?

Supports changing role prefixes during generation?

Can automatically compile Windows help file format?

Includes online help for each dialog box/prompt?


For information about generation of views using NoetixViews Administrator, see Option 1: Generate Using NoetixViews Administrator.

For information about generation of views using scripts, see Option 2: Generate Using Scripts.

Option 1: Generate Using NoetixViews Administrator

Noetix views can be generated from a client computer using the NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator). This generation method involves running NoetixViews Administrator on a Microsoft Windows-based client computer and performing the generation using a series of wizards.

Before generating Noetix views you must complete the pre-generation tasks listed in Pre-Generation Considerations.

NOTE: On a Windows-based computer, script-based generation of Noetix views is available for only Stages 2 through 4. To do this, after Stage 1 is completed, click Tools >

Support > SQL*Plus Prompt or click on the toolbar to connect to the database through SQL*Plus as the Noetix System Administration User and continue with the next stages. For information about script-based generation, see Option 2: Generate Using Scripts.

The Noetix views generation comprises the following tasks:1. Generation preparations: Complete the pre-generation tasks.

2. Generation phases: Perform the following steps for generating views:

a. Start NoetixViews Administrator.

b. Stage 1: Create Noetix System Administration User account.

c. Stage 2: Grant Noetix System Administration User limited privileges to the Application Object Library (AOL) tables.

d. Stage 3: Set up the Noetix System Administration User.


e. Stage 4: Generate Noetix views.

f. Run Noetix Answer Builder (when using Noetix Platform).

g. Generate Noetix Help File.

h. Verify generation.

3. Generation administration: Perform the following steps after the views, answers, and Noetix Help File have been generated:

a. Publish Noetix Help File (optional).

b. Grant Noetix query users access to Noetix views.

c. Configure reporting tool or install Noetix Generator for Oracle Discoverer (Noetix Generator).

Start NoetixViews AdministratorThis section describes the steps required to start NoetixViews Administrator.

To start NoetixViews Administrator:1. Click Start > All Programs > NoetixViews > NoetixViews Administrator. The

welcome dialog box is displayed. This dialog box displays two options:

a. Create a Noetix System Administration User Account

b. Connect to an Existing Noetix System Administration User Account


To generate views for the first time, click Create a Noetix System Administration User Account, and click OK.

NOTE: When you use NoetixViews Administrator after generation for maintenance tasks, or to perform a regeneration or upgrade, you must click Connect to an Existing Noetix System Administration User Account.

This connects you to NoetixViews Administrator. The application’s main window will display behind the wizard pages and allow you to view any messages that the wizard displays. It provides the tools necessary to administer Noetix views generations and perform maintenance tasks. These tools include shortcuts to each generation stage, connections to related applications, and utilities that perform related generation tasks.


Stop and Resume a GenerationDuring generation, you may encounter an error or discover that you need to gather additional information before continuing. In that case, you can stop the process and resume it later.

To resume a generation:• If you are logged on to NoetixViews Administrator: On the Tools menu, click

Installation Stages and then select the required generation stage, or click the toolbar button numbered with the generation stage you need to complete.

• If you are not logged on to NoetixViews Administrator: Log on to NoetixViews Administrator as the Noetix System Administration User who began the generation. If any generation stage was not completed previously, the software detects which generation stage is incomplete and prompts you to restart that stage. Again, you might complete a stage and exit NoetixViews Administrator before all the stages were complete. In that case, when you log on again, you are prompted to begin the next stage. Click Yes to connect to the wizard for generation.

When a generation is running, the script output is displayed on the NoetixViews Administrator window. To copy the output at a point, right-click the information, and click View In Notepad to view the output as a text file or Save As to save the output as a text file that can be viewed later.


Stage 1: Create Noetix System Administration User AccountTo begin Stage 1 of the generation process:1. If you choose to create a Noetix System Administration User account, the

welcome page of Stage 1 wizard is displayed. The Stage 1 wizard performs all of the tasks necessary to create a Noetix System Administration User account. This account owns all the tables and procedures used during the generation process, and also the resulting views. To connect to this wizard from the main window of NoetixViews Administrator, click the button labeled 1 on the toolbar. Click Next.


2. The next page prompts you to provide information about a database user with DBA privileges. This information was collected in the pre-generation stage. On the appropriate text areas, type the user name and password of a database user with DBA privileges. Then, type the database name or use the list to identify the database where the database user resides. Click Next.


3. The next page prompts you to type a user name and password for the Noetix System Administration User account. Choose a meaningful name that identifies the user account specifically for NoetixViews. The default user name is NOETIX_SYS. Click Next.

NOTE: The user name must start with a letter and can contain only the letters A to Z, digits 0 to 9, and underscore (_). The user name cannot contain double quotation marks (") or single quotation marks (') and cannot exceed 30 bytes. Diacritical marks and characters for Western European languages can also be typed.


4. The next page allows you to permanently grant the SELECT ANY TABLE and/or SELECT ANY DICTIONARY privileges to the Noetix System Administration User account. These privileges are usually granted and allow the database user access to a number of database tables or to delete unused synonyms for a user. To grant these privileges (recommended), click Yes. To deny these privileges, click No. Click Next to continue.

If you do not permanently grant these privileges, you will need to log on to the database with the required privileges each time you delete a role or query user. NOTE: The SELECT ANY DICTIONARY privilege is applicable only to Oracle Server 9i and later.


5. The next page identifies the tablespace storage locations for the objects owned by the Noetix System Administration User. For the default tablespace, select the tablespace name chosen during the pre-generation steps from the list. Repeat the same procedure for the temporary tablespace. Click Next to continue. NOTE: The size next to the tablespace name indicates the amount of space available in each tablespace but is not guaranteeing that enough space is available to complete the generation. This is manually confirmed during the pre-generation steps. Temporary tablespace is handled differently in Oracle 8i and later. Your temporary tablespace will display as having 0 MB free, regardless of how much tablespace you actually have available.


6. The next page allows you to choose a default path for the base installation directory. To change the location of the default path for the base installation directory, click the open folder icon located to the right of Base Directory. Using the Browse for Folder dialog box, change the directory location. Click Next to continue.

7. If you want to go to Stage 2 of the generation process after Stage 1 is completed, select Yes. Click Finish. A confirmation message is displayed when Stage 1 is successfully completed.


Stage 2: Grant Limited Privileges to AOL DataTo begin Stage 2 of the generation process:1. If you chose to continue after Stage 1, Stage 2 wizard starts automatically. This

wizard performs the steps to grant the Noetix System Administration User access to the Application Object Library (AOL) tables. To connect to this wizard from the main window of NoetixViews Administrator, click the button labeled 2 on the toolbar. Click Next to continue.


2. The next page prompts you for logon information for the Oracle E-Business Suite APPS user to grant access to the necessary AOL objects. This password should have been gathered during the pre-generation tasks. Type the user name and password of the APPS user. The database where this user is defined will be on the TNS Name box by default. Click Next to continue.

NOTE: An Oracle E-Business Suite AOL (APPLSYS) user account can be entered instead if you have run Stage 2 of the generation process using APPLSYS in the past.


3. If you want to go to the next step of the generation process after Stage 2 is completed, select Yes. Click Finish. A confirmation message is displayed when Stage 2 is successfully completed.


Stage 3: Set Up Noetix System Administration User AccountTo begin Stage 3 of the generation process:1. If you chose to continue after Stage 2, Stage 3 wizard starts automatically. Stage 3

of the generation process creates synonyms for the Noetix System Administration User to set up the account with the necessary tables and views. To connect to this wizard from the main window of NoetixViews Administrator, click the button labeled 3 on the toolbar. Click Next to continue.


2. The next page prompts for a confirmation of the user name of the Oracle E-Business Suite APPS or APPLSYS user that was provided in Stage 2 of the generation process. A default name will be displayed and should be accurate. Click Next to continue. If the default name is incorrect, exit the wizard, and confirm that you are running Stage 3 of the generation process for the correct Noetix System Administration User account.


3. On the next page, select Yes. Click Finish. A confirmation message is displayed when Stage 3 is successfully completed.


Stage 4: Generate ViewsTo begin Stage 4 of the generation process:1. If you chose to continue after Stage 3, Stage 4 wizard starts automatically. Stage 4

of the generation process generates views, answers, and the Noetix Help File. To connect to this wizard from the main window of NoetixViews Administrator, click the button labeled 4 on the toolbar. Click Next to continue.


2. If you are generating Noetix views for Oracle E-Business Suite 11.0 or later, the next page prompts you to select a translation language. If the default language is incorrect, select the translation language you will be using in your implementation of NoetixViews from the list. Click Next to continue.

NOTE: If some query users require a different translation language than the one chosen here, you can set this on a per-user basis after generation. For more information, see steps 5 and 11 in “Create Noetix Query Users Using GUI” in “Noetix Query User Management.”


3. The next page allows you to select the forms of views you want to generate.

NOTE: The selections you make on this page before generation are set as defaults the next time you run Stage 4.

The following options are available on this page. Each option is available only if the respective form of views is detected in your NoetixViews configuration.

• Global Extension: Select this check box if you want to generate global views. If this check box is selected, global roles are created, and a set of views is generated for each global role. For more information about global views, see Global Views in “Forms of Noetix Views.”

• Cross Operations Extension (XOP): Select this check box if you want to generate XOP views. If this check box is selected, XOP roles are created, and a set of views is generated for each XOP role. Additionally, if the Oracle E-Business Suite modules at your site for which you are generating XOP views contain organizational units that are included in standard roles, and not in XOP roles, those standard roles will also be created. For more information about XOP views, see XOP Views in “Forms of Noetix Views.”


• Standard: Select this check box if you want to generate standard views for all the available modules in your NoetixViews configuration. The check box is selected by default. If you select this check box, standard roles are created, and a set of views is generated for each standard role.

• Include Inventory views: Select this check box if you want to generate organization-specific views for Oracle Inventory. This check box appears only if Noetix views for Inventory is detected in your NoetixViews configuration. You can select this check box only if the Standard check box is selected. If you have more than one inventory organization at your site, you can use this option to generate a set of views specific to each inventory organization. If this check box is selected, organization-specific roles are generated for Inventory, and a set of views is generated for each inventory organization.

NOTE: The views for those modules that support only global form (such as NoetixViews for Oracle Service) will always be generated regardless of the selections on this page. Any such modules will be listed in a message at the bottom of the page that states that views for these modules will be generated. This message may also mention the Application Object Library (AOL) and Noetix Administration Objects modules, if they are present.


4. (Optional) If NoetixViews for Oracle Projects is detected in your NoetixViews configuration, the option to add multi-currency columns to the views for Projects will be available. The Add Project Multi-currency Columns to views check box allows you to add multi-currency columns to the views for Projects. This check box is selected by default. Clear the check box if you do not want to add multi-currency columns to the views.

NOTE: If you click Cancel, Stage 4 of the generation process stops. You must restart Stage 4 to complete the generation process.


5. Provides the Pause for role prefix editing check box. This option allows you to edit role prefixes while generating views. This check box is selected by default. Clear the check box if you do not want to edit role prefixes. For information about role prefixes, see Name Role Prefixes.

NOTE: The selections you make on this page before generation are set as defaults the next time you run Stage 4.

For more information about editing role prefixes, see Edit Role Prefixes.


6. (Optional) The next page is displayed only if you have purchased Noetix Platform, Noetix Search, or any of the Noetix Generator products. Select the Answer Builder check box to run Noetix Answer Builder.

On the same page, choose whether to review any warnings that may be generated during the generation process. Selecting the Continue if warnings detected check box allows you to continue through generation regardless of warnings. However, if there are any errors in Stage 4 of the generation, the Noetix Answer Builder Wizard will not run. If you clear the Continue if warnings detected check box, it will allow you to review any warnings as they are generated before deciding to continue.

For more information, see Run Noetix Answer Builder (When Using Noetix Platform). Click Next to continue.


7. The next page prompts you to select the format in which the Noetix Help File is to be generated. Select the check box next to the corresponding help format. Click Next to continue.

IMPORTANT: The Query Tool Help format is ideal for advanced users who use SQL*Plus, TOAD, and similar tools. As the database comments require a large amount of Oracle tablespace, you must generate Query Tool Help only after a successful generation of Noetix views.

If you want to manually generate the help files after generation, clear the help format check boxes, and click Next. For information about manually generating the help files, see Generate Noetix Help File.

NOTE: If any errors are detected in Stage 4 of the Noetix views generation, the Noetix Help File will not be generated. As a workaround, after completing Stage 4, you must first run the ifix4sts.sql script to override Stage 4 errors and then manually generate the Noetix Help File. The ifix4sts.sql script is located in your NOETIX_SYS user directory (by default, <hard disk drive>:\Program Files\Noetix Corporation\NoetixViews\Installs\<NOETIX_SYS_TNS>).


8. Click Finish to start generating Noetix views.

After this page, Stage 4 of the generation process starts. At certain points while processing (which may take awhile), the pages in the following sections appear. Stage 4 is not completed, until a message stating that the stage is complete is displayed.

As Stage 4 of the generation process runs, output messages appear in the NoetixViews Administrator window, behind the dialog boxes prompting you for additional information. You may create a copy of the messages appearing on the text area at any time. Select the required text, and, on the shortcut menu, click Copy to copy the selected text to a text file. Alternatively, click on the text area, and, on the shortcut menu, click Save as to convert the text to a text file.


Get PasswordsDuring Stage 4 of the generation process, NoetixViews Administrator will need access to the database tables belonging to each of the Oracle E-Business Suite modules detected. You will be prompted for the Oracle E-Business Suite APPS user password to ensure that the generation can access all the necessary tables. If you are generating views for Oracle Payroll, you will also be prompted for the password of the Noetix Payroll Data Mart database user (XXEIS user).

The Get Passwords wizard is displayed requesting the necessary passwords. You should have gathered these passwords during the pre-generation steps outlined earlier in this administrator guide.

NOTE: If you are regenerating views using the same *.dat files as in previous generations, the wizard may not need to prompt you for this information.


To grant NoetixViews Administrator access to the Applications tables:1. When the Get Passwords wizard starts, a set of windows is displayed, prompting

you for the necessary passwords. For each window, type the password for the indicated user, and then click Finish. After the password for each user is entered and validated, the wizard will close and the generation will continue.

NOTE: If you click Cancel, Stage 4 of the generation process stops. You must restart Stage 4 to complete the generation process.


Activate Multi-Currency Columns for Projects Views (Optional)During Stage 4 of the generation process, you may be prompted to add multi-currency columns to the views for Oracle Projects. For information about the conditions in which the prompt appears, see Multi-Currency Activation in NoetixViews for Oracle Projects in “Module-Specific Information.”

Edit Role PrefixesDuring Stage 4 of the generation process, the Edit Role Prefix dialog box is displayed. It lists the default role prefixes that you can modify to customize each Noetix role. For information, see Role Prefix Naming Conventions.

NOTE: This page appears only if you choose to edit role prefixes during views generation. For more information, see step 5.

IMPORTANT: You may accept the default role prefixes, but it is recommended that you choose prefixes that are more intuitive for users. Also, ensure that the names of the Noetix roles do not match the names of other roles in the Oracle database; otherwise, errors will occur during the generation.


The following columns are available on the Edit Role Prefix dialog box:

• Prefix: The default prefix for each role.

• Context: The level in the organization hierarchy at which the views accessible to the role are partitioned.

• Application Name: The name of the module that the role pertains to.

• Ledger: The name of the ledger. If XOP views have been generated, the value in the Ledger column is prefixed with “Cross Ledger.” For XOP views, the value of this column is made up of the chart of accounts name and the Accounting Flexfield values. For example, if the chart of accounts name is OPM Accounting and the Accounting Flexfield contains OPM US, the value in the Ledger column would be “Cross Ledger (COA: OPM Accounting Flex: OPM US).”

• Operating Unit: The name of the operating unit. If XOP views have been generated, the value in the Operating Unit column is prefixed with “Cross Operating Unit.” For XOP views, the value of this column is made up of the chart of accounts name and the Accounting Flexfield values. For example, if the chart of accounts name is India and the Accounting Flexfield contains Vision India Hyderabad|Vision India Mumbai, the value in the Operating Unit column would be “Cross Operating Unit (COA: India Accounting Flex: Vision India Hyderabad|Vision India Mumbai).”

• INV/MFG Organization: The name of the inventory or manufacturing organization. If XOP views have been generated, the value in the INV/MFG Organization column is prefixed with “INV/MFG Organization.” For XOP views, the value of this column is made up of the chart of accounts name and the Accounting Flexfield values. For example, if the chart of accounts name is India and the Accounting Flexfield contains IN1-Hyderabad|Vision Operations, the value in the Operating Unit column would be “Cross Operating Unit (COA: India Accounting Flex: IN1-Hyderabad|Vision Operations).”

• Business Group: The name of the business group.

• Process Organization: The name of the organization in Oracle Process Manufacturing.


To change a role prefix:1. Select the required Noetix role from the Edit Role Prefix dialog box.

2. Press F2 or double-click the role prefix to modify it. Repeat this step for each prefix listed. After all the prefixes have been changed, click OK to continue. A message appears before continuing with the generation. Click Yes to continue.

IMPORTANT: If you click Cancel on the Edit Role Prefix dialog box, Stage 4 of the generation process stops. You must restart Stage 4 to complete the generation process.

3. Confirm that you have finished editing your role prefixes by clicking Yes. You may return to the previous page by clicking No.

NOTE: If any of the generated roles are in conflict with other roles or users in the database, they are listed in the tmpcrole.lst file created in the NOETIX_SYS user directory.

A confirmation message is displayed when Stage 4 is successfully completed. Continue to the next section to check for errors.


Verify GenerationThe following instructions can be used after any generation stage or after all stages have been completed to verify the status of a Noetix views generation. Verification involves checking generation progress, then running a process to check for any errors that may have occurred during the generation.

To verify the Noetix views generation:1. Click Start > All Programs > NoetixViews > NoetixViews Administrator. The

welcome dialog box is displayed.

2. On the NoetixViews Administrator main window, click on the toolbar. The Noetix Installation Status dialog box is displayed. Click the NoetixViews Installation Status tab to view the status of each generation stage.


3. On the Tools menu, click Support > Find Script Errors. An output of all files containing errors will be displayed on the text area of the NoetixViews Administrator window. This command will also create an error log called finderr.lst in your NOETIX_SYS user directory. Each time you run this command, this log will be overwritten. Contact Noetix Technical Support if any errors are found.

NOTE: The Noetix Installation Status dialog box may indicate Stage 2 as completed, but may not specify the completion time and date, as specified for the other completed generation stages. This occurs after performing a scripts-based generation. Be assured that Stage 2 of the generation process is successful if the status is displayed as completed, regardless of whether the time and date are specified.

Generate Noetix Help FileThe Noetix Help File can be generated during Stage 4 of the generation process or manually at any time after generating Noetix views using the following instructions.

NOTE: If any errors are detected in Stage 4 of the Noetix views generation, you cannot generate the Noetix Help File. However, if you intend to override Stage 4 generation errors and generate the Noetix Help File, you must first run the ifix4sts.sql script and then manually generate the Noetix Help File. The ifix4sts.sql script is located in your NOETIX_SYS user directory (by default, <hard disk drive>:\Program Files\Noetix Corporation\NoetixViews\Installs\<NOETIX_SYS_TNS>).

The Noetix Help File is available in three formats. For information about determining which help formats will be most beneficial for your enterprise, see Pre-Generation Considerations.

To generate Noetix Help File:1. Click Start > All Programs > NoetixViews > NoetixViews Administrator. The


2. On the Tools menu, click Generate Online Help and click the help format you want to generate. To generate all available formats at once, click Help Generation Wizard.

3. NoetixViews Administrator will perform the processes necessary to generate the Noetix Help File in the specified format.


The Query Tool Help, if generated, will automatically be available to those with the applicable tools.

Additional steps are needed to allow users to access the Microsoft WinHelp and HTML formats, if generated. The following instructions explain how to locate these help files and publish them to users.

Microsoft WinHelp FormatAfter the Noetix Help File is generated in the Microsoft WinHelp format, the noetix.hlp file is located in <BASE_INSTALL_DIR>\<ACCOUNT_TNS>\MsHelp, where <BASE_INSTALL_DIR> is the location where you installed NoetixViews Administrator and <ACCOUNT_TNS> is the folder created in the name of the Noetix System Administration User (usually NOETIX_SYS) + _ + the TNS Name of the database instance on which the user resides. For example: C:\Program Files\Noetix Corporation\NoetixViews\Installs\NOETIX_SYS_dev.seattle\MsHelp

The noetix.hlp file should be moved to a shared server drive, and a shortcut to the file must be created on the desktop of each Noetix query user’s computer.


HTML Help FormatAfter the Noetix Help File is generated in the HTML Help format, the HTML files are located in <BASE_INSTALL_DIR>\<ACCOUNT_TNS>\htmlhelp\help, where BASE_INSTALL_DIR is the location where you installed NoetixViews Administrator and ACCOUNT_TNS is the name of the Noetix System Administration User (usually NOETIX_SYS) + _ + the TNS Name of the database instance on which the user resides. For example, C:\Program Files\Noetix Corporation\NoetixViews\Installs\NOETIX_SYS_dev.seattle\htmlhelp

Point your browser to noetix.htm within this directory to view the HTML Help. These HTML files will need to be published on a Web server and users must be notified of this location.

Query Tool Help FormatAfter the Noetix Help File is generated in the Query Tool Help format, the following views are generated in the schema:

• Help_Noetix_Views: For a description of each view

• Help_Noetix_Columns: For a description of all the columns in a view

You can retrieve help information for the Noetix views with your query tool. This help format can be obtained in two ways. The first uses a built-in feature of the query tool while the other method involves querying a help view. This process works well especially with query tools that allow you to see two queries at a time.


Option 2: Generate Using Scripts

The scripts-based generation involves generating Noetix views by running scripts from SQL*Plus and provides a straightforward means of providing information and making generation decisions. A scripts-based generation may be preferable for large generations or certain Microsoft Windows environments. For information about determining the best generation method for your specific needs, see Choose a Generation Method.

Prior to performing a scripts-based generation, you may have to install NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator). For information about installing NoetixViews Administrator, see Install the Software on Windows in “Installing NoetixViews for Oracle E-Business Suite.”

NOTE: On a Windows-based computer, script-based generation of Noetix views is available for only Stages 2 through 4. To do this, after Stage 1 is completed, click Tools >

Support > SQL*Plus Prompt or click on the toolbar to connect to the database through SQL*Plus as the Noetix System Administration User and continue with the next stages.

The Noetix views generation comprises the following tasks:1. Generation preparations: Complete the following tasks before generation:

a. Complete the pre-generation tasks.

b. Install NoetixViews Administrator on a Windows-based computer (optional).

2. Generation phases: Perform the following steps for generating views:

a. Stage 1: Create Noetix System Administration User account.

b. Stage 2: Grant Noetix System Administration User limited privileges to the Application Object Library (AOL) tables.

c. Stage 3: Set up the Noetix System Administration User.

d. Stage 4: Generate Noetix views.


e. Run Noetix Answer Builder (when using Noetix Platform).

f. Generate Noetix Help File.

g. Verify generation.

3. Generation administration: Perform the following steps after the views, answers, and Noetix Help File have been generated:

a. Publish Noetix Help File (optional).

b. Grant Noetix query users the access to Noetix views.

c. Configure reporting tool or install Noetix Generator for Oracle Discoverer (Noetix Generator).

Stage 1: Create Noetix System Administration User AccountTo begin Stage 1 of the generation process:1. Change the present working directory to the server directory containing the

generation scripts of NoetixViews.

2. Using SQL*Plus, connect to the database as a database user with DBA privileges. Provide the user details in the following format: <username>/<password>@<dbconnectstring> NOTE: If you are using an instance that is not stored in the ORACLE_SID environment variable, type @dbconnectstring.

3. Run the generation script for Stage 1, install1.sql, as follows: start install1.sql


4. Answer the following prompts:

• Please enter the Oracle User Name for the NoetixViews SysAdmin User.

NOTE: The user name can contain only the letters a to z and A to Z, digits 0 to 9, underscore (_), number sign (#), and dollar sign ($); must start with a letter; and cannot exceed 30 bytes. Diacritical marks and characters for Western European languages can also be typed.

• Please enter the Oracle User Password for the NoetixViews SysAdmin User.

NOTE: You will be prompted to re-enter the password for verification.

• Please enter the Database Connect String for the Database.

• Please enter the Default Tablespace to create NoetixViews Objects in.

• Please enter the Temporary Tablespace to assign the NoetixViews SysAdmin Acct.

• For full functionality of the Query User Maintenance facility, you must permanently grant the SELECT ANY TABLE and SELECT ANY DICTIONARY (Oracle 9i and later) privileges to the Noetix System Administration User account. These privileges allow the Noetix Administrator to efficiently maintain synonyms created for query users. Removing Noetix role access from certain query user types will not be allowed if these privileges are not granted. You can grant these privileges each time you run the Query User Maintenance wizard (for role deletions) and then automatically revoke the privileges when the process is completed. This option requires a DBA Account user name/password each time you need to delete a role or query user. Some of the steps in Stage 4 of the generation processes run faster if these privileges are granted.

• Grant these privileges to the Noetix Administrator User?


5. Verify the information that you have entered. If the information is incorrect, exit the SQL*Plus session (usually by pressing CTRL+C), and run Stage 1 of the generation process again. If the information is correct, press ENTER to continue.

6. If you want to run Stage 2 later, exit SQL * Plus. To do this, at the SQL prompt, type exit, and then press ENTER. If you want to run Stage 2 immediately after this stage, see the next section.

Stage 2: Grant Limited Privileges to AOL DataTo begin Stage 2 of the generation process:1. Using SQL*Plus, connect to the database as the Oracle E-Business Suite APPS

user. To do this, at the SQL prompt, type the following command: connect <username>/<password>@<dbconnectstring>


3. Answer the following prompt:

• Please enter the Oracle User Name for the NoetixViews SysAdmin User.

4. Verify the information that you have entered. If the information is incorrect, exit the SQL*Plus session (usually by pressing CTRL+C), and start Stage 2 of the generation process again. If the information is correct, press ENTER to continue.



Stage 3: Set Up Noetix System Administration User AccountTo begin Stage 3 of the generation process:1. Using SQL*Plus, connect to the database as the Noetix System Administration

User. To do this, at the SQL prompt, type the following command: connect <username>/<password>@<dbconnectstring>



• Please enter the Oracle user name for the APPS or AOL User.

NOTE: Enter the logon information for the Oracle E-Business Suite APPS user. An Oracle E-Business Suite AOL (APPLSYS) user account can be entered instead if you have run Stage 2 of the generation process using APPLSYS in the past.

4. Verify the information that you have entered. If the information is incorrect, exit the SQL*Plus session (usually by pressing CTRL+C), and run Stage 3 of the generation process again. If the information is correct, press ENTER to continue.



Stage 4: Generate ViewsTo begin Stage 4 of the generation process:1. Ensure that you are connected to the database as the Noetix System

Administration User.


3. Answer the following prompts. To accept the default value, press ENTER; otherwise, type a value for each item when prompted, and then press ENTER.

• Please enter the Oracle User Name for the Noetix System Administration User.

NOTE: Use the same user name you used when starting SQL*Plus.

• Please enter the Oracle User Password for the Noetix System Administration User.

• Please enter the Database Connect String for the Database.

• Please enter the Default Tablespace to create Noetix objects in.

• Please enter the Oracle Apps Translation Language.

• Create Global Extension Views? (Y/N)

NOTE: You can see this prompt only if global form of Noetix views is detected in your configuration. If you type Y, global roles are created, and a set of views is generated for each global role. For more information about global views, see Global Views in “Forms of Noetix Views.”


• Create Cross Operations Extension (XOP) Views?

NOTE: You can see this prompt only if XOP form of Noetix views is detected in your configuration. If you type Y, XOP roles are created, and a set of views is generated for each XOP role. Additionally, if the Oracle E-Business Suite modules at your site for which you are generating XOP views contain organizational units that are included in standard roles, and not in XOP roles, those standard roles will also be created. For more information about XOP views, see XOP Views in “Forms of Noetix Views.”

• Create Standard Views?

NOTE: If you type Y, standard roles are created, and a set of views is generated for each standard role.

• Include Standard Inventory Module Views?

NOTE: You can see this prompt only if NoetixViews for Oracle Inventory is detected in your NoetixViews configuration. If you have more than one inventory organization at your site, you can use this option to generate a set of views specific to each inventory organization. If this check box is selected, organization-specific roles are generated for Inventory, and a set of views is generated for each inventory organization.

• Add Projects Multi-currency columns to the views?

NOTE: You can see this prompt only if NoetixViews for Oracle Projects is detected in your NoetixViews configuration.

• Pause to edit the Noetix prefix file (tupdprfx.sql)?

NOTE: Do you want the generation process to pause so that you can edit the role prefixes your Noetix views will be created with? Answer Y to this prompt; otherwise your Noetix views will be created with default role prefixes. If you answer yes, the generation will pause after you have entered all prompts and the generation has created the default file for you to edit. Instructions to edit these prefixes are listed at that step in the generation.


• Run Answer Builder? (Answer Y for Yes or N for No)

NOTE: This prompt is displayed if you have purchased NoetixAnswers. You must answer yes to create metadata for prebuilt reports specific to your Oracle configuration. After the metadata is created successfully, run Noetix Generator for Noetix Platform—Oracle E-Business Suite Edition (Noetix Generator) to generate metadata into NQS and NWQ.

• Continue to next stage on warnings? (Answer Y for Yes or N for No)

NOTE: Answering yes allows you to continue through generation regardless of warnings. Answering No allows you to review any warnings as they are generated before deciding to continue.

• Generate Query Tool Help (Database comments)? (Answer Y for Yes or N for No)

IMPORTANT: This step can also be performed after generation or through NoetixViews Administrator. The Query Tool Help format is ideal for advanced users who use SQL*Plus, TOAD, and similar tools. As the database comments require a large amount of Oracle tablespace, you must generate Query Tool Help only after a successful generation of Noetix views.

• Generate Microsoft Help? (Answer Y for Yes or N for No)

NOTE: This step can also be performed after generation or through NoetixViews Administrator.

• Generate Web (HTML) Help? (Answer Y for Yes or N for No)

NOTE: This step can also be performed after generation or through NoetixViews Administrator. If any errors are detected in Stage 4 of the Noetix views generation, the Noetix Help File will not be generated. As a workaround, after completing Stage 4, you must first run the ifix4sts.sql script to override Stage 4 errors and then manually generate the Noetix Help File. The ifix4sts.sql script is located in the same directory where the install4.sql script is present.


4. Verify the information that you have entered. If the information is incorrect, exit the SQL*Plus session (usually by pressing CTRL+C), and start this stage again. If the information is correct, press ENTER to continue. After all the values have been entered correctly, the Noetix views generation will continue through the next steps.

After this step, Stage 4 of the generation process will begin. At certain points while processing (which may take awhile), the prompts in the following sections will be displayed. Stage 4 is not completed, until a message stating that the stage is complete is displayed.

Get PasswordsDuring Stage 4, the process of views generation needs to access the database tables belonging to each of the Oracle E-Business Suite modules detected. You will be prompted for the Oracle E-Business Suite APPS user password to ensure that all the necessary tables can be accessed. If you are generating views for Oracle Payroll, you will also be prompted for the password of the Noetix Payroll Data Mart database user (XXEIS user).

The generation will prompt you with the user names it needs passwords for. You should have gathered these passwords during the pre-generation steps outlined earlier in this administrator guide. Type the correct password for each user.

Activate Multi-Currency Columns for Projects Views (Optional)During Stage 4 of the generation process, you may be prompted to add multi-currency columns to the views for Oracle Projects. For information about the conditions in which the prompt appears, see Multi-Currency Activation in NoetixViews for Oracle Projects in “Module-Specific Information.”


Edit Role InformationThe generation process will continue until it requires role prefixes to be defined. If you have chosen to edit the tupdprfx.sql file, the generation will pause and you will be prompted to open the tupdprfx.sql file and type your customized role prefixes to identify each of your Noetix roles. For information about customizing role prefixes, see Name Role Prefixes.

NOTE: Generation will pause only if you choose to edit role prefixes during views generation. For more information, see step Stage 4: Generate Views.

While you may accept the default role prefixes, it is recommended that you choose prefixes that are more intuitive for users. It is recommended that separate names be given to the role prefix and the Oracle table.

Apart from editing the role prefixes, you can also use the tupdprfx.sql file to enable or disable a role and specify whether the organizational unit of the role will be included in a global and/or XOP instance.

To edit the role information:1. If you had chosen to edit the tupdprfx.sql file, the generation will pause with

the message, “The generation will now pause to allow you to customize your tupdprfx.sql file with your generation specific role prefix values.”

2. Open an additional SQL*Plus session, and then navigate to your NOETIX_SYS user directory. Edit the tupdprfx.sql file with the UNIX editor of your choice.


Given below is a sample section of the tupdprfx.sql file contains a section like the following for every role that the generation will create:

-- AP (Instance: 3)-- Original Role_Prefix: AP8-- COA: Operation Accounting Flex-- <Ledger/SOB>: Vision Operations (USA)-- OU: Vision Operations (USA)--BEGIN

noetix_prefix_pkg.update_prefix_record( -------------------------------------------------------i_role_prefix => 'AP12', /* +++ EDIT THIS LINE ONLY+++ */ i_use_org_in_xop_flag => ‘ ’ /* +++ EDIT THIS LINE (Y or N) ONLY+++ */ i_use_org_in_global_flag => ‘ ’ /* +++ EDIT THIS LINE (Y or N) ONLY+++ */ --------------------------------------------------------i_application_label => 'AP', i_owner_name => 'AP', i_coa_id => 101,i_sob_id => 1, i_org_id => 204, i_master_org_id => 204, i_organization_id => 204, i_instance_type => 'S' );

---- Enable/Disable Roles associated with this role_prefix

-- noetix_prefix_pkg.update_role_status(

--------------------------------------------------------- i_user_enabled_flag => 'Y', /* +++ EDIT THIS LINE ONLY

(Y or N) +++ */ ------------------------------------------------------------------------------------------------------- i_application_label => 'AP',

i_role_label => 'PAYABLES', i_coa_id => 101,

i_sob_id => 1, i_org_id => 204, i_master_org_id => 204, i_organization_id => 204, i_instance_type => 'S'); --END;


NOTE: For every role prefix, the introductory comment block displays the organizational units (chart of accounts, ledger or ledger, operating unit, business group, and so on) associated with the role prefix. This will help you to associate a user prefix with an organizational unit and aid in renaming the role prefixes effectively.

3. In the tupdprfx.sql file.

a. To edit the role prefix, edit the value of the i_role_prefix parameter. For example, if you want to change this role, called AP12 by default, to USAP, you would replace AP12 with USAP. Repeat this for each prefix listed. Ensure each prefix you type is unique and conforms to the character limitations listed in Role Prefix Naming Conventions.

b. To specify whether the organizational unit of the role will be included in the XOP instance or not, set the value of the i_use_org_in_xop_flag parameter to Y or N. Similarly, to specify whether the organizational unit of the role will be included in the global instance or not, set the value of the i_use_org_in_global_flag parameter to Y or N.

NOTE: The i_use_org_in_xop_flag and i_use_org_in_global_flag parameters are valid only if the value of the i_instance_type parameter is set to S.

c. To enable or disable the roles associated with the role prefix, set the value of i_user_enabled_flag parameter to Y or N.

4. After all changes have been done as required, save and close the file.

5. Return to your SQL*Plus session, and press ENTER to resume the generation process.

NOTE: If any of the generated roles are in conflict with other roles or users in the database, they are listed in the tmpcrole.lst file created in the NOETIX_SYS user directory.


Verify GenerationTo verify that each stage of the Noetix views generation completed without errors, you can run a script that produces an output listing of all generation errors detected. This script can be run after each individual numbered script is completed, or it can be run after all four stages of the generation process are complete.

To verify that a Noetix views generation completed successfully:1. Remain in the server directory containing the NoetixViews files.

2. Run the following script at the UNIX prompt: finderr.bat An output of all files containing errors will be displayed. This command will also create an error log called finderr.lst in the NoetixViews installation directory. Each time you run this command, this log will be overwritten.

3. Contact Noetix Technical Support if any errors are found.

Generate Noetix Help FileNoetix Help File can be generated during Stage 4 of the generation process, or at any time after generating Noetix views by using scripts.

NOTE: If any errors are detected in Stage 4 of the Noetix views generation, you cannot generate the Noetix Help File. However, if you intend to override Stage 4 generation errors and generate the Noetix Help File, you must first run the ifix4sts.sql script and then manually generate the Noetix Help File. The ifix4sts.sql script is located in the same directory where the install4.sql script is present.

The Noetix Help File is available in three formats that can be generated with the following procedure.


To generate the Noetix Help File:1. Using SQL*Plus, connect to the database as the Noetix System Administration

User. To do this, at the SQL prompt, type the following command: connect <username>/<password>@<dbconnectstring>

2. At the SQL prompt, type start <sql script>, and then press ENTER, where <sql script> specifies the script file used for generating the Noetix Help File.

The following script files are available for Noetix Help File generation:

NOTE: For more information about these help formats, see Choose Help Formats to Generate.

3. Answer any prompts asked by the script.

4. Repeat this step to generate additional help formats, if needed.


You must compile and publish the Microsoft WinHelp help file and publish the HTML help file, if generated, using the instructions in the following sections.

Help Format SQL Script

All Help Formats iallhlp.sql

Microsoft WinHelp imshlp.sql

HTML Help ihtmlhlp.sql

Query Tool Help icomhlp.sql


Compile and Publish Microsoft WinHelp FormatYou will need to compile the Microsoft WinHelp help file using the Noetix Easy Help Wizard and then publish the help file to users.

The Noetix Easy Help Wizard, which is installed along with NoetixViews Administrator, will transfer the Noetix Help File for Windows source file (.rtf ) from the server to the Windows client using the File Transfer Protocol (FTP). The wizard will then compile the file, generating the Noetix Help File locally and creating an icon on your desktop.

The Noetix Easy Help Wizard can be used if your Windows client and the server where you installed NoetixViews Administrator both use Transmission Control Protocol/Internet Protocol (TCP/IP) and the directory where you installed NoetixViews Administrator is accessible to your FTP server.

To transfer and compile the Microsoft WinHelp format:1. Log on to the Windows-based computer where NoetixViews Administrator is

installed.

2. Click Start > All Programs > NoetixViews > EasyHelp Wizard. The Noetix Easy Help Wizard is displayed. Click Next.


3. The next page prompts you for a UNIX user name, password, and URL of the server on the network to transfer the source file generated during the generation to a client where it will be compiled. The user name entered must have access to the server directory where the noetix.rtf file exists. Click Next.

4. The next page displays the path to the installation directory where the scripts and noetix.rtf file are currently located. Confirm that the installation directory in the text field is correct. Click Next.


5. The text box in the next page displays your choices for the user name, server, and directory where the scripts and the noetix.rtf file are located. To view the Noetix Help File after it is generated, select the check box. Click Finish to compile and transfer the Noetix Help File.

6. After the Noetix Help File is compiled, you will have the option of creating a desktop shortcut to the Noetix Help File on the computer running Windows. Click Yes, if you want to create a shortcut.

Next, publish the compiled help file to users.


To publish the Microsoft WinHelp help file:1. Navigate to the noetix.hlp file in

<BASE_INSTALL_DIR>\<ACCOUNT_TNS>\MsHelp, where <BASE_INSTALL_DIR> is the location where you installed NoetixViews Administrator and <ACCOUNT_TNS> is the name of the Noetix System Administration User (usually NOETIX_SYS) + _ + the TNS Name of the database instance on which the user resides.

EXAMPLE: C:\Program Files\Noetix Corporation\NoetixViews\Installs\NOETIX_SYS_dev.seattle\MsHelp

2. Move the noetix.hlp file to a shared server drive. (Each time you regenerate Noetix views, replace the single version of this file on the server.)

3. Distribute a shortcut to the shared file to all Noetix query users.

Publish the HTML Help FormatThe HTML help format does not need to be compiled, but will need to be published to users.

To publish the HTML help format:1. Navigate to the htmlhelp directory within the NOETIX_SYS user directory. (You

can point your browser to htmlhelp\help\noetix.htm to view the HTML Help.)

EXAMPLE: C:\Program Files\Noetix Corporation\NoetixViews\Installs\NOETIX_SYS_dev.seattle\htmlhelp

2. Publish the files to a Web server or shared server drive. To do this, move the entire htmlhelp directory tree to a directory on your network that is accessible to your Web browser.

3. Instruct users to open the /htmlhelp/help/noetix.htm page using a Web browser.


Run Noetix Answer Builder (When Using Noetix Platform)

NoetixAnswers, a component of Noetix Platform, is installed and maintained using Noetix Answer Builder. Noetix Answer Builder creates metadata for custom prebuilt reports based upon NoetixViews. After successfully running Noetix Answer Builder, you must run Noetix Generator for Noetix Platform—Oracle E-Business Suite Edition (Noetix Generator) to generate the metadata into Noetix QueryServer (NQS) and Noetix Web Query (NWQ).

Additionally, Noetix Generator generates your base views and your security structure into NQS and NWQ allowing you not only access your NoetixViews data in NQS and NWQ but also ensures that proper security is applied. Users logging on to NWQ will see only the data you allowed them to access in NoetixViews.

You can run Noetix Answer Builder when prompted during Stage 4 of the generation process. Alternatively, after the views are generated, you can start NoetixViews

Administrator, and click Answer Builder on the Tools menu or click on the toolbar. You can also generate answers using scripts. For doing this, use SQL*Plus on a computer that is running Windows or UNIX, and run the ianswers.sql script. For more information, see Available SQL and MS-DOS Scripts in “Maintenance.”

IMPORTANT: If there are any errors in Stage 4 of the generation, you cannot generate Noetix answers.

After you have run Noetix Answer Builder, you must generate the metadata created by Noetix Answer Builder into NQS and NWQ to create answers specific to your Oracle configuration. Apart from generating the answers, you must also generate the user and role configuration into NQS and NWQ. Run Noetix Generator for Noetix Platform—Oracle E-Business Suite Edition (Noetix Generator) to do so. For more information about Noetix Generator, see the Noetix Generator for Noetix Platform Administrator Guide for Oracle E-Business Suite.


To run Noetix Answer Builder after generating Noetix views:1. Click Start > All Programs > NoetixViews > NoetixViews Administrator. The


2. On the Tools menu, click Answer Builder or click on the toolbar. The Noetix Answer Builder Wizard is displayed.

3. Click Next.


4. On the next page, the Answer Builder check box is selected by default. The check box is unavailable for selection. Click Next.

NOTE: The Continue if warnings detected check box is displayed only in Stage 4 of the generation. The check box is not displayed if you are running Noetix Answer Builder Wizard after you have completed Stage 4 of the generation process.

5. On the next page, click Finish to run the Noetix Answer Builder Wizard.

6. When the Noetix Answer Builder process is completed successfully, an alert is displayed to inform you about the same. Click OK.

Chapter 5

Noetix Query User

Management

This chapter explains how Noetix query users are added, modified, and deleted with the use of the NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator) or scripts.


OverviewIn NoetixViews for Oracle E-Business Suite (NoetixViews), Noetix query users’ access to data is determined by the roles, the Oracle General Ledger security access, and the custom Oracle Human Resources and Oracle U.S. Federal Financials security settings. When a user is set up to use Oracle Applications mode security, the Oracle E-Business Suite responsibilities and security profiles he or she has been assigned can also provide limits on what data and views can be accessed.

Below is a description of Noetix query user types and definitions, as well as an explanation of when each Noetix query user type is best applied:

Database User (Type U)Noetix query accounts of Database User (Type U) type can be accessed through any query tool or from SQL*Plus. NoetixViews allows only users of this type to create synonyms and optimize views. Typically, the query users you create will be of this type. These user accounts should correspond to existing users in the database, and there should be no differences in capability. When you use Noetix Platform, a user account is created in Noetix QueryServer (NQS) for each Database User (Type U) type user.

Oracle E-Business Suite Authenticated User and Responsibility (Types A and R)Noetix query users of the Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) types are defined in Oracle E-Business Suite. These are not Oracle database accounts and are used to support Applications mode capability within Oracle Discoverer.

Type code User type description

U Database User

A Oracle E-Business Suite Authenticated User

R Oracle E-Business Suite Authenticated Responsibility

N Noetix System Administration User

O Oracle Administrative Database User

Chapter 5: Noetix Query User Management 121

These users are automatically added to an Applications mode End User Layer (EUL) when used in conjunction with Noetix Generator for Oracle Discoverer (Noetix Generator). If you do not plan on using Oracle Discoverer’s Applications mode authentication, then you should not establish users of these types. These user types are valid only for Oracle E-Business Suite version 11.5.9 and later.

When an Oracle E-Business Suite Authenticated Responsibility (Type R) type user is added for an Oracle E-Business Suite responsibility, any user of Oracle E-Business Suite who has this responsibility can log on to an Oracle Applications mode EUL and access permitted business areas. Noetix query users of the Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) types are active only when you use Noetix Generator with an Applications mode EUL in Oracle Discoverer or if you use Noetix WebQuery (NWQ) as a reporting tool. These user types have no impact as database users and rely on their associated APPS database user account to maintain a link with the database. If you create a standard Discoverer EUL, then, only users of Noetix System Administration User (Type N), Oracle Administrative Database User (Type O), and Database User (Type U) types will be able to log on to Oracle Discoverer with the appropriate business areas.

For convenience, set up responsibilities in Oracle E-Business Suite, and assign these responsibilities to Oracle E-Business Suite users. Then, add these responsibilities as Noetix query users of the Oracle E-Business Suite Authenticated Responsibility (Type R) type. Assign Noetix roles to these Noetix query users, and set up access to data in views for various Oracle E-Business Suite modules using the Noetix Query User Maintenance tab of the Security Manager dialog box. After these Noetix query users are generated into the Noetix Metadata Repository (NMR) with the use of the Noetix Generator for Noetix Platform—Oracle E-Business Suite Edition (Noetix Generator) or extracted into the Applications mode EUL with the use of the Noetix Generator, users can log on to NWQ or the EUL with their Oracle E-Business Suite credentials and thereafter pick the responsibilities that have been assigned to them in Oracle E-Business Suite and also set up as Noetix query users. Thus, the users will not have to be individually added as Noetix query users of the Oracle E-Business Suite Authenticated User (Type A) type; moreover, changes can be conveniently made to a few Noetix query users of the Oracle E-Business Suite Authenticated Responsibility (Type R) type instead of numerous Type A users.

You cannot log on to NWQ or to a third-party reporting tool as a Noetix query user of the Oracle E-Business Suite Authenticated Responsibility (Type R) type.


However, for an Oracle E-Business Suite user, you can set up an Oracle E-Business Suite Authenticated User (Type A) type user as well as an Oracle E-Business Suite Authenticated Responsibility (Type R) type user for its responsibility. When both of them have been set up in NoetixViews Administrator, the access mode assigned to the Oracle E-Business Suite Authenticated User (Type A) type user will take precedence.

If the existing responsibilities do not provide a useful structure for reporting security, separate reporting responsibilities should be created in Oracle E-Business Suite as a means to grant access to Noetix views. These responsibilities are groups to put together users based on the access they can have to Noetix views and are not to be used by Oracle E-Business Suite.

This way only a group of users are allowed to access Noetix views instead of all the users of a particular responsibility. With this approach, license compliance becomes easier for the client.

When you use Noetix Platform, a user account in NQS is created for each Oracle E-Business Suite Authenticated User type user. When users log on to NWQ using those user accounts, they are prompted with a list of responsibilities and have to pick up the one they want to log on with. Noetix Platform can import these responsibilities only from Oracle E-Business Suite 11i and later.

Noetix System Administration User (Type N)The Noetix System Administration User (Type N) is a special query user account associated with the current NOETIX_SYS schema. This account is created during generation. Optimizing views and synonyms cannot be created for the NOETIX_SYS user.

Oracle Administrative Database User (Type O)The Oracle Administrative Database User (Type O) is defined automatically depending on the APPS user in Oracle E-Business Suite. It is possible to have multiple Oracle Administrative Database Users if there are multiple APPS users in Oracle E-Business Suite.

The Noetix query users of the Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) types rely on the APPS user to maintain a link with the database. Therefore, the APPS user should have the responsibilities and privileges in Oracle E-Business Suite that are required for the Noetix query users to effectively query the database through Noetix views.


The Oracle Administrative Database User (Type O) and Noetix System Administration User (Type N) are database logon accounts that are automatically created as needed.

Gather User InformationYou 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 for Oracle E-Business Suite (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). For more information about how to assign roles, see step 12 in “Creating Noetix Query Users Using GUI.”

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 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. 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 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 step 11 in “Creating Noetix Query Users Using GUI.”


• 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 step 6 in “Creating Noetix Query Users Using GUI.”

• Decide the ledgers 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 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 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 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 or access a custom list of ledgers. Also, for the Noetix views for U.S. Federal Financials, you can create custom lists of ledgers and assign appropriate budget access levels for the Noetix query users to control their access to those ledgers. For more information about how to assign ledgers, see step 7 in “Creating Noetix Query Users Using GUI.”

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. 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 Noetix views for the Oracle Install Base, Oracle Order Management, Oracle Payables, Oracle Projects, Oracle Purchasing, Oracle Receivables, and Oracle Service Contracts. 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 step 8 in “Creating Noetix Query Users Using GUI.”


• 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 Materials, 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 step 9 in “Creating Noetix Query Users Using GUI.”

• 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 step 10 in “Creating Noetix Query Users Using GUI.”


Create Noetix Query Users Using GUI

Creating a Noetix query user involves either of the following:

• Granting an existing database user, Oracle E-Business Suite user, or Oracle E-Business Suite responsibility access to Noetix views.

• Creating a database user and granting access to NoetixViews for Oracle E-Business Suite (NoetixViews).

You can add Noetix query users using the Noetix Query User Maintenance tab of the Security Manager dialog box of the NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator). Apart from using the dialog box-based method of adding a Noetix query user, you can also use the add user wizard. For adding a Noetix query user using an existing database user, Oracle E-Business Suite user, or Oracle E-Business Suite responsibility, you can use both the methods. However, if you need to create a database user before adding it as a Noetix query user, you can use only the add wizard.

NOTE: In Oracle E-Business Suite Release 12, the concept of set of books has been replaced by ledger. In this guide both “set of books” and “ledger” have been used interchangeably to refer to the same concept.

Add a Noetix Query User Using an Existing UserUse the instructions below if you are adding an existing database user or Oracle E-Business Suite user or responsibility as a Noetix query user.

To add a Noetix query user:1. Click Start > All Programs > NoetixViews > NoetixViews Administrator. The


2. Log on as the Noetix System Administration User.


3. Click on the NoetixViews Administrator toolbar. Alternatively, on the Tools menu, click Security Manager. The Security Manager dialog box appears. The Noetix Query User Maintenance tab of the Security Manager dialog box displays the names and types of the users who have been added as Noetix query users. By default, you can see the Noetix System Administration User (Type N) and Oracle Administrative Database User (Type O). The dates on which the Noetix query user accounts were created and would expire are indicated. For Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) type users, the start and end dates correspond to the start and end dates of the respective Oracle E-Business Suite users and responsibilities. The Noetix Query User Maintenance tab also indicates whether views are optimized for query tools and synonyms for the views are created for the selected users.


4. On the Noetix Query User Maintenance tab, click Add. The Add Users Properties dialog box appears.


5. On the General tab, do the following:

a. Select a user type in the User Type list. The available options are Database User, Oracle E-Business Suite Authenticated User, and Oracle E-Business Suite Authenticated Responsibility.

b. Click Add. If the user type selected is Database User (Type U) or Oracle E-Business Suite Authenticated User (Type A), the Add Users dialog box appears. If the user type selected is Oracle E-Business Suite Authenticated Responsibility (Type R), the Add Responsibilities dialog box appears.

NOTE: For Oracle E-Business Suite Authenticated User (Type A) type users, the list of users displays only those users who have one or more responsibilities assigned to them in Oracle E-Business Suite.


To add a Noetix query user of the Database User (Type U), Oracle E-Business Suite Authenticated User (Type A), or Oracle E-Business Authenticated Responsibility (Type R) type, follow these steps:

i. (Optional) In the Add Users or Add Responsibilities dialog box, use the % or _ wildcard characters in the Name filter box to filter the users by name.

ii. (Optional) If the user type selected is Oracle E-Business Suite Authenticated User (Type A), in the Responsibility filter list, select a responsibility name to filter the users based on their Oracle E-Business Suite responsibility.

iii. From the User Name or Responsibility Name list, select the required user names or responsibilities by selecting the corresponding check boxes.


If you want to select all user names or responsibilities, click Select All. If you want to clear the selection, click Deselect All. The number of users or responsibilities selected is displayed at the bottom of the dialog box.

NOTE: If the user names or responsibilities that you want to select are not listed in the list, close the dialog box. On the General tab, click Refresh. A message appears stating that the list of user names or responsibilities is updated.

iv. Click OK to add the users and return to the General tab. The selected users or responsibilities are displayed in the Names list. Also, the number of users or responsibilities selected is displayed beneath the Names list.

IMPORTANT: If the names of database users selected for adding as Noetix query users contain lower-case or mixed-case letters and special characters that are not supported by Oracle Database, the names should be provided within double quotation marks when the corresponding users log on to Oracle Discoverer Desktop.

c. In the Language list, click a language used by NoetixViews. If you select <Default Noetix Language Processing>, the language associated with the current environment will be set as the default language for the selected Noetix query users. If that language is not defined in Oracle E-Business Suite, the language that was chosen during Stage 4 of the generation process will be set as the default language.


d. (Optional) Select the Create Query Tool Optimizing Views check box, which is available only for Database User (Type U) type users. Selecting this check box at the time of creating a Database User type Noetix query user account enhances the performance of reporting tools (for example, Noetix Platform, Microsoft Access, or Crystal Reports) that query directly from the database rather than their own meta-layers.

NOTE: Reporting tools (for example, Oracle Discoverer’s End User Layer (EUL), SAP BusinessObjects’ Universe, or IBM Cognos' Catalog) that access their own meta-layers do not benefit from this option. Therefore, do not select this check box while using any reporting tool that accesses its own meta-layer.

e. If the user type selected is Database User (Type U), make sure that the Create Synonyms check box is selected. This option creates synonyms for views corresponding to each role granted to the Noetix query users. The Create Synonyms check box is available only for Database User (Type U) type users and it is selected by default. Clear this check box if the synonyms are not to be created. However, it is recommended to keep this check box always selected.

NOTE: Do not select the Create Query Tool Optimizing Views and Create Synonyms check boxes if the Noetix query users of the Database User type also own Oracle E-Business Suite tables. If you do so, you may encounter problems while assigning Noetix roles to the users.

If you click OK on this tab without navigating to the Roles tab and assigning roles to the user, a confirmation message appears prompting you whether to create Noetix query user accounts without assigning any roles to them. Click Yes if you want to proceed. Click No if you want to assign roles and row-level security to the selected users or responsibilities.


6. Use the Business Group tab to control access to data in global Noetix views for Oracle Advanced Benefits, Oracle Human Resources, Oracle Payroll, and Oracle Time and Labor based on business groups for a Noetix query user.

Use the Business Group tab on the Add Users Properties dialog box of the NoetixViews Administrator to control access to data in the Oracle Human Resources Management System (HRMS) for a Noetix query user. For more information about controlling access to HRMS data and the views for which secured or customizable access is available, see Row-level security in “Module-Specific Information.”


The Business Group tab will be available only if:

• You have purchased the global form of Noetix views for at least one of the following Oracle E-Business Suite modules:

• Human Resources,

• Payroll

• Advanced Benefits

• Time and Labor

• You are not modifying Oracle Administrative Database User (Type O) type user.

IMPORTANT: When assigning row-level security to Noetix query users using the Business Group tab, the following points should be noted:

• For allowing Noetix query users to view data from the Noetix views for the selected Oracle application, appropriate roles corresponding to the selected business groups should be assigned to the users.

• In Oracle Discoverer and Noetix WebQuery, user authentication based on the roles and row-level security settings similar to Oracle E-Business Suite is supported. For information, see Row-level security.

• In Oracle Business Intelligence (Oracle BI), SAP BusinessObjects, and IBM Cognos Business Intelligence (Cognos BI), user authentication based on the roles and row-level security settings are supported for only the Oracle E-Business Suite Authenticated User (Type A) type Noetix query users if the query users are mapped to the users registered in these BI tools. For information, see Row-level security.


To control access to HRMS data:1. Click an application name in the Application list. Your options are Benefits,

HR, Payroll, and Time and Labor. After you select the application, the corresponding settings appear in the Settings for the <application name> application section.

2. Select or clear the Enforce Oracle HR security profile processing check box. When the check box is selected, the following options for global security profiles are available:

• the business group specified by the user's login session: This option is the default for Noetix query users of the Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) types. This option ensures that even if the Noetix query user's logon credentials in Oracle E-Business Suite include a global security profile, data is returned for only the business group derived from these credentials. In other words, data is not returned for other business groups that are encompassed by the global security profile. Thus, this option provides the same level of security that is present in Oracle E-Business Suite.

• all business groups included in the global security profile: This option ensures that data is returned for business groups encompassed by the Noetix query user's global security profile as long as they are also displayed in the Assigned Business Groups list. This option enables the Noetix query user to access data from multiple business groups through a global view for Advanced Benefits, Human Resources, Payroll, and Time and Labor with the row-level restrictions specified by the global security profile.

Regardless of which option you choose, you still need to ensure that the business groups you want the Noetix query user to access with the row-level restrictions applied in Human Resources are also in the Assigned Business Groups list.


If you do not want to filter data according to the security profiles of the Noetix query user, clear the Enforce Oracle HR security profile processing check box, and proceed with the next step.

IMPORTANT: The Enforce Oracle HR security profile processing check box is available for Noetix query users of the Database User (Type U) and Noetix System Administration User (Type N) types only if they are also set up as the reporting users for security profiles.

3. In the Settings for the <application name> application section, select one of the following options:

• Derive from Oracle EBS: Click this option to grant access to business groups on the basis of the Noetix query user's security settings in Human Resources. This option is available only if the Noetix query user is of the Oracle E-Business Suite Authenticated User (Type A) or Oracle E-Business Suite Authenticated Responsibility (Type R) type. This is also the default option for these users. These business groups will appear in the Assigned Business Groups list and cannot be modified. When the Standard HRMS security model is used, the list is determined by the values of the HR:Business Group profile option for all responsibilities assigned to the Noetix query user. In the case of the Security Groups Enabled security model, the list is determined by the security groups assigned to the Noetix query user of the Oracle E-Business Suite Authenticated User (Type A) type. If the Noetix query user is of the Oracle E-Business Suite Authenticated Responsibility (Type R) type, the list will be empty. Go to step 13 to save the changes.

NOTE: If multiple users are selected, the Assigned Business Groups list will display the "<multiple users selected>" text for this option.

• Custom: Click this option to grant access to a custom list of business groups. After you have selected this option, the Add button will be available below the Assigned Business Groups list. By default, this option is selected for users of the Noetix System Administration User (Type N) and Database User (Type U) types. Go to step 4 to proceed with adding business groups.


• All: Click this option to grant access to all the business groups defined in Human Resources. The business groups will appear in the Assigned Business Groups list. Go to step 13 to save the changes.

If the data access privileges of the Oracle E-Business Suite Authenticated User (Type A) type, Oracle E-Business Suite Authenticated Responsibility (Type R) type, and reporting users change in Oracle E-Business Suite, click Refresh

Security ( ) on the toolbar of the NoetixViews Administrator. For more information, see Row-level security.

NOTE: On clicking the Refresh Security button, a message is displayed, stating that the process of refreshing the security may take some time.


4. To specify a custom list of business groups, do the following:

a. Click Add. The Add Business Groups dialog box appears with the list of all the business groups that have been defined in Human Resources and that are yet to be added to the Assigned Business Groups list.


The following columns and options are available in the Add Business Groups dialog box:

• Show only current user’s Oracle EBS-derived access: Allows you to view only the business groups that are accessible to the Oracle E-Business Suite Authenticated User (Type A) or Oracle E-Business Suite Authenticated Responsibility (Type R) type user in the selected Oracle application. This check box is available for only the Oracle E-Business Suite Authenticated User (Type A) type or Oracle E-Business Suite Authenticated Responsibility (Type R) type users. If you do not select this check box, all the business groups that are available in the selected Oracle application will be listed.

• Name: Indicates the name of the business group.

• ID: Indicates the ID of the business group.

• Legislation Name: Indicates the legislation name corresponding to the business group.

• Legislation Code: Indicates the legislation code corresponding to the legislation.

• Affected Noetix Roles: Indicates the Noetix roles that have access to the views corresponding to the business group.

• EBS-Derived: Indicates whether the user can access the business group in the selected Oracle application.

Click a column title to sort the business groups by the entity represented by the column.

NOTE: You need to scroll to the right to see all the information in a row. The width of columns in the list can be adjusted to see more if required. To adjust the width of columns in the list, select the line between columns in the header, and drag it to the required position. Also, you can resize the height and width of the dialog box by dragging the sides of the dialog box.


b. To see only those business groups that are accessible to the Noetix query user in Human Resources, select the Show only current user's Oracle EBS-derived access check box. This check box is available for only the Oracle E-Business Suite Authenticated User (Type A) type or Oracle E-Business Suite Authenticated Responsibility (Type R) type users.

c. To assign a business group to the Noetix query user, select the corresponding check box. To select all the business groups, click Select All. To clear the selection, click Deselect All.

d. Click OK. The selected business groups will be listed in the Assigned Business Groups list of the Business Group tab.

e. To remove a business group from the Assigned Business Groups list, select the business group, and click Remove. To select multiple business groups, press CTRL, and click the business groups.

IMPORTANT: If application-specific security of Human Resources is applied, data will be returned with row-level security for only those business groups that are in the Assigned Business Groups list and that are also accessible to the Noetix query user in Human Resources. If application-specific security of Human Resources is not applied, data will be returned without row-level security for the business groups in the Assigned Business Groups list.


7. Use the Ledger tab to do one or more of the following:

• Control access to data in the global form of Noetix views for Oracle Assets and Oracle General Ledger based on ledgers for a Noetix query user.

• Control access to data in the standard, Cross Operations Extension (XOP), and global forms of Noetix views for Oracle U.S. Federal Financials based on ledgers for a Noetix query user. In some Noetix views for U.S. Federal Financials, access to data can be controlled at both ledger and budget access levels. For more information about NoetixViews for Oracle U.S. Federal Financials and views for which you have to specify budget-level security, see Row-level security in “Module-Specific Information.”

NOTE: The tab, list, and column labels change dynamically based on the version of Oracle E-Business Suite at your site. For Oracle E-Business Suite versions prior to Release 12, the labels appear as Set of Books where applicable. For Oracle E-Business Suite Release 12 and later, the labels appear as Ledger.

The Ledger tab will be available only if:


• You have purchased the global form of Noetix views for Assets.

• You have purchased the global form of Noetix views for General Ledger.

• You have purchased the standard, XOP, or global form of Noetix views for U.S. Federal Financials.

• You are not modifying the Oracle Administrative Database User (Type O) type user.

IMPORTANT: When assigning row-level security to Noetix query users using the Ledger tab, the following points should be noted:





To control access to data in Noetix views based on ledgers:1. In the Application list, click an application name. The options are Assets,

Federal Financials, and General Ledger. After you select the application, the corresponding settings appear in the Settings for the <application name> application section.


• Derive from Oracle EBS: Click this option to grant access to ledgers based on the security settings of the Noetix query user in the selected Oracle application. This option is available only if the Noetix query user is of the Oracle E-Business Suite Authenticated User (Type A) type or Oracle E-Business Suite Authenticated Responsibility (Type R) type. This is also the default option for these users. The ledgers to which the user has access are displayed in the Ledgers list. If you click this option for the Federal Financials application, the ledgers to which the user has access are displayed in the Ledgers list. The budget levels assigned to the user for each ledger are displayed in the Budget Access Levels list on the right. When this option is selected, the data in the lists cannot be modified. Go to step 13 to save the changes.

NOTE: If multiple users are selected, the Ledgers list will display the "<multiple users selected>" text for this option.

• Custom: Click this option to grant access to a custom list of ledgers. After you select this option, the Add button will be available below the Ledgers list. By default, this option is selected for users of the Noetix System Administration User (Type N) and Database User (Type U) types. For the Federal Financials application, click this option to specify ledgers and budget access levels for Noetix query users and grant them custom access to U.S. Federal Financials views. For information about specifying a custom list of ledgers and associated budget access levels for Noetix query users, see steps 3 and 4 respectively.


• All: Click this option to assign all the ledgers in the selected Oracle application to the Noetix query users. The ledgers are displayed in the Ledgers list. For the Federal Financials application, click this option to assign all the ledgers and the associated budget access levels to the Noetix query users. The ledgers are displayed in the Ledgers list. The budget levels associated with each ledger are displayed in the Budget Access Levels list. When this option is selected, the data in the lists cannot be modified. Go to step 13 to save the changes.

If the data access privileges of the Noetix query users of the Oracle E-Business Suite Authenticated User (Type A) type or Oracle E-Business Suite Authenticated Responsibility (Type R) type change in Oracle E-Business Suite or if row-level security changes have been made in Oracle E-Business

Suite, click Refresh Security ( ) on the toolbar of the NoetixViews Administrator to update the changes in NoetixViews. For more information, see Row-level security.

NOTE: When you click the Refresh Security button, a message is displayed stating that the process of refreshing the security may take some time.


3. To specify a custom list of ledgers, do the following:

a. Click Add below the Ledgers list. The Add Ledgers dialog box displays the list of ledgers that are available in the selected Oracle application and that are yet to be added to the Ledgers list.

The following columns and options are available in the Add Ledgers dialog box:

• Show only current user’s Oracle EBS-derived access: Allows you to view only the ledgers that are accessible to the Oracle E-Business Suite Authenticated User (Type A) or Oracle E-Business Suite Authenticated Responsibility (Type R) type user in the selected Oracle application. This check box is available for only the Oracle E-Business Suite Authenticated User (Type A) type or Oracle E-Business Suite Authenticated Responsibility (Type R) type users. If you do not select this check box, all the ledgers that are available in the selected Oracle application will be listed.


• Ledger: Indicates the name of the ledger.

• Ledger ID: Indicates the ledger ID.

• Chart of Accounts: Indicates the chart of accounts corresponding to the ledger.

• COA ID: Indicates the chart of accounts ID.

• Affected Noetix Roles: Indicates the Noetix roles that have access to the views corresponding to the ledger.

• EBS-Derived: Indicates whether the user can access the ledger in the selected Oracle application.

Click a column title to sort the ledgers by the entity represented by the column.


b. To assign a ledger to the Noetix query user, select the corresponding check box. To select all the ledgers, click Select All. To clear the selection, click Deselect All.

c. Click OK. The selected business groups will be listed in the Ledgers list of the Ledger tab.

NOTE: You need to scroll to the right to see all the information in a row. The width of columns in the list can be adjusted to see more if required. To adjust the width of columns in the list, select the line between columns in the header, and drag it to the required position.

d. To remove a business group from the Ledgers list, select the ledger, and click Remove. To select multiple ledgers, press CTRL, and click the ledgers.


4. If you select the Federal Financials application in step 1, you can specify budget access levels for the ledgers that you have added in step 3. To specify budget access levels for a selected combination of chart of accounts and ledger, do the following:

a. In the Ledgers list, select a ledger. The Add button below the Budget Access Levels list becomes available. Click Add. The Add Budget Access Levels dialog box is displayed.


The following columns and options are available in the Add Budget Access Levels dialog box:

• Show only current user’s Oracle EBS-derived access: Allows you to view only the budget levels assigned to the Oracle E-Business Suite Authenticated User (Type A) or Oracle E-Business Suite Authenticated Responsibility (Type R) type user in U.S. Federal Financials for the selected ledger. This check box is available for only the Oracle E-Business Suite Authenticated User (Type A) type or Oracle E-Business Suite Authenticated Responsibility (Type R) type users. If you do not select this check box, all the budget access levels for the ledger as defined in U.S. Federal Financials will be listed.

• Sequence: Indicates the sequence of the budget level.

• Name: Indicates the name of the budget level.

• EBS-Derived: Indicates whether the budget level is accessible to the user in U.S. Federal Financials.

Click a column title to sort the budget levels by the entity represented by the column.


b. To assign a budget access level to the Noetix query user, select the corresponding check box. To select all the budget access levels, click Select All. To clear the selection, click Deselect All.

c. Click OK. The selected budget access levels will be listed in the Budget Access Levels list of the Ledger tab.


d. Repeat steps a through d for each ledger.


e. To remove a budget access level for a ledger from the Budget Access Levels list, select a ledger from the Ledgers list, select the budget access level for the selected ledger, and then click Remove. To select multiple budget access levels, press CTRL, and click the budget access levels.

8. Use the Operating Unit tab to control access to data in global Noetix views for Oracle Install Base, Oracle Order Management, Oracle Payables, Oracle Projects, Oracle Purchasing, Oracle Receivables, and Oracle Service Contracts based on operating units for a Noetix query user.

The Operating Unit tab will be available only if:


• Install Base

• Order Management


• Payables

• Projects

• Purchasing

• Receivables

• Service Contracts


IMPORTANT: When assigning row-level security to Noetix query users using the Operating Unit tab, the following points should be noted:





To control access to data in Noetix views based on operating units:1. In the Application list, click an application name. The options are Install Base,

Order Management, Payables, Projects, Purchasing, Receivables, and Service Contract. After you select the application, the corresponding settings appear in the Settings for the <application name> application section.


• Derive from Oracle EBS: Click this option to grant access to operating units based on the security settings of the Noetix query user in the selected Oracle application. This option is available only if the Noetix query user is of the Oracle E-Business Suite Authenticated User (Type A) or Oracle E-Business Suite Authenticated Responsibility (Type R) type. This is also the default option for these users. The operating units to which the user has access are displayed in the Operating Units list. When this option is selected, the data in the list cannot be modified. Go to step 13 to save the changes.

NOTE: If multiple users are selected, the Operating Units list will display the "<multiple users selected>" text for this option.

• Custom: Click this option to grant access to a custom list of operating units. After you select this option, the Add button will be available. By default, this option is selected for users of the Noetix System Administration User (Type N) and Database User (Type U) types. For information about specifying a custom list of operating units, see step 3.

• All: Click this option to grant access to all the operating units available in the selected Oracle application to the Noetix query user. The operating units are displayed in the Operating Units list. When this option is selected, the data in the list cannot be modified. Go to step 13 to save the changes.


If the data access privileges of the Noetix query users of the Oracle E-Business Suite Authenticated User (Type A) type or Oracle E-Business Suite Authenticated Responsibility (Type R) type change in Oracle E-Business Suite or if row-level security changes have been made in Oracle E-Business Suite, click Refresh

Security ( ) on the toolbar of the NoetixViews Administrator to update the

changes in NoetixViews. For more information, see Row-level security.


3. To specify a custom list of operating units, do the following:

a. Click Add. The Add Operating Units dialog box displays the list of operating units that are available in the selected Oracle application and that are yet to be added to the Operating Units list.

The following columns and options are available in the Add Operating Units dialog box:


• Show only current user’s Oracle EBS-derived access: Allows you to view only the operating units that are accessible to the Oracle E-Business Suite Authenticated User (Type A) type or Oracle E-Business Suite Authenticated Responsibility (Type R) type user in the selected Oracle application. This check box is available for only the Oracle E-Business Suite Authenticated User (Type A) type or Oracle E-Business Suite Authenticated Responsibility (Type R) type users. If you do not select this check box, all the operating units that are available in the selected Oracle application will be listed.

• Operating Unit: Indicates the name of the operating unit.

• Org ID: Indicates the organization ID for the corresponding operating unit.

• Organization: Indicates the organization name for the corresponding operating unit.

• Ledger: Indicates the name of the ledger corresponding to the operating unit.

• Ledger ID: Indicates the ledger ID.

• Chart of Accounts: Indicates the chart of accounts corresponding to the ledger.


• Affected Noetix Roles: Indicates the Noetix roles that have access to the views corresponding to the operating unit.

• EBS-Derived: Indicates whether the user can access the operating unit in the selected Oracle application.


Click a column title to sort the operating units by the entity represented by the column.


b. To assign an operating unit to the Noetix query user, select the corresponding check box. To select all the operating units, click Select All. To clear the selection, click Deselect All.

c. Click OK. The selected operating units will be displayed in the Operating Units list of the Operating Unit tab.


d. To remove an operating unit from the Operating Units list, select the operating unit, and click Remove. To select multiple operating units, press CTRL, and click the operating units.


9. Use the Inventory Organization tab to control access to data in global 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 based on the inventory organizations for a Noetix query user.

The Inventory Organization tab will be available only if:


• Bills of Material

• Cost Management

• Enterprise Asset Management

• Inventory


• Master Scheduling/MRP

• Quality

• Work in Process


IMPORTANT: When assigning row-level security to Noetix query users using the Inventory Organization tab, the following points should be noted:





To control access to data in Noetix views based on inventory organizations:1. In the Application list, click an application name. The options are Bill of

Materials, Cost Management, Enterprise Asset Management, Inventory, MRP, Master Sched. & Capacity, Quality, and Work in Process. After you select the application, the corresponding settings appear in the Settings for the <application name> application section.


• Derive from Oracle EBS: Click this option to grant access to inventory organizations based on the security settings of the Noetix query user in the selected Oracle application. This option is available only if the Noetix query user is of the Oracle E-Business Suite Authenticated User (Type A) or Oracle E-Business Suite Authenticated Responsibility (Type R) type. This is also the default option for these users. The inventory organizations to which the user has access are displayed in the Inventory Organizations list. When this option is selected, the data in the list cannot be modified. Go to step 13 to save the changes.

NOTE: If multiple users are selected, the Inventory Organizations list will display the "<multiple users selected>" text for this option.

• Custom: Click this option to grant access to a custom list of inventory organizations. After you select this option, the Add button will be available. By default, this option is selected for users of the Noetix System Administration User (Type N) and Database User (Type U) types. For information about specifying a custom list of inventory organizations, see step 3.

• All: Click this option to grant access to all the inventory organizations available in the selected Oracle application. The inventory organizations are displayed in the Inventory Organizations list. When this option is selected, the data in the list cannot be modified. Go to step 13 to save the changes.


3. To specify a custom list of inventory organizations, do the following:

a. Click Add. The Add Inventory Organizations dialog box displays the list of the inventory organizations that are available in the selected Oracle application and that are yet to be added to the Inventory Organizations list.

The following columns and options are available in the Add Inventory Organizations dialog box:

• Show only current user’s Oracle EBS-derived access: Allows you to view only the inventory organizations that are accessible to the Oracle E-Business Suite Authenticated User (Type A) or Oracle E-Business Suite Authenticated Responsibility (Type R) type user. This check box is available for only the Oracle E-Business Suite Authenticated User (Type A) type or Oracle E-Business Suite Authenticated Responsibility (Type R) type users. If you do not select this check box, all the inventory organizations that are available in the selected Oracle application will be listed.


• Organization: Indicates the inventory organization.

• Organization ID: Indicates the inventory organization ID.

• Master Organization: Indicates the item master organization.

• Master Organization ID: Indicates the item master organization ID.

• Organization Code: Indicates the inventory organization code.

• Chart of Accounts: Indicates the chart of accounts for the corresponding inventory organization.


• Cost Organization: Indicates the cost organization for the corresponding inventory organization.

• Cost Organization ID: Indicates the cost organization ID.

• Affected Noetix Roles: Indicates the Noetix roles that have access to the views corresponding to the inventory organization.

• EBS-Derived: Indicates whether the user can access the inventory organization in the selected Oracle application.

b. Click a column title to sort the inventory organizations by the entity represented by the column.


c. To assign an inventory organization to the Noetix query user, select the corresponding check box. To select all the inventory organizations, click Select All. To clear the selection, click Deselect All.


d. Click OK. The selected inventory organizations will be displayed in the Inventory Organizations list of the Inventory Organization tab.


e. To remove an inventory organization from the Inventory Organizations list, select the inventory organization, and click Remove. To select multiple inventory organizations, pres CTRL, and click the inventory organizations.

10. Use the Service Request tab to control access to data in global Noetix views for Oracle Depot Repair, Oracle Field Service, and Oracle TeleService based on the service request types for a Noetix query user.


The Service Request tab will be available only if:

• You have purchased Noetix views for at least one of the following Oracle E-Business Suite modules:

• Depot Repair

• Field Service

• TeleService


IMPORTANT: When assigning row-level security to Noetix query users using the Service Request tab, the following points should be noted:





To control access to data in Noetix views based on service request types:1. In the Application list, click an application name. The available options are Depot

Repair, Field Service, and TeleService. After you select the application, the corresponding settings appear in the Settings for the <application name> application section.


• Derive from Oracle EBS: Click this option to grant access to service request types based on the security settings of the Noetix query user in the selected Oracle application. This option is available only if the Noetix query user is of the Oracle E-Business Suite Authenticated User (Type A) or Oracle E-Business Suite Authenticated Responsibility (Type R) type. This is also the default option for these users. The service request types to which the user has access are displayed in the Service Request list. When this option is selected, the data in the list cannot be modified. Go to step 13 to save the changes.

NOTE: If multiple users are selected, the Service Requests list will display the "<multiple users selected>" text for this option.

• Custom: Click this option to grant access to a custom list of service request types. After you select this option, the Add button will be available. By default, this option is selected for users of the Noetix System Administration User (Type N) and Database User (Type U) types. For information about specifying a custom list of service request types, see step 3.

• All: Click this option to grant access to all the service request types available in the selected Oracle application. The service request types are listed in the Service Requests list. When this option is selected, the data in the list cannot be modified. Go to step 13 to save the changes.






3. To specify a custom list of service request types, do the following:

a. Click Add. The Add Service Requests dialog box displays the list of the service request types that are available in the selected Oracle application and that are yet to be added to the Service Requests list.

The following columns and options are available in the Add Service Requests dialog box:


• Show only current user’s Oracle EBS-derived access: Allows you to view only the service request types that are accessible to the Oracle E-Business Suite Authenticated User (Type A) type or Oracle E-Business Suite Authenticated Responsibility (Type R) type user. This check box is available for only the Oracle E-Business Suite Authenticated User (Type A) type or Oracle E-Business Suite Authenticated Responsibility (Type R) type users. If you do not select this check box, all the service request types that are available in the selected Oracle application will be listed.

• Type Name: Indicates the service request type.

• Type ID: Indicates the service request type ID.

• Affected Noetix Roles: Indicates the Noetix roles that have access to the views corresponding to the service request type.

• EBS-Derived: Indicates whether the user can access the service request type in the selected Oracle application.

Click a column title to sort the service request types by the entity represented by the column.


b. To assign a service request type to the Noetix query user, select the corresponding check box. To select all the service request types, click Select All. To clear the selection, click Deselect All.

c. Click OK. The selected service request types will be listed in the Service Requests list of the Service Request tab.



d. To remove a service request type from the Service Requests list, select the service request type, and click Remove. To select multiple service request types, press CTRL, and click the service request types.

11. Use the Security Rules tab to control the access to accounting data corresponding to a ledger in the NoetixViews for General Ledger based on the Accounting Flexfield security rules assigned to a Noetix query user. The Security Rules tab will be available only if your NoetixViews configuration has views that support Accounting Flexfield security rules. For more information, see Row-level security in “Module-Specific Information.”

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.”


IMPORTANT: When assigning row-level security to Noetix query users using the Security Rules tab, the following points should be noted:




To control access to accounting data in Noetix views based on flexfield security rules:1. In the Forms of views - application list, click an application name. The options

are Global - General Ledger and Standard & Cross Operational - All.

2. In the Select enforcement option list, select one of the options. The options are No Rows, All Rows, Effective Responsibility, All Responsibilities, and Per Ledger. If you select Per Ledger, go to next step to customize the flexfield security rules setting for a selected ledger. Otherwise, go to step 13 to save the changes. For information about the enforcement options, see Row-level security in “Module-Specific Information.”

NOTE: The available options may vary depending on the type of the Noetix query user you select.

If a new ledger is added in Oracle E-Business Suite, the views must be regenerated in order for the security rules to be enforced by the Noetix views that would return data for that ledger. If any security rule-to-responsibility assignment changes or additions are made or any responsibility-to-user assignment changes or

additions are made, click Refresh Security ( ) on the toolbar of NoetixViews

Administrator to update the changes in NoetixViews. If the definition of an existing rule is changed, the change is automatically detected by NoetixViews without regenerating the views or refreshing the security.


3. If you have selected the Per Ledger option in step 2, do the following:

a. In the list of ledgers displayed, click the ledger that you want to select.

NOTE: For the standard and XOP forms of the views, the list of ledgers displayed will contain only those ledgers for which flexfield security rules are available.

b. Under Enforcement Options per Ledger, select one of the options. The options are Effective Responsibility, All Responsibilities, No Rows, All Rows, Assign rules. If you select Assign rules, go to step 4.

c. Repeat steps a and b if you want to select another ledger. Otherwise, go to step 13 to save the changes.

4. If you have selected the Assign rules option in step 3, the Add GL Security Rules dialog box is displayed.


After the Add GL Security Rules dialog box is displayed, do the following:

a. To assign a flexfield security rule to the Noetix query user, select the corresponding check box. To select all the flexfield security rules, click Select All. To clear the selection, click Deselect All.

The following columns are available in the Add GL Security Rules dialog box:

• Rule Name: Indicates the name of the flexfield security rule.

• Rule ID: Indicates the ID of the flexfield security rule.

• Chart of Accounts: Indicates the chart of accounts that the flexfield security rule is assigned to.

• Segment Name: Indicates the segment column for which the flexfield security rule is defined.


b. Click OK. The selected flexfield security rules will be displayed in the Accounting KFF Security Rules list of the Security Rules tab under the Enforcement Options per ledger area. To remove a security rule, select the flexfield security rule, and then click Remove.

IMPORTANT: If you have purchased global Noetix views for General Ledger, make sure that the ledgers for which you are assigning flexfield security rules are also selected in the Ledger tab.

5. Repeat steps 3 and 4 if you want to assign flexfield security rules for another ledger. Otherwise, go to step 13 to save the changes.


12. Use the Roles tab to assign roles to the Noetix query user.

NOTE: The column labels change dynamically based on the version of Oracle E-Business Suite at your site. For Oracle E-Business Suite versions prior to Release 12, the labels appear as Set of Books where applicable. For Oracle E-Business Suite Release 12 and later, the labels appear as Ledger.

By default, all role labels appear as selected on the Noetix Role Labels list. The following columns are available:

• Role Label Name: The label or description for the role. Role labels are logical groups of related roles that may have different organizational units or role types. They help you in easily finding the required roles and granting them to the user.

• Granted Roles: The number of roles granted to the user for the corresponding role label.


• Application: The name of the module to which the role belongs, for example, General Ledger (Oracle General Ledger) and Payables (Oracle Payables).

• Application ID: The module ID in Oracle E-Business Suite.

You can select a role label to add the corresponding roles or select multiple role labels. To select multiple role labels, press CTRL, and click the role labels.

IMPORTANT: When assigning roles to Noetix query users using the Roles tab, the following points should be noted:





To add roles:1. On the Roles tab, select the required role labels from the Noetix Role Labels

list.

2. Click Add. The Add Noetix Roles dialog box is displayed. The roles displayed in this dialog box correspond to the selected role labels on the Noetix Role Labels list and are yet to be assigned to the Noetix query user.

The following are the columns in the Add Noetix Roles dialog box:

• Role Name: The name of the role, as edited during Stage 4.

• Role Type: The type of the role, whether it is a standard, Cross Operations Extension (XOP), or global role.

• Application Label: The name of the module for which the role has been created, for example, GL (General Ledger) and HR (Oracle Human Resources).


• Description: The description of the role.

• Role Label: The role label corresponding to the role.

• Operating Unit: The operating unit with which the role is associated.

• Inventory Organization: The inventory organization with which the role is associated.

• Ledger: The ledger with for which the role has been created.

• Business Group: The business group for which the role has been created.

• Chart of Accounts: The chart of accounts with which the role is associated.

• Master Organization: The name of the item master organization with which the role is associated.

NOTE: You need to scroll to the right to see all the information in a row. The width of columns in the list can be adjusted to see more if required. To adjust the width of columns in the list, select the line between columns in the header, and drag it to the required position. Click a column title to sort the roles by the entity represented by the column. Also, you can resize the height and width of the dialog box by dragging the sides of the dialog box.

3. To assign a role to the Noetix query user, select the corresponding check box. To select all the roles, click Select All. To clear the selection, click Deselect All.


4. Click OK. The selected roles will be displayed in the Granted Noetix Roles list of the Roles tab.

NOTE: You can click Remove selected to remove the selected roles or Remove all to remove the roles granted to the user for all role labels.

IMPORTANT: Be careful while assigning Noetix roles that pertain to Oracle Human Resources Management System (HRMS) to Noetix query users of the Database User (Type U) or Noetix System Administration User (Type N) types. These users do not have a security profile associated with their database user accounts, unless they are defined as reporting users in Human Resources for the required security profiles. Therefore, confidential data that is secured in HRMS through security profiles may be exposed through standard or global Noetix views to these query users if they are not also set up as reporting users.

13. Click OK on the Add Users Properties or <Noetix query user> Properties dialog box. You return to the Noetix Query User Maintenance tab of the Security Manager dialog box.

14. (Optional) Configure default flexfield security rules settings for the new Noetix query users to be created or for both the new and existing Noetix query users for the global form of the views. The default flexfield security rules settings can be configured for only the Noetix query users of the Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) types. For information on how to configure default flexfield security rules settings, see Row-level security in the “NoetixViews for Oracle General Ledger” section in “Module-Specific Information”.

15. Click OK on the Security Manager dialog box to save the changes to the database.

NOTE: The Regenerate synonym scripts check box on the Noetix Query User Maintenance tab regenerates the synonym scripts that are used for creating synonyms for Noetix query users of the Database User (Type U) type. By default, this check box is selected. Keep this check box selected if you are working in multiple environments (for example, generating views in a UNIX environment and maintaining query users in a Microsoft Windows environment).


Create a Noetix Query User Using the Add WizardUse the instructions provided in this section to create a Noetix query user using the Define New Noetix Query User Wizard. You can also use this wizard for creating a database user before adding it as a Noetix query user. You can create only database users using the wizard.

To create a Noetix query user:1. Click Start > All Programs > NoetixViews > NoetixViews Administrator. The


2. Log on as the Noetix System Administration User.


3. Click on the NoetixViews Administrator toolbar. Alternatively, on the Tools menu, click Security Manager. The Security Manager dialog box appears. The Noetix Query User Maintenance tab of the Security Manager dialog box displays the names and types of the users who have been added as Noetix query users. By default, you can see the Noetix System Administration User and Oracle Administrative Database User. The dates on which the Noetix query user accounts were created and would expire are indicated. For Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) type users, the start and end dates correspond to the start and end dates of the respective Oracle E-Business Suite users and responsibilities. The Noetix Query User Maintenance tab also indicates whether views are optimized for query tools and synonyms for the views are created for the selected users.


4. On the Noetix Query User Maintenance tab, click Add Wizard. The Define New Noetix Query User Wizard dialog box appears.


5. On the Start page, click Next to start the wizard. The User Creation Options page appears.

6. Do one of the following:

• Click Create New User Account to create a database user, and then add the database user as a Noetix query user. You will need DBA privileges to create this account. Click Next to continue.

• Click Select Existing User Account if the Noetix query user is to be set up for an existing database user, Oracle E-Business Suite user, or Oracle E-Business Suite responsibility. In this case, the user has already been created and needs to be added as a Noetix query user. Click Next, and proceed to step 10 to select the user.


7. If you have clicked the Create New User Account option in the previous step, the DBA Account page appears.

NOTE: The user must exist on the same instance as your Noetix System Administration User account; therefore, the Transparent Network Substrate (TNS) name is already filled in for you.


8. Type the name and password of a user with DBA privileges. The user must exist on the same instance as your Noetix System Administration User account; therefore, the Transparent Network Substrate (TNS) name is already filled in for you. Provide the information, and click Next. The Create User page appears.


9. Provide the user name and password of the database user that you want to create on the Create User page. A dialog box prompts you to confirm the new password. After providing the user name and password, choose a default and temporary tablespace for this database user schema. Click Next. After the database user is successfully created, the User Options page appears. Proceed to step 11.

IMPORTANT: The user name must start with a letter; must not contain double quotation marks (") or single quotation marks ('); cannot exceed 30 bytes. Also, use only uppercase letters (A-Z) for the user name. Diacritical marks and characters for Western European languages can also be typed.

10. If you have clicked the Select Existing User Account option in step 6, the Choose Users or Responsibilities page appears. This page allows you to select a user type and select existing users corresponding to the user type that should be added as Noetix query users.


To select a user type and users corresponding to the selected user type, follow these steps:

a. In the User Type list, click a user type. The options available are Database User, Oracle E-Business Suite Authenticated User, and Oracle E-Business Suite Authenticated Responsibility.

b. Click Add. If the user type selected is Database User (Type U) or Oracle E-Business Suite Authenticated User (Type A), the Add Users dialog box appears. If the user type selected is Oracle E-Business Suite Authenticated Responsibility (Type R), the Add Responsibilities dialog box appears.

NOTE: For Oracle E-Business Suite Authenticated User (Type A) type users, the list of users displays only those users who have one or more responsibilities assigned to them in Oracle E-Business Suite.

c. (Optional) In the Add Users or Add Responsibilities dialog box, use the % or _ wild card characters in the Name filter box to filter the user names.

d. (Optional) If the user type selected is Oracle E-Business Suite Authenticated User (Type A), in the Responsibility filter list, select a responsibility name to filter the users based on their Oracle E-Business Suite responsibility.

e. From the User Name or Responsibility Name list, select the required user names or responsibilities by selecting the corresponding check boxes. If you want to select all user names or responsibilities, click Select All. If you want to clear the selection of users, click Deselect All. The number of users or responsibilities selected is displayed at the bottom of the dialog box.

IMPORTANT: If the names of database users selected for adding as Noetix query users contain lower-case or mixed-case letters and special characters that are not supported by Oracle Database, the names should be provided within double quotation marks when the corresponding users log on to Oracle Discoverer Desktop.


Click Next. The User Options page appears.


11. The User Options page allows you to specify the following settings:

• In the Language list, click the language used by NoetixViews. If you select <Default Noetix Language Processing>, the language associated with the current environment will be set as the default language for this Noetix query user. If that language is not defined in Oracle E-Business Suite, the language that was chosen during Stage 4 of the generation process will be set as the default language.

• Select the Create Query Tool Optimizing Views check box, which is available only for Database User (Type U) type users. Selecting this check box at the time of creating a Database User type user enhances the performance of reporting tools (for example, Noetix Platform, Microsoft Access, or Crystal Reports) that query directly from the database rather than their own meta-layers.

NOTE: Reporting tools (for example, Oracle Discoverer’s End User Layer (EUL), SAP BusinessObjects’ Universe, or IBM Cognos' Catalog) that access their own meta-layers do not benefit from this option. Therefore, do not select this check box while using any reporting tool that accesses its own meta-layer.

• Select the Create Synonyms check box to create synonyms for views that are granted to Database User (Type U) type users. This option creates synonyms for each role granted to the Noetix query users. The Create Synonyms check box is available only for Database User (Type U) type users and it is selected by default. Clear this check box if the synonyms are not to be created. However, it is recommended to keep this check box always selected.

NOTE: Do not select the Create Query Tool Optimizing Views and Create Synonyms check boxes if the Noetix query users of the Database User type also own Oracle E-Business Suite tables. If you do so, you may encounter problems while assigning Noetix roles to the users.


Click Next. The Choose Security Pages page appears.


12. The Choose Security Pages page allows you to define custom security settings to the selected users or responsibilities who are to be added as Noetix query users. The following settings are available in this page:

• Click Accept the default settings and go to the Roles page if you want to apply the default custom security settings to the selected users or responsibilities and go to the Roles page.

• Click Choose pages to view if you want to define the custom security settings for the selected users and responsibilities. After selecting this option, in the list, select the check boxes corresponding to the custom security configuration pages that you want to display in the wizard. The list also displays the default security that is configured for each custom security page based on the query user type corresponding to the selected users or responsibilities. The default options available are Business Group, Inventory Organization, Ledger, Operating Unit, Service Request, and Security Rules. The options displayed will vary depending on the NoetixViews modules available in your NoetixViews configuration.

Click Next. If the first option is selected, the Roles page appears. If the second option is selected, the pages appear in the wizard according to the check boxes selected. For more information about how to define security settings for users or responsibilities, see steps 6 through 11 in “Add a Noetix Query User Using an Existing User.”

13. When the Roles page appears, assign the required roles to the selected users or responsibilities. For more information about assigning roles, see step 12 in “Add a Noetix Query User Using an Existing User.”

Click Next. The Finish page appears.

14. Click Finish. You return to the Noetix Query User Maintenance tab. The Noetix query user accounts created corresponding to the selected users or responsibilities are displayed in the Noetix Query Users list.


15. (Optional) Configure default flexfield security rules settings for the new Noetix query users to be created or for both the new and existing Noetix query users for the global form of the views. The default flexfield security rules settings can be configured for only the Noetix query users of the Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) types. For information on how to configure default flexfield security rules settings, see Row-level security in the “NoetixViews for Oracle General Ledger” section in “Module-Specific Information”.


NOTE: The Regenerate synonym scripts check box on the Noetix Query User Maintenance tab of the Security Manager dialog box allows you to regenerate the synonym scripts that are used for creating synonyms for Noetix query users of the Database User (Type U) type. By default, this check box is selected. Keep this check box selected if you are working in multiple environments (for example, generating views in a UNIX environment and maintaining query users in a Microsoft Windows environment).


Create Noetix Query Users Using Scripts

The scripts-based method of creating Noetix query users allows you to add multiple Noetix query users at the same time. You can add existing database users and Oracle E-Business Suite users and responsibilities as Noetix query users of Database User (Type U), Oracle E-Business Suite Authenticated User (Type A), and Oracle E-Business Suite Authenticated Responsibility (Type R) types.

Using scripts, you can also create database users in the Oracle database and later add the users as Noetix query users of Database User (Type U) type.

IMPORTANT: The scripts-based method does not allow you to set a translation language, assign security rules for data in views for Oracle General Ledger, and customize security for data in views for various Oracle E-Business Suite modules. To work with these features, use the Noetix Query User Maintenance tab of the Security Manager dialog box.

Add Existing Users as Noetix Query UsersThe i_create_sm_users.sql script available in NoetixViews for Oracle E-Business Suite (NoetixViews) allows you to create multiple Noetix query users based on existing database users and Oracle E-Business Suite users and responsibilities. These query users can be categorized into Database User (Type U), Oracle E-Business Suite Authenticated User (Type A), and Oracle E-Business Suite Authenticated Responsibility (Type R) types. The i_create_sm_users.sql script cannot be used to create Noetix query users of the Oracle E-Business Suite Authenticated User (Type A) type who have no responsibility assigned to them in Oracle E-Business Suite.

Some features of the i_create_sm_users.sql script include:

• Support for adding multiple users by using wild card characters.

• Support for assigning multiple roles by using wild card characters.


• Support for assigning up to 30 role labels or role names to the selected users.

NOTE: For users of the Database User (Type U) type, only role names can be assigned.

• Support for adding one or more users of the Oracle E-Business Suite Authenticated User (Type A) type corresponding to a specific Oracle E-Business Suite responsibility.

• Support for selecting only active users. This feature is available for only users of the Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) types.

• Support for automatically detecting only those roles based on the organizational unit settings available in Oracle E-Business Suite for a selected user. This feature is available for only users of the Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) types.

The following procedure explains how to use the i_create_sm_users.sql script to create multiple Noetix query users based on existing users.

To add users or responsibilities as Noetix query users:1. Depending on the operating system, do one of the following to start an SQL*Plus

session:

• On a Windows-based computer:

a. Log on to NoetixViews Administrator.

b. On the Tools menu, click Support > SQL*Plus Prompt from the NoetixViews Administrator main window. The Oracle SQL*Plus window appears.

• On a UNIX-based computer:

a. Change the present working directory to the server directory that contains the NoetixViews generation scripts.


b. To connect to the database as the Noetix System Administration User and to start an SQL*Plus session, run the following command at the command prompt. sqlplus <username>/<password>@<dbconnectstring>

2. In the SQL*Plus session, run the i_create_sm_users.sql script. Answer the following prompts. To accept the default value, press ENTER; otherwise, type a value for each prompt, and press ENTER.

a. Please enter the type of query users you would like to create. Valid values are A (EBS Authenticated User), R (EBS Authenticated Responsibility), or U (Database User). default [A]: Type U to specify the type of user as database user, type A to specify the type of user as Oracle E-Business Suite user, and type R to specify the type of user as Oracle E-Business Suite responsibility. If you have typed U or R, go to step c.

b. If you have typed A in the previous step, answer the following prompt:

For an EBS Authenticated User (Type A), you can enter an EBS responsibility here. If you enter a responsibility name, the list of users will be derived from the users assigned to the responsibility specified. To derive the user list from the specified responsibility, enter its name here. You may use wildcard characters to specify multiple responsibilities. NOTE: If you specify "%" here, then the responsibility user list will not be used. *** Use the wildcard characters "_" or "%" to specify multiple responsibilities. *** default [%]:


c. Please enter the name of the database user you would like to create. *** Use the wildcard characters "_" or "%" to create multiple users. *** default [%]:

NOTE: Depending on the type of the user specified to be added in step a, this prompt displays database user, EBS Authenticated User (Type A), or EBS Authenticated Responsibility (Type R) user.

IMPORTANT: For Database User (Type U) type user, ensure that the user name is provided exactly as it appears in the Oracle database. For Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) type users, ensure that the user name is provided exactly as it appears in Oracle E-Business Suite. Also, the i_create_sm_users.sql script cannot be used to create Noetix query users of the Oracle E-Business Suite Authenticated User (Type A) type who have no responsibility assigned to them in Oracle E-Business Suite.

d. Include only active users (those that have not been end dated.) Valid values are "Y" to include only active users or "N" to include all defined users. default [Y]:

NOTE: This prompt is available for only the Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) type selected users. Depending on the type of the user specified to be added in step a, this prompt asks to provide value for active users or active responsibilities.

e. For type "A" users, the default role assignment is handled automatically based on the organizational unit access that is detected for a particular user. In this mode, you are prompted to enter a set of role labels (templates). Based on your role label selections, a list of roles is generated for each user account as determined by each user's detected organizational unit access. The other mode of operation is to explicitly grant a list roles to the specified user accounts, regardless of their organizational unit access. Valid values are "Y" to specify roles automatically based on role label and organizational unit settings or "N" to specify an explicit list of roles. default [Y]:


NOTE: This prompt is available for only the Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) type selected users. Depending on the type of the user specified to be added in step a, this prompt asks to provide value for type A or type R users.

f. What default mode of access for row-level security would you like? For type "A" and "R" users, specify "ALL", "EBS", or "NONE". For type "U" users, specify "ALL" or "NONE". If the row-level security is not available, then the "EBS" access mode will be automatically changed to "NONE". default [NONE]:

NOTE: If row-level security is available, the default value is “EBS” for Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) type users.

g. What default mode of access for GL security would you like? For type "A" and "R" users, specify "ALL", "EBS", or "NONE". For type "U" users, specify "ALL" or "NONE". If the GL security is not available, the value specified is populated in the security manager, but is not used. default [NONE]:

NOTE: If row-level security is available, the default value is “EBS” for Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) type users.

h. Create query tool optimizing views? This parameter is ignored if a user type other than "U" is specified. default [N]:

NOTE: Do not type Y if the Noetix query user owns Oracle E-Business Suite tables. If you do so, you may encounter problems while assigning Noetix roles to the user. Also, do not type Y if the Noetix query users use any reporting tool, such as Oracle Discoverer, that accesses its own meta-layer because they do not benefit from this option.


i. Create query user synonyms for views? This parameter is ignored if a user type other than "U" is specified. default [N]:

NOTE: Do not create synonyms if the Noetix query users own Oracle E-Business Suite tables. If you do so, you may encounter problems while assigning Noetix roles to the users.

3. Press ENTER, when prompted, to see a list of role names or role labels. The list of available role names or role labels is displayed. This will allow you to assign a role or a set of roles to the specified users. Every time you run the script, the script provides you an option to assign a maximum of 30 role labels or role names for the selected users.

NOTE: For Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) type users, by default, you will be prompted to view a list of role labels unless you have typed the value N in step e. If the list is long, you will be prompted to press ENTER more than once to see all the role names or labels.

4. To assign a single role name or role label, type the role name or role label, and press ENTER. To skip a role name or role label prompt, press ENTER. When you assign a role label corresponding to an Oracle module to an Oracle E-Business Suite Authenticated User (Type A) or Oracle E-Business Suite Authenticated Responsibility (Type R) type user for whom EBS access mode is specified, the roles corresponding to the role label are automatically assigned based on the user’s organizational unit access configured in Oracle E-Business Suite. If you assign role names instead of role labels for these user types, the roles are first verified against the corresponding organizational units and only those role names for which the user has organizational unit access are included.

NOTE: Use the percent character to select all Noetix role names or role labels that start with a prefix. For example, to select all the role names that start with GL, use GL% and to select all the role labels that start with HR, use HR%.

5. Verify the information that you entered.

6. Press ENTER, when prompted, to see the list of Noetix query users selected.

7. Press ENTER, when prompted, to see the list of role labels or role names assigned to the specified users.


NOTE: After this step, the t_create_sm_users.sql script will be automatically generated that contains all the settings defined for the users or responsibilities.

8. Verify that all the information that you entered is correct. If the information is incorrect and you want to re-run the script or you want to edit the t_create_sm_users.sql script and run it manually, exit the SQL*Plus session (usually by pressing CTRL+C). If the information is correct and you want to proceed, press ENTER.

9. Repeat steps 2 through 8 if you want to add more users or responsibilities as Noetix query users.


Create a Database UserThis procedure allows you to create a database user in the Oracle database that you can add later as a Noetix query user of Database User (Type U) type.

To create database users:1. Depending on the operating system that you use, do one of the following to start

an SQL*Plus session:

• On a Windows-based computer, do the following:

a. Log on to NoetixViews Administrator.

b. On the Tools menu, click Support > SQL*Plus Prompt from the NoetixViews Administrator main window. The Oracle SQL*Plus window appears.

• On a UNIX-based computer, do the following:

a. Change the present working directory to the server directory that contains the NoetixViews generation scripts.

b. On the Tools menu, click Support > SQL*Plus Prompt from the NoetixViews Administrator main window. The Oracle SQL*Plus window appears. sqlplus <username>/<password>@<dbconnectstring>

2. On the SQL*Plus session, run the instuser.sql. Answer the following prompts. To accept the default value, press ENTER; otherwise, type a value for each item when prompted, and press ENTER.

• Please enter the Oracle User Name for the NoetixViews Query User

IMPORTANT: The user name must start with a letter; must not contain double quotation marks (") or single quotation marks ('); cannot exceed 30 bytes. Also, use only uppercase letters (A-Z) for the user name. Diacritical marks and characters for Western European languages can also be typed.

• Please enter the Oracle User Password for the NoetixViews Query User


• Please enter the Database Connect string

• Please enter the Default Tablespace to create Noetix objects in

• Please enter the Temporary Tablespace to assign the Noetix query user

3. Verify the information that you have entered. If the information is incorrect, exit the SQL*Plus session (usually by pressing CTRL+C), and start over. If the information is correct, press ENTER to continue.

4. Repeat these steps for each user that you want to create.


Modify Noetix Query UsersModifying query users involves adding or deleting features, adding or deleting roles of NoetixViews for Oracle E-Business Suite (NoetixViews), and changing access to data in views for various Oracle E-Business Suite modules.

NOTE: For modifying users, you need to use the Noetix Query User Maintenance tab of the Security Manager dialog box. However, you can partially modify Database User (Type U) type users by running the idelqusr.sql script. This script allows you to delete already assigned roles from the Noetix query user account. For more information, see To delete a Noetix query user using scripts in “Delete Noetix Query Users.”


To modify the general properties of an existing Noetix query user:1. On the Noetix Query User Maintenance tab of the Security Manager dialog box

of the NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator), select a Noetix query user, and click Edit. The <Noetix query user> Properties dialog box appears.

2. On the General tab of the <Noetix query user> Properties dialog box, you can change the language code for the query user. If the user is a Database User (Type U) type user, you can select or clear the selection for creating query tool optimizing views or synonyms. However, you cannot change the user type and user name.

For information about various options on the General tab, see step 5 in “Add a Noetix Query User Using an Existing User.”

3. Click OK on the <Noetix query user> Properties dialog box. You return to the Noetix Query User Maintenance tab.

4. After you have finished changing the general properties of all the required Noetix query users, click OK to commit the changes to the database.

To modify access to data in HRMS for a Noetix query user:1. Click the Business Group tab on the <Noetix query user> Properties dialog box to

modify the Noetix query user’s access to data in the Noetix views for Oracle Advanced Benefits, Oracle Human Resources, Oracle Payroll, and Oracle Time and Labor. The tab will display the business groups currently assigned to the Noetix query user for each Oracle application.

For information about the Business Group tab, see step 6 in “Add a Noetix Query User Using an Existing User.”


3. Click OK to commit the changes to the database.


To modify query user’s access to data based on ledgers:1. Click the Ledger tab on the <Noetix query user> Properties dialog box to modify

the Noetix query user’s access to data in the Noetix views for Oracle Assets, Oracle General Ledger, and Oracle U.S. Federal Financials. The tab will display the ledgers currently assigned to the Noetix query users for each Oracle application.

For information about the Ledger tab, see step 7 in “Add a Noetix Query User Using an Existing User.”



To modify the Noetix query user’s access to data based on operating units:1. Click the Operating Unit tab on the <Noetix query user> Properties dialog box to

modify the Noetix query user’s access to data in the Noetix views for Assets, General Ledger, and U.S. Federal Financials. The tab will display the operating units currently assigned to the Noetix query user for each Oracle application.

For information about the Operating Unit tab, see step 8 in “Add a Noetix Query User Using an Existing User.”




To modify the Noetix query user’s access to data based on inventory organizations:1. Click the Inventory Organization tab on the <Noetix query user> Properties

dialog box to modify the Noetix query user’s access to data in the Noetix views for Bills of Material, Cost Management, Enterprise Asset Management, Inventory, Master Scheduling/MRP, Quality, and Work in Process. The tab will display the inventory organizations currently assigned to the Noetix query user for each Oracle application.

For information about the Inventory Organization tab, see step 9 in “Add a Noetix Query User Using an Existing User.”



To modify the Noetix query user’s access to data based on service request types:1. Click the Service Request tab on the <Noetix query user> Properties dialog box to

modify the Noetix query user’s access to data in the Noetix views for Deport Repair, Field Service, and TeleService. The tab will display the service request types currently assigned to the Noetix query user for each Oracle application.

For information about the Service Request tab, see step 10 in “Add a Noetix Query User Using an Existing User.”




To modify access to accounting data for a Noetix query user:1. Click the Security Rules tab on the <Noetix query user> Properties dialog box to

modify the Noetix query user's access to accounting data in Noetix views based on the flexfield security rules. The tab will display the flexfield security rules setting currently assigned to the Noetix query user.

For information about the Security Rules tab, see step 11 in “Add a Noetix Query User Using an Existing User.”




To add or delete roles for an existing Noetix query user:1. Click the Roles tab on the <Noetix query user> Properties dialog box to modify

the roles assigned to the Noetix query user. The tab will display the Noetix roles currently assigned to the Noetix query user.

For information about adding or deleting roles on the Roles tab, see step 12 in “Add a Noetix Query User Using an Existing User.”


3. When you have finished adding or deleting roles for all the required Noetix query users, click OK to commit the changes to the database.

Modify Default Flexfield Security RulesFor the Noetix query users of the Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) types, the default flexfield security rules setting assigned can be modified. For information on how to modify the default flexfield security rules setting, see Row-level security in the “NoetixViews for Oracle General Ledger” section in “Module-Specific Information.”


Delete Noetix Query UsersA Noetix query user account can be deleted with the use of the Noetix Query User Maintenance tab of the Security Manager dialog box or scripts.

IMPORTANT: Using the Noetix Query User Maintenance tab, you can delete only Noetix query users of the Oracle E-Business Suite Authenticated User (Type A), Oracle E-Business Suite Authenticated Responsibility (Type R), and Database User (Type U) types. Using scripts, you can delete only Noetix query users of the Database User (Type U) type. To delete the database users that are associated with Noetix query users, you need to log on to the database as a user with DBA privileges.

If you are using Oracle Discoverer, you will need to use Noetix Generator for Oracle Discoverer (Noetix Generator) to update security in your End User Layer (EUL). For more information about updating security, see the Noetix Generator for Oracle Discoverer Administrator Guide. You must select the Remove Business Area Security on Non-NoetixViews Query Users check box; otherwise, the deleted query user will still have access to the EUL.

You must be granted the SELECT ANY TABLE privilege to delete a query user.


To delete a Noetix query user using NoetixViews Administrator:1. On the Noetix Query User Maintenance tab, select a Noetix query user. To select

multiple Noetix query users, press CTRL, and click the users.

2. Click Remove. A message appears to confirm the same. Click Yes.

NOTE: When you select the Noetix System Administration User (Type N) or an Oracle Administrative Database User (Type O), that is, the database logon accounts that are automatically created, the Remove button is unavailable.

3. Click OK to commit the changes. Noetix query user accounts will only be removed if you click OK to commit the changes to the database.

The user record will be removed, and the query user will no longer have access to Noetix views.


To delete a Noetix query user using scripts:1. Change the present working directory to the server directory containing the

NoetixViews generation scripts.

2. Using SQL*Plus, connect to the database as the Noetix System Administration User: connect <username>/<password>@<dbconnectstring>

3. Run the delete user script, idelqusr.sql: start idelqusr.sql

4. Answer the following prompts. To accept the default value, press ENTER; otherwise, type a value for each item when prompted, and press ENTER.

• Please enter the Query User name.

NOTE: Type the name of the Database User (Type U) type user.

• Remove this Query User from NoetixViews? (Selecting this option will remove all roles and created synonyms.)

Type "Y" to delete the user. Type "N" to remove roles from the user. If you type "N," you will be prompted to select roles for removal. Press ENTER to see all the roles assigned to this Noetix query user. If you want to delete a single role, type its name. If you want to delete all roles, type %.

5. Verify the information that you have typed. If the information is incorrect, exit the SQL*Plus session (usually by pressing CTRL+C), and start over. If the information is correct, press ENTER to continue.


• Do you want to remove additional query users or query user roles? Type “Y” to remove additional query users or roles. Otherwise, type “N”. If you typed "Y," repeat steps 4 and 5. If you typed "N," all the Noetix query users or roles to be deleted are listed.

7. Verify the information. To confirm, press ENTER. To cancel, exit the SQL*Plus session by pressing CTRL+C.


If you have deleted roles from a query user record, then the user will no longer have access to the views pertaining to the removed roles. If you have deleted the user, the user record will be removed, and the query user will no longer have access to Noetix views.

Data Security in NoetixViewsThe data security model provided in NoetixViews has the following components:

• User authentication: This is the validation of the credentials provided by the user while logging on to business intelligence (BI) tools. The credentials consist of a username and password, and at times, selecting an Oracle E-Business Suite responsibility.

• View and answer authorization: The privileges of a user to query a Noetix view or run a Noetix answer. Users obtain these privileges by being granted a Noetix role or an access to a folder that contains the views or answers in the BI tools. For information, see View and Answer Authorization.

• Data access privilege: The privilege of a user to access specific data or rows from a Noetix view. This is determined by the settings of the Noetix query user that is associated with the user querying the data from the views in the BI tool. For information, see Row-level security.

View and Answer AuthorizationFor querying a view or running an answer in the business intelligence (BI) tool, users need to be assigned the required privileges. For assigning these privileges, the following are done:

• For each BI tool user, a corresponding Noetix query user is created. The query user is assigned a Noetix role through the Security Manager dialog box. The role assigned to the query user allows the user to access a set of views corresponding to the role in the BI tool.

• The BI tool user is granted access to a folder, business area, group, or role that contains the views or answers in the BI tools. After these privileges are granted, the users can access all the respective views or answers.


Noetix Generators automatically configure access to views and answers in the BI tool for a BI tool user based on the Noetix roles assigned to the associated Noetix query user. In some BI tools where the Noetix Generators do not configure access to views and answers automatically for a BI tool user, the administrator of the BI tool has to manually grant the required permissions to the BI tool user.

Noetix Generators, BI Tools, and Noetix Query UsersOracle Discover and Noetix WebQuery (NWQ) use Noetix query users’ settings to manage access to views and answers. The setup required for the Noetix query user to access the views or answers in the BI tool is done by the Noetix Generator for the respective BI tools. Oracle Business Intelligence (Oracle BI), IBM Cognos Business Intelligence (Cognos BI), and SAP BusinessObjects do not use the Noetix query users’ settings to manage access to views and answers. In these tools, the BI tool administrator decides the BI tool user’s access to views and answers. However, in these BI tools, to apply row-level security for a BI tool user, the BI tool user needs to be associated with a Noetix query user. For more information about row-level security, see Row-level security.

This section explains how to set up a Noetix query user's access to views and answers in the following BI tools. The discussion pertains to Noetix query users of Database User (Type U), Oracle E-Business Suite Authenticated User (Type A), or Oracle E-Business Suite Authenticated Responsibility (Type R) type, except where it is specifically mentioned to include other types of Noetix query users.

Noetix WebQueryThe following steps need to be performed while setting up users’ access to views and answers in Noetix WebQuery (NWQ):

1. Using the Security Manager dialog box, add Noetix query users of Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Responsibility (Type R) types for the Oracle E-Business Suite users and responsibilities, and assign roles to them. You can also add database users as Database User (Type U) type users. The roles assigned to the Database User (Type U) type users are automatically assigned to the respective database users in the Oracle database. For information about creating query users and assigning roles, see Row-level security and Row-level security.


2. Run Noetix Generator for Noetix Platform—Oracle E-Business Suite Edition (Noetix Generator). Noetix Generator creates folders in NWQ for containing the views and answers that correspond to Noetix roles. It also creates NWQ users for each Database User (Type U) and Oracle E-Business Suite Authenticated User (Type A) type users. A user is also set up for each Oracle E-Business Suite user assigned to the responsibility of the Oracle E-Business Suite Authenticated Responsibility (Type R) type users. Noetix Generator grants NWQ users those answer folders in NWQ that correspond to the roles assigned to the query user. However, Noetix Generator does not grant the users access to the NWQ folders containing views. This step is performed by the Noetix Platform administrator.

Oracle DiscovererThe following steps need to be performed while setting up users’ access to views in Oracle Discoverer. Noetix answers are not generated into Discoverer.

1. Using the Security Manager dialog box, add Noetix query users of Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Responsibility (Type R) types for the Oracle E-Business Suite users and responsibilities, and assign roles to them. You can also add database users as Database User (Type U) type users. The roles assigned to the Database User (Type U) type users are automatically assigned to the respective database users in the Oracle database. For information about creating query users and assigning roles, see Row-level security and Row-level security.

2. Run Noetix Generator for Oracle Discoverer (Noetix Generator). Noetix Generator creates business areas for each extracted Noetix role. The folders in each business area correspond to the views of that role. Noetix Generator also automatically configures each user’s access to the business areas. For Applications Mode End User Layers (EULs), Noetix Generator maps Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) type users to their corresponding Oracle E-Business Suite user or responsibility. They are also granted access to the business areas in the EULs based on the roles assigned to the corresponding Noetix query users. For standard EULs, Noetix Generator maps the Database User (Type U) type users to their corresponding database user in the Oracle Database and grants them the business areas that correspond to the roles assigned to the query user.


Oracle Business IntelligenceThe following steps need to be performed while setting up users’ access to views and answers in Oracle Business Intelligence (Oracle BI):

1. Using the Security Manager dialog box, add Noetix query users of Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Responsibility (Type R) types for the Oracle E-Business Suite users and responsibilities, and assign roles to them. You can also add database users as Database User (Type U) type users. The roles assigned to the Database User (Type U) type users are automatically assigned to the respective database users and they gather access to the views in the Oracle database. For information about creating query users and assigning roles, see Row-level security and Row-level security. For information about how Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) type users gain access to views and answers in Oracle BI, see Row-level security.

2. Run Noetix Generator for Oracle Business Intelligence (Noetix Generator). Noetix Generator configures the Oracle BI metadata repository with subject areas containing folders, which hold Noetix views and answers. For each folder, Noetix Generator creates a user group. The Oracle BI administrator makes each Oracle BI user a member of these groups. This allows them to access the views and answers in the respective folders.

IBM Cognos Business IntelligenceThe following steps need to be performed while setting up users’ access to views and answers in IBM Cognos Business Intelligence (Cognos BI):

1. Using the Security Manager dialog box, add Noetix query users of Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Responsibility (Type R) types for the Oracle E-Business Suite users and responsibilities, and assign roles to them. You can also add database users as Database User (Type U) type users. The roles assigned to the Database User (Type U) type users are automatically assigned to the respective database users and they gather access to the views in the Oracle database. For information about creating query users and assigning roles, see Row-level security and Row-level security. For information about how Oracle E-Business Suite Authenticated User (Type A)


and Oracle E-Business Suite Authenticated Responsibility (Type R) type users gain access to views and answers in Cognos BI, see Row-level security.

2. Run Noetix Generator for IBM Cognos BI (Noetix Generator). Noetix Generator configures the Cognos Framework Manager model with packages containing folders. These folders contain the query subjects that are mapped to the views in the database. Noetix Generator creates folders that contain answers. It also creates roles that correspond to Noetix roles and are associated with respective folders. The Cognos BI administrator grants these roles to the users that allow them to access the corresponding views and answers.

SAP BusinessObjectsThe following steps need to be performed while setting up users’ access to views and answers in SAP BusinessObjects:

1. Using the Security Manager dialog box, add Noetix query users of Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Responsibility (Type R) types for the Oracle E-Business Suite users and responsibilities, and assign roles to them. You can also add database users as Database User (Type U) type users. The roles assigned to the Database User (Type U) type users are automatically assigned to the respective database users and they gather access to the views in the Oracle database. For information about creating query users and assigning roles, see Row-level security and Row-level security. For information about how Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) type users gain access to views and answers in BusinessObjects, see Row-level security.

2. Run Noetix Generator for SAP BusinessObjects (Noetix Generator). Noetix Generator configures the BusinessObjects Universes with classes and objects that are mapped to the views in the database and generates the answers. It also creates groups that correspond to Noetix roles. The BusinessObjects administrator grants these roles to the users that allow them to access the corresponding views and answers.


Data Access PrivilegeNOTE: In Oracle E-Business Suite Release 12, the concept of set of books has been replaced by ledger. The terms “set of books" and "ledger" refer to the same concept.

Data access privilege imply the privileges of the Noetix query users or BI tool users who are linked to Noetix query users of the Oracle E-Business Suite Authenticated User (Type A) type to access data from Noetix views, such as rows from a Noetix view. In NoetixViews, the rows returned by the Noetix views for a Noetix query user is decided based on the row-level security set for the Noetix query user. When row-level security is applied, the Noetix query user's access to data within Noetix views corresponding to a role can be further restricted.

The row-level security consists of organizational unit security and application-specific security. Row-level security is supported in only global forms of the Noetix views for the following Oracle E-Business Suite modules:

• Oracle Advanced Benefits

• Oracle Assets

• Oracle Bills of Material

• Oracle Cost Management

• Oracle Depot Repair

• Oracle Enterprise Asset Management

• Oracle Field Service

• Oracle General Ledger

• Oracle Human Resources

• Oracle Install Base

• Oracle Inventory

• Oracle Master Scheduling/MRP


• Oracle Order Management

• Oracle Payables

• Oracle Payroll

• Oracle Projects

• Oracle Purchasing

• Oracle Quality

• Oracle Receivables

• Oracle Service Contracts

• Oracle TeleService

• Oracle Time and Labor

• Oracle U.S. Federal Financials

• Oracle Work in Process

NOTE: NoetixViews support only application-specific security for the Noetix views corresponding to Depot Repair, Field Service, and TeleService.

For Noetix query users of the Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) types, the restrictions to access data are applied based on the data access privileges defined in Oracle E-Business Suite. For Noetix query users of the Database User (Type U) type, these restrictions are configured by the Noetix System Administration User (Type N) through NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator). Row-level security is enforced by global views in the database when a Noetix query user queries data from them. Each global view has an access control list (ACL) that defines the organizational units that a Noetix query can access. These organizational units include business groups, ledgers, operating units, and inventory organizations. When a Noetix query user queries data from global views, global views validate the user and ACL information and enforce the row-level security on the user.


Additionally, data security similar to row-level security is supported in standard and XOP forms of Noetix views for General Ledger and U.S. Federal Financials. This type of security is also supported in standard form of Noetix views for Advanced Benefits, Human Resources, Time and Labor, and Payroll.

In Oracle E-Business Suite, an Oracle E-Business Suite user can be assigned multiple General Ledger responsibilities to which security rules are attached and multiple Oracle Human Resource Management System (HRMS) responsibilities to which security profiles are attached. After adding this user as a Noetix query user and assigning the Derived from Oracle EBS security mode in NoetixViews Administrator, when the Noetix query user or a BI tool user who is linked to this Noetix query user queries data from the global form of Noetix views for General Ledger, Advanced Benefits, Human Resources, Time and Labor, and Payroll through a business intelligence (BI) tool, the number of rows returned will be further filtered by the responsibility with which the user logs on.

In BI tools such as NoetixWebQuery (NWQ) and Oracle Discoverer, Noetix query users of the Oracle E-Business Suite Authenticated User (Type A) type can select a General Ledger or HRMS responsibility when they log on to these BI tools. After logging on, if the Noetix query users want to select a different General Ledger or HRMS responsibility, they will have to log off from the current user session, and log on to the BI tool again.

In BI tools such as Oracle Business Intelligence (Oracle BI), SAP BusinessObjects, and IBM Cognos Business Intelligence (Cognos BI), BI tool users log on with the responsibility associated with the Noetix query user of the Oracle E-Business Suite Authenticated User (Type A) type to which they are linked. After logging on, if the BI tool users want to select a different General Ledger or HRMS responsibility, they can run the Noetix Responsibility Tool to change the responsibility. This application allows BI tool users to change their General Ledger or HRMS responsibility without logging off from their current user session.


Organizational Unit SecurityOrganizational unit security is applied to Noetix query users based on their access to organizational units. These organizational units include business groups, ledgers, operating units, and inventory organizations. In the global forms of Noetix views that support row-level security, the organizational unit security is applied by default. Additionally, organizational unit security is supported in standard and XOP forms of Noetix views for U.S. Federal Financials. Organizational unit security can be set up for the following types of Noetix query users:

• Database User (Type U)

• Oracle E-Business Suite Authenticated User (Type A)

• Oracle E-Business Suite Authenticated Responsibility (Type R)

• Noetix System Administration User (Type N)

NoetixViews also provides the functionality to override the organizational unit security defined for the Noetix query users of the Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) types in Oracle E-Business Suite.

NoetixViews supports organizational unit security for the global forms of the Noetix views for the following Oracle E-Business Suite modules:

Oracle E-Business Suite modules Organizational unit

Oracle Advanced Benefits, Oracle Human Resources, Oracle Time and Labor, and Oracle Payroll

Business group

Oracle Assets, Oracle General Ledger, and Oracle U.S. Federal Financials

Ledger

Oracle Install Base, Oracle Order Management, Oracle Payables, Oracle Projects, Oracle Purchasing,Oracle Receivables, and Oracle Service Contracts

Operating unit


Also, for Oracle E-Business Release 12 and later, global form of Noetix views support organizational unit security provided by the Multi-Org Access Control (MOAC) feature for Noetix query users of the Oracle E-Business Authenticated User (Type A) type.

Oracle Bills of Materials, Oracle Cost Management, Oracle Enterprise Asset Management, Oracle Inventory, Oracle Master Scheduling/MRP, Oracle Quality, and Oracle Work in Process

Inventory organization

Oracle E-Business Suite modules Organizational unit


Application-Specific SecurityApplication-specific security is applied over the existing organizational unit based security applied to Noetix query users. The application-specific security restricts their access to data in Noetix views based on security rules, security profiles, and budget access levels. NoetixViews supports application-specific security in global Noetix views for the following Oracle E-Business Suite modules:

Application-specific security is also supported in standard and XOP forms of views for U.S. Federal Financials and General Ledger and in standard form of views for Human Resources, Advanced Benefits, Payroll, and Time and Labor. By default, for the standard views of Human Resources, Advanced Benefits, Payroll, and Time and Labor, application-specific security is defined in Oracle E-Business Suite and cannot be modified through NoetixViews Administrator.

Application-specific security that is applied based on security rules and budget access levels can be set up for the following Noetix query users:

• Database User (Type U)



• Noetix System Administration User (Type N)

Oracle E-Business Suite modules Application-specific security based on

Oracle Advanced Benefits, Oracle Human Resources, Oracle Time and Labor, and Oracle Payroll

Security profiles

Oracle General Ledger Security rules for the Accounting key flexfield

Oracle U.S. Federal Financials Budget access levels

Oracle Depot Repair,Oracle Field Service,and Oracle TeleService

Service request types


Application-specific security that is applied based on security profiles can be set up for the following Noetix query users:



NOTE: For Noetix query users of the Database User (Type U) and Noetix System Administration User (Type N) types, the security profiles will apply only if the Noetix query users are also defined in Human Resources as reporting users for the security profiles.

NoetixViews also provides the functionality to override the application-specific security defined for the Noetix query users of the Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) types in Oracle E-Business Suite.

Refresh Security for Query Users

The data access privileges of Noetix query users are determined by a security data cache. The settings in the security data cache determine the organizational units for the views modules that query users can access. In the case of Noetix query users of the Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) types, the security data cache stores information about the access of the corresponding Oracle E-Business Suite users and responsibilities to organizational units in Oracle E-Business Suite. However, the default settings can be overridden by the privileges specified in the Noetix Query User Maintenance tab of the Security Manager dialog box.

The security data cache is initially loaded during Stage 4 of the views generation process and thereafter refreshed during each regeneration. The security data cache can also be refreshed to reflect the latest settings in Oracle E-Business Suite through the use

of the Refresh Security icon ( ) on the toolbar of the NoetixViews Administrator or a scheduled Concurrent Manager job. After Stage 4 of the generation process is completed, this Concurrent Manager job is automatically created for refreshing the security in the views. A default schedule for the job is also set up.


To change this schedule, log on to Oracle E-Business Suite as the XXNAO user, who is automatically created by NoetixViews and has access to all the NOETIX_SYS schemas in the Oracle database. You can then view or modify update requests for any NOETIX_SYS schema.

The following list provides information about the support for security data cache in NoetixViews:

• For all the global form of Noetix views except for the global views for Oracle Advanced Supply Chain Planning, Oracle Grants, Oracle Process Manufacturing, and Oracle Project Manufacturing, the security data cache stores the organizational unit and application-specific security settings and provides the functionality to refresh these security settings.

• For standard and Cross Operations Extension (XOP) forms of views for Oracle U.S. Federal Financials, the security data cache stores security settings similar to row-level security and provides the functionality to refresh the organizational unit and application-specific security settings.

• For standard views for Oracle Advanced Benefits, Oracle Human Resources, Oracle Payroll, and Oracle Time and Labor, the security data cache stores the application-specific security settings after the generation of views. Any changes made subsequently in Oracle E-Business Suite will be reflected in these views only after they are regenerated.

• With respect to General Ledger and other modules, for all forms of the views that support the Accounting Flexfield, the security data cache stores the application-specific security settings and provides the functionality to refresh these settings.


Provide Row-Level Security in BI Tools

Row-level security provides the ability to restrict Noetix query user's access to data in global Noetix views. For the Noetix query users of the Oracle E-Business Suite Authenticated User (Type A) type, row-level security is automatically configured based on their data access privileges in Oracle E-Business Suite. For Noetix query users of the Database User (Type U) type, row-level security is configured manually by the Noetix System Administration User in NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator). After you define the row-level security for Noetix query users in NoetixViews Administrator, you can generate the Noetix query users and their row-level security settings into the meta-layers of Oracle Discoverer and Noetix WebQuery (NWQ) by using the Noetix Generator application for the respective business intelligence (BI) tools. When Noetix query users generated in these BI tools log on to these BI tools and query data from global views, global views validate the user information and data access privileges of the user to enforce row-level security.

However, BI tools, such as Oracle Business Intelligence (Oracle BI), SAP BusinessObjects, and IBM Cognos Business Intelligence (Cognos BI), do not support row-level security settings defined for Noetix query users because you cannot generate the Noetix query users and their row-level security settings into the meta-layers of these BI tools. To support row-level security in these BI tools, you must register a BI tool user used in Oracle BI, BusinessObjects, and Cognos BI, and link the user to a Noetix query user of the Oracle E-Business Suite Authenticated User (Type A) type.

Linking a BI tool user to an existing Oracle E-Business Suite Authenticated User who has been added as a Noetix query user in NoetixViews Administrator is a two step process. First, you have to create a BI tool for Oracle BI, BusinessObjects, or Cognos BI. After creating a BI tool, you must select a BI tool user available in the BI tool that you created and link that user to the Oracle E-Business Suite Authenticated User. For this Oracle E-Business Suite Authenticated User, you must also select an appropriate responsibility.

The BI Tool User Registration tab of the Security Manager dialog box in NoetixViews Administrator allows you to create a BI tool and link an Oracle E-Business Suite Authenticated User to a BI tool user used in Oracle BI, BusinessObjects, or Cognos BI.


Manage BI ToolsBefore you register a BI tool user, you need to add BI tools using the Manage BI Tools dialog box. You can also use this dialog box to modify the settings of BI tools or to remove BI tools. This topic explains how to add, modify, and remove BI tools.

To add BI tools:

1. On the Tools menu, click Security Manager. Alternatively, click on the toolbar. The Security Manager dialog box appears.

2. Click the BI Tool User Registration tab.

3. Click Manage BI Tools. The Manage BI Tools dialog box appears.

The BI Tools list in the Manage BI Tools dialog box displays the list of available BI tools. The following columns are available in this list:

• Friendly Name: Indicates the name specified for the BI tool.

• Type: Indicates the BI tool type.


• BI Tool URL: Indicates the URL of the server where the BI tool services are running.

• LDAP Directory: Indicates the Lightweight Directory Access Protocol (LDAP) directory name or IP address.

NOTE: You need to scroll to the right to see all the information in a row. The width of columns in the list can be adjusted to see more if required. Select the line between columns in the header, and drag it to the required position. Also, you can click a column title to sort the BI tools by the entity represented by the column.

4. In the Manage BI Tools dialog box, click Add. The Add BI Tool dialog box appears.

5. Do the following:


a. In the Friendly Name box, enter a name for the BI tool. This name is used during the BI tool user registration process.

b. In the Product Name list, click the BI tool. The values are BusinessObjects, Cognos, and Oracle Business Intelligence.

c. In the BI Tool URL box, enter the URL of the server where the BI tool services are running. The label of this box changes to Server Name when the selected BI tool in the Product Name list is BusinessObjects. For BusinessObjects, you can enter a port number in this box.

Additionally, you may select the Validate LDAP directory users check box if the BI tool uses LDAP directory for user authentication. After you select this check box, do the following:

NOTE: To validate user or browse the LDAP directory, the Noetix System Administration User must be a member of the LDAP directory and should have logged on to Windows using domain credentials. If validation process for the LDAP directory name or IP address specified is not successful, the Noetix System Administration User can override the validation process when registering a BI tool user used in the BI tool for which the LDAP directory validation is performed. LDAP directory validation may fail even after providing the correct value in the event of a temporary network connectivity issue. In this event, the Noetix System Administration User should verify with the network administrator that the value specified for LDAP directory is correct.

a. In the LDAP directory box, enter the name or IP address of the LDAP directory where the users are located. BI tool user names entered in the BI Tool User Registration tab will be validated against directory entered here.

NOTE: You may have to include the port number also if you are not using the default port number for the LDAP directory.

b. In the Search Container box, enter the name of the container within the LDAP directory, or click Browse to select a container.

NOTE: If you do not specify a container and the LDAP directory specified has many users, the validation process may take a long time.

Click OK. You will return to the Manage BI Tools dialog box after the changes are saved. The newly added BI tool is listed in the BI Tools list.

6. Click OK. You will return to the BI Tool User Registration tab.



To modify the settings of BI tools:




4. In the BI Tools list, select the BI tool that you want to edit, and then click Edit. The Edit BI Tool dialog box appears.

5. After you modify the details of the selected BI tool, click OK. You will return to the Manage BI Tools dialog box after the changes are saved.



To remove BI tools:




4. In the BI Tools list, select the check box corresponding to the BI tool that you want to remove, and then click Remove. If the BI tool that you want to remove has registered BI tool users, a dialog box prompts you to confirm whether you want to unregister the users and remove the BI tool. Otherwise, a dialog box prompts you to confirm whether you want to remove the BI tool.

NOTE: You can select more than one BI tool by selecting the corresponding check boxes. Also, you can select the Select/Deselect All check box to select all the BI tools or clear the Select/Deselect All check box to clear the selection of all BI tools.


5. Click Yes. You will return to the Manage BI Tools dialog box after the changes are saved.

NOTE: If you remove a BI tool that has registered BI tool users on the BI Tool User Registration tab, the BI tool users associated with the BI tool will also be removed.



Manage BI Tool UsersAfter you create a BI tool, you can register a user used in the new BI tool and link the user to a Noetix query user of the Oracle E-Business Suite Authenticated User (Type A) type using the BI Tool User Registration tab. If you remove the Noetix query user linked to a registered BI tool user, the BI tool user will become invalid and cannot be used. If you want to continue using the BI tool user, you must link the user to a Noetix query user and assign a responsibility.

This section explains how to register BI tool users, modify the settings of registered BI tool users, and remove registered BI tool users.

To register BI tool users:


2. Click the BI Tool User Registration tab. The Registered BI Tool Users list displays the list of registered BI tool users. You can list the registered BI tool users for a specific BI tool or for all BI tools by selecting All BI Tools or the BI tool from the Filter by BI Tool list. The following columns are available in the list:

• BI Tool User Name: Indicates the name of the registered BI tool user.

• BI Tool: Indicates the BI tool used by the registered BI tool user.

• Oracle EBS Query User: Indicates the name of the Noetix query user linked to the BI tool user.


• Responsibility: Indicates the responsibility associated with the Noetix query user.

• End Date: Indicates the end date for the BI tool user registration.

NOTE: You need to scroll to the right to see all the information in a row. The width of columns in the list can be adjusted to see more if required. Select the line between columns in the header, and drag it to the required position. Also, you can click a column title to sort the BI tools by the entity represented by the column.

3. Click Register. The Register BI Tool User dialog box appears.

4. Do the following:

a. In the User Name box, enter the name of the BI tool user.

b. In the BI Tool list, click the appropriate BI tool for the BI tool user you have specified.

c. In the EBS-Authenticated Query User list, click the Noetix query user whom you want to link to the BI tool user.

d. In the Default Responsibility list, click a responsibility for the Noetix query user you have selected.


e. (Optional.) To specify an end date for the BI tool user registration, click the check box corresponding to the End Date field, then select a date.

NOTE: If you want to add more than one user, select the Register another user check box.

f. Click OK. A message appears stating that the BI tool user registration was successful. If the BI tool user is from a BI tool for which you have specified LDAP validation, the validation is performed when you click OK. If the user cannot be validated, you may choose to add it anyway.

g. Click OK. You will return to the BI Tool User Registration tab after the changes are saved and if the Register another user check box is not selected. The newly registered BI tool user is listed in the Registered BI Tool Users list.



To modify the settings of registered BI tool users:



3. In the Registered BI Tool Users list, select a registered BI tool user, and then click Edit. The Edit Registration dialog box appears. If you remove the Noetix query user of the Oracle E-Business Suite Authenticated User (Type A) type linked to the registered BI tool user, the Oracle EBS Query User and Responsibility columns will be blank.

4. After you modify the details of the selected BI tool user, click OK. You will return to the BI Tool User Registration tab after the changes are saved.


To remove registered BI tool users:



3. In the Registered BI Tool Users list, select the check box corresponding to the BI tool user that you want to remove, and then click Unregister. A dialog box prompts you to confirm whether you want to remove the registered BI tool user.

NOTE: You can select more than one BI tool user by selecting the corresponding check boxes. Also, you can select the Select/Deselect All check box to select all the BI tool users or clear the Select/Deselect All check box to clear the selection of all the BI tool users.

4. Click Yes. You will return to the BI Tool User Registration tab.



Update Reporting Tool or EULYou may need to refresh your query tool when Noetix query users are added, modified, or deleted, or permissions have been changed. Refer to your query tool’s documentation for instructions.

If you are using NoetixViews for Oracle E-Business Suite (NoetixViews) with Oracle Discoverer, you will need to use Noetix Generator for Oracle Discoverer (Noetix Generator) to update security in your End User Layer (EUL) each time you add, modify, or delete query users. For more information about updating security, see the Noetix Generator for Oracle Discoverer Administrator Guide. You must select the Remove Business Area Security on Non-NoetixViews Query Users check box; otherwise, deleted query users will still have access to the EUL.

Generate Noetix Query Users into NQS (When Using Noetix Platform)

If you are using NoetixViews for Oracle E-Business Suite (NoetixViews) in conjunction with Noetix Platform, you will need to generate Noetix query users into Noetix QueryServer (NQS) every time you add, modify, or delete users, or when permissions have been changed. You can easily generate Noetix query users and their permissions into NQS by using Noetix Generator for Noetix Platform—Oracle E-Business Suite Edition (Noetix Generator).

Noetix query users are automatically generated when you run Noetix Generator after generation. If you make subsequent changes to Noetix query users or security only, you can use Noetix Generator to generate the changes into NQS. For information, see the Noetix Generator for Noetix Platform Administrator Guide for Oracle E-Business Suite.

Chapter 6

Maintenance

This chapter lists the maintenance and configuration tasks for NoetixViews for Oracle E-Business Suite (NoetixViews).


OverviewThe NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator) equips you with the tools to perform a number of maintenance tasks from the administrator’s computer.

Many of the NoetixViews for Oracle E-Business Suite (NoetixViews) maintenance tasks can also be performed using SQL scripts.

Locate Important Directories and Files

This section provides information about the location of the important directories and files that are created in the NoetixViews for Oracle E-Business Suite (NoetixViews) application folder when you generate, regenerate, or upgrade Noetix views.

When You Generate Noetix ViewsAfter you generate Noetix views on your computer, a base installation directory called Installs is created in the NoetixViews application folder. The base installation directory may contain one or more Noetix System Administration User (NOETIX_SYS user) directories. The NOETIX_SYS user directory name will be in the following format: <schema name>_<TNS name>.

IMPORTANT: Administrators should place the NOETIX_SYS user directory in a secure location and ensure that only authorized individuals have access to this directory because it contains the tconnect.sql file, which, in turn, contains the connect string and password for the NOETIX_SYS user. The tconnect.sql file is created when iconnect.sql is run.

Chapter 6: Maintenance 233

When you run the view generation process for the first time, a NOETIX_SYS user directory is created in the base installation directory. The NOETIX_SYS user directory contains the scripts required for generating views and the *.lst files that are created when the scripts are run.

You can change the base installation directory of the NOETIX_SYS schema. For more information, see Change Base Installation Directory. If you do not know the location of the current base installation directory, click About on the Help menu of NoetixViews Administrator. In the About NoetixViews for Oracle E-Business Suite Administrator dialog box, you can view the location of the current base installation directory.

For information about:

• The NOETIX_SYS user directory, see Understand NOETIX_SYS Schema.

• Navigating to the currently connected NOETIX_SYS user’s directory, see Explore from Here.

• The important UNIX scripts, see Available UNIX Scripts.

• The important SQL and MS-DOS scripts, see Available SQL and MS-DOS Scripts.

When You Regenerate or Upgrade ViewsEach time you regenerate the views or upgrade the product, backup copies of the existing tupdprfx.sql, tupdqu1.sql, and tupdqu2.sql files are automatically created in the backups folder in the installation directory. On a Windows-based computer, the default path to the backups folder is <hard disk drive>:\Program Files\Noetix Corporation\NoetixViews\Installs\<NOETIX_SYS_TNS>. On a UNIX-based computer, the backups directory is created in the server directory containing the generation scripts of NoetixViews.

When you perform a regeneration or upgrade, if the backups folder already contains a backup copy of the tupdprfx.sql, tupdqu1.sql, or tupdqu2.sql file, the existing backup file is moved to the <filename>.hist folder in the backups folder, and the new backup file is created in the backups folder.


The files in the <filename>.hist folder follow a naming convention that comprises three parts:

<file name>_<date of backup>_<time of backup>

For example, if the tupdprfx.sql file is backed up for the second time on April 30, 2007 at 04:30 P.M., the following file will be created in the tupdprfx.sql.hist folder:

tupdprfx.sql_20070430_163000

The backup process is used in situations when the existing role prefixes and query user settings are lost during a regeneration or upgrade. In such situations, you can manually restore the settings using the backup files to revert to the earlier configuration. The backup files can also be used when you may have to apply the same role prefixes and query user settings on NOETIX_SYS schemas in testing and production environments. The role prefixes and query user settings can be applied only if the schemas belong to the appropriate Oracle E-Business Suite instance.

NoetixViews Administrator Tools

The following tools and features are available within the NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator). For information about other features, on the Help menu, click Help Topics.

To access these tools: 1. Click Start > All Programs > NoetixViews > NoetixViews Administrator. The


2. Locate the tool on the toolbar or on the menu options.


Change Base Installation Directory The Change Base Installation Directory tool allows the user to specify the base installation directory. For example, if the base installation is e:\installs, then NOETIX_SYS user directories will be created in e:\installs.

You can only change this option when you are not connected as a user. Click the Disconnect on the NoetixViews Administrator toolbar before changing your base installation directory.


Explore from HereThe Explore from Here feature opens Microsoft Windows Explorer with the current directory as the connected user’s NOETIX_SYS user directory.


Grant Select Any Table/DictionaryThis option allows the user to grant themselves the following:

• SELECT ANY TABLE privilege.

• SELECT ANY DICTIONARY privilege (Oracle Server 9i and later only).

This permission is usually granted during Stage 1 of the generation process and requires a logon with DBA privileges.


Override Oracle Tool DetectionNoetixViews for Oracle E-Business Suite (NoetixViews) will automatically detect tools such as SQL*Plus and SQL*Loader when loading NoetixViews Administrator and installation software. On the Tools menu of NoetixViews Administrator, click Override Oracle Tool Detection to override the detected tools. On the Override Oracle Tool Detection dialog box, choose the version of SQL*Loader and/or SQL*Plus that you would prefer to use from the Override Path lists.


Enable/Disable Administrator FunctionalityBy default, the ability to generate NoetixViews and NoetixAnswers and generate the Noetix Help File (Help Generation) is enabled for the Noetix System Administration User. On the Tools menu, click Support > Enable Noetix Administrator Functionality to disable these features, if required.

NOTE: You can also disable these features using scripts. For doing this, using SQL*Plus, run iguifs.sql. For more information, see Available SQL and MS-DOS Scripts.

When these features are disabled, the menu options and buttons will not be available in NoetixViews Administrator, preventing users from inadvertently starting a generation of Noetix Help File. However, this does not prevent users from running the same processes using scripts.

To change these settings, you must provide valid logon information for a user with DBA privileges.


You can choose to enable or disable features for all sessions or only the current session.

• Enabling/disabling features for all sessions will affect anyone who logs on with the user name that is currently used for logging on. This change will affect all future sessions but not the current session.

• Enabling/disabling features for the current session will temporarily enable or dis-able the features for the user name that is currently used for logging on. This change will affect the current session but not the subsequent sessions.

Administrative ScriptsThis section provides information about the script files that can be used to complete a variety of generation and maintenance tasks pertaining to NoetixViews. A number of important UNIX, MS-DOS, and SQL scripts are available in the NOETIX_SYS user directory (by default, <hard disk drive>:\Program Files\Noetix Corporation\NoetixViews\Installs\<NOETIX_SYS_TNS>) on a computer running Microsoft Windows and in the server directory containing the generation scripts of NoetixViews on a UNIX-based computer.

Available UNIX ScriptsThe following is a list of UNIX scripts that you can run on a UNIX-based computer to complete some important generation and maintenance tasks:

• checkenv.sh: Checks whether the logon user’s environment is ready for installing, upgrading, or maintaining Noetix views.

• icronenv.sh: Sets up the Cron environment when regenerating views by using Cron.

• icrontab.sh: Populates the crontab file when regenerating views by using Cron.

• inst4cron.sh: Starts Stage 4 of the views generation process from Cron.• setup.sh: Sets up generation scripts and metadata on a Unix-based computer. It

also sets the execute permission on all *.sh, *.bat, @echo, and @goto files.

NOTE: The setup.sh file is applicable for Noetix views generation on a UNIX-based computer only. This script should be run after all the generation scripts are transferred to the UNIX-based computer and prior to the views generation.


Run a UNIX ScriptTo run a UNIX script:1. On a UNIX-based computer, change the present working directory to the

directory containing the generation scripts of NoetixViews.

2. Run the required UNIX script. It is advisable that you work with your support representative to run the appropriate script and complete the specified task.

Available SQL and MS-DOS ScriptsThe following is a list of important SQL and MS-DOS script files that can be run on Windows or UNIX:

• iallhlp.sql: Regenerates the Noetix Help File in the same formats as gener-ated in the previous generation.

• ianswers.sql: Runs Noetix Answer Builder.• iappspkg.sql: Installs wrapper packages in the APPS schema that are required

by NoetixViews.• icomhlp.sql: Generates or regenerates Noetix Help File in the Query Tool

(column comments) Help format.• iconcmgr.sql: Loads the concurrent program when regenerating views by

using the Concurrent Manager.• iconnect.sql: Generates the tconnect.sql file. This file is generated based

on the most recent record available for Stage 4 of the views generation process in the N_VIEW_PARAMETERS table. It is required only if the tconnect.sql file is missing.

• i_create_sm_users.sql: Adds Oracle database users and Oracle E-Business Suite users and responsibilities as Noetix query users of Database User (Type U), Oracle E-Business Suite Authenticated User (Type A), and Oracle E-Business Suite Authenticated Responsibility (Type R) types.

• idelqusr.sql: Removes Noetix query users of the Database User (Type U) type and their roles.

• ifix4sts.sql: Overrides the generation errors of Stage 4 of the generation process. This file can be run only if views have been generated despite errors. Run this file if you need to run the steps successive to Stage 4 of the generation process, such as generating answers that cannot be completed if any errors are detected during Stage 4.

• igetprm.sql: Gathers parameters for unattended regeneration of views using the Concurrent Manager or Cron.


• igetpw.sql: Gathers passwords for unattended regeneration of views using the Concurrent Manager or Cron.

• iguifs.sql: Enables or disables the generation stages and/or the Noetix Help File generation in NoetixViews Administrator.

NOTE: The iguifs.sql script can be run only on Windows.

• ihtmlhlp.sql: Generates or regenerates Noetix Help File in the HTML for-mat.

• imshlp.sql: Generates or regenerates Noetix Help File in the Microsoft Win-Help format.

• install1.sql: Starts Stage 1 of the generation process.• install2.sql: Starts Stage 2 of the generation process.• install3.sql: Starts Stage 3 of the generation process.• install4.sql: Starts Stage 4 of the generation process.• instuser.sql: Creates an Oracle database user (if run from a database account

with DBA privileges).• listchng.sql: Provides information about the changes that have occurred in

the Noetix views since a previous generation. It also displays the changes occurring in the views due to a NoetixViews upgrade.

• listcnfg.sql: Provides information about your Noetix views generation.• listinfo.sql: Provides information about the FND configuration in the

Application Object Library (AOL).• listjoin.sql: Provides a list of Z$ columns that can be used for joins.• preupd.sql: Performs tasks needed prior to upgrading NoetixViews.• tupdprfx.sql: Provides information about the role prefixes in your views.• tupdqu1.sql: Provides information about Noetix query users, such as their

names, types, and start and end dates. Whether query tool optimizing views or synonyms for the views are created for the users is also indicated.

• tupdqu2.sql: Provides information about Noetix query users, such as their names, types, and roles. It also contains the assignment of General Ledger and budget user security for the users.

• inst4cm.prog: Starts Stage 4 of the views regeneration process from the Con-current Manager.

• clear.bat: Removes old and extraneous files. You may encounter errors while generating or regenerating views, or upgrading the product. After the errors are resolved, run clear.bat, and continue with the generation, regeneration, or upgrade.

• finderr.bat: Checks a Noetix views generation for errors.


Run an SQL or MS-DOS ScriptYou can run an SQL or MS-DOS script on Windows or UNIX. When you are running these scripts on a computer running Windows, you can call the SQL*Plus or Support prompt from NoetixViews Administrator.

To run an SQL script at the command prompt from NoetixViews Administrator:1. In NoetixViews Administrator, on the Tools menu, click Support > SQL*Plus

Prompt to open an SQL*Plus session from the NoetixViews Administrator main window.

2. On the SQL*Plus prompt, run the appropriate script to complete the specified task. It is advisable that you work with your support representative to run the appropriate script and complete the specified task.

To run an MS-DOS script at the command prompt from NoetixViews Administrator:1. In NoetixViews Administrator, on the Tools menu, click Support > Support

Prompt. This will take you to the command prompt that will allow you to run the support scripts. The prompt points to the directory that holds the script files specific to the Noetix System Administration User account that you are connected to.

2. The prompt is displayed as Noetix Home, to describe the location where all files related to the Noetix views generation are located. Work with your support representative to run the appropriate script to complete the specified task.


To run an SQL script on UNIX:1. Change the present working directory to the server directory containing the


2. Using SQL*Plus, connect to the database as the Noetix System Administration User. To do this, at the SQL prompt, type the following command: sqlplus <username>/<password>@<dbconnectstring>

3. Run the required SQL script. It is advisable that you work with your support representative to run the appropriate script and complete the specified task.

To run an MS-DOS script on UNIX:1. Change the present working directory to the server directory containing the


2. Run the required MS-DOS script. It is advisable that you work with your support representative to run the appropriate script and complete the specified task.

Resolve Issues in Your Noetix Views Generation

If there is an issue in your Noetix views generation (for example, if NoetixViews for Oracle E-Business Suite (NoetixViews) is not functioning correctly or if it is not returning data as described in the Noetix Help File), a workaround may be provided by Noetix Technical Support. The workaround is typically in the form of a modified SQL script that will be placed in the NOETIX_SYS user directory, often overwriting an existing file. If you need to overwrite an existing file, make a copy of the existing file at the same location and rename it as <file name>.old. Run Stage 4 of the Noetix views generation process. NoetixViews will use the modified SQL script to change the affected views to overcome the issue.

Noetix Technical Support retains bug workaround scripts for every NoetixViews customer, upgrading them as and when necessary. These scripts are available with the upgraded product software released to the customer, and they smoothly integrate in the Noetix views generation process. After the issue is formally corrected in the product, the workaround is retired by Noetix Technical Support.


Refresh Key Flexfield Data Cache Tables

Key flexfield data cache tables are created, loaded, and indexed during Stage 4 of the view generation process. However, these tables need to be refreshed to reflect the changes in the segments values or descriptions related to a key flexfield code combination defined at your site. The data in the data cache tables can be refreshed fully or incrementally.

Full RefreshIn the full refresh process, the existing information in the data cache tables is replaced with the information from the source key flexfield tables. When the data cache tables are fully refreshed, reports based on the global views that use these data cache tables are unavailable until the full refresh is completed. In the full refresh process, a Concurrent Manager program is automatically created and scheduled for each available data cache table. This program is created during Stage 4 of the generation process. By default, the program is scheduled to run on a monthly basis. You can change this schedule when required.

NOTE: Some key flexfields may also have a data cache description table created in addition to the data cache value table. In such cases, a request set is also created to refresh the data cache description table and data cache value table. For example, a request set named N_KFF_GL_ACCT-RSET(UID-5035) is created to refresh the N_KFF_GL_ACCT and N_KFF_GL_ACCT_D tables.

The Concurrent Manager program names created for full refresh use the <data cache table name>-Initial Upload (<NOETIX_SYS>[UID-<NOETIX_SYS internal identifier>]) format. For example, the Concurrent Manager program created for the N_KFF_GL_Acct data cache table will be named as N_KFF_GL_Acct-Initial Upload (HG_B911_PO_BL_SSY[UID-5035]).


The following query can be used to list all the Concurrent Manager programs that are created for the full refresh process in a NOETIX_SYS schema:

select program_name from n_f_kff_flex_source_pgms where program_type = 'INITIAL'

IMPORTANT: To run this query, you have to use a database query tool, such as Toad to connect to the NOETIX_SYS schema.

To verify the Concurrent Manager programs in Oracle E-Business Suite:1. Log on to Oracle E-Business Suite as the XXNAO user. The XXNAO user is a

super user that is automatically created for handling all the application objects corresponding to the NOETIX_SYS schema. The default password for this user is set as welcome#1.

2. Select the key flexfield responsibility corresponding to the NOETIX_SYS schema at your site. This responsibility is required for viewing, scheduling, or submitting the jobs used to refresh data cache tables. By default, the responsibility name uses the Noetix Administration Objects.KFF(<NOETIX_SYS>[UID-<NOETIX_SYS internal identifier>]) format. For example, the key flexfield responsibility corresponding to the HG_B911_PO_BL_SSY schema will be named as Noetix Administration Objects.KFF(HG_B911_PO_BL_SSY[UID-5035]).

3. Verify the Concurrent Manager programs created for the full refresh process. If required, modify the default schedule for the Concurrent Manager programs, and then resubmit the programs.

The source data changes are reflected in the global views after the data cache tables are refreshed. For more information about data cache tables, see Key Flexfield Views in “Forms of Noetix Views.”

Incremental RefreshIn the incremental refresh process, data cache tables are updated only with the changed data from the source key flexfield tables. The incremental refresh process uses triggers to detect and capture data changes from the source key flexfield tables between refreshes. The incremental refresh process can be used if the data cache tables have to be refreshed frequently. When compared to the full refresh process, the existing data in the data cache tables is available for report generation during the incremental refresh process. However, the changed data will be available for report generation only after the incremental refresh process is completed.


By default, the incremental refresh infrastructure is installed and not activated to detect the source data changes. A Concurrent Manager program is available to enable the incremental refresh process. You will have to manually run this Concurrent Manager program to enable the incremental refresh process. The Concurrent Manager program uses the Enable Incremental Refresh-(<NOETIX_SYS>[UID-<NOETIX_SYS internal identifier>]) format for the name. For example, the Concurrent Manager program created for the HG_B911_PO_BL_SSY schema will be named as Enable Incremental Refresh-(HG_B911_PO_BL_SSY [UID-5035]).

The Concurrent Manager program performs the following when run:

• Activates the triggers to detect and capture data changes from the specified source key flexfield tables.

• Submits the individual full refresh Concurrent Manager program for the data cache tables corresponding to the specified key flexfield.

• Cancels the individual full refresh Concurrent Manager program schedule for the data cache tables corresponding to the specified key flexfield.

• Schedules the incremental refresh request set for the specified key flexfield. The request set is scheduled to run automatically to update the data cache tables every four days. You can change this schedule when required. The request set created for incremental refresh uses the INCREMENTAL_REFRESH-<NOETIX_SYS>[UID-<NOETIX_SYS internal identifier>]) format for the name. For example, the request set created for the HG_B911_PO_BL_SSY schema will be named as INCREMENTAL_REFRESH-HG_B911_PO_SSY[UID-5035]).

To enable incremental refresh:1. Log on to Oracle E-Business Suite as the XXNAO user. The XXNAO user is a


2. Select the key flexfield responsibility corresponding to your NOETIX_SYS schema that is required for viewing, scheduling, or submitting the jobs used to refresh data cache tables. By default, the responsibility name uses the Noetix Administration Objects.KFF(<NOETIX_SYS>[UID-<NOETIX_SYS internal identifier>]) format. For example, the key flexfield responsibility corresponding to the HG_B911_PO_BL_SSY schema will be named as Noetix Administration Objects.KFF(HG_B911_PO_BL_SSY[UID-5035]).


3. Click Submit Requests. The Submit a New Request dialog box appears.

4. Click Single Request, and then click OK. The Submit Request dialog box appears.

5. In the Name box, search for the Concurrent Manager program, and then select the program.

6. In the Parameters dialog box, type the flexfield code or search for the flexfield code corresponding to the key flexfield for which you want to enable incremental refresh. By default, the parameter value is set to ALL. Noetix recommends enabling incremental refresh for all the key flexfields available in the NOETIX_SYS schema at your site. Click OK to save the changes and close the Parameters dialog box.

IMPORTANT: Noetix recommends using either full or incremental refresh for all the key flexfields. If you enable incremental refresh for only some key flexfields, data corresponding to some key flexfields that are included in global views may not be synchronized.

7. Click Submit. If you have enabled incremental refresh for only one key flexfield in step 6 and if you want to enable incremental refresh for another key flexfield, click Yes, or else, click No. The incremental refresh will be enabled for the data cache tables corresponding to the specified key flexfields.


Refresh Parent-Child Hierarchy Data

The parent-child hierarchies corresponding to the Accounting Flexfield segments are stored in a flattened table. Based on the parent-child hierarchy data available in the flattened table, the parent-child hierarchies and parent-child essentials views are generated during Stage 4 of the view generation process. However, the flattened table needs to be refreshed to reflect the changes in the parent-child hierarchies of the Accounting Flexfield segments. A Concurrent Manager program is created when parent-child views are generated in NoetixViews. If modifications are made to a segment hierarchy structure in Oracle E-Business Suite, the Concurrent Manager program should be run the to capture the changes. This includes changes to existing parent-child hierarchies and new parent-child hierarchies added to a segment that had at least one previous hierarchy. The changes made to existing parent-child hierarchies include addition of new parents and childs to an existing hierarchy or moving a child from one parent to another.

To refresh the flattened table:1. Log on to Oracle E-Business Suite as the XXNAO user. The XXNAO user is a


2. Select the parent-child hierarchy responsibility corresponding to your NOETIX_SYS schema that is required for viewing, scheduling, or submitting the jobs used to refresh the flattened table. By default, the responsibility name uses the Noetix Administration Objects.HIER(<NOETIX_SYS>[UID-<NOETIX_SYS internal identifier>]) format. For example, the parent-child hierarchy responsibility corresponding to the HG_B911_PO_BL_SSY schema will be named as Noetix Administration Objects.HIER(HG_B911_PO_BL_SSY[UID-5035]).

3. Click Submit Requests. The Submit a New Request dialog box appears.

4. Make sure that the Single Request option is selected, and then click OK. The Submit Request dialog box appears.


5. In the Name box, search for the default Concurrent Manager program that is created for refreshing the flattened table corresponding to your Noetix schema, and then select the program. The default Concurrent Manager program uses the Noetix Segment Hierarchy Table Refresh (<NOETIX_SYS>[UID-<NOETIX_SYS internal identifier>]) format. For example, the Noetix Segment Hierarchy Table Refresh (HG_B911_PO_BL_SSY[UID-5035]) Concurrent Manager job is created for the Noetix Administration Objects.HIER(HG_B911_PO_BL_SSY[UID-5035]) responsibility.

6. Click Submit. If you want to submit another request, click Yes, else, click No. The Concurrent Manager job will be run and the flattened table will be updated with the parent-child hierarchies changes. After submitting the job request, you can verify the status of the request.


NoetixViews CustomizationThe functionality in Oracle E-Business Suite is vast, and Noetix attempts to support the majority of customer’s operational reporting needs out of the box. However, if the customer configuration is not supported out of the box, the views can be customized by modifying the existing scripts in the NOETIX_SYS user directory. NoetixViews for Oracle E-Business Suite (NoetixViews) uses these modified scripts to generate customized views at a customer’s site.

The modifications done in the scripts must be approved by Noetix certified personnel to maintain the supportability of the software. The customer requirements beyond the NoetixViews design and architecture will be considered customer-specific, and are typically billable.

This section provides information about the NoetixViews customization and the Noetix Customization Maintenance (NCM) program. The instructions to customize NoetixViews in this section must only be performed by certified individuals who are trained in how to develop, deploy, and maintain hook scripts. The NoetixViews Customization Certification (NVCC) course is available for customers skilled in SQL who have a core knowledge of the NOETIX_SYS schema. Passing an exam at the end of the course is a requirement. The standards specified in NVCC are critical for maintaining the stability and supportability of your NoetixViews environment. The Noetix patch framework:

• Makes customized views easier to maintain.• Enables the corresponding changes to be reflected automatically in the Noetix

Help File.• Generates the changes automatically in the Oracle Discoverer Business Area or

Noetix Platform if you have the Noetix Generator for Oracle Discoverer (Noetix Generator) or the Noetix Generator for Noetix Platform—Oracle E-Business Suite Edition (Noetix Generator) respectively.

Please contact Noetix Technical Support if you require a quote for the views customizations and do not have certified personnel.


Understand NOETIX_SYS SchemaNOTE: NOETIX_SYS is the default name of the Noetix System Administration User account created during a new generation of Noetix views. You can choose a different name for the Noetix System Administration User account during Stage 1 of the Noetix views generation process. For more information, see Stage 1: Create Noetix System Administration User Account in “Generation of Views.”

All the NoetixViews objects are contained within the NOETIX_SYS schema on the database.

NOTE: Oracle DBAs may drop the NOETIX_SYS user with the Cascade option to remove a generation of Noetix views. Additional steps are necessary to drop the associated database roles.

The technical customers may want to explore the NOETIX_SYS schema for a better understanding of how Noetix is able to generate so many customized CREATE VIEW statements in such a short span of time. If you observe each NOETIX_SYS schema, you will find a number of NoetixViews template tables called n_view_%_templates that store generic information common for all customers (hand-crafted metadata before it has been tailored to your specific Oracle E-Business Suite configuration). You will also find non-template tables called n_view_% that contain information unique to the specific Oracle E-Business Suite instance for which the views were generated. This information is used by the NoetixViews scripts, and the resulting unique CREATE VIEW statements can be found in the mkview.lst file in the NOETIX_SYS user directory. The CREATE VIEW statements for views built by the NoetixViews Cross Operations Extension (XOP) can be found in mkviewx.lst. The CREATE VIEW statements for views built by the Global extension are found in the mkviewg.lst file.

These mkview%.lst files can be used as a supplemental tool to help your technical report developers. While the Noetix Help File is ideal to assist end users to navigate NoetixViews, the mkview.lst file is useful for technical users who want to understand how each view was built.

IMPORTANT: Do not directly modify the mkview%.sql or mkview%.lst files. These files are automatically generated during the views generation and are overwritten each time the views are regenerated or upgraded. More importantly, this type of change would require customer intervention for the life of the NoetixViews software to keep the reports intact. You must do the customizations within the Noetix approved methodology as specified in this section.


Customize NoetixViewsThe customizations, extensions, and bug fixes to NoetixViews can all be accomplished using a common methodology. There are a number of files in the NOETIX_SYS user directory that can be replaced with carefully designed files, called hook scripts, to implement the required changes. A hook script may be developed by Noetix Engineering, Noetix Technical Support or other individuals who have successfully completed the NoetixViews Customization Certification (NVCC) course. These hook scripts affect generation of Noetix views. Hook scripts provide advanced flexibility to the software by altering the values populated in the Noetix template or non-template tables to change the resulting CREATE VIEW statements.

Some types of customizations that can be implemented in the views include:

• Adding a column.• Dropping a column.• Altering a column or view description.• Joining a new table to an existing view to generate a completely new view.• Generating selective views on the basis of specific directives.

Let us consider an example to illustrate a view customization. You want to generate several copies of the AP_Invoices view based on the combination of your ledger and operating unit. If you need a column added to this view to meet your reporting requirements, use a hook script to update the NoetixViews metadata repository with the new column information. All subsequent regenerations would result in the AP_Invoices view, the Noetix Help File, and possibly your Discoverer End User Layer (EUL) with the new column included.

In the same example, if there is a ledger that is no longer used in your organization and you would prefer not to expose the AP_Invoices view for that ledger, you can suppress the view generation for that ledger using a suppression hook script. More information about suppressing your views generation is available in the next section.


Suppress Noetix ViewsThe entire metadata for supported NoetixViews modules is shipped as .dat files with the product software. As a result, views for all modules will be generated or upgraded. The generation of views can be limited by a suppression hook script when the customers prefer to have separate schemas for some NoetixViews modules. To perform a suppressed Noetix views generation, the customers will create multiple NOETIX_SYS user directories and copy the suppression hook script unique to each schema to the respective NOETIX_SYS user directory before generating the views.

Suppress Parent-Child Hierarchy Views in NoetixViewsThe parent-child hierarchies and parent-child essentials views are generated for each segment of each chart of accounts in Oracle E-Business Suite. These views can be used only with the global Noetix views and are generated for a segment only if a flex value set is defined on that segment. By default, the parent-child hierarchies and parent-child essentials views are generated in a NoetixViews configuration. NoetixViews provides a feature for suppressing the parent-child hierarchy views. You can decide to suppress either the parent-child hierarchies views or the parent-child essentials views or both depending on the requirement.


To suppress the parent-child hierarchy views:1. On a computer that is running Windows, from the C:\Program Files\Noetix

Corporation\<NoetixViews installation folder>\Master\Scripts folder, copy the wnoetxu4.sql script to the C:\Program Files\Noetix Corporation\<NoetixViews installation folder>\Master\Custom folder. On a computer that is running Linux or UNIX, the wnoetxu4.sql script will be available under the directory where you have copied all the NoetixViews installation files and scripts.

2. Edit the file using a text editor application, and then look for the PARENT CHILD PROCESSING section:

3. To suppress the parent-child hierarchies views, remove the double hyphen (--) from the beginning of the line "define GENERATE_HIERARCHY_VIEWS=’N’". To suppress the parent-child essentials views, remove the double hyphen (--) from the beginning of the line "define GENERATE_DIMENSION_VIEWS=’N’".


4. Save the changes.

5. Run the view generation process.

Suppress Charts of Accounts in NoetixViewsNoetixViews provides a feature for suppressing the charts of accounts that are not required in a NoetixViews configuration. For example, this feature can be used to suppress those charts of accounts that are not associated with a ledger. Suppressing a chart of accounts results in that chart of account's segments not being including in the views, the associated code combinations not being cached in the Noetix key flexfield data cache, the data for all associated ledgers, operating units, and inventory organizations not being returned by the global views, the associated ledgers, operating units, and inventory organizations not getting generated in the corresponding standard or XOP roles, and no parent-child views generated for its segments. The following procedure explains how to suppress charts of accounts.

To suppress charts of accounts:1. Identify the charts of accounts that you want to suppress.

2. On a computer that is running Windows, from the C:\Program Files\Noetix Corporation\<NoetixViews installation folder>\Master\Scripts folder, copy the wnoetxu3.sql script to the C:\Program Files\Noetix Corporation\<NoetixViews installation folder>\Master\Custom folder. On a computer that is running Linux or UNIX, the wnoetxu3.sql script will be available under the directory where you have copied all the NoetixViews installation files and scripts.

3. Edit the file using a text editor application, and then look for the line that reads “--Suppression script goes here...”. After you locate this line, press ENTER to move to the next line.


4. Type the following lines of code: begin n_org_suppression_pkg.COA_Suppression( i_coa_id => <chart of accounts ID>); end; / where <chart of accounts ID> represents the chart of accounts ID. For example, to suppress a chart of accounts with ID 50194, type the following lines of code: begin n_org_suppression_pkg.COA_Suppression( i_coa_id => 50194) end; / If you want to suppress more than one chart of accounts, use separate lines of code for each chart of accounts and end each line with a semicolon (;).


5. Save the changes.

6. Run the view generation process.

NCM ProgramThe hook scripts provided by Noetix as customer-requested enhancements are eligible for maintenance under the Noetix Customization Maintenance (NCM) program. NCM is an extension to your Noetix Technical Support agreement. The customizations will be maintained and upgraded as necessary with each Oracle E-Business Suite and NoetixViews release. The upgraded product software will include the upgraded customization hook scripts. You do not have to worry for any broken reports as a result of customization of your NoetixViews because these hook scripts adhere to the upgrade protection policy.

Chapter 7

Regeneration of Views

This chapter details the instructions and information necessary to regenerate Noetix views, Noetix answers, and the Noetix Help File.


OverviewPeriodic maintenance is required to keep your Noetix views generation in synchronization with your Oracle configuration. Noetix Corporation recommends frequent regenerations to keep NoetixViews for Oracle E-Business Suite (NoetixViews) metadata and user accounts synchronized with changes made to your Oracle database or applications (for example, to pick up security changes or new flexfields). The frequency with which you regenerate will depend on the frequency of changes you make in your Oracle environment.

Noetix views must be regenerated in the following situations:

• A significant patch to Oracle E-Business Suite has been applied.• You have upgraded your Oracle E-Business Suite (if your current version of

NoetixViews supports that version).• You have upgraded Oracle Database.• You have standard or Cross Operations Extension (XOP) form of the views and

performed one or more of the following tasks:

• New business groups, ledgers, operating units, inventory organizations, service requests, time categories, collection plans, or collection plan elements added to your Oracle environment.

• The key or descriptive flexfield configuration in Oracle E-Business Suite has changed, such as a key flexfield structure has been added or modified.

• Additional flexfield security rules have been created in Oracle E-Business Suite or a new segment has been added to the Accounting Flexfield.

• You have global form of the views and performed one or more of the following tasks:

• The key or descriptive flexfield configuration in Oracle E-Business Suite has changed, such as a key flexfield structure has been added or modified.

• Additional flexfield security rules have been created in Oracle E-Business Suite or a new segment has been added to the Accounting Flexfield.

• The configuration of the Codes, Lookups, or Types values has changed.• You have received hook scripts or customizations from Noetix Technical Support,

but not a new software product.

Chapter 7: Regeneration of Views 261

In all of these circumstances, Noetix views must be regenerated to incorporate any changes made to either NoetixViews or the Oracle configuration.

When regenerating, you must start with a successful Noetix views generation (that is, the last time you ran Stages 1 through 4 of the generation process, they must have all completed successfully). If your generation was not successful, use the steps described in Option 1: Generate Using NoetixViews Administrator and Option 2: Generate Using Scripts in “Generation of Views” to complete your generation, or call Noetix Technical Support. Attempting a regeneration when the initial generation was not successful may fail and cause you to lose important generation settings.

NOTE: After regenerating the views, to provide Noetix query users the latest views with appropriate security through query tools, you may need to update the query tool meta-layers and take additional steps. For information, refer to the documentation of the query tools.

Choose a Regeneration Method

Noetix views can be regenerated with the use of the NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator) or scripts. In addition, regenerations can be scheduled using a Concurrent Manager job or using a UNIX-based Cron job.

You will need to choose the method that will work best for your environment. Consider the following requirements when making your choice:

?Should I regenerate, or should I upgrade?

• Have you received a new version of NoetixViews? An upgrade installs a new version of NoetixViews.

• Has your Oracle environment changed or do you need to apply a patch? A regeneration recreates your NoetixViews metadata after changes have been made to your database or applications and is often needed to apply patches from Noetix Corporation as well. This chapter explains how Noetix views are regenerated.


• How familiar are you with Noetix views generations and regenerations? If you do not have much experience administering your NoetixViews for Oracle E-Business Suite (NoetixViews) environment, you may do best with a wizard-based regeneration, which provides more information about the prompts asked during the process.

• What environment or computer do you currently use for administrative tasks? If you use Microsoft Windows, SQL*Plus, Cron (the UNIX scheduling service), or the Concurrent Manager (the Oracle scheduling service) for other administrative tasks, you may want to use a similar process for regenerating NoetixViews.

• Do you need to regenerate outside of business hours? If so, the Cron or Concurrent Manager methods, which can be scheduled, may work best for you.

• Have you added ledgers, operating units, or inventory organizations to your Oracle environment? If so, regenerating will create roles and views for these new structures. You will need to determine the role prefixes for these new roles, which can’t be done in a scheduled regeneration method.

The following table lists the considerations for each regeneration method:

Features

Compare Regeneration Methods


ScriptsConcurrent Manager Job

Cron Job

Runs on Windows?

Runs on UNIX/Linux?

Can be scheduled?

Supports editing role prefixes during regeneration?


IMPORTANT: If a regeneration fails or is aborted, your next attempt should be done using the same regeneration method, computer, and NOETIX_SYS user directory. If you switch regeneration methods after an unsuccessful regeneration, it may be difficult to retain your Noetix query user accounts and role prefixes.

Option 1: Regenerate Using NoetixViews Administrator

Regenerating views using the NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator) involves walking through a short series of wizards in the application used to administer NoetixViews for Oracle E-Business Suite (NoetixViews). The steps you follow are very similar to the steps used when initially generating NoetixViews.

Can be used without additional setup steps?

Can include NoetixAnswers regeneration?

Can automatically compile Windows help format?

Includes online help for each dialog box/prompt?

Features

Compare Regeneration Methods


ScriptsConcurrent Manager Job

Cron Job


This regeneration method is performed using a Microsoft Windows-based client computer, usually the administrator’s, where NoetixViews Administrator has been installed. If this computer does not already have NoetixViews Administrator installed, see Install the Software on Windows in “Installing NoetixViews for Oracle E-Business Suite” for information about how to install this software.

NOTE: On a Windows-based computer, script-based regeneration of Noetix views is available for only Stages 2 through 4. To do this, after Stage 1 is completed, click Tools >

Support > SQL*Plus Prompt or click on the toolbar to connect to the database through SQL*Plus as the Noetix System Administration User and continue with the next stages. For information about script-based regeneration, see Option 2: Regenerate Using Scripts.

To regenerate Noetix views using NoetixViews Administrator:1. Log on to NoetixViews Administrator as your existing Noetix System

Administration User account: For information, see Start NoetixViews Administrator in “Generation of Views.”

2. Refresh generation scripts: When regenerating after the NoetixViews configuration has changed, the NoetixViews Administrator can confirm that the collection of scripts in the NOETIX_SYS user directory is appropriate for the NoetixViews version being implemented. On the Tools menu, click Support > Refresh Scripts to accomplish this task. This displays information regarding the version number of the scripts located within your NOETIX_SYS user directory.

3. Complete Stages 2, 3, and 4 of the generation process: Run Stages 2, 3, and 4 of the views generation process. During Stage 4 of the regeneration of views, NoetixViews Administrator will detect the previous settings and give you the option to reuse them in the current generation. Settings include role prefixes and Noetix query users. To use the existing settings from the database, select Yes on the displayed wizard page. Do not select No unless directed by Noetix Technical Support, or if you want to replace the role prefixes and query users in the database with the ones saved in the tupdprfx.sql, tupdqu1.sql, and tupdqu2.sql files in the NOETIX_SYS user directory. For more information about the stages of the generation process, see Option 1: Generate Using NoetixViews Administrator in “Generation of Views.”

CAUTION: Please note that if you change a role prefix, any reports written against Noetix views within that role will break. Also, changing the multi-currency option during a regeneration of views impacts reports written against the views for Oracle Projects. For information, see Changing the Multi-Currency Option While Regenerating Noetix Views.


NOTE: If any errors are detected in Stage 4 of the Noetix views regeneration, the Noetix Help File will not be regenerated. As a workaround, after completing Stage 4 of the Noetix views regeneration, you must first run the ifix4sts.sql script to override Stage 4 errors, and then manually regenerate the Noetix Help File. The ifix4sts.sql script is located in your NOETIX_SYS user directory (by default, <hard disk drive>:\Program Files\Noetix Corporation\NoetixViews\Installs\<NOETIX_SYS_TNS>).

4. Run the listchng script (optional): This will create a file showing differences between your previous and new generations. start listchng.sql These changes will be contained in the listchng.lst file.

5. Regenerate answers (when using Noetix Platform): You will need to rerun Noetix Answer Builder. After successfully running Noetix Answer Builder, you must run Noetix Generator for Noetix Platform—Oracle E-Business Suite Edition (Noetix Generator) to update your answers, as well as to generate your query user data into NQS. For more information, see Regenerate Noetix Answers.

6. Regenerate the Noetix Help File: You will need to regenerate your Noetix Help File so it will reflect your updated generation. For information about generating and distributing the Noetix Help File, see Option 1: Regenerate Help Using NoetixViews Administrator.

7. Update query tools (if needed): Refer to your query tool documentation to see if your tools or their meta-layers need to be updated. If you are using Noetix Generator for Oracle Discoverer (Noetix Generator) in conjunction with Oracle Discoverer, you will need to extract views as described in the Noetix Generator for Oracle Discoverer Administrator Guide to update your End User Layer (EUL).


Option 2: Regenerate Using Scripts

Regenerating Noetix views using scripts involves running a series of scripts from SQL*Plus. The steps you follow are very similar to the steps used when initially generating Noetix views.

This regeneration method is mainly performed on a UNIX-based computer. If the NoetixViews for Oracle E-Business Suite (NoetixViews) files and scripts are not already present on this computer from the earlier generation, see Load the Software on UNIX in “Installing NoetixViews for Oracle E-Business Suite.”

NOTE: On a Windows-based computer, script-based regeneration of Noetix views is available for only Stages 2 through 4. To do this, after Stage 1 is completed, click Tools >

Support > SQL*Plus Prompt or click on the toolbar to connect to the database through SQL*Plus as the Noetix System Administration User and continue with the next stages.

To regenerate Noetix views using scripts:1. Using SQL*Plus, connect to the database as the existing Noetix System

Administration User: sqlplus <username>/<password>@<dbconnectstring>

2. Complete Stages 2, 3, and 4 of the generation process: Run Stages 2, 3, and 4 of the views generation process. When prompted whether to save previous settings, ensure that you type Yes to save the role prefixes and query user settings in the database. Do not type No unless directed by Noetix Technical Support, or if you want to replace the role prefixes and query users in the database with the ones saved in the tupdprfx.sql, tupdqu1.sql, and tupdqu2.sql files in the NOETIX_SYS user directory. For more information, see Option 2: Generate Using Scripts in “Generation of Views.”

CAUTION: Please note that if you change a role prefix, any reports written against Noetix views within that role will break. Also, changing the multi-currency option during a regeneration of views impacts reports written against the views for Oracle Projects. For information, see Changing the Multi-Currency Option While Regenerating Noetix Views.


NOTE: If any errors are detected in Stage 4 of the NoetixViews regeneration, the Noetix Help File will not be regenerated. As a workaround, after completing Stage 4 of the NoetixViews regeneration, you must first run the ifix4sts.sql script to override Stage 4 errors, and then manually regenerate the Noetix Help File. The ifix4sts.sql script is located in the same directory where the install4.sql script is present.

3. Run the listchng script (optional): This will create a file showing differences between your previous and new generations. start listchng.sql These changes will be contained in the listchng.lst file.

4. Regenerate answers (when using Noetix Platform): You will need to rerun Noetix Answer Builder. After successfully running Noetix Answer Builder, you must run Noetix Generator for Noetix Platform—Oracle E-Business Suite Edition (Noetix Generator) to update your answers, as well as to generate your query user data into NQS. For more information, see Regenerate Noetix Answers.

5. Regenerate the Noetix Help File: You will need to regenerate your Noetix Help File to reflect your updated generation. For information about generating and distributing the Noetix Help File, see Option 2: Regenerate Help Using Scripts.

6. Update query tools (if needed): Refer to your query tool documentation to see if your tools or their meta-layers need to be updated. If you are using Noetix Generator for Oracle Discoverer (Noetix Generator) in conjunction with Oracle Discoverer, you will need to extract views as described in the Noetix Generator for Oracle Discoverer Administrator Guide to update your End User Layer (EUL).


Option 3: Regenerate Using Scheduled Concurrent Manager Job

Regenerating Noetix views using a scheduled Concurrent Manager job requires a number of initial tasks to set up the environment and parameters to be used. After this initial setup is completed, no additional user input is required, and the regenerations can be scheduled.

NOTE: If you have upgraded NoetixViews for Oracle E-Business Suite (NoetixViews) and have used the Concurrent Manager earlier to regenerate your views, you need to repeat steps 5 and 6 in Step 1: Set Up Custom Application. Subsequently, you need to perform the procedures listed in Step 2: Populate Parameter File, Step 3: Populate Password File (for a standard install environment only), Step 4: Grant Permissions to APPS Objects (for an Oracle E-Business Suite On Demand Service (EBSO) environment only), Step 5: Define Concurrent Program, and Schedule Regeneration in Concurrent Manager. You should perform these procedures only after you have upgraded NoetixViews. For information about upgrading NoetixViews, see Upgrade the Software in “Installing NoetixViews for Oracle E-Business Suite.”

This method will involve setting up a Concurrent Manager job from a UNIX environment.

Initial SetupThe initial setup needs to be done once for each NOETIX_SYS schema. After the setup has been done, for subsequent regenerations, go to Schedule Regeneration in Concurrent Manager to start the regeneration.

Initial setup involves the following steps:

• Step 1: Set Up Custom Application• Step 2: Populate Parameter File• Step 3: Populate Password File (for a standard install environment only)• Step 4: Grant Permissions to APPS Objects (for an EBSO environment only)• Step 5: Define Concurrent Program


Step 1: Set Up Custom ApplicationYou will need to create the custom application record and directories that will allow you to use the Concurrent Manager to regenerate Noetix views. This step may need to be done by a DBA with experience in setting up custom applications.

NOTE: For information about creating the directory, setting up the environment variables, and creating a program link, see the Oracle E-Business Suite documentation.

To set up the custom application:1. Log on to the UNIX-based computer as the user associated with the Concurrent

Manager. Usually this is the same user who owns the Concurrent Manager log and output files. You will be using this account to run the concurrent process.

For the purposes of this document, this user is referred to as noetix_unix.

NOTE: This user can be found by changing to the Oracle E-Business Suite log or output files directories, using the UNIX commands cd $APPLCSF/$APPLLOG or cd $APPLCSF/$APPLOUT, and viewing the owners. The owner of the log and output files is the UNIX user account.

2. In the $APPL_TOP directory, create a TOP directory for the Noetix custom application—XXNOETIX—that you will register in step 8. This custom application’s TOP directory, XXNOETIX_TOP, is to be used by the Concurrent Manager and should be at the same level as the $FND_TOP directory. This directory structure depends on the operating system and the Oracle E-Business Suite version that is being used and should include subdirectories such as bin, sql, and ctl. Ensure that the noetix_unix user has full permissions to this directory.

As part of the custom application directory setup, the environment variables need to be set in the <dbname>.env file for the custom application’s TOP directory structure.

3. Navigate to the bin directory of the XXNOETIX directory you just created, and create a program link called inst4cm under Host Language Concurrent Programs. ln -ns $FND_TOP/bin/fndcpesr inst4cm

If you do not have an environment variable set for the $APPL_TOP directory, you may need to use the absolute path to the bin directory of the $FND_TOP directory rather than $FND_TOP/bin.


4. Under the XXNOETIX directory, create a /noetix_install_dir directory to be used exclusively for NoetixViews. This new directory should be at the same level as the bin directory.

5. Load the NoetixViews scripts into the noetix_install_dir directory following the steps described in Load the Software on UNIX in “Installing NoetixViews for Oracle E-Business Suite.”

6. Copy the file inst4cm.prog from the noetix_install_dir to the bin directory within the XXNOETIX directory structure.

NOTE: After copying the inst4cm.prog file to the XXNOETIX/bin directory, ensure that you have permissions to run the file.

7. Log on to Oracle E-Business Suite as a user with the System Administrator responsibility.

8. Register an application with the following values:

• Application: Noetix Custom Application• Short Name: XXNOETIX• Base Path: XXNOETIX_TOP• Description: Noetix Custom Application

9. Set up the standard/EBSO data group for the application with the following values:

• Application: Noetix Custom Application• Oracle ID: APPS• Description: Noetix Custom Application

Step 2: Populate Parameter FileThis step will populate a parameter file with default values for all of the information that Noetix views regeneration will need, such as regeneration options and user names. These default values appear when you set up your scheduled regeneration jobs (if they have not been already set up at the time of the previous generation). You can change them at a later step for each scheduled job you create.


The script you run in this step will gather and validate the parameters and save them to the noetix_install_dir/autorun/cparam.sql file. You will have to provide all the required parameters (except passwords) for a scheduled regeneration. While scheduling a regeneration in Concurrent Manager, the Noetix System Administration User password will be taken from the secured cparam.sql file.

To populate the parameter file:1. Change the present working directory to the noetix_install_dir directory on the

computer containing the NoetixViews generation scripts.

2. Using SQL*Plus, connect to the database as the Noetix System Administration User: sqlplus <username>/<password>@<dbconnectstring>

NOTE: If you are using an instance that is not stored in the ORACLE_SID environment variable, type @dbconnectstring.

3. Run the script to gather parameters: start igetprm.sql


• Please enter the <NOETIX_SYS user> password.

• Please enter the name of the database where the <NOETIX_SYS> user resides.

NOTE: Type the Transparent Network Substrate (TNS) name of this database.

• What type of unattended install environment do you operate in (STANDARD or EBSO)?

NOTE: Type STANDARD or EBSO depending on your environment.

• Please enter the default tablespace for the <NOETIX_SYS> user.


• Please enter the Noetix Administrator Installation Path.

NOTE: Type the full path to the noetix_install_dir directory, to which the NoetixViews scripts were loaded.

• Please enter the APPS user name.

• Please enter the language used in the install stage 4 processing.

• Should Global views be installed (if available)? Please answer Y or N.

NOTE: If global form of Noetix views has been purchased, should they be generated? Valid responses are Y and N.

• Should XOP views be installed (if available)? Please answer Y or N.

NOTE: If Cross Operations Extension (XOP) form of Noetix views has been purchased, should they be generated? Valid responses are Y and N.

• Should Standard views be installed? Please answer Y or N.

• Should standard INV views be installed (if available)? Please answer Y or N.

NOTE: If NoetixViews for Oracle Inventory has been purchased, should organization-specific views be generated? Valid responses are Y and N.

• Should Projects Multi-currency columns be installed (if available)? Please answer Y or N.

NOTE: If NoetixViews for Oracle Projects has been purchased, Oracle E-Business Suite 11.5.8 or later detected, and Oracle Projects installed, should the multi-currency columns be generated? Valid responses are Y and N. Changing the multi-currency option during a regeneration of views impacts reports written against the views for Oracle Projects. For information, see Changing the Multi-Currency Option While Regenerating Noetix Views.

• Should Database comments be generated? Please answer Y or N.

IMPORTANT: The Query Tool Help format is ideal for advanced users who use SQL*Plus, TOAD, and similar tools. As the database comments require a large amount of Oracle tablespace, you must regenerate Query Tool Help only after a successful regeneration of Noetix views.


• Should Microsoft Help be generated? Please answer Y or N.

• Should HTML Help be generated? Please answer Y or N.

• Should we run Answer Builder? Please answer Y or N.

• Should we run Answer Builder if warning occur in Stage 4? Please answer Y or N.

• Overwrite configuration files using previous settings from the database? (Y/N)

NOTE: This parameter value is ignored in scheduled regenerations, and the role prefixes and settings for Noetix query users will be saved.

• Which stages do you want the installer to run?

NOTE: Choose which type of regeneration you want to schedule, and type A, B, or H: A: This option will run Stages 2 through 4 of the generation process and regenerate answers and the Noetix Help File. B: This option will run only Noetix Answer Builder and regenerate the answers. H: The option will regenerate only the Noetix Help File in the formats specified earlier.

The values you typed will be populated into cparam.sql, and you can continue to the next step.


Step 3: Populate Password FileIMPORTANT: This step is relevant only if the type of your unattended install environment is standard. Skip to Step 4 if you have an EBSO environment at your site.

This step populates a password file with the user accounts and passwords that are required during a regeneration.

The script you run in this step will gather and validate the passwords and save them to the noetix_install_dir/autorun/cpw.sql file. Permissions are automatically set on this file so that the passwords are secure and accessible only to the noetix_unix user.

To populate the password file: 1. Change the present working directory to the noetix_install_dir directory on the

computer containing the NoetixViews scripts.



2. Run the script to gather passwords: start igetpw.sql

3. Type the passwords for the users as required by the script, and then press ENTER. The list of users that is displayed varies depending on the user configuration at your site. However, this list usually includes your APPS accounts.

4. Exit SQL*Plus.

The values you typed will be populated into cpw.sql, and you can continue to the next step.


Step 4: Grant Permissions to APPS ObjectsIMPORTANT: This step is relevant only if you have an EBSO environment at your site. Skip to Step 5 if you have a standard environment.

This step is required to grant the NOETIX_SYS user the permissions to the Oracle APPS schema objects if the version of Oracle E-Business Suite has been upgraded or any patch has been applied to the APPS schema. If there has not been an upgrade, you need not perform the following steps, and you can skip to Step 5.

To grant permissions to APPS objects:1. Using SQL*Plus, log on to the APPS schema.

2. Run the iappspkg.sql script.

3. Run scripts to grant the NOETIX_SYS user the permissions to the APPS schema objects. These scripts are available with the EBSO support providers. For more information about these scripts, contact Noetix Technical Support.

Step 5: Define Concurrent ProgramThis step defines a concurrent program that will be used to run your scheduled Noetix views regeneration. You will be prompted to type the APPS user name and password, as well as other necessary information to set up the concurrent program.

To define the concurrent program:1. Change the present working directory to the noetix_install_dir directory.



3. Run the script to load the concurrent program: start iconcmgr.sql

http://support.noetix.com/



• Please enter a valid Oracle Apps user account

NOTE: This account is typically APPS.

• Please enter the Oracle User Password for the Apps User

• Please enter the name of the Oracle Application you wish to associate with this Concurrent Program definition. Use the application_short_name to define this item.

NOTE: Type the short name of the application that you created in Step 1: Set Up Custom Application.

• Which Request Group do you want to attach this Concurrent Program to?

NOTE: Type the name of the request group that you want to add the concurrent program definition to.

• Please enter the name of the Oracle Application you wish to associate with the Request Group specified above. Use the application_short_name to define this item.

Answers to the remaining prompts are taken from the choices you made while performing Step 2: Populate Parameter File. Accept these defaults; you can change them in each Concurrent Manager job that you run. If some responses are wrong, you can correct them now; however, it is recommended that you correct the responses while populating the parameter file.



• Please enter the NOETIX_SYS user name.

• Please enter the name of the database where the NOETIX_SYS user resides.

NOTE: Type the TNS name of this database.


• Please enter the default tablespace for the NOETIX_SYS.

• Please enter the NoetixViews Administrator Install Path.

NOTE: Specify the full path to the UNIX directory where the NoetixViews scripts reside (the noetix_install_dir directory).

5. Verify the information that you have entered. If the information is incorrect, exit the SQL*Plus session (press CTRL+C), and start Step 5 again. If the information is correct, press ENTER to continue.

After all the values have been entered, the script will use the parameters you have entered to define the concurrent program, and you can continue to the next step.


Schedule Regeneration in Concurrent ManagerTo schedule your Noetix views regeneration, you need to submit a Concurrent Manager request.

IMPORTANT: If you are scheduling a regeneration and think that variables that do not get displayed by the Concurrent Manager (such as passwords) may have changed since your initial setup, verify that the parameters and passwords saved in the cparam.sql and cpw.sql files are still correct. If you need to change the NOETIX_SYS password or other parameters, perform Step 2: Populate Parameter File again. To change the APPS or other administrative passwords, perform Step 3: Populate Password File again.

To schedule the Concurrent Manager job:1. Log on to Oracle E-Business Suite as an Oracle E-Business Suite user with access

to the request group.

2. Submit the <name> request.

3. Type or verify the following values.

• NOETIX_SYS Name

• NOETIX_SYS Database

• Default Tablespace

• NOETIX_SYS Language

• Install Global Roles?

• Install XOP Roles?

• Install Standard Roles?

• Install Individual Inventory Roles?

• Add the Projects Multi-Currency Columns (11.5.8+ only)?

• Generate Database Comment Help?


• Generate Microsoft Help?

• Generate HTML Help?

• Run Noetix Answer Builder?

• Continue to next stage on warnings?

• Installation Option

NOTE: Choose which type of regeneration you want to schedule, and type either A, B, or H: A: This option will run Stages 2 through 4 of the generation process and regenerate answers and the Noetix Help File. B: This option will run only Noetix Answer Builder and regenerate the answers. H: The option will regenerate only the Noetix Help File in the formats specified earlier.

For more information about these options, see Step 2: Populate Parameter File.

4. Schedule and submit the Concurrent Manager request.

NOTE: If any errors are detected in Stage 4 of the Noetix views regeneration, the Noetix Help File will not be regenerated. As a workaround, after completing Stage 4 of the Noetix views regeneration, you must first run the ifix4sts.sql script to override Stage 4 errors and then manually regenerate the Noetix Help File. The ifix4sts.sql script is located in the same directory where the install4.sql script is present. For information about manually regenerating the Noetix Help File using scripts, see Option 2: Regenerate Help Using Scripts.

You may repeat these steps to set up additional Concurrent Manager jobs. View the status and log of the job in Oracle E-Business Suite to ensure that the regeneration has been successful. The job can be modified or deleted. For information, refer to the Oracle E-Business Suite documentation.


Option 4: Regenerate Using Scheduled Cron Job

Regenerating Noetix views using Cron, the UNIX scheduling service, requires a number of initial tasks to set up the environment and parameters to be used. After this initial setup is completed, regenerations can be run on a scheduled basis with no user input required.

NOTE: If you have upgraded NoetixViews for Oracle E-Business Suite (NoetixViews) and have used the Cron earlier to regenerate your views, you need to repeat the last step in Step 1: Create UNIX User and Directory. Subsequently, you need to perform the procedures listed in Step 2: Populate Parameter File, Step 3: Populate Password File (for a standard install environment only), Step 4: Grant Permissions to APPS Objects (for an Oracle E-Business Suite On Demand Service (EBSO) environment only), Step 5: Set Up Cron Environment, and Schedule Regeneration in Cron. You should perform these procedures only after you have upgraded NoetixViews. For information about upgrading NoetixViews, see Upgrade the Software in “Installing NoetixViews for Oracle E-Business Suite.”

This method will involve setting up a Cron job from a UNIX environment.

Initial SetupThe initial setup needs to be done once for each NOETIX_SYS schema. After this setup has been done, for subsequent regenerations, go to Schedule Regeneration in Cron to start the regeneration.

Initial setup involves the following steps:

• Step 1: Create UNIX User and Directory• Step 2: Populate Parameter File• Step 3: Populate Password File (for a standard install environment only)• Step 4: Grant Permissions to APPS Objects (for an EBSO environment only)• Step 5: Set Up Cron Environment


Step 1: Create UNIX User and DirectoryYou will need to create a user account and directory in the UNIX-based computer you would use for your regeneration tasks.

To create the UNIX user and directory:1. Create a UNIX user account exclusively for Noetix administrative tasks.

For the purposes of this document, this account is referred to as noetix_unix, but you can name the account anything you want.

2. Grant this user account permissions to the crontab file. This is necessary because you will be using this account to run the Cron job.

3. Log on as the noetix_unix account you have created.

4. Create a directory to be used exclusively for NoetixViews.

For the purposes of this document, this directory will be called noetix_install_dir.

5. Load the NoetixViews scripts into the noetix_install_dir directory following the steps described in Load the Software on UNIX in “Installing NoetixViews for Oracle E-Business Suite.”

Step 2: Populate Parameter FileThis step will populate a parameter file with default values for all of the information that Noetix views regeneration will need, such as regeneration options and user names. These default values appear when setting up your scheduled regeneration jobs (if they have not been set up at the time of the previous generation). You can change them in a later step for each scheduled job you create.

The script you run in this step will gather and validate the parameters and save them to the noetix_install_dir/autorun/cparam.sql file. You will have to provide all the required parameters (except passwords) for a scheduled regeneration. While scheduling a regeneration, the Noetix System Administration User password will be taken from the secured cparam.sql file.


To populate the parameter file:1. Change the present working directory to the noetix_install_dir directory on the

computer containing the Noetix views generation scripts.



3. Run the script to gather parameters: start igetprm.sql


• Please enter the <NOETIX_SYS user> password.

• Please enter the name of the database where the <NOETIX_SYS> user resides.

NOTE: Type the Transparent Network Substrate (TNS) name of this database.



• Please enter the default tablespace for the <NOETIX_SYS> user.

• Please enter the Noetix Administrator Installation Path.

NOTE: Type the full path to the noetix_install_dir directory, to which the NoetixViews scripts were loaded.

• Please enter the APPS user name.

• Please enter the language used in the install stage 4 processing.


• Should Global views be installed (if available)? Please answer Y or N.

NOTE: If global form of Noetix views has been purchased, should they be generated? Valid responses are Y and N.

• Should XOP views be installed (if available)? Please answer Y or N.

NOTE: If Cross Operations Extension (XOP) form of Noetix views has been purchased, should they be generated? Valid responses are Y and N.

• Should Standard views be installed? Please answer Y or N.

• Should standard INV views be installed (if available)? Please answer Y or N.

NOTE: If NoetixViews for Oracle Inventory has been purchased, should organization-specific views be generated? Valid responses are Y and N.

• Should Projects Multi-currency columns be installed (if available)? Please answer Y or N.

NOTE: If NoetixViews for Oracle Projects has been purchased, Oracle E-Business Suite 11.5.8 or later detected, and Oracle Projects installed, should the multi-currency columns be generated? Valid responses are Y and N. Changing the multi-currency option during a regeneration of views impacts reports written against the views for Oracle Projects. For information, see Changing the Multi-Currency Option While Regenerating Noetix Views.

• Should Database comments be generated? Please answer Y or N.

IMPORTANT: The Query Tool Help format is ideal for advanced users who use SQL*Plus, TOAD, and similar tools. As the database comments require a large amount of Oracle tablespace, you must regenerate Query Tool Help only after a successful regeneration of Noetix views.

• Should Microsoft Help be generated? Please answer Y or N.

• Should HTML Help be generated? Please answer Y or N.

• Should we run Answer Builder? Please answer Y or N.

• Should we run Answer Builder if warning occur in Stage 4? Please answer Y or N.


• Overwrite configuration files using previous settings from the database? (Answer Y for Yes or N for No)

NOTE: This parameter value is ignored in scheduled regenerations, and the role prefixes and settings for Noetix query users will be saved.

• Which stages do you want the installer to run?


The values you typed will be populated into cparam.sql, and you can continue to the next step.


Step 3: Populate Password FileIMPORTANT: This step is relevant only if the type of your unattended install environment is standard. Skip to the Step 4 if you have an EBSO environment at your site.

This step populates a password file with the user accounts and passwords that are required during a regeneration.

The script you run in this step will gather and validate the passwords and save them to the noetix_install_dir/autorun/cpw.sql file. Permissions are automatically set on this file so that the passwords are secure and accessible only to the noetix_unix user.

To populate the password file:1. Connect to the database, and do the following:

a. Change the present working directory to the noetix_install_dir directory on the computer containing the NoetixViews scripts.

b. Using SQL*Plus, connect to the database as the Noetix System Administration User: sqlplus <username>/<password>@<dbconnectstring>


2. Run the script to gather passwords: start igetpw.sql

3. Type the passwords for the users as required by the script, and then press ENTER. The list of users that is displayed will vary depending on the user configuration at your site. However, this list usually includes your APPS accounts.

4. Exit SQL*Plus.

The values you typed will be populated into cpw.sql, and you can continue to the next step.


Step 4: Grant Permissions to APPS ObjectsIMPORTANT: This step is relevant only if you have an EBSO environment at your site. Skip to Step 5 if you have a standard environment.

This step is required to grant the NOETIX_SYS user the permissions to the Oracle APPS schema objects if the version of Oracle E-Business Suite has been upgraded or any patch has been applied to the APPS schema. If there has not been an upgrade, you need not perform the following steps, and you can skip to Step 5.

To grant permissions to APPS objects:1. Using SQL*Plus, log on to the APPS schema.

2. Run the iappspkg.sql script.

3. Run scripts to grant the NOETIX_SYS user the permissions to the APPS schema objects. These scripts are available with the EBSO support providers. For more information about these scripts, contact Noetix Technical Support.

Step 5: Set Up Cron EnvironmentThe next step is to create an environment script required for the regeneration. The script you run creates the cronenv.sh file, which is stored in the directory containing the Noetix views generation scripts. You need to edit and test this file to ensure that it functions correctly in your environment.

To set up the Cron environment:1. Change the present working directory to the noetix_install_dir directory.

2. Run the script to set up the environment: icronenv.sh

This script does not prompt you for any information.

http://support.noetix.com/


3. With the UNIX editor of your choice, manually edit the cronenv.sh file to suit your environment. You need to verify that the values listed for your Oracle_SID, Oracle_BASE, PATH (path to SQL*Plus), and other environment variables are correct. Modify them if they are incorrect, and then save the file.

4. To test if the environment has been set up correctly, do the following:

a. Type the following at the command prompt to run the cronenv.sh file, and press ENTER: . cronenv.sh

b. Type the following at the command prompt to start SQL*Plus and press ENTER: sqlplus

If this command successfully starts SQL*Plus, then the environment has been set up correctly.

5. Exit SQL*Plus.

Schedule Regeneration in Cron To schedule your NoetixViews regeneration, you need to run a script to add a regeneration job in the crontab file for your user account.

IMPORTANT: If you are scheduling a regeneration and think that variables that do not get displayed (such as passwords) may have changed since your initial setup, verify that the parameters and passwords saved in the cparam.sql and cpw.sql files are still correct. If you need to change the NOETIX_SYS password or other parameters, perform Step 2: Populate Parameter File again. To change the APPS or other administrative passwords, perform Step 3: Populate Password File again.

To set up the scheduled Cron job:1. Change the present working directory to the noetix_install_dir directory.

2. Run the script to create the Cron job: icrontab.sh


3. Answer the following prompts. To accept the default value, press ENTER; otherwise, type a value (Y or N) for each item when prompted, and press ENTER.

• Install Global Extension Roles?

• Install Cross Operations Extension (XOP) Roles?

• Install Standard Roles?

• Install Individual Inventory Roles?

• Generate Database Comments?

• Generate Microsoft Help?

• Generate HTML Help?

• Run Answer Builder (If Answers Purchased)?

• Continue to next stage on warnings?

• Installation Option? Valid values (A,B,H)


• What are your scheduling options for your Cron Job?

NOTE: Set the schedule for your regeneration by giving values for the following prompts. To indicate no preference for a prompt, type an asterisk (*). For example, if you wanted the regeneration to run every day at 11:00 P.M., you would type 23 for the hour and an * for every other value.


You must specify an appropriate numeric value for at least one of the following entries (that is, you cannot type an * for every prompt). If you have any questions about schedule options, consult the man pages for the crontab file. What minute of the hour do you want to schedule the cron job? Valid Values (0-59, or *) What hour of the day do you want to schedule the cron job? Valid Values (0-23, or *) What day of the month do you want to schedule the cron job? Valid Values (1-31, or *) What month of the year do you want to schedule the cron job? Valid Values (1-12, or *) What day of the week do you want to schedule the cron job? Valid Values (0-6 with 0=Sunday, or *)

For more information about these prompts, see Step 2: Populate Parameter File.

4. Verify the information that you have entered. If the information is incorrect, exit the SQL*Plus session (usually by pressing CTRL+C), and start this stage again. If the information is correct, press ENTER to continue.


An entry will be created in your crontab file.

#n#n Note: all comments will be included in your cron entry harmlessly#n use * for any value to indicate no preference#n#n min : minute (0-59),#n hr : hour (0-23),#n day : day of the month (1-31),#n mon : month of the year (1-12),#n dotw : day of the week (0-6 with 0=Sunday).#n#n Use: #n#n min hr day mon dotw $noetixdir/inst4cron.sh Y Y Y N N N N Y Y Y A#n#n Sample: 30 23 * * 0 $noetixdir/inst4cron.sh Y Y Y N N N N Y Y Y A#n#n Means 11:30 PM every Sunday#n#n Noetix cron entry:#n# The following parameters have been entered for the Noetix Automated Installer# cron job on DDD MMM DD HH:MM:SS PDT YYYY# Parameters# 1 Install XOP Roles - Y# 2 Install Ind. INV Roles - Y# 3 Install Global INV Role - Y# 4 Create Multi-Currency Columns (11.5.8+) - Y# 5 Gen Database Comments - Y# 6 Generate Microsoft Help - Y# 7 Generate HTML Help - Y# 8 Run Noetix Answer Builder - Y# 9 Continue to next stage on warnings - Y# 10 Overwrite Configuration Files in Install Dir - Y# 11 Installation Option - B#0 9 24 10 5 /export/home/users/username/install_dir/inst4cron.sh Y Y Y Y Y Y Y Y Y Y B


NOTE: If any errors are detected in Stage 4 of the Noetix views regeneration, the Noetix Help File will not be regenerated. As a workaround, after completing Stage 4 of the Noetix views regeneration, you must first run the ifix4sts.sql script to override Stage 4 errors and then manually regenerate the Noetix Help File. The ifix4sts.sql script is located in the same directory where the install4.sql script is present. For information about manually regenerating the Noetix Help File using scripts, see Option 2: Regenerate Help Using Scripts.

You may repeat these steps to set up additional scheduled jobs. Each time you run this script, it will add another regeneration entry to your crontab file.

View Regeneration StatusYou can view the status of a regeneration job while it is running, or later, by looking at the log files. A log file is created for each job that runs, regardless of whether it is successfully completed. The log file names contain the date and time when the job started running.

To view the regeneration logs:1. Navigate to the log directory under the noetix_install_dir directory. You can see a

separate file for each job. The log files are named in the cron<YYYYMMDDhhmmss>.log format.

2. Open the log file corresponding to the date and time when the job started. You can view the tasks that have been completed during the run.

3. To view the exit status and errors, scroll to the bottom of the file.

Edit or Delete a Cron JobIf you need to edit a job you have set up (for example, rescheduling a regeneration or changing the parameters used) or delete it, you can manually edit the job entry in the crontab file.

To edit or delete a scheduled Cron job:1. Log on to UNIX as the user who created the job that you want to edit or delete.

2. Change the present working directory to noetix_install_dir/autorun.


3. Type the following to edit or delete a Cron job: crontab -e

Press ENTER. An output of all the Cron jobs that the user has created will be displayed.

4. Navigate to the Noetix regeneration job you want to edit or delete. To quickly find the beginning of the first Noetix job, search for #n Noetix Cron entry. The Cron job parameters will be displayed.

5. Edit the job. If you want to delete the job, delete the whole entry (all lines beginning with #n, as well as the Noetix automated installer parameters).

6. Save the crontab file, and exit.


Regenerate Noetix Answers/Help File Separately

This section provides information about the tasks to be performed after the regeneration of views, such as, regenerating Noetix answers and Noetix Help File.

Regenerate Noetix AnswersAnswers should be regenerated after the regeneration of views, so that Noetix QueryServer (NQS) objects, such as query users, are synchronized with the updated NoetixViews for Oracle E-Business Suite (NoetixViews) metadata.

Answers can be regenerated in the following ways:

• Run Noetix Answer Builder Wizard from NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator). After the metadata for prebuilt reports is created, you must generate the metadata into NQS and NWQ.

• Regenerate answers using scripts.

• Use Concurrent Manager or Cron to schedule regeneration.

Option 1: Regenerate Answers Using NoetixViews AdministratorYou can regenerate answers by running Noetix Answer Builder Wizard from NoetixViews Administrator. After answers have been regenerated, make sure that you run Noetix Generator for Noetix Platform—Oracle E-Business Suite Edition (Noetix Generator) to generate the metadata into NQS and NWQ. For more information, see the Noetix Generator for Noetix Platform Administrator Guide for Oracle E-Business Suite.

This procedure also generates your updated views and query users into NQS and NWQ.


To run Noetix Answer Builder from NoetixViews Administrator:1. Click Start > All Programs > NoetixViews > NoetixViews Administrator. The

NoetixViews Administrator welcome dialog box is displayed.

2. On the Tools menu, click Answer Builder or click on the toolbar. The Noetix Answer Builder Wizard welcome page is displayed. Click Next.

3. On the next page, the Answer Builder check box is selected by default. The check box is unavailable for selection. Click Next.


NOTE: The Continue if warnings detected check box is displayed only in Stage 4 of the generation process. The check box is not displayed if you are running Noetix Answer Builder Wizard after you have completed Stage 4.

4. On the next page, click Finish

.

5. When the Noetix Answer Builder process is completed successfully, a message is displayed to inform you the same. Click OK. After running Noetix Answer Builder successfully, you must run Noetix Generator for Noetix Platform-Oracle E-Business Suite Edition (Noetix Generator) on the NQS computer.


Option 2: Regenerate Answers Using ScriptsTo regenerate answers using scripts:1. Using SQL*Plus, connect to the database as the Noetix System Administration

User (Type N): connect <username>/<password>@<dbconnectstring>


2. Type start ianswers.sql, and then press ENTER.

NOTE: After the metadata is created successfully, run Noetix Generator for Noetix Platform—Oracle E-Business Suite Edition (Noetix Generator) to generate metadata into NQS and NWQ.

Option 3: Regenerate Answers Using Scheduled JobTo regenerate answers using a scheduled Concurrent Manager or Cron job:1. Ensure you have completed all the initial setup steps for scheduling a Noetix views

regeneration using Concurrent Manager or Cron:

• For Concurrent Manager, see Initial Setup.

• For Cron, see Initial Setup.

2. Schedule a new job only for regenerating answers. Ensure the following:

• The regeneration process for Noetix views has already been completed before scheduling the job for regenerating answers,

• When prompted whether to generate answers by running Noetix Answer Builder, type Y.

• When prompted whether to run Noetix Answer Builder despite warnings in Stage 4, type Y.


For information about defining a job in the Concurrent Manager, see Schedule Regeneration in Concurrent Manager. For information about defining a job in Cron, see Schedule Regeneration in Cron.

Regenerate Noetix Help FileThe Noetix Help File should be regenerated when:

• NoetixViews has been upgraded or the views have been regenerated.• You recognize a need for an additional Noetix Help File format.

During Noetix views regeneration, you are given the option to regenerate the Noetix Help File. The Noetix Help File can also be regenerated independently of a Noetix views regeneration using the instructions in this section. The Noetix Help File can be regenerated using NoetixViews Administrator, scripts, or a scheduled regeneration method.

If you are regenerating the Microsoft WinHelp format, NoetixViews Administrator can regenerate it in one step, while all other methods will require transferring files to a Windows-based computer to be compiled using a separate wizard. Instructions for generating Noetix Help File using each regeneration method can be found in the following sections.

NOTE: If any errors are detected in Stage 4 of the Noetix views regeneration, the Noetix Help File will not be regenerated. However, if you intend to override Stage 4 errors and regenerate the Noetix Help File, you must first run the ifix4sts.sql script and then manually regenerate the Noetix Help File. If you have regenerated Noetix views using NoetixViews Administrator, the ifix4sts.sql script is located in your NOETIX_SYS user directory (by default, C:\Program Files\Noetix Corporation\NoetixViews\Installs\<NOETIX_SYS_TNS>). If you have regenerated NoetixViews using scripts, the ifix4sts.sql script is located in the same directory where the install4.sql script is present.


Option 1: Regenerate Help Using NoetixViews AdministratorTo regenerate Noetix Help File from NoetixViews Administrator:1. Click Start > All Programs > NoetixViews > NoetixViews Administrator. The


2. If prompted, select Use Existing Account, and log on with the user name and password for the Noetix System Administration User (usually NOETIX_SYS). Also indicate the TNS name where the Noetix System Administration User schema resides.

3. On the Tools menu, click Generate Online Help. Highlight the help format that you want to generate. NoetixViews Administrator will perform the processes necessary to regenerate a help file in the specified format.

4. Publish the Noetix Help File to users as follows, depending on the help formats generated:

• Publish the Microsoft WinHelp help file, if generated: After the Noetix Help is generated in the Microsoft WinHelp format, the noetix.hlp file is located in <BASE_INSTALL_DIR>\<ACCOUNT_TNS>\MsHelp, where <BASE_INSTALL_DIR> is the location where you installed NoetixViews Administrator and <ACCOUNT_TNS> is the name of the Noetix System Administration User (usually NOETIX_SYS) + _ + the TNS Name of the database instance on which the user resides. The noetix.hlp file will need to be moved to a shared server drive and a shortcut to the shared file placed on the desktop of each Noetix query user’s computer.

EXAMPLE: C:\Program Files\Noetix Corporation\NoetixViews Administrator\Installs\NOETIX_SYS_dev.seattle\MsHelp


• Publish the HTML help file, if generated: After the Noetix Help File is generated in the HTML Help format, the HTML files are located in <BASE_INSTALL_DIR>\<ACCOUNT_TNS>\htmlhelp, where <BASE_INSTALL_DIR> is the location where you installed NoetixViews Administrator and <ACCOUNT_TNS> is the name of the Noetix System Administration User (usually NOETIX_SYS) + _ + the TNS Name of the database instance on which the user resides. Point your browser to <BASE_INSTALL_DIR>\<ACCOUNT_TNS> \htmlhelp\help\noetix.htm to view the HTML Help. EXAMPLE: C:\Program Files\Noetix Corporation\NoetixViews\Installs\NOETIX_SYS_dev.seattle\htmlhelp These HTML files will need to be published on a Web server and users must be notified of this location. To publish the files, move the entire htmlhelp directory tree to a directory on your network that is accessible to your Web browser. Instruct users to open the /htmlhelp/help/noetix.htm page using a Web browser.

• The Query Tool Help, if generated, will automatically be available to those with the applicable tools: No additional steps are necessary.

Option 2: Regenerate Help Using ScriptsTo regenerate help using scripts:1. Using SQL*Plus, connect to the database as the Noetix System Administration

User (Type N): connect <username>/<password>@<dbconnectstring>


2. At the SQL prompt, type start <sql script>, and then press ENTER, where <sql script> specifies the script file used for generating the Noetix Help File.


The following script files are available for Noetix Help File generation:

3. Answer any prompts asked by the script.

4. Repeat this step to generate additional help formats, if needed.


You will need to compile and publish the Microsoft WinHelp help file and publish the HTML help file, if generated, using the instructions in the following sections.


The Noetix Easy Help Wizard, which is installed along with NoetixViews Administrator, will transfer the Noetix Help File for Windows source file (.rtf ) from the server to the Windows-based client computer using the File Transfer Protocol (FTP). The wizard compiles the file and generates the Noetix Help File locally. After generation, the wizard gives you an option to create a shortcut for the Noetix Help File on your desktop.

The Noetix Easy Help Wizard can be used if your Windows-based client and the server computers where you installed NoetixViews Administrator use Transmission Control Protocol/Internet Protocol (TCP/IP) and the directory where you installed NoetixViews Administrator is accessible to your FTP server computer.

Help Format SQL Script

All Help Formats iallhlp.sql

Microsoft WinHelp Help imshlp.sql

HTML Help ihtmlhlp.sql

Query Tool Help icomhlp.sql


To transfer and compile the Microsoft WinHelp format:1. Log on to the Windows computer where NoetixViews Administrator is installed.

2. Click Start > All Programs > NoetixViews > EasyHelp Wizard. The Noetix Easy Help Wizard appears. Click Next.

3. The next page prompts you for a UNIX user name, password, and URL of the server on the network to transfer the source file generated during the generation to a client where it will be compiled. The user specified must have access to the server directory where the noetix.rtf file exists. Click Next to continue.


4. The next page displays the path to the installation directory where the scripts and noetix.rtf file are currently located. Confirm that the installation directory on the text field is correct. Click Next to continue.

5. The next page displays your choices for the user name, server, and directory where the scripts and the noetix.rtf file are located. To view the Noetix Help File after it has been generated, select the check box. Click Finish to transfer and compile the Noetix Help File.


6. If the help source file (noetix.rtf ) is present in <installation_folder>\Installs\MsHelp and you transfer the help source file again or the generated Noetix Help File (noetix.hlp) is present in the <installation_folder>\Installs\MsHelp and you regenerate the Noetix Help File, a confirmation message is displayed prompting you to take a backup of the previous files.

In the message:

• Click Yes to create a backup of the help source file (noetix.rtf ) or the Noetix Help File (noetix.hlp). The backup files will be created in <installation_folder>\Installs\MsHelp\backup. This option is recommended.

• Click No to overwrite the files with the new ones without creating a backup of the existing files.

IMPORTANT: The backup files in <installation_folder>\Installs\ MsHelp\backup will be overwritten on subsequent generation of the Noetix Help File. You must manually archive the backup files before regenerating the Noetix Help File using the wizard.

7. After the Noetix Help File is generated, you will have the option of creating a desktop shortcut to the Noetix Help File on your computer running Windows. Click Yes, if you want to create a shortcut.

Next, publish the compiled Noetix Help File to users.

To publish the Noetix Help File:1. Navigate to the noetix.hlp file in

<BASE_INSTALL_DIR>\<ACCOUNT_TNS>\MsHelp, where <BASE_INSTALL_DIR> is the location where you installed NoetixViews Administrator and <ACCOUNT_TNS> is the name of the Noetix System Administration User (usually NOETIX_SYS) + _ + the TNS Name of the database instance on which the user resides.

EXAMPLE: C:\Program Files\Noetix Corporation\NoetixViews\Installs\NOETIX_SYS_dev.seattle\MsHelp

2. Move the noetix.hlp file to a shared server drive. (Each time you regenerate NoetixViews, replace the single version of this file on the server.)

3. Distribute a shortcut to the shared file to all Noetix query users.


Publish HTML Help FormatThe HTML help format does not need to be compiled, but will need to be published to users.

To publish the HTML help format:1. Navigate to the htmlhelp directory within the NOETIX_SYS user directory. (You

can point your browser to htmlhelp\help\noetix.htm to view the HTML Help.)

EXAMPLE: C:\Program Files\Noetix Corporation\NoetixViews\Installs\NOETIX_SYS_dev.seattle\htmlhelp

2. Publish the files to a Web server or shared server drive. To do this, move the entire htmlhelp directory tree to a directory on your network that is accessible to your Web browser.

3. Instruct users to open the /htmlhelp/help/noetix.htm page using a Web browser.

Option 3: Regenerate Help Using Scheduled JobTo regenerate help using a scheduled Cron or Concurrent Manager job:1. Ensure you have completed all the initial setup steps for scheduling a Noetix views

regeneration using Cron or the Concurrent Manager:

• For Cron, see Initial Setup.

• For the Concurrent Manager, see Initial Setup.

2. Schedule a new regeneration job only for regenerating the help file. Ensure the following:

• The regeneration process for Noetix views has already been completed before scheduling the job for regenerating the help file.

• When prompted whether to generate each format of the help file, type Y for the help formats you want to generate.


• When prompted for your Generation option, select H for Generate Selected Help Content Only. When choosing this type of regeneration, the answers you provide for prompts that do not apply, such as whether to generate Noetix Cross Operations Extension (XOP) roles, will be ignored. Only the Noetix Help File will be regenerated.

For information about defining a job in Cron, see Schedule Regeneration in Cron. For information about defining a job in the Concurrent Manager, see Schedule Regeneration in Concurrent Manager.


You will need to compile and publish the Noetix Help File and publish the HTML help format, if generated, using the instructions in the following sections.


The instructions to compile and publish the Microsoft WinHelp help file are the same as mentioned earlier when you had regenerated Noetix Help File using scripts. For information, see Compile and Publish Microsoft WinHelp Format.

Chapter 8

Uninstalling the Software

This chapter describes how to uninstall NoetixViews for Oracle E-Business Suite (NoetixViews).


OverviewThis chapter contains information on how to uninstall NoetixViews for Oracle E-Business Suite (NoetixViews) from a computer running Microsoft Windows or UNIX.

Uninstall the Software from Windows

If, for some reason, you need to uninstall NoetixViews for Oracle E-Business Suite (NoetixViews), you can do so with the NoetixViews Uninstall wizard.

To uninstall NoetixViews:

1. Click Start > All Programs > NoetixViews > Uninstall. The NoetixViews Uninstall wizard appears.

2. On the Welcome to the NoetixViews Uninstall page, click Next to begin the uninstallation.

Chapter 8: Uninstalling the Software 309

3. On the Uninstall NoetixViews page, verify the installation path, and click Uninstall.


4. On the Uninstalling page, click Next when the button becomes available, which will be when the uninstallation is complete. You can click Show Details to view the actions performed by the uninstall wizard. On clicking Show Details, the detailed information about the uninstallation is displayed. To copy the log at a point, you can right-click the information and click Copy Details To Clipboard. You can then paste and save the log in any text-editing program.

Chapter 8: Uninstalling the Software 311

5. On the Uninstallation Complete page, click Finish. The wizard exits.

NOTE: The uninstallation process removes only NoetixViews from your computer. However, the NOETIX_SYS schema in the database will not be affected. Contact your system administrator to drop the schema.


Uninstall the Software from UNIX

For generation of Noetix views on a UNIX-based computer, you only need to copy the required script files to the installation directory and generate the views using those scripts. There is no component installed on the computer that needs to be uninstalled. Therefore, uninstalling NoetixViews for Oracle E-Business Suite (NoetixViews) on a UNIX-based computer comprises only deleting the Noetix installation directory in which the scripts were copied and, consecutively, the views generated.

NOTE: This procedure will remove only NoetixViews from the UNIX-based server. However, the NOETIX_SYS schema in the database will not be affected. Contact your system administrator to drop the schema.

Appendix A

Module-Specific Information


NoetixViews for Oracle General Ledger

NOTE: In Oracle E-Business Suite Release 12, the concept of set of books has been replaced by ledger. In this guide both “set of books” and “ledger” have been used interchangeably to refer to the same concept.

NoetixViews for Oracle General Ledger provides some special features not available in other views. This section describes the additional considerations involved with the General Ledger views. These considerations involve the extra data security on the General Ledger views and the views of archived data.

Appendix A: Module-Specific Information 315

General Ledger Data SecurityData security, the ability to restrict access to data, is handled in Noetix views for Oracle General Ledger in three ways:

• Assigning roles to a query user.

• Assigning Accounting Flexfield security rules to a query user.

• Assigning accounts to a budget organization.

RolesEach ledger in General Ledger has its own set of views and each set is associated with a role. A role prefix is assigned to each of these sets of views belonging to a specific role. These role prefixes are assigned during the view generation process.

This is a security feature, since each user can be restricted to accessing data only within certain ledger. This is done by assigning roles to users. When you assign roles, even the Noetix System Administration User must have the General Ledger role assigned to access General Ledger data.

The concept of a role is an Oracle Database feature. The Noetix query users that are granted a role automatically have access to all the views assigned to that role. Roles are assigned to Noetix query users after generation. For more information about assigning roles to Noetix query users, see step 12 in “Add a Noetix Query User Using an Existing User” in “Noetix Query User Management.”


Accounting Flexfield Security RulesThe second level of security in NoetixViews is based on Accounting Flexfield security rules. NoetixViews uses the flexfield security rules in the same manner in which the concept of flexfield security rules is implemented in Oracle E-Business Suite. For more information about flexfield security rules, see Oracle documentation.

To use this security method to prevent access to particular accounts for specific Noetix query users, first define the flexfield security rules in the Oracle E-Business Suite Object Library. These rules allow you to specify ranges of values to be included or excluded for individual Accounting Flexfield segments. You can set up any number of these rules. Although Oracle E-Business Suite allows defining security rules on any flexfield, NoetixViews uses only rules defined for the Accounting Flexfield.

After you have defined the flexfield security rules and generated the views, the next step is to assign security rules to Noetix query users. When you set up Noetix query users, first assign them the appropriate roles, and then assign the appropriate General Ledger security rules. This can be done using the Security Manager dialog box. For more information about assigning security rules, see step 11 in “Add a Noetix Query User Using an Existing User” in “Noetix Query User Management.”

When the views are generated, the generation procedure copies references to the flexfield security rules into the views. If you add a flexfield security rule in Oracle E-Business Suite to a new segment of the Accounting Flexfield or create a ledger, the views must be regenerated before they incorporate the changes.

With any change or addition to flexfield security rules in Oracle E-Business Suite, you should review and update users’ access to General Ledger data in NoetixViews.

When views are run in the query tool, they dynamically check the flexfield security rules that have been assigned to the user running the query. This ensures that if flexfield security rules are changed for the user in NoetixViews Administrator, the effect is immediate. There is no need to regenerate views when the flexfield security rules are changed.

Budget OrganizationsThe third type of data security is associated with General Ledger budget organizations. This security is intended to be used to limit managers to a view of only the ledger data for which they have budget authority. This can be accomplished by letting managers have access only to pre-canned queries that are limited to their budget organization.


The creation of budget organizations and the assignment of ranges of accounts to them is a standard General Ledger feature. Refer to Oracle documentation for more information.

The GL_Org_Balances, GL_Org_Budgets, and GL_Org_Budget_To_Actuals views determine, while running, which accounts are authorized for a given budget organization. No special generation steps are necessary to make these views work.

Archived DataGeneral Ledger has a feature that archives balances and journal entries. This procedure copies a previous year's data to special archive tables. A separate procedure can purge the data from these archive tables. The archived views look at this archived data.

If the data in the archive tables has been copied to tape and then purged, it needs to be restored to these tables before it can be queried. With the archived views, the data does not have to be re-integrated with the standard balances and journal entry tables before it can be queried.

IMPORTANT: If you have migrated your Oracle E-Business Suite instance from version 11.5.10.2 to Release 12, you must regenerate the GL_Archived_Balances and GL_Archived_Je_Lines views after the first time you purge your archived data. Otherwise, these views will return an error when run. You do not need to regenerate these views after running the purge process subsequently.

About Access to Accounting DataNOTE: In this section, the Oracle Database User, Oracle E-Business Suite Authenticated User, and Oracle E-Business Suite Responsibility type Noetix query users are referred as Type U, Type A, and Type R respectively.

Security rules defined on the Accounting Flexfield control access to accounting data in Oracle E-Business Suite. In NoetixViews, these rules are enforced by individual Noetix views for Oracle General Ledger that supports the Accounting Flexfield. These views return accounting information, such as the actual, budget, summary, and parent balances and journal entry lines.


The following security modes are available on the Security Rules tab of the NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator) Security Manager to control a Noetix query user’s access to accounting data:

• No Rows: Prevents a Noetix query user from accessing any rows from the Noetix views that enforce flexfield security rules. This security mode is the default for the Type U and Type R query users for all forms of the views. For Type A query users, this option is the default for only the standard and Cross Operations Extension (XOP) forms of the views.

• All Rows: Allows a Noetix query user to access all the rows from the Noetix views that enforce flexfield security rules.

• Effective Responsibility: Allows a Noetix query user to access rows from the Noetix views that enforce flexfield security rules based on the rules associated with the user’s effective responsibility. Rows are also filtered by the ledger associated with the responsibility. This security mode is available for only the Type A and Type R Noetix query users and is the default.

NOTE: In Noetix WebQuery and Oracle Discoverer, the effective responsibility is the responsibility that the users select at the time of log on. In Other Business Intelligence (BI) tools, such as Oracle Business Intelligence (Oracle BI), IBM Cognos Business Intelligence (Cognos BI), and SAP BusinessObjects, the effective responsibility of the users is the responsibility of the Oracle E-Business Suite user to which a user is mapped in NoetixViews.

• All Responsibilities: Allows a Noetix query user to access rows from the Noetix views that enforce flexfield security rules based on the rules and ledgers associated with all the responsibilities assigned to the user. This option is available for only the Type A query users and the global form of the Noetix views.

• Per Ledger: Allows customizing a Noetix query user’s access to the accounting data corresponding to a specific ledger. This security mode is available for all type of query users and for all forms of the views.

• Assign Rules: Allows you to assign the flexfield security rules associated with a selected ledger through the Add GL Security Rules dialog box when the Per Ledger security mode is assigned to a Noetix query user.


For the purpose of applying the security settings corresponding to the Effective Responsibility and All Responsibilities options to the Noetix query users, the responsibilities assigned to the query users in Oracle E-Business Suite are divided into the financial and nonfinancial categories. The financial responsibilities include responsibilities for the Oracle modules that process accounting data, such as General Ledger, Oracle Payables, Oracle Receivables, Oracle Assets, Oracle Purchasing, Oracle Order Management, Oracle Inventory, Oracle Projects, and Oracle Work in Process. The nonfinancial responsibilities include responsibilities for the Oracle modules such as Oracle Human Resources, Oracle Advanced Benefits, and Oracle Quality. The Effective Responsibility and All Responsibilities options apply security settings to Noetix query users differently for the financial and nonfinancial responsibilities.

One of the following conditions is used for applying the flexfield security rules settings corresponding to the Effective Responsibility option to Noetix query users:

• A financial responsibility and it has no flexfield security rules assigned to it. When this responsibility is assigned to a Noetix query user, the user will have access to all the rows for the ledgers associated with the responsibility.

• A financial responsibility and it has flexfield security rules assigned to it. When this responsibility is assigned to a Noetix query user, the rules will be enforced. Rows are also filtered based on the ledgers associated with the responsibility.

• A nonfinancial responsibility and it has no flexfield security rules assigned to it. When this responsibility is assigned to a Noetix query user, the user will have no access to rows from views that enforce flexfield security rules.

• A nonfinancial responsibility and it has flexfield security rules assigned to it. When this responsibility is assigned to a Noetix query user, the rules will be enforced. Rows are also filtered based on the ledgers associated with the responsibility.

One of the following conditions is used for applying the flexfield security rules settings corresponding to the All Responsibilities option to Noetix query users:

• A single financial or a single nonfinancial responsibility that has flexfield security rules assigned to it. When this responsibility is assigned to a Noetix query user, the rows will be filtered based on the flexfield security rules and ledgers assigned to the responsibility.


• A single financial responsibility that has no flexfield security rules assigned to it. When this responsibility is assigned to a Noetix query user, the user will have access to all the rows corresponding to the ledgers associated with the responsibility.

• A single nonfinancial responsibility that has no flexfield security rules assigned to it. When this responsibility is assigned to a Noetix query user, the user will have no access to the rows from the views that enforce flexfield security rules.

• One financial responsibility with flexfield security rules assigned to it and a nonfinancial responsibility with no flexfield security rules. When these responsibilities are assigned to a Noetix query user, the rows will be filtered based on the ledgers and the flexfield security rules assigned to the financial responsibility.

• One financial responsibility with no flexfield security rules assigned to it and a nonfinancial responsibility with flexfield security rules assigned to it. When these responsibilities are assigned to a Noetix query user, the flexfield security rules settings of the financial responsibility will take precedence over the nonfinancial responsibility. Therefore, the user will have access to all the rows corresponding to the ledgers assigned to the financial responsibility.

• One financial responsibility and a nonfinancial responsibility with flexfield security rules assigned to both responsibilities. When these responsibilities are assigned to a Noetix query user, rows corresponding to the ledgers are filtered based on the flexfield security rules assigned to both responsibilities.

Flexfield security rules are mainly enforced on General Ledger views that return accounting data. However, any Noetix view that includes the Accounting Flexfield can be configured to enforce flexfield security rules by modifying the properties of the view and running the generation process. If you want to include Noetix views corresponding to other Oracle modules, contact Noetix Technical Support. By default, the following views enforce flexfield security rules in NoetixViews:

• GL_All_Balances

• GL_All_Budgets

• GL_All_Encumb_Je_Lines

• GL_All_Je_Lines


• GL_AP_Inv_Je_Line_Details

• GL_Archived_Balances

• GL_Archived_Je_Lines

• GL_Balances

• GL_Budget_To_Actuals

• GL_Budgets

• GL_Encumbrance_Balances

• GL_Foreign_Balances

• GL_Foreign_Je_Lines

• GL_Foreign_Summaries

• GL_Funds_Available

• GL_Je_AP_Inv_Dist_Details

• GL_Je_AP_Pmt_Dist_Details

• GL_Je_SLA_AP_Inv_Dist

• GL_Je_SLA_AP_Pmt_Dist

• GL_Je_SLA_AR_Adj_Dist

• GL_Je_SLA_AR_Misc_Rcpt_Dist

• GL_Je_SLA_AR_Std_Rcpt_Dist

• GL_Je_SLA_AR_Tran_Dist

• GL_Je_Tran_AR_Adj_Dist

• GL_Je_Tran_AR_Misc_Dist


• GL_Je_Tran_AR_Pymt_Dist

• GL_Je_Tran_AR_Tran_Dist

• GL_Journal_Entry_Lines

• GL_Org_Balances

• GL_Org_Budget_To_Actuals

• GL_Org_Budgets

• GL_Parent_Budget_To_Actuals

• GL_Parent_Child_Budgets

• GL_Rollup_Account_Balances

• GL_Rollup_Account_Budgets

• GL_Rollup_Parent_Balances

• GL_Rollup_Parent_Budgets

• GL_Stat_Balances

• GL_Stat_Budget_To_Actuals

• GL_Stat_Budgets

• GL_Summary_Balances

• GL_Summary_Budget_To_Actuals

• GL_Summary_Budgets

For information about how to assign flexfield security rules, see step 11 in “Create Noetix Query Users Using GUI” in “Noetix Query User Management.”


Configure Default Flexfield Security Rules SettingsNOTE: In this section, the Oracle Database User, Oracle E-Business Suite Authenticated User, and Oracle E-Business Suite Authenticated Responsibility type Noetix query users are referred as Type U, Type A, and Type R, respectively.

When Noetix query users are created, they are assigned the default flexfield security rules settings. The Noetix administrator has the option to modify a query user's settings after the user is created. This option is supported only in the global form of the Noetix views. The available default settings are Effective Responsibility, All Responsibilities, and All Rows. By default, for Type A and Type R query users, the Effective Responsibility option is set as the default flexfield security rule setting. For Type U query users, the All Rows option is set as the default flexfield security rule setting and cannot be changed. When the default flexfield security rule setting is changed, the new setting is assigned to the newly created query users of Type A and Type R. The Noetix administrator is also provided with an option to apply the new setting to existing query users.

To configure the default flexfield security rules settings:1. On the Noetix Query User Maintenance tab of the Security Manager dialog box,

select the users of the Oracle E-Business Suite Authenticated User (Type A) type for whom you want to configure the default flexfield security rules settings. If you are creating the Noetix query users for the first time, skip this step, and go to step 2.


2. Click Set Defaults. The Default Security Rule Settings dialog box appears.

3. Under EBS Users, select the appropriate default security mode. The options are Effective Responsibility, All Responsibilities, and All Rows. For information about the security modes, see About Access to Accounting Data.


4. Under Do you want to apply the default to existing users?, select one of the following options:

• No, apply only to new users: Click this option to apply the default flexfield security settings to only the selected users who are to be created as new Noetix query users. If you have clicked this option, go to step 6.

• Yes, apply to new and existing users: Click this option to apply the default flexfield security settings to both the selected users who are to be created as new Noetix query users and existing Noetix query users. If you have clicked this option, go to step 5.

5. Under How do you want to change the existing users?, select one of the following options:

• Update only users that have the previous default: Click this option if the previous default flexfield security rules settings of the existing Noetix query users need to be modified to the latest.

• Update only users that have no custom security rules: Click this option if you do not want to apply default flexfield security rules for the Noetix query users for whom custom flexfield security rules are assigned.

• Update all users to the new default: Click this option if you want to apply the default flexfield security rules to all the Noetix query users.

6. Click OK. If you are applying the new default security rules settings to new and existing users, a message appears indicating that you are about to change the default security rules for the existing users.


7. Click Yes if you want to apply the new default security rules setting to the existing users. Click No if you want to return to the Default Security Rules Settings dialog box.

NOTE: If you click Yes, the views that return results based on the security rules setting will now start returning results based on the new default security rules setting. Also, any custom security rules settings that were applied to query users should be reapplied after the new default security rules setting is applied.



NoetixViews for Oracle Human Resources

NoetixViews for Oracle Human Resources involves some special considerations that are not applicable to other NoetixViews for Oracle E-Business Suite (NoetixViews) products.

NoetixViews for Oracle Human Resources provides more than 65 views of Oracle E-Business Suite Human Resources Management System (HRMS) data based on the specific configuration at your site. The exact number of views at your site depends on how many special information types (SITs) you have defined and/or how many extra information types (EITs) are installed at your site. For example, many NoetixViews for Oracle Human Resources customers have more than 100 views.

Each view accesses a predefined set of fields in the database, assigns the data to column names, and provides the user with a variety of ways to view data. The product is a tool for the end user to assist in day-to-day Human Resources functions, such as employee management, recruitment, and payroll processes.

To optimize the product’s performance and maintain the confidentiality of data, those involved in the generation of views should be familiar with the concepts in this section.

The views for Human Resources are of two types: standard and global. Standard views for Human Resources return data for a single business group, and a Noetix role is generated for each detected business group. In contrast, global views for Human Resources provide access to all detected business groups in an instance of Oracle E-Business Suite. While supporting multiple structures of key flexfields, global views can be accessed through a single set of roles.


About Access to Human Resources DataThis section provides information about the roles for NoetixViews for Oracle Human Resources and the security policies supported by those views.

Noetix Roles for Human ResourcesNoetixViews uses database roles to group related views and simplify security administration. A Noetix query user who is granted a role can then query all views in that role.

For standard views, the following roles are generated for each detected business group:

• HR_HUMAN_RESOURCES: Includes views that return nonconfidential data, confidential data (except for salary data), and data for extra information types (EITs) and special information types (SITs). Human Resources supervisors and those who require broad access to Human Resources data should be granted this role.

• HR_MANAGER: Includes views that return nonconfidential data and confidential data (except for salary data). Managers who require limited access to Human Resources data should be granted this role.

• HR_SALARY_MANAGER: Includes views that return confidential salary data.

• HR_EXTRA_INFO_TYPES: Includes views that return data for EITs.

• HR_SPECIAL_INFO_TYPES: Includes views that return data for SITs.

• HR_USER: Includes views that return nonconfidential data.

For global views, only one set of these roles with the default, configurable prefix of HRG0_ will be generated.


Security Policies in Views for HRMSThe views for Oracle Advanced Benefits, Human Resources, Oracle Payroll, and Oracle Time and Labor support the following kinds of security policies:

• Application-Specific Security of Human Resources: This security policy is the default for Noetix query users of the Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) types. For these query users, application-specific security is applied in global views when no changes are made on the Business Group tab of the <Noetix query user> Properties dialog box of the NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator).

This security policy applies employee data and business group restrictions on Noetix query users that are similar to the restrictions applied on users in Human Resources. Employee data restrictions are always determined by the security profile or global security profile applied to the Noetix query users during logon.

For standard views, the business group is hard-coded in the view and cannot be changed or overridden. The security profile defined for the Noetix query users of the Oracle E-Business Suite Authenticated User (Type A) and Oracle E-Business Suite Authenticated Responsibility (Type R) types in Oracle E-Business Suite will determine their access to data in standard views. For Noetix query users of the Database User (Type U) and Noetix System Administration User (Type N) types, the security profiles will apply only if the query users are also defined in Human Resources as reporting users for the security profiles. The security profiles cannot be overridden in standard views.

For global views, the business group is determined by the security model and security profile or global security profile applied to the Noetix query users during logon. If the Standard Human Resources Management System security model is used in Human Resources, the business group assigned to the security profile is used or the business group assigned to the responsibility during logon with the global security profile is used. If the Security Groups Enabled security model is used, the business group is indicated by the security group used during logon. Irrespective of the security model, application-specific security of Human Resources will result in access to a single business group in the global views. For Noetix query users of the Database User (Type U) and Noetix System Administration User (Type N) types, application-specific security of Human Resources will apply in the global views only when these users are also specified as reporting users for security profiles in Human Resources.


In such cases, access to employee data will be determined by the security profiles to which the reporting users are assigned.

For information about security profiles, global security profiles, responsibilities, and security groups, see the Oracle documentation.

• Custom Security: Custom security is available for only certain global views for Advanced Benefits, Human Resources, Payroll, and Time and Labor. Custom security is established when application-specific security of Human Resources is overridden through settings on the Business Group tab of the <Noetix query user> Properties dialog box. Through custom security, you can override the employee data restrictions of security profiles and global security profiles, allow access to all business groups within the organization hierarchy of a global security profile, and create custom lists of accessible business groups.


The following table indicates how the settings in Human Resources and on the Business Group tab of the <Noetix query user> Properties dialog box collectively secure data in global views for Advanced Benefits, Human Resources, Payroll, and Time and Labor:

Table 1: How HRMS Data is Kept Secure

At logon, when the Noetix query user has a

And it is The global view will return

Security profile

Not enforced by Noetix-Views

All employee data in all business groups in the Assigned Business

Groups list on the Business Group tab

Security profile

Enforced by NoetixViews

Employee data restricted by the security profile and the business group assigned to the security

profile when the Standard HRMS security model is used so long as the business group is also in the

Assigned Business Groups list on the Business Group tab

OrEmployee data restricted by the security profile and the business

group for the security group used during logon when the Security

Groups Enabled security model is used so long as the business group

for the security group is also in the Assigned Business Groups list

on the Business Group tab

Global security profile

Not enforced by Noetix-Views

All employee data in all business groups in the Assigned Business

Groups list on the Business Group tab


Global security profile

Enforced by NoetixViews

Employee data restricted by the global security profile and for the

business group assigned to the responsibility during logon when

the Standard HRMS security model is used so long as the busi-ness group is also in the Assigned Business Groups list on the Busi-

ness Group tab1

OrEmployee data restricted by the global security profile and the business group for the security group used during logon when the Security Groups Enabled

security model is used so long as the business group for the security

group is also in the Assigned Business Groups list on the Busi-

ness Group tab1

OrEmployee data restricted by the global security profile and for all business groups in the organiza-tion hierarchy of the global secu-rity profile so long as the business

groups are also in the Assigned Business Groups list on the Busi-

ness Group tab2

1 The Enforce Oracle HR security profile processing check box and the business group specified by the user's login session option on the Business Group tab are selected.2 The Enforce Oracle HR security profile processing check box and the all business groups included in the global security profile option on the Business Group tab are selected.

At logon, when the Noetix query user has a

And it is The global view will return


For information about how to control access to data in global views for Advanced Benefits, Human Resources, Payroll, and Time and Labor, see step 6 in “Add a Noetix Query User Using an Existing User” in “Noetix Query User Management.”

The following table lists the Noetix views pertaining to Human Resources that provide secured or customizable access to data:

Table 2: NoetixViews for Oracle Human Resources

View nameHuman Resources security profile applied at:

HR_Accural_Pln_Hist Any level

HR_Address_Hist Person and Organization levels

HR_AP_1099_Payments(available for only United States legislation)

Person level

HR_Applicant_Hist Person, Assignment, and Vacancy levels

HR_Ben_Elig_Info Position, Person, and Assignment levels

HR_Budgets Position level

HR_Carrier_Asg_Hist Security level

HR_COBRA_Prem_Stat(available for only United States legislation)

Position level

HR_COBRA_Track(available only for United States legislation)

Position level

HR_Contact_Hist Person level

HR_Contingent_Worker_Info Any level

HR_EI_Academic_Rank Person level

HR_EI_Asg_Ben_Derived Person level

HR_EI_Asg_Federal Person level

HR_EI_Asg_Locality Person level

HR_EI_Asg_Types Position, Person, and Assignment levels

HR_EI_GHR_Probations Person level


HR_EI_GHR_Sep_Retire Person level

HR_EI_Job_Types Any level

HR_EI_Loc_Types Any level

HR_EI_Per_Types Person level

HR_EI_Pos_Types Any level

HR_EI_US_Add_Details(available for only United States legislation)

Person level

HR_EI_US_Passport_Dtls(available for only United States legislation)

Person level

HR_EI_US_Visa_Dtls(available for only United States legislation)

Person level

HR_Element_Links Person, Organization, and Payroll level

HR_Emp_Absence_Hist Person and Assignment levels

HR_Emp_ADA_Info(available for only United States legislation)

Person level

HR_Emp_Asg_Details Person and Assignment levels

HR_Emp_Assign_Costs Organization, Person, and Assignment levels

HR_Emp_Assign_Costs_Hist Person and Assignment levels

HR_Emp_Assign_Hist Person and Assignment levels

HR_Emp_Ben_Health Person and Assignment levels

HR_Emp_Ben_Others Person and Assignment levels

HR_Emp_Beneficiary Person level

HR_Emp_Element_Entry_Vals Person and Assignment levels

HR_Emp_Emergency Person and Assignment levels



HR_Emp_Ethnic_Info(available for only United States legislation)

Person and Assignment levels

HR_Emp_Headcnt_Hist Person and Assignment levels

HR_Emp_Headcounts Person and Assignment levels

HR_Emp_Info Person and Assignment levels

HR_Emp_LOS Person and Assignment levels

HR_Emp_Reviews Person and Assignment levels

HR_Emp_Sal_Analysis Person and Assignment levels

HR_Emp_Sal_Hist Person and Assignment levels

HR_Emp_Sal_Pro_Current Person and Assignment levels

HR_Emp_Sal_Pro_Hist Person and Assignment levels

HR_Emp_Tax_Details(available for only United States legislation)

Person level

HR_Emp_Terms_Hist Person and Assignment levels

HR_Emp_Total_Comp Person and Assignment levels

HR_Emp_Veteran_Info(available for only United States legislation)


HR_Emp_Work_Hist Person and Assignment levels

HR_Emp_Xfers_Hist Person and Assignment levels

HR_New_Hire_Hist Organization, Person, and Assignment levels

HR_Oth_Headcnt_Hist Person and Assignment levels

HR_Pay_Scales Any level

HR_People_Grp_Hist Person and Assignment levels

HR_Person_Hist Person and Assignment levels

HR_Phones_Hist Person level

HR_Pos_Hierarchies Position level



HR_Pos_Requirements Position level

HR_Req_Vac_Track Position and Vacancy levels

HR_Schools_Attended Any level

HR_SI_Type Person level

HR_Turnover_Hist Organization, Person, and Assignment levels

HR_Vac_Job_Match Position and Vacancy levels

HR_Vac_Pos_Match Person, Position, and Vacancy levels

HR_Accural_Pln_Hist Any level

HR_Address_Hist Person and Organization levels



The following table lists the Noetix views pertaining to Advanced Benefits that provide secured or customizable access to data:

Table 3: NoetixViews for Oracle Advanced Benefits


BEN_COBRA_Beneficiaries(available for only United States legislation)


BEN_Elig_Elec_Enrollments Person and Assignment levels

BEN_Emp_Dependents Person level

BEN_Life_Evnt_Workflow Person and Assignment levels

BEN_Payroll_Ben_Costs Person level

BEN_Potential_Life_Evnts Person and Assignment levels

BEN_Ptpnt_Benefit_Costs Person and Assignment levels

BEN_Ptpnt_Communications Person and Assignment levels

BEN_Ptpnt_Court_Orders Person and Assignment levels

BEN_Ptpnt_Electabilities Person and Assignment levels

BEN_Ptpnt_Eligibilities Person and Assignment levels

BEN_Ptpnt_Enroll_Actions Person and Assignment levels

BEN_Ptpnt_Enrollments Person and Assignment levels

BEN_Ptpnt_Flex_Credits Person and Assignment levels

BEN_Ptpnt_Flex_Spending Person and Assignment levels

BEN_Ptpnt_Life_Events Person and Assignment levels


The following table lists the Noetix views pertaining to Payroll that provide secured or customizable access to

Table 4: NoetixViews for Oracle Payroll

View name Human Resources security profile applied at:

PAY_Accruals (available for all legislations except for Australia)


PAY_Check_Register Payroll, Person, and Assignment levels

PAY_Costing_Analysis Payroll, Person, and Assignment levels

PAY_Costing_Details Organization level

PAY_Costing_Summary Organization level

PAY_Custom_Balances (available for all legislations except for Australia and United Kingdom)

Payroll, Person, and Assignment levels

PAY_Deductions_Owed Payroll, Person, and Assignment levels

PAY_Emp_Not_Paid Payroll, Person, and Assignment levels

PAY_Emp_Not_Paid_Vg Payroll, Person, and Assignment levels

PAY_Gre_Totals (available for only United States legislation)

Organization level

PAY_Gross_And_Net_Balances Payroll, Person, and Assignment levels

PAY_Gross_To_Net_Summary Organization level

PAY_Hours_By_Cost_Center Organization level

PAY_Invalid_Addresses (available for only United States legislation)

Person level

PAY_Payment_Methods Person and Assignment levels

PAY_Payment_Register Payroll, Person, and Assignment levels

PAY_Payroll_Activities Payroll, Person, and Assignment levels

PAY_Payroll_Audit Payroll, Person, and Assignment levels

PAY_Payroll_Messages Organization, Payroll, Person, and Assignment levels


The following table lists the Noetix views pertaining to Time and Labor that provide secured or customizable access to data:

Table 5: NoetixViews for Oracle Time and Labor

PAY_Payroll_Proc_Summary Payroll level

PAY_Run_Results Payroll, Person, and Assignment levels

PAY_Tax_Balances (available for all legislations except Australia and United Kingdom)


PAY_Third_Party_Balances (available for only Canadian legislation)


PAY_Third_Party_Register Payroll, Person, and Assignment levels

PAY_Void_Payments Payroll, Person, and Assignment levels

PAY_Accruals (available for all legislations except for Australia)


PAY_US_Payroll_Register (available for only United States legislation)


PAY_US_W2_Register (available for only United States legislation)



HXC_All_Assignment_Hist Person and Assignment levels

HXC_All_Person_Hist Person level

HXC_Assignment_Time_Info Person and Assignment levels

HXC_BEE_Batch_Headers Organization level

HXC_BEE_Batch_Lines Person and Assignment levels

HXC_BEE_Error_Messages Organization level

HXC_PUI_Latest_Timecards Person and Assignment levels

View name Human Resources security profile applied at:


SIT ViewsNoetixViews for Oracle Human Resources provides the user with various views that maximize the information delivery ability of special information types (SITs) in Human Resources Management System (HRMS). SITs are a collection of personal attributes that usually provide information related to recruitment, such as specific qualifications and skills, which are predefined in the Personal Analysis key flexfield.

NoetixViews for Oracle Human Resources provides views to augment your recruitment, career development, and applicant matching capabilities by using SITs. SIT views are generated during generation based on the SITs defined and enabled at your site.

The format for each view name is HR_SI_Type_STRUCTURE_NAME. For example, the views HR_SI_Type_Education or HR_SI_Type_Communication_Skills would each return a list of people associated with each SIT defined at your site. These may be grouped by Applicant, Employee, or Employee and Applicant Person Types. The number of HR_SI_Type views per site is directly related to the number of SITs that were defined in Oracle HRMS.

Views displaying current job and position requirements based on the SIT definitions are also available. The names for these views will look similar to HR_Job_Requirements or HR_Position_Requirements.

HXC_PUI_Missing_Timecards Person and Assignment levels

HXC_PUI_Time_Entry_Errors Person level

HXC_PUI_Timecard_History Person and Assignment levels

HXC_SS_Latest_Timecards Person and Assignment levels

HXC_SS_Missing_Timecards Person and Assignment levels

HXC_SS_Time_Category_Hours Person level

HXC_SS_Timecard_Action_Hist Person and Assignment levels

HXC_SS_Timecard_History Person and Assignment levels



In addition, the following views are designed to assist you in matching a pool of internal and external applicants to specific vacancies at your firm (regardless of whether your organization has decided to use Job or Position functionality within Oracle HRMS): HR_Vac_Job_Match and HR_Vac_Pos_Match.

NOTE: SITs defined for Job and Position Requirements or Skills used in the Oracle Training module do not result in NoetixViews HR_SI_Type views being generated.

Joining to SIT ViewsThe information in each special information type (SIT) view can be linked to the data in the HR_Person_Hist view. Therefore, each SIT view contains one Z$ column to allow joins to the HR_Person_Hist view. You can also join an SIT view to any current view that includes a join to Z$ column for HR_Person_Hist.

Noetix Generator for Oracle Discoverer (Noetix Generator) automatically sets up joins between the HR_SI_Type views and other current views containing a join to Z$ column to HR_All_Person_Hist, and you can do the same when configuring other query tools.

When joining an SIT view with HR_Person_Hist, only current results will be returned. This is because SIT views return only current information.

Please note that use of SITs is optional. When an SIT view is joined to another view, the data returned will be limited by the attributes in the particular SIT view. This reduces the information returned from a query involving an SIT view and a join to column. For example, HR_Emp_Asg_Details joined to HR_SI_Type_Education would result in assignment details for all employees meeting the criteria of the special educational information designated in the SIT view. If an employee did not meet the educational criteria, that particular employee record would not be returned.

Joining views using outerjoins is not a good option because of the way Oracle executes queries against views that are outerjoined together. This option only works when query criteria is limited by search by (A$) columns in both views involved in an outerjoin. An equijoin does not have this requirement, and only one search by (A$) column needs to be used as query criteria. (Using two could be faster, however, if query performance is required.)

NOTE: This special join to consideration is not true for NoetixViews for Oracle Human Resources date-tracked views (views with names ending in Hist). The HR_SI_Type views


are not historical and may cause historical information to be missing from the resulting query.

EIT ViewsExtra information type (EIT) views, available with NoetixViews for Oracle Human Resources, maximize the information delivery ability of EITs in Human Resources Management System (HRMS). Introduced in Oracle E-Business Suite 11.0 and further enhanced in 11i, EITs are developer descriptive flexfields available for six key areas (person, assignment, position, job, location, and organization).

In addition, Oracle HRMS allows the addition of unlimited descriptive flexfields for further customization of each EIT. For example, a user may want to use the person EIT to display additional personal information such as passport details, visa details, visit details, etc.

NoetixViews generates views for the person and assignment EIT types and also detects any customized descriptive flexfields. Each EIT view contains only information related to the specific EIT. These simple EIT views are designed to be joined to related Human Resources views (through the use of Noetix Z$ columns) to provide more detailed data. For example, the information in the person EIT views can be linked to the data in the NoetixViews HR_Person_Hist view or, in addition, to any Human Resources view that includes the Z$HR_Person_Hist column.

Similarly, the assignment EITs can be linked to the data in the HR_Emp_Asg_Details view or to any Human Resources view that includes the Z$HR_Emp_Asg_Details column in NoetixViews. For more information about how to join views using Z$ columns, see the NoetixViews for Oracle E-Business Suite User Guide.

The format for each view name is HR_EI_ASSIGNMENT_TYPE. For example, the person EIT view HR_EI_US_Passport_Dtls will display United States Passport Details. EIT views will be generated only for the Person and Assignment types of EITs supplied by Oracle. Person EITs are available for U.S., Global, and Government categories. Assignment EITs are available for U.S., Federal, and Great Britain categories.


Oracle DateTrack and NoetixViewsThe Oracle DateTrack feature allows you to store changes in records that happen over a period of time. The DateTrack feature adds the dimension of time to an application’s database. Some tables in Human Resources use the DateTrack feature to record changes in the employee data and to preserve the historical information in an organized manner. These tables typically contain an employee’s details such as an employee’s personal, assignment or compensation details.

This section provides an overview about the DateTrack feature and information about how the feature is used in NoetixViews for Oracle Human Resources.

NOTE: The DateTrack feature is also used in the Payroll and Advanced Benefits modules of the Oracle E-Business Suite.

Identifying DateTracked RecordsThe Oracle table that stores DateTracked information has the following attributes:

• The table name ends with _F. For example, PER_ALL_PEOPLE_F.

• The Effective_Start_Date and Effective_End_Date columns exist, and the values in these columns cannot be null. The Effective_Start_Date column indicates when the record was inserted, and the Effective_End_Date column indicates when the record was deleted or updated.

In most DateTracked tables, the effective dates form a part of the primary key consisting of an ID and the two effective dates. For example, in the table PER_ALL_PEOPLE_F, Person_Id + Effective_Start_Date + Effective_End_Date is the primary key.

• The effective dates are contiguous. For example, if the effective start date of the current record is 16-JAN-2000, then the effective end date of the previous record will be 15-JAN-2000.

• The effective dates do not have any time stamps, and, thus, there can only be one record per day.


Following is an example of a DateTracked table:

Managing Records in DateTracked TablesThis section provides information about how to insert, update, and delete records in a DateTracked table.

Inserting RecordsIf you insert a record in a DateTracked table, the effective start date is set to the current day and the effective end date is set as 31-DEC-4712. This effective end date value is the default value set by Human Resources if you do not specify an effective end date. However, you can specify an effective end date that is later than the effective start date.

Emp_No NameEffective_Start_Date

Effective_End_Date

Salary

E101 James Brown 01-Jan-1990 31-Dec-1995 15,500

E101 James Brown 01-Jan-1996 31-Jul-1998 18,500

E101 James Brown 01-Aug-1998 28-Feb-2002 20,500

E101 James Brown 01-Mar-2002 31-Dec-4712 23,500


Updating RecordsIf you update a record in a DateTracked table, a message is displayed asking whether you want to update or correct the record. If you choose:

• Update: The value in the Effective_End_Date column of the existing record changes to yesterday. A record is created with the updated values having the Effective_Start_Date column value as the current date and the Effective_End_Date column value as 31-Dec-4712.

IMPORTANT: If the record you are updating has effective start date as the current day, a message is displayed stating that the previous values will be lost because the Oracle DateTrack feature does not support time stamp values and hence there can be only one record per day. If you want to make a second change on the same day, you must do it in the correction mode.

• Correction: The existing record is overwritten with the new values and the same effective dates are retained.

Deleting RecordsIf you delete a record in a DateTracked table, you are prompted to select the type of delete. If you choose:

• Delete (End Date): The effective end date of the current record is set to today's date. The record disappears from the dialog box in Human Resources although you can view the record by running a query.

• Zap (Purge): All records matching the key value are deleted.

• Future Change (All): Any future-dated changes to the current record are removed. The effective end date of the current record is set to 31-DEC-4712. You can view the record by running a query.

• Delete Next Change (Next Change): The next change to the current record is deleted. A record may or may not have a future DateTracked record.

• If a future DateTracked record exists for the record, the future DateTracked record is deleted, and the effective end date of the deleted row becomes the effective end date of the current record.


• If no future DateTracked record exists and the current row has an effective end date other than 31-DEC-4712, then the effective end date is set as 31-DEC-4712. The record disappears from the dialog box in Human Resources although you can view the record by running a query.

Oracle DateTrack in NoetixViews for Oracle Human ResourcesNoetixViews for Oracle Human Resources uses the Oracle DateTrack feature. Because all the significant tables in Human Resources are DateTracked tables, the DateTrack feature plays an important role in the NoetixViews architecture. However, there are some views that return only the current record.

With respect to current and historic information, there are three types of views:

• Current Only: These views have no name suffixes, nor any time period information in their view descriptions. The current views return information that is current as of the time the query is run in NoetixViews.

• Datetracked Historic: These views have the Hist suffix in their names and the words Current and Historic in their view descriptions. These views contain Human Resources DateTracked information — multiple records for the same entity as of current, historic, and future effective dates. More information about the Noetix historical views and the effective dates is provided in the following section.

• End Dated Historic: These view names have no suffixes. The words Current and Historic are present in their view description. These views contain information that is not DateTracked but may include historic information, based on the end dates of work structure entities included in the views.


DateTracked Historic Views and Effective DatesThe attributes of a DateTracked historic view are:

• The view name ends with _Hist (for example, HR_Emp_Assign_Hist).

• The view will contain three effective date columns: Effective_Start_Date, Effective_End_Date, and Effective_End_Date_Stored. The effective date columns will be populated from the Oracle base table. For example, the effective date columns in the HR_Emp_Assign_Hist view are populated from the PER_ALL_ASSIGNMENTS_F table. The PER_ALL_ASSIGNMENTS_F table is the underlying DateTracked table for the HR_Emp_Assign_Hist view, and drives the data for the view.

NOTE: The views display the effective start date and effective end date only from the underlying DateTracked tables that drive the data for the view. The underlying DateTracked tables are the base tables for these views, although there may be other DateTracked tables that provide additional value to this view. For example, although the HR_Emp_Assign_Hist view is populated with data from other DateTracked tables, such as PER_ALL_PEOPLE_F, the effective dates from tables other than the PER_ALL_ASSIGNMENTS_F table will not appear as columns in the view.

The Effective_End_Date_Stored column is used to store the values from the actual database column, Effective_End_Date. The Effective_End_Date column in the view is the pretty version of the database column. It will be null if the value of the Effective_End_Date column in the Oracle database is 31-DEC-4712.

NOTE: You must use the Effective_End_Date_Stored column in filters. However, if you want to display the column in reports, you must use the Effective_End_Date column.

More complex views may be built from more than one DateTracked base table. In this case, there may be more than one set of effective dates in the view. You may need to create a filter for each pair of effective dates to avoid duplicates. Then again, some of these effective dates may be null; so filtering on all of them may cause your report to return no data. Add and test your filters one at a time.


Exceptions in Effective Dates Used in DateTracked Historic ViewsFollowing are the exceptions in the effective dates in DateTracked historic views:

• A few DateTracked historic views have only two columns: Effective_Start_Date and Effective_End_Date. The Effective_End_Date_Stored column is missing in these views.

• Sometimes, the effective date columns have variant names, such as Benefit_Effective_Start_Date. Such views often do not have the Effective_End_Date_Stored column; therefore, you should filter the records using the NVL function on the effective end date. These column names do not start with Effective and, consequently, will appear elsewhere in the alphabetized column lists of views.

For such views, the expression to display the current record in Noetix WebQuery (NWQ) is as follows:

TRUNC(now()) BETWEEN Effective_Start_Date AND NVL( Effective_End_Date,'31-DEC-4712')

IMPORTANT: Even though the NWQ date format is <MM/DD/YYYY>, in expressions you use the date format that you see in Oracle E-Business Suite.

• Some Human Resources tables do a kind of logical DateTracking without having effective date columns. This might be because of the following reasons:

• These tables are mostly used outside the Human Resources arena and perhaps predate the Human Resources date tracking techniques.

• These tables contain the Date_From and Date_To columns and the tables contain records with overlapping dates. For example, in the PER_ADDRESSES table only one primary address can exist at a time, but there could be other types of addresses with overlapping dates. These dates will be displayed in Noetix views. Keeping in mind that you might need to filter on the Primary_Flag column, your expression can be: TRUNC(now()) BETWEEN Date_From AND NVL( Date_To,'31-DEC-4712')


How to Use Oracle DateTrack in NoetixViews for Oracle Human ResourcesThis section provides information about how you can use the Oracle DateTrack feature to select and display the required records in NoetixViews for Oracle Human Resources.

Displaying DataTo display the current record in Noetix WebQuery (NWQ) using the Noetix historical views, you should use the following expression:

TRUNC(now()) BETWEEN Effective_Start_Date and Effective_End_Date_Stored

Even if you have renamed these columns in your report, you must use the actual column names in the expression. It does not matter which column name you select but for readability it is recommended that you select an effective date rather than some random column. You might want to write the code in Notepad and then paste it in the Expression box of NWQ. It is a good idea to save these files because you are likely to reuse this code.

If you are not using NWQ as your reporting tool, you should use the following expression:

TRUNC(sysdate) BETWEEN Effective_Start_Date and Effective_End_Date_Stored

No matter which query tool you are using, it is essential to truncate today’s date to avoid loss of data. Remember that the effective dates do not have a time stamp; therefore, if today is 31-AUG-2006 and one of the effective dates is today’s date, you must truncate the Now() or Sysdate() functions, and select this record.

When you are selecting data from a Noetix historical view, keep in mind that the effective date may be a meaningless column to include as a field in your report. If you are listing employees and jobs, the effective start date in the record is not necessarily the date the employee first got that job. It is likely to reflect some other change to the employee assignment, one you do not care about here.


Using Flag ColumnsSome DateTracked historical views include flag columns that can eliminate the need to filter on effective dates when you want to select the current record. The most common flag columns are the Current_Employee_Flag, Current_Assignment_Flag, and Current_Applicant_Flag columns. You do not need to worry about null values in the flag columns because these columns will always have a value.

The Current_Employee_Flag and Current_Applicant_Flag columns do not limit a query to the current row of data. If you are looking at the HR_Emp_Assign_Hist view and there are six records for a person, all the six records will be flagged as Y or N depending on whether the person is a current employee. The Current_Applicant_Flag column works in the same way.

As for the Current_Assignment_Flag column, looking at the same employee with six assignment history records, the value of the column will be Y only for the current assignment record or records.

IMPORTANT: Human Resources allows an employee to have more than one assignment at a time. So, there can be duplicate records for an employee. If you want a single record, filter on the Primary_Flag column. You must do this even if your generation does not use multiple assignments because this feature cannot be turned off and there may be an accidental secondary assignment.

Another thing to keep in mind about the Current_Assignment_Flag column is that a person may have a current assignment with an assignment status as Terminate Assignment. So you may need to filter on multiple columns to limit your query to single records for the current employees.


Hiding Duplicate RowsMost of the time, you are not interested in historical data. You want to see the current data and at the same time avoid duplicates.

In NWQ, selecting the Hide Duplicate Rows check box on the Columns page results in display of distinct records, just as using the SELECT DISTINCT SQL statement does. This is useful for eliminating duplicates in reports, but should only be used as a last resort in reports that will be run often, shared with others or become part of your corporate reporting repository. Hiding duplicate records without understanding why they occur may result in reporting errors.

Depending on how you sort, you may not see records that actually are duplicates. For example, if you are using a view like HR_Emp_Assign_Hist and listing employees by job, the same employee might appear under different jobs and not be recognized as a duplicate. Selecting the Hide Duplicate Rows check box will not eliminate this problem.

Actually, there are no duplicates. Each row in the table is created because something has changed. However, there may be no differences in any of the columns in your query. On rare occasions, there will be no change in any data that the view has selected because the change was to a column that is not included in the view.

Displaying Data at a Point of TimeOne thing to watch out for is that certain information from non-base tables may be repeated in the view. For example, for an employee with six assignment history rows, the employee’s date of last hire will occur on all six rows. If the repeated field is a date, as this one is, you can take advantage to select data from another period of time. For example, if you are creating a hire report, you might want to select the employee’s job at the time of hire. Your expression would then compare three dates:

Date_Of_Last_Hire BETWEEN Effective_Start_Date AND Effective_End_Date_Stored

The same technique might be advisable when you are working with views containing more than one pair of effective dates, where you compare one date with another. You may need to test this before you decide the date that should be between other dates.


We are now moving on to more challenging queries. We already saw how there might be another date in the view that you can use as a constant. For example, the actual termination date (the Actual_Termination_Date column) and the date the person started a job in the company (the Person_Start_Date column) are constants. There are few Noetix views that have an Effective_Start_Date column but no Effective_End_Date column, and the Effective_Start_Date column is a constant. Here are a few examples:

• HR_New_Hire_Hist view: Service_Start_Date BETWEEN Effective_Start_Date AND Effective_End_Date_Stored

• HR_Emp_Reviews view: Interview_Date_Start BETWEEN Effective_Start_Date AND Effective_End_Date_Stored

Suppose you have a specific date in mind that is not today’s date. You have an option to hard code a date in your expression instead of using the Now() or Sysdate() functions:

'01-JAN-2005' BETWEEN Effective_Start_Date AND Effective_End_Date_Stored

You might not want a hard-coded date. You want to create a report that displays the data as it was a year or two years ago, and you do not want to modify it every time you run it. To do this:

1. Create a calculated column called Last_Year_Date. If you do not want to display this column in your report, you can hide it by selecting the Is Hidden check box on the New Calculated Column page in NWQ.

2. Write the following expression in the Expression box to set the value of this column to last year: TO_CHAR(now(),'YYYY') – 1


3. You can concatenate the day and month to the year. The following expression concatenates today’s date with the previous year, but you could also use a constant, such as 01-JAN-: TO_CHAR(now(),'DD-MON')||'-'|| (TO_CHAR(now(),'YYYY') - 1)

4. Now you have the date string that is required in your raw filter. Instead of TRUNC(now()) function, use the following expression: TO_CHAR(now(),'DD-MON')||'-'|| (TO_CHAR(now(),'YYYY') - 1) BETWEEN Effective_Start_Date and Effective_End_Date_Stored

You do not need to truncate your date because you have already eliminated any time stamp from your calculated date.

Creating calculated columns is easier than developing complex expressions because the query engine is somewhat less fussy. You can see components of your query and work up to the complexity that you want. You can also sometimes use a calculated column to test your query, provided you are computing with database columns and not creating a constant. Display the column, then run the report and drag up the computed column as a page item. The number of rows displayed should match the number of rows your filter returns. Also, it is easier to see which data gets eliminated.

If you use such dates in a filter, you will limit your query to a single record at some other point in time. You can also use them to perform counts in computed columns and develop a complex report.


Reporting ChangesOne of the challenges with historical data is to find out the record where a change in the required value occurred for the first time. For example, you want to create a report displaying the names of the supervisors who changed during the course of work on an assignment. There may be several rows of assignment data where something else changed except the supervisor name. You should use the following expression to limit your query to only those rows where the supervisor is different from the previous row:

EXISTS

SELECT 1 FROM <fully qualified installation_name>."HR_Emp_Assign_Hist" a

WHERE a.Assignment_Number = "HR_Emp_Assign_Hist"."Assignment_Number"

AND a.Business_Group = "HR_Emp_Assign_Hist"."Business_Group"

AND a.Current_Employee_Flag = 'Y'

AND a.Primary_Flag = 'Y'

AND a.Supervisor_Employee_Number <> "HR_Emp_Assign_Hist".Supervisor_Employee_Number

AND a.Effective_End_Date = "HR_Emp_Assign_Hist".Effective_Start_Date - 1)

NOTE: The carriage returns are invalid in expressions. They are added here for readability, and you should remove it in your expression.

This example takes advantage of the fact that effective dates are always contiguous. The effective end date in the subquery will be one day previous to the start date of the main query.

Such techniques require a fairly high level of SQL skill, but once they are developed, it is much easier to clone and adapt them. For example, it would be fairly simple to modify the earlier code to detect job changes.


Creating Intelligent History QueriesYou might want to select all the history records for an employee based on a characteristic feature in the employee’s current record. For example, you might want to display the job history for everyone in your organization who is currently working as a Director. Assuming that all director jobs will contain the DIRECTOR word in the job flexfield, you can write the following expression to do this:

EXISTS

(SELECT 1 FROM "<fully qualified installation_name>"."HR_Emp_Assign_Hist" a

WHERE a.assignment_number = "HR_Emp_Assign_Hist"."Assignment_Number"

AND a.Business_Group = "HR_Emp_Assign_Hist"."Business_Group"

AND a.Current_Employee_Flag = 'Y'

AND a.Primary_Flag = 'Y'

AND a.Job_Name LIKE '%DIRECTOR%'

AND TRUNC(now())BETWEEN a.Effective_Start_Date AND a.Effective_End_Date_Stored)

NOTE: The carriage returns are invalid in expressions. They are added here for readability, and you should remove it in your expression.

Unfortunately, NoetixViews for Oracle Human Resources does not support passing parameters to subqueries. Therefore, you must modify the expression to work for a different job.


Creating Data Batches and Handling StragglersThere is a frequent need in Human Resources to create a report or an outbound interface that runs on a regular basis and reports the change in a record. Let us consider an example to understand this scenario. Usually, a list of department transfers is generated monthly. However, if the list for the previous month needs to be generated on the first few days of this month, the late data entries for the previous month will not be included in this batch. That is, if on 03-APR-2006 you make an entry and set the effective end date value as 29-Mar-2006 for the record, then the record will not be selected if you run a query on 02-APR-2006. The issue is that such records will also not be picked up when you run the query in the following month because the query will be looking at effective dates in April and not March.

NoetixViews for Oracle Human Resources does not currently offer a way around this problem because it does not include Last_Update_Date or Creation_Date columns in the views. You need to filter on the following two conditions: the effective start dates lie within the month in question or the effective_start_date is in the earlier month, and the last update date is within the month in question. Your SQL expression would look like this:

((AND effective_start_date BETWEEN ’01-MAR-2006’ and ’31-MAR-2006’)

(OR effective_start_date <’01-MAR-2006’

AND last_update_date BETWEEN ’01-MAR-2006’ AND ’31-MAR-2006’))

The view should be customized to add the Last_Update_Date or Creation_Date columns from the base table to the view. For more information, contact Noetix Technical Support.




Restricting DateTrackingWhen you edit or delete a DateTracked record, a message is displayed asking you to select the type of update or delete you want to perform. Before displaying the message, the application calls a custom library event called DT_SELECT_MODE, and the event passes the options that should be displayed to the user.

You can control the options displayed to the user (such as Update or Correct) by using a custom code. If necessary, you can restrict the user to update or delete records and display an error message instead.

For more information about DT_SELECT_MODE, see the Oracle documentation.

Benefit Classification AssumptionsViews containing benefit element information (such as HR_Ben_Elig_Info, HR_Emp_Ben_Others, and HR_Emp_Total_Comp) will not return all data unless benefit classification information has been entered into Human Resources Management System (HRMS) and benefit elements have been assigned to a benefit classification. For information about how a view may be restricted by this assumption, please read the specific view essay in the Noetix Help File.

Support for Additional Personal Details Descriptive FlexfieldIn some Noetix views for Human Resources, columns labeled PEO$<attribute> are generated for only certain contexts of the Additional Personal Details descriptive flexfield (stored in the PER_ALL_PEOPLE_F table of Oracle E-Business Suite):

View label Supported contexts

HR_Applicant_Hist APL, Global Data Elements

HR_Carrier_Asg_Hist EMP, Global Data Elements

HR_Emp_ADA_Info EMP, Global Data Elements

HR_Emp_Absence_Hist EMP, Global Data Elements

HR_Emp_Asg_Details EMP, Global Data Elements


HR_Emp_Assign_Costs EMP, Global Data Elements

HR_Emp_Assign_Costs_Hist EMP, Global Data Elements

HR_Emp_Assign_Hist EMP, Global Data Elements

HR_Emp_Ben_Health EMP, Global Data Elements

HR_Emp_Ben_Others EMP, Global Data Elements

HR_Emp_Beneficiary EMP, Global Data Elements

HR_Emp_Ethnic_Info EMP, Global Data Elements

HR_Emp_Headcnt_Hist EMP, Global Data Elements

HR_Emp_Headcounts EMP, Global Data Elements

HR_Emp_Info EMP, Global Data Elements

HR_Emp_LOS EMP, Global Data Elements

HR_Emp_Reviews EMP, Global Data Elements

HR_Emp_Sal_Hist EMP, Global Data Elements

HR_Emp_Sal_Pro_Current EMP, Global Data Elements

HR_Emp_Sal_Pro_Hist EMP, Global Data Elements

HR_Emp_Terms_Hist EMP, Global Data Elements

HR_Emp_Total_Comp EMP, Global Data Elements

HR_Emp_Veteran_Info EMP, Global Data Elements

HR_Emp_Work_Hist EMP, Global Data Elements

HR_Emp_Xfers_Hist EMP, Global Data Elements

HR_New_Hire_Hist EMP, Global Data Elements

HR_Person_Hist EMP, Global Data Elements

View label Supported contexts


For these views, the Noetix Help File also specifies the contexts for which the PEO$<attribute> columns are generated for the Additional Personal Details descriptive flexfield.

Default Hours for Salary CalculationsInformation required to complete the calculations for calculated salary-related columns is, in some cases, optional setup information in Human Resources Management System (HRMS). If information is not available in Oracle HRMS to perform the calculations, make the following assumptions for standard full-time employees (hourly or salaried positions):

• 8 paid working hours per day• 5 working days per week• 12 working months per year• 52 working weeks per year• 2,080 paid working hours per year

Please note that paid vacation and holidays are considered working days for these calculations, and the earlier values should not be reduced to account for them.

If one of these assumptions is incorrect for a business group or organization in your configuration, you can define standard working conditions in Oracle HRMS at the business group or organization level to override our assumption. If this cannot be accomplished or if multiple assumptions of ours are false, then a customization must be made to NoetixViews for Oracle Human Resources to provide correct calculations. Please contact Noetix Technical Support for this customization.

Setup Business GroupNoetixViews for Oracle Human Resources generates a set of views and multiple roles for each business group defined in your Human Resources Management System (HRMS) configuration. Oracle HRMS ships with a predefined business group called the Setup Business Group. If the Setup Business Group has been modified to become an active defined business group, NoetixViews for Oracle Human Resources will work as expected and generate views for the information associated with this business group.


Optional Views and ColumnsSome views and columns in NoetixViews for Oracle Human Resources are included only in specific configurations for Oracle Human Resources Management System (HRMS) or a business group within Oracle HRMS. The most common examples are legislative-specific views and columns. For example, business groups operating under U.S. legislation will have additional views and columns that relate to U.S.-specific government-mandated reporting information. No specific actions during the generation process are required to generate these views and columns. As long as your configuration of Oracle HRMS is complete, NoetixViews for Oracle Human Resources will automatically detect the configuration and include or exclude the appropriate columns. If you are still in the process of setting up Oracle HRMS or even a new business group and all the configuration information is not available, some columns relating to the configuration-specific information (such as flexfields) may not be included in NoetixViews for Oracle Human Resources.

Performance-Related IssuesSeveral concepts affect system performance when retrieving information from Oracle Human Resources Management System (HRMS) using NoetixViews for Oracle Human Resources.

In general, Oracle HRMS has a smaller number of rows than other Oracle E-Business Suite; performance is generally better because there is less information to sort through. Two factors that can negatively affect performance, however, are the use of functions within NoetixViews for Oracle Human Resources and the use of information that is optional within Oracle HRMS.


FunctionsNoetixViews for Oracle Human Resources uses functions in almost all views to accomplish several tasks:

• To take advantage of complex date-tracked information.• To perform complex compensation calculations.• To create various formats for addresses.• To implement row-level security.

Oracle only supports user-defined functions that are usable from standard SQL with Oracle Database version 7.1 and later. NoetixViews for Oracle Human Resources is compatible with Oracle Database version 9.2 or later. Function performance is dependent upon the Oracle Database versions, and the later versions of Oracle Database exhibit higher function performance.

Optional InformationInformation that is optional in Oracle Human Resources Management System (HRMS), such as jobs and positions information, should only be included if you intend to use it. Because of the flexibility in defining and assigning jobs and positions inherent in Oracle HRMS, this information may be defined within an Oracle HRMS instance yet never used. When you search for information with an optional field or column, Oracle does not perform the most efficient search. Noetix alleviates this problem by associating columns with indexed fields. Again, these columns are search by columns and are identified with the prefix A$.


NoetixViews for Oracle PayrollOracle Payroll stores all payroll information at the most granular level. This makes the data structure highly complex and the data difficult to manage. NoetixViews for Oracle Payroll simplifies the complex data structure by providing predesigned views for key payroll areas, such as employee earnings, employee deductions, employee taxes, employer liabilities, registers, costing, and various employee exceptions.

To create reports from such complex and huge data, the data must be summarized first. This process is very time-consuming. NoetixViews for Oracle Payroll accelerates this process by creating intermediate summary tables. These tables are created by computing balances for every assignment per payroll run.

Oracle makes frequent changes to the data structure of Payroll due to the frequent changes in the employment law. The upgrade protection feature of NoetixViews for Oracle E-Business Suite (NoetixViews) protects the reports developed by NoetixViews for Oracle Payroll from these changes.

NoetixViews for Oracle Payroll uses the data mart technology to simplify the complexities of Payroll. Most of the views of the NoetixViews for Oracle Payroll module are built on Noetix Payroll Data Mart. For a list of these views, see About Noetix Payroll Data Mart.

NoetixViews for Oracle Payroll contains approximately 30 views, providing both a broad and deep insight into the payroll data. Many of these views can be joined to the Oracle Human Resources views for more information about employees, pay rates, and so on. The Payroll views are available for the United States, Canadian, Australian, and United Kingdom legislations. However, Cross Operations Extension (XOP) views cannot be generated for payroll views because they would not return valid results.

NoetixViews for Oracle Payroll uses the same security model as NoetixViews for Oracle Human Resources. For more information about Human Resources security in NoetixViews, see Security Policies in Views for HRMS.

For more information about the payroll views, see the Noetix Help File.


About Noetix Payroll Data MartNoetix Payroll Data Mart helps in computing and saving balances for every assignment per payroll run. These balances can be used for reporting and not for making a balance call.

Noetix Payroll Data Mart computes all the balances for each payroll run for the most commonly used dimensions that include RUN, Period-to-Date, Month-to-Date, Quarter-to-Date, and Year-to-Date. These balances will be used for reporting because it makes the query performance faster than the Oracle delivered balance calls.

IMPORTANT: Noetix Payroll Data Mart can be set up only in a Microsoft Windows operating environment.

The following views of the NoetixViews for Oracle Payroll module are built on Noetix Payroll Data Mart either directly or indirectly through a base table that uses the data mart technology:

• PAY_Accruals• PAY_Balances• PAY_Custom_Balances• PAY_Deductions• PAY_Earnings• PAY_Employer_Ben_Liability• PAY_Employer_Tax_Liability• PAY_Garnishment_Balances• PAY_Gre_Totals• PAY_Gross_And_Net_Balances• PAY_Gross_To_Net_Details• PAY_Gross_To_Net_Summary• PAY_Negative_Balances• PAY_Tax_Balances• PAY_Third_Party_Balances• PAY_US_Payroll_Register• PAY_US_W2_Register


Before Installing Noetix Payroll Data MartThis section provides information about the tasks to be performed before installing the Noetix Payroll Data Mart.

Install Oracle PayrollThe Payroll application must be successfully installed before installing Noetix Payroll Data Mart.

Calculate TablespaceYou must calculate the tablespace necessary for the data mart indexes and tables before beginning the generation. The storage required for 1,000 employees per pay period is approximately 7 MB. The EIS Datamart DB Stats.xls workbook, found in the Payroll_Datamart.zip file, can be used to calculate the tablespace. The workbook will help you to estimate the data storage space needed for the number of employees and payroll frequency in your organization. However, the calculation may not always be accurate.

You can use an existing tablespace if it has the required space. Otherwise, you must create a tablespace. During the generation of Noetix Payroll Data Mart, a script is run to select or create this tablespace. It is recommended that you create separate tablespaces for indexes and tables.

Installing Noetix Payroll Data MartThis section provides information about the tasks that must be performed to install Noetix Payroll Data Mart.

IMPORTANT: Noetix Payroll Data Mart must be installed before generating Noetix views. Otherwise, you will not be able to install the NoetixViews for Payroll module.

For information about generating views, see Option 1: Generate Using NoetixViews Administrator and Option 2: Generate Using Scripts in “Generation of Views.” For information about upgrading NoetixViews, see Upgrade the Software in “Installing NoetixViews for Oracle E-Business Suite.” Verify the generation before continuing.


How to Install Noetix Payroll Data MartNOTE: If you are upgrading from one version of the data mart to another, see Upgrade Noetix Payroll Data Mart.

To install Noetix Payroll Data Mart:1. Navigate to Datamart/Payroll.

2. Unzip the Payroll_Datamart.zip file, and extract all the files to a local directory. The directory path cannot contain spaces and more than 79 characters. The maximum number of characters is a limitation of SQL*Plus.

3. Log on to SQL*Plus as the APPS user.

4. Modify the EIS_Datamart_DBA_Install.sql script to change the path and size of the data file (tablespace). The default is a locally managed tablespace. You can change this to a dictionary managed tablespace to suit your environment. If an existing tablespace is used, delete the section in the script that is used to create the tablespace.

5. Run the EIS_Datamart_DBA_Install.sql script. This script prompts for the following parameters:

• SID: Database connect string where the data mart should be installed.

• SYSTEM Password: SYSTEM password to create the database user XXEIS and the tablespaces required for tables and indexes.

6. Run the EIS_Datamart_Install.sql script. This script prompts for the following parameters:

• Directory: Directory in which the zip file has been extracted. Do not put a \ at the end.

• SID: Database connect string where the data mart should be installed.

• APPS User Name: User name of the APPS user. It is usually APPS unless changed during the installation of Oracle E-Business Suite.


• APPS Password: APPS Password to give grants to XXEIS on the objects and create the custom application, responsibility, and user.

• XXEIS Password: The password to create the tables, sequences, packages, synonyms, and triggers in the XXEIS schema. This password was set while running the EIS_Datamart_DBA_Install.sql script to create the XXEIS user. If the password has not been changed, it would be xxeis.

• Tablespace for XXEIS Tables: Tablespace in which the data mart tables will be created. Proper sizing of the tablespace must be done. Give the same tablespace that was created for tables using the EIS_Datamart_DBA_Install.sql script.

• Tablespace for XXEIS Indexes: Tablespace in which the data mart indexes will be created. Give the same tablespace that was created for indexes using the EIS_Datamart_DBA_Install.sql script.

• Datagroup Name: Datagroup to which the XXEIS user must be attached. The default value is Standard.


Objects Created During GenerationThe following application objects are created during generation:

Object Name Object Type Description

XXEIS Database User It is used to store all the objects of the data mart. The same user will be used for any future applications from Noetix Payroll Data Mart.

XXEIS Custom Application

Custom Application

It is registered as part of the generation. All the concurrent programs will be created with this application.

XXEIS Payroll Data Mart Menu

Application Menu

It will be used to submit any concurrent pro-grams of the data mart.

XXEIS_DM Application User

It is the default data mart user created with the XXEIS Payroll Data Mart responsibility to submit the concurrent programs. The default password is welcome1.

XXEIS Payroll Process

Request Group

It has all the data mart concurrent programs.

XXEIS Payroll Data Mart

Responsibility It is granted to any user who has to submit the concurrent programs, mainly EIS Gener-ate Balances, which is used to populate the data mart.

EIS Generate Balances Pro-cess

Concurrent Program

It is used to populate the data mart. For more information, see step 3 in “Populate Data Automatically.”

EIS Generate Balances Date Range Process

Concurrent Program

It is used to populate the data mart. This enables you to set a start date and an end date for which balances are to be populated. For more information, see the note after step 3 in “Populate Data Automatically.”

EIS Payroll Datamart Purge Process

Concurrent Program

It is used to purge the balance in the data mart that is not required. For more informa-tion, see Purge Noetix Payroll Data Mart.


Populating Noetix Payroll Data MartAfter Noetix Payroll Data Mart is installed, balances must be extracted for the past payroll runs to populate the data mart tables. An administrator who is aware of the reporting needs for this data must perform this task. The administrator must know how many years of data need to be extracted. It is recommended that you use at least the previous year and the current year’s data.

IMPORTANT: Do not begin the population of data prior to running Stage 4 of the Noetix views generation. Otherwise, the generation will fail because the system cannot grant execute permission to the EIS_Utility package. If you want to run these processes at the same time, you may begin populating data after the role prefix editing step begins in the Noetix views generation.

The data mart tables can be populated either automatically or by scheduling.

When the data is populated automatically, the data mart gets populated every time a payroll is run. Typically, it would add 1-12% of the overall payroll processing time.

EIS Payroll Datamart Purge Date Range Process

Concurrent Program

It is used to purge the balance in the data mart that is not required. This enables you to set a start date and an end date for which balances are to be purged. For more infor-mation, see Purge Noetix Payroll Data Mart.

EIS Worker Process

Concurrent Program

It is the thread program spawned by the EIS Generate Balances for multi-threading the payroll process. This can be manipulated for performance reasons. For more informa-tion, see the Oracle documentation.

EIS Grant Access to Accrual Plans Process

Concurrent Program

It must be run when any accrual plan is cre-ated. For more information, see Grant Access to Accrual Plans.

Object Name Object Type Description


When the data population is scheduled, the data mart gets populated at the scheduled time. It can be scheduled periodically based on the reporting needs of the organization. You can also choose to do it manually without scheduling. If you do so, you will have to populate the data manually every time you run a payroll.

NOTE: When the number of employees in the organization is not very large, it is recommended that the data be populated automatically. Otherwise, it is recommended that the data population job be scheduled.

Populate Data AutomaticallyTo populate data automatically:1. Ensure that the Oracle Balance Initialization process has been completed and

verified in the Payroll application.

2. Log on to Oracle E-Business Suite with the following credentials:

• User name: XXEIS_DM

• Password: welcome1

• Responsibility: XXEIS Payroll Datamart

When you log on for the first time, you will be prompted to change the password.

3. On the Concurrent Manager, click XXEIS Payroll Datamart > Processes and Reports > Submit Processes and Reports to run the EIS Generate Balances process to gather the balances and store them in the data mart.

This process requires the following parameters:

• Start Year: Start year for which balances need to be extracted.

• End Year: End year for which balances need to be extracted.


• Enable Triggers (Yes or No): Set it to Yes. It enables the data mart triggers. After every successful payroll run, this populates the data mart summary tables automatically for all the future payroll runs. Data will be immediately available for reporting. The default value is Yes.

• Remove All Current Data (Yes or No): When set to Yes, it removes all the existing data and repopulates the data for the given parameters. The default value is No. Set this value to Yes only if needed.

NOTE: Instead of the EIS Generate Balances process, you can also run the EIS Generate Balances Date Range process. This process enables you to set a start date and an end date for which balances are to be populated in the data mart. There is also an optional balance name parameter that can be used to generate the balances in the data mart for only a single balance. This option is useful when a specific balance has been incorrectly populated in the data mart and needs to be repopulated. But before repopulating the data mart, the specific balance needs to be purged in the data mart from the time the data mart has been populated. The remaining parameters are the same for both the processes.

4. While the EIS Generate Balances process is running, gather statistics for the XXEIS schema every 30 to 40 minutes. This will greatly improve the performance of the process. This is needed only during the initial population of the data mart with payroll history, and not for subsequent populations.

Populate Data by SchedulingThe only difference between populating data automatically and scheduling it is in the value that is set for the Enable Triggers (Yes or No) parameter. The value for the Enable Triggers (Yes or No) parameter is set to No when you schedule the population of data. All other steps are the same.

For information about scheduling data population job, see steps 1 through 3 in “Populate Data Automatically.” After you specify the values for all the parameters, you can schedule the job as a Concurrent Manager task.

Maintain Noetix Payroll Data MartTo maintain Noetix Payroll Data Mart, some tasks must be performed periodically after the initial population of data. This section provides information about all those tasks.


Purge Noetix Payroll Data MartYou can use the EIS Payroll Datamart Purge process to purge the data that is not required.

To purge balances:1. Log on to Oracle E-Business Suite as the APPS user.

2. On the Concurrent Manager, run the EIS Payroll Datamart Purge process. This process requires the following parameters:

• Start Year: Start year for which the balances need to be purged.

• End Year: End year for which the balances need to be purged.

• Balance Name: This is an optional parameter that allows purging a specific balance from the data mart. If this parameter is not supplied, then all balances will be purged from the data mart.

NOTE: Instead of the EIS Payroll Datamart Purge process, you can also run the EIS Payroll Datamart Purge Date Range process. This process enables you to set a start date and an end date for which balances are to be purged in the data mart. The remaining parameters are the same as the EIS Payroll Datamart Purge process.


Update Noetix Payroll BalancesWhenever there is a change in the balance feeds, the data mart must be updated with the latest data. You can update the data mart in the following two ways:

• Update automatically: This is same as populating the data automatically. For information, see steps 1 through 3 in “Populate Data Automatically.”

• Update by scheduling: This is same as populating the data by scheduling. For information, see Populate Data by Scheduling.

You would either need to purge the data mart or set the Remove All Current Data (Yes or No) parameter to Yes depending on the changes that are made to the data mart.

Gather StatisticsMany of the Noetix Payroll views use cost-based optimization. To take full advantage of this, it is necessary to gather statistics on a regular basis, ensuring that the XXEIS schema is included. For more information, see the Oracle documentation.

Grant Access to Accrual PlansIn Oracle Human Resources Management System (HRMS)/Payroll, whenever a accrual plan is created or any change is made to an existing accrual plan, Payroll dynamically creates fast formula packages. For NoetixViews to function properly, the XXEIS user needs to have grants for these newly created packages.

The EIS Grant Access to Accrual Plans concurrent program will create these grants. This process needs to be run each time an accrual plan is created or changed.

To grant the XXEIS user the access to accrual plans:1. Log on to Oracle E-Business Suite with the following credentials:

• User name: XXEIS_DM.

• Password: The password that you defined earlier. If you have not changed it, then it is welcome1.

• Responsibility: XXEIS Payroll Datamart.


2. On the Concurrent Manager, click XXEIS Payroll Datamart > Processes and Reports > Submit Processes and Reports to run the EIS Grant Access to Accrual Plans process to create grants to any new or modified accrual plans. This process does not require any parameters.

After running the concurrent program, the grants for these dynamically created packages are given to XXEIS, and the NoetixViews accrual views will reflect the changes.

Upgrade Noetix Payroll Data MartIf you have previously installed Noetix Payroll Data Mart, you have to upgrade your generation for the latest version of the data mart. Upgrading the data mart will not change the current data that is stored in the data mart; it will only upgrade the version with latest software components related to Noetix Payroll Data Mart.

IMPORTANT: Noetix Payroll Data Mart must be upgraded before upgrading NoetixViews for Oracle Payroll. Otherwise, you will not be able to upgrade the views.

To upgrade Noetix Payroll Data Mart:1. Navigate to Datamart/Payroll.

2. Unzip the Payroll_Datamart_Upgrade.zip file, and extract all the files to a local directory. The directory path cannot contain spaces and more than 79 characters. The maximum number of characters is a limitation of SQL*Plus.

3. Log on to SQL*Plus as the APPS user.

4. Run the EIS_Datamart_Upgrade.sql script. This script prompts for the same parameters that are prompted when running the EIS_Datamart_Install.sql script. Only the parameters for tablespaces are not prompted as you have it already during your first generation. Give the same information that you had given during your first generation. To continue with the upgrade process, see step 6 of “Installing Noetix Payroll Data Mart.”


Uninstall Noetix Payroll Data MartTo uninstall Noetix Payroll Data Mart:1. Run the EIS_Datamart_Uninstall.sql script to delete all XXEIS objects.

This script prompts for the following parameters:

• SID: Database connect string where the data mart is located.

• APPS User Name: User name of the APPS user. It is usually APPS unless changed during installation of Oracle E-Business Suite.

• APPS Password: APPS Password to delete the user, responsibility, and custom application.

• XXEIS Password: The password to delete the packages, triggers, synonyms, tables, and sequences in the XXEIS schema. This password was set while running the EIS_Datamart_DBA_Install.sql script to create the XXEIS user. If the password has not been changed, then it would be xxeis.

2. Manually remove the XXEIS user and tablespaces. They were originally created while running the EIS_Datamart_DBA_Install.sql script.


NoetixViews for Oracle Projects

NOTE: In accordance with the changes implemented in Oracle E-Business Suite Release 12, the term "base currency" has been replaced with "primary currency" and the term "foreign currency" has been replaced with "transaction currency."

NoetixViews for Oracle Projects provides a solution for maintaining control and visibility of projects. It displays project information at a single source point enabling you to track and manage a project through the project lifecycle.

NoetixViews for Oracle Projects includes approximately 50 views that cover various project types such as capital, contract, and indirect. The subject areas covered are projects, tasks, resources, budgets, expenditures, invoices, revenues, and status inquiry. These views belong to the basic, value added or cross functional type and additionally are categorized as detail or summary-level views.

Detail views present transaction details as entered in Projects. Usually, these transactions can be entered in various currencies. All detail views include one or more transaction currency amount, as well as converted project and project functional currency amounts. A currency-code column differentiates the currency types for the user.

Summary views require the summation of individual transaction amounts. Therefore, summary views show the amounts in a single currency. The project functional currency and currency-code columns are not displayed.


BackgroundIn Oracle E-Business Suite 10.7, the Oracle Project Costing module had the facility to enter receipts in multiple currencies. Oracle expanded the multi-currency functionality within the Project Costing module with Oracle E-Business Suite 11.0.3 and then further extended the multi-currency support to Oracle Project Billing with Oracle E-Business Suite 11.5.8, Family Pack J.

NoetixViews for Oracle Projects introduces compatibility for Oracle E-Business Suite 11.5.10 and earlier and now supports Projects' multi-currency functionality in the areas of Project Accounting, Project Costing, and Project Billing.


Multi-Currency Terminology in Oracle Projects

Terminology Definition

Agreement Currency (AC) The currency mentioned on agreement in which funding is done.

Bill Transaction Currency (BTC)

This can vary between an expenditure item, an event, and a billing schedule. After an amount is derived in bill transaction currency during revenue and invoice processing, the rest of the amounts in various currencies, namely project functional cur-rency, project currency, and invoice currency are derived based on the Bill Transaction Currency. In other words, it is the single point arrived at first, and then the rest of the currency amounts are derived.

Denom Currency The currency in which expenditure is recorded against a project. This can also be treated as a trans-actional currency for the expenditure/costing pro-cess.

Functional Currency (F) This is the single common currency used for book keeping and is specific to operating units and led-gers. This terminology is used in all subledger mod-ules and is called project functional currency in project modules.

Funding Currency (FC) The currency in which the project is funded.

Invoice Currency (IC) Invoices will be raised in this specific currency while billing project customers.

Invoice Processing Currency (IPC)

Funding and invoice amounts are converted to this currency to check against funding and evaluate hard and soft limits. This can be one of the follow-ing values: Project Functional Currency, Project Currency or Funding Currency. Only one value is valid for a project, and this cannot be changed after the initial expenditure is booked.


For more information about multi-currency functionality in Projects, see the Oracle documentation.

For information about various subject areas in Projects, see Subject Areas in Oracle Projects.

Effect of Multi-Currency on Different Types of ProjectsIn Projects, amounts entered through transaction entry dialog boxes are in corresponding transaction currencies. For example, when a particular project is funded, it may be treated as a funding transaction. When a customer is invoiced, it may be treated as an invoicing transaction. Given each transaction amount, each implementation or setup dictates the currency type for converting each amount.

Capital Projects transactions will include agreements, funding, and expenditures. These transactions will be grouped to be posted into assets. No billing activity takes place for these types of projects. Indirect projects may include the same transaction types, but neither asset creation nor billing to the customer will take place for indirect projects. Finally, contract projects may span across all types of transactions in Projects except asset creation.

Project Currency (PC) The currency to which all transactions of a project are converted for processing and summarization. This can be defined per project.

Project Functional Currency (PFC)

The principal currency in which accounting data is maintained in Projects. Same as functional currency in subledger modules. There is one project func-tional currency for each operating unit.

Receipt Currency This currency information will be entered as a transactional attribute while recording expenditure.

Revenue Processing Currency (RPC)

Revenue is processed using a common currency called the revenue processing currency which is always the project functional currency.

Terminology Definition


Creating a report for a particular subject area with transactions in a particular currency type is a simple report. However, when the same information is shown for a combination of subject areas with multiple currencies in each subject area, it becomes increasingly complex. The amounts must be converted into values having a common denominator to facilitate valid comparison. For example, a budget-to-actual view and/or report should show a common currency type to easily compare budget amount with the actual or expense amount.

It is for this reason that the Oracle E-Business Suite’s folder feature defaults a currency type that displays the amounts in each subject area and allows you to toggle to view currency columns in different currency types, if selected.

Multi-Currency Activation in NoetixViews for Oracle ProjectsYou can activate multi-currency columns in NoetixViews for Oracle Projects during Stage 4 of the generation process.

Prerequisites for Multi-Currency Activation• Oracle E-Business Suite 11.5.8 or later must be installed.

• Oracle Projects must be installed.

• NoetixViews for Oracle Projects must be purchased.

Activating the Multi-Currency ColumnsOn detecting the required software during Stage 4 of the generation process, NoetixViews for Oracle E-Business Suite (NoetixViews) prompts you to choose whether the new multi-currency columns should be generated in NoetixViews for Oracle Projects.

NOTE: NoetixViews does not determine whether you are actually using the Projects’ multi-currency functionality.


For information about activating the multi-currency columns:

• Using NoetixViews for Oracle E-Business Suite Administrator (NoetixViews Administrator), see Activate Multi-Currency Columns for Projects Views (Optional) in “Generation of Views.”

• Using scripts, see Activate Multi-Currency Columns for Projects Views (Optional) in “Generation of Views.”

NOTE: It is possible to implement the multi-currency functionality in NoetixViews for Oracle Projects without activating the feature in Oracle E-Business Suite. Noetix recommends that you activate the multi-currency columns in NoetixViews only if your functional experts confirm that you are currently using multiple currencies in Projects, or you intend to use this Oracle feature in the future.

Results of Multi-Currency ActivationActivating multi-currency columns in NoetixViews for Oracle Projects results in the following changes:

• All transactional views have transaction-specific currency values in the base amount columns. Additional columns for project functional currency (with _PFC suffix) and project currency (with _PC suffix) may also be generated. These additional columns are not added for every occurrence of a transactional amount column. Most of the _PFC columns corresponding to the transaction-amount columns are generated. Some of the _PC columns corresponding to the transaction-amount columns are also generated. You cannot summarize on the transaction-amount columns with this option as the columns can be in multiple currencies. You must summarize the transaction-amount columns based on the corresponding _PFC or _PC columns.

NOTE: An expense amount in Project Currency might not equate to the Payables Functional Currency amount for the same transaction.

• Information related to currency codes and exchange rates is generated.


NOTE: If you use the multi-currency functionality of Projects at your site, you must activate multi-currency columns in your views. Otherwise, the amount columns in your views will contain values in project functional currencies, and not display information related to currency codes and exchange rates.

Changing the Multi-Currency Option While Regenerating Noetix ViewsIf you changed your choice to activate multi-currency columns since your last generation, NoetixViews displays a caution message, which would help you to decide whether to generate multi-currency columns in your Projects views during a regeneration. If you did not activate the multi-currency columns earlier and choose to do so now, then additional columns will be generated in your Projects views, and values in the amount columns will be in transactional currencies.

If you activated the multi-currency columns earlier and choose not to do so now, the multi-currency columns will not be generated in your Projects views. NoetixViews are impacted as follows:

• All summary views will have project functional currency values. This is the same if the multi-currency option is active.

• All transactional views will use project functional currency in the amount columns. There are a few exceptions to this rule such as agreement and funding currency amounts.

• The currency codes and exchange rate columns will not be generated. It is assumed that all amounts are in the project functional currency.

Reports based on these views will change in either situation. Therefore, preferably, after you decide to activate or not activate multi-currency columns, do not change your decision during a subsequent generation.


Subject Areas in Oracle ProjectsThe following table shows the subject areas of Projects, the related functional areas, Oracle dialog boxes, and the currency types that are supported for those subject areas. NoetixViews for Oracle Projects might not support all the currency types in all the subject areas shown, to maintain proper granularity of the result set (detail versus summary), as well as cross-functionality with other NoetixViews modules.

Subject area Functional area Dialog box name Currency type

Billing Agreements Agreements Agreement Cur-rency

Events Events Entry Bill Transaction Currency (BTC) Amount/BTC[In one way, this is a transaction on billing.]

Funding Fund Projects (Default Folder)

Funding Currency (FC)

Fund Projects (Mult-currency folder)

FC/FC amountPFC Amount/PFC CodeProject Currency (PC) Amount/PC Code

Invoice Review Lines Invoice Currency (IC) Amount/IC CodePC Amount/PC Code

Summary IC Amount/IC Code [that is, transactioncurrency for bill-ing]


Withheld amount inquiry

BTC, FC, Invoice Processing Cur-rency (IPC), PFC, and PCamounts and codes

Retention Retention Inquiry PFC Amount/PFC CodePC Amount/PC CodeFC Amount/FC Code

Budgets Budgets Budgets/Budget Lines

Always Project Functional Cur-rency (PFC)

Expenditures Expenditure Expenditure Inquiry - Cost Distributions

FC/AmountPFC Amount/PFC CodePC Amount/PC CodeTransaction Amount/Transac-tionCurrency Code

Expenditures (Multicurrencyfolder) - Allowed only for expense reports.

Reimbursement Currency(Denom Currency) (Transactionalcurrency for Expenditure)Receipt Currency can beentered.

Revenue Revenue Distribu-tion

Expenditure Inquiry -Revenue Distribu-tions

PFC Amount

Revenue Inquiry Revenue Lines PFC Amount



Revenue Sum-mmary

PFC Amount/PFC Code

PSI Project Status Inquiry

Commitments PC Amount

Events PFC Amount

Invoices Similar to Invoice Inquiry dialog box

Resource Status PFC AmountPC Amount

Summary PFC AmountPC Amount

Task Status PFC AmountPC Amount



NoetixViews for Oracle U.S. Federal Financials

Oracle U.S. Federal Financials provides a financial management solution to the U.S federal agencies, that complies with the mandates of U.S. Federal Guidelines. NoetixViews for Oracle U.S. Federal Financials provides predesigned views that cover all the functionality in U.S. Federal Financials, such as budgetary control, fund accounting, cost accumulation and allocation, multiple receivable line accounting, maintaining United States Standard General Ledger (US SGL) accounts, maintaining treasury cash accounts, and having multiple organization capabilities. NoetixViews for Oracle U.S. Federal Financials include about 50 views that deal with these functional subject areas of U.S. Federal Financials. These views belong to the basic and cross functional types.

The basic views of NoetixViews for Oracle U.S. Federal Financials cater to the application functionality provided by the Federal Administrator responsibility. Noetix query users with the Noetix roles of Federal Administrator can access these views.

The cross-functional views of U.S. Federal Financials link the Oracle General Ledger, Oracle Receivables, Oracle Payables, and Oracle Purchasing modules with U.S. Federal Financials. For the support of U.S. Federal Financials cross functional views, Noetix Corporation has extended the functionality of the existing views for General Ledger, Receivables, Payables, and Purchasing to include columns that link up these modules with U.S. Federal Financials. For example, in the General Ledger view GL_Journal_Entries, columns such as Fund_Check_Status, Je_Batch_Transaction_Code, and Je_Header_Transaction_Code have been added. Similarly, in the Purchasing views PO_Purchase_Orders and PO_Requisitions, the PO_Header_Transaction_Code and Req_Header_Transaction_Code columns have been added respectively. These views can be accessed by Noetix query users having the appropriate roles for each of the modules.


The funds availability views are categorized into summary and detailed views. Noetix extracts the data displayed on the Funds Available Inquiry window of the U.S. Federal Financials module and replicates it into two summary views, FV_Funds_Avail_By_Fund and FV_Funds_Avail_By_Treas_Sym. These views provide information about the available funds in an organization, summarized on the basis of the funds and treasury symbols. The detail views provide information about the basic functional areas of the U.S. Federal Financials and related modules, such as, budget, expenses, obligations, and commitments. They provide transaction-level details which can be further summarized. This summarized data can be matched with the summary views and be used for the purpose of data drilldown.

IMPORTANT: The Noetix views for U.S. Federal Financials are secured on the basis of the ledgers. However, the following views are also secured by budget levels:

• FV_Budget_Appr_GL_JE

• FV_Budget_Auth_SLA_GL_JE

• FV_Budget_Authority_Trans

• FV_Budget_Transactions

• FV_Fund_Distr_GL_JE

• FV_Fund_Distr_SLA_GL_JE

• FV_Fund_Distributions

• FV_SLA_Budget_Trans

Only those users who are assigned appropriate budget levels through the Security Manager dialog box can have access to these views. For information about defining custom security for Noetix query users, see step 7 in “Add a Noetix Query User Using an Existing User” in “Noetix Query User Management.”


Subject Areas of NoetixViews for Oracle U.S. Federal FinancialsThe following table displays the subject areas of the NoetixViews for Oracle U.S. Federal Financials, modules related with the subject areas, Noetix roles for the views, and approximate number of the views pertaining to the subject areas:

Subject areas Modules involved Noetix roleApproximate number of views

Budget levels,budget distributions,transaction typesappropriation or fund parameters,fund groups or treasury account codes,enhanced transactions,transaction codes,federal account symbols,appropriation parameter authorizations,other authorizations,budget appropriations,funds distributions, and funds availability

Oracle U.S. Federal Administrator

Federal Administrator

20

Budget appropriations and fund distributions

Oracle U.S. Federal Administrator and Oracle General Ledger

Federal Administrator

2

Journal entry

Oracle U.S. Federal Administrator and Oracle General Ledger

General Ledger

2


Finance charges, transaction code mapping,interagency transfer,invoice status history,cash receipts,accrue finance charges, and invoice write-off

Oracle U.S. Federal Administrator and Oracle Receivables

Accounts Receivables

7

Interagency transfer,assign reason codes,invoice returns,treasury confirmation,invoice payments, and purchase invoices

Oracle U.S. Federal Administrator and Oracle Payables

Accounts Payables

11

Purchase orders,purchase order receipts, andrequisitions

Oracle U.S. Federal Administrator and Oracle Purchasing

Purchasing 6

Subject areas Modules involved Noetix roleApproximate number of views

Appendix B

Legal Notices


Third-Party License TermsThe applications grep, egrep, and sed are distributed with the NoetixViews for Oracle E-Business Suite (NoetixViews) and NoetixViews for Oracle E-Business Suite Data Warehouse Edition software under the GNU General Public License. Noetix hereby offers to give any third party, for a charge no more than our cost of physically performing the distribution, a complete computer-readable copy of the grep, egrep and/or sed source code, which shall be distributed under the GNU General Public License and supplied on a medium customarily used for software interchange. Requests for source code must be submitted within three years of this offer, and should be directed to Noetix Corporation, 5010 148th Avenue NE, Suite 100, Redmond, WA 98052-5119, USA.

GNU GENERAL PUBLIC LICENSE

Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc.

675 Mass Ave, Cambridge, MA 02139, USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

Preamble

The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to ensure that the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to ensure that you have the freedom to distribute copies of free software (and charge for this service if you want), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to

Appendix B: Legal Notices 391

certain responsibilities for you if you distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must ensure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.

Also, for each author’s protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.

Finally, any free program is threatened constantly by software patents. We want to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and modification follow.

GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The “Program”, below, refers to any such program or work, and a “work based on the Program” means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term “modification”.) Each licensee is addressed as “you”.

Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.


You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:

1. You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.

2. You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.

3. If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.

In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

Appendix B: Legal Notices 393

3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

1. Accompany it with the complete corresponding computer-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

2. Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete computer-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

3. Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.

If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.


6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.

Index

The index provides a quick way to look up topics and keywords used in this administrator guide.


AAccounting Flexfield, 91, 316

Accounting Flexfield security rules, 168

add budget access level, 149

add business groups, 140

add flexfield security rules, 170

add inventory organizations, 161

add ledgers, 147

add operating units, 154

add query users using script, 190

add roles, 174

add service request types, 166

Add Wizard, 177

adding responsibilities, 132

adding users, 132

administrative privileges, 31

all responsibilities, 319

Applications tables, 88, 89, 105

application-specific security, 218

APPLSYS user, 74, 101

“Apps” user, 74, 122

Apps-mode security, 4, 120generating into NQS, 122

archived data for General Ledger, 317

Bbase installation directory, 235

benefit element information, 357

budget organizations, 316

business group security, 135

Business Group tab, 135

Cchanging installation directory, 34

chart of accounts, 14, 205and XOP Roles, 17

checkenv.sh script, 240

clear.bat script, 242

COA suppression, 256

Concurrent Managercreating a custom application, 269–270defining concurrent program, 275–277environment, 262grant permissions to APPS objects (EBSO

environment), 275populate password file (standard

environment), 274populating parameter file, 270–273scheduling regeneration, 278–279

configure default flexfield security rules setting, 323

cparam.sql script, 271, 281

cpw.sql script, 274, 285

create synonyms, 134

Croncreating a directory for regenerations, 281deleting a scheduled regeneration, 291environment, 262, 286–287scheduling regeneration, 287–291set up the environment, 286valid time values, 288–289viewing status, 291

crontab file, 240, 281, 287, 291, 292

Cross Operations Extension (XOP), 10–17and Inventory roles, 17calendar periods, 16generating

using scripts, 105security, 11

Index 397

Ddata access privilege, 213

Data Security in NoetixViews, 208

Database User, 4, 120

DateTrack, 343in NoetixViews for Human Resources, 346

default flexfield security rules, 323

Discoverer, Oracleupdating security, 230

Eeffective responsibility, 319

errorsduring generation, 60, 85, 94, 109during upgrade, 46, 49in DateTracking, 357

Extra Information Type (EIT) views, 342joining, 342supported types, 342

Ffinderr.bat script, 109, 242

flexfield security rules, 317all responsibilities, 318effective responsibility, 318

flexfieldsdescriptive flexfields, 342, 357flexfield security rules, 316See also Accounting Flexfield

full refresh, 245

functions in NoetixViews for Oracle Human Resources, 361

GGeneral Ledger. See NoetixViews for Oracle

General Ledger

General tab, 130

generationchoosing methods for generation, 62generate using NoetixViews

Administrator, 63–95global views, 18list of steps for script-based method, 97pausing & resuming, 66preparing files & directories for scripts

generation, 43script-based generation, 97–114verifying generation

after generating using NoetixViews Administrator, 93–94

after script generation, 109

generation scriptsianswers.sql, 241iguifs.sql, 242inst4cm.prog, 242inst4cron.sh, 240install1.sql, 242install2.sql, 242install3.sql, 242install4.sql, 242listcnfg.sql, 242setup.sh, 240

Get Passwords Wizard, 88

Grant Select Any Table/Dictionary tool, 237

HHTML Help, 61, 96

See also Noetix Help Systempublishing the Help, 114, 299, 304

Human ResourcesSee NoetixViews for Oracle Human ResourcesOracle Date Tracking, 343

managing records in date-tracked table, 344

Using date tracking in NoetixViews for Human Resources, 349


Ii_create_sm_users.sql script, 241

iallhlp.sql script, 110, 241, 299

ianswers.sql script, 241, 296

icomhlp.sql script, 110, 241, 299

iconcmgr.sql script, 241, 275

iconnect.sql script, 232, 241

icronenv.sh script, 240, 286

icrontab.sh script, 240, 287

idelqusr.sql script, 207, 241

ifix4sts.sql script, 86, 94, 104, 109, 241, 265, 267, 279, 291, 297

igetprm.sql script, 241, 271, 282

igetpw.sql script, 242, 274, 285

iguifs.sql script, 242

ihtmlhlp.sql script, 110, 242, 296, 299

imshlp.sql script, 110, 242, 296, 299

incremental refresh, 246

inst4cm.prog script, 242, 270

inst4cron.sh script, 240, 290

install1.sql script, 98, 242




instuser.sql script, 197

inventory organization security, 157

Inventory Organization tab, 157

Inventory rolesand Cross Operations Extension (XOP), 17generating

using NoetixViews Administrator, 82

Jjoining

extra information type (EIT) views, 342special information type views, 341

Kkey flexfield views

columns, 25data cache table, 21integration with global views, 21–22

Llanguage code, 200

language, translation, 80, 102, 190

ledger security, 143

Ledger tab, 143

listchng.lst file, 47, 49, 265, 267

listchng.sql script, 47, 49, 242, 265, 267

listcnfg.sql script, 242

listinfo.sql script, 242

listjoin.sql script, 242

logon errors, checking, 240

MMaster/Unix directory, 41

Microsoft Windows Help, 61, 95, 299, 300, 305See also Help Systemand Noetix Easy Help Wizard, 111, 300, 305compiling the Help, 111–113, 301–303publishing the Help, 114, 303

multi-currency, 6

multi-currency columnsactivating using scripts, 105

Index 399

NNoetix Answer Builder, 85, 115

Only regeneration, 273only regeneration, 279, 284run Noetix Generator for Noetix Platform—

Oracle E-Business Suite Edition, 115running, 115

Noetix Easy Help Wizard, 111, 300, 305See also Microsoft Windows Help

Noetix Generator for Noetix Platform—Oracle E-Business Suite Edition, 115

Noetix Generator for Oracle Discoverersecurity, 120, 121updating security, 230

Noetix Help System, 4See also specific help formats; Noetix Help

System scriptsdistributing to users, 95, 96generating

using NoetixViews Administrator, 86, 94–96

using scripts, 110regenerating, 297

scheduling with Cron or Concurrent Manager, 304–305

using NoetixViews Administrator, 298–299

using scripts, 299–300regenerating selected content, 273, 279, 284scheduling regeneration, 273, 284scripts for generating Help, 110types of Help, 61

Noetix Help System scriptsiallhlp.sql, 241, 296, 299icomhlp.sql, 241, 296, 299ihtmlhlp.sql, 242, 296, 299imshlp.sql, 242, 296, 299

Noetix Payroll Data Mart. See Payroll Data Mart, Noetix

Noetix Platformand NoetixViews, 7creating user accounts, 120, 122generating user accounts, 230

Noetix Query Users, 4and Discoverer security, 121configuring existing user using

scripts, 191–196creating accounts

using Security Manager dialog box, 177creating new accounts

using scripts, 190–198enabling features, 186generating into NQS, 120, 230recommendation for account creation, 123security options, 124

Noetix query userscreating, 127

Noetix Script Copy Wizard, 43, 48

Noetix System Administration User, 69, 122, 235changing base installation directory, 235configuring

using NoetixViews Administrator, 76–78using scripts, 101

creatingusing NoetixViews Administrator, 67–72using scripts, 98–100

default user name, 69enabling & disabling features, 239naming, 59schema, 122security, 239user type, 122

Noetix viewsgeneration

using NoetixViews Administrator, 63–96using scripts, 97–114

NOETIX_UNIX user, 269, 274, 281, 285

noetix.hlp file, 114, 303

noetix.rtf file, 112, 301


NoetixAnswers, 7, 115and Noetix Generator for Noetix Platform—

Oracle E-Business Suite Edition, 7

NoetixViewsadd-on products, 7

NoetixViews Administrator, 3installing, 31–38preinstallation considerations, 30running SQL scripts, 243running UNIX scripts, 241starting NoetixViews Administrator, 64tools & features, 234–240

for browsing to files, 236for changing base installation

directory, 235for disabling features, 239for granting “SELECT ANY TABLE”

privilege, 237for overriding Oracle tool versions, 238

upgrading, 44

NoetixViews for Human Resources, 327–361functions, 361optional views & columns, 360performance, 360salary calculations, 359setup business group, 359

NoetixViews for Oracle General Ledger, 314–326archived data, 317assigning security, 315, 317budget organizations, 316modifying General Ledger security for Noetix

query users, 200security, 5, 315–317

NoetixViews for Oracle Payroll, 362–374installing Noetix Payroll Data Mart, 364

NoetixViews for PayrollSee also Payroll Data Mart, Noetix

Oonline help. See Help System

operating unit security, 151

Operating Unit tab, 151

Oracle DateTrack, 343

Oracle E-Business Suite securityAPPLSYS account, 74, 101limitations on max Roles, 124

organizational unit security, 216

Pparameter file, 270, 281

passwordspopulating file for regenerations, 274, 285required for generation, 53

payroll data mart, Noetixcalculating tablespace, 364installing, 365–366pre-requisites for installation, 364uninstalling, 374

performanceand user profiles, 5of NoetixViews for Human

Resources, 360–361

permissions, changing on script files, 240

prefixesdefaults, 59, 91, 103editing

after generation, warning notice, 59during generation with NoetixViews

Administrator, 90–92during generation with scripts, 103during regeneration, warning, 264, 266during upgrades, warning, 47, 49

limits when scheduling regenerations, 262

pre-update processusing NoetixViews Administrator, 46using scripts, 49

procedure owner, 67

profiles, creating for users, 5

Index 401

Qqueries, runaway, 5

Query Tool Help, 61, 95See also Help System; query toolsdistributing to users, 299, 300, 305

query toolsand modifying users, 230performance, 188

Query User Maintenance utility, 199, 205

query users. See Noetix Query Users; user accounts; user accounts, administering

Rrefresh data cache tables, 245

refresh parent-child hierarchy data, 249

refresh. See regenerating; regenerating NoetixViews

Refreshing Security for Query Users, 208

regeneratingSee also regenerating NoetixViewsNoetix Help System, 297–305NoetixViews, 263–292

regenerating NoetixViews, 6, 263–292comparing old & new generations, 265failed regeneration, warning, 263methods for regenerating, 261–262

scheduling with Concurrent Manager, 268–279

scheduling with Cron, 280–292using NoetixViews

Administrator, 263–265using scripts, 266–267

populating parameter file, 281–284populating passwords file, 285reasons to regenerate, 260scheduling services, 262verifying script versions, 264vs. upgrading, 261

regeneration scriptsSee also generation scripts; regenerating

NoetixViews; regeneratingiconcmgr.sql, 241icronenv.sh, 240icrontab.sh, 240igetprm.sql, 241igetpw.sql, 242listchng.sql, 242

remove files, 242

requirements, system, 30

Roles tab, 172

Roles, NoetixViews, 5See also prefixesadding or removing, 204defined, 5

row-level security, 221

Run, 115

runaway queries, 5

Sscheduling regenerations

See also regenerating NoetixViews; scheduling scripts

methodsusing Concurrent Manager, 268–279using Cron, 280–292

restrictions on Role prefixes, 262

scheduling scriptsSee also regeneration scripts; regenerating

NoetixViewscrontab file, 281iconcmgr.sql, 275icronenv.sh, 286icrontab.sh, 287

scheduling services, 262


scriptschanging permissions on files, 240file formats, 41for generating Help, 110preparing files & directories, 43running

from a command line, 241in SQL*Plus, 241

SQL scripts, 241transferring files

using FTP client, 38, 41using Script Copy Wizard, 39–41

UNIX scripts, 240verifying script versions, 264

securitySee also Apps-mode security; Oracle E-Business

Suite securityassigning flexfield security rules, 317–322assigning General Ledger security, 315for General Ledger, 5, 315–317for General Ledger with XOP General Ledger

Roles, 17granting access to data, 120options for Noetix Query Users, 124security rules for General Ledger, 124“SELECT ANY TABLE ” privilege, 237

security rules, 5, 124, 315, 316

Security Rules tab, 168

security, derived from Oracle EBS, 138, 145

SELECT ANY DICTIONARY, 70

SELECT ANY TABLE, 70

Service Request tab, 163

service request type security, 163

setup.sh script, 42, 43, 240, 270, 281

special information type views, 340–342joining, 341

SQL scripts, 241

SQL*Loaderchanging version, 238

SQL*Pluschanging version, 238running scripts, 241

statusof Cron regeneration, 291of generation

using NoetixViews Administrator, 93–94using scripts, 109

suppress chart of accounts, 256

suppress parent-child hierarchy views, 254

system requirements, 30

Ttable owner, 67

tables for the Application Object Library, 73

tablespacecalculating for Noetix Payroll Data Mart, 364creating for generation, 54locally managed, 54storage location, 71temporary space, 71

The, 70

translation language, 80, 102, 190

tupdprfx.sql script, 242

Types of Noetix views regeneration, 273, 279, 284

UU.S. Federal Financials, 385

uninstalling NoetixViews Administrator, 308

UNIX scheduling service. See Cron

UNIX scriptsSee also specific UNIX scripts

upgrade scripts & filesiappspkg.sql, 241listchng.lst, 49listchng.sql, 47, 242preupd.sql, 49, 242

Index 403

upgrading NoetixViewsediting prefixes, warning, 47, 49generating answers, 47, 49methods


vs. regenerating, 261

upgrading NoetixViews Administrator, 44

user accounts, 4See also specific account names & types; Roles,

NoetixViews; user accounts, administeringcustom access for data, 205database user, 68security, 4, 120

user accounts, administering, 120See also user administration scripts; user

accountscreating database accounts, 180creating new accounts

using Query User Maintenance utility, 127–176

using scripts, 197–198using wizard, 177

creating profiles, 5deleting a user

using Query User Maintenance utility, 206using scripts, 207

modifying, 199–204

user administration scriptsinstuser.sql, 242

Vviews

See also specific module namescreating synonyms, 181, 186generating


naming conventions, 59–61owner, 59, 67regenerating using previous settings,

warning, 264, 266searching with wildcards, 60

Wwarning logs, 85

Web Help. See HTML Help

XXOP. See Cross Operations Extension (XOP)

ZZ$ columns list, script, 242

Administrator Guide - Magnitudesupport.noetix.com/docs/707/610/noetixviewsadministratorguide.pdf ·...

Documents

Transcript of Administrator Guide - Magnitudesupport.noetix.com/docs/707/610/noetixviewsadministratorguide.pdf ·...