Restricting Document type in F-63

Hi All,
        Please help as this is required to restrict Document Type in F-63 ,our requirement is that we want to create some new roles and in that we can only process for one Document type say "ZA" only and that document type shud be by default set in the F-63, i know the object responsible for this is F_BKPF_BAL with actvt 01,02,03,04,06.08,10,22,43,77 but this object is not maintained in F-63 .
Please help with the max possibile way to restrict the same along with the actvt field . Or is there any other way to achieve the goal.
Thanks,
Chandresh

As you Pointed out the Object F_BKPF_BLA is the one which Check/Maintaines the Accounting Document: Authorization for Document Types
The object consists of the "Authorization group" and "Activity" fields. The authorization group can be freely defined by the user. You take the possible input values for the "Activity" field from table TACTZ.
If you want to use this authorization, proceed as follows: Defined by SAP
Enter an authorization group for the document types that are to be specially protected.
Define the authorization that you want to assign to selected employees, in which you list the authorization groups and the activities allowed.
Allocate this authorization using the corresponding profile.

Similar Messages

  • How to block or restrict document type

    Hi friends
    How to block or restrict document types .
    My Business people will not use document types in feature

    Hi,
    The documentation about the authority check within posting is given in the online documentation for the posting ta eg. FB01:
    Perhaps you would like to read the documentation from IMG on the authorization:
    Financial Accounting > Financial Accounting Global Settings > Document > Document Header > Check Display Authorization for
    Document type
    Defining Authorizations for Document Types
    Use
    You can define a special authorization for every document type. To do this, you need to determine what document types in which
    form employees are allowed to process. Authorizations are checked for the following activities:
    Posting documents
    Document display and line item display
    Changing documents
    Programs that evaluate documents.
    The system does not check the authorization for document types that are not assigned an authorization group.
    Procedure
    In Customizing for Financial Accounting, carry out the activity Maintain Enter an authorization group in the document type. You then assign autho For each document type, you can specify whether users are required to enter.
    The same for check of the authorizations of gl accounts.
    PLease check in OMR4 and in OBA7 that for the document types the athorizations groups are maintained.
    F_BKPF_BLA Accounting Document: Authorization for Document Type
    F_BKPF_BES Accounting Document: Account Authorization for G/L Account.
    For example:
    The transaction FB01 includes the above objects - you can see this in Trx. SU24, also as transaction F-02 is a parameter transaction with the original being FB01 these objects would be valid for F-02 also.
    Please also refer to the following NoteS
      150496     F_BKPF_BLA: Authorization for document types
      198238     FI reporting: Authorization check for documen
    I hope this helps to solve the problem.
    Regards
    Ravinagh Boni

  • How to restrict document types in hierachy

    Hi
    My scenario is
    For DIR of document type A only DIRs of document type B and C should be attached in the document hierarchy. How to restrict the user from attaching other type of documents?
    What will be the best solution for this scenario?
    Thanks in advance
    Prasad K

    Hi
    Plz
    Any inputs on this?
    Regards
    Prasad

  • Setting quotas & restricting document types

    I have two administration related queries (coming from my customers):
    1. How does an administrator set email quotas for its users in Beehive? Also related to the same, the administrator may want to set different quotas for different user types: for example: 100MB for regular users, 150MB for sales, 200MB for managers, etc. Is it possible to achieve this in Beehive? and how?
    2. Is it possible for the administrator to restrict certain document types as attachments in the email. For example the administrator may want to restrict users from attaching video format files (.wmv, .avi, etc) as attachments.
    Dhiraj Bhandari
    Sales Consultant, Bangalore, India
    <<<removed because of privacy reasons>>>
    Edited by: Ruben de Vries on Mar 12, 2009 3:42 PM

    Please don't post privacy sensitive information on public forums.
    For Oracle employees, please use the appropriate [internal forums|http://myforums.oracle.com/jive3/category.jspa?categoryID=735] .
    But did you already try reading the [Beehive docs|http://www.oracle.com/pls/bee1/search?remark=quick_search&format=ranked&word=quota] ?

  • Problem with document type in ME51N

    Hi all,
    ME51N transaction will pickup NB document type by default. We can change the default document type by using personal settings in ME51N. But, can we restrict document type using ABAP development irrespective of default settings. Suppose NB is default doc type. If we open ME51N, some other doc type should come other than NB. Is it possible by ABAP development. Its very urgent. Please help me in  this.
    Thanks in Advance,
    Siva Sankar.

    Siva Sankar
    You may use Field Exit to do this enhancement. You can create fieldexit from report RSMODPRF.
    In order to use field exit check/activate Profile Parameter abap/fieldexit using t code RZ11.
    Thanks & regards
    Amol Lohade

  • Reporting issue on document types

    Hi experts,
    We have an requirement in the report which is based on a gl cube,
    where we need to show all the accounting documents of type DZ and the reversals of only these documents ie RD of only DZ.
    RD Documents are not only the reversals of DZ document they can also be the reversals of other document types.
    So how to show only RD document for DZ document types.
    Please help me on this issue.
    Regards,
    Nishuv.

    Hi Ram,
    Thanks for the reply....
    So now i need to create a query which brings only accounting documents of document type DZ.
    And then create a new query in which i need to create a new variable for accounting document no with replacement path and should give the first query as replace the query with first query result.
    And also in the second query i need to restrict document types with DZ and RD.
    Is this correct ?
    Please let me know....
    Regards,
    Nishuv.

  • Restriction of GR & IR for PO with specific document type

    Hi,
    How we can restrict doing Goods Receipt & Invoice Receipt for a Purchase order, instead they do the payment directly for the Purchase order item in FI. We need to restrict GR & IR for PO with particular document type.
    Regards,
    Srinivas

    Hi,
    Yes i do feel the same. Normally if a PO is created means system expects a GR and and IR .If you do not expect the ir means it is a free entry.
    But however you can control the GR / IR through account assignment .please check the account assignment definition at SPROMMPUR-Account assignment-AAcategory.
    Once the PO is created with account assignment the procurement is for consumption  (non stock)
    if it is a stocked procurement system will check the GR/IR indicator in the PO.
    When a PO is created in MM module and the cycle is not completed , it will always show as open PO.I think the context for FI direct posting will be differrant.
    Regards,

  • 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).

  • Sales document type restriction to create sales order

    Hi Frinds,
    My client has one requirement ...they have different sales document type. For sales document type  free of charge delivery they want only some authorised person should be able to create sales order. Is it possible to set the authorisation to create sales order according to sales document type.
    Regards
    SV

    Yes, 
           As already suggested, it is very well possible to restrict the user for the use of certain sales document type from basis.
    & to add to the above,
    Create Z* table with Sales Org + Doc type = UserID.
    call this table in VA01 transaction & write piece of coding , if current USerID have entry in this table with the said combination - should not allow to proceed further.
    without any basis involvement also you can ahieve your requirement.
    Note: Sales Org is used for validation purpose only.
    Regards,
    Reazuddin MD

  • BASIS--to restrict authorization for a PO document type & 122 movement type

    Dear All,
    Plz guide me how to restrict authorization for a PO document type & for a movement type 122 i.e. for eg. if a user has authorization for PO document type IC then he should not be able to rum movement type 122 for any T-code he runs.
    Thanks in advance
    Arpit
    Basis

    Hi,
    Your request was not too clear to me.. As per my unde
    Here is some details of Authorization object related to Purchase Order:
    Document Type in Purchase Order( M_BEST_BSA )
    Purchasing Group in Purchase Order (M_BEST_EKG )
    Purchasing Organization in Purchase Order  (M_BEST_EKO)
    Plant in Purchase Order  (M_BEST_WRK )
    Document Type in Outline Agreement (M_RAHM_BSA )
    Purchasing Group in Outline Agreement (M_RAHM_EKG )
    Purchasing Organization in Outline Agreement ( M_RAHM_EKO )
    Plant in Outline Agreement ( M_RAHM_WRK )
    This can be helpfull to you to restrict authorization to PO..
    In Organization Level, it can be restricted by Purchasing group, Purchasing organization and plant..
    Regards,
    Sandip

  • Document type restriction

    To restrict access to specific document type (BLART) on  transactions FBL5N and FB03, we applied the following settings:
    - Assign authorization groups (BRGRU) to document types in OBA7
    - Assign authorization groups (BRGRU) to roles in PFCG
    - Assigning users to the appropriate roles
    but all users can view all types of documents!
    how I should proceed to restrict access to particular types of documents for users?
    Many thanks in advance!
    Ismail

    Hi,
    Please do to the following steps :
    1. Go to SE16
    2. Enter table name as TBRG
    3. Click on Create
    4. Enter Object F_BKPF_BLA
    5. Enter Value - this will be yours authorization object value.
    6. Enter Description
    7. Save
    8. Go to transaction code PFCG
    9. Create a new role
    10. Click on
    11. Enter Object F_BKPF_BLA
    12. Enter Value - this  value is the value created by you in table TBRG.
    13. Enter Activities
    14. Generate .
    15. Assign role to users.
    Please remove authorization object F_BKPF_BLA from all the existing roles before assigning newly created role to users.
    We hope your problem gets resolved by following this steps else revert.
    Regards,
    Tejas

  • Document Posting restriction using posting key,document type combination

    Hi
    We have a authorization restriction issue using posting key&document type&Accoutn type  combination.
    Requirement is
    User A should be able to post to vendors only for particular posting key&document type.He should be able to post to with any other posting keys and document types to vendors.
    We have tried with document type authorization object/vendor authorization objects from user profile but it does,t work.
    can any one suggest some way please/
    r
    regards

    Hi
    I think you should be able to achieve the same through Validation rule:
    Prerequisite
    Document Type - XXXX
    Check
    User name = 123 and Posting Key = XX
    You can set a an error messsage which would be bleeped when the check fails
    Regards
    Sanil Bhandari

  • Document type restriction in GL posting.

    Dear All,
    How can i restrict a GL account to have only one specific document type documents. I mean only one document type should be posted to that GL.
    It should not contain any other document type other than specified one.
    I know this is possible through validation. But it is not checking if i write validation in OB28. If possible can any one guide me in writing the validationIs there any other way to restrict
    a GL for only one document type.
    Please reply...thanks in advance.
    sapuser.

    Hi,
    To make the GL account specific to a particular document type, you can write the validation as below:-
    Step 1:-
    Create a message ID via transaction code SE91 for message class /EACC/MSG/ACC_COMP as you want to display to user.
    Step 2:-
    Go to transaction GGB0 and create the validation step at complete document level in Financial Accounting as below:-
    Pre Requisits:-
    BKPF-BLART = 'KR'. (example KR doument type)
    Check:-
    BSEG-HKONT <> '1234567890' (the account no. you want to get posted only with the document type given above.)
    Message:-
    Message created in step 1 as error message.
    Step 3:-
    Please also check that this validation has active status (Status=1) at line line item level (level 2) for your company code in transaction OB28.
    Regards,
    Gaurav

  • Document Type Restriction in cFolders

    Hi all,
    We have implemented cFolders 4.0 in our project as a document repository. We have a requirement to allow users to upload certain document types only (e.g. .doc, .xls). Is this configuration available out of the box? Otherwise, how do we customize the standard cFolders configuration to enable this restriction?
    Thanks in advance.
    Regards,
    Alvin

    Hi ,
    Iam learning DMS,CProjects now.Can you send me some study material for CFolders,DMS & CProjects.Pls send it to [email protected]
    Thanks & regards,
    Sudhakar

  • Restriction of Document type

    Dear Sir
    we have created document type by one user and i want to restrict for other user for change in that document type with user specific
    eg. user 1 created document with doc type dev and save
           user 2 has creation authorisation of save doc type but he/she should not have authorisation to edit user 1 docue

    If I have understood your requirement correctly, you want to say that:
    There are two users say, USER1 & USER2 & both use same document type, say DC1.
    For example, USER1 has created a DIR with doc. type DC1. And you want to restrict changing of this DIR by USER2 & viceversa.
    If this is your requirement, then what you can do is, you can utilize the "Authorization Group" functionality in DMS.
    Create two different Authorization groups for USER1 & USER2. For example, create Authorization group AUT1 for USER1 & Authorization group AUT2 for USER2.
    In roles & authorizations, you create two different roles. For USER1 you assign the Authorization group AUT1 in object BEGRU
    For USER2 you assign the Authorization group AUT2 in object BEGRU.
    Once you do this & assign roles to respective users, USER1 can create the DIR with doc type DC1 & enter the Authorization group AUT1 & saves it. Now even if USER2 tries to open it, he/she can't access it, since her roles do not have authorization for the Authorization group AUT1.
    The same thing works for USER2. Say, if USER2 creates DIR with Authorization group AUT2, USER1 can't access it.
    This is the only way, that you can control it.
    Otherwise, you may need to create two different Document types for USER1 & USER2 depending on your business requirement.
    I hope this helps.
    Regards
    Amaresh Makal

Maybe you are looking for