User should not be able to change the payment terms

Dear All,
My issue is that user should not be able to change the payment terms in any of the document.I have tried to do it through authorization but it is not working out.
Mona.

Dear Mona,
This may only be done through SP_Transaction_Notification.
Thanks,
Gordon

Similar Messages

  • How do I disable editing of pages in author mode? User should not be able to edit content . Can this

    How do I disable editing of pages in author mode? User should not be able to edit content . Can this be customized on component basis?

    You have to remove modify rights for those users on that page. Component basis is possible but will create ACL complications. Please check http://dev.day.com/docs/en/cq/current/developing/components/boilerplates.html for that.
    Yogesh
    www.wemblog.com

  • How will I block/restrict the user to change the payment term in FBL5N?

    Hi All,
    How will I block/restrict the user to change the payment term in FBL5N????
    I have tried on following objects:
    F_BKPF_BLA
    F_BKPF_BUK
    F_BKPF_GSB
    F_BKPF_KOA
    F_IT_ALV
    F_KNA1_BED
    F_KNA1_BUK
    F_LFA1_BUK
    S_ALV_LAYO
    But, not succeeded.
    =>Actually user runs FBL5N, double click on a record then click on Change icon.
    =>Change Payment Term.
    Please reply ASAP. Point will be awarded.
    With Best Regards
    Dharmendra

    Hi Dharmendra,
    Please set an authorization trace in ST01 and then ask the user to execute the transaction and the steps on the same application server as the o ne on which the trace has been set (valid in case we are talking about mutiple application servers for same <SID>). After this is done switch off the trace,list it and fill all the authorization objects. That might give you the perfect idea.
    Regards.
    Ruchit.

  • Do not change the payment term created a Sales Order with reference

    Hi Gurus,
    Do not change the payment term created a Sales Order with reference to a contract where the payer of the change in Sales Order.

    Hello ,
    As per my understanding , you do not want the payment terms to be changed even if the payer partner function is changed ,
    as standard sap redetermines the payment terms with change in partner function, you may use the exit
    USEREXIT_MOVE_FIELD_TO_VBAK- header level
    USEREXIT_MOVE_FIELD_TO_VBAP- Item level
    in this you could write a small code which will not change the payment terms when payer is redetermined
    hope this helps
    Thanks
    akasha

  • Issuing a warning message while changing the payment terms in FB02

    Hi Gurus,
    The requirement is as follows:
    For a particular payment terms meant for customer only when we change the payment terms in FB02, the system should give an warning message.
    For example - A customer has the payment terms 0001in his master data and thus in the accoutning document as well after releasing billing to accounting. An user wants to change the payment terms to 0070 being in FB02. As and when he puts the payment terms 0070, the system should give an warning meesage saying 'bla bla bla ........' or the same message at the time of saving the document.
    How to make this possible. Please help.
    Rgds,
    BABA

    Mr. Tiwari,
    This is the standard feature of SAP!!!  You get below messages
    1)
    Net due date on 05.10.2007 is in the past
    Message no. F5149
    Effects on Customizing
    You can define when this system message is to be issued in accordance with your requirements.
    You do this in Customizing as follows: Cross-Application Components -> Bank Directory -> Change Message Control.
    The application area and message number can be taken from the technical documentation.
    2)
    Net due date on 05.10.2007 is in the past
    Message no. F5149
    Effects on Customizing
    You can define when this system message is to be issued in accordance with your requirements.
    You do this in Customizing as follows: Cross-Application Components -> Bank Directory -> Change Message Control.
    The application area and message number can be taken from the technical documentation.
    Terms of payment changed; Check
    Message no. F5231
    Effects on Customizing
    You can define when this system message is to be issued in accordance with your requirements.
    You do this in Customizing as follows: Cross-Application Components -> Bank Directory -> Change Message Control.
    The application area and message number can be taken from the technical documentation.
    Regards
    Santosh Hegde

  • Any pointer to look into, when buyers cannot change the payment terms

    Any pointer to look into, when buyers cannot change the payment terms on the POs due to the error u201CExpected/Overall value should be equal or greater than invoiced amountu201D
    A thought process to look around, to investage this issue is appreciated.
    Thx/RICK

    Rick,
    this message may be due to the user trying to change a Purchase order item payment terms when there is already a blocked supplier invoice registered for the item.  The vendor invoice payment terms normally override the PO payment terms.  Users sometimes think they can speed up payment to a vendor by changing the payment terms on the PO.  This can only be done before an invoice is registered and the PO term can be overridden at invoice entry time in any case.
    Have a look at the terms on any associated invoice and the vendor record for the Purch org.  
    You may also want to have a look at your business process for blocked invoice resolution.
    If the user wishes to speed up payment of an invoice they need to contact the users who are responsible for the vendor payments.  We call them AP staff in our org - stands for Accounts Payable.
    Hope this helps
    Allen

  • User should not be able to import a request.

    Dear Forum,
    We have a role created with all the transaction (*) given to a user.
    We want to revoke/restrict the authorization to import a request.  User be able to create/edit/release the request but should not be able to import.  This should happen without changing to existing (*) but at the same time user should not able to import.
    <removed_by_moderator>
    Regards,
    DD
    Edited by: Julius Bussche on Feb 18, 2009 10:48 AM

    > And in the new role you can restrict the user.
    I suspect the how was the original question. S_TRANSPRT is the (already given) answer. Deriving will do nothing for that object as not one of its fields is organizational. Besides that, restricting some more objects to make sure the user cannot create and/or use any workarounds is essential to make this work properly.
    The additional request This should happen without changing to existing (*) scares me a bit. Why do these users need over 70000 transactions?

  • User should not be allowed to change plant in SO once PR/PO is created

    Hi SAP Gurus,
    User has created the Purchase Request & Purchase Order for a sales order line item. After PR/PO creation user is able to change the plant. We need to stop that is there any standard configuration or setting by which i can stop the user to change the plant.
    System is giving the error if i am trying to delete the item since the PO exist but not stoping me to change the plant.
    Thanks
    Surender

    Hi,
    Standard setting is not available.You need to write the specific code in Sales order change exist by checking the VBEP -schedule line table where the PR exists.so for the line item the Plant should not be changeable.
    Sales Order Change exit the following requirement has to be incorporated.
    You can find the user exits in SPRO-Sales and DistributionSystem ModificationsUser Exits--User Exits for Order Processing.
    Regards,
    Saju.S

  • User should not be able to edit characteristics Value

    Hi Friends
    I have requirement where in a user creates a document with Two characteristics assigned to that Document.
    Say CHAR1 and CHAR2.
    When he creates DIR , He assigns value to these characteristics
    CHAR1 = 666454
    CHAR2 = 55333
    No I want No other user to be able to change the values assigned to both CHAR1 and CHAR2.
    Can this be possible.
    With Regards
    Mangesh Pande

    Hi Mangesh,
    I think the easiest way to find an authorization object which prevents users to edit characteristic values would be to made an authorization trace in transaction ST01. For further information please see the following link:
    http://wiki.sdn.sap.com/wiki/display/PLM/AuthorizationTrace-+ST01
    This trace lists all checked authorization objects and you should be able to identify a suitbale object for restricting edit permission for classification values.
    Best regards,
    Christoph

  • Release retriggering while changing the payment terms

    Dear All,
    After releasing the purchase order if anybody Changes then payment terms in me22n, release should retrigger how to configure this process
    Regards,
    Vijaybhaskar

    Hi,
    You have two option to achieve this no.1 through user exit
    refer this link
    Release strategy for PO on Payment terms..
    No. 2 through version management
    refer this link
    Restricting Purchase order's payment terms change authorization

  • User should not be able to cancel Proforma invoice if Excise Invoice Exist

    Dear All ,
                     I have a requirement that i have a performa invoice for which a excise invoice is created and then when i go to VF02 and check on Complete the i want to check whether the exicise invoice is cancelled or not . Can Anybody help me out with the exit name in which i can apply the check.
    Regards
    Shankar
    Edited by: Shankar  SB on May 10, 2010 5:38 AM
    Edited by: Shankar  SB on May 10, 2010 5:41 AM
    Edited by: Shankar  SB on May 20, 2010 3:13 AM

    Hi,
    Standard setting is not available.You need to write the specific code in Sales order change exist by checking the VBEP -schedule line table where the PR exists.so for the line item the Plant should not be changeable.
    Sales Order Change exit the following requirement has to be incorporated.
    You can find the user exits in SPRO-Sales and DistributionSystem ModificationsUser Exits--User Exits for Order Processing.
    Regards,
    Saju.S

  • HT5552 every time i try and make a purchase on itunes it keeps saying the payment is not accepted and to change the payment option. I know my personal bank card has the funds so why doesn't the payment go through?

    i am trying to make a pruchase but it won't accept the payment option. I don't know while and i know my card has funds in it. what might be the cuase of this?

    You need to contact Apple to get the questions reset. Click here, phone them, and ask for the Account Security team, or fill out and submit this form.
    (94948)

  • Manuals users should not be able to submit a concurrent program at a specific time frame:

    Hi
    Please let me know is it possible to restrict some users to submit a Concurrent program during a selected time frame .
    Eg we have an issue in which Process Lockboxes concurrent Program is submitted by the batch user and is also by the Users manually from Front end .What I want is that during a particular time frame everyday say from 12:00 AM to 6 PM I want to restrict manual users to submit this program ,whereas the Program can be submitted by the Batch user any time  .
    Please let me if its possible to achieve this and how .
    Thanks
    Rishabh

    Please don't post duplicates -- restrict user to submit concurrent Program
    Continue the discussion in your original post.
    Thanks,
    Hussein

  • User should not be voiding the dispute created by other User

    Hi,
    I having an Issue at my work place.I have got a Requirement from the Finance Functional Folks that the user should be able to create the dispute case and also void the case created by him.But the user should not be able to void the dispute case created by the Other user.
                                           As of now when I am testing the user is able to void the dispute case created by him and also void the dispute case created by other user.So now I am trying to restrict so that user should not be able to void the dispute case created by other user.
    In the Roles Built at work place I have fdm_coll01-collections Management and also udm_dispute-dispute manamgement T-codes built in One Role.can any one of you let me know at which authorization object this can be restricted as I am having a hard time trying to find out.
    In Ideal SAP World what my idea was a Dispute case created by the user in Production should not be allowed to void the dispute case.so creating a dispute case and voiding a dispute case should be treated differently and should be done by different persons in an organization.

    In Ideal SAP World what my idea was a Dispute case created by the user in Production should not be allowed to void the dispute case.so creating a dispute case and voiding a dispute case should be treated differently and should be done by different persons in an organization.
    So why not talk back to your FI Folks. Also check with your Compliance Team.
    But anyhow, I do not see in the real world a conflict of duties by giving access to both creating a Dispute and voiding a dispute and more over voiding a dispute is considered critical since it would allow to Release Blocked Orders.
    But the user should not be able to void the dispute case created by the Other user.
    If every transcation and conversation with a Customer is recorded in the Collections Management system, I do not see a requirement for the same Team Member having access to close a dispute created by other user. 
    AB.

  • Not allowing changes to payment terms after the AR document is released to accounting

    Hi,
    Anyone know the best way to not allow a user to change the payment terms after the AR document has been created in AR? This is affecting aging because users are changing the payment terms without permission. What is the best way to control that?
    Thank you.
    AK

    Hi A K
    Frequent change in payment terms is something business should introspect. Payment term is decided and agreed upon with customer/vendor during the initial stages.
    However from IT perspective, it can be controlled keeping some system controls.
    1. Limit the Customer master change transaction to very limited users or to a manager. There should be internal approvals by management for business to make a change. Bring this into force.
    2. Regularly run the customer master change reports and provide the trend to management to restrict or limit the changes.
    3. Use Change Message control for master data by providing necessary warnings or error messages when master data is changed.
    4. In  the sales order level, there is every possibility to change the payment term. Based on the user authorization get the payment term field greyed out and provide change access to accounting or to a specific user upon approvals. This is a bit complex process but I feel this brings up controls and stops the process from exploitation.
    5. Also activate 'Sensitive fields' KNB1-ZTERM for payment term field in customer master. This brings up another layer of confirmation of change by other users.
    6. Another back route, not recommended in all cases, is to subsititute the required payment term during accounting document posting.
    Hope it helps.
    Thanks,
    Sekhar

Maybe you are looking for