Dimension hierarchy

Import the xpo file for this project into version 3- SP3 system. The labels are hard-coded.

Functionality

Standard Axapta does not have any hierarchy on financial dimensions. One also cannot restrict some dimensions for a particular user group.

This project fills up this gap.

General ledger setup now has a new menu called Valid dimension combination.

A dimension combination must exist in this form before it can be used in any journal. Use create button to automatically create all the combinations.

Use user group button if you wish to limit the users that can post to a specific combination, if anyone can post to this combination then do not specify any user group.

Example: Say a company has Department - A, Cost center B, Purpose C1, C2, C3 and user groups finance and purchase.

If the above form is missing the combination A-B-C1 then once the user selects A as department and B as Cost center then only C2 and C3 are available in lookup and posting.

If you associate A-B-C2 with purchasing then finance will have option of A-B-C3 where as purchasing as option of A-B-C2 and A-B-C3.

Unfortunately finance user will be able to manually type in C2 (though C2 does not appear in the lookup). This behavior cannot be stopped without extensive modifications. However, user will get an error at posting time in this case.

Probably I have managed to confuse you with this explanation, why don't you just download the project and try it out? Create the above dimensions and see how it works.

I am hoping this will work for inter-company, please let me know if you have any problems.

If you find any bugs and can reproduce it in the demo system, please do let me know.

Send mail to harry@systomatics.com with questions or comments about this web site.

Disclaimer: I am working with Microsoft Business Solutions. The code on this site may or may not be related to my official duties with Microsoft. I do not claim in any expertise in modules represented on this website. Essentially there is just one person doing functional specifications (in head), design specifications (in head), coding and some testing. There is no way the project on this site will be free of bugs. The projects are intended as guidelines and may god help you if you decide to implement the projects without making any changes. If you implement any project resulting into data corruption or anything like that then do not even think of suing me because a. I have already warned you and b. I don't have any money. I may or may not respond to your emails about supporting the project. I may or may not upgrade the projects to the next service pack / version.