Currently when deploying tasks from a project to a service order, the service order number is the same for each - only the line number updates. Is there a way / setting that will have the application create a new different service order number for each task deployed on a project? Not just increment the line number?
Solved
Alliance PSA Module
Best answer by Joshua Liem
Hi Melissa,
From Miscellaneous I, enable the Use Unique Request ID option.
+24Hi Melissa,
Just out of curiosity, why would you want to do this? This would mean you could not easily see these service order tasks were related to that specific project?
As you know, if you create two projects, the project numbers themselves are only differentiated by the project ID incremented by one. Normally service orders also increment by one with each new one via the service order module.
Seems to me you would have to also modify the formula used to determine the project’s service order serial number to use a sequence that is not the normal nnnn at the end of the Request ID which is the project ID
Say project is USPJ2201200001, then sequence perhaps should be something like:
USPJ220120001-0001@@1
USPJ220120001-0002@@2
etc.
to keep it sane…and not conflicting with the next USPJ#. I am not sure this could be done outside of a customization and if you do this as a customization then the line number can also always be @@1 too. I could be wrong but this is what I think.
+24Good idea, Joshua, though I am wondering if this also works with PSA generated orders? When I read the definition in the Global Application Setup.pdf:
It does not mention PSA or projects. If it does, then my initial concern is how do you visually link the service order back to a task from within the Service Order module? It is not obvious by the Request ID that it originated as a project task. Plus this has the knock on effect it is a global setting and perhaps the customer does not want to affect the call routing order_id generation process.
But still, worth investigating for Melissa’s question.
The issue is with integration to their financial system, it cannot handle duplicate order numbers. They want to use either phase or transactional PSA invoicing at different steps in the project with the same order number their system cannot process.
Joshua, that setting worked. It actually created a unique SV number when deployed from a project. It references the project number in the source document id. thank you!
+24Cool, thanks Joshua!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.