Restricting the user from deleting a personel number

Hi All,
Can anyone help me in restricting the user from deleting a personel number.
Thanks & regards,
Venkat

Hi Venkat,
The utility menu will ultimately calls to PU00 so it doesnt matter , system wont allow him to delet.
You can try it out in quality if you want.
Award points if useful
Regards,
Bhupesh Wankar

Similar Messages

Is it possible to restrict the user from creating a sibling and allow him to ONLY create child nodes in DRM?

When in a hierarchy, a user right clicks on a node to crate a new node, he has two options
-Child
-Sibling
Is it possible to restrict the user from creating a sibling and allow him to ONLY create child nodes?
Business cases:
1. different level nodes need to have different prefixes.
- Thus, the default prefix property definition uses the level number to assign a prefix
- Also, a validation, to ensure the correct prefix, uses the level number
But if the user can create a child and a sibling then the default prefix will only be right for a single case and not both.
Thanks

If the images are exactly the same size then make sure the layer with the mask
is the active layer and in the other documents go to Select>Load Selection and choose
your document with the layer mask under Source document and under channel choose the layer mask.
After the selection loads press the layer mask icon at the bottom of the layers panel.
MTSTUNER

How to restrict a user from deleting a PO

Dear All,
I have to restrict some users from deleting a line item in PO. They will be authorised to create & change the PO but they must not be able to delete the line item.
Further it would be more helpful if it is possible to restrict them from deleting one perticular type of PO(ex-Capex PO). They can change a capex PO but can not delete it.
Any of the answars will be highly appreaciated.
Regards
Rutabhadra Panda

Hello,
Speak to your basis guy, put if you have created Capex PO as a particular document type, then maintain authorisation object M_BEST_BSA (Document Type in Purchase Order) and activity 06 delete.
You may find that delete is still possible through activity 02 change, so you might need to maintain different roles depending on what you need.
Thanks.

How to restrict the user from making any changes in Sales order- item level

Hi to all
How to restrict the users from making any changes in sales order at item level if the same sales order is released by senior user through status profile.
Regards
Anish Parikh
Edited by: anish parikh on Jan 24, 2008 5:16 AM

Hi Anish,
This can be achieved through the roles and authorization.
This can be done through the basis team. they can create user profiles and roles.
For the roles they assign some transaction codes so that they can view the only assigned tr. codes.
Like that ur requirement can be done.
Also u can prevent the user to change any fields in the sales order screen (VA02). for that please modify the authorisations.
Hope i answers.
Reward points if useful.
Edited by: kaleeswaran bhoopathy on Jan 24, 2008 9:57 AM

How to secure the users from deleting the work items

Hi all,
I have a question like this.........whether we could secure the users from deleting the work items by someone in the Project and also assigning a specific user to allow them to delete the idoc.
Please help me on this as this is critical.........
Thanks in advance
Chakri

One of t he possible way is, ask the basis team to create users as Service Users and you can determine whether the login user is whether a service or dialog user by using the a bapi BAPI_USER_GET_DETAIL under the exporting parameter logondata with field USRTYP where if the logged in user is Service user then this field will be populated as S if the user is a dialog user then it will be populated as A.
Now in more efficient way of fixing this is get the list of users for whom you donot want to give the authorization of deleting workitems and assign the appropriate role for all the listed users...
for roles and authorizations i hope the basis team is the right team to consult....

How to restrict the user from accessing other screens before submittingdata

Hi All,
I have some screens developed in Webdynpro ABAP and all these have been linked to Portal as pages. In Portal If i click on the link in detailed navigation i can see the corresponding screen on the right side. Now in one screen i have to input some data and submit the data, Now my problem is if i enter some data and before submitting the data if i click on any other link in the detailed navigation, that corresponding screen is opening and all the data of the previous screen is lost.
Can any one suggest me, how can i restrict the user from accessing other screens before submitting the data of that screen from portal perspective.

Hi Prasanna,
The pages can be restricted from the user access by using the ACL permission or you can restrict the page by making invisible in navigation area which you do not want to show to the user . Open the page properties and select navigation category in the drop down and select the Invisible in navigation area property to yes.By default this property is No.Change the property for all pcd pages which want to hide from user access.
Hope this helps you...
Regards,
Rudradev Devulapalli
Reward the points if helpful....

How to Restrict the users from changing the Default variant of report.

Hello everybody,
The requirement is to restrict the users to save and overwrite the default layout variant (Layout for higher managenet)set for the report, but at the same time they should be able to change and save the other layouts for which they are having access.
I have written the logic in the program which is working fine for all the scenario when we execute the report. But the logic doesnt work if the user is selecting the layout on the output screen of the report.
for e.g if the user runs the report using the layout varaint for which he is having the authorization then he gets the all 4 options so he then he can select the layout for which he is not authorized and he can overwrite.
i have debugged and check as i have found that after the report output is shown all the layout paramater is controllled by the statndard SAP objects.
Can anyone help me out in this issue.
Thankyou in advance.
*to get the default layout variant.
w_save = 'A'.
if p_vari is initial.
    clear disvariant.
    disvariant-report = sy-repid.
    w_variant = disvariant.
    call function 'REUSE_ALV_VARIANT_DEFAULT_GET'
      exporting
        i_save     = w_save
      changing
        cs_variant = w_variant
      exceptions
        not_found = 2.
    if sy-subrc = 0.
      p_vari = w_variant-variant.
    endif.
endif.
*logic to check user authorization to change the layout setting.
if p_vari = c_layout.
    if not sy-uname is initial.
      select single * from agr_users
              where agr_name = c_role
              and   uname    = sy-uname.
      if sy-subrc = 0.
        w_save = 'A'.
      else.
        w_save = ' '.
      endif.
    endif.
endif.
Regards,
Satish.

Hi Maine,
Thanks for your reply.
As you mentioned for your own program, you can control the parameter "I_SAVE", when calling "REUSE_ALV_GRID_DISPLAY".
so already i have use the same logic and control the parameter through I_SAVE and here i am calling method ALV_GRID->SET_TABLE_FOR_FIRST_DISPLAY instead of "REUSE_ALV_GRID_DISPLAY".
and it works fine when we execute the report but the logic doesnt work when the user tries to change and save the layout variant on the output screen of the report.
Regards,
Satish

Restrict the Users from doing Transactions from transactional Iview.

Dear all,
We are having some transactional iviews in EP7.0 and ECC 6.0. We want to restrict the enduser from doing transactions by entering the transaction codes.
1.Can we remove the command line
2.Can we restrict the user
We are using transactional iviews using connectors.
Reply asap
Thanks
Ravi.S

1) There is an its parameter you add in transaction SICF in the webgui service. It is something like ~noheaderokcode.
See here:
http://help.sap.com/saphelp_webas620/helpdata/en/96/c09788c65b11d480c100c04f99fbf0/content.htm
2) Backend authorisations define which transaction codes you have access to.
Paul

Restrict the user from seeing public objects

HI
How to avoid the user from see the other schema public objects
if i use odbc drive for crystal report and i am able to see other schema owner
objects
like ctxsys,dmsys,mdsys
even though it is coming from Public schema i try
revoke select on all_users from public;
it did not help
pls give me some solution how to avoid this

I'm not following you. What I suggested was (let's say it uses all_tables):
- create a local view called all_tables
- filter in that view anything you don't want to see
ops$oskar@test9i$ grant create session to u1 identified by u1;
Grant succeeded.
ops$oskar@test9i$ grant create view to u1;
Grant succeeded.
ops$oskar@test9i$ conn u1/u1
Connected.
u1@test9i$ select distinct owner from all_tables;
OWNER
CTXSYS
MDSYS
OPS$OSKAR
SYS
SYSTEM
WKSYS
WMSYS
7 rows selected.
u1@test9i$ create or replace view all_tables as select * from sys.all_tables where owner not like '%SYS%';
View created.
u1@test9i$ select distinct owner from all_tables;
OWNER
OPS$OSKAR

How to restrict the user from Closing the PO when it is not matched yet

Hi,
Actually PO is finally closed in lines level without matching. Now the problem is how to restrict this in future so that the user can not finally close it when it is not matched.
Thanks
Kavya

Kavya,
Check the setup of Line Type . Check for Receipt Tolerance on the Line Type . It should not be 100%
Please let me know if you have any questions
Thanks
Navin

Is it possible to restrict the user from opening the WSDL page in a browser

Hello All,
The user should be able to send requests to the webservice, but not be able to view the wsdl file in the browser. How can we do this in Weblogic 10 ? is this configurable ?
We need to do this because, the webservice is going to be exposed to the outside world and we don't want everyone to be able to see the WSDL.
Thanks
Chandra

I don't know how to do that, but I would advise against relying on an architecture where you have to hide the WSDL to provide security. That's an illusion. If you fully expose the WSDL and then implement proper security mechanisms, even BASIC Auth under HTTPS, your service will be more secure than with a hidden WSDL.

File Open/Save dialog Restrict the user path selection Is there any way?

Hello,
Is there any way by which we can restrict the user from selecting the path from the Folder Browser/ File Open/ File Save dialog boxes?
For example, I have a list of paths & want to allow the users to select from those paths or their sub folders. Is there any way to achieve this?
Thanks!
-Vinay Pugalia
If a post answers your question, please click "Mark As Answer" on that post or
"Vote as Helpful".
Web : Inkey Solutions
Blog : My Blog
Email : Vinay Pugalia

Hello Vinay Pugalia,
>>For example, I have a list of paths & want to allow the users to select from those paths or their sub folders. Is there any way to achieve this?
As far as I know, starting with Windows Vista, the Open and Save As common dialog boxes have been superseded by the
Common Item Dialog:
https://msdn.microsoft.com/en-us/library/windows/desktop/ms646960%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396
You could have a try to restrict the value of “look in”(shown in the opne dialog) and “Save in”(shpwn in the save dialog). If you want an example about the usage of this API, you could post a code sample request to:
https://code.msdn.microsoft.com/site/requests
Regards.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Blocking users from deleting chat history

I am a system admin and our users are suing skype IM. Some users are using the skype IM for their personal use. We want to view all the chat history of all the skype users. So, I want to block the users from deleting the skype chat history.

Any chance anyone from Skype can respond to this?? The lacking control over skype as a system admin is the main reason Skype is lacking adoption in the enterprise. We need a simple chat and video call solution both internally and externally but Skype might be out automatically if there is no way to control the chat history. Primarily we need to stop users from deleting the history, and the ability to retrieve the history remotely.

Prevent user from deleting PO

1. Is there a way to prevent the user from deleting the PO item if GR/SA had been done for service PO. (Just like how the system behave for material PO - Message 06 115).
2. We also want to prevent the user from deleting the PO item if GR/SA and IR had been done for service and also material.
Please advice. Thank You.

1.Is System allowiing the user to DO ?
2.User Deleting only Items ?
if So then u have to activate User Exits or BADIs.
Regards
Peram

How to restrict the user(Schema) from deleting the data from a table

Hi All,
I have scenario here.
I want to know how to restrict a user(Schema) from deleting the values from a table created in the same schema.
Below is the example.
I have created a table employee in abc schema which has two values.
EMPLOYEE
ABC
XYZ
In the above scenario the abc user can only fire select query on the EMPLOYEE table.
SELECT * FROM EMPLOYEE;
He should not be able to use any other DML commands on that table.
If he uses then Insufficient privileges error should be thrown.
Can anyone please help me out on this.

Hi,
kumar0828 wrote:
Hi Frank,
Thanks for the reply.
Can you please elaborate on how to add policies for a table for just firing a select DML statement on table.See the SQL Packages and Types manual first. It has examples. You can also search the web for examples. This is sometimes called "Virtual Private Database" or VPD.
If you have problems, post a specific question here. Include CREATE TABLE and INSERT statements to create a table as it exists before the policies go into effect, the PL/SQL code to create the policies, and additonal DML statements that will be affected by the policies. Show what the table should contain after each of those DML statements.
Always say which version of Oracle you're using. Confirm that you have Enterprise Edition.
See the forum FAQ {message:id=9360002}
The basic idea behind row-level security is that it generates a string that is automatically added to SELECT and/or DML statement WHERE clauses. For example, if user ABC is only allowed to query a table on Sunday, then you might write a function that returns the string
USER != 'ABC'
OR      TO_CHAR (SYSDATE, 'DY', 'NLS_DATE_LANGUAGE=ENGLISH') = 'SUN'So whenever any user says
SELECT *
FROM    table_x
;what actually runs is:
SELECT *
FROM    table_x
WHERE   USER != 'ABC'
OR      TO_CHAR (SYSDATE, 'DY', 'NLS_DATE_LANGUAGE=ENGLISH') = 'SUN'
;If you want to prevent any user from deleting rows, then the policy function can return just this string
0 = 1Then, if somone says
DELETE employee
;what actually gets run is
DELETE employee
WHERE   0 = 1
;No error will be raised, but no rows will be deleted.
Once again, it would be simpler, more efficient, more robust and easier to maintain if you just created the table in a different schema, and not give DELETE privileges.
Edited by: Frank Kulash on Nov 2, 2012 10:26 AM
I just saw the previous response, which makes some additional good points (e.g., a user can always TRUNCATE his own tables). ALso, if user ABC applies a security policy to the table, then user ABC can also remove the policy, so if you really want to prevent user ABC from deleting rows, no matter how hard the user tries, then you need to create the policies in a different schema. If you're creating things in a different schema, then you might as well create the table in a different schema.

Restricting the user from deleting a personel number

Similar Messages

Maybe you are looking for