on 07-25-2008 8:30 AM
Hi guys,
Our requirement of release strategy for PRs is as follows;
the strategy should be triggered based on the following
1) PR document type
2) PR value
3) purchase group
4) user creating the PR
For example, if user1 is creating the PRm it should go to Manager1-HOD1-CEO and if it is created by user2 it should go to Manager2-HOD2-CEO like this.
Like the above, there will be more than 500 users creating the PR and in one combination maximum 2 users will be there.
WE are configuring four characteristics for the above four values for comm structure CEBAN and different strategies for different combinations.
If we use ERNAM for this scenario, we need to configure more than 200 strategies for PR. Is there any other way of doing this to reduce the number of release strategies or this is the only way ?
Also if we link the release strategy to HR module can we reduce the number of strategies to be configured?
Any ideas or suggestions?
fine.lets think X-user(who willbe creating a PR)
the release codes willbe based on Manager1-Manager2-HOD1-HOD2-CEO and so on.
now lets say for a particular pr whoose document type willbe NB,ER (purchasing group),<1000 INR(value)---the release will go upto Manager1.
for this u willbe using the release code of the Manager1only and while assigning objects u willbe choosing NB,ER,<1000 INR respectively for the characteristics.
again for a particular pr whoose document type willbe NB,ER (purchasing group),1000-20000 INR(value)---the release will go upto Manager1and HOD1.for this u willbe using the release code of the Manager1 and HOD1 and while assigning objects u willbe choosing NB,ER,1000-20000 INR respectively for the characteristics.
AND SO ON.............
regards,
indranil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
let the user have the authorisation of creating all types of PRs.
but definitely they willnot be having the authorisation for releasing the PRs as per ur earlier post
the persons like Manager 1,Manager 2 etc will be having their respective release codes and the person who willbe authorised to release thru those particular codes wilbe assigned for that role by the basis person to its user id.
regards,
indranil
Hi Indranil,
What u are suggesting will arise after release strategy has been triggered. My questin was how to configure release strategy so that only particular strategy will be triggered based on the user.
As u ahve suggested we can control the authorisations for a release code, But this will not solve my problem.
My problem is whetehr i need to create that many no of strategies or i can reduce the numbers by some other criteria
any more suggestions?
Thats the point i am trying to say.Triggering of release strategy doesnot depend upon user,but the characteristic value u r choosing as well as the clients requirement.if ur client want that for different document type,different release strategies will trigger,then u have to create different strategies.otherwise in one release strategy u can assign all the document types.
regards,
indranil
HI Indranil,
Sorry to bother u. Again if strategy is to be triggered on the basis of characteristic, i need to create a characteristic for creator also and i need to include this in configuration. This requires more than 200 strategies to be configured.
is there any better way of doing this to reduce the number of strategies
This is what i was looking for.,
thanks in advance
why are u using the characteristic for user?any specific reason?
i ask u this becoz if the user who willbe creating the pr will also be having the release authorisation,that authorisation can be assigned thru basis person.and if the user willnot be having any release authorisation then there is no need to use him/her as a characteristic.
regards,
indranil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.