on 08-21-2014 10:14 AM
Hi PS Experts,
I try to define WBS User Status for a status profile in transaction OK02.
The status CACL has to be selectable from any other status. If CACL is set, it should not be possible to change this status.
The sequence logic for the other status works so far.
At the moment I do not see any change to realize my requirements for status CACL.
Anyone having an idea?
StNo | Stat | Low | High |
1 | 1BQU | 1 | 2 |
2 | PBIH | 2 | 3 |
3 | ODIN | 3 | 4 |
4 | JSHP | 4 | 6 |
5 | SRNE | 5 | 7 |
6 | PRDS | 5 | 7 |
7 | DELI | 7 | 8 |
8 | INST | 8 | 9 |
9 | ISFI | 9 | 10 |
10 | ADST | 10 | 11 |
11 | ADFI | 11 | 12 |
12 | INSP | 12 | 13 |
13 | GPIN | 13 | 15 |
14 | HDTS | 14 | 16 |
15 | HDTC | 14 | 16 |
16 | BROP | 16 | 17 |
17 | TECC | 17 | 18 |
18 | FIAC | 18 | 19 |
19 | WPFI | 19 | 20 |
20 | CACL | ??? | ??? |
Regards,
Philipp
Hi Philipp,
As CACL will be the final status from which from which you do not wish to change the status, please ensure that the lowest status number that will be assigned to this is 21 and the highest also 21. This will mean that once CACL is set, you will not be in a position to revert to the earlier status.
Regards
Varun Rudrabhatla
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rudrabhatla,
thanks for the fast reply.
If I do so, I get the following error message
The lowest status number is larger than the status reference number
Message no. BS268
The lowest sequence number cannot be higher than the actual status order number.
For status 20 I have to assign the lowest number <= 20. With this approach, the status 20 can not be changed. But this does not solve the second part of my requirements. Status 20 must be setable from any other status. The only way to do this is to enter status 20 as the highes number for all other status. But this would mess up my defined sequence logic for Status 1 to 19.
hi Phillip,
in this case i think this should work -
this should allow you to select status 20 from any status before and once you are in status 20 it doesn't allow you before that status.
only side affect of this setting is i can change any status to any status between 20
for ex: i can change 1BQU to HDTS
not sure if this is ok for you.
StNo | Stat | Low | High |
1 | 1BQU | 1 | 20 |
2 | PBIH | 2 | 20 |
3 | ODIN | 3 | 20 |
4 | JSHP | 4 | 20 |
5 | SRNE | 5 | 20 |
6 | PRDS | 5 | 20 |
7 | DELI | 7 | 20 |
8 | INST | 8 | 20 |
9 | ISFI | 9 | 20 |
10 | ADST | 10 | 20 |
11 | ADFI | 11 | 20 |
12 | INSP | 12 | 20 |
13 | GPIN | 13 | 20 |
14 | HDTS | 14 | 20 |
15 | HDTC | 14 | 20 |
16 | BROP | 16 | 20 |
17 | TECC | 17 | 20 |
18 | FIAC | 18 | 20 |
19 | WPFI | 19 | 20 |
20 | CACL | 20 | 20 |
Hi mos lan,
that is exactly myproblem. The status changes between StNo 1 and StNo 19 have to follow the original defined sequence logic. e.g from 1BQU is only a change to PBIH possible AND also to CACL.
I guess this is not possible with the range logic from SAP. Therefore I proposed the customer the following idea:
Define no StNo for CACL -> this Status is selectable as checkbox parallel to one of the (radio button) status.
Regards,
Philipp
Hi Philip,
You are correct in proposing that sol. as the range logic for user statuses will not achieve your business requirement of setting the last status at any point in time.. These two are contradicting each other.
Cheers
Sammar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If CACL is set, it should not be possible to change this status.
Hi,
For CACL you can set lowest status no. as 21. 21 itself will require a status with lowest no. 21 or more (which o other user status have as per your data). But, still the status can be 'reset' manually as and when required.
Please check and let us know if it works.
Regards
Saurabh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
100 | |
11 | |
11 | |
6 | |
6 | |
5 | |
4 | |
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.