Without result recording closing system should not allow for usage decesion

Hi
without result recording closing system should not allow for usage decision.I think it is possible through user status. Please tell the procedure .
Thanks and regards,
vairavan

Dear vairavan,
You can check for the authorisation object.I can't remember that authoriation object right now.But surely you can restrict that with authorisation object.
Anyone knows the authoristaion object.
Regards,
Sunil Patil

Similar Messages

  • With out goods issue for order system should not allow for order confirmati

    Dear all
    with out goods issue system should not allow for order/operation confirmation.
    how it is possible.
    Regrads
    Srinivas

    Dear ,
    In some cases we required to do confirmation or TECO without GI .
    We can change it as per req using user exit
    Regards,
    Ishwar

  • QA32: Without going in Inspection lot stock screen system should not allow for UD

    Hi
    At the time of UD "without going in Inspection lot stock screen system should not allow to save the UD".
    Please suggest how to restrict.
    Regards
    Ashish

    Please go through the below link & with small changes you can fulfill  your requirement using user profile
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/601c82e3-b743-2c10-dbb6-ed4c00167157?QuickLink=index&…

  • System should not allow PO beyond Maximum price.

    Gurus,
    My requirement is as follows:
    I have a material which has a Max Purchase price of 100.Now whenever I create a PO system should not allow me to create a PO beyond 100.
    Pl suggest a way out
    SN

    Hi,
        According your rquirement while creating  PO , material price ( that  should be a condition based) does not cross your price limits,
    In PO we have number of conditions like
    Gross price
    Discounts
    Surcharge
    etc........so on
    for each condition type we can give upper limit while maintaining Material-Vendor info record(vendor -material specific).for this combination only it's works.
    Regards,
    Venkat

  • System should not allow to delete PO line Item after GR/IR

    Hi,
    I am working on a SAP Retail Implementation project.
    Currently the system is allowing us to delete the PO line items after doing GR or IR against that PO line item. But the clients requirement is that the system should not allow to delete PO line item after doing GR/IR.
    We are using Account Assignment Category-N, Item Category-S.
    Please let me know if you have the solution for this requirement.
    Thanks in advance
    Thanks & Regards,
    Suresh

    Hi,
    Standard SAP will not allowed the PO to be deleted once it was GR done. The controlled is on the attributes of message to set as "E"
    Message no. 06115
    But if invoiced takes place, the is the point that PO can be deleted.
    You have to do have a Enhancement using MM06E005, insert you logic here to check PO history tables like EKBE, then check if invoice " Q" (BEWTP) exist, the PO cannot be deleted once the user delete the PO line and SAVE it. Ask you developer to help you on the following coding.
    Use MM06E005 and EXIT_SAPMM06E_012
    IF SY-TCODE = 'ME22N'.
    IF sy-ucomm = 'MESAVE' OR SY-UCOMM = 'YES'..
    LOOP AT TEKPO.
    IF TEKPO-LOEKZ = 'L'.
    SELECT SINGLE BELNR FROM EKBE INTO BELNR1 WHERE EBELN = TEKPO-EBELN AND EBELP = TEKPO-EBELP AND BEWTP = 'E'.
    IF SY-SUBRC = 0.
    SELECT SINGLE BELNR FROM EKBE INTO BELNR2 WHERE EBELN = TEKPO-EBELN AND EBELP = TEKPO-EBELP AND BEWTP = 'Q'.
    IF SY-SUBRC = 0.
    Regards,

  • After creation of PO system should not allow to change the price in PO

    Hi There,
    In my scenario once PO is created then after send to vendor PO print document,Users are changing the price in PO.so system should not allow to change the price in PO once PO got saved.
    So please advice.

    Hi,
    you could set in customizing for field selection keys the net price      
    to display for ME22N so that changes can not be made         
    (transaction OLME -> purchase order -> Define Screen Layout at Document Level).
    Please check that you have set all the relevant field selection      
    groups to display: AKTV, ME22, ME22N... (read and apply note 30316)                                                                               
    Other workaround is try to do by yourself with the badi                      
    ME_PROCESS_PO_CUST and send your own error message.    
    Regards,
    Edit

  • During PO creation system should not allow to save if it cross the PR value

    Hi,
    As I said in above subject line while creating the PO system should not allow to create more than the PR value and Quantity.
    Always system should allow the person to create the  Po with in PR value as well quantity in order to set up please let me know the configuration settings.
    thanks in advance.

    Hi,
    Please search the forum first for your queries for existance and then post queries., coz, the same question has been answered so many times before.

  • System should not allow to do the changes in PO once the ID created.

    Hi All,
    Once the Inbound Delivery is Created based on the Purchse Order, System should not allow to do the changes in the Purchase Order like Deletion of Item, etc..
    Any Configuration Changes is avaliable. ?
    Regards,
    Sudhakar

    Dear,
    Please check the staus in order
    Current order status xxxx does not allow goods receipt (Message no. C6009)? is this the message?
    This will not allow you to do GR for production order when you activate status profile "SAT1" in the production order. After that when you confirm order it will automatically assign next user status i.e. "SAT2" (if not assign it manually in CO02) it will allow you to do GR for that production order.
    Regards,
    R.Brahmankar

  • System should not allow to add line items in delivery

    Hi,
    1) system should not allow to add line items in delivery( in reference to sales order or STO)
    2) sales order/STO should not be changed if delivery exists
    how to control the above
    Alec

    Hi Lakxmi,
           I found answer for 1st point from you are old answers.
          can you throw somelight on 2nd point.
    Thanks
    Anil

  • Delivery is invoiced fully so system should not allow to create 2nd invoic

    hi Expert,
    my issue is, once invoice is created for delivery.
    system should not allow user to create
    second invoice for same delivery number.
    where to check the confiurtion to stop such
    behaviour
    waiting for your reply
    thanks
    Alicia

    Hi Alicia
    In the copy control from delivery to invoice - T code VTFL
    you can maintain the copy routines. try maintaining routine
    3-- which is delivery reatled header
    4-- which is delivery related item
    also at item level copy control you may add the check in billign quantites
    this would stop formc reating another invocie
    Hope this helps
    Thanks
    Akasha

  • Invoice cancellation should not allow for closed periods

    Dear All,
    We will be closing the posting period for each quarter,and declare the sales figure.,what ever the invoices we have made should not be cancelled in that quarter.,i want the a check in the system that if any cancellation during this quarter which is closed ,should not allow to cancel the invoice.ofcourse the accounting document will not be generated as the posting period is closed but still the invoice is generated and blocked for accounting.i want the creation of billing document should be blocked.
    i Know this can be achieved By defining new routine in VOFA and assign it in VTFL., but is there any standerd routine there which will solve my purpose or i hae to go for new routine.
    REgards
    Shakthi

    Hello Shakthi,
    In standard, there is note 180756.
    Unfortunately the note 180756 just helps for billing creation, it is not useful for
    billing cancellation.
    The note 180756 suggests to develop a copy requirement routine checking
    the periods.
    But in VF11 copy requirement routine are not performed.
    Unfortunately there is not a ready-to-use workaround.
    In transaction VOFA is possible to define a "copy requirement" routine,
    which is performed when the invoice is cancelled.
    You could create a routine doing the necessary check, and put
    it here.
    Regards,
    Alex

  • Once payment received  for bill system should not allow to cancel

    Hi  Experts ,
    we have created  commercial  invoice  and posted to fi document and    payment  received  from party.but when  we  try to  cancel  the same billing document system allowing  to  cancel the document.So Client  requirement  is once  payment received from party system it  should not  allow to cancel the billing document.
    Please  give  your  valuable suggestions on the same ...
    regards...
    MM

    Hello,
    In the Tx VOFA for the billing type to be cancelled(Ex F2), please
    fill the field Copying Requirements(V_TVFK-GRBED_S) with '29'.
    This routine prevents the cancellation of the billing documents which
    have been cleared.
    Regards,
    Raghavendra YN

  • System shud not allow for batch change after  bacth determiantion.

    Dear ALL,
       I have one Isuue at my client , there requiremtn is -
    "Performing the process it was detected that the raw material and packaging material  batches could be changed after the process order created, which allows to picking a batch instead FEFO. "
    Is there any way that system not allow for any change related to batch and its qunitity.
    Awaiting for fevorable respoce.
    Regards,
    Prerna Verma

    Hi Prerena,
    Activating Check Batch Tab in COR4 will performs an additional check in order itself.This check works after completing Batch Determination.For example during Batch Determination system has selected (as per your sort rule) Batch X for issue.But later User tries to change this Batch No. to Batch Y(by overwriting the batch no. in Batch field).But if you have activated this Check Batch function then system will perform the check immediately whether this new Batch complies the Batch Determination rule or not.And if found wrong then gives you an error or warning msg(depends oin your msg control).
    my second point is regarding Transaction code COB1 to deactivate the Allow change function.See if you activate the this tab then you finds that qty fields editable during Batch determination.So you can change the qty. manually during batch detemination.
    So in your case 2 level checks required.
    1) During Batch Determination (COB1) - Deactivate Allow change
    2) After Batch Determination(COR4) - Activate Check Batch
    Regards,
    Dhaval
    Edited by: Dhaval on Sep 27, 2010 8:43 PM

  • QA32 Without results recording system should not allow UD

    Dear All,
    Here we have only incoming inspection. For that i have activate 01 insp type in material master and respective master data also maintained. My problem is Once GRN has done its has gone to QA32. From there first i am doing results recording and save it. After that i was not able to do UD. Then i have gone to INspection lot change the user stantus to INIT then only system will allow me to do UD.
    Any automatic setting is there to be achieve this one. Whenever i wil do results recording no need to chagne the profile status or anything then i will do UD.
    Could you pls help me to resolve this issue.

    If you used the standard SAP process described here:
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20fbc091-ea3a-2b10-f0a3-877ffbf36436?quicklink=index&overridelayout=true
    You shouldn't have to do anything except make sure all the required characteristics have a status of 5.
    You shouldn't have to manually mark the inspection lot complete.
    FF

  • System should not allow overlapping trips

    How to restrict the sytem - overlapping trips should not be allowed in R3 as well as ESS. Error message should be displayed.

    That is a standard functionality.
    Say  you have created a trip from 01.01.2009 to 05.01.2009 and created an expense report for it.
    Now you try to create another travel request from 03.01.2009 to 07.01.2009, system will give error

Maybe you are looking for