Moving from Test to Production Environments

About the Oracle BI Server XML API 12-15 The fully qualified name is the best identifier to use when searching an XML repository file to find a particular object, because the name of each object is visible in the Administration Tool. For example: qualifiedName=quot;Sample Salesquot;.quot;H0 Timequot;.quot;Monthquot; Note that qualified names for Presentation objects use .. between the subject area and the presentation table name. This syntax is used because there is no such thing as a presentation schema, which would normally go between a catalog and a table. For example: qualifiedName=quot;Sample Smallquot;..quot;Facts Revenuequot;.quot;Billed Qtyquot; A similar convention is used for Physical layer objects, when the database does not have a physical catalog or physical schema. ■ uid. This identifier, also called the UpgradeID, is a 32-bit number that is unique across the entire repository. The uid is created by the Oracle BI Server for the lifetime of the object. You can leave it blank when creating new objects in XML, because the server generates it automatically when it loads the RPD file. When you alter an object, make sure not to change the uid. The uid is used for compare and merge algorithms. It can also be useful for tracing relationships when analyzing or reverse-engineering XML metadata. For example: uid=73185 ■ id. This identifier, also called the VoidID, is created by the Oracle BI Server for the lifetime of the object. It is used in situations where the object type can be used to achieve better performance than the uid. Like the uid, you can leave the id blank when creating new objects in XML, because the server generates it automatically when it loads the RPD file. When you alter an object, make sure not to change the id. The id is a structure that contains two pieces of information: the type and a unique number within that type for example, 2000:123456. Each object type, such as a logical column, has a particular number associated with it for example, 2000. So, two objects of the same type both have the same number in the first part of the id. The unique number in the second part of the id is a randomly assigned number within that type. It must be unique within the type, but does not need to be unique across different object types. For example, a repository might have the valid ids 2000:123456 and 2001:123456. Although the id is typically created by the Oracle BI Server, you can create your own if needed, as long as you ensure that it is unique. For example: id=4010:1720

12.4.2 About Naming Requirements for Repository Objects

All repository object names must follow these requirements: ■ Names cannot be longer than 128 characters ■ Names cannot contain leading or trailing spaces ■ Names cannot contain single quotes, question marks, or asterisks Note that repository object names can include multibyte characters. 12-16 Oracle Fusion Middleware Integrators Guide for Oracle Business Intelligence Enterprise Edition 13 Logical Elements 13-1 13 Logical Elements Logical elements are typically those elements that are exposed in the Business Model and Mapping layer, or in other words, the elements that appear in the center pane of the Administration Tool. This chapter contains the following topics: ■ Section 13.1, Logical Column ■ Section 13.2, Business Model ■ Section 13.3, Logical Complex Join ■ Section 13.4, Logical Level ■ Section 13.5, Dimension ■ Section 13.6, Logical Table ■ Section 13.7, Logical Foreign Key ■ Section 13.8, Logical Key ■ Section 13.9, Logical Table Source ■ Section 13.10, Logical Source Folder ■ Section 13.11, Measure Definition ■ Section 13.12, Aggregation Rule ■ Section 13.13, Override Aggregation Rule ■ Section 13.14, Logical Display Folder

13.1 Logical Column

The logical column element corresponds to the logical column object in the Business Model and Mapping layer. The logical column tag includes the following attributes: Table 13–1 Logical Column Tag Attributes Attribute Name Description isDerived When set to true, indicates that the logical column is based on a user-defined expression for example, another logical column, a constant value, or a variable.