CO02 Authorisation Object for System Status

[Former Member]

Hi All,

Could you please let me know how to restrict access to the System Status of a production order ?

T-Code : CO02.

Thanks a lot in advance.

Thanks and Regards

Kushan

[Former Member]

You can use this authorization object C_AFKO_AWA to restrict the authorizations for

maintaining production orders and process orders for each plant and

order type.

This authorization object is a combination of the previous authorization

objects C_AFKO_ATY and C_AFKO_AWK for production and process orders.

ined fields

The system checks the following fields:

Field Possible Values Description

ACTVT 01 The user can create orders.

02 The user can change orders.

03 The user can display orders.

04 The user can print orders.

06 The user can archive orders and delete them.

AUTYP 10 Production orders (PP-SFC)

40 Process orders (PP-PI-POR)

AUFART All order types valid for production

and process orders.

WERKS All valid plants in the system.

Thanks,

Prasant K Paichha

[Former Member]

Respected Sir,

Greetings for the day!!!!!!

I am facing a problem of similar kind....

I want the plant users to create Production orders,change it,and TECO it if necessary............

But I want some restrictions in doing so.....The users should not be able to "REVOKE TECO".

I tried using BS22,but it applies for all users,and I want some of users with that right.

I am also not able to do through SHD0...

plz guide

[Former Member]

Dear Kushan!

Actually, the "System Status" on Co02-Production Order as a part of general status, and are maintained and delivered by SAP.

which cannot be restrict the blue i button for the system status.

Regards

Anwer Waseem

[Former Member]

HI,

Can you brief is more on what is that you want to achieve? what exaclty do you want to do?

[Former Member]

Hi All,

Thanks for all your valuable contributions. I'm still stuck with this issue. I need to block users accessing the Status of CO02.

I found User Exit EXIT_SAPLCORE_003 for this purpose, but it does not trigger in CO02.

Is there anything else that I can do to block users accessing the status ?

Thanks and Regards

Kushan