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

Similar Messages

  • 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

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

  • 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 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 to put condition for one date range should not interfear with another ?

    hi friends,
    how to put condition for one date range should not interfear with another  date range.
    my data base table has two fields
    from date
    to date.
    when we enter the date range in the data base , new date range means from date and to date should not interfear.
    can  anybody help me.
    thanks &Regards,
    Revanth
    Edited by: rk.kolisetty on Jul 1, 2010 7:18 PM

    Do it the SAP way....
    First entry...from is today, to is 99991231.
    New dates entered, now we have two rows...:
        from is original date  to becomes yesterday.
        From is today          to is 99991231

  • How to put Reason for  rejection to line item level?

    Hi
    I am updating the Sales order at line item and putting the reason for rejection but it didnt updates the database. Below is the code.
          LOOP AT LT_VBUP1 INTO WA_VBUP1.
             ON CHANGE OF  WA_VBUP1-VBELN.
              CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
                EXPORTING
                  SALESDOCUMENT    = WA_VBUP1-VBELN
                  ORDER_HEADER_INX = LV_ORDER_HEADER_INX
                TABLES
                  RETURN           = IT_RETURN
                  ORDER_ITEM_IN    = IT_ORDER_ITEM_IN
                  ORDER_ITEM_INX   = IT_ORDER_ITEM_INX.
              CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
                EXPORTING
                  WAIT = 'X'.
              CLEAR WA_TY_SOCLOSE.
              IF SY-SUBRC EQ 0.
                LT_TY_SOCLOSE-VBELN = LV_SALESDOCUMENT.
                LT_TY_SOCLOSE-STCLOSE = 'Y'.
              ELSE.
                LT_TY_SOCLOSE-VBELN = LV_SALESDOCUMENT.
                LT_TY_SOCLOSE-STCLOSE = 'N'.
              ENDIF.
              APPEND  LT_TY_SOCLOSE.
            ENDON.
            CLEAR: WA_ORDER_ITEM_IN,WA_ORDER_ITEM_INX.
            WA_ORDER_ITEM_IN-ITM_NUMBER =  WA_VBUP1-POSNR.
            WA_ORDER_ITEM_IN-REASON_REJ = 'Y1'. " Putting order of rejection for the archiving
            WA_ORDER_ITEM_INX-ITM_NUMBER = WA_VBUP1-POSNR.
            WA_ORDER_ITEM_INX-UPDATEFLAG = 'U'.
            WA_ORDER_ITEM_INX-REASON_REJ = 'X'.
            APPEND WA_ORDER_ITEM_IN TO IT_ORDER_ITEM_IN.
            APPEND WA_ORDER_ITEM_INX TO IT_ORDER_ITEM_INX.
            CLEAR WA_VBUP1.
          ENDLOOP.
    Correct me where I am putting wrong.
    Regards
    Mohinder

    LOOP AT LT_VBUP1 INTO WA_VBUP1.
    ON CHANGE OF WA_VBUP1-VBELN.
    CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
    EXPORTING
    SALESDOCUMENT = WA_VBUP1-VBELN
    ORDER_HEADER_INX = LV_ORDER_HEADER_INX
    TABLES
    RETURN = IT_RETURN
    ORDER_ITEM_IN = IT_ORDER_ITEM_IN
    ORDER_ITEM_INX = IT_ORDER_ITEM_INX.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
    WAIT = 'X'.
    CLEAR WA_TY_SOCLOSE.
    IF SY-SUBRC EQ 0.
    LT_TY_SOCLOSE-VBELN = LV_SALESDOCUMENT.
    LT_TY_SOCLOSE-STCLOSE = 'Y'.
    ELSE.
    LT_TY_SOCLOSE-VBELN = LV_SALESDOCUMENT.
    LT_TY_SOCLOSE-STCLOSE = 'N'.
    ENDIF.
    APPEND LT_TY_SOCLOSE.
    ENDON.
    CLEAR: WA_ORDER_ITEM_IN,WA_ORDER_ITEM_INX.
    WA_ORDER_ITEM_IN-ITM_NUMBER = WA_VBUP1-POSNR.
    WA_ORDER_ITEM_IN-REASON_REJ = 'Y1'. " Putting order of rejection for the archiving
    WA_ORDER_ITEM_INX-ITM_NUMBER = WA_VBUP1-POSNR.
    WA_ORDER_ITEM_INX-UPDATEFLAG = 'U'.
    WA_ORDER_ITEM_INX-REASON_REJ = 'X'.
    APPEND WA_ORDER_ITEM_IN TO IT_ORDER_ITEM_IN.
    APPEND WA_ORDER_ITEM_INX TO IT_ORDER_ITEM_INX.
    ***********************************************************************<<<<do this bit here
    CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
    EXPORTING
    SALESDOCUMENT = WA_VBUP1-VBELN
    ORDER_HEADER_INX = LV_ORDER_HEADER_INX
    TABLES
    RETURN = IT_RETURN
    ORDER_ITEM_IN = IT_ORDER_ITEM_IN
    ORDER_ITEM_INX = IT_ORDER_ITEM_INX.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
    WAIT = 'X'.
    CLEAR WA_VBUP1.
    ENDLOOP.

  • 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

  • Not able to put reason for rejection at sales order level.

    Hi Gurus,
    I have an issue where I am not able to put reason for rejection for line item in sales order. It gives error as please delete the follow on document purchase order line item number 10. I have already deleted the line item in purchase order. Then tried but did not work. Tried by deleting the purchase requision item also but it did not work.
    Tried to undelete the item from PO and then again tried to put reason for rejection but it could no worked out. 
    Please guide me what can be the solution.
    Regards
    Vinod

    As far a I understand you created PO for line item
    So first check whether GR is reversed or not for PO
    Then mark this line item for deletion in PO and then in PR
    Check if you have created any billing document for PO if so reversed that invoice
    Also check if you have created any delivery for the Line item in sales order if yes then reversed the same
    If you have Sales order related Billing, and if you have done billing reverse the same
    If you have Delivery related Billing, and if you have done billing reverse the same
    After reversing all docuemnts created for Sales order then only try to reject the line item
    You can check table VBFA for document flow

  • How to put Menu in WebDynPro for ABAP

    How to put Menu in WebDynPro for ABAP

    What kind of menu do you want? Normally WD4A doesn't need any menu's. You can create (drag and drop) UI elements on your view and use navigation links to navigate from one view to another (for example). In classical dynrpo programming these buttons (back, cancel, exit, etc.) are used to navigate.
    But in WD4A 'menu' is created using the UI elements like button, inputfield, textview, table (grid), etc.
    So let me know what kind of menu you're talking about, and I might be able to help you.
    Kind regards,
    Micky.

  • Unable to put  Reason for Rejection for Return Sales Order

    Hi
    I am unable to put  Reason for Rejection for Return Sales Order.
    what may be the reason?
    Reg,
    Antaa21

    hi
    One of the possible reson could be, there is subsequent document created. Please check the VBFA table for document flow and see if there is any other document created for this line item, if yes then you have to reverse the same
    Check whether this field is maintained as DISPLAY only or not
    T-Code SE51(Screen Painter)
    Give Program Name SAPMV45A
    (before doing this confirm from the field from sales order, keep curcer on the pricing date press F1
    and then select technical details)
    Screen Number 4441
    (before doing this confirm from the field from sales order, keep curcer on the pricing date press F1
    and then select technical details)
    Select Attributes radio button.
    Go to Element list Tab. Inturn select Special Attribute tab in Subscreen.
    For Field Name "VBAP-ABGRU" Check what is maintained might be it is maintained as DISPLAY only.

  • 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 to put different component quantity for different  subcontracting vendo

    How to put different component quantity for different  subcontracting vendor

    Hi,
    To achieve this, you have to create alternative BOMs for the assembly with different component quantities.
    First create in Alternative BOMs in CS01
    1. C223 - Create Production Versions for the the assembly for each Alternative BOMs
    For e.g. 0001 for Alternative BOM 1 and 0002 for Alternative BOM 2 and so on...
    Production Version 0001 - For Vendor 1
    Production Version 0002 - For Vendor 2 and so on...
    2. ME11 - Create Subcontracting Purchase Info record for assembly, plant, purchase org and vendor 1 (Here in "Purchasing Data 1" screen, specify the Production Version "0001"), similarly for vendor 2, specify production version "0002" and so on...
    3. ME21N - In PO, system will propose the BOM as per Production Version which is assigned in Purchase Info record for the vendor, material (assembly), plant and purchase organization.

  • Workflow: Select Reason for rejection from dropdown list.

    Hi all
        I have to create a step where the Manager has to select the
    Reason for Rejection from a dropdown list refering to a custom
    parameter table maintained from t-code sm30.
    Please post your suggestions on this.
    Thanks for your time,
    Mallik

    Thanks for your Reply,
       But It doesn't seem to work because It has to display a (table parameter) field containing the predefined Reasons for Rejection(dropdown list or more like search
    help) from which the supervisor has to select one and it has to be attached and sent as a mail.
    thanx

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

Maybe you are looking for