20 Working with Properties
Dimensions include properties that are used by their nodes. The Properties page lists the properties that can be added to dimensions. Oracle Enterprise Data Management Cloud provides an initial set of properties. You can create custom properties from the properties page or when you register Universal applications.
The properties available to an application's dimensions depend upon the application type:
- When you register a Universal application, you can create custom properties or select existing properties.
- When you register an Oracle Fusion Cloud EPM application, properties are automatically added, based on the dimensions' Dimension Types.
You can customize how properties are displayed in viewpoints. For example, you can display an alternate name for a property, see Understanding How to Configure Properties for a Viewpoint.
An application's type determines some characteristics of properties, as described in the following table:
Table 20-1 Properties and Application Types
Application Type | Property Considerations |
---|---|
Oracle Fusion Cloud EPM applications | You cannot add or remove properties. The only properties available to nodes are the properties automatically added when the application was registered. For application-specific properties, see: |
Oracle Financials Cloud General Ledger Applications | You cannot add or remove properties. The only properties available to nodes are the properties automatically added when the application was registered. For application-specific properties, see Predefined Properties for Oracle Financials Cloud General Ledger Applications |
Oracle E-Business Suite General Ledger Applications | You cannot add or remove properties. The only properties available to nodes are the properties automatically added when the application was registered. For application-specific properties, see Predefined Properties for E-Business Suite General Ledger Applications |
Universal applications |
|
Users applications | You cannot add or remove properties. The only properties available to nodes are the properties that were automatically added when the application was created. See Predefined Properties for Users Applications. |
Note:
- Oracle Fusion Cloud EPM applications may have unique considerations. If so, those considerations are described in the topic for the application type.
- For all application types, you can add properties that are not registered with the application to a node type, thus making the property available in viewpoints. Unregistered properties added to node types are not included when you import or export an application's data.
Why would you add a property to a node type if it cannot be imported or exported? You can use such properties to customize sorting or to include descriptions and comments for Oracle Enterprise Data Management Cloud users.
Property Data Types
Properties are defined using the following data types:
Property Data Type | Definition | Examples |
---|---|---|
Boolean | A value that can be true or false | True
|
Date | A date value. Does not include a time value. | 03/05/2023 |
Float | A number that has a decimal place | 587.5 |
Integer | A whole number | 1000 |
List | A sequence of strings |
|
Memo | Large strings that allow formatting and whitespace characters, such as line feeds and Tab characters. | A Java regular expression, for example
|
Node
Note: Subtypes are available for node data types. See Node Data Type Subtypes. |
Basic subtype: A pointer to another node in either the same or a different node set. | A parent node, for example, Accounts -
Project |
User subtype: A pointer to a User or User Rollup node in any Users application | A cost center manager, for example Barry
Mills |
|
Numeric String | A string that allows numeric characters (0-9) only. | 12475381469113081838 |
Sequence | An automatically-generated incrementing number. | 0001005
|
String
Note: Subtypes are available for string data types. See String Subtypes. |
Basic subtype: Text and numeric characters. |
Owner's Equity |
Email subtype: Email address | user@companyname.com |
|
Hyperlink subtype: Hyperlink information | https://companyname.com |
|
Timestamp | A date and time value | 03/05/2023 11:30 AM |
Property Level
The property level determines where property values are defined:
- Node: Defined property values apply to that node across all locations and viewpoints.
- Relationship: Defined property values are unique to specific parent-child relationships within a hierarchy set.
Caution:
Property level applies to defined property values only. Inherited and derived values (if the default expression uses positional logic) may not conform to the node and relationship level constraints. See Inheriting Properties and Derived Properties.
Property Origin
The property origin identifies how a value originated for a node. Property values can have these origins:
-
Default: value can be configured when an application is registered
-
Defined: value is defined by the user
-
Inherited: value is inherited from an ancestor node
-
Derived: value is calculated. For example, number of children.
-
Derived and Stored: value was derived and then stored on the node.
-
Calculated (Name and Parent properties only): During a request, the value of the node name or parent was calculated. For node names, after the request has been completed the origin displays Defined.
-
Unknown: the origin of the value cannot be determined
For more information, see:
- Understanding Data Chains
- Configuring How a Viewpoint Displays Properties
- Understanding Property Names and Namespaces
- Adding, Removing, and Configuring a Node Type's Properties
- Removing a Property from a Node Type in a User Defined Dimension
- Inspecting Properties
- Inheriting Properties
- Derived Properties
Note:
For help with building expressions for deriving property values, see Using Expressions to Define Custom Business Logic.