How add new tab after reason for rejection tab using tcode va01

Hello,
       How to add new tab after Reason for Rejection tab using tranzaction code VA01.
pls suggest solution.

I don't think you can add a tab after reason for rejection tab. There are custom tab, which you can use for your convenient, given by SAP. You can look into the below details:
Program : SAPMV45A
Screen: 8459(Item) and 8309(Header).
Kuntal.

Similar Messages

  • How to add new tab after reason for rejection tab using tcode va01

    Hello,
    how to add new tab after reason for rejection tab using tcode va01.

    Hi,
    You can check this link...
    Hope it will be helpful to you.
    [https://forums.sdn.sap.com/click.jspa?searchID=23016273&messageID=6825861]
    [http://www.sapdevelopment.co.uk/enhance/fexits.htm]
    -Maharshi
    Edited by: Maharshi Vyas on Mar 3, 2009 12:45 PM

  • How add new tab after reason for rejection tab using tcode va01 using badi

    I want to add new tab in va01 using badi. I search badi ->  badi_sd_update_plval  at the time of implementation it  ask about access key.
    which is suitable badi for va01 enhancement.
    Any screen exit is available for this enhancement.

    You need to implement BADI through SE19. Refer below link for details
    http://help.sap.com/saphelp_nw04/helpdata/en/eb/3e7cf4940e11d295df0000e82de14a/frameset.htm
    Hope this helps..

  • How does the field ABGRU-Reason for Rejection get populated in routines

    Hi All,
    How does the field ABGRU-Reason for Rejection get populated in routines(VOFM)?
    BELNR,KPOSN,etc...fields are populated through KOMK and KOMP structures, similar way what structure is used for ABGRU?
    by the time the control from VA01 comes to routine the values of VBAK and VBAP are cleared, so these structures like KOMP and KOMK are used.
    Thanks in advance.

    You need to add rejection reason field ABGRU as a new field to pricing field catalog (KOMG structure) through APPEND structure KOMPAZ. KOMG inherits new fields from KOMKAZ (for header level fields) or KOMPAZ (for item level fields) structures and it is not directly modified but through KOMKAZ and KOMPAZ structures
    Since VBAP-ABGRU can vary from item to item, add it to item pricing communication structure KOMPAZ in SE11. Once KOMPAZ is added with new ABGRU field and activated it will automatically appear in pricing field catalog (KOMG)
    Afterwards the ABGRU field will then start to appear in the field catalog where you can create condition table (V/03) including the ABGRU as a field. Once done the rest is assigning the condition table to access sequence which is in turn assigned to the relevant condition type that you want to price based on partner function (all under IMG -> SD -> Basic functions -> Pricing -> Pricing control)
    In the pricing user exit userexit_pricing_prepare_tkomp in include MV45AFZZ, you will need a few lines of coding to fetch VBAP-ABGRU for the item and pass it to tkomp-abrug field. This will then be used by system to read the new condition table that you created.
    tkomp-abgru= xvbap-abgru
    So if you populate special pricing based on ABGRU (with possibly other conditions) in the condition table then that condition record will be read for the corresponding condition type.
    You would of course need a developer to modify KOMPAZ structure and code the user exit for moving the rejection reason to tkomp
    That is in short how you can achieve this

  • Workflow : How to put condition on Reason for Rejection ( BUS2032 ).

    Hi Experts,
    The situation is :
    I am trying to implement a condition on "Reason for Rejection" . If  there is any change in the " Reason for Rejection " ( VA02 )  tab of a particular item , a mail should be sent to a particular person .  How do I design a condition so that it would trigger a mail. What all information do I need. A clear suggestion would be  very helpful.
    Previously we created a workflow in the " BUS2032 " on " CHANGED " event. I tried to get item level information ( old and new ) from the same  Bussiness Object. What do I need to do to get the information ( old and new ).
    Thanks in advance,
    Raghava Vakada.

    Hi Experts,
    Please very very urgent,
    It is very helpful to me,
    <b>Please Please.......</b>
    Thanks in advance,
    Raghava Vakada

  • How can I disable the Reason for Rejection field in VA02 line items

    Hi,
      I dont want the users to be able to change the reason for rejection field in the sales order line items. Can someone please suggest a tried and tested way of doing this
    Thanks for reading.

    Set up an auth object for the field.  In userexit field modification check the auth object and set the field to be grayed out if they don't have authority.  Users can then not change the value of the field  Sample code
    IF screen-name = 'VBAP-ABGRU'.
           AUTHORITY-CHECK OBJECT 'Z_BLK_REAS'
                   ID 'ABGRU' DUMMY.
          IF sy-subrc EQ 0.
            screen-input = 1.
          ELSE.
            screen-input = 0.
          ENDIF.
      ENDIF.

  • How Add new Bill to location for an existing Customer

    Hi all :
    Would you please let me know where can add a new Bill to location for an existing customer ?
    OM Superuser > Order, Return > Order Organizer> New Sales Order
    Thank you

    You can add bill to location as follows
    Order Management Super User> Customer > Standard >Find your customer
    Add a new address if necessary
    And then in Business Purpose area, enter BILL TO as the usage.
    Hope this answers your question
    Sandeep Gandhi

  • User Exists In Sales Order Creation Program for adding "Reason For Reject"

    Hi gurus
    I have following requriement
    As New Sales Order created (VA01) by default or at the time of saving the sale order, perticular "Reason for Rejection" should be set to each line item.
    This is then can be removed in change (VA02) with Mass change.
    We need this to review the sales order / block sales order from MRP run.
    Please let me know how to manage this or is there any user exist for the same.
    Thanks
    Sunil K

    Hi,
    As per my knowledge the automatic creation of rejection order is not possible, still will check out and know.
    but for urgent use you will have to follow the manual way of changing the line items from OK to blocked for apporoval so you can achieve their not passing on to MRP.
    manual way is what is described below:
    You can either reject the whole sales document or individual items.
    Reject all items:
    If you want to reject all the items, choose Reject document in the change modus for the sales document.
    The system automatically selects all the items and you can enter a reason for rejection in the following dialog box.
    Enter the appropriate reason for rejection and choose Copy.
    The system assigns the same reason for rejection to all the selected items.
    Reject individual items:
    If you only want to reject some of the items, select those items in the item overview screen and choose Edit - Fast change of... - Reason for rejection.
    A dialog box appears in which you can enter the appropriate reason for rejection.
    Enter the appropriate reason for rejection and choose Copy.
    The system assigns the same reason for rejection to all the selected items.
    Reject individual items with different reasons of rejection:
    If you want to enter different reasons for rejection for the items, choose the Reason for rejection tab page from the overview screen when changing the sales document.
    You can enter a different reason for rejection for each item in the Reason for rejection field.
    regards,
    Siddharth.
    Edited by: SD on Mar 15, 2008 10:22 AM

  • Reason for Rejection getting Auto Populated

    Hi,
    I am creating an std order without reference to a preceding document, still the "reason for rejection" is auto populating in the Reason for rejection Tab.
    I dont want this to happen, please suggest.
    Sachin

    Hi,
    Suppose an order has been created of 100MTS and been Dispatched & Billed only 90 MTS.Now rest of 10 MTS ,you dont want to dispatch.Then in that case , Marketing person will mention the Reason of Rejection like Order Shortclosed.Now if you will see the Status of order in Document Flow , it will be closed.
    So if it is MTO Scenario, then just De-Assign the Stock from the Sales Order and assign it to the newly created one.
    Best Regards,
    Ankur

  • Reason for rejection in Quotation

    Hi SAP-Guys,
       I'm creating a quotation and i won't set any reason for rejection for that,but while saving it reason for rejection is populating automatically, i was unable to find out the reason .
      please help me on what basis it is fetching , any steps to follow.
    Regards
    Krishna

    Re: Reason for rejection in Quotation  
    Hi,
    I am creating an std order without reference to a preceding document, still the "reason for rejection" is auto populating in the Reason for rejection Tab.
    I dont want this to happen, please suggest.
    Sachin

  • Implement workflow process for material reservation using tcode IW32

    Hi
    How can I implement workflow process for material reservation using tcode IW32
    - PM order.
    Thanks,
    Amos

    Hi;
    Have been able to find the solution to create the IDoc MRESCR after entering a reservation? 
    I am in the same situation and I do not see the IDoc output in the BD87. 
    It would be nice if you share the solution.
    Thanks in advance

  • How can I pass value in status and reason for rejection using BAPI_LEAD_CREATEMULTI when creating multiple lead

    Hello,
    I want pass value in STATUS and Reason for rejection according to requirement when i am creating multiple lead using BAPI_LEAD_CREATEMULTI. Please help me how can i pass value. Please give some sample code that in which table i have to pass values and please also tell me INPUT_FIELDS values. Please help me
    Regards,
    Kshitij Rathore

    Hello,
    Please help me for solve this problem. I am trying to solve problem from last 4 days but i didn't get any solution.
    Regards,
    Kshitij Rathore

  • Status of Sales Order Open Even after assigning Reason for Rejection.

    Hi All,
    I am facing with a basic problem wherein even after assigning a reason for rejection status for a sales order, the sales order numbere is appearing in  the list of Open Sales Order(VA05).
    Also another case is i created a sales order with one line item, invoiced the same. Now i cancel the invoice and further wanted to close the sales order as i cannot delete the same. In this case also i see that even after assigning the reason for rejection, the sales order number along with its details appear in the list of open orders.
    Can somebody please tell me whatt configurations have i missed?.
    Regards
    Bhushan
    Edited by: NAGABHUSHAN THIPPANNA on Nov 30, 2009 9:14 AM

    Hi Vivek,
    Thanks for the reply... My issue got solved partially. Now if i assign a "Reason for rejection" to the sales order then that sales order is not reflecting in the VA05 (open orders list).
    But given a scenario wherein i create  a sales order and whose quantities & values  gets updated in the standard infostructures and i will be able to see the same by executing MCTE (incoming orders & Qty). After assigning the reason for rejection for the same sales order i view the output of MCTE then the report still displays the old ordered quantity and value. Is there any wayout to control this wherein the moment we assign a reason for rejection for a line item in a sales order and the values get reversed in the standard infostructures.
    Thanks and Regards
    Bhushan

  • How to enable field "reason for rejection" of view "status" in CRMD_ORDER

    Hello Everyone
    I need to activate/enable field "Reason for Rejection" in view "Status" of transaction CRMD_ORDER though a delivery document is created for the sales order.
    Can some one pls let me know where do I need to code to make field "Reason for Rejection" enabled.
    FYI, the same logic was applied for VA02 as well and the logic is written in userexit "USEREXIT_FIELD_MODIFICATION" which is working fine.
    Apprecriate your quick response.
    Thanks
    Dharma

    Hi Raj,
    Usually we use function module CRM_STATUS_UPDATE to
    change user status in document. But if you want to
    trigger next process or change from certain user status to next status interactively by the system, you can
    use Badi CRM_ORDER_STATUS (here you have after and before
    method).
    Hope this could help.
    Rgds,
    Gun.

  • How to sets the Reason for Rejection of the Open Sales Order Lines

    Hello gurus,
              I want to set the Reason for Rejection of the Open Sales Order Lines, Case is like :
    If current date is exeed the Auto Void Confirmed Back Order Days(for item level) +  date (last responding from customer), then reason for rejection should be set, So i want the logic to find out the date is exceed or not.
    Thanks
    Anjana

    Hello anjana,
       Actually your question is some confusing, but if u want to get eldest change as active sales order then logic is as follows:
    1.  On base of OBJNR u have to get UDATE from JCDS table
    2. then write logic as:
    SORT i_jcds BY objnr stat chgnr DESCENDING.
          LOOP AT i_jcds INTO wa_jcds1.
            CLEAR lv_stat.
            lv_stat = wa_jcds1-stat.
            AT NEW objnr.
              AT NEW stat.
                CLEAR: wa_tab.
                wa_tab-objnr = wa_jcds1-objnr.
                wa_tab-stat = lv_stat.
              ENDAT.
            ENDAT.
            IF wa_jcds1-inact = 'X'.
              CLEAR lv_tabix.
              IF sy-tabix > 1.
                lv_tabix = sy-tabix - 1.
              ELSE.
                lv_tabix = 1.
              ENDIF.
              READ TABLE i_jcds INTO wa_jcds2 INDEX lv_tabix.
              IF sy-subrc = 0.
                wa_tab-chgnr = wa_jcds2-chgnr.
                wa_tab-udate = wa_jcds2-udate.
                wa_tab-utime = wa_jcds2-utime.
                APPEND wa_tab TO i_tab.
              ENDIF.
              CONTINUE.
            ELSE.
              wa_tab-chgnr = wa_jcds1-chgnr.
              wa_tab-udate = wa_jcds1-udate.
              wa_tab-utime = wa_jcds1-utime.
            ENDIF.
            AT END OF objnr .
              AT END OF stat.
                APPEND wa_tab TO i_tab.
              ENDAT.
            ENDAT.
          ENDLOOP.
          DELETE ADJACENT DUPLICATES FROM i_tab COMPARING objnr stat.
          SORT i_tab BY objnr stat udate utime.
          DELETE ADJACENT DUPLICATES FROM i_tab COMPARING objnr.
    3. now in i_tab table u'll get eldest UDATE
    Hope its work for u.
    Thanks & Regards,
    Sumit Joshi

Maybe you are looking for