In the Presentation layer, subject areas enable you to show different views of a business model to different sets of users.
Populate subject areas using the contents from a single business model. Subject areas cannot span business models.
Subject areas are created automatically by dragging and dropping business models from the logical layer.
See Localizing Oracle Business Intelligence in System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
Aliases are created automatically whenever presentation objects are renamed, so that any queries using the original name do not break.
A subject area cannot have the same name as any of its child presentation tables. For example, you cannot have a subject area called Customer that has a Customer table within it.
These options are used typically for localization purposes. When you externalize strings in the Presentation layer and run the Externalize Strings utility, the results contain the session variable information and the translation key.
In most situations, this option should be selected. Many client tools differentiate between key and nonkey columns, and the option Export logical keys provides client tools access to the key column metadata. Any join conditions the client tool adds to the query, however, are ignored, because the Oracle BI Server uses the joins defined in the repository.
If you are using a tool that issues parameterized SQL queries, such as Microsoft Access, do not select the Export logical keys option. Not exporting logical keys stops the tool from issuing parameterized queries.