Associating existing project/program created in SPM with an order in OMT

[snehapatel]

I have found several references wherein you can create project oversight in SPM from the order in OMT. My requirement is other way round wherein a program/project is first created in SPM and then the order is created in OMT. Is there any way to capture the program/project reference during order creation so that it gets linked to existing program/reference  which has been already created. Also when the order decomposition takes place the project tasks should get created under the existing project/program based on the domain orders or order tasks followed by runtime synchronization of project tasks and order tasks.. Could you please guide on how this can be implemented.

Thanks,

Sneha

[Kenneth Phillip]

Hello Sneha - thank you for the use case, I am sure other users may face a similar one.

First, SPM integration with OMT has no awareness of the relationship between Program and project. Program is at the order level. The integration creates projects at the OLI level of the order hierarchy. OOB, you cannot accomplish your desire outcome.

Now, if you want to do what I believe you are asking at the project to OLI level, use an existing project, if a user wants to change the project id manually, use an existing project and its project tasks, it has to be done before decomposition. OOB, you cannot edit the project ID in the order line task relationship table after the OMT has decomposed the order. Reason being, OOB, OMT is auto creating the project first (requests SPM to instantiate the project from the targeted project template as inputted in the Project Management for Oversight OLI decision table) during order line decomposition.

OMT then automatically captures the project ID that SPM returns to OMT, and populates its Order Line Task Relationship table, once that occurs - one time synchronization between the project and the top order line item is completed. The key phrase here is "one time sync". If you attempt to simply try to re-direct the sync'ed relationship to another project instance after decomposition, by editing the project ID in the order line task relationship table, it will break the relationship already established, i.e..; lose sync.

To do what you want, this OOB auto create project for order line logic has to be customized so the user can add their project ID manually in the order line task relationship table.

I recommend the following - override the function: createProjectForOrderLine

 - in OOB file: sn_ind_tmt_orm.OrderLinePrjUtilOOB, to override createProjectForOrderLine and keep it empty in customizable file sn_ind_tmt_orm.OrderLinePrjUtil.

-  then manually input the project id in the relationship table - Order Line Task relationship (sn_ind_tmt_om_order_line_rel_task)  to map to the order line-item task id to the already created project, its ID. OMT should then attempt one time sync with the already user created project and sync the related project tasks for that project.  If we are using the same project template of course that aligns with the active project's project tasks to order tasks.

Try that, and please update me. Thanks, Ken

[Kenneth Phillip]

Hi again, putting on my product manager hat, bear in mind, you are overriding the OOB behavior as designed. I am just providing a suggested work around to the OOB implementation. It is the current constraint, it is supposed to automatically instantiate the project from the template, and automatically capture the project id returned, and yes, it's a constraint for your scenario as described - OOB auto creation of projects based on populating the project from the template that OMT requested to create a project from.  A simple way of going about this without changing OOB behavior would be to create your project, save as a template, then use the template to keep "as-is" implementation, assuming that you are at project kickoff time for the customer order delivery phase of the project. I would like though if you are of the mind to send to me directly your use case scenarios that describe your problem statements. It would be useful as a SN product manager to consider for "potential" future enhancements for the feature 😊