web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Ledger Allocation Rules
Microsoft Dynamics AX (Archived)

Ledger Allocation Rules

(0) ShareShare
ReportReport
Posted on by Sunil 755

I've set up a" Fixed Percentage" allocation rule to allocate some expenses from Dept # 11 [in AX 2012 R3].

The expenses are being allocated to subsidiary companies but to a different department (i.e. Dept # 01). 

However, when the transactions are generated, the destination entries show department # 11 (instead of Dept #01, as per my setup).

Any suggestion is greatly appreciated.

*This post is locked for comments

I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 305,182 Super User 2026 Season 1 on at

    Hi Sunil,

    Can you provide screenshots of your setup or tell how exactly is has been setup?

  • Sunil Profile Picture
    Sunil 755 on at

    The allocation is definition is as follows:

    8206.allocations.jpg

    The allocation that were generated are as follows:

    8206.allocations.jpg

  • Ludwig Reinhard Profile Picture
    Ludwig Reinhard Microsoft Employee on at

    Hello Sunil,

    Are you sure that the the correct rule no. ... 11 processed the Journal lines above? If so, have you already checked LCS for an available hotfix that might help fixing the issue? A number of hotfixes have been released for problems around ledger allocations especially for older AX versions. Maybe one of them helps?! What's your system version R3 CU...?

    Ludwig

  • Sunil Profile Picture
    Sunil 755 on at

    Hi Ludwig,

    I am running R3 - CU10.  I'll double check if there is anything in CU 11 to fix this.

    Thanks.

  • Ludwig Reinhard Profile Picture
    Ludwig Reinhard Microsoft Employee on at

    Good morning Sunil, I would suggest that you check for an available hotfix and probably try setting up the allocation rule once again from scratch - probably on a demo machine - to test whether everything is ok with the allocation rule Setup. If nothing helps and you still experience the Problem I would suggest that you get into contact with one of your system developers and/or the MS support team. Would be great if you could keep us updated here. Many thanks and all the best, Ludwig

  • Ludwig Reinhard Profile Picture
    Ludwig Reinhard Microsoft Employee on at

    Hello Sunil,

    Just wondering whether you have made some progress here and/or whether some help is still required?

    Best regards,

    Ludwig

  • Sunil Profile Picture
    Sunil 755 on at

    Hi Ludwig,

    I deleted the rule and setup it up again (in the same environment and in a different environment) - with the same result.  I've checked on hotfixes and there is none that address "Fixed percentage" allocation method.  So I've entered a ticket with MS.

    I'll update you when they get back to me.

    Thanks,

    Sunil

  • Suggested answer
    Sunil Profile Picture
    Sunil 755 on at

    Hello Ludwig,

    We reported this to Microsoft and they have now provided us with a Hotfix.

    Thanks for all your help.

    Sunil

  • Community Member Profile Picture
    Community Member on at

    Hi Sunil!

    Thank you for the feedback. Can you provide us with the KB or hotfix number?

    I'm in the preparation of a system where we will extensively use the ledger allocation feature of R3... I've already submitted 2 bug reports, one of them is turned out to be solved already in KB3126365, the other one is a minor bug still at Microsoft with low priority and it probably doesn't affect you beause it becomes only critical when you plan to extend the number of posting layers covered by ledger allocation (like we do now):

    Class LedgerAllocationProcessRequest.getLedgerAmounts() uses wrong enum to define the posting layer(s) to consider. It uses OperationsTax::Current instead of CurrentOperationsTax::Current.

    So some info on the problem and the solution would be more than welcome here!

    Thank you in advance,

    mrt

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
CP04-islander Profile Picture

CP04-islander 34

#2
Michel ROY Profile Picture

Michel ROY 14

#3
Jagadabi Profile Picture

Jagadabi 6

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans