Forms of Noetix Views

insigihtsoftwareoffers three forms of views for NoetixViews, namely standard, Cross Operations Extension (XOP), and global, to manage users access to view information pertaining to various organizational units, such as ledgers, business groups, operating units, and inventory organizations available in Oracle
E-Business Suite. The following list provides a brief description for standard, XOP, and global forms of views:

The standard form of views provides information pertaining to a specific organizational unit.

•  The XOP form of views provides information pertaining to one or more organizational units based on the settings configured for the chart of accounts in an Oracle E-Business Suite module.

The global form of views provides information pertaining to all the organizational units.

Note: The global form of Noetix views offers several benefits over the standard or XOP form of views. You can switch to the global form to avail these benefits for a better enterprise-wide reporting experience. For information about the utilities and processes that will help ease the transition of your views from the standard or XOP form to the global form, see Article No. 000014656 (INFO: How do I switch to global views?).

Standard Views

The 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 Views

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.”

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 Cross Operations Extension (XOP) is an extension to the 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.

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 Generated

The 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 E-Business Suite 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.

Customers who do not have an item master organization defined for their site require customization of NoetixViews, to avail themselves 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 XOP views for Oracle 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 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.

Guidelines for Using XOP Views

For each chart of accounts, a set of XOP views will be generated to cross over all ledgers/sets of books, 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/sets of books, 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/sets of books, each with a different primary currency, would be: “How many products were sold last year across all ledgers/sets of books?” For the same ledgers/sets of books, 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/sets of books?” In the result of this query, the amounts would not be converted to a single currency.

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

XOP Views and Multi-Currency

The multi-currency functionality of Oracle E-Business Suite is not supported by XOP views.

Irrespective of whether the multi-currency functionality is activated at your environment, insigihtsoftwarerecommends that you use a single primary currency across all ledgers/sets of books to ensure accurate information from the XOP views.

For example, if your environment has two ledgers/sets of books without the multi-currency functionality, both having the same primary currency and identical calendar periods, XOP views can retrieve information accurately from those ledgers/sets of books. Even if your environment has two ledgers/sets of books 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 MRC

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

For example, a company has two ledgers/sets of books for its operations in the United States and Mexico. The primary ledger/set of books, representing the entire company (both operations) uses U.S. dollars as its currency. The reporting ledger/set of books, 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/set of books. 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/set of books. The retrieved information, containing financial data in U.S. dollars, can be used to evaluate the company’s global performance.

XOP Views and Calendar Periods

The number of calendar periods you have created for each ledger/set of books 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/sets of books.

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

XOP Views for Inventory

Two 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 Pregeneration Considerations or Pregeneration Considerations 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 generated 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 Views

The global extension of NoetixViews allows users to view data across organizational units and build queries using the data. Depending on your Oracle E-Business Suite setup, the data can span organizational units, such as business groups, ledgers, operating units, and inventory organizations.

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/sets of books, 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 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 Forms of Noetix Views.

The access of the Noetix query users to global views is determined by the data access privileges granted to them through the Noetix Views 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.

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.

Global Views and Multi-Currency

For a global role, users can retrieve accurate data from the corresponding global views across ledgers/sets of books if the ledgers/sets of books use the same primary currency.

Important: For global views that retrieve information from ledgers/sets of books with different primary currencies, the users need to be careful while grouping or summarizing the values in different primary currencies.

Global Views and MRC

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

For example, a company has two ledgers/sets of books for its operations in the United States and Mexico. The primary ledger/set of books, representing the entire company (both operations) uses U.S. dollars as its currency. The reporting ledger/set of books, 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/set of books. 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/set of books. The retrieved information, containing financial data in U.S. dollars, can be used to evaluate the company's global performance.

How Global Views Are Generated

A single global role with a set of views is generated for all active organizational units defined in an Oracle
E-Business Suite module. Similar to standard and XOP views, Noetix query users can access global views through global roles. When a global role is assigned to a Noetix query user, the user can query data related to the organizational units from the views corresponding to the role subject to the access permissions defined for the user.

The global forms of Noetix views are available for all the supported Oracle E-Business Suite modules except the following:

• Oracle Grants Accounting

• Oracle Grants Proposal

• Oracle Project Manufacturing

• Oracle General Ledger (GL Parent Budget to Actuals, GL Parent Child Balances, GL Parent Child Budgets, GL Rollup Parent Balances, and GL Rollup Parent Budgets)

Some additional columns are generated in the global views based on the organizational units across which the views span.

Benefits of Global Views

The key features of the global form of Noetix views are the following:

• Ease of use:Generates the fewest number of views without compromising coverage of Oracle E-Business Suite, which in turn, decreases the number of reports that you need to maintain.

• Enterprise-wide reporting: Enables users to access data pertaining to multiple organizations through each global view.

• Row-level security: Restricts the data returned by the global views in the BI tools based on the data access privileges of the Oracle E-Business Suite users.

• Intuitive user interface: Provides an organized and intuitive presentation model in the BI tools for enhanced reporting experience.

• Rapid implementation: Facilitates rapid deployment of upgrades, enhancements, and customizations through reduced turnaround time for generations and regenerations.

• Organization refresh feature: Returns information about newly added organizations in Oracle E-Business Suite without the need to regenerate the views.

• Incremental regeneration feature: Regenerates views incrementally to process view customizations without the need for a complete regeneration of NoetixViews.

• Parent-child hierarchies: Supports parent-child hierarchies defined on Accounting Flexfield segments.

• Subledger Accounting: Supports high-value reporting on subjects, such as reconciliation activities among General Ledger and its source modules and the analysis of Subledger Accounting transactions for Release 12.

Key Flexfield Support in Noetix Views

This section explains how key flexfield-related information is displayed in the standard, Cross Operations Extension (XOP), and global forms of the views. Key flexfield segments are generated in Noetix views for the key flexfields that are configured in Oracle E-Business Suite and supported by NoetixViews.

The following key flexfields are supported by NoetixViews:

• Account Aliases

• Accounting Flexfield

• Asset Key Flexfield

• Bank Details KeyFlexField

• Category Flexfield

• Cost Allocation Flexfield

• Grade Flexfield

• Item Catalogs

• Item Categories

• Job Flexfield

• Location Flexfield

• People Group Flexfield

• Personal Analysis Flexfield

• Position Flexfield

• Stock Locators

• System Items

• Territory Flexfield

Key Flexfield Views

For 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 Flexfield, and the concatenated segment values. A data cache description table is also created for the Accounting 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 the extent of support provided for key flexfields in standard, Cross Operations Extension (XOP), and global views.

Key Flexfields Supported by NoetixViews

The following table lists the key flexfields that are supported by NoetixViews.

Columns in Key Flexfield Views

A 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 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 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 Views

When 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 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 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 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 Pregeneration Considerations 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.

Key Flexfield Support in Standard and XOP Views

Standard and XOP forms of views generate columns for the key flexfield segments depending on how the key flexfields are configured in Oracle E-Business Suite. Both forms of views will include segments corresponding to only a single key flexfield structure. Depending on the requirement and functionality, a standard or XOPform of the view may also include columns for the key flexfield segment descriptions along with key flexfield segments. For the standard and XOP form of the views, columns for each supported key flexfield are displayed in one of the following formats:

One column for each individual segment (Example: Acct$Account, Acct$Company, Acct$Department, and Acct$Product), and one column for the concatenated segment value
(Example: Acct$Progress Accounting Flexf).

One column for the concatenated segment value (Example: Budget$Operations Accounting F).

One column for each individual segment (Example: Acct$Appropriation, Acct$Department, and Acct$Fund), one column for each individual segment description (Example: Acct$$DESC$$Appropriation, Acct$$DESC$$Department, and Acct$$DESC$$Fund), one column for the concatenated segment value (Example: Acct$$Progress Accounting Flexf), and one for the concatenated segment description (Example: Acct$$DESCRIPTION$$).

One column for each individual parent segment (Example: Parent$Account, Parent$Company, Parent$Department, and Parent$Product), one column for each individual child segment (Example: Child$Account, Child$Company, Child$Department, and Child$Product), one column for each individual parent segment description (Example: Parent$$DESC$$Account, Parent$$DESC$$Company, Parent$$DESC$$Department, and Parent$$DESC$$Product), one column for each individual child segment description (Example: Child$$DESC$$Account, Child$$DESC$$Company, Child$$DESC$$Department, and Child$$DESC$$Product), one column for the parent concatenated segment value (Example: Parent$Operations Accounting F), one column for the child concatenated segment value (Example: Child$Operations Accounting Fl), one column for the concatenated parent segment description (Example: Parent$$DESCRIPTION$$), and one column for the concatenated child segment description (Example: Child$$DESCRIPTION$$).

Key Flexfield Support in Global Views

For 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.

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. Key flexfield views are available to users only if multiple key flexfield structures are used in the global views.

For the Accounting Flexfield, if the global views contain key flexfield columns that return concatenated descriptions of the segments or that return descriptions for the qualifier segments or both, a key flexfield view is created with the D suffix.

Columns in Key Flexfield Views

A 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 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 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 Views

When 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 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 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. In these global views, a join-to column is provided for the key flexfield view that returns descriptions.

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.