Overwrite sec level in order to restart workflow especially in parked SC

Dear Friends
how can you achieve generally the following requirement.
Generally in our company all user have the security level BBP_WFL_SECURITY= 4 in the personalization tab of TXN
SU01.
How to achieve that workflow is always restarted when changes are made in parked SC. After this changes are
made the user will order this SC.
Anyhow it is not possible to overwrite security level BBP_WFL_SECURITY= 4 which is set in the personalization.
Because after clicking Order button the privously determined  agents are displayed as Approver.
Regards
Marco

Hi,
did you mean BBP_WFL_SECUR_BADI ???
if so,  sorry I forget to post our
implementation in this BADI due to which we have tried to achieve this req.
Regards
Marco
Z_EBP_WFL_SECUR_BADI -
our implementation
IF i_e_header-created_by =  actual_user.
SELECT * FROM sww_wi2obj INTO TABLE lt_sww_wi2obj WHERE
    instid = object_id
    AND typeid = 'BUS2121'.
    LOOP AT lt_sww_wi2obj INTO ls_sww_wi2obj.
      SELECT * FROM swwwihead INTO TABLE iswwwihead WHERE
        wi_id = ls_sww_wi2obj-wi_id AND
        wi_stat = 'WAITING'.
      IF sy-subrc = 0.
        new_sec_level = 2.
        EXIT.
      ENDIF.
    ENDLOOP.
ENDIF.

Similar Messages

  • Work Order Release Approval workflow

    Hi All,
    I am trying to setup Work Order Release Approval workflow. I have set its AME using supervisory level as the action type. When I tried set work order status, I had to set the department as I set department attribute as its AME condition, and work order status changed into Release - Pending and form become disable.
    Where can the supervisor make his/her approval to relese the pending status?
    I tried the Maintenance Super User page, but it can only review.
    Any help is greatly apprecaited.
    Thank you,
    Iqbal

    HI
    Please post EBS release version da and platform details
    1001759 wrote:
    Hi All,
    I am trying to setup Work Order Release Approval workflow. I have set its AME using supervisory level as the action type. When I tried set work order status, I had to set the department as I set department attribute as its AME condition, and work order status changed into Release - Pending and form become disable.
    Where can the supervisor make his/her approval to relese the pending status?
    I tried the Maintenance Super User page, but it can only review.please see if this helps you
    follow this navigation
    1. eAM
    2. Work Orders > Query for existing unreleased work order.
    3. Release it & submit for approval.
    4. Approve the WO.
    ;) AppsMAsti ;)
    Sharing IS Caring

  • Restarting workflow in SRM 7.0

    Hi,
    In SRM 5.0, we could restart workflows manually with triggering an event of the BOR object manully.
    Is there any similar way of doing it in SRM 7.0? This is sometimes required, for example why the approver rules are changed and some more reasons. The first level does sometimes delete the active workflow and starts a new one.
    I tried triggering the event "READY_FOR_WORKFLOW" of class "SAPSRM/CL_WF_PDO" by passing the GUID of the shopping cart and also passing event container value of Initiator. the workflow is started and it is going to error.
    Can anyone help in this case ? Any other way of doing it?
    Thanks,
    Sivagami

    Hi,
    We have some custom code to restart workflows in SRM 7.0. But I believe the standard must offer a standard tool to restart workflow instances for technical administrators. All workflow I know can be restarted with standard tools. In most cases this is possible with triggering an event.
    For example a new Shopping cart workflow could be manually triggered in SRM5 with the standard report u201CBBP_PDH_WFL_DB_UPDATE_BACKu201D. I believe trigger a bus2121 is also possible in the meantime. What program should a customer use in SRM70?
    Thanks,
    Sivagami

  • Substitution and activated the same at the line item level in order to subs

    I have created a substitution and activated the same at the line item level in order to substitute the ZRSPL (Payment Block) field by a constant value and a vendor invoice is posted using Transaction FB60. But the same is not working. When I post a vendor invoice using FB60, Payment Block field is being shown as blank instead of the constant value which I want to substitute.
    >
    > My prerequsite is mentioned below :
    > BKPF-TCODE = 'FB60' AND BKPF-BUKRS = 'ABC' AND ( BKPF-BLART = 'KR' OR
    > BKPF-BLART = 'KY' ) AND BSEG-DMBTR > '10000'

    Hi,
    I am not understanding the logic behind the prerequisites mentioned in your query.
    Payment block field exists only for vendor related line item.  However, you have not mentioned vendor reconciliation account in the prerequisites.  It means, this substitution will trigger for all the line items which is wrong.
    Or try following  options.....
    1) Substitution->Simulation
    2) Extras->Expert Trace
    Best Regards,
    Madhu

  • Purchase order release strategy Workflow not working

    Hi All,
    I am working on PO Approval release strategy and it is not working fine . The release strategy set up is configured by my functional consultant . I just copied the standard workflow template WS20000075 and making changes to my custom workflow template . When ever po is created an event "RELEASESTEPCREATED" get triggered and the first approver receives an workitem and when he approves it goes to Second Approver and it is working fine . But when rejected then a notification email goes to initiator . Now when an initiator login into ME22N and made any changes ( even material text change ) in it then again "RELEASESTEPCREATED" event getting triggered . But I need to trigger my workflow only when there is change in PO Net value .
    Kindly help me how to achieve this functionality .
    Thanks and regards
    Dilip

    Hi Vikram,
    There is already an existing entry for BUS2012 with event CHANGED against the change doc EINKBELEG .
    Acutlly when login as initiator and try to change PO through ME22N here are my observations :
    case 1:   When Buyer click on  " Cancel Reject " button and do any changes ( even text change ) then RELEASESTEPCREATED and CHANGED events  are triggering  . But since the event linkaged is set to RELEASESTEPCREATED workflow get restarted again.
    Even the CHANGE event does'nt have 'RELEASECODE' as parameter to restart workflow .
    Case 2:  When Buyer doesn't click on " Cancel Rejection" buttion and do any changes then only CHANGE event get triggered
    which do nothing since there is no event linkage .
    Is to  click on " Cancel Reject" button mandatory ? .  But even though we make " Cancel Reject"  as Button mandatory then RELEASESTEPCREATED Button triggering for any change but we need to trigger it for only net Value change .
    Thanks and regards,.
    Dilip Kumar

  • Purchase Requisition to Purchase Order conversion through workflow

    Hello Experts,
    My requirement is to create purchase requisition to purchase order automatically through workflow. How to proceed with these conversion, since am new to workflow please help me with the  valuable inputs.
    Thanks,
    Naveen

    How does the senior person approve? using workflow or using transaction ME54N?
    if it's the standrad transaction then again, use a user exit or the released event.
    even if the approval is done in the workflow I would not recomend using creating the purchase order as part of the workflow since this is not a workflow issue, but if there is no other option create a new method in BUS2105 (use delegation) and call the BAPI in it.

  • Need BAPI for Purchasing Order Reject through Workflow

    Hi All.
    I need a bapi to reject Purchase Order(PO) through Workflow. i've found some to release but not to reject, ('08' status Code). Can anybody hlp me please.
    Thanks & Regards,
    Mani.

    You can check standard Wflow Template WS65400030
    I think you can use Method ResetRelease of businress Object BUS2012

  • Restart Workflow SWPR

    Hi Experts,
                      Sometimes in SWPR Restart Workflow i find Errors in Workflow but when i select the workflow and click on the restart flag still the workflow is not Restarting and i find it in error status only.Mostly PO/PR release workflows. Please help me on this How to restart workflows.
    Regards,
    Hari

    Generally as I far I know in my limited knowledge, you restart a WF:
    1. Some step during execution hanged or erred out due to unknown reason may be due to lack of authorization
    2. Rule failure
    3. Time gap
    4. Missing data
    Overall and simply to say to use this transaction where it is possible to continue from the exact point of failure without a new instance.
    Regards, IA

  • How to restart workflow step by RIDC?

    Hello everybody,
    I have a problem with the writing records to the wf_in_queue.hda. Horrible... ;o)))
    I'd like to restart workflow steps automatically by RIDC (java code).
    Can you write me which java code can i use?
    Thank you
    Martin

    Not sure if RIDC has necessary functions.
    Take a look at CIS: http://docs.oracle.com/cd/E21764_01/doc.1111/e10807/c10_cis.htm#i1092638

  • Change or Restart Workflow and Skip to Workflow

    You have the option in server settings to "Restart current workflow for the selected projects", with the choices of skipping to current workflow stage or to a particular workflow stage. Using a new 2013 project server workflow neither of these
    choices work. The project in each case is returned to the very first workflow stage.
    Is this a bug or badly designed workflow?
    Is this also the case with legacy 2010 workflows?
    rgds
    Mike
    Mike Mahoney

    Mike,
    Thanks to John on the Product Team, I think I can explain what is going on.
    I am going to assume you have a workflow similar to the one below? Some simple logic, a wait event and a transition or some type.
    As the workflow progresses in the above case, it will log a message out, then wait for the submit button to be pressed before transitioning.  If you try to use the Change / Restart workflow function and choose Restart  > Skip to Stage 3, what
    you will see is the workflow restart, log Stage 1 to the history list, and then wait for input. There is no skipping through as the workflow is waiting for the event.
    The new workflows, whilst allowing looping etc, are essentially still sequential in nature, so to skip though the various stages, they need to start at the beginning and then progress through the stages depending on the logic in the stage transitions.
    Just like in 2010, to get something to progress, you need to introduce some special 'Skip to Stage' logic (for want of a better phrase), with this logic, you can tell the workflow 'If the workflow is being run normally, or restarts the workflow and includes
    this stage' execute the actions within. This is achieved by using the 'Include Stage' condition I mentioned in a post above.  In the example below, I have wrapped the logging and the Wait for submitted event in an 'Include Stage' action (and added
    some extra logging)
    Now when this workflow runs normally, it will go through and execute everything, including the bits inside the 'Include Stage' action because the workflow was started normally (as in the name). 
    However, if I choose to restart > Skip to Stage 3 for instance, the workflow will realise it is in 'Skip to Stage' mode and not execute anything in the 'Include Stage' action as the workflow is not being run normally, nor is that stage included (we
    are skipping to Stage 3). As the Wait for Submit is not executed, the workflow will not wait for the submit button to be pressed and progress without issue to the desired stage. From a logging perspective, you should see something like 'Stage 1 > Leaving
    Stage 1 > Stage 2 > Leaving Stage 2 > Stage 3 > Included Stage 3.
    It took some time, but I hope that explains what your seeing. If it doesn't, well it does give a good overview of how to use Skip to Stage logic in 2013 workflows.
    Alex Burton
    www.epmsource.com |
    Twitter
    Project Server TechCenter |
    Project Developer Center |
    Project Server Help | Project Product Page

  • ASCP: How do I get the list of 1st level planned orders using msc_full_pegging table

    How do I get the list of 1st level planned orders using msc_full_pegging table, is any one having the script.

    Do you mean supply_type? If so, yes it will be in pegging table as supply_type or otherwise you can join this table with msc_supplies by joining transaction_id column and get the order_type from that which will be the supply type.
    Thanks,
    Abhishek Sharma
    P.S:- Try opening the discussion in a separate window and see if you get the option to mark it correct or helpful,

  • Restart workflow

    Hi all,
    I need to restart workflow which is in status ‘STARTED’. I’ve tried transaction SWPR but there I can restart only workflows in status ‘ERROR’.
    Is there possibility to restart my workflow?
    Thanks for your answers,
    Kind regards,
    Petr.

    hi petr pinos,
    Try with this wapi " SAP_WAPI_ADM_WORKFLOW_RESTART" where you have give the workitem id as the import parameter and the person responsible.
    Keep in bind the workitem id that you are going to give in this wapi the workflow workitem id not the task workitem id.
    And one more thing is, the person responsible should have the authorization for triggering this workflow if not make the workflow as a general task.
    Hope this will solve your problem.
    Regards
    Balaji E.

  • Workflow on invoice parking and posting

    Hello,
    Can anybody guide me how to configure the workflow for invoice parking and posting in detaills?
    Thanks
    Nilesh

    hello ,
    Prerequisites
    In the Implementation Guide (IMG) for Logistics Invoice Verification, you can specify for which company code, which vendors, which invoices, and above which amount a document is subject to release. In an invoice document that is completed for posting, the amount that is subject to release is based on the gross amount. (Logistics Invoice Verification ® Document Parking ® Define Release Criteria)
    Technical Implementation (MM-IV-LIV)
    Object Types
    Object technology is used to create the interface between the ERP functions and the Workflow system. The information given below is primarily of a technical nature and is not necessary for an initial overview.
    Incoming invoice
    Object type Bus2081 (Incoming invoice)
    Workflow Template
    The actual operational procedure is implemented as a workflow template. You will find this workflow template in your ERP system.
    Workflow template: WS 20001004
    Description: Release the Completed Log. IV Document
    Triggering Event for Workflow Template
    The event for workflow template IncomingInvoice.CompletedToRelease is triggered if the parked document is complete for posting (RBKP-RBSTAT='B') and is subject to release (RBKP-RFGKZ='X').
    This coupling between the event and the workflow template to be started is deactivated in the standard system. If you want to use the workflow template, you have to activate it in Customizing for Logistics Invoice Verification.
    User Roles
    You complete parked invoices for posting and release them at the following organizational levels.
    Processor Determination: Clerk Responsible for Releasing Invoices
    If you have already maintained an organizational unit, you can use it here.
    If no organization unit is available, create an organizational unit that includes the people responsible for releasing invoice documents that are complete for posting.
    Use the organizational unit in Customizing for Logistics Invoice Verification in the activity for defining release criteria.
    Processor Determination: Clerk Responsible for Completing Invoices for Posting
    If you have already maintained an organizational unit, you can use it here.
    If no organization unit is available, create an organizational unit that includes the people responsible for completing parked invoice documents for posting.
    Link the organizational unit to the single-step task TS20000879:
    ·        By simple processor assignment
    All users in the organizational unit receive the work item.
    ·        By defining an individual role
    Only selected users in the organizational unit receive the work item.
    Authorization Objects
    You must have maintained the authorization to display invoices (activity 03, M_RECH_WRK) for users who are responsible for releasing invoices.
    You must have maintained authorization to change parked invoice documents (activity 77, M_RECH_WRK) for users who are to complete parked invoice documents for posting.
    Several other specific customizing steps are necessary for this workflow template in addition to the general customizing that is necessary to make sure that the workflow system functions properly.
    Activating Event-Receiver Linkage
    The event IncomingInvoice.CompletedToRelease (Invoice document completed for posting and subject to release) for object type BUS2081 (Incoming invoice) is an event that triggers workflow template WS 20001004 and is entered in the event linkage table as such as the standard event.
    This coupling between the event and the workflow template to be started is deactivated in the standard system. If you want to use the workflow template, you activate the linkage between the triggering event and the workflow template as receiver of the event in Customizing for Logistics Invoice Verification. (Logistics Invoice Verification ® Document Parking ® Activate Workflow Template for Release for Posting.)
    Use
    The release of invoice documents that have been completed for posting is supported by a link to a workflow procedure.
    Prerequisites
    The event IncomingInvoice.CompletedToRelease must be triggered for an invoice (BUS2081) so that a release procedure is started. We recommend implementing this workflow together with the SAP workflow template WS20001003.
    In Customizing for Logistics Invoice Verification, you maintain the activity Define Release Criteria under Document Parking.
    Features
    Release for Posting
    In the release step, the person responsible for releasing the invoice document decides if it should be released. The system uses the virtual attribute ReleaseAgent for object type BUS2081 to determine the person responsible for releasing the document. The release criteria in Customizing for Logistics Invoice Verification are checked for this.
    If the person responsible decides to release the document, it is first released in the background and then posted.
    If he or she decided to reject the document, it is forwarded for further processing to the accounts payable clerk responsible for completing invoice documents for posting. The rejection reason should have been entered using the memo function.
    Completing Invoices for Posting
    The accounts payable receives a work item in his or her inbox. In this work item, he or she can read the reason why the invoice document was rejected and change it. If the accounts payable clerk parks the changed invoice document, saves it as complete, deletes it, or posts it, the workflow ends. It makes sense to save the invoice document as complete and therefore trigger the release workflow again, assuming that the invoice document is subject to release.
    If the invoice document is parked, deleted, posted, or released in the background outside the workflow process, the workflow ends.
    regards
    venga

  • Tcode for Assign CoCode to a Workflow Variant for Parking Document

    HI, what is is the Tcode and path for Assign CoCode to a Workflow Variant for Parking Document.
    regards
    JK

    HI Aravindh Ji,
    Thanks for ur reply.. my company currency code is SGD... iam trying to assigning sap standard workflow variant 0001 to my company code its showing error message ur COMPANY CODE CURRENCY IS NOT SAME AS WORKFLOW CURRENCY. In our group remaining company codes using same work flow...their currency codes also SGD.. cu plz advice me to solve this problem.
    regards
    JK

  • Purchase Order Release Strategy Workflow

    Dear SDNers,
    I created a custom workflow to trigger workflow when PO created. This workflow send mails to portal for approval to approve the release stratagies of purchase order.
    From portal side its working fine. Once the approval approves, user decision step going to next level. every thing is fine from portal side.
    But if they go for R3 side to release PO at ME29N, here facing probelm
    Suppose, Workitem is waiting at level1. Approver1 recieves used decission step at portal. But by logging into R3 system and release PO, the workitem which is at approver1's inbox has to vanish from his inbox. Its not happening now.
    What I hav to do. Kindly let me knwo.
    Thanks in advance,
    Regards,
    Venkat

    Hi Venkat,
    Two things you should change here:
    1. The Event that triggers your workflow should be BUS2012(RELEASESTEPCREATED). This event occurs when a release strategy is activated for a PO due to various reasons.
    2. You workflow should have a 1 : 2 fork . One path (fork path) should follow the User Decision path using a portal and the other should be a asynchronous workitem with the following 3 as terminating events:
          BUS2012         RELEASED
          BUS2012         RESET
          BUS2012         SIGNIFICANTLYCHANGED
    The workitem can be with or without agent.
    This should help you.
    Regards
    Gautam
    Edited by: gautam maini on Jun 28, 2011 5:13 PM
    Edited by: gautam maini on Jun 28, 2011 5:14 PM

Maybe you are looking for