Issue with User status in REL stage.

[Former Member]

Hi all,

i had created User status profile with few status followed by lowest & highest no. System work fine in CRTD (System Status), acording to the highest and lowest no. assigned, but once it is in REL status system is allowing to go back at any user status from any user status. it is not according to the no assigned to the highest & lowest status no. Any solution for this issue.

Regards

[Former Member]

Can you please share the details of you user status profile, how you have defined? so that it will be easy to provide a proper solution.

Praveen

[Former Member]

hi,

the status is as follow:

Status No Status Short text Lowest Highest

5 CRTD abc 5 10

10 AWL1 abc 10 20

15 L1RJ xyz 10 15

20 L1AP xyz 20 35

25 AWL2 xyz 25 35

30 L2RJ xyz 10 30

As per logic system should not allow to move in status no 10 (AWL1) when current status is 25 (AWL2).

it is working fine in CRTD, but once it is REL system is not working according to the lowest & highest no allocated to the status.

Regards.

[Former Member]

Then enter 10 as the lowest for the line 25.

[former_member203108]

If you enter 10 as the lowest for 25, then system will allow you to move to status 10 from 25. I think Mukesh doesnt want this and he also done the config correctly

[Former Member]

I have tested this scenario (the values as you mentioned above) in my system and working fine. In CRTD and REL statuses.

The setup you have done is correct only.

Try creating a new project and test the scenario in development client once.

Praveen

[Former Member]

Dear all,

i have tested the scenario in all the aspects @ REL status, syatem is working accordingly when i am comming top to down (5 to 35, once it is bottom to up (35 t0 5) it is not stoping the user status as per the lowest no. assigned. if the lowest no assigned is 25 system is allowing 10, 15, 20 & 25 all user status. i hope senario is clear now, Kindly suggest.

Regards

[former_member203108]

I had understood your problem, but whatever you are saying it should not happen like this in Std. SAP. check whether any ABAP development has been done to allow the user status to change irrespective of the order, after releasing.