Change Shopping Cart Workflow

Trying to figure out a way to route the shopping cart back to the requestor at all points during the approval process. There are customizations made to the workflow such as a finance reviewer, a commodity approver, manager (org hierarchy) and a financial approver (for $50K+). Client wants shopping cart to come back to approver at any point. Any suggestions?
Thanks in advance.

Basically, what we want to do is to route the shopping cart back to the requestor at any point in the approval process. Commodity Approval is based on material group, Manager Approval is based on shopping cart amount and org hierarchy, CFO approval is based on shopping cart amounts over $500k.Approval amounts are nased on a Z-Table. Using workflow WS14000133 n-step approval of shopping cart (BADI)
Thanks for the response so far! Let me know if you need any additional info MJ!

Similar Messages

  • Shopping Cart Workflow Problem is not able to determine agents

    Hi Experts,
    We are facing a problem in SRM 5.0 shopping cart workflow. Normal flow is as follows: -
    Create SC > Goes for Approval to level 1 approver > Item appears in Approver's list > L1 approver approves it > Follow - on Document is created.
    Currently while creating shopping cart, we are able to see name of approver in approval preview. Still that item doesn't appear in approver's list. We checked in workflow log, it is getting stuck in task which is supposed to determine next level approver.
    Currently approval is done using workflow template WS14000133 and BADI BBP_WFL_APPROV_BADI. In this BADI we are able to find approver perfectly but that is not getting filled in the container of workflow. The Approver List of workflow container is appearing blank.
    Any pointers to this issue will be helpful
    Thanks
    Siddarth

    Hi Ricardo,
    In BBP_WF_APPROV_BADI we have implemented Method GET_REMAING_APPROVERS. The code snippet of method is as follows: -
    CALL METHOD EXITINTF->GET_REMAING_APPROVERS
      EXPORTING
        IN_UPDATE = IN_UPDATE
        DELETE_REJECTED_ITEMS = DELETE_REJECTED_ITEMS
        ITEM_DEDUCT_RESET = ITEM_DEDUCT_RESET
        ITEM_APPROVAL_HISTORY_TABLE = ITEM_APPROVAL_HISTORY_TABLE
        APPROVAL_HISTORY_TABLE = APPROVAL_HISTORY_TABLE
        ACTUAL_APPROVAL_INDEX = ACTUAL_APPROVAL_INDEX
        GUID = GUID
        OBJECT_TYPE = OBJECT_TYPE
        OBJECT_ID = OBJECT_ID
      IMPORTING
        APPROVAL_TABLE = APPROVAL_TABLE
        APPROVAL_ADMINISTRATORS = APPROVAL_ADMINISTRATORS
        ITEM_APPROVAL_TABLE = ITEM_APPROVAL_TABLE
        NO_FURTHER_APPROVAL_NEEDED = NO_FURTHER_APPROVAL_NEEDED
      CHANGING
        ITEM_APPROVAL_OBJ = ITEM_APPROVAL_OBJ.
    Now can you please tell me which variable I am suppose to look at?
    Thanks
    Siddarth

  • Wrong Agent Determination in Shopping cart Workflow

    Hi All,
    I am having problem in shopping cart workflow.
    If we create shopping cart with 15 or more line items then Approval is going to wrong line item cost object owner. However if we create shopping cart with 14 line items then it showing correct financial Approver. Even we raised one more shopping cart with value similar to 15 line items shopping cart and it also going to correct Approver.

    After 2 days of debugging i found where is the problem. I am explaing this below.
    First i created 2 Shopping cart. First one has 14 Line item which shows correct Agent.
                                                  2nd one has 15 Line item which shows wrong Agent.
            CALL METHOD l_o_pdo_sc->get_item_detail
              EXPORTING
                iv_item_guid = l_r_item_guid->guid
              IMPORTING
                et_item      = l_i_item_i
                et_account   = l_i_account_i
    *MOD-002:Begin
                et_limit     =   l_i_limit_i.
            APPEND LINES OF: l_i_limit_i TO l_i_limit.
            APPEND LINES OF: l_i_item_i TO l_i_item,
                                           l_i_account_i TO l_i_account.
    Case for First SC.
    l_i_account_i  has value of Line Items. First line item suppose 1L.
    After appending the l_i_account(2nd itab) has also first .line item 1L.
    Case for 2nd one.
    l_i_account has value of Line Items. First line item 1L.
    But after appending the l_i_account has no first line item 1L.
    Please give some solution to this problem.

  • Change Shopping Cart in status "Awaiting Approval"?

    Hi there,
    Quick question: Should a user be able to change thier shopping cart if it is still in "Awaiting Approval"? It would seem like a logical thing for the user to be able to change the quantity, date etc of the item before it is approved?
    I have been looking at template SAPLBBP_SC_UI_ITS 120 and it seems SAP standard prevents this?
    How would I allow users to be able to change shopping carts in awaiting approval state?
    Any help would be greatly appreciated, thanks
    Lynton

    BBP_WFL_SECURITY badi may helps or  via su01 personalisation tab security.
    helps you . keep value HIGH
    Shopping cart approval - shopping cart not changeable
    br
    muthu

  • How to change shopping carts of other users

    Hi Experts,
    Please advise if there is any transaction which SRM admin can use to change shopping carts of other users. I found that BBP_MON_SC is only able to delete the shopping carts.
    Regards,
    Kamal

    Hi,
    As Manish told, you can not change shopping carts for other users. I think as per as my knowledge even SAP will not recommend these type of funcitonalites.
    thanks
    Ravi

  • Shopping Cart Workflow - "Wait for change event" not firing?

    Hi there,
    I have a scenario where if I create a shopping cart above my spending limit it will go into the approver's inbox, that is fine.
    Now if I change the total value of the shopping cart to be within my spending limit the original workflow should be "logically deleted" and a "no step approval workflow" should be triggered.
    I see when the SC workflow triggers it also branches with a "wait for events", so that if it changes etc it will get caught here.
    When I change the SC it does not do anything, the value of the cart changes but it still sits in the approvers inbox and the "no step approval workflow" does not trigger.
    We are busy upgrading to SRM 5.0, it worked perfectly in the SRM 3.0 system we had.
    Any ideas what would cause the "change event" not to fire?
    Thanks for the help
    Lynton

    Hey Masa,
    You are the man!! That solved it.....I have implemented the BBP_WFL_SECUR_BADI and for whatever reason I set the security level to 4 when it should have been 2.
    4     "High" (workflow is never restarted when changes are made)
    3     "Medium" (WF restarted conditionally when changes are made)
    2     "Low" (workflow is always restarted when changes are made)
    1     "None" (changes to the object are not allowed)
    0     "Not defined"
    Thanks for the help
    Lynton

  • Shopping Cart workflow retrigger for changes done to SC already created

    Hi all,
    A shopping cart is created and later on in "Check Status" when the shopping cart is opened in change mode and any changes are made to the shopping cart either header or item level, the whole approval workflow is retriggered and the approvers are determined again.
    We have a scenario where for a particular account assignment category the approvers are added manually - ad hoc approvers through the "Add Approver" in "Approval Preview". For these shopping carts with manual approvers when in "Check Status" any changes are done to header or items of the shopping cart, the whole approval workflow is retriggered and the manual approvers previously added are refreshed as per standard SAP.
    I have to put a check in DOC_CHECK badi for the existence of approvers. If no approvers found an error message has to be thrown for adding the approvers manually. I am doing this by reading the approvers from the container for a cart created already. But when changes are made and the workflow is retriggered, the workflow container contains only the previous approvers and not the refreshed ones. So this is not captured in DOC_CHECK badi.
    Is there any way to capture the retriggering of workflow in DOC_CHECK badi, so that the check for approvers works fine even after a change being done to a shopping cart which is already created.
    Thanks and Regards,
    Asha

    Try this FM BBP_PDH_WFL_APPROVAL_SIMULATE
    Regards, IA

  • Shopping Cart Approvers for changed shopping carts

    Hi
    We're currently working on a patching process and are having problems with shopping cart approvals
    We have a 2 stage approval for carts over £75K
    The scenario that is not working is
    The approver 1, approves the cart
    Then approver 2 rejects the cart
    The shopper then changes the cart by increasing the value
    The workflow should resend the cart back to approver 1 but it sends the cart to approver 2
    What changes need to be done to send the cart back to the original approver ?

    For  for n-Level Approval Shopping Cart sub workflow( 14000134 ) the workitem status  is set in the container element APPROVE_OR_REJECT when Sc is rejected it is set other than Zero and when is approved it is set to ZERO check in the workflow log whether this conatiner element is getting populated or not.

  • AD-hoc approver n step item level shopping cart workflow

    Hi
    We are on latest version of SRM and using n step item level SC approval workflow.
    The scenario goes like this:
    -     Requester creates shopping cart and workflow goes for two step approval.
    -     In the approval preview the requester is able to see both levels of approvers, which is correct.
    -     Requester now selects second level approver and replaces him with a ad-hoc approver. WE DO NOT WANT THIS.  Requester should NOT be able to replace an approver determined by approval badi. However should be able to extend approval step with ad-hoc approver say third level approver a ad-hoc approver. Also he should be able to change AD-HOC approvers ONLY.
    Thanks
    Joe

    Jo,
      You may be able to achieve it in the BADI BBP_WFL_SECUR_BADI .
    You can use the Business Add-In (BAdI) BBP_WFL_SECUR_BADI to determine whether
    A shopping cart can be changed during the approval process
    The approval workflow restarts when changes are made to the document
    A reviewer/approver can be added or changedThese are the call scenarios (see import parameter SCENARIO).
    Regards,
    Suren

  • Change shopping cart

    Hello all, I am confusing in a point, I have this issue:
    I have a shopping cart with 1 item and 2 approvers
    First approver reject the SC
    Creator of shopping cart can change this shopping cart after the approver reject it?
    When the shopping cart can be changed?
    Thanks
    Rosa

    Hi ,
    Whether the SC requester can change the SC or not is determined by the parameter "BBP_WFL_SECURITY" under the personlization tab in trascn PFCG for the SC creator role(e.g. EMPLOYEE role).
    When the Approver rejects the SC,the witem is sent back to the requester informing him that the Sc has been rejected by the 1st approver and if he has the authorisation(based on the parameter BBP_WFL_SECURITY) to chnage the SC,he can change the SC and resend it for approval.Then the Sc will be again sent to the 1st approver for approval and the cycle continues.
    To change the SC,the SC creator will be able to see a CHANGE button on the Screen to make the changes and resend the SC for approval.in order to get the change button, the parameter setting level should be atleast "Low".
    See the foll details on security level:
    Security Levels
    Each user in the SRM system can have a Security Level.
    The Security Level predicts how a workflow will react when a change has been made to a business docuement. I.e. A Shopping Cart, Purchase Order etc.
    There are 5 different values for the BBP_WFL_SECURITY and there are several ways to check the security levels.
    Checking the Security Level of a user
    Here I discuss two ways to check the BBP_WFL_SECURITY of a user. The first is by using the Business Object Builder and the second is by using User Maintenance.
    1) Business Object Builder: SWO1
    Logon with a user who is authorized to access transaction SWO1 Business Object Builder.
    Enter the Business Object for a SRM User BUS4101 and press 'Test'. Now press the 'Instance' button to give us the ability to examine the user. Enter the user name of the user and execute. Now we can see many of the attributes that are associated with this user. The Security level of the user is available here. The value is the BBP_WFL_SECURITY for the instanced user.
    2) User Maintenance: SU01
    Logon with a user who is authorized to access transaction SU01 User Maintenance.
    Enter the 'Username' of the user. You can now see much of the data that is associated with this user. To check the users security level we must navigate to the 'Personalization Tab'. Now Double-Click on the object key 'BBP_WFL_SECURITY'.
    Security Level Definition
    As mentioned above, there are 5 different Security Level values that can be assigned to a user, each of which will have a different effect on a workflow when the associated business document has been changed. These range from 0-4 and they can be maintained for each user in User Maintenance (SU01 -> Personalization Tab -> BBP_WFL_SECURITY), provided the user you have logged on with has the ability to make changes to these settings.
    Please note that if the customer has an active implementation of the BBP_WFL_SECUR_BADI, it is possible that the BBP_WFL_SECURITY settings in the database can be overridden.
    BBP_WFL_SECURITY = 4 High
    If the user who changes the purchasing document has their security level set to 'High', the workflow will never restart after the change has taken place. No restart flag has been set in BBP_PDH_WFL_CHECK_RESTART. Again, as mentioned above, the BADI can override these settings.
    BBP_WFL_SECURITY = 3 Medium
    If the user who changes the purchasing document has their security level set to 'Medium', the workflow will re-evaluate the starting conditions of the workflow. If the change made to the document means that the starting conditions of a new workflow are satisfied, then the new workflow will be called and replace the old workflow. The existing workflow will be terminated.
    If, however, no other starting conditions have been satisfied, then the workflow will continue. Again, as mentioned above, the BADI can override these settings.
    BBP_WFL_SECURITY = 2 Low
    If the user who changes the purchasing document has their security level set to 'Low', then the workflow will always restart after the change has been made. The restart flag in function module BBP_PDH_WFL_CHECK_RESTART will be flagged. Again, as mentioned above, the BADI can override these settings.
    BBP_WFL_SECURITY = 1 None
    Here the user does not have a security setting and changes to the document at not possible. Again, as mentioned above, the BADI can override these settings.
    BBP_WFL_SECURITY = 0 Not Defined
    When the setting is '0', however, the value is INITIAL. Again, as mentioned above, the BADI can override these settings.
    It is wise to note that depending on the business document there are differences in how changes will effect a workflow! Please see the function module BBP_PDH_WFL_CHECK_RESTART to see these exactly!
    Workflow Security BADI
    Occasionally, the business requirements of a company necessitate the ability to override the workflow security settings of users. In this case, function module BBP_PDH_WFL_SECLEVEL_GET checks if an active implementation of the BAdI BBP_WFL_SECUR_BADI exists. If it does, then the logic contained in the BAdI will determine what security level is required. If not, then the value will be taken from the database as normal. These can be used specifically to determine whether a purchasing document can be changed during approval and also to determine how the workflow should behave when a change to the purchasing document has taken place.
    HTH
    BR,
    Disha.
    Do reward full points for  useful answers.

  • Moving the Shopping Cart workflow forward in a approver Rejects a line item

    Hi Friends,
       We a facing an issue while Shopping Cart Approval process.
    We have designed our SC Workflow , with Schema and 4 Process levels. Currently the Approvals are happening fine.
    Issue is happening when a Line Item is Rejected by a Single Approver. The Approval process does not move forward.
    We need need to move the SC process forward.
    Ex: SC: 1000000032
    Approval Flow:
    ITEM1:  APP01 -> APP02
    ITEM2:  APP05 -> APP07
    Scenario:01 :
    Once APP01 & APP05 approves in first level.  Then APP02 & APP07 approves . Then the process completes.
    Scenario:02:
    Once APP01 Rejects & APP05 Approves in first level. Then the SC WF does not move forward.
    How can I move the WF process forward once a approver rejects.
    Need your inputs.
    Regards,
    Jagan

    Hello Markus,
    what you describe does not correspond to condition standard determination to know if decision has to be checked or not.
    Indeed, this evaluation is done by /SAPSRM/IF_WF_PROCESS_SBWF~IS_DECISION_ACCEPT_REQUIRED method from /SAPSRM/CL_WF_PROCESS_SBWF class.
    Inside this method, the default behavior is based on decision of current process level:
    - If it is not "rejected" or not "approved" (this means, if it is "inquired"), there is an interaction
    - else, there is no interaction.
    Then, for "rejected" or "approved" decision, a Business Rule evaluation is done in order to check if the document responsible need to accept the current decision.
    If evaluation ID is true, acceptance by Contact Person is required.
    I am currently not able to check workflow behaviour for partial rejection when no acceptance by contact person is customized.
    I will see this next week.
    Regards.
    Laurent.

  • Changing shopping cart in approval stage-SRM 5.0

    Hi All,
    I am facing an issue in Integration environment. It is working fine in Dev.
    Even if the security level at user details is defined as "Low" (2), user is not able to change the shopping cart in approval status (via Check Status, in case of requester or via Approver Inbox, in case of approver).
    Change button is not appearing in the check status.
    I checked following SDN blog but this is not helpful as it is working fine in Dev environment witout deactivating this BADI or implementing it as detailed in this blog.
    http://wiki.sdn.sap.com/wiki/display/SRM/Changingshoppingcartinapproval+stage
    Can someone please let me knwo if I am missing some configuration? Helpful answers will be rewarded. Thanks
    Regards
    Kapil

    Resolved with OSS note- 1397705

  • Change shopping cart status to reject when older than certain period

    Hi Guru's,
    I'm new to this environment.
    Please help me with advice and sample code for the following.
    I need to check if shopping cart is open for more than 20 days then change status to reject, daily background job.
    Then need to inform user of new status via email.
    Which is the correct FM, s to use.
    Many thanks
    Daniel

    Hi
    <b>Here are the steps -></b>
    1. Create a Customer Implementation of BBP_DOC_CHANGE_BADI for Object (filter) type - BUS2121 using SE18 Transaction.
    In the coding, you can set you condition ( >= 20 days then change status to reject)
    2. Using either of the standard Function modules, you can create a Z program to send emails.
    <b>Use the following Standard SAP Function modules -></b>
    SO_OBJECT_PREPARE_FOR_SEND
    SO_OBJECT_SEND
    SO_DOCUMENT_SEND_API1     
    SO_NEW_DOCUMENT_ATT_SEND_API1
    SO_NEW_DOCUMENT_SEND_API1    
    <u>Other related links -></u>
    Re: Email notifications
    SO_NEW_DOCUMENT_SEND_API1 is working in foreground not in background..
    Hope this will help.
    Regards
    - Atul

  • Free Text Shopping cart WorkFlow

    Hi,
    I have to know if a shopping cart was created from a Free text item or from catalog before the WF starts (in a check funtion module).
    Is there any way to know if the shopping cart was created from free text or catalog?
    Thanks

    Hi,
    As per my understanding, you want to make decision, if it is Free text you need to start one work flow, else another workflow.
    This check you can do it in Starting conditions of the workflow. SWB_COND (Transaction).
    Go to SWB_COND, choose business object BUS2121, it will display all work flows which are event linkage activated.
    Now go to specific workflow which you need to start if it is Free text Shopping cart, if the condition is true workflow will start.
    If starting conditions are complex, suggest you to create new attribute and use the same in starting conditions.
    Hope this will be helpful, all the best.
    Regards,
    Mohan Vamsi

  • Changing shopping cart screen

    Hi Expert,
    When I'm creating new shopping cart and found that some tab are collapsed. Is there any way to make it expand in default. I want to expand all tab so that user will not miss out any information to be fill in.
    I found a similar BADI BBP_SC_MODIFY_UI but not sure how this will help.
    Thanks.
    Regards,
    Henry

    Hi,
    See these threads for more pointers:
    Re: Expand all areas in item details as default
    Expand Accounting Details in SC and PO as default
    Definately you need to change the std code for this requirement.There is not std config/setting available for this.

Maybe you are looking for