This content has been marked as final. Show 14 replies
However, most settings can be changed on the project itself as long as there are no transactions.
Were I to advise my users in this case, I would tell them to recreate the project.
Thanks. Unfortunately the users dont want to recreate a project , agreement and budget again.
Ok ... then change the settings.
What are the differences between the template used and the one you should have used?
List them, go into the project and make the changes. The project will behave as if it was created from the correct template.
If the project type is different you may have problems if the Project Type Class allows or requires different kinds of budgets. If there are transactions you will not be able to change many key setups. If you have generated and released revenue you will be unable to change billing setups.
The one field you won't be able to change under any circumstance is the CREATED_FROM_PROJECT_ID.
Edited by: Chaco on Mar 27, 2013 12:37 PM
Thanks a lot for your reply. Sure I shall try this.
I have another question too.
Do you know if we can restrict users from modifying a project (status) and allow only a super user to modify ?
You may enable the Project Status WORKFLOW.
That can be configured to send the status change request to a super user.
You may also configure the workflow to look is the user initiating the workflow is a super user, and if not reject the request automatically.
Another option is to create 2 responsibilities and remove the function for changing project status from one of them.
Thanks. This is to be done only for one project. How can this be done ?
Project Setups are restricted by project role.
If the sys admin or separate person is given the Project Manager Role and all other team members are given roles less powerful, then you control access on who can change the project status.
If you need more complex divisions of functions you may not be able to accomplish this via project roles.
Thanks a lot Chaco.
My requirement is that only one project which we have created should not be updated by anyone except one person. We could create a new responsibility and have the project form open with one project alone..But how do we stop the project from being listed when the current responsibility is used to query.
Changing the cross project view to No will limit viewing of the project to team members.
Thanks a lot. Can you please tell me if I can change the project's operating unit after creation ?
No; the OU is dictated by profiles set for the responsibility. Projects is heavily OU specific. Accounting is also driven to the Ledger/SOB in system implementation options.
Thanks a lot for your help.