The business structure is reflected in Apliqo FPM using is represented through the Company dimension and up to four flexible business segments that can be used flexibly. The Company serves acts as the balancing entity and determines defines the currency of the Local currency. The business segments might be; local currency for financial transactions. Business segments can include Cost Centers, Profit Centers, Departments, Customers, Products, or Locations of the business. It will depend , depending on the specific requirements of the Apliqo FPM implementation.
Both the Company dimension and the Business Segment dimensions will define determine the level of detail that at which data is stored in the General Ledger cube. The FIN General Ledger cube is the main cube , which serves as the primary source for reporting and analysis.
To set up configure the Business Segment setup Segments, navigate to Administration > Business Segments.
...
General Considerations
Dimensions and Hierarchies
The leaf elements of a dimensions store the business data in the cube. This this dimension represent the smallest level of detail of the business data stored in a cube within Apliqo FPM. These elements provide the granular details essential for analysis and reporting.
...
The company Company and business segments dimensions will contain Business Segment dimensions typically include at least one hierarchical structure that rollups up aggregates the leaf elements to into a total consolidated element. The total consolidated element knowns total, known as the top node. The top node may contain encompass intermediary consolidated elements that are , representing sub-totals of the leaf elements that are the members of the intermediary consolidation. Within a hierarchy there can be multiple top nodes that rollup the leaf elements differently to express different sub-totals that are used for business grouped according to specific criteria. These hierarchical structures enable flexible reporting and analysis.
For example, if a business segment is used to represent the Cost Centers of the business. One rollup of the Cost Centers may be by locations. The top node of the rollup would be ‘Total Cost Centers by Location’. The sub-total consolidations would the different locations of the cost centres. Another rollup of the Cost Centers may be by General Manager. The top node might be ‘Total Cost Centres by General Managers’. The sub-totals would be the General Managers. Each General Manager consolidation would have the cost centers the General Manager is responsible for. Both top nodes the same leaf elements with different sub-total/consolidations of the leaf elements. The limitation of multiple rollups in a single hierarchy is that they represents Cost Centers, one hierarchy might aggregate them by location, with the top node labeled “Total Cost Centers by Location.” Sub-totals in this hierarchy would represent specific locations. Another hierarchy might group Cost Centers by General Manager, with the top node labeled “Total Cost Centers by General Managers,” and sub-totals representing the managers. In both cases, the same leaf elements (individual Cost Centers) are aggregated differently to meet distinct reporting needs.
However, multiple rollups within a single hierarchy cannot be combined for reporting and analysis, which limits flexibility in such configurations.Alternated
Alternative Hierarchies
To overcome this limitation, alternative hierarchies can be created in within the company Company and business segment dimensions that can be combined for reporting and analysis. Each alternative hierarchy contains one or more rollup of the leaf elements of the dimension as described above. Using the previous example two hierarchies would be created in the Cost Center business segment dimension, one hierarchy to contain Cost Centers by Location, the other to contain Cost Centers by General Manager.Rollups verses hierarchies. Rollups are relatively simple to implement and understand, making them suitable for straightforward for your reporting needs. Hierarchies provide greater design flexibility and provide new insights. Using our example above, having a Cost Center by Location and Cost Centers by Managers hierarchies mean that these two hierarchies can be cross-tabbed in the same report to see the performance of the Cost Centers by Location and General ManagerBusiness Segment dimensions. These hierarchies provide separate rollups of the same leaf elements. Using the example above, one hierarchy could group Cost Centers by Location, while another groups them by General Manager. With alternative hierarchies, these two perspectives can be cross-tabbed in reports, allowing users to analyze Cost Center performance by both Location and General Manager simultaneously.
Rollups vs. Hierarchies
Rollups are straightforward to implement and are well-suited for basic reporting requirements. In contrast, hierarchies offer enhanced flexibility and deeper analytical insights. For instance, with hierarchies for Cost Centers by Location and by General Managers, cross-referenced reports can reveal performance across both dimensions, providing a more comprehensive view of business operations.
Required Elements
All dimensions have the in Apliqo FPM include a default hierarchy that is shares the same name as the dimension. Every Each business segment dimension must have the contain:
A consolidated top node
...
named “Total FIN BSEG x”
...
A default leaf element
...
named “NA FIN BSEG x”, where x
...
represents the index of the business segment
...
dimension.
Similarly, the Company hierarchy requires a consolidated top node , named “Total FIN Company” and the a leaf element of named “NA FIN Company”Company. Many other ” Other dimensions /and hierarchies use often follow the same naming convention conventions for the top node of the dimension/hierarchy and the their top nodes and default leaf element. Do not delete these elements as they are important to the operation elements. These elements are critical for the proper functioning of Apliqo FPM and should not be deleted.
The “Total FIN BSEG x” and the “Total Accounts” consolidations are used to reconcile play a key role in reconciling the balancing entity. The “Total FIN BSEG x” rollup in the business segment hierarchy must include encompass all the leaf elements of the business segment. Other Conversely, other rollups and alternate alternative hierarchies do are not have required to include all the leaf elements . They will be defined by the business requirements. and can be customized to meet specific business needs.
The “Total FIN BSEG x” rollup is considered regarded as the correct definitive total that against which all other totals are compared to. The same validated. This principle also applies to the FIN Company and other dimensions in within Apliqo FPM.
Elements and Attributes
Elements and Attributes
The Once created, the principal name of the a leaf element cannot be changed once the leaf element has been created. For this reasonmodified. Therefore, it is recommended that to use system keys are used for the principal names of the leaf elements instead of business descriptions. These system keys may already often exist within the business organization’s source data. An To assign a business description to a leaf element, you can use an Alias Attribute or a String Attribute are used to give the leaf element a business description.
Deleting a leaf element can lead to a loss of data. When updating the hierarchy the elements of a hierarchy result in data loss. Instead of deleting elements when updating a hierarchy, the elements are unwound from the rollup instead of being deleted. The rollup , and the hierarchy is rebuilt from based on the hierarchy updated definition defined stored in Apliqo FPM. Any leaf elements that are not part of the new hierarchy definition become orphans in the hierarchy. These orphan leaf elements should be reviewed , after the hierarchy definition has been updated in Apliqo FPM or the leaf elements can be manually deleted from the hierarchy.Generally, consolidated elements can be deleted. Numeric update or manually deleted if no longer needed.
Consolidated elements, however, can generally be deleted since numeric data cannot be stored against a consolidated elementthem. String data, such as comments, can still be stored against consolidated elements.Elements can have Alias Attributes that can be used to give the element a business description. Aliases must also
Types of Attributes
Alias Attributes: Provide business descriptions for elements and must be unique within the hierarchy
...
. They cannot duplicate the principal name or other aliases.
...
Apliqo FPM’s default alias
...
, “Code and Description,” concatenates the element’s principal name
...
with its business description.
...
String Attributes: Store textual data, such as descriptions, which do not need to be unique.
Numeric Attributes: Store numerical data associated with an element.
All business segment dimensions have include a “Description” attribute, which is a string attribute that stores the business description of the for leaf element. String attributes do not have to be unique. elements. Attributes are managed in the business segment maintenance pages.through the Business Segment Maintenance pages in Apliqo FPM.