Change Requests

#495 - Fix attribute setting case when pOverrideAttrValue is set to 1 in import CoA processes

Symptoms

Attribute value is not set if current attribute value is empty and pOverrideAttrValue is set to 1.

Solution

Attribute value is set regardless of its current value If pOverrideAttrValue is set to 1 (forcing change of attribute value). If pOverrideAttrValue is set to 0 the attribute value will be set only in case it is currently empty, existing non-empty attribute value will be retained.

#552 - }APQ.C3.Dim.CoAMap.Update.Hierarchies.GL should include all leaf accounts excluding statistical accounts

Requirement

Rollup Total GL Accounts needs to be loaded with all accounts of the target dimension that are set up as leaf-level elements in }APQ C3 CoA Map cube except accounts that are descendants of C3_STATISTIC fixed account.

Solution

MDX query selecting leaf-level accounts originally selecting all descendants of C3_MGMTTB fixed accounts now queries all accounts from }APQ C3 CoA Map that are set up as leaf-level elements for the target dimension.

#542 - Improve handling of pVersion parameter in }APQ.C3.FIN.Cub.GeneralLedgerTB.Update.From.GeneralLedger

Requirement

When roundtrip is run with help of wrapper process }APQ.C3.FIN.Roundtrip.Main with Version parameter set to ACT value, steps using process }APQ.C3.FIN.Cub.GeneralLedgerTB.Update.From.GeneralLedger will fail with following error message: Error: Prolog procedure line (752): Dimension element "*ERR*" not found in dimension "FIN Version"

The error is caused by a recent change introduced in release 2020.11.1, fix #230 that changed the order of priority for roundtrip parameters are passed to individual processes. This change causes the ACT value to be passed as the value of the pVersion parameter to the process.

The process should be adjusted to be able to accept non-live versions as well, including cases when multiple values are passed to the pVersion parameter.

Solution

Handling of pVersion parameter values is changed to lookup all versions in the pVersion filter that have their live counterparts (_RULE suffix). In this case, non-live version tokens will be replaced with live version counterparts to make sure proper logic of the processing.

#553 - Add pOverrideElementType parameter to process }APQ.C3.Dim.CoAMap.Dimension.Sync

Requirement

Add parameter pOverrideElementType to the process }APQ.C3.Dim.CoAMap.Dimension.Sync to enable or disable change of element type for existing elements in physical dimension.

Solution

The process parameter pOverrideElementType was added to the process, the parameter accepts values 0 or 1 with the following function:

  • If pOverrideElementType is set to 0, the value of ElType promoted in }APQ C3 FIN CoA Map for the dimension will be ignored for all elements that already exist in the target physical dimension. This function doesn't apply to elements that exist in the template dimension only and are not present in the target physical dimension at the time the process is run.
  • If pOverrideElementType is set to 1, the value of ElType promoted in }APQ C3 FIN CoA Map will be applied to elements in target dimension. When the element already exists in the target dimension and has a different element type, it will be recreated with the type ElType as promoted from the mapping cube.

#549 - Fix }APQ.C3.Dim.CoAMap.SetFlags to adjust ElType if invalid and add dummy accounts only for descendants of C3_MGMTTB

Requirement

Element type ElType in the }APQ C3 FIN CoA Map cube should be adjusted by the process if it is invalid - either not set or set as an account on leaf level with children or as an account on a consolidated level without any children. Adding leaf-level dummy accounts should be enabled in the case when pAddDummyAccounts is set to 1 and the account is a descendant of C3_MGMTTB and is on a consolidated level without children.

Solution

Added ElType setting to C for all accounts that have no children and are not set as C in }APQ C3 FIN CoA Map, other cases when either ElType was not set to N or C, or when ElType was set to N and the account had child accounts were previously addressed. The code adding dummy accounts now tests an account to be a descendant of C3_MGMTTB.

#559 - C3_STATISTIC setting should not be mandatory for CoA

Requirement

Setting C3_STATISTIC should not be mandatory and enforced since the chart of accounts being built doesn't have to have any statistical accounts included.

Solution

The setting is now optional and not enforced by the process }APQ.C3.Dim.CoAMap.SetFlags. A warning is reported to messages and to the system error log In case the setting is missing. Process }APQ.C3.Dim.CoAMap.Update.Hierarchies.GL will adjust MDX to query statistical accounts being excluded from accounts that are added under the Total GL Accounts category if the setting is available and points to an existing account.

#555 - }APQ.C3.Dim.PlanDimension.Check should check only leaf elements descending from Total of BSEG or BSEG Plan dimensions

Requirement

The process }APQ.C3.Dim.PlanDimension.Check should check only leaf elements of FIN BSEG and FIN BSEG Plan dimensions that are descending from Total FIN BSEG or Total FIN BSEG Plan node.

Solution

MDX generating subset for the check now queries only leaf elements descending from either Total FIN BSEG or Total FIN BSEG Plan for FIN BSEG and FIN BSEG Plan.

#535 - Initial mapping setting to C3_MGMTTB should be entered to Mapping Level Override

Requirement

Currently the process }APQ.C3.Dim.CoAMap.SetFlags assumes initial value of mapping for C3_MGMTTB is preset by the user in Mapping Level column, however the Mapping Level column should be read only to check results of the mapping as this field will get updated by the process rendering all custom settings to be lost. Thus all user inputs should be entered into one measure, preferably to the Mapping Level Override field. Additionally setting up the Mapping Level Override field should be enabled for all direct descendants of Reporting Rollups.

Solution

All settings of mappings to plan dimension are expected to be input into Mapping Level Override field, this is valid for C3_MGMTTB as well as for direct descendants of Reporting Rollups.

Please Note: Default settings of Mapping Level Override are set to 0 in case no Mapping Level Override was set on C3_MGMTTB level only, other levels require the user to input Mapping Level Override manually if that particular levels are required to be mapped into planning dimension.

#560 - Fix process }APQ.C3.Dim.CoAMap.PlanDimension.Update

Requirement

Refactor the process }APQ.C3.Dim.CoAMap.PlanDimension.Update as follows:

  • NA FIN PCoA element should be a descendant of Total FIN PCoA
  • Don't create Total GL Accounts rollup in FIN PCoA
  • Make sure C3_MGMTTB is created only once as a descendant of Reporting Rollups
  • Allow other rollups as for example cash flow rollup to be included in plan dimension in case it descends from Reporting Rollups and has proper mapping to planning dimension

Solution

The process has been refactored to allow finding a parent with an existing mapping to planning dimension in a tree of all element's parents. The element must be descending from Reporting Rollups in operative dimension. Unnecessary checks for existence of settings of C3_TB, C3_MGMTTB and C3_REPORTINGROLLUPS that caused silent skip of processing were removed. Failed test for existence of plan dimension in FIN CoA ID will not cause an error, failing the processing, only warning will be output. Code generating FIN PCoA Rollups, Reporting Rollups and NA FIN PCoA was replaced by refactored code tracking the tree of element's parents that have mapping to FIN PCoA. Additionally process }APQ.C3.Dim.CoAMap.Update.Hierarchies.GL was refactored to make sure NA FIN OCoA should be descending from FIN OCoA Rollups.

Please Note: Changes related to NA FIN OCoA position are enabled only when FIN OCoA is regenerated in the CoA framework by deleting the existing rollup in FIN CoA Map, reimporting and running }APQ.C3.Dim.CoAMap.Update.Hierarchies.GL again.

0 Comments

Add your comment

E-Mail me when someone replies to this comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.