- SAP Community
- Groups
- Interest Groups
- Application Development
- Discussions
- Change Variant Created by Another User
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Change Variant Created by Another User
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2008 8:53 PM
Hi,
Is there a way to make changes to a variant created by user ID other than yourself? I want to modify an existing variant that was created by a user ID that is no longer with the company. I don't want to use the user ID that created the variant.
Thanks,
Wes
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2008 9:17 PM
Please read the threads here in the forum about report RSVARENT, which will unlock the protection again.
I recommend that you give it a test run in a sandbox first together with a developer. ( Very NB! )
The report has some nasty features for the unsuspecting...
- It contains no authority-checks what-so-ever.
- By default it is not protected by an authorization group (see SAP notes on report RSCSAUTH).
- In earlier releases, if you do not specify which report variant you specifically want to unprotect, it unprotects them all.
- It does not raise any exceptions or error messages or warnings before you make mistakes.
To be treated with caution, but it does the job.
Cheers,
Julius
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2008 9:17 PM
Please read the threads here in the forum about report RSVARENT, which will unlock the protection again.
I recommend that you give it a test run in a sandbox first together with a developer. ( Very NB! )
The report has some nasty features for the unsuspecting...
- It contains no authority-checks what-so-ever.
- By default it is not protected by an authorization group (see SAP notes on report RSCSAUTH).
- In earlier releases, if you do not specify which report variant you specifically want to unprotect, it unprotects them all.
- It does not raise any exceptions or error messages or warnings before you make mistakes.
To be treated with caution, but it does the job.
Cheers,
Julius
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2008 11:17 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2008 11:46 PM
Yes it does the job, but please take note of the warnings in my above post because RSVARENT will not warn you if you do not use (and protect it) carefully.
If you do not maintain the input parameters for exactly that which you want, it will do more than you intended.... and by default it cannot be excluded that anyone can run it to the selection screen.
The Rolls-Royce approach is to use the S_PROGRAM authorization group to protect the variants of the reports via field p_action = 'VARIANT' to a group of users authorized to maintain them (via transaction VARCH) and therefore also schedule them or change programs scheduled with those variants. The developer can in special cases also determine that the report is submitted in the background only via the parameters set by the variant, without a user being able to influence the selection screen in the foreground.
Take care,
Julius
Edited by: Julius Bussche on Nov 26, 2008 12:50 AM
- SAP Managed Tags:
- Security
