How to restrict change type in CC31

Hi ,
I have a new requirement in which I need to restrict change types in txn CC31 (Create ECR).onlya set of people should create a ECR with one change type and another set of ppl with another change type, but I am not able to find any auth object with the field CCART(Change types) to provide these restrictions .
Is creating a new auth object the only way ? please let me know if there is any other possibility  or any other auth objects which can be used for the same ?
Thanks,
Nanda

Fields of such types (e.g. document types, master data accounts, etc) are often not the same field name that you are looking for in an authorization object, but rather grouped in their master records and the authority-check is against the assigned group value.
More often than not, if no group value is assigned to a record then no check is made.
So what you can try to look for is a BEGRU type field of an object in the code and look to see where it is gettings its value from.
Might be worth a try...
Cheers,
Julius

Similar Messages

  • How to Restrict Material Type in MM01 ?

    *Hi experts,*
    *How to restrict material type ? i wanted to restrict the end-user not to access any other material types than Raw material,Semi-finished goods. it means when end user trying to create material then if he enters other than these two material types then he should get error saying that "your not authorized to select that xyz material type".*
    *I have tried to restrict the object M_MATE_MAR(Material Master : Material type) but am unable to do so. is there any other object which take care of Material types ? did i selected correct object or not??*
    *can anyone help out.*

    Hi,
    You have to make few configuration settings before you actually restrict at the object level. The solution is clearly discussed in the below thread:
    how to restrict material master by material type  t-code MM01
    Hope this helps!!
    Regards,
    Raghu

  • HOW TO Restrict Absence Type LOV Self Service in 12.1.3

    Hi All,
    Will someone please inform of whar is the package to use for this new feature restriction as stated below. Thanks.
    From new feature PDF 12.1.3:
    3.26.4.6. Restrict Absence Type LOV
    Prior to this release, all absence types created using Oracle HRMS are displayed to users in Self-Service HR. With this release, implementers can update ""a package"" to restrict the absence types that are displayed to users based on the business requirements. This feature ensures that employees enter only those absences for which they are eligible, and managers do not have to verify the validity of the absence type of employee requests.

    Apologies for the delay here.
    The package in question is hr_absence_restricted. You replace the Package Body of this package so that the function absences_restricted returns a comma-separated array of Absence Type ids that SHOULD NOT be displayed.
    For example,
    RETURN '123, 456, 789'
    Would prevent Absence Type Ids 123, 456 and 789 from appearing in the user's List of Values. This is supposed to be described in the following Oracle Article but it's not published:
    Oracle Article How To Restrict Absence Type LOV in Oracle Self-Service Human Resources (Doc ID 1122674.1)

  • How to restrict changing password for user ?

    Hi All experts ,
    We have created users . Users should not change their password without permission of Administrator . How to restrict them by setting Permissions / Authorizations ? 
    Thanks.
    KISHORE SATPUTE

    Hi,
    In "USER MAINTENANCE- SU01" --> in the "logon tab" there are 5 different "user type"
    1. dialog
    2. system
    3. communication
    4. service
    5. reference
    Kindly mention the function and role of all the above mentioned user types specifically and hows is one user type different from another.
    These are as follows:-
    1. Dialogue:-
    For this kind of users:-
    GUI login is possible.
    Initial password and expiration of passowrd are checked.
    Multi GUI logins are checked.
    Usage:- These are used for GUI logins.
    2. System
    For this kind of users:-
    GUI login is not possible.
    Initial password and expiration of passowrd are not checked.
    Usage:- These are used for internal use in system like background jobs.
    3. Communication
    For this kind of users:-
    GUI login is not possible.
    Users are allowed to change password through some software in middle tier.
    Usage:- These are used for login to system through external systems like web application
    4. Service
    For this kind of users:-
    GUI login is possible.
    Initial password and expiration of passowrd are not checked.
    Multiple logins are allowed.
    Users are not allowed to change the password. Only admin can change the password
    Usage:- These are used for anonymous users. This type of users should be given minimum authorization.
    5. Reference
    For this kind of users:-
    GUI login is not ible.
    Initial password and expiration of passowrd are not checked.
    Usage:- These are special kind of users which are used to give authorization to other users.
    Rewads point if helpful
    Thanks
    Pankaj Kumar

  • How to restrict  changes in Tabs: Defaults and Parameters in tcode:  SU3

    Good Morning Everybody.
    Do you know how to restrict End Users can change data stored in Tabs Defaults and Parameters of tcode: SU3.
    I was checking Authorization Objects related this transaction but I did not find a way to fix this issue.
    Thanks for your comments.
    Mauricio Cardozo.
    BASIS Consultant.

    I've been looking into this same question.  I don't think there's any way to protect individual user parameters, which is what we really wanted to do, but it is possible to protect the Parameters tab as a whole while still granting access to the Address and Defaults tabs (if desired).  SU3, which is usually given to all users, gives change access to all three tabs in the User Data, but to make it more fine-grained, as the last person said, take away SU3 and instead grant whatever combination of SU0, SU1, or SU2 makes sense for your organization.  SU0 gives access to the Defaults tab, SU1 to the Address tab, and SU2 to the Parameters tab.
    So, in your case, you would grant SU1 only, so users can change their name or phone number, etc, but not Defaults or Parameters.  They won't even be able to see defaults or parameters if you do this, though.
    I hope this helps.
    --Matt

  • 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

  • How to restrict Order types KA  and AB in script output form

    How to restrict KA AND AB order types in script output data is coming from  bkpf-blart .
    program is rfkord10.
    and form is f140_acc_stat_1
    in script output i dont want to  display KA AND AB order types ..
    data is coming from standard report.
    i copied form into zform.
    in output it is displaing all order types ..
    is there any solution to restrict above order types.

    Hi
    Check the data structures used in the script
    Since it is account statement of customer it uses the Tables BSID and BSAD in which the field BLART field is there whose values are KA and AB
    check for the structures which are used in the script and in them search for the field BLART in Se11 and accordingly keep the condition
    It will work
    Regards
    Anji

  • How to restrict changes of material quantity in Maintenance Order

    Hi Expert,
    How can i restrict the user to change the material and quantity in the Order's components tab.(IW32) Eg, not allow changes after RELEASE.
    Can the system keep track on all the changes for material number and quantity in the Orders?
    Please Advise
    Thank You
    Best Regards

    Hi,
        Better way is grey that tab after releasing the MO .. try BADI ;-IWO1_SCREEN_MODIFY Field Content and Display Modification
    You can also explore User exit ;-PPCO0023 : Check Changes to Order Components
    FM ;- STATUS_READ
    regards
    pushpa

  • IT0045 - How to restrict loan types to a maximum of 1 per employee?

    Hi Gurus - We have a requirement to restrict employees to only one loan type to be open at a time. This means if an employee has a Vehicle Loan currently running, he or she cannot create another one unless the previous one is closed.
    Setting the Time Constraint of IT0045 to "T" and then setting the individual Subtypes (Loan Types) to Time Constraint of 2 did not work. SAP apparently creates a unique sequential number for each loan type thus enabling more loans to be created for the same loan type. I guess this is the standard functionality.
    1. How can we prevent the user from taking more than one loan type?
    2. The ENDDA of the loan record may not reflect the correct loan schedule. Sometimes users create it a 31.12.9999. We need to check the payment in IT0078 I guess.
    The 45 infotype has this functionality for India. I am using International Payroll for Nigeria.
    Any help in this regards would be appreciated.
    Thanks
    Pramod

    Thanks Mohan. That constant is for India payroll only. I am using international payroll customized for Nigeria. SAP creates a unique sequential number for each loan you create and makes this number as part of the primary key thereby allowing any number of loans of the same type to be created. This is a default functionality. However SAP has modified this for India's IT0045. Do you have any other suggestions? Thanks once again.
    Regards
    Pramod

  • 'How to restrict change in Quantity/Price in saved Purchase Order in SAP B1'

    Dear All,
    How can I restrict a user from changing Quantity or Price in a saved Purchase Order in SAP B1 8.81 PL 0?
    Regards.

    Try This TN SP
      If @object_type='22' and @transaction_type='U'
    BEGIN
    If Exists (SELECT T0.docnum FROM [dbo].[OPOR] T0
    INNER JOIN [dbo].[POR1] T1 ON T1.DOCENTRY = T0.docENTRY
    WHERE     T0.DOCENTRY = @list_of_cols_val_tab_del)
    BEGIN
    Select @error = -1,
    @error_message = 'Update not possible'
    End
    End
    Regards
    Kennedy

  • Vl02n : How to restrict changed in Delivery after TO confirmation

    Hi,
    Standard behaviour of system is observed as follows.
    Delivery created --> TO Create --> No changes in Delivery --> TO Confirmed --> Delivery Item quantity can be increased or Line item/s or delivery itself can be deleted.
    Needs to be restriced Delivery Changes , once TO Confirmation is done.
    Can you please advice me, how to achive this.
    Regards,
    Manish Gupta

    Hi:
    I had a similar trouble in a 46B version, and if I remember well, the system when the TO was confirmed, the system display a warning message, no error message. I achieved display error message with two user-exits.
    1. In report MV50AFZ1, in subroutine 'USEREXIT_SAVE_DOCUMENT_PREPARE', you can write this tcode (it verify that the end user that manage deliveries don't delete items in delivery when TO is confirmed by users of warehouse, because they are not the same users).
    EHM 280403 (CHEQUEAR ANTES DE GRABAR) / do a check before save
    *break-point.
    verif si utilizamos sy-uname / check if I must use sy-uname
    CHECK sy-tcode = 'VL02N' OR sy-tcode = 'VL02'.
    TABLES: ltak.
    DATA: BEGIN OF iltap OCCURS 30,
    lgnum LIKE ltap-lgnum,
    tanum LIKE ltap-tanum,
    tapos LIKE ltap-posnr,
    posnr LIKE ltap-posnr,
    pquit LIKE ltap-pquit,
    nlpla LIKE ltap-nlpla,
    vorga LIKE ltap-vorga,
    nsola LIKE ltap-nsola,
    nista LIKE ltap-nista,
    END OF iltap.
    DATA: linpan TYPE i, "delevery line in dynpro-> PAI (xlips)
    lintab TYPE i, "delivery lines in table ->PBO (lips, linelips)
    ot LIKE ltak-tanum,
    confir LIKE ltak-kquit.
    DESCRIBE TABLE ilips LINES linpan.
    DESCRIBE TABLE xlips LINES lintab.
    *PASO A SELECT SINGLE: ACCESO + RAPIDO
    SELECT SINGLE tanum kquit INTO (ot, confir) FROM ltak
    WHERE vbeln = xlips-vbeln.
    *ENDSELECT.
    IF sy-subrc = 0 and confir = 'X'.
    SELECT lgnum tanum tapos posnr pquit nlpla vorga nsola nista
    INTO CORRESPONDING FIELDS OF TABLE iltap FROM ltap
    UP TO lintab ROWS
    WHERE lgnum = '151'
    AND tanum = ot
    AND pquit = 'X'.
    *DESCRIBE TABLE ilips LINES linpan.
    *DESCRIBE TABLE xlips LINES lintab.
    IF lintab > linpan AND linpan > 0.
    LOOP AT xlips.
    READ TABLE ilips WITH KEY posnr = xlips-posnr
    BINARY SEARCH.
    IF sy-subrc NE 0. "es la posicion eliminada (item deleted)
    READ TABLE iltap WITH KEY nlpla = xlips-vbeln
    posnr = xlips-posnr
    BINARY SEARCH.
    IF sy-subrc = 0
    AND iltap-pquit = 'X'
    AND iltap-nsola EQ iltap-nista
    AND iltap-vorga NE 'ST'
    AND iltap-vorga NE 'SL'.
    message e027(ZB) WITH ot.
    ENDIF.
    ENDIF.
    ENDLOOP.
    VERIFICAR SI SE MANTIENE
    ELSEIF lintab < linpan.
    message e028(ZB) WITH ot.
    ENDIF.
    ENDIF. "sy-subrc
    2.Enhancement V50PSTAT, FM 'EXIT_SAPLV50P_001' in the include 'ZXV50U07' you can write this tcode (it check that the end user in a delivery with a TO confirmed cannot change the quantity to avoid problems):
    INCLUDE ZXV50U07 *
    EHM ABRIL 2003 : IMPEDIR Q MODIFIQUEN ENTREGAS CON OT CONFIRMADA
    *BREAK-POINT.
    CHECK sy-tcode = 'VL02N' OR sy-tcode = 'VL02'.
    EHM 020703 (CHEQUEO SY-UCOMM DISTINTO A WABU_T -> CONTAB. SM)
    CHECK sy-ucomm NE 'WABU_T'.
    FIN VERIF. (Q NO VERIFIQUE A EXPEDICIONES AL IMPRIMIR EL ALBARAN)
    TABLES: lips, ltak, ltap.
    DATA: BEGIN OF tltap OCCURS 30,
    lgnum LIKE ltap-lgnum,
    tanum LIKE ltap-tanum,
    tapos LIKE ltap-posnr,
    posnr LIKE ltap-posnr,
    pquit LIKE ltap-pquit,
    nlpla LIKE ltap-nlpla,
    vorga LIKE ltap-vorga,
    nsola LIKE ltap-nsola,
    nista LIKE ltap-nista,
    END OF tltap.
    DATA: ordcar LIKE lips-vbeln,
    ocposi LIKE lips-posnr,
    occant LIKE lips-lfimg.
    DATA: ot LIKE ltak-tanum,
    confir LIKE ltak-kquit.
    CLEAR: occant, ot, confir.
    SELECT lfimg INTO occant FROM lips
    WHERE vbeln = is_lips-vbeln
    AND posnr = is_lips-posnr.
    ENDSELECT.
    INCIDE A lkat-vbeln ??
    SELECT SINGLE tanum kquit INTO (ot, confir) FROM ltak
    WHERE vbeln = is_lips-vbeln.
    ENDSELECT.
    (SE AÃu2018ADE EL SINGLE PARA HACER MAS RAPIDO EL ACCESO A LTAK)
    IF sy-subrc = 0.
    SELECT lgnum tanum tapos posnr pquit nlpla vorga nsola nista
    FROM ltap
    APPENDING CORRESPONDING FIELDS OF TABLE tltap
    WHERE lgnum = '151'
    AND tanum = ot.
    EHM 280403: OJO: SOLO PARA LAS POSICIONES DEL PEDIDO
    CONFIRMADAS. LAS DEMAS SE PUEDEN MODIFICAR
    VERIFICAR Q NO VIENE LA OT DE MAS DE UNA ENTREGA
    READ TABLE tltap WITH KEY nlpla = is_lips-vbeln
    posnr = is_lips-posnr
    BINARY SEARCH.
    IF sy-subrc = 0
    AND tltap-pquit = 'X'
    AND tltap-nsola EQ tltap-nista
    AND tltap-vorga NE 'ST'
    AND tltap-vorga NE 'SL'.
    IF occant NE is_lips-lfimg.
    MESSAGE e025(ZB) WITH ot.
    ENDIF.
    ENDIF.
    ENDIF.
    *DATA:
    One suggestion: be careful with the performance with the SQL on tables LTAK and LTAP if you have a lot of records in this tables, because you could have an expensive performance of tcodes VL02N, VL02 and so on. You can avoid it with secondary indexes (if you can growth in DB) or archiving data of LTAK, LTAP with object RL_TA (if deliveries are loaded in a reasonable period).
    I hope this help you.
    Regards.
    Eduardo
    Edited by: Eduardo Hinojosa on Sep 3, 2009 5:01 PM

  • How to restrict change to plant specific data in MM01 and MM02 transaction.

    Hi Experts,
    The requirements is to restrict the plant specific data change in one system. As of now we have 2 different system lets say sys-1 and sys-2. our requirement is if at all any of the users are trying to change/create the material in Sys-1 they should be only able to update basic information and parts regional information/global informations only in sys-1.
    Do we have any option in customizing?
    If not then what would be the way to achieve this?
    Please help.
    Thanks!!!!
    Rajesh.

    Hi,
    Please refer the below link it may help you..............
    Authorization object for label Data view in mm02

  • How to restrict change/creation of Infotype record after termination action

    Hi All,
    Based on my client requirement, we have to restrict any change or creation of certain infotypes after performing termination action.
    For Ex:- Suppose termination date is 01.01.2008. End user should not able to change or create any new record for infotype 0001, 0008 and 0016 after 01.01.2008.
    This is very critical. Request your valid input ASAP.
    Thanks in advance.
    Regards,
    Purnima

    Hi Sreenu,
    Thanks for your valid input.
    I tried by giving "EDQ". Then I got below mentioned error while performing termination action.
    Error:- "Status EDQ of the user interface MP000100 missing"
    Can you help please?
    Regards,
    Purnima

  • How to restrict transaction type in customized activity pop-up

    We have created a custom workcenter link for search enhancement of activities. We copied the work center link and are calling the same component as in std search but a different customized configuration with added and deleted fields in search criteria. This works fine. Now the requirement is to restrict the 'transaction types' available when we click on the 'new' button in the new custom activity search page. As this pop-up emanates from the std component, it can not be functionally configured (because that would restrict the 'transaction types' while creating new activity in std componnet) but should be technically handled. Please advise.

    Hi Amar,
    Solution here is to let the framework know who is caller ?
    That is, when pop up is opening, you have to put a code in this pop up view to understand who is invoking this pop up , Is it the search page of std. component configuration or is it the custom search page configuration ?
    So have a static attribute in some Z class, you can use your IMPL class also for that matter, Now whenever you know that its custom config i.e. in DO_CONFIG_DETERMINATION, read the role key( i assumed that you have a role key for your custom config)
    and if its custom role key, then set this static parameter say ZCUST_CONFIG = abap_true else abap_false (this is must to reset it using else as this is static attribute )
    Now, in your pop_up view, read this static attribute as XXXX_IMPL=>zcust_config , and if true, then you know that the pop up is invoking from custom config, so do the coding to remove the unwanted transaction types.
    and you are done !!
    Hope it helps you.
    Thanks & Regards,
    SUCHITA

  • How to restrict changes to Vendor Master withholdind tax data

    Dear Experts,
    I want restrict users to make any changes to withholding tax data in vendor master,please suggest solution
    Regards,
    Varun

    Hi
    You can restrict the user with authorization control. Take the basis help and create the seprate role for Change Vendor master WHT
    And assign to all the user.
    regards
    Prasanna

Maybe you are looking for