N- Level Process Controled Item workflow.

Hi Experts,
I am using Process Controlled item level workflow in SRM 7.0 (WS40000014) . My workflow is working for only one level approval.
I dont know how to increase number of approvers.... Could any one please suggest a BADI and process to achieve this?  
Thanks in advance,
Regards,
Bhanu.

Hi Bhanu,
    Increasing the number of approval level( APPROVAL_INDEX ) is not same as SRM 5.0 in SRM 7.0.
     First you have to implement custom BADI for increasing Process level which is same (APPROVAL_INDEX), then implement another BADI to process the approval level. you can find the sample code for increasing the process level in standard Badi '/SAPSRM/BD_WF_PROCESS_SC'. 
Best Regards,
Saravanan Dharmaraj

Similar Messages

  • Back and Forth Logic in process-controlled (BRF) workflows in SRM 7.0

    Hi all,
    I am using the process-controlled workflow in SRM 7.0.
    The approval itself works ok, but now I am trying to set up the back-and-forth functionality (similar to how it worked for the Badi in SRM 5.0) as default:
    This is what happens:
    Requester creates shopping cart.
    Shopping cart goes for approval.
    Approver rejects SC.
    Back at the requester the SC can only be displayed, but not changed.
    As far as I can tell this happens for any kind of decision set (as long as all items are rejected).
    This is what I am trying to set up.:
    Once the SC is back at the requester, he can either accept the rejection OR change the SC and 're-order' it ie send it back to approver again.
    I know if the requester checks the flag 'Work Item to Requester at Process End' this can be done, but I need the system to have this functionality automatically without setting a flag manually.
    I really appreciate any suggestions on this issue.
    Cheers
    Ulrike

    Dear Masa,
    thanks for your helpful answer. I have an better idea now, but I am still not quite able to set it up.
    I have applied note 1296209.
    When i tried to set up this step I did the following:
    level type of that step I used 'Approval with completion'.
    Created Expression of type SAP Formula Interpreter, with return type Boolean, and use formula:
    0V_WF_CURRENT_DECISI = 'REJECTED'
    linked the evaluation id to above expression.
    Task id for the step is: 40007994 - Accept Decision / Adjust Document
    When i do this and create a SC, my system dumps after clicking on describe requirement::
      The following error text was processed in the system SR7 :  The method could not be found at dynamic call.
    The error occurred on the application server SAP01_SR7_07 and in the work process 1 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
          Method: CALL_RFW of program /SAPSRM/CL_WF_RULE_CONTEXT====CP
          Function: /SAPSRM/WF_BRF_0EXP000 of program /SAPSRM/SAPLWF_BRF_DATA
          Method: PROCESS_SPECIFIC of program CL_CALL_FUNC_METHOD_BRF=======CP
          Method: IF_RULE_COMPONENT_BRF~PROCESS of program CL_EXPRESSION_BASE_BRF========CP
          Method: GET_RESULT of program CL_EXPRESSION_POOL_BRF========CP
          Method: IF_EXPRESSION_BRF~GET_SUBEXPRESSION of program CL_EXPRESSION_BASE_BRF========CP
          Method: IF_FOEV_CONNECTOR~EVALUATE of program CL_FORMULA_BRF================CP
          Method: EVALUATE of program CL_FOEV_FORMULA===============CP
          Method: EVALUATE of program CL_FOEV_FORMULA===============CP
          Method: EVALUATE of program CL_FOEV_FORMULA===============CP
    What I don't understand about your explanation is what you mean by "Acceptance by Contact person". I don't have that option anywhere in my BRF? Is that supposed to show up under Resp. Resolver Name (like RR_MANAGER)?
    Also where did you add that step in Process level configuration? I have 2 approval steps (just approval, without completion) and then i wanted to enter this step after those levels before the automatic system decision.  But i wasn't able as the system doesn't allow you to add a completion step after a 'normal' approval step.
    Cheers for your help
    Ulrike

  • SRM 7.0 Process-Controlled (BRF) Workflow -- Error message to Shopping Cart

    I am modifying a BRF Expression used to calculate approval levels.  During this calculation, I may run into error conditions (e.g. Currency tranlsation not found) that I want to display to the user (in the Shopping Cart).
    I have tried raising the following exceptions:
    /sapsrm/CX_WF_RULE_ERROR.
    /sapsrm/CX_WF_RULE_ABORT.
    Raising these exceptions do result in SLG1 log entries being written, but the User is not informed of the error (ie. at top of shopping cart where other messages display).
    I can probably jump out of the Webdynrpo to read logs, but thought there MUST be some standard way of passing error conditions from the BRF, back to WF, and then back to the Webdynpro Window.
    Anybody raise error messages back to the online user from Process-Controlled Workflow?
    Thanks,
    - Tim

    >
    Saravanan Dharmaraj wrote:
    > Hi Tim,
    >
    >    I am not sure about your business requirement, but if you want to display custom error message while user create a SC, SAP has provided a standard BADI - BBP_DOC_CHECK_BADI. You can implement this Badi to raise a custom error,warning message. You can build your brf logic in the BADI implementation..
    >
    >
    > Best Regards,
    > Saravanan Dharmaraj.
    Hi Saravanan,
    I am actually modifying the Approval Limit Checks (for multi-currency translations) that you recently coded in Maryland.  It can occur that errors occur in determining limits (new Currency translation I just added), or during the lookup of agents (ie user config is inconsistent).
    In these cases, I can make the shopping cart Dump, by raising untrapped error messages, or assertions.   However, I would like to raise exceptions that get trapped (such as the ones I identified in original post), and then make their way to the shopping cart.
    Unless I am missing something, I don't think the WF BADIs, or BRF are gonna communicate errors back to the shopping cart, even though these components are called during cart creation and checks.
    I realize that I can recode the Agent Determination BADIs,  BRF calls, or even read BRF logs within BBP_DOC_CHECK_BADI.  I mentioned this in my original posting as well.
    Anyway, any help is appreciated.
    Thanks,
    - Tim

  • Process Control In Workflow

    Hi Experts,
    I am new to workflow and trying to get familiar with all steps used in workflow.
    Can anybody tell me whats the use of Process Control Step in Workflow.
    If possible please provide some related document.
    Regards,
    Himanshu

    Hi Himanshu,
    I guess you already looked at the SAPHelp? All step types are explained there.
    Regards,
    Martin

  • Problem with Confirmation (BUS2203) Process Controlled Workflow SRM 7.0

    Hi gurus,
    I'm having a bit of trouble with the Process-Controlled approval workflow for the business object "BUS2203" (Confirmation) in SRM 7.0.
    Basically, I've configured it to determine N-process levels, and for each level to retrieve the corresponding agents/approvers. When I am creating the confirmation, I go to the "Approval" tab and I can see all of my approvers there. Nevertheless, the moment I confirm an item (ie, put a confirmed quantity and press the confirm button) first I get the status "Awaiting Approval" and then when I close/or click the refresh button I get the status "Release Rejected".
    Has anyone had this problem before with this workflow? Do you know if this is a standard error, or might I be doing something wrong? I tried to look through the OSS notes, but unfortunately couldn't find anything..
    Please feel free to provide any idea that may be useful!
    Many thanks...
    Adi

    Hi,
    Can you paste your process definition? BRF event and expressions.
    Does it work with SAP sample 1 step approval process definition?
    Regards,
    Masa

  • Is migrating open application workflows to process-controlled WFL required?

    Dear forum members,
    We have upgraded an SRM system from version 5.0 to 7.0 (SP 7) and we have gone live in SRM 7.0 with the old application-controlled workflows still being used for old and new documents.
    We are in the process of changing the workflow to the new process-controlled (BRF) workflow and this works OK for new docments in our test systems.
    Can you confirm if we MUST migrate the old workflows to the new BRF workflow when we activate the new p-c workflow into the live system?
    I would prefer to have the old application-controlled workflow continue for existing document approvals and use the process-controlled workflow for new ones.
    My questions are:
    1. Can we use both application and process-controlled workflows together at the same time (new docs use p-c workflow, existing approvals to continue to use A-C workflow while they run down)?
    2.  If not, can we migrate SC n-step BADI workflow to the p-c workflow (report /SAPSRM/PR_WF_MIGRATION_CFG implies not)
    Any help or advice is appreciated as always!
    Thanks a lot,
    Nick

    hello,
    we are dealing with the same issue in a srm migration from 5.0 to 7.0.
    We have a copy of the production system with a lot of open workitems based on application controlled workflows.
    We build up new process controlled workflows and activated those for the new shopping carts.
    The report for the migration (/SAPSRM/PR_WF_MIGRATION_CFG) of open workitems seems to be not sufficient, because
    - all open workitems are going to be restarted, right?
    we tried to approve old woritems from the powl, that seems to work. Simultaneously brf workflow works fine.
    Right now we are wondering why it should not be possible to finish the old workitems application controlled and the new ones process controlled. Do we miss something?
    Has anybody experiences based on customer projects?
    kind regards
    Carsten

  • Help: Process control - kill itself and its phater

    Friends,
    If I use the Process control. Is it possible to use the Process Control 'Cancel workflow' to kill ONLY the actual sub-wf and its phater, without killing its grandfhater ?
    Grandfhater - WF
    Fhater - Sub-WF
    Actual Sub-WF (Using Process control here)
    I want to kill only this actual and its fhater. I want the grandfhader alive and go on.

    Create Container element[like status] in Father SUB-WF and In Actual SUB-WF.
    Based on condition if you want to terminate Actual SUB_WF and Father SUB-WF then set the set container element status = 'X' and then use process control [terminate workflow] this will terminate Actual SUB-WF.
    then do the binding fo container element status from Actual SUB WF to Father SUB WF.
    Then in the father SUB WF check the container element status . if Status = 'X'. then use process control to terminate the Father SUB WF.
    In the process control use terminate workflow.

  • Approval Level in Process Controlled workflows

    Hi Sap Gurus,
    How can i find the number of approval levels in process controlled workflows for Shopping Cart, Purchase Order....
    Thanks in advance

    Hello,
    IMG: SAP Implementation Guide > SAP Supplier Relationship Management > SRM Server > Cross-Application Basic Settings > Business Workflow > Process-Controlled Workflow > Business Process Configuration > Define Process Levels
    For concerned object type, select "Process Schema Definition" directory.
    Then, select correct process level schema to display "Process Level Configuration" directory: here are the process levels defined.
    Regards.
    Laurent.

  • SRM 7.0 Process Controlled Workflow-Level Type in Process level config

    Hello Experts,
    In SRM 7.0 for Process controlled workflow,for Level Type in Process Level configuration we have 3 different options
    1) Approval with Completion
    2) Approval
    3) Automatic(System User)
    Can you plz explain what is the difference between these 3 diffrent potion for Level Type in Process Level configuration.
    Your help will be highly appreciated,
    Thanks & Regards,
    RKS

    1. Approval with completion : This allows approvers to make any changes to document while approving. Generally you define this type for buyer in SC approval.
    2. Approval :  above minus change
    3. Automatic (system approval) : If no process level is determined, you need to set up a process level with automatic approval to approve the document by system.

  • Approver not determined process controlled workflow in SAP SRM 7.0

    Hello all,
    I have setup process controlled workflow in SAP SRM 7.0 EHP3 for shopping cart approval.
    I have 4 approval levels.
    I have used item-based Decision for entire document because for some items i want system approval.
    In implementation of BADI /SAPSRM/BD_WF_RESP_RESOLVER, in the method /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_AREA_TO_ITEM_MAP, i am skipping the items for which i want system approval.
    Also in method /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_APPROVERS_BY_AREA_GUID of BADI implementation class, i am keeping the approver table empty for the step which i want system approval.
    For example i have 1 item in shopping cart and for 1st step, based on some accouting criteria, i want system approval for 1st level and the workitem should go directly to 2 approval step when shopping cart is ordered. This is not happening.
    But if i have multiple items, and one item should have system approval based on some criteria and the 1st approval level should be system approval and other item should go to the 1st approver. This is happening and showing 'system' approver for item1 and 'appr_xyz' for item 2.
    For shopping cart having only 1 item, If i approve the shopping cart in this state only, it doesn't go to any approver and is not usable.
    am i missing anything in BADI /SAPSRM/BD_WF_RESP_RESOLVER??
    Please let me know.
    Regards,
    Yayati Ekbote

    Hi Adrian,
    Yes it is possible to display custom workflows in the Universal Worklist,  However, I am not sure what you are trying to do with a routing table.  If the workitems are of type decision, you can use UserDecisionHandler (action handler) configured in the XML file to use the Approve/Reject functionality - we are talking about webflow connector here correct?  R/3 connector?
    Regards,
    Beth Maben
    EP - Senior Support Consultant II
    SAP Active Global Support
    Global Support Centre Ireland
    **SDN Forum Moderator:
    SAP Enterprise Portal: Application Integration
    **SDN Universal Worklist Wiki:
    http://wiki.sdn.sap.com/wiki/x/ehU

  • Process controlled workflow - SC process schema evaluation

    Hi experts,
    at the moment I'm using the n-step item level approval in SRM 5.0.
    We are implementing SRM 7.0. With the new process controlled workflow I'm not sure how to
    implement the logic of our "old" system.
    Depending on category and item value the SC item has to be approved by 0 - 7 users.
    I've created an event which finds a Z-process schema via FM.
    In the FM I've tried to change the process schema (debugger) for one SC item.
    But the schema has been changed for all items.
    Is it possible to use different process schemas for items?
    When yes how can I set the schema e.g.
    item 10 schema1
    item 20 schema1
    item 30 schema2
    item 40 schema1
    Thanks in advance for your inputs!
    Regards
    Stefan

    Hi,
    Schema Evaluation is document header level.
    There are 2 ways for implementation.
    1. Schema Evaluation returns Schema name. For example, 1 step approval, ... 7 step approval
    2. 1 Fixed Schema and 7 level evaluations. 1 Schema has 7 approval steps and each evaluation returns true or false.
    You have to implement GET_AREA_TO_ITEM_MAP method of Agent BADI to exclude/include items.
    BTW. If you set workflow framework as Application-Controlled Workflow, your old workflow logic works without any change.
    Regards,
    Masa

  • Process Controlled Workflow - 1-step approval for shopping cart approval

    Hi,
    I have configured a one-level approval for SC (Process Controlled Workflow):
    Object Type: BUS2121
    Additional 1 level under schema: 3C_SC_600_000 (the last level is the automatic approval)
    Level Type: Approval with completion
    Eval ID: 0EV_SC_SL1
    RR Name: RR_SPENDING_LIMIT_APPROVER
    RR Param: USTONY.Y (I hardcoded it using my user ID, for the moment)
    Task ID: 40007953 (I have checked, it's generalized as well)
    Decision Type: Item-based decision for entire document
    For PPOMA_BBP:
    Under my org unit (Position):
    Approval Limit: 1000
    Output Limit: 1000
    I didn't do any BADI implementations yet.
    During creation of SC by other user, before "Order" the SC, the approval preview can show correctly that the Processor is as indicated in the config.
    Once the SC is ordered, the whole step is gone and the event linkage becoming delinked (because there is error, and according to the config in SWEQADM).
    However, I cannot find the workitem (no workitem generated) and SLG1 does not give any clue whatsoever.
    I tried debugging method APPROVAL_LIMIT, and it seems fine as well.
    Please help, what did I do wrong here?
    Thanks,
    Tony Y

    Hi Sahil,
    I even changed to first process level to:
    Level Type: Approval
    Eval ID: 0EV000
    RR Name: RR_MANAGER
    RR Param: (Blank)
    Task ID: 40007953 (I have checked, it's generalized as well)
    Decision Type: Decision for entire document
    Under PPOMA_BBP:
    I made myself as a head of the org unit with the role manager.
    The requester is "Exclude" the role manager.
    The agent can be determined now.
    But the workitem ID is still cannot be generated. It's always no workitem generated.
    Please everyone, any help?
    Thanks in advance,
    Tony

  • Error during approval Process flow in Process controlled workflow

    Hello Experts,
    We are in SRM 7.0 classic scenario using Process controlled workflow.WE recently connected a new backend R/3 system to our SRM system i.e we now have 2 R/3 backend system connected to SRM system
    It is regarding the two new additional account assignment categories that came into picture when we connected the new R/3 backend system to our SRM system, i.e. Asset and Network.
    There seems to be some problem with the approval workflow for those SHC, that have such Acc *** Cats.
    Please find below my obeservations:
    - if you have just one line item in the SHC, and this item is either booked on Asset or on Network, than everything goes fine. After the Acc *** approval, the PR is created in R/3
    - if you have SC with a mix between an "old" Acc *** Cat (Cost Centre, WBS and Order) and one of the "new" Acc *** Cats, than the workflow is not working as required --- the manager, that is responsible for the accounting approval of the two positions (e.g Cost Centre and Asset) gets only one work item in his approval overview --- in that work item, the two positions are there, but the Asset one is grayed out --- so, the Manager approves only the Cost Centre positions and than the SC is no longer with the approver --- if you observe the SC now from the requisitioner point of view, the status of the line items in the approval process overview of both(!) lines is "approved", but the overall status of the SC is still "in approval"
    Can you all experts plz let us know why this is happening and how this can be resolved?
    Any pointers will be highly appreciated.
    Thanks & Regards,
    RKS

    Hi,
    What is Resp. Resolver Name and Decision Type in your Process Level Definition? Did you create custom agent BADI implementation?
    Regards,
    Masa

  • SRM 7.0 Process Controlled Workflow change

    Hi
    I have a SRM 7 process controlled Shopping cart workflow working ok, Approval based on value levels. The customer wouldlike to change this so that approval is also based on cost center attributes and also want at each approval level to have a reviewer.
    Could anyone advise me how to add in a reviewer, as well as an approver for a particular process step, and also confirm that to have the cost center attribute taken account of at each process step, i would have to develop and code a new expression / evaluation ID, rather than use existing one.
    Many Thanks
    john

    Hi John,
    Reviews are common for all process level.. itu2019s not process level specify like approvers.. Also we can add reviewers dynamically by a simple BADI implementation and configurations as follows..
    BADI Implementation:
    BADI : /SAPSRM/BD_WF_RESP_RESOLVER
    Enhancement Spot: /SAPSRM/BD_WF_AGENTS
    BADI Definition : /SAPSRM/BD_WF_REVIEWER_RULE
    Configuration:
    We can see Reviewer folder for all process schemas..
    For adding approver or pool of approvers for a particular process level, review my answer in the following forum.. Re: SRM 7.0 SP05 - BRF Item level approval does not work
    Thanks!!
    Bharath

  • SRM 7.0 - Process controlled workflow

    Hi,
    Landscape -  SRM 7.0 SP05
    Workflow - Porcess controlled
    Scenario - Self service procurement
    Problem:
    1. We have mulitple level approval workflow for the shopping cart. I am using standard workflow task- 40007953 and using /SAPSRM/BD_WF_RESP_RESOLVER badi to determine agents.
    2. All the potential approvers (managers) are determined correctly by this badi but the issue is work-item is sent to all the approvers at the same time where as the requirement is to sent the work-item to each approver in series i.e. only when the work-item is approved by the lower level manager, it should go to the higher level manager.  Currently, this workflow task sends the work-item to all potential approvers at one go who can start working on parallely which is not desired.
    Could anyone please help me to resolve this?
    Please note that adding additional process steps in the process-level configuration was the option but we could not opt for that at this point of development as we have gone too far in terms badi development for agent derterminiation
    Thanks & regards,
    Amit

    Amit,
      It is not possible to send the work item to people in sequence by configuring only one process level. If you have only one process level, the agent determination will only be applicable to that process level. If you are trying to assign multiple agents to that step, then all will get the work item at the same time.
    I recommend doing one thing, Create multiple process levels(= no of approval levels you want). For each process level you keep same event and expressions. But your agent determination badi implementation need to be tweaked. Here is how you can do that
    Use Parameters along with agent determnation badi implementation. In other words derive Agents based on the value of parameter using your badi implementation. This parameter can be configured in Process Controlled Workflow Configuration.
    Example,
    Process step 1 - WF_BADI - Parameter1
    Process step 2 - WF_BADI - parameter2
    Now write some code in the WF_BADI to pick up particular agent if parameter value is Parameter1 , pick another agent if parameter value is parameter2. Doing this way you wont ve to redesign your BADI implementation as you are able to break up the Agent logic based on parameter values.
    Virender Singh

Maybe you are looking for