SAP OSS user ID's

[Former Member]

We are trying to implement a good process for requesting, checking out, and assigning the OSS ID's. Can you please let us know what you do or perhaps best practice of this?

Do you have SAP_ALL assigned to OSSUSER IDs?

Do you require approval from a manager prior to using?

Does your ID's expire in SU01 valid-to date?

How do you designate an OSS ID is for a particular message or ticket?

Do people request these before they log tickets or after when SAP wants this information?

Are you using Fire Fighter to track what they do?

Are you reviewing their activity? If so, how often?

We want to make the SOX auditors happy with our process. Any information will be helpful.

Thanks,

Carly

[arpan_paik]

Hi Carly,

1) SAP_ALL never.

2) Even any update access not without approval.

3) Create a display role for all the module and assign that to OSS ID.

4) If you have FF ID then that is more good. Link OSS ID to FF ID and put display role to FF ID.

5) Now if for certain case update access is required then specific approval is required and that will be monitored by FF log.

6) Thumb rule is that SAP not mean to update any data in customer system.

7) Based their suggestion Support will update

😎 Normally in 90% case SAP will need display access and for this no approval should be mapped as SAP will display only.

9) Also a map is required with basis team to open client

Arpan