GL Advanced Rules & Advanced Rule Structures

(0) Share

Report

Posted on by howalker

1,212

I need an unusual combination of posting rules for income statement accounts. My client wants 365 to allow posting based on one the following financial dimension rules:

Cost center must be blank if store is populated. Then the required dimensions are main account, store, business stream (a custom fin dim).
Store must be blank if cost center is populated. Then the required dimensions are account, cost center, business stream.
Cost center and store must be blank if business stream 30 is populated. Then the required dimensions are account, business stream.

I have not found a way to do this that works. I have tried:

Creating three advanced rules which have the logic in the rule itself and not an advanced rule structure. I did not attach any advanced rule structure here.
(1A) This did not work since 365 combined all the logic in the rules and allowed me to post to all fin dims at the same time, which is forbidden according to the requirements.
(1B) This also does not work because allowing blanks is not supported in the rule itself.
Creating an advanced rule that is blank and then attaching a single advanced rule structure which contain the three combinations of the rules above.
(2A) 365 does not allow creating an advanced rule structure in this way since it sees the other financial dimensions with an * and complains that they are overlapping.
Creating three advanced rules that are blank and then attaching a single advanced rule structure to each rule.
(3A) I tried in multiple combinations setting store and/or cost center to allow blanks, value = 0 and/or value < 1 in an attempt to create my own disallow feature since 365 itself does not natively support disallowing a fin dim in this setting. In this situation 365 accepts my entry but then throws a cryptic hard error when creating a journal.
(3B) 365 combines all these structures in to a single set of logic which then disallows posting to either store or cost center. The values are not available in the drop down.

Any advice would be appreciated.

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (0)

Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hi,

I have not tested the following configuration but would imagine that it works for the scenario you describe. Would be great if you could test the following setup:

Please let me know If it does not work. I will do some testing on my demo machine then.

Best regards,

Ludwig

Was this reply helpful? Yes No
howalker 1,212 on at

Like (0)

Report

Thank you. I configured three advanced rules, each blank, and each has a single advanced rule structure attached. One is for no cost center, one is for no store, and one is for no cost center and no store. I am getting the same error as I got before when creating a journal line. I typed in the account number 602000 (which 365 accepts), and then when I click in to the next fin dim segment Store, I get this error: "Unable to return DimensionAttributeValue record for 400000." 365 then blanks out my line and I then get "Blank is not allowed for Store for the combination."

Was this reply helpful? Yes No
Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hello Howard,

Do you really need the advanced rules?

I once used a similar setup as illustrated in the screenshot and managed that without advanced rules.

Probably try the setup without the advanced rule structure.

If it still does not work, I'll test it tomorrow on a demo machine in detail.

Best regards,

Ludwig

Was this reply helpful? Yes No
Suggested answer

ZvikaR 168 on at

Like (1)

Report

We had exactly (or at least super similar) requirement in our own retail implementation.

We resolved it without advanced rules

The thing that I believe would not work with Dr. Reinhard suggestion is that one need to make CC empty AFTER a store was selected, and the dimension logic does not work "backwards".

The "compromise" we created was creating a "fake" dimension values for stores dimension called "corporate"

To apply our solution approach in your case will be:

order of dimensions: Steam, Cost Centre, Store

dimension values: to the cost center list add value "STORES" that will indicate this is a "Stores" situation.

Dimension structures:

Note that in our case we found it easier to put dimension Store before Cost Center (and created a special "store" dimension for "Corporate") as posting for a store is much more common, and it was easier to set up the retail module to just populate Store ID.

Was this reply helpful? Yes No
Khaled Alloud 3,658 on at

Like (0)

Report

Dear Howard,

Hope i am not missing any information mentioned in the post, my question is what is the Account structure that you are initially using?

I mean it is important that you setup the structure you need, in the appropriate sequence of dimensions before setting up the rules.

Thank you,

Was this reply helpful? Yes No
ZvikaR 168 on at

Like (1)

Report

Hi Howard, did any of the suggestions resolved your issue? did you resolve it in another way?

For the benefit of the community reading this it would help if you updated the status of the issue.

Was this reply helpful? Yes No
Suggested answer

howalker 1,212 on at

Like (0)

Report

Nothing worked. I gave up. The client wound up creating 9999 dummy values in both store and cost center so when a valid store code is used, then 9999 cost center must be used, and vice versa.

Was this reply helpful? Yes No
Suggested answer

ZvikaR 168 on at

Like (0)

Report

Yes, in the method I described above we also ended up creating a dummy value

The difference that we only needed to create ONE dummy value for the first dimension, and we blanked the second dimension through the set up of the rules. That way user cannot select dummy values for both dimensions.

Was this reply helpful? Yes No