Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Najeem JanatAli]

What are the advantages of have parent and child project set up. If there is only one  project do we still still  require to set up parent project
 I only  noticed that when you extract a list of project at top level it have parent project as well as projects which dont have parent. All in one list 

Any suggestion / advise

Thanks and regards

——————————
Nazim Lalji

——————————

[Mark Prouty]

We use sub-projects for grouping different kinds of expenses, different product groups, different shipment locations or shipment dates, project management, warranty, trailing costs, field service, change orders, different sub-contracts. We don’t typically have transactions against the top level project- but use it as a summary of sub-projects. Top level is used for total project Gantt chart & activity milestones.

——————————
Mark Prouty
Programmer / Analyst
ANGI Energy Systems
Janesville WI
——————————
——————————————-

[Chan Stevens]

My normal recommendation is to stick with single/parent project approach until you find a need to expand to parent+child approach. You’d typically only need to set up child projects if something is significantly different than the parent or needs to be managed separately from the parent. Some examples:

• Multiple project types such as fixed price and time/material
• User/security differences such as personnel only authorized to work on portions of the overall project
• Financial posting profile differences (revenue recognition, etc.)
• Multiple rates in effect for the same resource/category

——————————
Chan Stevens
Industry consultant
Cincom Systems
Cincinnati OH
——————————
——————————————-

[Koen Cuypers]

Dear Nazim Lalji,

It is not required to create child (sub) projects in the PMA module. This functionality is mainly used when organizations have large projects. This allows them to apply different rules to the sub project and enables you to (financially) close the subproject while the main project is still active. 
I hope this will help you to make a proper decision on deciding to use only parent projects or also use child projects.

Please do not hesitate to request more information when needed.

Kind regards,

——————————
Koen Cuypers
Industry Specialist @ AXtension

——————————
——————————————-

[Zvika Rimalt]

Another scenario that may call for the use of sub-projects is when just part(s) of your project’s cost needs to be capitalized into a fixed asset through elimination.

——————————
Zvika Rimalt
Functional Solution Architect
Vancouver BC Canada
——————————
——————————————-

[Girish V. Nair]

Hi Nazim, 

 Various types of components for cost treatment, consumption, effort tracking, billing and revenue recognition can be part of a single contract. These have to be considered as different projects under the same contract or as different sub-projects within the same header for better tracking and reporting.

 When such multiple components (Hours, Expenses, Fees, Items, Milestones) of delivery are part of a project, these are generally handled by different delivery / project managers though it is part of same contract. In Such cases the planning for each deliverable could be separate (through separate sub projects), while the budget could be at the consolidated level (through Header project) and the cost tracking and reporting needs to be at each sub-project as well as header project level.

 In such cases it is preferable to have the Project Hierarchy relationship.

Thus a single project contract can have various components such as Fixed billing values where revenue recognition needs to be based on % completion, Time and material components where the billing and revenue needs to be treated differently.

 Have attached high level picture that should co-relate with my explanations above.

 

——————————
Girish V
Senior Advisory Consultant
Tectura India

——————————
——————————————-