Scribd
Upload
63 views1 page

Version, Hierarchy and Relationship Hierarchy: New Import: Source:-Client File, Server File, Database

The document discusses the different sections of an import file in Adaptive Planning including Version, Hierarchy, Node, Relationship, and Hierarchy Node. It explains that imports create new versions to import data and validate it before saving to the database. The Relationship section is highlighted as the one that will be used to create nodes in the correct structure and populate all properties in a single pass for the example import.

Uploaded by

nara4all
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
63 views1 page

Version, Hierarchy and Relationship Hierarchy: New Import: Source:-Client File, Server File, Database

The document discusses the different sections of an import file in Adaptive Planning including Version, Hierarchy, Node, Relationship, and Hierarchy Node. It explains that imports create new versions to import data and validate it before saving to the database. The Relationship section is highlighted as the one that will be used to create nodes in the correct structure and populate all properties in a single pass for the example import.

Uploaded by

nara4all
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Import :-

Imports are always performed on new, empty versions created as part of the import process.
This approach allows you to verify that data was imported correctly and resolve any issues
before saving the data to the database or merging with data in other versions. After you verify the
data, you can use the blender to combine imported data with data originating from other sources.

An Import can have up to 5 sections, though not all are required. In our example, we are going to
be using a Version, Hierarchy and Relationship section. Heres a brief description of each.

Version This section can be used to populate Version-level properties for the version
being created by your Import. Only the Version Name property is required.
Hierarchy This section creates the hierarchies (and populates Hierarchy-level
properties) that will exist in your new version. The Hierarchy Name & Top Node
properties are required. In Essbase-speak, the Top Node is similar to the dimension root
in an outline, it is the first parent from which all limbs and leaves will be created.
Node This section creates nodes in a new version, and can populate Global-level node
properties only. The only required property is Node Name.
Relationship This section creates nodes and structures your hierarchy (based on
Parent-Child relationships). Both global and local-level node properties can be populated.
Well be using this section to create our nodes in the correct structure and populate all
properties in a single pass. There are 2 required properties, Parent Node Name & Node
Name.
Hierarchy Node This section can assign local-level node property values specific to a
hierarchy. For that reason, if using this section, you must also have a Hierarchy section
in your file. The required properties are Hierarchy Name & Node Name.

New Import :

Source :- Client file,

Server File,

Database

You might also like