Restrict User to particular Documant Type

Dear All,
Please read Carefully !
I have 5 Document Type to create PO.
now my problem is that how can i restrict a particular user only for 2 Doucument Type PO.
Only Allowed Document Type i.e. 2 not all must be Found in Dropdown List not all document Type.
Regards,
Pardeep Malik

Dear All,
Thnks for ur response !
But i want to hide Document type in Dropdown List !
Please help me
Regards,
Pardeep Malik

Similar Messages

Restrict User for Particular Doc Types and GL Account

Dear Experts,
I want to restrict few users with Doc type JV and Posting to GL Account 1 - 1000
I created a set for Username fo be restricted and i have written a Validation for Line Item saying
Prerequiste
BKPF-BLART = 'JV' AND BKPF-USNAM IN T_DOC_USERS
Check
BSEG-HKONT >= '1' and BSEG-HKONT >= '1000'
Mesaage
User Resticted for Doc Type JV and GL Account
Can someone please advice on priority
Thanks in Advance !!!!
Regards
Rahul

HI
1.You can restrict the user to document types by authorization settings Transaction Code PFCG
Note : This will not hide entries in a drop down list.
2.You can restrict the user to view the General Ledger reports like FBL3n,FBL1N like wise
Hope this will help you

Restriction of a particular Movement type

Hi Experts,
Can we restrict entry for a particular movement type ( Say 501/502 Movement type)
1) For a particular User
2) For a particular Material Type
3) For a particular Material Code etc
If yes what is the best option? Pls reply points will be provided for helpful answers
Regards
Milind Nair

Hi Milind
If u want to restrict movements userwise u can do it with authorization
Use auth object M_MSEG_BMB & M_MSEG_BWA &M_MSEG_LGO .. Here remove the movement type you want to restrict for the user or assign the activity as display only.
Take help from basis for this
Vishal...

Restricting Material for particular Order type

Dear Guru's,
Is it possible to restrict particular material for particular order type in CO01.
E.g. Material A is used in CO01 for order type X
Material B is used in CO01 for order type Y
I want to restrict CO01 should not allow production order creation of material A with order type Y.
Regards
Chandan.

Hy,
By the use of production scheduling profile you can set default order type for the required materials.But it doesn't restrict the other order type. During the manual order creation if user has select other order type then , there is no restriction.So as Mr. Shiva said put restriction over manual order creation, if possible.other option may be by using User Exit.
Now in your case you want to restrict materials not material type. So it is quite complicated for Abaper to write code , because the for every new material Abaper has to change code.
So there is one option by grouping perticuller materials under one production scheduler and then it is more convient for Abaper to create code for User Exit.
Pls refer below thread which may give some more inputs for your requirments.
[Ugent: How to restrict a Material Type for a Specific Process Order Type;
Regards,
Dhaval

How to give authorization for create and change particular Condition Type

Hi...
In my requirement is , Only one user can be authorized to create and change a particular condition type 'ZABC' in vk11 and vk12 .
For remaining condition type can be used as in normal .
How to do this ? How to give authorization for a particular user for particular condition type ?
Plz guide me ..
Thanks in advance .
Deepa .

Hi Deepa ,
u can check A.Object V_KOND_VEA, in user profile u can assign condition type or tables.
have a word with ur basis guy , so he can help u in better way.
aand also ref FM SD_COND_AUTH_CHECK
Regards
Prabhu

Restrict the user   based on document type on migo transaction-prepare GRN

Hi,
We are running ECC6.0 R/3 system.We had a requirement as follows
In MIGO transaction , we want to restrict the user on document type i.e. we want that a particular user can prepare GRN for document type STO only. He cannot prepare GRN for other document type.
We checked SU24->maintain check indicators for transaction codes->enter migo->execute->check indicator.This returned us the authorisation objects present in Migo transaction.We checked the help of all these objects,but none of them we found suitable for above mentioned requirement.We were planning to find out the proper authorisation object to add to Profile generater.
The following is the objects which we have checked for.
A_B_ANLKL-->     Asset Postings: Company Code/Asset Class
A_B_BWART-->     Asset Postings: Asset Class/Transaction Type
B_USERSTAT-->     Status Management: Set/Delete User Status
B_USERST_T-->     Status Management: Set/Delete User Status using Process
C_AFKO_AWK-->     CIM: Plant for order type of order
C_CACL_DSG-->     Interface Design
C_DRAW_BGR-->     Authorization for authorization groups
C_DRAW_DOK-->     Authorization for document access
C_DRAW_TCD-->     Authorization for document activities
C_DRAW_TCS-->     Status-Dependent Authorizations for Documents
C_KLAH_BKP-->     Authorization for Class Maintenance
C_STUE_BER-->     CS BOM Authorizations
C_STUE_WRK-->     CS BOM Plant (Plant Assignments)
C_TCLA_BKA-->     Authorization for Class Types
C_TCLS_BER-->     Authorization for Org. Areas in Classification System
C_TCLS_MNT-->     Authorization for Characteristics of Org. Area
F_BKPF_BUK-->     Accounting Document: Authorization for Company Codes
F_BKPF_BUP-->     Accounting Document: Authorization for Posting Periods
F_BKPF_KOA-->     Accounting Document: Authorization for Account Types
F_FICA_FOG-->     Funds Management: authorization group of fund
F_FICA_FSG-->     Funds Management: authorization group for the funds center
F_FICB_FKR-->     Cash Budget Management/Funds Management FM Area
F_KNA1_APP-->     Customer: Application Authorization
F_LFA1_APP-->     Vendor: Application Authorization
F_SKA1_BUK-->     G/L Account: Authorization for Company Codes
G_GLTP -->       Spec. Purpose Ledger Database (Ledger, Record Type,
                               Version)
J_1IDEP_SL-->     Authorization object for depot sale transaction
J_1IEXC_OT-->     Authorization object for Other Excise Invoice Create
J_1IEX_PST-->     Autorization object for posting Other Excise invoice
J_1IGRPT1-->     Auth. for PART1 at GR
J_1IINEX -->            Incoming Excise Invoice
J_1IRG23D-->     Authorisation object for Depo Transactions
K_CCA-->                     CO-CCA: Gen. Authorization Object for Cost Center
                                Accounting
K_CSKS     -->                CO-CCA: Cost Center Master
K_CSKS_SET-->     CO-CCA: Cost Center Groups
K_PCA-->                    EC-PCA: Responsibility Area, Profit Center
L_TCODE-->                    Transaction Codes in the Warehouse Management System
M_ANFR_BSA-->     Document Type in RFQ
M_ANFR_EKG-->     Purchasing Group in RFQ
M_ANFR_EKO-->     Purchasing Organization in RFQ
M_ANFR_WRK-->     Plant in RFQ
M_BEST_BSA-->     Document Type in Purchase Order
M_BEST_EKG-->     Purchasing Group in Purchase Order
M_BEST_EKO-->     Purchasing Organization in Purchase Order
M_BEST_WRK-->     Plant in Purchase Order
M_MATE_CHG-->     Material Master: Batches/Trading Units
M_MATE_STA-->     Material Master: Maintenance Statuses
M_MATE_WRK-->     Material Master: Plants
M_MRES_BWA-->     Reservations: Movement Type
M_MRES_WWA-->     Reservations: Plant
M_MSEG_BMB     -->Material Documents: Movement Type
M_MSEG_BWA-->     Goods Movements: Movement Type
M_MSEG_BWE-->     Goods Receipt for Purchase Order: Movement Type
M_MSEG_BWF-->     Goods Receipt for Production Order: Movement Type
M_MSEG_LGO-->     Goods Movements: Storage Location
M_MSEG_WMB-->     Material Documents: Plant
M_MSEG_WWA-->     Goods Movements: Plant
M_MSEG_WWE-->     Goods Receipt for Purchase Order: Plant
M_MSEG_WWF-->     Goods Receipt for Production Order: Plant
M_RAHM_BSA-->     Document Type in Outline Agreement
M_RAHM_EKG-->     Purchasing Group in Outline Agreement
M_RAHM_EKO-->     Purchasing Organization in Outline Agreement
M_RAHM_WRK-->     Plant in Outline Agreement
Q_TCODE     QM -->         Transaction Authorization
S_ADMI_FCD-->     System Authorizations
S_ALV_LAYO-->     ALV Standard Layout
S_BDS_DS-->     BC-SRV-KPR-BDS: Authorizations for Document Set
S_BTCH_ADM-->     Background Processing: Background Administrator
S_BTCH_JOB-->     Background Processing: Operations on Background Jobs
S_CTS_ADMI-->     Administration Functions in Change and Transport System
S_DATASET-->     Authorization for file access
S_DEVELOP-->     ABAP Workbench
S_DOKU_AUT-->     SE61 Documentation Maintenance Authorization
S_GUI-->                     Authorization for GUI activities
S_OC_DOC-->     SAPoffice: Authorization for an Activity with Documents
S_OC_ROLE-->     SAPoffice: Office User Attribute
S_OC_SEND-->     Authorization Object for Sending
S_PACKSTRU-->     Internal SAP Use: Package Structure
S_PRO_AUTH-->     IMG: New authorizations for projects
S_RFC-->                     Authorization Check for RFC Access
S_SCD0     -->                Change documents
S_SPO_DEV-->     Spool: Device authorizations
S_TABU_DIS-->     Table Maintenance (via standard tools such as SM30)
S_TCODE     -->                Transaction Code Check at Transaction Start
S_TRANSLAT-->     Translation environment authorization object
S_TRANSPRT-->     Transport Organizer
S_WFAR_OBJ-->     ArchiveLink: Authorizations for access to documents
V_LIKP_VST-->Delivery: Authorization for Shipping Points
V_VBAK_AAT-->Sales Document: Authorization for Sales Document Types
V_VBAK_VKO-->Sales Document: Authorization for Sales Areas

Have you executed a trace while a functional user executes the transaction code for the specific parameters? (i.e. document type). The trace will then show which objects are being checked; then look at the object documentation in txn Su21 to determine if there are any ways to restrict on the particular value; in some cases, if the authorization group field is being checked, additional configuration is needed in order to implement the security (Su21 will explain in detail for the particular object).

How to restrict LOV to a particular project type through form personalize.

Hi,
I got a requirement to restrict LOV to a particular Project type through form personalization in project accounting module. form name: PAXPREPR
i tried the below code in Builtin, but it didn't work
SELECT distinct PROJ.SEGMENT1, PROJ.NAME,
PROJ.DESCRIPTION, PROJ.PROJECT_ID
FROM PA_PROJECTS_ALL PROJ,
PA_PROJECT_TYPES_ALL TYPES,
pa_proj_elements ppe,
pa_proj_structure_types ppst,
pa_structure_types pst
WHERE PROJ.TEMPLATE_FLAG <> 'Y'
AND PROJ.PROJECT_TYPE = TYPES.PROJECT_TYPE
AND TYPES.CC_PRVDR_FLAG <> 'Y'
AND proj.project_id = ppe.project_id
and ppe.object_type = 'PA_STRUCTURES'
and ppe.proj_element_id = ppst.proj_element_id
and ppst.structure_type_id = pst.structure_type_id
and pst.structure_type = 'FINANCIAL'
and proj.project_type = 'GRANT'
order by PROJ.SEGMENT1
please suggest me where i went wrong.
Edited by: 925049 on Apr 3, 2012 2:49 PM

In the Control Data of FS00 there is field 'Authorization Group'
Please Create an Authorization Group for those user ID who can post TDS entries.
then Maintain this group for TDS related GL.
Then others will not able to post to this GL.
Regards,
Alok

Restricting Purchase order for a particular material type

Hi All,
How do I restrict a purchase order document type to be created for a particular material type.
For eample PO document type NB should allow to create for materials with the material type ROH only and restrict the other material types by issuing an error.
Many thanks in advance.
Regard,
Ravi

Hi Ravi,
This is not directly achievable in std. You will have to implement the check in a user exit, e.g. the BAdI ME_PROCESS_PO_CUST method PROCESS_ITEM.
But why this strange reqmt? Maybe there's another solution whuch would keep you in std?
BR
Raf

Restrict user SELECT query time on a particular VIEW

Hi - I am trying to restrict user SELECT statemnet time on a particular view.There is a user called ABC and he is accessing many objects in database.All SELECT statments are fine execept when he query a particular VIEW.That view SELECT causing performance problem.So I am trying to restrict the SELECT query time on a VIEW.
Can you please help me to achive this task through some SQL command like ALTER USER etc...
Thanks for your help.

user2538196 wrote:
Hi - I am trying to restrict user SELECT statemnet time on a particular view.There is a user called ABC and he is accessing many objects in database.All SELECT statments are fine execept when he query a particular VIEW.That view SELECT causing performance problem.So I am trying to restrict the SELECT query time on a VIEW.
Can you please help me to achive this task through some SQL command like ALTER USER etc...
Thanks for your help.It sounds like you are really trying to solve a performance problem with the view. I agree with Justin that the solution to restrict access to the view dynamically sounds unwieldy.
Consider tuning the view, or perhaps the query using the view. Post the view and see if anyone can help you tune it.

Transaction MB01 we are trying to restrict user to only run Document Type U

Dear All,
In Transaction MB01 we are trying to restrict user in Document Type in Purchase Order and restriction is only user can create Document Type UB (Stock Transport Ord. )
But I am create a dummy user and dummy role and assign MB01 to that role but it is not working I canu2019t understand why? What I can do wrong if nothing is wrong then what is the solution

Document types also use the "authorization group" concept. You do not grant access to them individually, but rather protect groups of them and then grant the access back again.
This means they are optional objects... --> which also implies that they are not the only objects...
If a document type is not protected by an authorization group, then there is no check... --> except for the mandatory objects such as the movement type to actually use the document...
This is normally explained, together with the customizing prerequisites, in transaction SU21.
Cheers,
Julius
ps: Please do not duplicate-post the same question. To keep the forums tidy, we reject such posts.

Task restricted to one particular user

Hi,
I just want to have a task restricted to one particular user only so that no other user can have access to that task.How is possible to restrict to one particular user only?I want that the other user cannot see the task given to him.
Thanks and Regards,
Manish.

Hello cselby11,
Text messages are an important form of communication and I definitely want to assist you in getting this resolved. Are you now using the stock application or a different third party application for messages? Is your girlfriend having an issue receiving text messages from other contacts or is it just from your number? Are you able to receive her text messages? What zip code are you located in? If you have a signature enabled on your messages please remove and retest. Let me know if you continue to experience difficulties so I can further assist.
DaisyP
VZWSupport
Follow us on Twitter @VZWSupport

MM-Restrict particular Mat type for specific Doc type

How to restrict particular material type in particular Purcharasing document type...

Go to OMS2 and Select Material type and in Internal / External Purchase Orders and in External Purchase Order tab Set the Value 0 No External Purchase Orders allowed and Save.
I dont know how far we can Control this for a Particular Document type.
Coz if you Set this this will be applicable to all Purchaisng Documents

For a particular document type posting using FB50/F-02 should be restricted

Hi all,
I have a requirement that, for a particular document type posting using FB50/F-02 should be restricted.
Any idea?
Thanks,

Hi,
what Exactly i need to write in validation is...
PREREQUISITE.
company code eq '0001' or '0002' or '0003'.
and doc type 'XX'.
CHECK
data: l_flag type c.
check action eq 'BU'. "only when clicked on 'post' in FB50
Import l_flag from memory id 'YMMID'.
if l_flag eq ''.
endif.
message
'Doc cann't be posted'.
Is it possible to write above code in validation?

BADI for MIGO for restricting User to entered other MVT types?

Hi All,
BADI for MIGO for restricting User to entered other MVT types?
I want to restrict some of user not to use 501 Movement type ..I already created a Ztable for checking User for 501 type.
Please let me know any Enhancement to be used to restrict user ?
Thanks and Regards
Steve

Hi Steave,
You can use this enhancement exit MB_CF001, this exit will be called every time before posting, you can use your logic in this exit. see its documentation first before implementing.
Regards
Ahsan

How to restrict users from printing documents and exporting to local file

Hi SAP gurus,
I have two questions.
1. How can I restrict users from printing a document? i.e. billdoc? I would like to know if I could block it though authorization. If yes, what auth obj to use?
2. How to restrict certain users from exporting to local file? the System> List>Save-->Local File. I have tried restricting it using auth object S_GUI but it seems it is only applicable to older versions of SAP. im on ecc6.
Thank you in advance.

Hi,
Check this:
Create your own gui status and attach it to the list in the event START-OF-SELECTION.
In the menu painter extra -> adjust template.
Make it a list status and you will see all the standard list options appear including list->download
Deactivate the ones you don't want.
If you just want to prevent users from downloading the list you can achieve this with authorization object S_GUI, activity 61. Menu option will still be there though.
Please note that if you remove authorisation for S_GUI activity 61 then all downloads will not be possible.
If you just want to disable downloads only for a particular report, you can try this test program:
Code:
REPORT ztest.
DATA: PROGNAME LIKE SY-CPROG value 'Z_CHECK_AUTH',
        FORMNAME LIKE SY-XFORM value 'F_CHECK_AUTH'.
START-OF-SELECTION.
    CALL FUNCTION 'SET_DOWNLOAD_AUTHORITY'
         EXPORTING
              FORM    = FORMNAME
              PROG    = PROGNAME
         EXCEPTIONS
              OTHERS = 1.
WRITE: / 'TEST'.
You also need this:
Code:
PROGRAM z_check_auth.
FORM f_check_auth USING pe_result TYPE i.
pe_result = 5.
ENDFORM.
Also have a look at the exit SGRPDL00.
Hope this helps you.
Rgds,
Raghu

Restrict User to particular Documant Type

Similar Messages

Maybe you are looking for