B Glossary
application
An Oracle Enterprise Data Management Cloud application is a related set of dimensions, segments, or value sets used to meet a specific set of operational, analytical, or reporting requirements.
application adapter
An application adapter encompasses the registration, bindings, validations, imports, and exports for a specific application type within Oracle Enterprise Data Management Cloud.
application type
An application type is a category that defines the product represented by the external application. For example, Planning and Universal are examples of an application type.
approval group
An approval group consists of the users or groups assigned to a policy as approvers. The user configuring the policy determines whether the users and groups can approve the request simultaneously or if they must approve in a specific order.
approval method
An approval method determines if approvals are serial or parallel. If serial, one approver at a time approves in a specified order. If parallel, all approvers can approve in any order and at the same time.
approval policy
An approval policy consists of the settings and groups configured to approve changes to an application, dimension, hierarchy set, or node type. A user with the Owner permission to the policy level (application, dimension, hierarchy set, or node type) can configure approval policies.
assignee
An assignee is the user who currently has the request assigned to them. Only one user can be assigned at a time.
binding
Bindings are created between dimensions and viewpoints in an Oracle Enterprise Data Management Cloud application to ensure that the bound data objects conform to an external application's requirements.
binding keys
Binding keys are created during application registration to control the binding rules and the import and export constraints on a binding for a dimension.
binding type
Specifies whether a binding is a node-type or a hierarchy-type binding. Node-type bindings represent viewpoints with a flat list of nodes that use list node sets. Hierarchy-type bindings represent viewpoints with a structured set of nodes that use hierarchy node sets.
bound data object
A bound data object is an object that is used by the external application. Changes made to a bound object directly impact the external application when the dimension is exported. When you import to an existing dimension, data in the dimension's bound data chain is affected.
commit policy
Commit policies provide a final review stage for a request during which all request items are reviewed and committed by a user specified in the commit policy in order to enforce a segregation of duties.
connection (application-specific)
Enable you to share data from one specific application in Oracle Enterprise Data Management Cloud to one specific external application. Application-specific connections cannot be reused in other applications.
connection (global)
Global connections enable you to share data with external applications using extracts. You can use a global connection in multiple extracts, but each extract can use only one global connection.
constraint
Constraints enable you to enforce specific data rules (such as name uniqueness) across node types and dimensions in an application.
contributor
A contributor is a user or group who has submitted, reassigned, approved, or added an attachment or comment to a request.
data
Data is a generic term used to refer to objects or information when it is not necessary to denote specific details. For example, when you import an application, data is imported.
data access
Data access determines the actions that a user with Participant permission can perform and the properties that they can see and update.
data chain
A data chain consists of the objects used to populate a dimension. The data chain may include one or more node types, one hierarchy set (if working with related nodes), one node set, and one viewpoint.
data manager (role)
As a Data Manager, you are a data steward or analyst. You load data and manage data quality. For example, you can import dimensions, perform comparisons, run validations, and resolve data issues.
default view
The default view is created during registration and is associated with an external application.
dimension
A dimension organizes business information. A dimension usually contains hierarchies of related nodes and can contain nodes from different node types. For example, an application with a Year dimension often includes nodes for each time period, such as quarters and months.
Note:
In some financial applications a dimension may be called a value set, chart of account, or chart of account segment.dimension type
Dimension types are specific to the application type and define the dimension characteristics based on the external application type. For example, for Financial Consolidation and Close applications the dimension types are Account, Entity, Movement and Custom. The dimension type controls properties, validations, and other characteristics such as binding type (hierarchy or node type).
enterprise data
Enterprise data is organized and managed in Oracle Enterprise Data Management Cloud. It may include master data, domains, dimensions, hierarchies, reference data, application settings, metrics, measures, business classifications, and business taxonomies.
export
Exports are application-type specific mechanisms that move data from Oracle Enterprise Data Management Cloud to an external target system. Exports are controlled through the application registration, bindings, and binding keys.
export mapping
Exports data for one or more mapping keys.
expression
An expression consists of one or more lines of logic, called statements, that can be used to define custom business logic.
expression term
An expression term contains objects and operators that get evaluated to a value.
external application
An external application is an application such as Planning, residing entirely outside of Oracle Enterprise Data Management Cloud.
extract
Extracts enable you to retrieve data from a viewpoint within a dimension into a formatted file or a global connection. Extracts are configurable by users and can use bound and unbound data.
hierarchy
A hierarchy defines relationships between nodes. The hierarchy structure establishes familial relationships between nodes such as parent, child, sibling, descendant, and ancestor.
hierarchy set
A hierarchy set is a group of related nodes with a hierarchical structure which can have one or more top nodes.
implicitly shared nodes
When a node that has descendants occurs in more than one position in a hierarchy, after the initial occurrence of the node all of the other occurrences of that node in the hierarchy are considered implicitly shared nodes.
import
Import is a process in which the administrator imports data from an external application to populate a dimension's nodes, properties, and hierarchy relationships.
inheritance
Provides a way to define a default value for a property based on the position of a node within a hierarchy structure by retrieving the value from its closest ancestor that has a defined value.
invitee
An invitee is a user or group who is currently invited to approve a request.
list
A list is a group of nodes without a hierarchical structure. Lists can contain nodes of one or more types. For example, lists may be used to represent account segment value sets within a general ledger, a list of contacts, or accounts within a front office application.
literals
Literals are constant values that you manually enter in an expression.
location
The location is the full position of a node in a hierarchy. When a node is in multiple places in a hierarchy then each one will have a unique location. The location is the node combined with the full ancestor chain.
lock on commit
A property parameter that specifies that the property can only be updated on a newly added node. If this is enabled, after the request to add a node has been committed the value for the property is locked and can no longer be updated.
lookup set
Lookup sets are sets of key-value pairs that enable you to transform a set of values for properties into a different set of values.
mapping binding
A map binding allows node types to be mapped from dimensions in different source applications to a dimension in a target application.
mapping keys
Specifies the source node types mapped to target node types and defines a location name to export the mapping data.
master data
Master data is a single source of common business data used across multiple applications.
node
A node is an instance of a real-world business entity. Nodes can be used to represent an account, a cost center, a legal entity, a product, and so on. Nodes can be displayed in lists or hierarchies.
node set
A node set is a group of nodes for a particular business purpose. A node set uses a hierarchy set to manage a hierarchy of nodes or node types to manage list of nodes.
node set type
Determines whether a node set is a list-type or hierarchy-type node set. List-type node sets reference one or more node types. Hierarchy-type node sets reference a hierarchy set, which defines the node set's node types.
node type
A node type classifies and manages nodes based on common business characteristics. Node types are associated with dimensions; each node is assigned to a node type. Nodes are identified by a unique name and a description. For example, node name "1000", node description "Cash Account".
node type converter
Node type converters enable you to compare, locate, align, and drag and drop nodes of different node types across two different viewpoints.
notify policy
Notification policies enable application or dimension owners to notify specific users of completed requests submitted by other users.
object
An object is an element in an expression that represents a value.
operator
Operators perform logical comparisons in expressions.
owner (role)
As an owner, you are responsible for a business application or a subject area in your organization and you manage several functional areas in Oracle Enterprise Data Management Cloud.
permissions
Permissions secure access to applications, dimensions, data chain objects, and data. There are three permission levels: Owner, Data Manager, and Participant. For the Participant permission, you can also assign data access. See data access.
policy level
The policy level is the data object where an approval policy is set. Approval policies can be set at these levels: application, dimension, hierarchy set, and node type.
positional logic
Logic that describes the hierarchical position of a node, such as ancestor, parent, child, or bottom.
property
A property is a characteristic of an object. Nodes have identifying properties such as name and description. Nodes in hierarchies can have node and relationship properties. Node properties describe characteristics regarding the node itself, while relationship properties describe attributes of relationship in context.
property data type
The data storage format for the value of a property (for example, Boolean, date, string, or timestamp).
property default
Properties can be set up to have no default, a specified default or a derived default. This is managed in the property inspector and is setup during application registration based on the application type, dimension type, and property.
property level
Determines where property values are defined. For node-level properties, the defined property values apply to that node across all locations and viewpoints. For relationship-level properties, the defined property values are unique to specific parent-child relationships within a hierarchy set.
property parameters
Base property parameters are the initial configuration of a property from the application registration process. You can change the value of a base parameter for a specific application or node type by adding an override for that parameter at the application or node type level.
rationalization
Rationalization ensures data is represented consistently across multiple applications.
reference data
Reference data are permissible values that are often re-used, such as postal codes and state abbreviations.
registration
Registration is a process in which the administrator specifies the dimensions and properties to use from an external application to create an Oracle Enterprise Data Management Cloud application, default view, and data chain. Application registration also configures any other settings required by the application type. For example, Oracle Planning and Budgeting Cloud application registrations specify the plan types used by the application.
relationship
A connection between two nodes in Oracle Enterprise Data Management Cloud used for the parent-child organization of nodes in a hierarchy set.
request
A request is the mechanism to update data. Changes to data are organized into request items.
request item
A request item is a group of change actions for a specific node. A request item can contain one or more change actions.
request item action
Operations (such as add, insert, update, move, remove, or delete) that are performed on an item in a request. You can create a filter on a subscription or a policy for a request item action so that, for example, only specific actions generate a subscription request.
request stage
The request stage refers to the position of a request in the approval workflow. A request can be in one of these stages: Submit, Approve, or Closed.
request status
The request status is the status for the request: Draft, In Flight, Pushed Back, Recalled, Completed, or Rejected.
service administrator (role)
As a Service Administrator, you are a technical leader. You create and administer Enterprise Data Management service components. For example, you can manage user security, create and migrate applications, and set up maintenance and backups.
shared nodes
Nodes that exist under different positions within a hierarchy set or viewpoint.
statement
A statement in an expression is a discrete piece of information that controls the logic of an expression. There are three types of statements: If statements, Return statements, and Comments.
subscription
Subscriptions enable you to share data between viewpoints by subscribing a target viewpoint to a source viewpoint. When an update is made to the source viewpoint, a request is automatically generated to make the same change in the target viewpoint.
submitter
The submitter is the user who submitted a request. There is one submitter for a request. This user needs at least Submitter permission on all objects in the request.
template
Templates enable you to store application configurations in an offline file for use in other Oracle Enterprise Data Management Cloud environments.
unbound data object
An unbound data object is an object that is not used by the external application but instead can be used to model and evaluate potential changes to dimensions. Unbound objects are not updated by the import process. They may be indirectly affected by changes to other objects in their data chain.
user (role)
As a User, you are a business user or auditor. You view or modify data and may approve requests or audit changes made by other users. For example, you can browse data through views or submit and approve changes using requests.
validation
Validations preserve data integrity and enforce business logic in Oracle Enterprise Data Management Cloud.
validation level
The validation level is the data object to which a validation is applied in a custom validation. The validation level can be at the node type or hierarchy set.
view
Views give you a collection of lists and/or hierarchies for a particular context or activity, such as entity maintenance. Views consist of one or more viewpoints where you can update data. The default view is created when you register an application. A maintenance view is created for specific business needs.
viewpoint
Viewpoints provide a subset of nodes for you to work with. For example, viewpoints may represent different cost centers which require maintenance across applications such as financial applications and planning applications.
viewpoint type
Determines whether a viewpoint is a list-type or hierarchy-type viewpoint. The viewpoint type is determined by the node set that the viewpoint references.