[Hannah Larkin]

Hi Everyone,

My company is going through subject matter expert (SME) training now for D365 and we’re currently reviewing the Projects module. I work for a CPG company and we are asset heavy. Our current process is we create a parent project that is specifically designed to be a place holder for the annual budget (no financial transactions occur here). Under the parent project is where we create related initiative projects (AKA sub-projects) that hold the financial transactions. One sub-project can (and typically does) create multiple assets. I’m wondering if anyone has had any luck creating a workaround for the one to one ratio of project to asset?  Just to present an example, a sub-project could be a package line. We then break out the package line into various assets for better visibility and ease in future disposals. We want to avoid having the package line as just one asset but that seems to be how D365 operates with the Project module via elimination.

Any guidance or advice would be much appreciated!

Thanks 🙂

——————————
Hannah Larkin
——————————

[Mark Bailey]

Hi Hannah,

The elimination routines that drive the asset posting are a 1:1 relationship as you say. This is due to the business logic used in D365, of course you can have multiple projects pointing to one asset but not one project for multiple assets.

The only way I can think of getting around this is by creating sub-project for each asset you want to split out. So in your example you would have a structure a little like this:

• Header Project
  • Sub-Project  – Package line
    • Sub-Sub-Project 1 – Asset 1
    • Sub-Sub-Project 2 – Asset 2
    • Sub-Sub-Project 3 – Asset  3

etc….

There is no limit to the amount of sub-projects you can have under a projects and everything will roll up to the package line/header projects. The payoff with this is having to administer all the projects you’ve created. User will have to know which project to book costs too etc..  When it comes to elimination D365 has the periodic elimination routines you can use to eliminate more than one project at a time.
Other wise you will be look at development on the elimination routine so that you can create some sort of fixed asset allocation which will not be easily done.

As always try to solve the issue using std functionality and business process before looking to a development.

Hope this helps

Mark

——————————
Mark Bailey
Application Consultant
Annata
Portsmouth
——————————
——————————————-

[Zvika Rimalt]

another work around is to eliminate into a “clearing” ledger account, and from that leader account to create multiple Acquisition Journals into The different fixed assets.

——————————
Zvika Rimalt
Functional Consultant
Vancouver BC
——————————
——————————————-

[Hannah Larkin]

Thank you both very much! I was wondering if your solution was possible when I asked the question Mark. I’m glad to hear it is.

Zvika, I had not considered a clearing account approach. That is very interesting. We currently use that approach for another GL account at month-end. I will bring that idea to management. Thanks for the help.

——————————
Hannah Larkin
Daisy Brand
Dallas TX
——————————
——————————————-