Skip to Content
author's profile photo Former Member
Former Member

authorization group cannot add

Hi

I want to define the additional authorization group on the following tables.

v_tvm1

v_tvm2

v_tvm3

v_tvm4

v_tvm5

I have generated the access key for the v_tvm1 to check the scenario, the existing authorization object of the following tables are "VA" SD: Appl. table.

I have overwriten the authorization object and generate the new request which solved our problem but the existing authorization group might be pre-requisites for the SD Application and may arise inconsistences in the future.

I don't want to the users should authroized with the default authorization group "VA", otherwise, the users get unauthorized access of the tables whose authorization group are "VA"

I want to assign the new authorization group on the following table and restrict them by the new authorization group.So that, users will restricted by those tables have authorization group are "ZMMT"

When i add the new authorization group in the table maintenance by the se11, the process has been ended with the below popup

Choose the key from the allowed namespace

Message no. SV019

Diagnosis

You have attempted to create an entry and have used a key which is not

in your namespace.

This can cause problems in later upgrades because the entry could be

overwritten by an import, or overwrite an existing entry.

Procedure

Check your entry and try to enter a key value from your namespace.

You can display the namespace definition with RDDKOR54.

Please advise us. or do you recommending me to overwrite the existing authorization group on the following tables. ?

REgares

Anwer Waseem

SAP BASIS

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Jan 29, 2008 at 11:57 AM

    Hi Anwer

    Why do you need to change the auth group on them?

    Just get the users to access them via the tx linked to those views (check out Julius' post on the following thread https://forums.sdn.sap.com/click.jspa?searchID=8407692&messageID=4723045 ) and keep the standard VA auth group. Users shold not be able to access them in prod in any other way, especially not via SM30 etc.

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Anwer,

      As per my previous post

      1. Assign the transactions (look in the link that I provided) to the users

      2. Do not give the users access to SM30 in production. They do not need it. Find or create alternative transactions for the other tables they need to alter.

      There is very, very rarely need to give any users access to SM30 in production.

  • author's profile photo Former Member
    Former Member
    Posted on Jan 29, 2008 at 12:59 PM

    Thanks for the reply.

    Yeah! the super don't 've sm30 access in the PRD server.

    However, I will try to manage with the t-code instead of sm30.

    REgardssss

    Anwer Waseem

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.