cancel
Showing results for 
Search instead for 
Did you mean: 

Easy DMS Authorization

former_member219170
Participant
0 Kudos

Dear Friends,

I have done Easy SAP DMS installation. I created short cut also in Desktop.

I am having the following problem:

In Easy DMS I could not able to control authorization based on document type for users. The R/3 base application Release is 7.01

I did the following customization for Easy DMS. SPRO- Coross Applications- DMS- Easy DMS- Define user groups. The eentries are : User group: user, User: DMS_User1; Role: Z:DMS_USER. I didn't enter any thing in the paramteres.

For role Z:DMS_USER, I entered only ZAC and ZAL doc. types in respecteive objects. I have considered the objects: C_DRAD_OBJ;C_DRAW_DOK;C_DRAW_MUP;C_DRAW_STA;C_DRAW_TCD;C_DRAW_TCS. After that I removed doc. type in all objects and added the values for ACO_SUPER object. For ACO_SUPER added field as READ for activity ACO_ACT_S and DIS for ACO_OTYP_S.

In both the case with the userID: DMS_User1, could able to create / change / display DMS doc. for all doc. types in Easy DMS.

Can you help me how to do this ? Did I miss anything ?

When I am going thru help I found :

u2018ACO_SUPERu2019 is the only PFCG object for working with ACLs in SAP Easy Document Management.

PFCG roles (objects) and ACLs are independent of each other. If both PFCG objects and ACLs are maintained, the system takes both of them into account, but PFCG roles are given preference.

Can you help me so that I could able to control authorization for user based on doc. type.

Regards,

Sai Krishna

Accepted Solutions (1)

Accepted Solutions (1)

christoph_hopf
Advisor
Advisor
0 Kudos

Dear Sai,

based on your description I would not recommend you to use the ACO_SUPER authorizations. Because with this authorization object normally all other authorizations are overruled and no longer effective.

I think that an authorization trace could help to get the necessary authorization objects which are checked and required to control the user behavior. For more information on this trace and the DMS authorization objects please see the following links too:

http://wiki.sdn.sap.com/wiki/display/PLM/CADMS-AuthorizationObjects

http://wiki.sdn.sap.com/wiki/display/PLM/AuthorizationTrace-+ST01

Best regards,

Christoph

former_member219170
Participant
0 Kudos

Hi.

I solved my problem by removing ACO_SUPER object for that role.

Regards,

Sai Krishna

Answers (1)

Answers (1)

Former Member
0 Kudos

Dear sai krishna

I've met a same problem and I solved it.

Check this link []

Ask me what you don't understand.

An NLP