on 03-12-2007 3:08 PM
Hi there,
When you create a new Maintenance Project, you can NOT choose a solution. (while with all the other types of Projects, you can).
F1 suggest, you assign the MaintenanceProject in the Solution itself.
So you can only assign 1 MaintenanceProject to 1 Solution.
We have multiple Maintenance Projects (one for FI, one for Logistics, ...) for 1 Production system.
My Question(s):
- Is it necessary to assign a Maintenance Project to a Solution.
- What are the beneficial functionalities of it.
regards
Steven
Hi Steven,
main reason for the assignment of a maintenance project to a solution is the "Check-out/Check-in" functionality in Solution Directory. The idea is to log the complete Solution Directory against changes. Changes can then only be done by a check-out into a maintenance project. The assignment between solution and maintenance project determines that the check-out is done into the corresponding maintenance project. All changes that are done in the maintenance project are accessible via the history functionality of the solution. It is possible to use the same maintenance project for several solutions. In your case, you may select one of your existing maintenance projects for the check-out.
Best regards,
Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.