SRM Process Controlled Workflow - Re-start using FM BBP_PD_SC_UPDATE

Hi All,
We are upgrading from SRM4.0 to SRM7.0 SP07 in classic scenario. We switched to Process Controlled Workflow.
We have a CUSTOM application where the requisition items are entered and a Shopping Cart is created in SRM through Function Module BBP_PD_SC_CREATE. When the Shopping Cart is created in SRM , the Process Controlled Worflow is triggered successfully.
In the custom application , we allow users to do changes to the requisition that are awaiting approval.The changes are updated in SRM Shopping Cart through function module BBP_PD_SC_UPDATE. It is noticed that the workflow process levels are not re-started after the shopping cart is updated through FM BBP_PD_SC_UPDATE.
However , the process levels are re-started when the change is directly done to the Shopping Cart in SRM POWL. We want the process levels to be re-started even when the changes are done through BBP_PD_SC_UPDATE. The users are used do changes to the requisition through the custom application. We also noticed that system does not go through BAdI /SAPSRM/BD_WF_PROCESS_RESTART when changes are done to the SC through BBP_PD_SC_UPDATE.
Is there any way that we can trigger process level re-start when SC is changed through FM BBP_PD_SC_UPDATE
Thanks
Sukumar

HI ,
       This is not the correct way of updating the SC. please check the below process...
       first you try to get the SC document in Edit mode and this can be done only SY-UNAME should requester of the SC or( user who are changing the SC should be in the Org structure ). ( This point why i mentioned is you mentioned that your editing through custom application ).
note : use try and endtry and catch the exception when u get the SC document in Edit mode.
DATA: lo_pdo_sc             TYPE REF TO /sapsrm/cl_pdo_bo_sc_adv.
      "Instance SC PDO Layer
      lo_pdo_sc ?= /sapsrm/cl_pdo_factory_sc_adv=>get_instance( iv_header_guid   = p_guid "ps_shopping_cart-guid
                                                                iv_mode          = /sapsrm/if_pdo_constants_gen_c=>gc_mode_edit ).
   now you do what ever changes to the document. I mentioned points below.
        "Get Item Details
      lo_pdo_sc->/sapsrm/if_pdo_bo_sc~get_item_detail
do changes to the items of the SC.
       "Update SC Items
      lo_pdo_sc->/sapsrm/if_pdo_bo_sc~update_items
       "Submit Update
      lo_pdo_sc->/sapsrm/if_pdo_base~submit_update
       "Save SC
      lo_pdo_sc->/sapsrm/if_pdo_base~save
      or order the SC again.
      COMMIT WORK AND WAIT.
regards,
Devi

Similar Messages

SRM 7.0 Process-controlled Workflow not starting

Hi,
I have problems with implementing an own process-controlled workflow. The "Sample BC Set for Process Level Definition" /SAPSRM/C_SC_600_001_SP04 is working fine. However I do not succeed in triggering a customer Process Schema for BUS2121.
The (first?) problem can be duplicated as following:
1. BC-Set /SAPSRM/C_SC_600_001_SP04 is activated
1.1 When creating a shopping card (Web Portal) a approver ("Head of organizational unit" in OrgManagement) is displayed in the Details (Approval-Workitem is created when saving the shopping cart)
--> OK
2. Deactivation of Process Schema 3C_SC_600_001 (replace Eval.IDs with customer Eval.ID which contains always false expression)
--> When creating a shopping card (Web Portal) no approval data is displayed in the Details
--> OK
3. Copy Process Schema 3C_SC_600_001 into ZC_SC_600_001; replace customer Eval.ID with original Eval.IDs (Boole; no process schema in expression (Eval-ID 3EV_SC_600_001_100; Expression 3B_SC_600_001_100: "Execute always"))
--> When creating a shopping card (Web Portal) no approval data is displayed in the Details
--> NOT OK; the same result as with 1.1 is expected
Why is 3. not working? Any ideas would be very welcome.
Best regards

Hi..
what do you see in SLG1? .. i think your process level Eval.id result is false, that is the reason workflow is not kicking of
1- level approval.. check your process level configure and try to use 0ev000 as a Eval.Id instead your custom Eval.Id and test..
Saravanan

SRM Process Controlled Workflow

Hi Exports,
I have created a Process schema for SC object type (BUS2121)..
Looks like my process levels are trigged before the shopping cart is actually ordered by the user..
Is this a normal behavior? or I am missing any configuration? or I need to have a additional process level initially to check whether the SC completed?..
Please advice..
Thanks in advance
Bharath

HI,
Yes. That is correct task ID.
FYI. Task ID List for Process-Controlled Workflow
SRM Contract     BUS2000113               No Completion Task
          40007980     SRM_CT_APPR1     SRM Contract Approval
          40008003     SRM_CTR_Acc     Accept Decision / Adjust Document
          40007997     SRM_CTR_Revi     Revise Document
          40107926     SRM_CTR_RW     review document
SRM Shopping Cart     BUS2121
                                           40007952     SRM_SC_COMP1     SRM Shopping Cart Completion
          40007953     SRM_SC_APPR1     SRM Shopping Cart Approval (1)
          40007954     SRM_SC_APPR2     SRM Shopping Cart Approval (2)
          40007994     SRM_SC_Acc     Accept Decision / Adjust Document
          40007936     SRM_SC_Revi     Revise Document
          40007945     SRM_SC_RW     Review Document
SRM RFx     BUS2200     40107917     SRM_BI_COMP1     SRM RFx Completion
          40007982     SRM_BI_APPR1     SRM RFx Approval
          40107922     SRM_RFx_Acc     Accept Decision / Adjust Document
          40007998     SRM_RFQ_Revi     Revise Document
          40107927     SRM_RFQ_RW     Review Document
SRM Purchase Order     BUS2201
                                           40007973     SRM_PO_COMP1     SRM Purchase Order Completion
          40007974     SRM_PO_APPR1     SRM Purchase Order Approval
          40007995     SRM_PO_Acc     Accept Decision / Adjust Document
          40007996     SRM_PO_Revi     Revise Document
          40107924     SRM_PO_RW     Review Document
SRM Supplier Quote     BUS2202               No Completion Task
          40007981     SRM_QT_APPR1     SRM RFx Response/Bid Approval
                    No Adjust task
          40007999     SRM_QTE_Revi     Revise Document
          40107928     SRM_QTE_RW     Review Document
                    No Completion Task
          40008000     SRM_QT_APPR2     SRM Bid Approval
                    No Adjust task
          40107934     srm_bid_revi     Revise Bid
          40107935     srm_bid_rw     Review Bid
SRM Confirmation of Goods/Service     BUS2203               No Completion Task
          40007987     SRM_CF_APPR1     SRM Confirmation Approval
                    No Adjust task
          40008004     SRM_CF_Revi     Revise Document
          40107929     SRM_CF_RW     review confirmation
SRM Incoming Invoice     BUS2205               No Completion Task
          40008005     SRM_IV_APPR1     SRM Invoice Approval
                    No Adjust task
          40008006     SRM_IV_Revi     Revise Document
          40107925     SRM_IV_RW     Review Document
Auto          40007988     SRM_AUTOAPP     Automatic Approval
Auto          40007989     SRM_AUTOREJ     Automatic Rejection
Regards,
Masa

SRM Process Controlled Workflow Issue - Process Level Agent not shown up

System: SRM 7.0 (SP09)
Implemented BADI to determine agents at process level - BADI Definition /SAPSRM/BD_WF_PROCESS_CONFIG
Configuration: 1 Process Level (Seq 100, Lvl Type A, Resp. Resolver Name: Z_XXXXXX, Task ID 40007954, Decision Type 1)
When creating the Shopping cart based on the cart value, the agents are determined correctly and process level GUID is created with Agent ID associated.
something like
GUID1 - APPR1
GUID2 - APPR2
GUID3 - APPR3
GUID4 - APPR4
Before "Order" when we do preview of Approval Process, it shows all the approvers in the sequence as expected. As soon as the cart is ordered, the first process level GUID lost its agent thus throwing error saying "Strategy Z_XXXXXX did not determine any approver"
But when we look at the table /SAPSRM/D_WF_016, the corresponding entires of GUID1 has the agent ID as APPR1.
The task 40007954 has been GENERALIZED so as the master workflow template 40000014. The same is working in our Dev system but throwing error "Strategy Z_XXXXXX did not determine any approver" in QA system.
Any input is highly appreciated.

See the thing is the agents were picked up & saved in the table /SAPSRM/D_WF_016 in the process level BADI. The first process level guid doesn't get processed in the RESP_RESOLVER BADI. I put the break point and can see the agents were picked up & saved in Process Level BADI.
The funny part is it is working just fine in the Dev system. Secondly, when we do BOB for the same user (requester), it picks up the first level approver without the error.
Meaning, If USER1 shops for himself (Creator & Requester are same), we encounter this error. If USER2 shops for USER1, then the corresponding approvers were picked up correctly without the error. USER1 & USER2 have same authorizations in SU01D (USER2 is copy of USER1, so no authorization issues). Approvers determination is based on the requester.
Somewhere, we miss the settings. Don't know where though.

How to determine N Step Approval process through Process Controlled workflow

HI
For SC approval process after 4th level of approval the workflow keep go N step till the approval determine. If no approval find then go for WF Exceptions.
In PCW we have process level like 100, 200, 300 and so on. What would be the procedure for Nth process level determination in SRM process controlled workflows settings.
Regards
Kharabela

Hi,
From SRM 7.0 PCW, requestor of SC or creator(buyer) of the PO can't be in the approval list.. this is standard...
create two custom events like zev_po_schema_eva and zev_po_sl_approval
create two custom expression.. one with constants as zev_po_schema_def and other one is formula interpreter(0FB001)..
assign zev_po_schema_eva as schema evaluation for PO.. MAKE SURE YOU LINK THE zev_po_sl_approval
with as zev_po_schema_def..
   now create schema definition entry and specify as zev_po_schema_def..
   now create process level
   100 approval / approval with completion ( Your chooice ) .. maintain zev_po_sl_approval as evaluation id in the process level... maintain RR_SPENDING_LIMIT_APPROVER as Resp.Resolver...
maintain formula interperter value as (OV_SC_PREVAPPROVALIMI < 0V_PO_POTOTALVALUE ) AND (OV_SC_SPNDNGLMTFRQST < 0V_PO_POTOTALVALUE).
Saravanan

Complexity of using N-step BADI in SRM 7using Process controlled Workflow.

Hi,
Just as a big thought,
I have a Shopping Cart requirement, Here i am asked to develop a Custom workflow for SRM 7.0.
And the client is looking for us to use Process Control Workflows i.e(BRF integrated one).
I need to understand the complexity of using a N-step BADI.
How would be the complexity level if I use a N step BADI( ie Multiple approval levels on Line Item Based).
Kindly tell me the complexity of Using it and if any one has come across some requirement like this, then explain me that how did you face the situation.
Expecting an Earliest Response.
Thanks,
Shanky

Hi,
Is your project SRM 7.0 implementation project then you have to go for Process Controlled Workflow and if your project is upgrade then you can still go with Application Controlled Workflow but down line this has to switch to Process Controlled Workflow.
Best Regards,
Saravanan

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

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 is not starting

Hi,
I have problems with implementing an own process-controlled workflow. The "Sample BC Set for Process Level Definition" /SAPSRM/C_SC_600_001_SP04 is working fine. However I do not succeed in triggering a customer Process Schema for BUS2121.
The (first?) problem can be duplicated as following:
1. BC-Set /SAPSRM/C_SC_600_001_SP04 is activated
1.1 When creating a shopping card (Web Portal) a approver ("Head of organizational unit" in OrgManagement) is displayed in the Details (Approval-Workitem is created when saving the shopping cart)
--> OK
2. Deactivation of Process Schema 3C_SC_600_001 (replace Eval.IDs with customer Eval.ID which contains always false expression)
--> When creating a shopping card (Web Portal) no approval data is displayed in the Details
--> OK
3. Copy Process Schema 3C_SC_600_001 into ZC_SC_600_001; replace customer Eval.ID with original Eval.IDs (Boole; no process schema in expression (Eval-ID 3EV_SC_600_001_100; Expression 3B_SC_600_001_100: "Execute always"))
--> When creating a shopping card (Web Portal) no approval data is displayed in the Details
--> NOT OK; the same result as with 1.1 is expected
Why is 3. not working? Any ideas would be very welcome.
Best regards

In most cases, this means that the 'Start Process' is not configured correctly. Take a look at the following:
1. make sure that the Wf assigned to your start process is active
2. make sure that reference numbers are configured and assigned to your process
3. assign a user to receive error messages when an error occurs
Thanks,
Derrick Banks

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.

Useful link for Process controlled workflow

FYI Useful link for Process controlled workflow..
http://help.sap.com/saphelp_srm70/helpdata/en/74/c0256bebb54f1c8dfb519d2908152b/frameset.htm
Thanks!!
Bharath

Hi Peter Novoth,
Can you please create this as a sticky thread, so that this will be us full for everyone..
Thanks!!
Bharath

Process-controlled workflow hang due to dump

Hi all,
due to a temporary dump in an SRM 7 system, some document-related workflows are stucked... in other terms, these workflow processes have been started, the the dump occoured and by now, they seems to be stucked in "in process" state.
Tecnically, these are not workflow in error, so SWI2_DIAG is not helpful.
We'd like to unlock this situation and -eventually- restart the workflow process. How can we do it?
Thanks in advance for your help and support.
edit: system dump is now solved, which means, triggering the same workflow process will result in a success.
Edited by: Matteo Montalto on Jun 30, 2011 4:34 PM

Ok. There used to be OSS Note 1458380 - Process Controlled Workflow Restart Program, if the document is in "Awaiting Approval" Status.
Or do the manual restart by using tcode SWUE (Event trigger)
Object Category - ABAP Class
Object Type - /SAPSRM/CL_WF_PDO_SC
Event - READY_FOR_WORKFLOW
Object Key - <DOCUMENT_GUID>
Event Parameter - <SC Creator User ID>
and Click "Create Event" button
Use SWI1 to check whether the event is created and see whether the document is submitted for workflow triggering or use SWI6 to check for that SC document

Advantage of Process-Controlled Workflow

Good Morning!
What are the advantage of Process-Controlled Workflow? (and/or what are the advantage of Business-Rule-Framework?)

I am looking at a SRM 5.5 upgrade to SRM 7 and moving to PCW represents issues and risk to me.
The SAP Migration program /sapsrm/pr_wf_migration_cfg does not deal with the N Step Badi Wf's.
SAP's recommendation is to complete all active Wf's are restart with PCW which means finalising all approvals restarting Approvals using PCW from the start,
SAP recommend ALL processes should be moved to PCW from ACW in a production environment.
If your trying to implement a ACW N Step Badi in PCW then you will probably be looking at Resp Resolvers that refer to a Badi implementation where you will need abap code.
Not sure about a flexible set of approval levels, but think that's another Badi implementation, with abap code.
Not over impressed, I'm afraid. Better structured abap program code in the N Step BADI could be an improvement

Process Controlled Workflows VS Applicaiton Enabled Workflows-What to chose

G'Day All,
We are upgrading from SRM5.0 to SRM7.0
There are these bespoke shopping cart approval workflows developed previously. I have to do some sort of assessment to include
1) Why would we go for PCWs instead of just migrating the old ones in SRM 7.0 as business is pretty happy with the functionality they have got and are not interested in revising the workflow processes. Answer : Application enabled workflows are in maintainence mode so newer functionality would be delivered using PCWs.( is there any other justification ? )
2) Would we be able to map the existing workflow process to PCWs, here i need some pointers. I understand the PCWs are based on BRF though i don't know much about BRF( updating myself ). The key question i have is, whatever is there in bespoke workflow templates would i be able to replicate that using this i.e. a different technology. Since my exposure to either PCWs or BRF is not great so as a general rule i am asking, is it possible or are there any sort of technical limitations on what you can and what you can't do using PCWs which you could design using a normal workflow template?
I am sure this would be a common analysis which many of you might have done or are doing if you are involved in an upgrade.
An Interesting Fact : There is no documentation available on existing SRM 5.0 workflows as what differently they have done to standard. The only thing i know at this stage is they have a bespoke level 1 template which call different standard templates for n level approval process. The apporval process( agent determination ) is based purely on custom logic. I am not that worried about the agent determination as i know i could get that as rule evaluation in BRF. The crux for me is to understand how BRFcontrols or connects to workflow templates in this particular case and what permutation conbinations are possible.
So, i want to have a discussion on this and if possible some insight on all this new PCWs.
Hope to see some valuable comments.
Regards
Praveen

Hi everyone:
My question is the following.
We will implement SRM 7.01 with Process Controlled Workflow.
However in the manual is the following note:
Note: Even if you decide to use Process-Controlled Workflow in general,
there are a few workflows still on the old technology:
WS10400022 . Contract Alert Workflow
WS10000192 - Approval Workflow for Internal Users
WS10000209 - Approval workflow for new bidder/supplier
WS10000093/WS10000100 -Procurement Card Approval
Probably We will required some of this.
My question is if we are planning to configure process and application the correct strategy will be:
1.     Start the configuration with the application controlled workflow and then
2.     Follow with the change of the configuration application to process controlled workflow
3.     And configure the workflowu2019s in process.
u2022     Is there any problem when if we change the check application to process? Are there any chance that we loss the configuration?
u2022     Is there any problem in the functionality that both kinds of workflow (application-process) work at the same time?
u2022     If is possible to make change or maintenance of the application workflow?
Thanksu2019 a lot for all the help
Best Regards

Issue in Process Controlled workflow for Shopping cart in Quality system.

Hello All,
I ahve configured a Process controlled workflow in SRM 7.0 with custom resolver, and I am facing an issue taht the Workflow works well in Development but in Quality the approvers are dropped after SC is ordered in Quality system.
The SC Workflow drops the approvers picked up from the Interface method /SAPSRM/IF_EX_WF_RESP_RESOLVERGET_AREA_TO_ITEM_MAP and IF_EX_WF_RESP_RESOLVERGET_APPROVERS_BY_AREA_GUID of BADI /SAPSRM/BD_WF_RESP_RESOLVER. The approvers can be seen in the shopping cart Approval preview Tab until the SC is ordered.
I have compared the OSS notes relevant for Workflow, all of them have been transported, Also I compared and checked general Workflow settings, BRF Config and Process level settings in Dev and Quality, everything is same.
Also while debugging; the approvers can be seen in the decision set table in the create_process_forecast method of class /SAPSRM/CL_WF_PROCESS_MANAGER.
Kindly let me know what else i can check to find the root cause.
Thank you in advance for help!
Regards
Prasuna.

Hello Vinita;
Thanks for the input and sorry for the not so "ASAP" reply;
From what I'm seeing in from your 2 screenshot, i strongly believe that the problem is even before the Z implementation /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_APPROVERS_BY_AREA_GUID (in which the FM i ZSRM_GET_USER_FROM_PGRP is called. I think the problem could be in the process level determination ZSRM_WF_BRF_0EXP000_SC_APP100. Let me explain:
In your cases where not buyer is determined, in the approval tab there is not even a process level for buyer approval. If the problem were indeed in the implementation /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_APPROVERS_BY_AREA_GUID then the process level would be there, but the system will display, instead of the name of the buyer(if the buyer determination fails) a red label with the message: "With the strategy "Buyer determination" an approver could not be determined (or something like that..please check the image at the end of the text)".
I can propose a way to discard this: Implement the method /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_FALLBACK_AGENTS of class ZCL_BADI_SC_WC (in case you didn't know, in this method you can specify an "default" approver in case that the determination of approver in GET_APPROVERS_BY_AREA_GUID fails). The idea is to specify an default approval and see how it behaves:
If the user you indicated in the method GET_FALLBACK_AGENTS appears as approver, then yes, the problem is arises from implementation GET_APPROVERS_BY_AREA_GUID, in which case it could be a data problem (peharps in pposa_bbp?). You could also check in TX SU53 with the users with this problem to see if there's a missing authorization objetc.
If, in the other hand, the "default" approver is not shown, it means that the process level buyer determination is not even called, so you should check in more detail ZSRM_WF_BRF_0EXP000_SC_APP100 and /SAPSRM/CL_WF_PROCESS_MANAGER > Determine process restart –method ----- (i have never used this method, so i could not tell if it could be the source of the problem).
Also, you could implement the method GET_FALLBACK_AGENTS in this way so the default approver would be the WF administrator indicated in the customizing (or you could just append directly any user you want):
METHOD /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_FALLBACK_AGENTS.
   DATA: lv_admin_expr TYPE swd_shead-admin_expr,
         lv_admin      TYPE swd_shead-wfi_admin,
         lv_admin_type TYPE sy-input,
         ls_agent      TYPE /sapsrm/s_wf_approver.
   CALL FUNCTION 'SWD_WF_DEFINITION_ADMIN_GET'
     IMPORTING
       default_admin_expr = lv_admin_expr
       default_admin      = lv_admin
       default_admin_type = lv_admin_type.
   ls_agent-approver_id = lv_admin.
   APPEND ls_agent TO rt_agent.
ENDMETHOD.
Error of agent determination:
Please let me know the result of the test with the implementation of method GET_FALLBACK_AGENT. By doing this we could ensure if really the problem is in method GET_APPROVERS_BY_AREA_GUID or before. I just made the test in our system and I'm almost sure that you wont get the default approver, but i could be wrong.
Any question please let me know.
Best regards
Cristian R.

SRM Process Controlled Workflow - Re-start using FM BBP_PD_SC_UPDATE

Similar Messages

Maybe you are looking for