Cancellation Workflow for PO

Hello SRM Gurus,
We have a business requirement when purchaser cancel PO due to some reason it should go to his manager for approval. So my question is that is it possible to configure PO cancellation workflow (extnded classic). If yes how can we do  it ?
Thanks,
Prashant

Hi Prashant,
I do not see why it couldn't be possible to trigger a 1 step WF in case of PO cancellation.
In the criterai, you should be able to use the PO item status (cancelled) to drive your WF requirement.
Kind regards,
Yann

Similar Messages

  • Workflow for Billing Cancellation

    Hi,
    I would like to know that SAP have standard workflow for approved process billing cancellation or not?
    Can anybody help me pls?
    Regards,
    Jr.SD

    Hi there,
    Discuss your requirements with a Workflow consultant as there is no such thing as SD standard workflow.
    Well, this if I am understanding workflow as in SAP Workflow.
    If you are referring to processes, as in if you are able to cancel an invoice yes that is SAP standard - use transaction VF11.

  • Is there any workflow for travel cancellation?

    Dear All,
    Is there any workflow for travel cancellation?
    Regards
    Somu

    Dear Shankar,
    BUSINESS PROCESS:
    Employee applied Travel Request -----Manager approved----Travel Admin booked Tickets --- Employee has taken travel advance also.
    Now due to employee personal problem he do not want to travel. Now He want to cancel.
    Can employee get cancel option in ESS portal?
    How FI will recover the amount?
    What is the process?
    Regards
    Somu

  • Workflow for PR release

    Dear Experts,
    We have implemented SAP standard workflow for PR item release i.e WS00000038, when I reject a PR notification is not sent to initiator.
    If I see In SWEL - When a PR item is rejected system is picking up step "PR item significantly changed" instead of "Item release cancelled"
    Request your suggestions in this regard.
    Thanks,
    Uzair

    Hi,
    Please see the below thread, it may help you.
    Re: Trigger Purchase Requsition Workflow trigger after purchase req. changed

  • Workflow for Document Approval

    Hi all,
    I'm a newbie to SolMan and is trying to figure out how to implement a workflow for document approval. A similar question has probably been posted in the past, but I can't find a definite solution, only some hints.
    Basically, what we're trying to achieve is the following:
    When a document is uploaded using SOLAR02, and the creator of the document changes the status to ready for sign-off, we would like to trigger a workflow which will send an email to a couple of persons who are responsible to approve the document. We already implement the digital signature, we just want to add an automatic email notification to be sent to the approvers.
    Based on my research, it seems that this is not supported by SolMan and hence we have to do a custom development.
    There's an object key called SOLMANDOC and we should raise an event (something like SIGNATURE_PROCESS_START) to send an email notification to the approvers. Can somebody confirm whether my understanding is right ? Does anybody know the name of the BADI that we can modify to achieve our goal ? 
    FYI, we're using SolMan Rel 7.01 SP 19.
    Thanks in advance
    Lara

    Hi Phil,
    I'm facing with problems with creating a simple 2 steps release strategy.
    the problem is I cant approve the last step of the release.
    This is what I did:
    In spro Digital Signature->Signature strategy:
    in "Define Authorization groups" I create this entries:
    1. EING
    2. VERIF
    in "Define Individual Signatures" I create this entries:
    1.  S1   EING
    2.  S2   VERIF
    in "Define Individual Strategies: I create this entries:
    SigStrat: ZSIGSTR
    Signature Method: R
    Display comment: X Required
    Display Remark: X
    Display document: X
    Verification: not checked
    in "Assign individual signatures"
    CtrIn  Indiv.SIG.      AGrpDIG
    1          S1               EING
    2          S2               VERIF
    Display Predecessor for Ctrln is 2 is 1
    for "Display release statuses"  an entry with one line with the value 1
    and in "Display individual signatures there 2 entries 1 and 2.
    in spro "Define Document status schemes"
    stat scheme "ZSIGSTR"
    4 status:
    Status                 init status      Sequence    Low     High       lock         Signature schma  End status         Cancel status
    COPY_EDITING       X                  10           10       20          -                    
    REVIEW                                     20           10        40        X                    ZSIGSTR         RELEASED    DECLINED
    RELEASED                                30           10        40        X                   
    DECLINED                                  40           10        20             
    I created two roles with object c_sign_bpr one with the value "EING"   and the other with the value "VERIF"
    I assign this status scheme to a document type in my project.
    I tried to release a document the first step was the author of the document move the status to "REVIEW" and I got a window that i need to enter my password and it worked ok.
    The problem is in the second step that I need to release the document (now is in a REVIEW status) When I press on the icon in order to release I didn't get the option to release only to cancel there is no "V" option in the small window.
    Can you please tell me if I did a correct customization? also can you tell me if my problem is maybe missing authorization? Can you direct me to reading material or to an example?
    Best regards
    Lior Grinberg
    Edited by: Lior Grinberg on Nov 28, 2011 6:22 PM

  • Workflow for PO Release Strategy

    Hi all Workflow experts
    We are on ECC 6.0. We have created a 3 level Rel strategy PO and are creating the workflow for this scenario.
    The business object we are using is BUS2012 and WF Template is WS20000075.
    Each time a PO is created/changed workitem will be sent order we have defined, ie. L1, L2,L3. Each time mail goes to the inbox of the concerned approver.
    The problem is when the final approver cancels the release. Under activity 'Release of PO canceled, Task TS20000167 we have assigned the agent as Originator of PO. However at this instant mail does not go into the originator's mailbox.
    Approver is cancelling the release in ME28 as it should be, I presume.
    Are we missing something here? Is there any additional settings required to trigger the mail to the originator?
    I would be happy if the responses from you all does not point to SAP .htm files! since I have already gone through them but it is very hard to understand some simple things!
    Thanks in advance.
    Regards,
    Raghu

    All,
    I gather that ver 4.7 onwards, SAP has supported the PO rejection/cancellation feature. Since I am working on client's server which is 4.6 c I am not able to implement this. Unfortunately, in the process of doing R&D within the sandbox I seem to have damaged the template WS000075. Now I am getting an error message at the first approval level saying "relase written to buffer".
    Can anyone tell me what does this mean? Also is there a way to retrive the original template form the development clients?
    Regards,
    raghu

  • Workflow for marketing plan approval

    Hello everyone,
    Does anyone know if there is a standard workflow for approval of marketing PLANS (I don´t mean campaigns)??
    Best regards,
    Efrain

    Hi Jaya,
    I haven't used this particular workflow but hopefully the following is of use:
    - Email to initiator- the likely explanation is that the workflow has not identifed the recipient's email address. Follow steps 4 & 5 from the Blog and this should resolve the issue.
    - Cancelled Event - The wait step listens out for the triggering of the corresponding event on the BOR object.
          i.e. for this workflow wait step 164 is listening out for CANCELLED to be raised on that particular instance of BUS2010020.
          If this is triggered that branch of the fork will be triggered.
    - Locked/Rejected - There is no step (that I can see) that notifies the initiator that the campaign has been locked.
      However you can add your own Send Mail step(s). An alternative approach would be to have additional branches that listen for the  BUS2010020.locked and the rejected events and then have your Send Mail steps, however this is probably overcomplicating the solution.
    - Schedule condition and start condition - Again I haven't used campaigns yet but in the Blog they are using the Marketing Project Campaign BOR Object status profile and status table  - look at object BUS2010020 in SWO1.
    I hope that this is of use.
    Best Regards,
    Trevor

  • Cancel Workflow Button - Custom OA Page

    Hi, I tried searching for this, but didn't find anything.
    Is it possible to implement Cancel workflow process Button in Custom OA Page? If yes, some help would be much appreciated
    Thanks
    Ved.

    Hi,
    Please elaborate your requirement...
    If you want a button who will submit a Concurrent prgram for WorkFlow Cancellation then you can do it
    using OracleCallableStatement.
    Thanks,
    Gaurav

  • Workflow for releasing PR

    Hello Friends,
    I need a workflow for releasing the PR. For this I had used the default workflow WF_REQ_REL. Its working fine.
    My problem is, if I am rejecting and saving the release of an item in the PR, the workflow is currently choosing the outcome 'Purchase requisition item significantly changed'. Is this correct?
    When I reject the release of a particular item in the PR, I think the outcome to be executed should be 'Release of purchase requisition item refused'.
    Can someone give an appropriate explanation & a solution for this ? Is there anything wrong from my side ?
    Regards,
    Abijith

    Hi Abijith,
    Yes it will follow the significantly changed branch only if you cancel or reject a purchase requisition. The reason is if you check the status of purchase requisition then whenever the PR is rejected, the status becomes changed.
    If you want to take any action in the workflow when the PR gets rejected, then you need to read the field BANPR of table EBAN. If BANPR = 08(REJECTED) , this implies that the PR is rejected and you can take the further actions thereafter based on it.
    There is nothing wrong from your side. But try to look into more technical things like values of fields in table EBAN etc. to know why exactlly  it is following the SIGNIFICANTLY CHANGED branch.
    Feel free to ask more if you don't get this.
    Regards,
    Guddan

  • PR Workflow for release strategy

    Hi,
    Could you please let me know the steps how to configure the workflow for the PR release strategy for both item level as well as header level.
    Thanks in advance
    Shp

    Hello,
    If you wish to work with procedure 1, define the following:
    Release codes
    Release indicators
    Assignment of release indicators
    Release prerequisites
    Determination of release strategy
    1. Release codes
    Create the release codes.
    2. Release indicators
    Define release indicators and branch to the detail screen. Here you define whether fixed purchase requisitions may be changed by Materials Planning, for example, and whether an RFQ or a purchase order may be created from the requisition.
    You can also determine the field selection here.
    In the area "Changes after the start of the release procedure", you specify whether a requisition may be changed after the release procedure has begun. You specify whether the strategy has to be redetermined after changes, or whether the release procedure has to start all over again from the beginning.
    This parameter bears a relation to the parameter "Value change". For example, previous releases are not cancelled if the value of the requisition item after the change does not exceed plus 10% of its original value.
    Attention:
    Be sure to create a release indicator (e.g. B for "blocked") that serves as the starting point for subsequent indicators. Do not set the indicators for release for the issue of RFQs and PO on the detail screen for this indicator.
    Also create a release indicator characterizing the released status. Set the indicators for release for the issue of RFQs and PO on the detail screen.
    3. Assignment of release indicators
    Assign a release indicator in dependence on the status of the release.
    Example:
    You create a release strategy S1 consisting of two release codes 01 and 02. Release with 01 is a prerequisite for release with 02. If release has been effected with 01, the requisition has been given the "all clear" for the issue of RFQs.
    You have created the release indicators B (blocked), 1 (cleared for issue of RFQs) and 2 (cleared for RFQs and PO).
    Now enter the following as assignment:
    Strategy   C1  C2  C3 ...
    S1                           B (blocked)
    S1         X                1 (RFQ)
    S1         X   X            2 (RFQ/PO)
    4. Release prerequisites
    Define which release codes are involved in a release strategy. Specify whether a code is set for a release status following release, and whether one release status is a prerequisite for another (+).
    Example:
    Strategy   Code  C1  C2  C3 ...
    S1         01    X
    S1         02    +   X
    5. Determination of the release strategy
    Determine the conditions under which each release strategy is assigned. The criteria are account assignment category, material group, plant, and value of the requisition item.

  • LSO Cancellation Workflow issue???

    Hi Experts,
    I have copied the standard LSO Cancellation Workflow WS12000004, whenever i cancel the course in the portal the workflow is triggering and generating 2 parallel work items of Time Dependent Sub workflow . There is no fork in the main workflow even though its generating the same sub workflow parallel. But as per my requirement the sub workflow need to generate once... How can i achieve this???
    Thanks,
    Srikag

    Thanks for your reply...
    Whenever the event is triggering only one workflow is trigerring but its generating 2 same work items parllely, but i am not sure why its happening... Inside the workflow there is a condition based on that it will choose the path as Time dependent or Time independent course these both are 2 different sub workflows... Time dependent sub workflow is trigerring twice...
    I have checked the configuration in that they maintained the same workflow twice for different courses... Do you think this will be the problem...? If so 2 times the same workflow should trigger but in our case only one time workflow is trigerring but its generating the 2 same work items parllely...
    thanks,
    Srikag

  • Leave Cancellation Workflow - WS01000109

    Hey SAPiians,
    We have implemented the "Cancel Leave" service on the ESS at the client's end. We have already implemented and tested the service for "Leave Requests" using workflow "WS12300111".
    Now i have the following questions:
    1. Can the same workflow be used for "Cancellation of leave" ??
        If yes, are the necessary deletions performed from the respective 
        infotypes ??
    2. Can the workflow WS01000109 (Cancel Leave Request) be used for the
        same purpose ?? Where do i need to put the Workflow id in the
        config ??
    Here is what we did...
    1. We made a copy of the workflow WS01000109 (Cancel Leave Request) and did the expected activations in workflow wherever required.
    2. In transaction PTARQ under CUSTOMIZING -> Service-Specific Settings -> Working Time -> Leave Request -> Processing Processes -> Specify Processing Processes for Types of Leave -> Define Absences/Processing Processes, we put this workflow id in the section "Workflow Template" in the cancellation request input box.
    3. We then tested the scenario by raising a request. However, the request gets deleted without any approval and also no workitem is created in SWIA.
    Is there any other setting which needs to be done to activate the workflow ??
    Please guide.
    Thanks,
    Shashank

    hi Shashank
    Use only WS12300111 workflow template for delete,change and applying leave. Am using the same standard workflow for all the three cases its works fine. No need to worry about infotype. If you tag your workflow in cancellation request work item will go to the approver if he approves then run the post documetn which will convert from status approved to posted in tabel PTARQ_HEADER then go to t-code PA30  type the employee number and infotype 2001 and check the overview you can find the type of leave applied and date and all details.
    Regards
    vijay

  • Cancelling workflow in sourcing7

    Hi,
    I am using sourcing 7. My question is, how do I cancel a workflow? I do not see Workflow Definitions -> Current Workflow Processes in sourcing 7.
    Scenario: Contract document is submitted for approval. Approvers receive an email to take necessary action on the document.
    System admin logs in and wants to cancel the workflow. After this the Approvers should not see the pending action item and contract document status will move back to previous phase.
    Appreciate any help.
    Regards
    Moumita

    Hi Palz & Moumita,
    In our landscape we have enabled cancel on Contract Document screen with following option
    1) Copy the standard report for cancelling Workflow and create one restricted to the current Contract Document (This can be done with a hidden filter) - Note for this type of query to work, a new Query group has to be created for Contract Document since the hidden filter would be of Object Picker type
    2) Create a new report for the custom query
    3) Add this report to the "Document Report Configuration" for Contract Document
    To Cancel the workflow -
    1) Open the Contract Document in Workflow
    2) Go to Reports on Contract Document toolbar and run the report to cancel Workflow
    3) New pop up window opens with option to Cancel the Workflow
    Regards,
    Balaji

  • Workflow for Sales Order Release via Status Profile

    Dear all,
    i want to make a workflow for sales order which have 4 User Status in One status profile.
    Once Event triggered for sales order
    1.   Mail should go to main authority with sales order number.
    2.  Once authority will do some changes in the required field then he/she changes
         the user status-1 from defauts as per line Item and mail should go to department no-1 (Head authority).
    3.  Once again same changes in sales order but now user status-2 from user status-1
         as per line Item and mail should go to department no-2 (Head authority).
    4.  Once again same changes in sales order but now user status-3 from user status-2
         as per line Item and mail should go to department no-3 (Head authority).
    5.  Once again same changes in sales order but now user status-4 from user status-3
         as per line Item and mail should go to department no-4 (Head authority) .
    and parrally for each changes of Status mail should also go to User (Event Creator).
    6. Finally mail sholud go to User as you are permitted to do next business transaction for this sales order
    Please tel me the process as i am very new this topic and i am always going to stuck in Binding.
    please help me out.
    Thank You

    Hi Neeraj,
    First of all start with SWELS and SWEL T-Code to check if any standard event is getting triggered or not. If event is getting triggered, then use the same event to trigger the workflow; otherwise create a custom event of BO and use the same to trigger the workflow.
    Hope you are aware of T-Code SWO1 and delegation of BO. The BO used for your requirement will be BUS2000115.
    As you want the workflow to get triggered only for one status profile and one of its status, so use check function module. There set the condition for you status profile and status.
    The FM which you will be using the most is CRM_ORDER_READ. To read the status, you can also use CRM_STATUS_READ_OW.
    Now simply make the approval steps in the workflow using activity. In the activity, you can use the standard method USERSTATUSPOPUP to send the workitem for approval. In each step use the same activity with different agents as approvers.
    Just go with these things and let me know if you get stuck up somewhere.
    Regards,
    Guddan

  • SharePoint Online 2013 Workflows for one List stopped working after 07/08/2014

    Our client host application in Office 365 SharePoint Online 2013, and we just found that all workflows for one list stopped working after 7, Aug 2014. It kept displaying pop-up message "Something went wrong. To try again, reload the page and then start
    the workflow." when manually start a workflow for this List.
    Tested workflow for other list, there's no problem.
    Could anyone can help on this issue?

    Our client host application in Office 365 SharePoint Online 2013, and we just found that all workflows for one list stopped working after 7, Aug 2014. It kept displaying pop-up message "Something went wrong. To try again, reload the page and then start
    the workflow." when manually start a workflow for this List.
    Tested workflow for other list, there's no problem.
    Could anyone can help on this issue?

Maybe you are looking for