Quality Rejection reason

Dear Sir's,
Our user wants to see the Rejection reason in stock report i.e MB52,MB51.
Is it any t-code where we can seen the Block stock with rejection reason.
The rejection reason feed at the time of "Usage Decision".
Please suggest me.
Thanks in advance.
Regards
Ajit Sharma

Hi Ajit,
It is not possible to view the rejection reason in MB52 as it is  a Stock report.
You can get the rejection reason details in Reason for Movement column in MB51 report.
Thanks & Regards
V.Devaraj

Similar Messages

  • Sales orders with rejection reason in R3 are not nullified in  BW

    Hi,
    Actaully One sales order xs26665 has been uploaded into BW from R/3 with OrderQty 100
    After cancellation of same order xs26665 in R/3 by putting Rejection Reason, R3 extractor is generating two records as specified
    1st record specifies order xs26665 with Order Qty = -100
    2nd record specifies oredr xs26665 with Order Qty = 100 and updating filed "reason for rejection" = EQ.
    Because of this two records which are generated in R3 after cancellation which are loaded in to BW, The value of Order Qty for sales order xs26665 is not geting nullified and it still shows final value which is = 100 as order qty.
    This records is first geting uploaded in to ODS and further in to a cube in BW using deltas.
    Rgds,
    C.V.
    Message was edited by:
            C.V. P

    Hi CVP,
    make sure that the datasource that you are extracting the data from has got the field ROCANCEL and that the keyfield Quantity is marked or checked in the column Inversion.,.. (3rd field in your datasource... Selection Hide Inversion & Field Only).. There check the Inversion box for your Quantity field... only on enabling this would your Quantity in BW get negated...  The cancelled order would then be marked as 'X' for the field ROCANCEL which inturn would be picked up by the BW through the InfoObject 0STORNO..
    Hope it solves your issue...
    Regards
    Manick

  • How to set default reject reason in VA01 (create sales order)

    Hi
    Everybody can tell me how to set default reject reason for item in sales order.
    in our sap system there are a default reject reason as '90'. We want to set it as "Null".
    Thanks
    Henry

    Hi,
    Assigning a default Reason for Rejection is not in standard SAP. I am sure there is some enhancement/user exit which updates the reason for rejection.
    Please get the help of an ABAPer, create the sales order in debugging mode and he will find out the logic behind the automatic reason for rejection.
    Before that you can find the exits in the include MV45AFZZ for any code related to this.
    Hope this helps

  • STATUS_READ & line item rejection reason - too complex

    Hi All,
      I have to trigger an output to a smartform via an output routine. I have to do the following checks in my output routine before I decide to propose the output or decline to propose the output if conditions fail.
    1. Order header can have status PEND, Hold, Release. IF the status has changed to anything else except pending, i should propose output.
    2. Again if a line item is rejected with certain reason code, then also I have to propose the output.
      Both the above conditions must be checked before proposing the output. My issue is how do I know what was the old value of status and rejection reason.
    I tried using FM STATUS_READ, but it does not give something like this was the old value and this is the new value. I do not find any FM to get item rejection reason. Do I have to use change documents for these.
    examples
    a)Order with 2 Framing Configurable Line Items.  The user status of the order is changed from PEND to QAHD.  The standard order output label is proposed for both line items on the order.  At a later time, one of the line items is rejected for reason 90 (for example).  At that time a new label is created, just for that specific line item – with the rejected artwork text on the label. 
      In this case if I use STATUS_READ, i will get active status as QAHD, so I will try to propose normal output so I am fine. Later when the item is rejected, I will again get staus as QAHD and I will propose output for one unrejected item which is WRONG. I had already proposed the output in past, so I should not. I should only propose output for the rejected item.
    b)Order with 2 Framing Configurable Line Items.  The user status of the order is still in a PEND status.  The user changes one of the line items to a rejected for reason 91 (for example).  A label is printed just for that line item with the rejected artwork text on the label.  At a later time, the user status on the order is changed from PEND to QARD.  A label will print, only for the unrejected line item and the label is the standard order output label for HJ.
      In this case I do not know where to get the old rejection reason of item. If I do a database select, I will get current rejection reason 91, but how do I know if I had already proposed the output or not for a certain item.
    c)Another scenario to think about is that there is nothing preventing the user from setting a rejection status on an item and changing the user status at the same time and saving it.  In that case we would want only one label per piece (the rejected label for the rejected item and the standard label for the non-rejected item).
      I think I have to check the time order was updated and do something like that.
    All inputs are welcomed.
    Thanks
    Pulin

    Write the code like
      concatenate 'OR' int_orders-aufnr into d_objnr.
        call function 'STATUS_READ'
             EXPORTING
                  client          = sy-mandt
                  objnr           = d_objnr
             TABLES
                  status          = t_status
             EXCEPTIONS
                  object_not_found.
    Read table t_status with key stat = 'I0076'.
    if sy-subrc eq 0.
    do not print output.
    endif.
    Thanks
    Seshu

  • Lead Reject Reason Code

    In the out of the box lead process in CRM OnDemand, when you click the reject lead button you are taken to an unconfigurable form and asked to enter a lead reject reason, when you click save this information is then appended to the end of the comments field.
    Because it is in the comments field it's difficult to report on, and because its free form it's difficult to analyze. Has anyone come up with any workable ideas on
    1) how to either analyze lead reject information
    2) report on lead reject information
    3) a different way to collect lead reject information

    Hi, Its so interesting. We had the same requirement with one of our clients. We came up with a custom solution, which would support a picklist for reject reason and would solve the reporting issues as well. Here is what was done
    - Ended up not using the oob reject button
    - created 2 custom fields on the lead page. 1 for reject reason , 1 for status,
    - We also hid the oob status field and made the custom status field update through wf, when the lead is rejected, converted etc..
    This worked out well. Hope this will help

  • Oracle UCM - How to view workflow reject reason

    I have created a workflow
    Contributor --> Reviewer1 --> Reviewer2 --> HOD Approval
    If Reviewer1 or Reviewer2 or HOD Approval "REJECT" the document it redirected to most recent workflow step. While reject they enter "reject reason" but the reject reason is not shown to most recent workflow user.
    I need a solution to over come this
    Thanks
    Deepak

    You should read the readme.txt more carefully. It clearly states:
    "If desired, the include display_reject_reason might be used to display the reason." (i.e. it has not been added to any page yet)
    What you still need to do is to add a line <$include display_reject_reason$> somewhere in workflow_review_frames.htm (or find an include where this can be added).

  • Accept / Rejection Reasons for Shopping Cart Approval

    Hi experts!
    Our customer would like to have the following functionality.
    During approval workflow the user will either Accept or Reject the shopping cart and at the same time he must enter a reason for approval / rejection from a list with fixed texts / values.
    I didn't find any documentation about rejection reasons during approval of shopping cart. Has anybody of you ever seen this or realized anything like that?
    If SAP Standard doesn't offer anything suitable we might have to modify the approver screen or develop a new screen.
    Any helpful answer would be much appreciated.
    Best regards,
    Corinne

    Hi
    <b>Please try this -></b>
    Re: Make mandatory field-Reason for rejection notes-SC approval screen
    Reason for Return Delivery missing
    Re: Text Types Issue on Bid/Quote
    Temporary GUID coming from Sourcing in Doc change badi
    Reason for Return Delivery
    inactive approval and reject buttons on shopping cart approval screen
    <u>Else Use BBP_DOC_CHECK_BADI</u>
    SC header level Reject- Display error message
    Hope this will help. Do let me know.
    Regards
    - Atul

  • Rejection Reason - Future Period Date Placed in Service

    Hello all,
    While running PRC: Interface Assets to Oracle Assets program, I got Rejection Reason as Future Period Date Placed in Service
    Please give your inputs to clear this issue.
    Thanks and Regards,
    Muthu

    Hi
    The Date Placed on Service should be within an open period in Projects. FA period should also be open.
    It seems you enter a Date placed on service which is later than the end of the open Project period.
    Dina

  • In Authorization task, require entry of a Reject "reason" ?

    In Authorization task, require entry of a Reject "reason" ?
    When the Authorizer "Rejects" an authorization task, we want to require entry of the "Reject Reason". 
    The only thing we've thought of so far is to have a field that's mandatory during that moment...but we don't want them to have to enter anything if they "Approve", so we really want that field to be 'conditionally mandatory'....based on which button they click...

    We are also trying to implement the similar functionality. I have overwritten the confirm_action() function the code to take of the requirement i.e., showing a textarea while in authorization phase and making it mandatory while the user  hits 'Reject' button. But the issue that I am seeing is, this textbox is becoming mandatory for 'Reject' button, but it is not storing the user comments when it was rejected. Also, this textbox is becoming mandatory, when the user hits the 'Approve' button as well, but doesn;t insist the user to fill in. Any help in achieving this function is greatly appreciate.

  • The system shall allow for reporting by rejection reason code

    Allow the reporting of a reason code when an order is rejected for the purpose of tracking lost sales
    The system shall allow for reporting by rejection reason code to allow for tracking lost sales.

    A custom ABAP will have to be developed looking at table VBAK and VBAP to determine the reason for rejection, then group it by order number.

  • Reject reason schedule line not updated item level

    Hi,
    Say a particular sales order line item has 3 schedule lines all of which had been rejected through reason '00',
    Just a clarification as to why the line item doesnt get rejected with a reject reason if all the schedule lines in tht line item is rejected.
    Thanks
    Keshi

    Dear Keshi,
            When there is reason for rejection set for all schedule line then what is the need of getting at item level.
    Reason for rejection at Scheduleline level is more specific than at item level,
    I hope it will help you
    Regards,
    Murali.

  • Delete codes for rejection reasons in customizing

    Hello,
    We had some rejection codes, that we used for our sales orders.
    Now we want to delete all these codes in customizing step, because we won't use them anymore.
    Will it cause any trouble for my SD documents, that the deleted rejection codes have already been used for?

    If you still have active documents with the deleted rejection reasons then you will almost certainly have problems trying to process them further.
    1. If the document has been rejected you probably will not need to process it further anyway.
    2. If you do encounter a problem, I expect you would be able to select a different rejection code.
    If you are worried, you should test in a sandpit client.
    Deleting reason codes which have been used is really not good practice, hence my suggestion that you change the descriptions.

  • SD contract- reject reason 54 (billing already completed (ECC migration))

    hi SD expert,
    Any reason why the rejection reason 54 used for ? in SAP 4.6c, the Rj is' Rejected ' and in the SAP DB copy server 4.6C, the rejection reason change to 54. Anyone know when this reason rejection 54 used ?
    Thanks for your help

    Please remember to mark this thread as [solved] in the title. Thank you.

  • Report on Quality Rejection

    Hi
    I am having a material and I am Doing MIGO against the PO
    Then due to quality reasons I am sending back to vendor
    If I want make a report on material rejection report based on quality
    How can I do this
    NK

    In this case you should use Tables MKPF and MSEG.
    Else add field Reason for Movement in report MB51, in path SPRO > Inventory Management and Physical Inventory > Reporting > Define Field Selection for Material Document List > Here add RM07DOCS / MSEG / GRUND and activate selection and output indicator.
    And try to use, it will suffice your requirement.

  • Quality rejection reports

    dear all
    please tell me t-codes and reports for material rejected or rework from quality managenent.
    what are the standard reports available in sap for quality inspection results analysis?
    Prashant

    Hi Prashant,
    Pls. Check in Tcode : QE51N ( Inspection Results Recording).
    I hope this will server your purpose.
    Reward if useful.
    Regards,
    Tejas

Maybe you are looking for