ADempiere
ADempiere.netCommunity ChatWiki
develop
develop
  • ADempiere Documentation
  • About this Documentation
    • Copyright
    • Conventions Used
    • Contributors
    • Version Control
    • Getting Involved in the ADempiere Project
    • GNU Free Documentation License
  • Glossary
  • User Guide
    • Getting Started
      • About the Application
      • Launching the Application
      • Logging In
      • Finding Your Way Around the Java Client
        • The Application Menu
        • The Performance Dashboard
        • The Menu (Home) Tab
      • Finding Your Way Around the Web App
        • The Dashboard
      • Opening and Using Windows
        • The Tool Bar
        • Shortcut Keys
      • Entering Data - Fields and Buttons
        • Account Field
        • Assignment Field
        • Binary Data Field
        • Button Field
        • Color Field
        • Date Field
        • Date + Time Field
        • Untitled
        • Number Field
      • Dialogs and Forms
        • Account Dialog
        • Change Log or Record Info
        • Calculator Tool
        • Calendar Tool
        • Payment Dialog
      • Key Concepts
      • Workflow Activities
      • Workflow
      • Windows and Tabs
      • Reports and Processes
    • Garden World Demonstration Client
    • Untitled
    • System Administration
      • General Rules
        • System Rules
        • Security
          • Defining Users and Contacts
          • Roles and Managing Data Access
            • Dashboard Access
            • Role Access Update
        • Server
          • EMail Configuration
      • Managing the Client
        • Configuring the Client Password Reset
      • Managing Organizations
        • Document Status Indicators
      • Data
        • Data Import
    • Partner Relations
    • Revenue Recognition
    • Open Items
      • Dunning
    • Products & Material Management
      • Product Setup
        • Warehouse & Locators
        • Units of Measure
        • Asset Groups
        • Product Categories
        • Product Classifications, Classes and Groups
        • Product Attributes, Sets and Instances
          • Example - Using Product Attributes
        • Defining the Product
          • Product Types
          • Basic Product Setup
          • Product Bill of Materials
            • BOM Components
      • BOM Drop
    • Accounting & Performance Analysis
      • An Overview of Accounting in ADempiere
      • Accounting Setup
      • Calendar, Year and Periods
      • Tax Setup
      • Performance Measurement Setup
    • Assets and Asset Management
    • Manufacturing
      • Engineering Change Management
      • Product Configuration
      • Forecasting
    • Warehouse Management System
  • System Administration
    • Installation
      • System Requirements
      • Install ADempiere easily with Docker
      • Installing ADempiere Manually
        • Database Server Installation & Setup
        • Application Server Installation and Setup
        • Initialize the Database
        • Launch the Application Server
      • Securing Your ADempiere Installation
    • Upgrading and Migration
    • Database Maintenance
      • Database Backup and Restore
    • The Application Dictionary
      • Synchronize Changes with the Database
  • Developer Guide
    • Becoming a Developer
    • Software Development Procedure
    • ADempiere Version Control
    • ADempiere Best Practices
    • Development Environments
      • Creating WebUI Workspace using Eclipse Webtool
      • Customization Environment
Powered by GitBook
On this page
  1. User Guide
  2. System Administration
  3. General Rules

System Rules

PreviousGeneral RulesNextSecurity

Last updated 6 years ago

Trees and Tree Maintenance

Trees are collections and organizations of data using a summary and child structure. They are primarily used in financial reporting to summarize information in useful ways.

Each Accounting Dimension, such as Product, can have multiple trees and which tree gets used in a report is defined in a Reporting Hierarchy. Financial Reports are defined in lines and columns that can use the summary level elements of the tree. For example, in the Garden World Balance Sheet, there is a Reporting Line for Cash and the Account Element Value is set to 11 - Cash. This is a summary level account and the line value on the report would include all activity in all the subordinate accounts shown in the tree below.

Each Accounting Dimension requires at least one tree and the default trees are used if no Reporting Hierarchy is selected.

Where it is important to have multiple trees, a Reporting Hierarchy can be created to define the collection of trees to use in a given report. You can use the trees and reporting hierarchy to change the meaning of the summary product or to use different summary products.

For example, in Garden World, suppose it is important to report only on the sale of plants. A summary level product "Plants" could be created and the Product tree modified to group the various "plant" Products under the Summary Level Product. Then a financial Report Line Set or Report Column Set could be created that referenced this summary product and the "Plant Results" financial report would only shows results for the "plant" products. If it was important to show only "tree" plants, you could create a new product tree and hierarchy where the Plants summary level product only had "tree" type products as children. More realistically, you may need to use different categorizations altogether rather than subsets, such as New versus Legacy products in one tree and Plants, Tools, Furniture, Misc in another.