Like Customer , Vendor table that can be shared or used under table collection, need to have the Asset table (EAM) to be shared across LE.
Comments
Johan,
If there is another idea with a better description, please let me know and i will gladly move this comment to that mission.
I do not know that the shared tables approach is the solution here because i am not a developer. HOWEVER, the need to make assets more mobile along with diverted paths for the maintenance and repairs of assets between different LE's is paramount.
MANY firms seek to divest the operating "branches" LE's so that only one LE has the liability and other insurance burdens. BUT, the assets re lent on a long term basis (or short term) between the owning LE and the operating branches.
So, the FA is in the owning entity, but the asset may be rented to the borrowing LE for long or short term at a rate that is "at cost" or with a transfer price to the owning LE.
While it is possible to contrive asset creation in each LE to support lending and WO on the asset in both owning and borrowing LE's, this is a cumbersome design, and should be supported for modern industry inside the asset definition of D365F&SCM.
Thanks for your consideration.
Category: Asset Management
Administrator
Thank you for your feedback. This is a great suggestion!
Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.
Sincerely,
Johan Hoffmann
PM, Microsoft