×
Please select your Country
GLOBAL
    -~-~-~-
AMERICAS
    -~-~-~-
EUROPE
    -~-~-~-
    -~-~-~-
    -~-~-~-
ASIA PACIFIC
    -~-~-~-
MIDDLE EAST & AFRICA
    -~-~-~-

Imperial UK Implementation – Day 1

Tagetik for budgeting and planning

 

Started off the session with a recap of the deep dive. We moved on into a continuation of our discussions around dimensions. Most mortals won't be well equipped for this sort of a conversation, however we did have a good pool of resource through the Finance director and IT manager, in addition to having the ERP system leader present for more detailed queries. As it happened our nominal coding structure, which had been developed before the year 2000, had been well thought out and contained elements of dimensionality within it.

 

My normal approach the developing solutions, or working with them is to build a rough outline, try to test and break it and then make the real thing. In dimensional modelling this doesn't work particularly well as the dimensions and levels within create ‘homes’ for the data to go into. In other words if you don't create them at the outset you won't be able to build them in later, unless you go through a solution rebuild process which would necessitate a updating the extract/transform/load plus data entry forms. In short you need to get your dimensions set out correctly from the outset.

 

My advice to users of this and any similar tool is to get a very good understanding of the level of granularity of the source systems general ledger, get a strong understanding of the concepts around dimensions even to the point of organising working groups to define those aspects of your business that are most important to you. E.g. A property company may well be interested in a results at a property level, whereas a builders merchant would have an interest in product type, and an accountancy firm may be interested at a employee level. The chances are there is more than 1 dimension that is of interest in your business and in our case we selected franchise, product, department and customer, which sat within the 5 custom dimensions available within Tagetik.

 

Resolution of dimensions was a key outcome of the day and paved the way towards building the data model on day 2.

 

Read next post:

 Tagetik unified budgeting, planning and forecasting

Share this post!