Understanding Property Names and Namespaces

A property is identified by its name and namespace. For example, the Core.Node Type property has a namespace of Core and a name of Node Type.

Namespaces are useful because different external applications might use the same property name. They ensure that each property is uniquely identified while also preserving the property name. Namespaces are automatically assigned to properties when you register an application.

The following table describes the available namespaces.

Table 20-2 Namespaces

Namespace	Description
Core	Oracle Enterprise Data Management Cloud system properties. For example, the Core.Name property is used for node names. See System and Statistical Properties.
CoreStats	Oracle Enterprise Data Management Cloud statistical properties. For example, the CoreStats.# Children property calculates the number of child nodes for a given node. See System and Statistical Properties.
Custom	Properties for Universal applications.
EBSGL	Properties for Oracle E-Business Suite General Ledger applications. See Predefined Properties for E-Business Suite General Ledger Applications.
FCCS	Properties for Financial Consolidation and Close applications. See Predefined Properties for Financial Consolidation and Close Applications.
FCGL	Properties for Oracle Financials Cloud General Ledger applications. See Predefined Properties for Oracle Financials Cloud General Ledger Applications.
Lookup	Properties for Lookup class node types. See Predefined Properties for Lookup Node Types.
PLN	Properties for Planning applications. See Predefined Properties for Planning and FreeForm Applications.
User	Properties for User class node types. See Predefined Properties for Users Applications.

Properties with the Core and CoreStats namespaces are displayed on the Properties page regardless of whether you have registered an application. For properties with other namespaces, the Properties page will list only the properties used by registered applications. For example, if you have registered a Planning application but not a Universal application, the Properties page will list properties with the PLN namespace but will not list any properties with the Custom namespace.

For more information, see Working with Properties.

Example 20-1 Uniquely Identifying Two Properties with the Same Name

Oracle Enterprise Data Management Cloud includes a PLN.Account Type property. Suppose that you register a Universal application that has a property named Account Type. The Custom and PLN namespaces distinguish the two properties, as shown in the following examples: