Hi Rendi R,
1) Issue
- When creating a Work Order in D365 SCM (Asset Management), the system automatically creates a Project ID and related sub-project/activity
- This results in multiple sub-projects being generated for each work order/job
- Requirement is to stop automatic creation of sub-projects, as managing a large number of sub-projects is not desired
2) Reason
- In D365 SCM Asset Management, integration with Project management and accounting is standard behavior
The system is designed so that:
- Each Work Order Job creates a unique project (sub-project/activity)
- This enables:
- Cost tracking
- Revenue/cost posting
- Financial control per asset/work order
- The logic is controlled by:
- Work order project setup in Asset Management
- Parent project configuration
- The automatic creation of sub-projects is core system design, not just a configurable optional feature
- Therefore, each work order/job is tightly linked to a project for accounting purposes
3) Resolution
- There is no standard parameter to completely disable automatic project/sub-project creation
- Possible workaround approaches:
Option 1 (Best practice – reduce project volume):
- Configure a shared parent project
- Ensure multiple work order jobs reuse the same project where possible (e.g., same asset → same project)
- Adjust project structure to reduce fragmentation
Option 2 (Configuration alignment):
- Review:
- Asset Management → Setup → Work order → Project setup
- Project management parameters
- Ensure project grouping logic minimizes unnecessary project creation
Option 3 (Process redesign):
- Evaluate if full Project integration is required
- If detailed cost tracking is not needed:
- Consider alternative costing approach (e.g., ledger-based tracking, depending on requirements)
Option 4 (Customization – only way to fully stop it):
- Modify or extend logic that creates project records during Work Order creation
- Suppress or override project creation logic in classes related to:
- Work order job creation
- Project linkage
- This requires careful design to avoid breaking:
- Cost posting
- Asset management financial integration
Important considerations:
- Disabling or bypassing project creation can impact:
- Cost control
- Financial postings
- Reporting
- Any customization must ensure financial integrity is preserved
For a more detailed answer, please provide more information.
Rg,
Alexander
*Due to the complex and different possibilities of deploying Dynamics 365 I highly recommend not to setup the application without some expert/partner or support. (For more information contact me under anassl@inno-solutions.info or visit www.inno-solutions.de)
*The Information comes directly from the manufacturer or provider and are validated (not guaranteed) up to date of creation of the posting.
References:
- Microsoft Licensing Guide
- Microsoft Doc`s/Learn