Page Comparison

If you encounter a missing account in FIN OCoA dimension while loading data into the FIN General Ledger TB, don't reject the record. Instead, add the account to both the FIN CoA Map:FIN OCoA and FIN OCoA dimensions as part of the Total GL Accounts rollup. The account will be marked as unmapped in the UI, but the data will remain loaded in the FIN General Ledger TB cube.

• Please note: Since the account won't have the correct flags calculated after the data load, it's crucial to map it before proceeding with the roundtrip. Even OPV can't be calculated properly without mapping the account and applying the changes to the FIN OCoA dimension by syncing from template.

Follow below steps when implementing CoA:

• Set proper C3 account assignments, important settings are:Learn the account structure before loading into the system and consider which accounts should be assigned to mandatory C3 accounts. The accounts are:

  • TBD list

• Import structure from your data source into staging area

• Import rollups from the staging area so they integrate properly to FIN OCoA Rollups and Reporting Rollups that are always included in FIN OCoA dimension.

  • You may decide to load the individual rollups without specifying parent rollup should you need to automatically attach the elements to their parents - in this case always consider proper sequence of loading, so the elements are loaded after their parents are in place.

• Provide mandatory C3 accounts assignment so it is possible to proceed with flags calculation and Total GL Accounts and C3 Technical Accounts and KPI rollups management.

• At this point you may sync FIN OCoA from template dimension.

• You should now consider mapping from FIN OCoA to FIN PCoA.

  • Simple 1:1 mapping is possible to achieve by setting Mapping Level Override on C3_MGMTTB level to 0 (this might be set automatically should the value of Mapping Level Override be empty before running process }APQ.C3.Dim.CoAMap.PlanDimension.Update).