Maintaining different values for Accounting Type (KOART)

Question

Hi experts,
I have several accounting tcodes such as FBV0, FB03, FB08, FV65,FV60 in one parent role.
FV60, FV65 are added to this role as FBV0 is checking internally for this authorization object. 
All these tcodes share a same object  F_BKPF_KOA which differ by activity and the accounting type (KOART).
The KOART field is an org level field defined by SAP and I have entered D,K,S as values.
But the auth object values should be different for the accounting types.
i.e  03 for D,K,S
     01,02,03,77  for S
     03,77 for K
All the derived/child roles for this parent should also have the same document type as the parent. How can I achieve this as this object is maintained at the org level.
I could not delete this obj from being an org level element as it is defined by SAP.
Appreciate your response.
Thanks
Kee

Answer 1

> If KOART is an org field you cannot differentiate between authorized activities for each of the KOART values in one role. Whether you maintain values in the parent or not only matters if you're planning to assign the parent roles to users or if you just use them as templates.
>
Parent Roles should not be assigned to any users. It should only be used as Template to grant and control Non-Organization Level authorizations centrally (you can see these option in Parent roles). Concept of Parent-Child role is to avoid creating same roles where all authorization field values are exactly same and differs only for Organization Values (different Site / Branch Office specific constants). So we can maintain the Org. levels as different sets for a single Parent role as I already explained.
For more details:  Note#314513 - PFCG: Maintaining individual organizational levels
Note#532695 - PFCG: Incorrect organizational level values in derived roles
>
> Please elaborate on this one. I think we're running into an urban myth here....
>
> Organizational levels are only instruments to assist in building roles. For the final profile it does not matter whether a field is organizational or not. It will not influence the behaviour of the authority-check.
For the final profile it matters during loading of User authorization data to User Buffer. Think about the Parameter values stored for a particular user. How it behaves for all Objects containing a particular Auth. Field and providing default assignment for that user whenever he tries to perform any action where this field is required to populate.
If we delete any Object from SU24 proposal then it doesn't mean that the check will not be carried out or the Org. Field contained in that object will not be populated with it's values. I tried to make this clear to the requester.
Regards,
Dipanjan
Edited by: Dipanjan Sanpui on Jun 8, 2009 7:49 AM