purchase requisition is released by user but still showing in INBOX as you should release the item

    Hi Experts,

    My user got one issues that, for purchase requisitions even though he is released the PR’s still it is showing in INBOX as PR should release.

    I have gone though all the documents in SCN, even I have checked whether any BADI is implemented or not for this. but no BADI is implemented.

    but when I enter the BADI WF_BWP_SELECT_FILTER name in SE19… it is showing no implementations…..

    in SE18 under this BADI some standard example class is implemented “IF_EX_WF_BWP_SELECT_FILTER~APPLY_FILTER”.

    is this interface is creating any problem or Do i need any thing else.

    regards,

    Ramki

    Hi Experts,My user got one issues that, for purchase requisitions even though he is released the PR's still it is showing in INBOX as PR should release.I have gone though all the documents in SCN, even I have checked whether any BADI is implemented or not for this. but no BADI is implemented.but when I enter the BADI WF_BWP_SELECT_FILTER name in SE19... it is showing no implementations.....in SE18 under this BADI some standard example class is implemented "IF_EX_WF_BWP_SELECT_FILTER~APPLY_FILTER".is this interface is creating any problem or Do i need any thing else.regards,Ramki

    purchase requisition is released by user but still showing in INBOX as you should release the item

    Very Helpfull

    User Rating: Be the first one !
    Vice Professor Asked on November 2, 2016 in user interface-development.
    Add Comment
    1 Answer(s)

      Hi Ramki,

       

      No, the BAdI isn’t implemented yet. The example implementation that you see is just a sample that SAP provides for developers.

       

      Hope that helps.

      Add Comment

        Hi Ramki,

         

        No, the BAdI isn’t implemented yet. The example implementation that you see is just a sample that SAP provides for developers.

         

        Hope that helps.

        Add Comment

        Your Answer

        By posting your answer, you agree to the privacy policy and terms of service.